Samsung may be discontinuing bootloader unlocking across its phone lineup with the One UI 8 update. An XDA Developers (via Android Authority) contributor reported the change, indicating that Samsung devices, including international models, may no longer feature the necessary OEM Unlock toggle. Previously, this restriction primarily affected US models.

Samsung phones in the US already lacked the ‘OEM Unlocking’ toggle in Developer Options, preventing custom ROM installations. The restriction now appears to be expanding globally.

Contributor salvo_giangri identified a new bootloader configuration line: androidboot.other.locked=1. This line dictates whether a device permits bootloader unlocking. A value of ‘1’ ensures the Settings app does not display the OEM Unlock option, a prerequisite for unlocking.


Samsung’s One UI 8 gets fresh lock screen tricks


The One UI 8 firmware for non-US devices now includes this line, suggesting the restriction extends beyond specific regions.

Bootloader unlocking is crucial for enthusiasts and developers seeking to install custom ROMs or kernels, achieve root access, or customize devices. Current Samsung devices not yet running One UI 8 may still offer unlockable bootloaders. However, the report suggests this may change with future updates and new devices. An official statement from Samsung on the matter is pending.


Featured image credit


Ledger Cryptotwitter


Source link

Read More


Samsung’s One UI 8 update seems to prevent users from unlocking their device’s bootloader to load custom ROMs, as spotted earlier by SammyGuru. Over the weekend, users on the XDA Developers forum noticed that Samsung appears to have disabled the option on devices in regions outside the US, where the option had already been locked for years.

By unlocking the bootloader, users can install custom software and make other modifications to their phone. Users discovered the new restriction after digging into the code of the Settings app on One UI 8, which ships with the newly released Galaxy Z Flip 7 and Z Fold 7.

As pointed out by SammyGuru and Android Authority, the code contains the line “androidboot.other.locked=1.” When this line is set to “1,” it means the bootloader is locked, like it is here in the US. Before One UI 8, this line had previously been set to “0” to enable bootloader unlocking in regions outside the US. Users spotted the restriction within One UI 8 beta builds for the Galaxy S25 as well.

Samsung didn’t immediately respond to a request for comment.


Ledger Cryptotwitter


Source link

Read More


Samsung is reportedly disabling bootloader unlocking on its Galaxy smartphones, preventing users from installing custom ROMs and modifying the Android system. According to a report by Android Authority, the change is expected to roll out with the Android 16-based One UI 8 update.

 

Until now, bootloader unlocking was restricted only on Galaxy models sold in the US. However, with One UI 8, Samsung appears to be expanding the limitation to more global variants. While the company has not officially announced the move, the restriction has been spotted on the newly launched Galaxy Z Fold 7 and Galaxy Z Flip 7, both of which ship with One UI 8. The Verge also reports that beta builds of One UI 8 running on the Galaxy S25 block bootloader unlocking, something that was possible on One UI 7. 
ALSO READ: Samsung’s Android 16-based One UI 8 debuts with Galaxy Z series: What’s new

 


What is bootloader unlocking?


Unlocking the bootloader refers to disabling the security lock on a smartphone’s bootloader, allowing users to install third-party firmware or custom versions of Android. This process is commonly used by developers or some users to flash custom ROMs or gain full control over a device’s software.

 


Custom ROMs — where “ROM” stands for Read-Only Memory — are alternative versions of Android that replace the default OS. These ROMs often provide additional features, performance improvements, and more extensive customisation options. They also allow users to remove pre-installed system apps.


What does this change mean for users?


For users who rely on bootloader access to install custom ROMs, root their devices, or experiment with kernels and mods, Samsung’s move represents a significant restriction. If the bootloader can no longer be unlocked, it effectively limits the user’s ability to alter the system software or customise the Android experience beyond what Samsung offers.

 

As of now, bootloader unlocking remains possible on existing Samsung models not yet updated to One UI 8. However, that may no longer be the case once these devices receive the update or with the launch of future Galaxy smartphones.


