Samsung One UI 8 bootloader restriction

Samsung globally disabled the ability for consumers to unlock the bootloaders on their Galaxy devices, eliminating the possibility of installing custom operating systems discovered by a contributor to custom ROMs, known as "salvo_giangri"^[1]. At the time One UI 8 was still in beta and there was hope that it would no longer be the case in the stable release, however with the stable version release in July 25th 2025 on Galaxy Z Fold 7 / Z Flip 7 family, the restriction was still present.^[2]

Since its release in 2018, One UI has always featured a locked bootloader to U.S customers.^[3][1][4] For consumers outside the U.S. however, it has been a different story and many international Samsung phones, supported the unlocking of the bootloader. U.S. phones lacked the OEM unlock toggle seen in the Developer Options menu.^[4] Samsung removed this toggle for all devices, regardless of region in the One UI 8.0 update. As of June 2026, the newest version of One UI available is 8.5.^[5] This version did not (yet) re-add the OEM Unlocking toggle. The only way to currently get around this restriction is by using an external tool to downgrade the phone to One UI 7 or any older version, for which you need another phone or a PC with MacOS, Linux, or Windows 7 or higher, enable OEM Unlocking, and (re-)update the phone.^[6][7][8]

Samsung has not made a statement regarding this situation and has remained silent despite getting questioned on a post in Samsung Community whether the bootloader will remain unlocked when updating from One UI 7 to 8.^[9] This post also elaborates that in this user's case he, or she will lose Knox functionality which is a huge issue since Knox plays a huge role for the security and stability of the phone. This is called the Knox fuse, which is a physical component which "detonates" if the bootloader is unlocked, and locks the device out of using services like Secure Folder, or Samsung Wallet.^[10][11]

The feedback from the community and anyone that was aware of this was mostly, if not completely negative. Much of that negative feedback mainly based off losing freedom and damaging the brand of Android's "open source" nature. Removing this feature has nothing to do with safety, as it is hidden behind the Developer Options, and a fair amount of warning messages before finally unlocking the bootloader. Many users ^[12][3]