Jump to content

Talk:Oneplus phone update introduces hardware anti-rollback

Add topic
From Consumer Rights Wiki
Revision as of 22:57, 28 January 2026 by ELZURIX (talk | contribs) (Seems like they're going to revert this: new section)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Latest comment: 28 January by ELZURIX in topic Seems like they're going to revert this

title change

[edit source]

from a OnePlus issue its turned to a ColorOS (mb BBK let's see) issue as Oppo devices are also getting it SinexTitan (talk) 20:09, 23 January 2026 (UTC)Reply

potentially a little misleading / missing info?

[edit source]

as the discussion went on the oneplus subreddit, someone replied with some unverified information that may be helpful

https://www.reddit.com/r/oneplus/comments/1qlcb5a/comment/o1dnmkq/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

"That is quite misleading.

It applies only to China-regioned Snapdragon 8 Elite device which have updated to the latest ColorOS for now. (13, 13T, Find X8U, OnePlus Pad 2 Pro) This update triggers ARB protection in the AVB implementation, the reason being older versions of AVB on those firmwares contained a EDL signature leaked to the Chimera tool and Cellebrite, which could enable extraction of data from devices without the owner even knowing. However, OnePlus did this in a very rushed way which led to the mass bricking. This can currently be avoided on unlocked phones by substituting the new ARB-related images with older versions.(abl.img、xbl.img、xbl_config.img、xbl_ramdump.img). Custom ROM developers/maintainers will need to update their package to keep working. Allegedly OnePlus is working on new downgrade packages for the affected devices to prevent the bricking from happening, and changing how ARB works on other devices so custom ROMs or any other flashing with unlocked bootloader will not cause a brick. OnePlus have also issued a Service Bulletin in China to repair centers to rebate or refund 100% of motherboard replacements caused by the issue." Ceremony846923 (talk) 09:04, 24 January 2026 (UTC)Reply

the way I see it. one does not implement ARB by mistake. it was a conscientious decision to do it like this but due to the backlash they could've changed their stance on the matter. we might not know till it gets confirmed. now regarding CN vs other variants, the person that broke the news, AdaUnlocked themselves advise caution. in the same thread they also addressed being called misleading/spreading missinfo but albeit regarding the existence of the efuses. we apply the American method to this one for now "guilty till proven otherwise". SinexTitan (talk) 09:16, 24 January 2026 (UTC)Reply

more batshit crazy

[edit source]

[1] ROMs are being replaced with ones that got the same version number but with the fuse trigger SinexTitan (talk) 09:26, 24 January 2026 (UTC)Reply

Seems like they're going to revert this

[edit source]

https://9to5google.com/2026/01/27/oneplus-anti-rollback-measures-only-temporary-downgrades-returning-soon/

"Temporary", yeah, sure

Seems like they got too much backlash so they finally are doing the right thing, I hope? ELZURIX (talk) 22:57, 28 January 2026 (UTC)Reply