Why Samsung may be locking the bootloader


While unlocking a bootloader offers users more control, it also introduces a number of security concerns. Devices with unlocked bootloaders are more vulnerable to malicious software and unauthorised modifications, which can compromise user data and system integrity.

 


In addition to these security risks, an unlocked bootloader typically voids a device’s warranty. Some sensitive apps — particularly financial and banking apps — may also refuse to run on such devices due to safety concerns. Given these factors, Samsung may be opting to tighten bootloader controls to maintain device security, protect user data, and ensure compatibility with sensitive applications.


Ledger Cryptotwitter


Source link

Read More


Someone holding the OnePlus 13 outside.

Joe Maring / Android Authority

TL;DR

  • OnePlus is placing new restrictions on bootloader unlocking.
  • It requires filling out an application form and limits the number of requests to one every 30 days.
  • Thankfully, these limitations only apply to Chinese users (so far) and only on devices running at least ColorOS 16 based on Android 16.

Android has evolved significantly in the last decade, and one noticeable shift has been in the decline of custom development in Android. Custom ROMs or mods are far less popular among users, and while one reason is the perception of finesse in Android skins, OEMs have been pulling support. Recently, Samsung placed roadblocks to bootloader unlocking, which is key to installing any custom mods or rooting an Android device, and another major phone brand — OnePlus — is placing additional hurdles.

OnePlus has announced a new system that limits who can unlock the bootloader on their phones. Stating reasons such as “data security” and an enhanced “system stability” (based on machine translation from Chinese), OnePlus has introduced a new procedure where anyone wanting to unlock the bootloader on their devices must first fill out an online request form for “Deep Testing.”

Besides filling out the application form, users must ensure that their devices are not associated with any operator plans or have special enterprise or government-specific builds running on them. OnePlus also notes that you can apply for bootloader unlocking only once in 30 days, which is still better than Xiaomi, which recently limited the number of requests to one per year.

Don’t want to miss the best from Android Authority?

However, the announcement offers some sense of relief, too. Firstly, these requirements are only applicable to users in China, as they will only be enforced when their devices are updated to ColorOS 16, which is based on Android 16. It does not guarantee OnePlus will not enforce the same measures worldwide, although the support page clarifies that these restrictions will not apply to previous versions of ColorOS. That will be beneficial for anyone wanting to breathe life into an older or unsupported OnePlus phone, though users with new phones are not likely to appreciate it.

OnePlus is also assuring users that simply unlocking the bootloader won’t void the phone’s warranty, so long as they can return the device to the original firmware. This has been the company’s stance for as long as anyone can remember.

Interestingly, this isn’t the first instance when OnePlus has placed restrictions on bootloader unlocking. More than six years ago, OnePlus mandated certain OnePlus 6T users in the US to fill out requests to unlock the bootloader, preventing them from doing it immediately. However, it was enforced only on devices bought in contract with T-Mobile, which made the application process mandatory.

Nonetheless, OnePlus’ restrictions, despite being limited to China, signal a shift in brands’ openness towards customization and third-party development for Android devices, and it is especially disconcerting coming from a brand that owes its initial success to the custom ROM community.

Thank you for being part of our community. Read our Comment Policy before posting.


Ledger Cryptotwitter


Source link

Read More


Google’s Android Beta Program provides a great way for Pixel users to test upcoming Android releases before their public release. All compatible Pixel phones can join the program, and right now, can test Android 16’s December 2025 public release. Until now, the Pixel 10 lineup was not a part of the program, likely because it launched less than a month ago. But that’s finally changing, with Google allowing Pixel 10 owners to enroll in the program.

First spotted by Android Police tipster Anthony Maki, and as several Pixel 10 owners on Reddit report, Google is now allowing the Pixel 10 lineup to enroll in the Android Beta Program. But since Android 16 QPR2 Beta 2 isn’t out yet, Pixel 10 users will have to wait a little longer before they can install a beta build on their device.

