Talk:Oneplus phone update introduces hardware anti-rollback - Revision history

ELZURIX: /* Seems like they're going to revert this */ new section

2026-01-28T22:57:54Z

Seems like they're going to revert this: new section

← Older revision		Revision as of 22:57, 28 January 2026
Line 18:		Line 18:

	[https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/post-90459478] ROMs are being replaced with ones that got the same version number but with the fuse trigger [[User:SinexTitan\|SinexTitan]] ([[User talk:SinexTitan\|talk]]) 09:26, 24 January 2026 (UTC)		[https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/post-90459478] ROMs are being replaced with ones that got the same version number but with the fuse trigger [[User:SinexTitan\|SinexTitan]] ([[User talk:SinexTitan\|talk]]) 09:26, 24 January 2026 (UTC)

			== Seems like they're going to revert this ==

			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? [[User:ELZURIX\|ELZURIX]] ([[User talk:ELZURIX\|talk]]) 22:57, 28 January 2026 (UTC)

SinexTitan: /* more batshit crazy */ new section

2026-01-24T09:26:27Z

more batshit crazy: new section

← Older revision		Revision as of 09:26, 24 January 2026
Line 14:		Line 14:

	: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 [https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/#post-90452179 caution]. in the same thread they also [https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/post-90454883 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". [[User:SinexTitan\|SinexTitan]] ([[User talk:SinexTitan\|talk]]) 09:16, 24 January 2026 (UTC)		: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 [https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/#post-90452179 caution]. in the same thread they also [https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/post-90454883 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". [[User:SinexTitan\|SinexTitan]] ([[User talk:SinexTitan\|talk]]) 09:16, 24 January 2026 (UTC)

			== more batshit crazy ==

			[https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/post-90459478] ROMs are being replaced with ones that got the same version number but with the fuse trigger [[User:SinexTitan\|SinexTitan]] ([[User talk:SinexTitan\|talk]]) 09:26, 24 January 2026 (UTC)

SinexTitan: /* potentially a little misleading / missing info? */ Reply

2026-01-24T09:16:28Z

potentially a little misleading / missing info?: Reply

← Older revision		Revision as of 09:16, 24 January 2026
Line 1:		Line 1:
	== title change ==		==title change==

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

	== potentially a little misleading / missing info? ==		==potentially a little misleading / missing info?==

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

	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." [[User:Ceremony846923\|Ceremony846923]] ([[User talk:Ceremony846923\|talk]]) 09:04, 24 January 2026 (UTC)		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." [[User:Ceremony846923\|Ceremony846923]] ([[User talk:Ceremony846923\|talk]]) 09:04, 24 January 2026 (UTC)

			: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 [https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/#post-90452179 caution]. in the same thread they also [https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/post-90454883 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". [[User:SinexTitan\|SinexTitan]] ([[User talk:SinexTitan\|talk]]) 09:16, 24 January 2026 (UTC)

Ceremony846923: /* potentially a little misleading / missing info? */ new section

2026-01-24T09:04:05Z

potentially a little misleading / missing info?: new section

← Older revision		Revision as of 09:04, 24 January 2026
Line 2:		Line 2:

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

			== potentially a little misleading / missing info? ==

			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." [[User:Ceremony846923\|Ceremony846923]] ([[User talk:Ceremony846923\|talk]]) 09:04, 24 January 2026 (UTC)

SinexTitan: /* title change */ new section

2026-01-23T20:09:59Z

title change: new section

New page

== title change ==

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