Ok then; fuck you to hell, oneplus.
It's MY phone, and I should have the final say about whatever happens on my phone.
this post was submitted on 20 Jan 2026
21 points (88.9% liked)
Android
21024 readers
279 users here now
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: !android@lemdro.id
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 2 years ago
MODERATORS
Flashing a custom ROM prior to this update on top of ColorOS 16.0.3.501 (or newer) will result in an immediate hard brick. This is because, as of now, almost all current Custom ROMs for the OnePlus 13 / Ace 5 were built before this fuse policy came into existence.
π€
Why are they doing this?
Apart from being anti-consumer its also a security feature. They were probably asked to implement this by the indian governement in the security mandate. https://www.reuters.com/world/china/indias-proposed-phone-security-rules-that-are-worrying-tech-firms-2026-01-11/
Oneplus was the last consumer friendly brand we knew. Oppo is now ruining and making it moapplied apple and samsung.
The most charitable thing I can think of is anti-tampering, potentially some sort of exploit in the prior version to install undetectable malware then upgrading back to the latest where it could still be retained but not newly installed?
Idk tho seems just anti-consumer "Never settle"
A design that results in a hard brick on "tampering" is unusually destructive.
Say you buy a phone online, it's comes in DOA/bricked due to being tampered with in-transit.
Seems better then unknowingly getting a tampered with phone with spyware hooked in, and like my oneplus 6t just gives a generic "bootloader unlocked" that most end-users wouldn't really understand by comparison.
Idk still seems too destructive to me as well but I can see some possible rationale.
Pixels have a pretty strong warning on boot for unlocked bootloaders and an easily-typed URL with a detailed explanation.
That seems like enough to me from the manufacturer side. Of course I can imagine someone ignoring the warning; people sometimes climb into tiger enclosures with predictable results, but it shouldn't be on device manufacturers (or zoo management) to prevent all possible negative outcomes.
Pixels also have this anti rollback protection, IIRC. I'm unable to flash LineageOS based on Android 15 since I'm on Android 16.
I hadn't heard of Pixels doing that, but I'm guessing the attempt does not hard-brick the device.
I don't disagree at all, this is my most charitable take, definitely just ends up being anti-consumer.