The wait should not be long, though, as multiple signs point to Google releasing the second Android 16 QPR2 beta later today (September 17).

The first Android 16 QPR2 beta introduced several notable changes, including forced app icon theming, expanded dark mode, lock screen widget support on phones, and a new 90:10 split-screen multitasking option. The second beta should improve the existing features, add new ones, and, hopefully, squash many of the Pixel 10’s lingering bugs.

More importantly, the real highlight of Android 16 QPR2 Beta 2 could be updated GPU drivers for the Pixel 10’s PowerVR GPU, potentially resolving the device’s disappointing graphics performance. This should also help boost the phone’s battery life.

You can enroll your Pixel 10 in the Android Beta Program from here. Note that enrolling won’t require a reset, but leaving the beta for the stable build later will completely wipe your device.

Pixel 10 receives a second September update

Besides opening the Android Beta Program, Google also pushed a second September OTA for its newest Pixels. The 31MB update, carrying the build number BD3A.250721.001.E1, seemingly fixes the fuzzy display issue that has plagued many Pixel 10 users since launch.

The factory images for this new build are yet to go live on Google’s website, but if you own the Pixel 10, you should immediately see the OTA for download from Settings > Software update.


Ledger Cryptotwitter


Source link

Read More


What you need to know

  • One UI 8 might silently kill off bootloader unlocks on Galaxy phones, even outside the U.S.
  • The “OEM Unlocking” toggle in developer settings is apparently nowhere to be found on Z Fold 7 and Flip 7 running One UI 8.
  • A new boot configuration line (androidboot.other.locked=1) is hiding the unlock option entirely.

Samsung’s One UI 8 might quietly shut down bootloader unlocks on your beloved Galaxy phones once it hits the stable channel, a move that signals tighter control over what users can tweak under the hood.

One UI 8, built on Android 16 and launched alongside the Samsung Galaxy Z Fold 7 and Z Flip 7, seems to be missing the “OEM Unlocking” toggle in developer settings. This option was key for installing custom ROMs, and its removal, as per an XDA Forum post, points to Samsung tightening its stance on device modding (via SammyGuru).


Ledger Cryptotwitter


Source link

Read More


For Android enthusiasts, rooting and custom ROMs were once the ultimate draw. They made Android exciting and turned every phone into a project worth tinkering with. But the modding scene’s golden age has long passed, and that’s probably a good thing.

A Brief History of ROMs and Rooting

Custom ROMs and rooting have been a part of the Android experience for many since pretty much day one. The T-Mobile G1 was rooted within a few weeks of its launch, and from then on, experimenting with phones became something that all enthusiasts needed to do. It was also a key differentiating point that helped sell the platform.

While iPhone users had the option of jailbreaking their devices to install a handful of apps that Apple didn’t approve of, Android users could completely wipe their software and customize their devices from scratch.

The XDA-Developers forums.

Whatever you wanted your phone to be, you could find it in ROMs like CyanogenMod, Paranoid Android, and MoDaCo. Minimalist or feature-packed, speed or battery life, or a whole new user experience: a quick trip to the XDA forums would reveal the perfect ROM for you.

My own ROM journey began with my first Android phone, the HTC Desire. After HTC had spent months failing to provide any information on an update to Android 2.3, I decided to find out what options the community had already created. And so, I flashed my first Gingerbread ROM. I remember it being a bit of a hotchpotch. The camera was as likely to reboot the phone as it was to take a photo, but that was almost part of the fun.

After that, I moved to the Galaxy S3 and replaced Samsung’s gaudy TouchWiz software with various stock ROMs. Then I switched to Nexus phones and had less need for ROMs, so I explored the benefits of rooting instead. I loved the Xposed Framework with the near-endless customizations of the GravityBox app and the battery-saving Greenify. Its replacement, the almost-as-good Magisk, was equally addictive.

Screen saying Android Pay is blocked.

Eventually, that fell by the wayside, too. My banking apps stopped working if there was any sign of root software on my phone, so I had to make a choice. My last two phones have remained unrooted, and I won’t be going back.

