Oneplus phone update introduces hardware anti-rollback: Difference between revisions
→Company response: grammar - Capitalised P for OnePlus |
m link "custom ROM"; minor fmt |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 11: | Line 11: | ||
}}{{OngoingEvent}} | }}{{OngoingEvent}} | ||
The OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident refers to the January 2026 deployment of firmware updates by [[OnePlus]] that introduced a hardware-level anti-rollback mechanism. This permanently prevents users from downgrading their devices or installing custom ROMs. The updates, which affected the OnePlus 13, OnePlus 13T, and OnePlus 15, irreversibly blow electronic fuses inside the device's [[Qualcomm]] processor. Any subsequent attempt to install older firmware results in a permanent "hard brick" - the device becomes unusable. This cannot be repaired through standard methods.<ref name="xda-warning">{{cite web |url=https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |title=[CRITICAL WARNING] ColorOS 16.0.3.501 Updates = PERMANENT Anti-Rollback (ARB) & Fuse Blown. DO NOT DOWNGRADE! |website=XDA Forums |date=January 19, 2026 |access-date=January 22, 2026}}</ref> | The OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident refers to the January 2026 deployment of firmware updates by [[OnePlus]] that introduced a hardware-level anti-rollback mechanism. This permanently prevents users from downgrading their devices or installing [[wikipedia:List_of_custom_Android_distributions|custom ROMs]]. The updates, which affected the OnePlus 13, OnePlus 13T, and OnePlus 15, irreversibly blow electronic fuses inside the device's [[Qualcomm]] processor. Any subsequent attempt to install older firmware results in a permanent "hard brick" - the device becomes unusable. This cannot be repaired through standard methods.<ref name="xda-warning">{{cite web |url=https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |title=[CRITICAL WARNING] ColorOS 16.0.3.501 Updates = PERMANENT Anti-Rollback (ARB) & Fuse Blown. DO NOT DOWNGRADE! |website=XDA Forums |date=January 19, 2026 |access-date=January 22, 2026 |archive-url=http://web.archive.org/web/20260126173832/https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |archive-date=26 Jan 2026}}</ref> | ||
OnePlus has not issued any official statement addressing the mechanism.<ref name="android-authority">{{cite web |url=https://www.androidauthority.com/oneplus-arb-protection-3633783/ |title=New OnePlus updates can permanently lock your phone's software future |author=Adamya Sharma |website=Android Authority |date=January 19, 2026 |access-date=January 22, 2026}}</ref> | OnePlus has not issued any official statement addressing the mechanism.<ref name="android-authority">{{cite web |url=https://www.androidauthority.com/oneplus-arb-protection-3633783/ |title=New OnePlus updates can permanently lock your phone's software future |author=Adamya Sharma |website=Android Authority |date=January 19, 2026 |access-date=January 22, 2026 |archive-url=http://web.archive.org/web/20260127150054/https://www.androidauthority.com/oneplus-arb-protection-3633783/ |archive-date=27 Jan 2026}}</ref> | ||
==Background== | ==Background== | ||
OnePlus was founded on December 16, 2013, by Pete Lau and Carl Pei, both former OPPO executives, with OPPO Electronics as the primary investor. The company's first device, the OnePlus One, shipped with [[wikipedia:CyanogenMod|CyanogenMod]], a commercial variant of the popular custom ROM, through an exclusive licensing agreement with Cyanogen Inc.This partnership positioned OnePlus as a choice for modding enthusiasts. | OnePlus was founded on December 16, 2013, by Pete Lau and Carl Pei, both former OPPO executives, with OPPO Electronics as the primary investor. The company's first device, the OnePlus One, shipped with [[wikipedia:CyanogenMod|CyanogenMod]], a commercial variant of the popular custom ROM, through an exclusive licensing agreement with Cyanogen Inc. This partnership positioned OnePlus as a choice for modding enthusiasts. | ||
When that partnership collapsed due to Cyanogen's exclusivity deal with Micromax in India, OnePlus developed OxygenOS for global markets and HydrogenOS for China. In July 2021, OnePlus merged OxygenOS with OPPO's ColorOS, sharing a common codebase while maintaining separate branding for different regions. | When that partnership collapsed due to Cyanogen's exclusivity deal with Micromax in India, OnePlus developed OxygenOS for global markets and HydrogenOS for China. In July 2021, OnePlus merged OxygenOS with OPPO's ColorOS, sharing a common codebase while maintaining separate branding for different regions. | ||
| Line 27: | Line 27: | ||
On January 19, 2026, XDA Forums member AdaUnlocked posted a warning thread documenting the issue with evidence including chat logs showing that the CPU anti-rollback fuse had been blown, warnings from paid unbrick services stating that Snapdragon 8 Elite devices updated to the affected build should not be downgraded, & user reports confirming that motherboard replacement was required after failed downgrade attempts.<ref name="xda-warning" /> | On January 19, 2026, XDA Forums member AdaUnlocked posted a warning thread documenting the issue with evidence including chat logs showing that the CPU anti-rollback fuse had been blown, warnings from paid unbrick services stating that Snapdragon 8 Elite devices updated to the affected build should not be downgraded, & user reports confirming that motherboard replacement was required after failed downgrade attempts.<ref name="xda-warning" /> | ||
DroidWin confirmed that OnePlus had removed the download links for the OnePlus 13 downgrade firmware for all regions and that OnePlus 12 downgrade packages had been removed as well.<ref name="droidwin">{{cite web |url=https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |title=OnePlus Android 16 Anti Rollback is Here! |author=Sadique Hassan |website=DroidWin |date=January 20, 2026 |access-date=January 22, 2026}}</ref> | DroidWin confirmed that OnePlus had removed the download links for the OnePlus 13 downgrade firmware for all regions and that OnePlus 12 downgrade packages had been removed as well.<ref name="droidwin">{{cite web |url=https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |title=OnePlus Android 16 Anti Rollback is Here! |author=Sadique Hassan |website=DroidWin |date=January 20, 2026 |access-date=January 22, 2026 |archive-url=http://web.archive.org/web/20260126150930/https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |archive-date=26 Jan 2026}}</ref> | ||
==Affected devices== | ==Affected devices== | ||
| Line 33: | Line 33: | ||
The following devices and firmware versions have been confirmed to trigger the anti-rollback fuse: | The following devices and firmware versions have been confirmed to trigger the anti-rollback fuse: | ||
*OnePlus 13 / 13T: ColorOS 16.0.3.501<ref name="xda-warning" /> | *OnePlus 13 / 13T: ColorOS 16.0.3.501 / OxygenOS 16.0.3.501<ref name="xda-warning" /> | ||
*OnePlus 15: ColorOS 16.0.3.503<ref name="xda-warning" /> | *OnePlus 15: ColorOS 16.0.3.503<ref name="xda-warning" /> | ||
*OnePlus Nord CE 3: OOS 15.0.0.1301 | *OnePlus Nord CE 3: OOS 15.0.0.1301 | ||
| Line 49: | Line 49: | ||
When the device powers on, the Primary Boot Loader (PBL) in the processor's ROM loads and verifies the eXtensible Boot Loader (XBL). The PBL reads the current anti-rollback version from the Qfprom fuses and compares it against the firmware's embedded version number. If the firmware version is lower than the fuse value, boot is rejected. When newer firmware successfully boots, the bootloader issues commands through Qualcomm's TrustZone to blow additional fuses, permanently recording the new minimum version.<ref name="xda-warning" /> | When the device powers on, the Primary Boot Loader (PBL) in the processor's ROM loads and verifies the eXtensible Boot Loader (XBL). The PBL reads the current anti-rollback version from the Qfprom fuses and compares it against the firmware's embedded version number. If the firmware version is lower than the fuse value, boot is rejected. When newer firmware successfully boots, the bootloader issues commands through Qualcomm's TrustZone to blow additional fuses, permanently recording the new minimum version.<ref name="xda-warning" /> | ||
EDL (Emergency Download Mode), historically the last-resort recovery option using USB interface 9008, cannot bypass this | EDL (Emergency Download Mode), historically the last-resort recovery option using USB interface 9008, cannot bypass this restriction. While EDL operates from the Primary Boot Loader ROM and allows direct storage writes, the eFuses remain in the processor silicon. EDL's Firehose programmers must be OEM-signed and contain their own anti-rollback versions; previously functional unbrick tools now fail because the fuse has been blown.<ref name="xda-warning" /> | ||
As explained on the XDA thread, the term "Fuse Blown" refers to the Qfprom eFuses (Electronic Fuses) inside the Snapdragon chipset being electrically switched from "0" to "1", effectively preventing older software from running, rather than a physical fuse burnout.<ref name="xda-warning" /> | As explained on the XDA thread, the term "Fuse Blown" refers to the Qfprom eFuses (Electronic Fuses) inside the Snapdragon chipset being electrically switched from "0" to "1", effectively preventing older software from running, rather than a physical fuse burnout.<ref name="xda-warning" /> | ||
| Line 61: | Line 61: | ||
==Company response== | ==Company response== | ||
As of 23 January, 2026, OnePlus and OPPO have issued no official statement addressing the anti-rollback fuse mechanism. No press releases, community forum responses, or social media acknowledgments explain the policy or respond to reports of bricked devices.<ref name="android-authority-opinion">{{cite web |url=https://www.androidauthority.com/oneplus-fan-modding-bootloader-changes-breaking-point-3634505/ |title=I've been a OnePlus fan for 12 years, but this latest update is my breaking point |author=Dhruv Bhutani |website=Android Authority |date=January 23, 2026 |access-date=January 26, 2026}}</ref> | As of 23 January, 2026, OnePlus and OPPO have issued no official statement addressing the anti-rollback fuse mechanism. No press releases, community forum responses, or social media acknowledgments explain the policy or respond to reports of bricked devices.<ref name="android-authority-opinion">{{cite web |url=https://www.androidauthority.com/oneplus-fan-modding-bootloader-changes-breaking-point-3634505/ |title=I've been a OnePlus fan for 12 years, but this latest update is my breaking point |author=Dhruv Bhutani |website=Android Authority |date=January 23, 2026 |access-date=January 26, 2026 |archive-url=http://web.archive.org/web/20260222112757/https://www.androidauthority.com/oneplus-fan-modding-bootloader-changes-breaking-point-3634505/ |archive-date=22 Feb 2026}}</ref> | ||
The removal of official downgrade packages from OnePlus' community forums on 19 January, 2026, was interpreted by users as confirmation that the mechanism was intentional.<ref name="droidwin" /> | The removal of official downgrade packages from OnePlus' community forums on 19 January, 2026, was interpreted by users as confirmation that the mechanism was intentional.<ref name="droidwin" /> | ||
On January 27th 2026, in response to Android Authority OnePlus issued the following statement.<ref>{{Cite web |last=Simons |first=Hadlee |date=2026-01-27 |title=Here's why OnePlus bricked your phone when you tried downgrading it |url=https://www.androidauthority.com/oneplus-brick-phones-statement-3635475/ |url-status=live |access-date=2026-01-27 |website=Android Authority}}</ref><blockquote>To further strengthen device security, we’ve temporarily paused the ability to downgrade from 16.0.2.50x software builds to older builds. We will be restoring the ability to downgrade software builds in our next routine software update, but in the meantime customers looking to downgrade their build can contact OnePlus after sales channels directly.</blockquote> | On January 27th 2026, in response to Android Authority OnePlus issued the following statement.<ref>{{Cite web |last=Simons |first=Hadlee |date=2026-01-27 |title=Here's why OnePlus bricked your phone when you tried downgrading it |url=https://www.androidauthority.com/oneplus-brick-phones-statement-3635475/ |url-status=live |access-date=2026-01-27 |website=Android Authority |archive-url=http://web.archive.org/web/20260128131638/https://www.androidauthority.com/oneplus-brick-phones-statement-3635475/ |archive-date=28 Jan 2026}}</ref><blockquote>To further strengthen device security, we’ve temporarily paused the ability to downgrade from 16.0.2.50x software builds to older builds. We will be restoring the ability to downgrade software builds in our next routine software update, but in the meantime customers looking to downgrade their build can contact OnePlus after sales channels directly.</blockquote> | ||
==Comparison with other manufacturers== | ==Comparison with other manufacturers== | ||
Anti-rollback | Anti-rollback mechanism exists across the smartphone industry, but implementations vary in their impact on users. | ||
[[Samsung Knox]] implements fuse-based security that trips permanently when non-OEM firmware is flashed, disabling Samsung Pay and Secure Folder. Android Authority noted that the new OnePlus implementation is functionally identical to Samsung's model, where eFuses serve as irreversible warrants of system integrity, punishing modification with permanent hardware states.<ref name="android-authority" /> | [[Samsung Knox]] implements fuse-based security that trips permanently when non-OEM firmware is flashed, disabling Samsung Pay and Secure Folder. Android Authority noted that the new OnePlus implementation is functionally identical to Samsung's model, where eFuses serve as irreversible warrants of system integrity, punishing modification with permanent hardware states.<ref name="android-authority" /> | ||