Imagine buying the latest Samsung flagship only to find out you can no longer tinker under the hood. That’s the scenario unfolding with Samsung’s One UI 8 update, which appears to remove the once‑critical “OEM Unlocking” toggle from Developer Options—and with it, any easy path to unlocking the bootloader on Galaxy devices outside the U.S.

For years, Samsung quietly segmented its devices by region. In the U.S., carriers like Verizon and AT&T long ago disabled bootloader unlocking, preventing users from installing custom ROMs or kernels. Meanwhile, international models retained an entry in Settings → Developer Options called “OEM Unlocking,” guarding the door to deeper software freedoms.

With One UI 8—an Android 16‑based skin preinstalled on the Galaxy Z Flip7 and Z Fold7, and now rolling out in beta to the S25 series—Samsung has flipped the script globally. The code responsible for toggling bootloader access now reads: androidboot.other.locked=1

A “1” here means “locked,” effectively erasing the OEM Unlock switch everywhere, not just in North America.

The first breadcrumbs appeared over the weekend on the XDA Developers forums, where keen‑eyed contributors like salvo_giangri dissected One UI’s Settings APK. Their discovery was corroborated by Android Authority and SammyGuru, spotting the same “androidboot.other.locked=1” flag in firmware builds for non‑U.S. devices.

One UI 8 beta testers on S25 devices immediately confirmed the missing toggle—and international owners of the brand‑new Z series echoed the sentiment: no OEM Unlock, no bootloader freedom. Android Central’s Jay Bonggolto notes that this isn’t a simple beta stumble; rather, it looks baked into both stable and beta channels.

While Samsung has yet to issue an official statement, several plausible motives emerge:

1. Security and warranty concerns. Locked bootloaders mean fewer bricked devices and less carrier/Warranty support headaches. Banking apps and DRM‑protected services often refuse to run on unlocked or rooted phones, citing data‑theft or piracy risks.
2. Unified development approach. Samsung’s recent shift to Google’s trunk‑based development model—designed to ship updates faster—could discourage maintaining divergent code paths that accommodate bootloader unlocking in some regions but not others.
3. Revenue protection. By limiting ROM mods, Samsung (and Google) can better control app‑store ecosystems. They ensure Google Play Integrity checks aren’t bypassed by sideloaded or custom‑rooted software, keeping revenue streams healthy.

What’s next for One UI 8 and beyond?

Key questions remain unanswered:

• Will older devices on One UI 8 retrospectively lose unlock capability? If Samsung pushes this change to existing flagships, millions of current Galaxy owners could see their modding options vanish overnight.
• Is there an official appeal or workaround? On past occasions, manufacturers have quietly re‑enabled toggles after public backlash. Samsung may yet clarify whether this is permanent or an early beta quirk.
• How will carrier‑branded phones react? U.S. carriers already lock bootloaders; now the global market joins that club. It could standardize software support—but at the expense of user choice.

For the custom‑ROM crowd, the writing may be on the wall: One UI’s next chapter looks less like a sandbox and more like a walled garden. Whether Samsung reconsiders under community pressure—or entrenches this lockdown—only time will tell. Until then, those craving deep Android customisation might need to look elsewhere, or dig up an old device that still answers the call of the unlocked bootloader.