The Golden Age of Rooting Is Gone

Custom ROMs and rooting were, to an extent, of their time. Android was a new platform, embraced by enthusiastic users. And though there is still a small community around it, the peak has long since passed, and probably for good reason.

It isn’t just about the downsides that we happily overlooked. The security, compatibility, and performance implications, the bricked devices, and how it could be a time sink with minimal benefit. Or that much of the community has moved on. ROMs briefly threatened to go mainstream when OnePlus partnered with CyanogenMod, but ended up simply showing how vulnerable community projects can actually be.

Or even that it’s much harder to do now that most devices are locked down tighter than they’ve ever been.

Person holding the Samsung Galaxy S25 Ultra looking at the display.
Galaxy S25 Ultra
Justin Duino / How-To Geek

The truth is, modding is no longer needed. The most practical benefit of installing a custom ROM was to save your phone from obsolescence. But you can now expect three or four years of updates for a mid-range phone and seven for a flagship, so that’s unlikely to be a problem. Many phones have update policies that will outlast the device itself.

Android, and manufacturers’ customized versions of it, have improved beyond measure as well. The days of ugly graphics and cheesy skeuomorphic designs from Samsung and the like are long gone, replaced by clean, modern interfaces. Bloatware—unwanted pre-installed apps—can still be an issue on some devices. Yet some people like it, and you don’t need to root to remove it anyway.

One thing that kept me rooting my phones for a long time was the ability to add new features. Not big gimmicky things, but small, useful functions that should have been part of the software in the first place. Things like being able to resize widgets, getting more useful volume controls, or mapping buttons to specific tasks. Most of these have now been ticked off, too, as Android has become increasingly polished.

Trading Control for Convenience

The modding scene was an important part of Android’s history, and the platform’s openness was the reason many of us chose it over the iPhone. Its decline does undoubtedly mean that we’ve lost a lot of control over how we can use our devices. And with further limits on things like sideloading on the horizon, the Android world looks quite different from how it was in its first decade.

But I can’t feel too bad about it. ROMs and rooting had their day, and Android, and no doubt many of its users, have outgrown it. Smartphones have become highly commoditized. Where the early Android phones were rough and ready and invited tinkering, they’re now just tools that work exactly as expected. And that’s got to be a good thing.


Ledger Cryptotwitter


Source link

Read More


Android figures standing around Pixel phone with AOSP home page showing

Mishaal Rahman / Android Authority

TL;DR

  • Google has delayed releasing the source code for Android 16 QPR1, worrying custom ROM developers who rely on timely AOSP (Android Open Source Project) updates.
  • While Google typically publishes source code within 48 hours of a new release, it has been a week, breaking a long-standing precedent for the community.
  • Google confirmed the code is coming “in the coming weeks,” but the situation has reignited concerns about the company’s commitment to open-sourcing Android.

Last week, Google rolled out the Android 16 QPR1 update, bringing the company’s long-awaited Material 3 Expressive design overhaul and other exciting features to Pixel users. If you want to try new Android features but don’t own a Pixel device, your best option is usually to install a custom ROM based on the open-source version of the operating system. Google typically publishes the source code for new Android versions within 1-2 days of release, allowing independent developers to quickly start porting the new changes to their custom ROMs. That hasn’t happened this time, though, leaving many developers to wonder if Google’s history of timely open source releases is over.

AOSP, short for the Android Open Source Project, is an operating system Google releases under the permissive Apache 2.0 License, which allows anyone to use, modify, and distribute their own AOSP-based operating systems without paying fees or releasing their modified source code. This licensing structure is what allowed Android to become so popular, but it’s also why the OS looks so different across devices. The software experience only feels familiar across most smartphones, tablets, watches, and TVs running Android because companies must follow certain guidelines to get access to Google Mobile Services (GMS) — Google’s suite of proprietary apps that includes the Play Store.

