Samsung has decided to proceed with the Bootloader blocking also in Europe, a move that has caused a lot of discussion. Behind this choice is a European regulation that will come into force in August 2025 and which risks changing smartphone usage in Europe forever. This is why other manufacturers may soon follow suit.
From 1 August 2025, new provisions will come into force RED Directive (Radio Equipment Directive), which redefines the compliance requirements for all radio devices sold in Europe. This is a significant change, not so much for the amount of regulations introduced, but for the effect they will have on the entire Android ecosystem. The issue revolves around three articles that impose specific protections: against network interference, personal data compromise, and digital fraud. These are, in themselves, sacrosanct rules.
But the crux comes with the interpretation prevailingEach device must ensure full compliance not only with the hardware, but also with the software that controls the radio modules. This is where the bootloader comes in. Unlocking it essentially allows you to replace the original operating system with an alternative one, such as LineageOS or GrapheneOS.
But these systems, if they modify the radio drivers even minimally, invalidate the CE certification. An uncertified device can no longer be legally marketed or used, at least according to the most stringent reading of the law.
This scenario has therefore led Samsung to protect its devices. Not on a whim, but to avoid any software modifications falling under your legal liability. If a user installs a ROM that interferes with radio frequencies or compromises communications security, the manufacturer (and in some cases the importer) may be held directly liable.
RED does not explicitly talk about unlocking the Bootloader or custom ROM, but it opens one regulatory space in which the margins for maneuver are they narrow. And in doing so, it provides a solid argument for those who have been trying for years to close the loop between hardware, software, and services. After all, customizing the operating system also means breaking away from proprietary services and, therefore, from the model that ties the user to the brand.
Samsung is just the first to move, but it's hard to imagine it will be the only one. Starting in August 2025, it's very likely that other manufacturers will follow suit, at least for the European market.
Secure boot force enabled with preset certificates would essentially do that.
Except that would require a rewrite of the PC spec which I'm not sure would work out too well given the existence of loose mainboards for custom builds which ship with no OS by default and expect you to supply the OS yourself, ditto for niche manufacturers like Framework who also offer the option of letting you supply your own OS.
Some systems can bypass secure boot
Only if the motherboard vendor allows you to. Imagine buying a Dell or Asus laptop and being forced to only run Windows.
So on most motherboards secure boot is just fake secure boot to satisfy windows?
No. Thankfully (at the moment) vendors are allowing us to install other OSes, but if a vendor really wanted to lock you down to Windows all they'd need to do is hide one option in the bios. I'm uncomfortable with the idea that there's no technical reason preventing the PC industry from getting as locked down as Android phones did over time.