- cross-posted to:
- oneplus@lemdro.id
- cross-posted to:
- oneplus@lemdro.id
You must log in or # to comment.
Ok then; fuck you to hell, oneplus.
It’s MY phone, and I should have the final say about whatever happens on my phone.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.