Even if your company doesn’t license GMS, you can still build your own operating system from AOSP. The source code is freely available under the Apache 2.0 license, and Google regularly publishes new code to AOSP shortly after releasing a new Android version. Within hours of rolling out a new quarterly or major release to its Pixel devices, Google typically begins uploading the corresponding source code to AOSP. This process usually takes 24-48 hours due to the codebase’s size and complexity.

It’s been a week since Google released Android 16 QPR1, and there are no signs that the company has even begun to upload its source code. Normally, a minor delay wouldn’t be a cause for concern; perhaps the team responsible for AOSP releases is understaffed, or maybe there’s another complication. However, given recent changes to AOSP, developers are understandably concerned this delay is intentional. They’re worried about the impact these delays could have on their projects, as users have grown accustomed to fast turnarounds following a new Android release.

We reached out to Google a few days ago for comment on whether and when it plans to release the source code for Android 16 QPR1. In a statement to Android Authority, Google confirmed it will release the source code “in the coming weeks.” The company didn’t explain the reason for the delay or offer a more specific timeline, but its statement reassures developers that the code is coming — just later than usual.

Why are developers concerned about AOSP?

LineageOS Logo (2 of 3)

C. Scott Brown / Android Authority

Although AOSP is open source, nearly all of its development happens privately, with Google contributing the bulk of the code. Google used to develop some parts of Android in public, but it fully privatized development earlier this year to simplify its workflow. Aware that this would spark concern, Google told Android Authority that it remained committed to publishing Android’s source code.

This commitment was tested when Google released Android 16 back in June. While the company did publish the operating system’s source code, it dealt a huge blow to the Pixel custom ROM community by omitting code for Pixel-specific hardware features. This omission, while not affecting the core OS, fueled speculation that Google was planning to discontinue AOSP. In response to the outcry, Google’s VP and GM of Android Platform, Seang Chau, posted on X, stating that “AOSP is NOT going away.”

Google denies discontinuing AOSP

Mishaal Rahman / Android Authority

Though some skepticism remained, that statement from Google’s VP quelled most doubts at the time. However, the delayed release of security patch backports, coupled with the lack of source code for Android 16 QPR1, has reignited concerns about the company’s commitment to AOSP. If these delays become the new norm, the custom ROM community will have to adjust its release schedules accordingly. We asked Google whether to expect delays for future releases or if this is a one-time issue, and we’ll update this article when we hear back.

Don’t want to miss the best from Android Authority?

Thank you for being part of our community. Read our Comment Policy before posting.


Ledger Cryptotwitter


Source link

Read More


Tinkerers left in the cold as One UI 8 slams the door shut

Mobile phone giant Samsung has decided to kill off the bootloader on its operating system and prevent those who love to tinker with their phone from getting their fix.

While most Samsung Galaxy owners never fiddle with their phones’ innards, but there’s a hardcore group of Android obsessives who live for rooting, custom ROMs and alternative kernels. For years, Samsung let that crowd have their fun, at least outside the United States.

Now, that freedom appears to be over. One UI 8 has quietly killed off bootloader unlocking for good.

The change won’t come as a shock to anyone in the US, where Samsung shut down bootloader access yonks ago. Elsewhere, though, the option had clung on. That ends with the arrival of One UI 8, according to reports based on Galaxy S25 beta firmware.

The same lock has been confirmed on stable builds for the Galaxy Z Fold 7 and Z Flip 7. A closer look at the software code shows that the restriction is global. Once a phone is running One UI 8, the bootloader unlock switch is gone no matter where it’s sold.

The Android hobbyist crowd isn’t thrilled. Without unlock access, there’s no route to installing custom ROMs after Samsung drops official support or cranking out extra performance with bespoke kernels.

Samsung might argue this is less of a problem than it used to be. Its newer phones now promise seven years of Android updates, which is more than enough for most users. But for those who liked pushing their phones past its limits, One UI 8 is the end of the road.




Ledger Cryptotwitter


Source link

Read More