How to Unlock the Bootloader on Android: What Still Works in 2026
Check whether your exact phone can be unlocked in 2026, then follow the verified steps for Pixel, Nothing, OnePlus, Motorola, Sony and Xiaomi. Samsung One UI 8, greyed-out OEM unlocking and unlock APKs get straight answers.
Table of Contents
- Can your phone be unlocked in 2026? Check this first
- What unlocking the bootloader actually does
- What "OEM unlocking" is
- Why the phone wipes itself
- What it does not do
- Before you start
- What you need
- Think about factory reset protection
- The second wipe nobody mentions
- The universal procedure (Pixel, Nothing, OnePlus and most others)
- Brand by brand (2026)
- Google Pixel
- Nothing
- OnePlus
- Motorola
- Xiaomi, Redmi and POCO (HyperOS)
- Sony Xperia
- Samsung: One UI 8 changed everything
- Honor, Huawei, Asus, Vivo, LG and Realme/OPPO
- OEM unlocking greyed out or missing: causes and fixes
- "Bootloader unlock APK" and unlock tools: what is real
- After you unlock: what changes and what stays broken
- Relocking the bootloader safely
- Check whether your bootloader is already unlocked
- Troubleshooting matrix
- Should you unlock at all?
- Need a second pair of hands?
- Frequently asked questions
- Does unlocking the bootloader erase my data?
- Is the Samsung bootloader unlockable?
- How do I enable OEM unlocking on Samsung?
- Why is OEM unlocking greyed out or missing?
- What is the command to unlock the bootloader?
- Is there a bootloader unlock APK?
- Is there a code to unlock a Samsung phone?
- How long is the Xiaomi unlock wait?
- Can I relock the bootloader?
- What is an unlocked bootloader?
- The bottom line
- Sources and project documentation
You want to flash a custom ROM, patch a boot image for root, or just run your own kernel. All of them start at the same gate: the bootloader has to accept images the manufacturer did not sign. Whether your phone will let you through depends far more on the brand, the region and the carrier than on anything you do at the command line.
The short version. On most phones that allow it, you enable OEM unlocking in Developer options, boot into the bootloader, run fastboot flashing unlock and confirm on the screen. The phone then erases all user data.1 Three things changed or stayed true that older guides get wrong: Samsung removed bootloader unlocking from One UI 8.0 onward; Xiaomi adds a server-side permission and countdown; and there is no legitimate "unlock APK".151623
Sources checked November 5, 2026. This is a documentation-based guide: DroidRooter did not unlock any device for this update, and vendor rules change without notice. The status table is built from public sources and is not a compatibility promise.
Jump to: Can your phone unlock? · What unlocking does · Before you start · Universal steps · Brand by brand · OEM unlocking greyed out · Unlock APKs · After you unlock · Relocking · Troubleshooting · FAQ
Wipe warning. Unlocking a bootloader erases the phone: photos, apps, accounts, messages, settings. AOSP's own requirement is that the device warns you and then factory-resets so nobody can read your data off a phone they just unlocked.1 Back up to a PC and to a cloud or second drive first, and confirm you can restore something from each. Do this only on a phone you own or are authorized to administer.
Can your phone be unlocked in 2026? Check this first
Do this before you download anything. Unlock policy is set by the manufacturer, sometimes narrowed by the carrier, and it has moved in the past twelve months. Find your brand, note the caveat, then continue.
| Brand | Official route | Status (checked 2026-11-05) | Common blockers | Source |
|---|---|---|---|---|
| Google Pixel | OEM unlocking + fastboot flashing unlock |
Open on most phones | Phones locked to a carrier that restricts unlocking (Verizon is the usual example) may never receive the unlock token | 189 |
| Nothing | OEM unlocking + fastboot flashing unlock, no code |
Open (Phone (1) documented; other models not checked) | None reported for Phone (1) | 2010 |
| OnePlus | OEM unlocking + fastboot flashing unlock |
Open on global phones | T-Mobile US and MVNO variants need an unlock token with proof of purchase; mainland China models go through a "Deep Testing" application | 19268 |
| Motorola | OEM unlocking + a code from Motorola's portal | Model-dependent | Unisoc phones never; some newer models need up to 7 days online; older phones can become ineligible | 1117 |
| Sony Xperia | Service-menu check + IMEI-based code from Sony | Model-dependent | Service menu must say "Bootloader unlock allowed: Yes" | 12 |
| Xiaomi / Redmi / POCO | Community-app permission, then Mi Unlock after a countdown | Hard | China-region phones effectively closed; one device per year; Unisoc never | 1624 |
| Samsung | Developer options toggle + Download mode (One UI 7 and earlier only) | Removed from One UI 8.0, all regions | US and Canada Snapdragon models were already excluded | 152313 |
| Honor, Huawei, Asus, Vivo, LG | Effectively none | Closed or unreliable | See the short status section below | 2321 |
Two practical tests tell you more than any table. First, is there an "OEM unlocking" switch in Developer options? If it is missing, the vendor, carrier or firmware almost certainly does not permit unlocking; the greyed-out section explains the cases. Second, on a Samsung phone still on One UI 7 or earlier, what does Download mode say about OEM Lock? If it shows no value at all, Magisk's documentation says the phone is probably market-limited (USA or Canada).13
Not sure which row you are in? Send the exact model number and region through the contact page and we will tell you what the public evidence says for that variant.
What unlocking the bootloader actually does
The bootloader is the first code that runs after the hardware powers on. Its job is to check that the operating system it is about to start was signed by the manufacturer. Most Android phones ship with it locked, which means you cannot flash the bootloader or device partitions.1 Unlocking removes that restriction so the phone will accept images you supply: a custom ROM, a patched boot image, a different kernel.
Android describes this as the Verified Boot device state, which is either LOCKED or UNLOCKED. In the unlocked state the phone no longer refuses an image just because the vendor did not sign it, and you see a boot warning to that effect.2
What "OEM unlocking" is
OEM unlocking is the Developer options switch that gives the bootloader permission to unlock. In AOSP terms it sets get_unlock_ability to 1. A compliant bootloader refuses fastboot flashing unlock while that value is 0, and once you set it, it persists across reboots and factory resets.1 That is why the order matters: toggle first, command second. It is also why a missing or greyed-out switch is the biggest single obstacle people hit.
Why the phone wipes itself
When you send the unlock command, the device should show a warning and, once you acknowledge it, perform a factory data reset. AOSP states the reason plainly: to prevent unauthorized data access. RAM that has not already been overwritten should also be cleared during the process.1 The wipe is the security design, not a bug or a vendor quirk, and no setting lets you keep your data.
What it does not do
Unlocking does not root the phone, install a ROM, remove a carrier lock or SIM lock, or remove a Google, Mi or Samsung account lock. Our own bootloader unlock service page makes the same distinction: a bootloader lock, a carrier lock and an account lock are different problems, and one does not solve the others.
Before you start
What you need
- A computer with platform-tools. Download the current stable Android SDK Platform-Tools for your operating system from Google.4 Linux distribution packages can be old; Windows may need your vendor's USB driver, which Google links by manufacturer.146
- A data-capable USB cable. Charging-only cables are a classic cause of an empty
fastboot deviceslist. - A verified backup. Back up to two places. Phone-maker backup tools may not restore onto a different ROM later, which LineageOS warns about for Samsung and Motorola backups.8
- Enough battery to finish the process. Nobody publishes an exact threshold; treat 50 percent or more as sensible practical advice rather than a documented requirement.
- Time. The commands take minutes. Vendor gates (Xiaomi's countdown, Motorola's online wait) can take days.
Think about factory reset protection
Enabling OEM unlocking disables Google's factory reset protection (FRP) on the device.14 That has a real security cost: a phone that is unlocked and then lost or stolen is easier for someone else to wipe and reuse. LineageOS also tells users to remove Google accounts before some installs so FRP does not interfere afterwards.11 Treat this as a caution, not a hack: this guide does not cover getting past an account lock or FRP on a phone you do not control, and the unlock procedure does not do that.
The second wipe nobody mentions
If your goal is root, note that on Samsung, Magisk's documentation says the first Magisk install requires a full data wipe in addition to the wipe from the unlock.13 Plan for two wipes, and do not restore a large backup until the final setup is stable.
The universal procedure (Pixel, Nothing, OnePlus and most others)
This is the sequence documented by AOSP and used on the LineageOS install pages for the OnePlus 13, Pixel 7 and Nothing Phone (1).18910
- Enable Developer options. Go to Settings, About phone, and tap Build number seven times until Android says you are now a developer. Android's documentation lists the path per brand: Pixel is Settings > About phone > Build number; Samsung Galaxy S8 and later is Settings > About phone > Software information > Build number; OnePlus 5T and later is Settings > About phone > Build number.5
- Enable OEM unlocking. On a Pixel the toggle sits under Settings > System > Developer options.1 Other vendors place Developer options elsewhere (Xiaomi's path is Settings > Additional settings > Developer options).16 LineageOS words the instruction as "if present" because the switch genuinely does not exist on some phones.8
- Enable USB debugging on the same screen, connect the phone and run
adb devices. Accept the authorization prompt on the phone and confirm the list saysdevice, notunauthorized. - Reboot to the bootloader. Run
adb reboot bootloader. Or power off and use the key combination: LineageOS documents Volume Down + Power for the Pixel 7 and Volume Up + Volume Down + Power for the OnePlus 13.98 Combinations differ by model. - Confirm the connection. Run
fastboot devices. If the list is empty, go to the troubleshooting matrix. - Send the unlock command:
fastboot flashing unlock
- Confirm on the phone. LineageOS notes the screen may ask you to interact; the exact keys vary by model, so follow the prompt on your screen.8 The phone wipes and reboots.
Older phones: the legacy command is fastboot oem unlock. AOSP names fastboot flashing unlock as the current command. If the new one returns an "unrecognized command" error, first check that you are in the bootloader and not in fastbootd (the userspace mode used for other tasks), then try the legacy form, and only then look for a model-specific guide.114
A note on fastboot flashing unlock_critical: that is a separate command for critical partitions. AOSP says devices should not ship in that state, and that moving from lock_critical to unlock_critical should require physical interaction on the device. It is not part of an ordinary unlock, so ignore it unless a model-specific guide tells you otherwise.1
Brand by brand (2026)
Each block gives the status in one line, the steps that differ from the universal procedure, and the traps. Menu names vary by software version; where a path is not documented by a primary source, the text says "look for" rather than inventing one.
Google Pixel
Status: open on most phones, with a carrier check.
Follow the universal procedure. The main difference is the unlock token. A community-maintained record describes a Google system app that, when the phone first reaches the internet, checks for a carrier lock and, if the carrier does not restrict unlocking, fetches a token from Google that permits unlocking. If the token is never received, the bootloader cannot be unlocked.18 That is a single community source, so treat the mechanism as reported, but the practical lesson holds: connect a new Pixel to the internet once and make sure OEM unlocking is not greyed out before you spend time on anything else. A Pixel tied to a restrictive carrier such as Verizon is the case most likely to stay blocked.
Three Pixel-specific facts:
- Google advises that it is typically easier and safer to sideload the full OTA image than to use a factory image, and that you should relock the bootloader after using a factory image. Installing a factory image erases all data.3
- The May 2026 update for the Pixel 10, 10 Pro, 10 Pro XL and 10 Pro Fold includes a bootloader update that raises the anti-rollback version, and a May 2025 notice covers the Pixel 6, 6 Pro, 6a, 8, 8 Pro and 8a. After that update you cannot roll back to older bootloaders, and Google gives special steps (for May 2026, sideload the full OTA after the first successful boot so both slots are bootable) to avoid an unbootable phone if a flashed build fails to boot.3
- Community reports say Pixel 9 series phones disable some AI features once the bootloader is unlocked, regardless of root. Treat it as a reported behavior, not a documented policy.18
Related: Google Pixel root guide.
Nothing
Status: open on Phone (1); other models not independently checked here.
The Nothing Phone (1) uses the same flow as a Pixel: enable OEM unlocking, run fastboot flashing unlock, no code. LineageOS documents it that way, and the community record says the same.1020 We could not read a source for CMF phones or later models, so do not assume they behave identically.
OnePlus
Status: open on global phones; token or application on some variants.
Follow the universal procedure. The OnePlus 13 enters the bootloader with Volume Up + Volume Down + Power and unlocks with fastboot flashing unlock.8 Per the community record, global phones and Chinese models first released with ColorOS 15 or earlier can use the standard procedure, even after updating to ColorOS 16.19 Two exceptions:
- T-Mobile and MVNO variants (for example Metro) need an unlock token, and getting one requires the original proof of purchase from T-Mobile, even if the phone was later carrier-unlocked. A phone bought on eBay cannot get one. This does not apply to the OnePlus 6 or earlier.19 OnePlus hosts the token request page.26
- Mainland China models require an application to a "Deep Testing" program. Reports of tighter rules for newer ColorOS versions come from a forum we could not open, so this guide does not state the details.19
Related: OnePlus 12 and 13 root guide, OnePlus root guide 2026.
Motorola
Status: model-dependent; requires a code from Motorola.
- Enable OEM unlocking. LineageOS notes that some newer Motorola devices must be connected to the internet for up to 7 days before the toggle works.11
- In the bootloader, run
fastboot oem get_unlock_dataand copy the string it prints, joined into one line. - Submit it on Motorola's unlock portal, sign in, and receive a code. We could not open the portal ourselves, so follow its on-screen instructions and do not trust any fixed delivery time you read elsewhere.17
- Run
fastboot oem unlock <code>and confirm on the phone.
Caveats from the community record: Unisoc-based Motorola phones are never unlockable (a chipset policy, not Motorola's); a support exchange quoted there says most E-series phones are not covered by the unlock program; and phones can become ineligible after some age. Test eligibility on the portal before you buy or plan anything.17 The record also reports that on some models relocking after unlock can brick the phone, though not all models; read the relock section before you ever run a lock command on a Motorola.17
Related: Motorola Moto root guide.
Xiaomi, Redmi and POCO (HyperOS)
Status: hard. Permission first, then a countdown, then the PC tool.
Xiaomi Android One models skip all of the below and follow the standard flow.16 For everything else outside mainland China:
- Enable OEM unlocking in Settings > Additional settings > Developer options, then open the device unlock status page. If it says "Locked", use "Add account and device".16
- HyperOS adds a prior step. Before that request works, the community record says you must make a successful unlock request inside the Xiaomi Community app, with the region set to Global. Reported requirements are a Xiaomi account active for more than 30 days and app version 5.3.31 or later.16
- One device per year. From January 1, 2025 Xiaomi limits each account to one unlocked device per year, reported by Xiaomi-focused press and the community record. Older allowances of several per year are history.2416
- Expect a quota. Community reports say the Community app request has a daily cap (around 50 people) that fills almost immediately, with the window opening at midnight Beijing time.16 This comes from forum findings, not a Xiaomi statement.
- Meet the account conditions. The record lists a Xiaomi account in good standing, a SIM with an active data plan, and Wi-Fi turned off with mobile data on during the request, on phones with a SIM slot.16
- Wait out the countdown. The countdown is server-side, so no tool can skip it. It is typically 72 hours on HyperOS and 168 hours on MIUI, though people report 14 or 30 days. Do not remove the Xiaomi account or factory-reset the phone during the wait, because the countdown may restart.16
- Unlock with Mi Unlock on Windows. Xiaomi's page describes the sequence: sign in with your Mi account, power off, hold Volume Down + Power to reach Fastboot, connect and click Unlock. Xiaomi also warns that an unlocked phone loses some high-security features. The page is a legacy MIUI-era page, so it supports the tool steps only, not the HyperOS permission rules above.25
China-region phones: the community record calls official unlocking effectively impossible for these, especially imported ones, because Xiaomi removed it from the Community app. Wikipedia rates non-China HyperOS and mainland China HyperOS both "Very Hard".1623 Unofficial exploit chains exist; they are patched often, they are not an official route, and we do not cover or recommend them.
Related: Xiaomi and Redmi root guide, Xiaomi EU vs Global vs China ROM.
Sony Xperia
Status: model-dependent; code from Sony.
LineageOS documents the Xperia 1 II flow, and other models differ in detail:
- Dial
*#*#7378423#*#*to open the service menu, then go to Service info > Configuration. You can continue only if it says "Bootloader unlock allowed: Yes". - In Settings > About phone, record the first IMEI.
- Enable OEM unlocking in Developer options if present.
- Generate an unlock code on Sony's official unlock website using that IMEI.
- In fastboot, run
fastboot oem unlock <your_unlock_code>, and reboot if the phone does not do it itself.12
The page also warns that unlocking erases all data. We have not verified what Xperia unlocking does to camera or DRM features, so this guide makes no claim either way.
Samsung: One UI 8 changed everything
Status: removed. Read this section even if you only came for another brand, because older guides still describe a working procedure.
Starting with One UI 8.0, Samsung removed bootloader unlocking on phones and tablets in all regions (community records say the Galaxy Watch is a reported exception), according to Wikipedia (citing an XDA report from July 2025) and the community-maintained Wall of Shame.2315 Samsung has not published a statement we could find, and the original XDA thread returned an access error, so this is community-confirmed rather than vendor-confirmed. The practical consequences:
- If your phone is on One UI 7 or earlier and is an international model (the record also says Exynos phones regardless of region), the old flow still works. If you are on One UI 7, the community advice is not to update to One UI 8 until you have decided what you want.15
- If your phone is a US or Canadian Snapdragon model, it is not supported. Wikipedia and Magisk's documentation both describe North American devices as market-limited.2313 We do not link to or recommend the paid grey-market token services that exist.
- If your phone is on One UI 8 or later, there is no toggle to find. The record says that flashing One UI 8 on an already unlocked phone re-locks it, and that rolling back to One UI 7 is blocked unless the rollback bit is the same in both builds.15
- Hard-brick warning (community report). Community maintainers report that flashing One UI 8 firmware on a MediaTek Galaxy whose bootloader is already unlocked can permanently brick it, with three reported cases from one community. Do not flash One UI 8 on an unlocked MediaTek Samsung.15
The old flow, for One UI 7 and earlier only. Check first: Magisk's documentation says to enable Maintenance Mode (Settings > Device Care > Maintenance Mode), boot into Download mode and read the OEM Lock value. ON (L) means fully locked, ON (U) means locked with OEM unlocking enabled, OFF (U) means already unlocked. KnoxGuard "Active" or "Locked" means a carrier or insurer has remotely locked the phone, and that blocks Magisk whatever the bootloader state.13
- Enable Developer options via Settings > About phone > Software information > Build number, then switch on OEM unlocking.513
- Power off and enter Download mode with your model's key combination. The community guide lists: Home button phones, Power + Volume Down + Home; Bixby-button phones, Power + Volume Down + Bixby; phones with neither, hold Volume Down + Volume Up while connecting to a computer.15 Check your exact model because combinations differ.
- On the warning screen, long-press Volume Up until the unlock prompt appears, then press Volume Up again to confirm. The phone wipes and reboots.1315
- Complete setup, reconnect to the internet, then open Developer options again. The OEM unlocking entry should exist and be greyed out, which Magisk's documentation says means KnoxGuard has not locked the phone.13
The community record adds that the Galaxy S25 and some tablets need an internet connection before unlocking works.15
Knox is permanent. Unlocking or flashing custom firmware permanently trips Knox on supported devices. Wikipedia says Samsung Wallet, Secure Folder and Knox-framework apps then stay unusable even if you relock; the community record also lists Samsung Pay, Pass, Flow, Health, Secure Wi-Fi and Smart View, and notes a tripped Knox may be grounds to void the warranty.2315 Magisk's documentation says installing Magisk trips the warranty bit irreversibly.13 Details are in our Samsung Knox and warranty guide, root specifics are in the Samsung Galaxy root guide, and flashing problems are covered in Odin fail errors.
Honor, Huawei, Asus, Vivo, LG and Realme/OPPO
No step lists here, because there is nothing dependable to list:
| Brand | What public sources say | Source |
|---|---|---|
| Honor | An unlock command exists in fastboot but is reported to behave as if it unlocked without actually unlocking | 21 |
| Huawei | Stopped providing unlock codes in 2018 | 23 |
| Asus | Unlock tool and servers removed in August 2023; no working official unlock since | 23 |
| Vivo | Listed as impossible as of May 2022 | 23 |
| LG | Unlock-token website shut down on December 31, 2021 | 23 |
| Realme / OPPO | Realme allows unlocking for some models and regions through its "Deep Testing" app; the community record calls the process poor and region-dependent | 22 |
On Asus, one source headline hedged about whether the shutdown was permanent and forum representatives said the tool would return, so we say "no working official unlock since August 2023" rather than "shut down for good".23 Our bootloader unlock guide for 2026 covers the per-brand 2026 policy detail for these phones.
OEM unlocking greyed out or missing: causes and fixes
This is the most searched problem on the topic, and the honest answer is that the toggle reflects permission you may not have. Use the matrix to find your case.
| What you see | Likely cause | What to do | Source |
|---|---|---|---|
| Toggle missing entirely | The device build does not support flashing unlock (ro.oem_unlock_supported not set), a carrier-restricted variant, a US/Canada Samsung, or Samsung on One UI 8 or later |
Check the status table. If your row says closed, no setting changes that | 115 |
| Greyed out and on | The bootloader may already be unlocked; on Samsung, a greyed-out entry after setup means KnoxGuard has not locked the phone | On Samsung read the OEM Lock value in Download mode; on others check the boot warning screen | 1315 |
| Greyed out and off | Phone not yet activated or connected online (Pixel token check), a vendor wait (Motorola up to 7 days, Xiaomi account binding), a remote lock (KnoxGuard Active/Locked, or a carrier or finance lock) | Connect to the internet, sign in and give it time; remove carrier, finance or management locks through the party that applied them | 18111613 |
| Switch is on but fastboot says unlocking is not allowed | get_unlock_ability is still 0 |
Turn the switch off and on, reboot, then try again | 1 |
| Samsung toggle present but Download mode shows no OEM Lock line | Market-limited firmware | Treat as not unlockable | 13 |
On Samsung specifically, the community record names the usual causes of a missing or greyed-out switch: the phone is locked to a carrier that restricts unlocking, it is an American model, or it runs One UI 8 or later.15
Two honesty notes. First, if the vendor withholds permission, no app, setting or "trick" changes that; people who say otherwise are selling something. Second, this page does not teach bypassing account locks. If your phone is locked by a Google or Samsung account you cannot access, that is an ownership and account-recovery matter, not a bootloader one.
If you are stuck at a vendor gate, our bootloader unlock service page describes how we assess an exact model and what a service can and cannot do.
"Bootloader unlock APK" and unlock tools: what is real
People search for an app that unlocks a bootloader with a tap. There is no universal, safe one, and the design of Android explains why.
A locked bootloader is unlocked from the bootloader (or from Samsung's Download mode), with the vendor's permission and, in AOSP's model, a user confirmation on the device. Unlocking must wipe the phone.1 A normal Android app runs after the operating system has already been verified and started; it does not control the code that ran before it.
What actually exists:
- Real vendor routes: fastboot itself, Xiaomi's Mi Unlock tool on Windows, Motorola's code portal, Sony's code site, and (before One UI 8) Samsung's Download mode.25111213
- Asus's first-party unlock APK, which contacted Asus servers and then prompted a factory reset. It stopped working when Asus removed the tool and closed the servers in August 2023.23 It is the only genuine "unlock APK" most people can name, and it is gone.
- Wrappers and phone-to-phone setups. Some apps just send fastboot commands from one phone to another over OTG. That replaces the PC, not the permission: the target phone still needs a vendor that allows unlocking and the same OEM toggle.
- Everything else returned by search for these terms is forums, videos promising "free unlock" apps, and unrelated results. The risk is malware, stolen accounts or paid scams, so we do not name or link any of them.
A quick test: if a tool claims it can unlock a bootloader without OEM unlocking or vendor permission, it is either lying or using a device-specific exploit that will be patched. Our guide to temporary root without unlocking the bootloader covers that narrow, build-specific territory honestly. The same logic answers "unlock without a PC": there is no official PC-free path that skips the vendor's gate.
After you unlock: what changes and what stays broken
| Area | What changes | Source |
|---|---|---|
| Boot screen | Verified Boot reports an unlocked device state; phones typically show a warning at boot | 2 |
| Play Integrity | On Android 13 and higher, the device-integrity verdict needs hardware-backed proof that the bootloader is locked and the OS is a certified image. The optional basic verdict can still be returned with an unlocked bootloader | 7 |
| Banking, wallet and DRM apps | May refuse to run or degrade; behavior is app-specific and not guaranteed | 23 |
| Samsung Knox | Permanently tripped; Samsung Wallet, Secure Folder and Knox apps stay broken even after relock | 2313 |
| Pixel 9 and newer | Some AI features reported disabled | 18 |
| Security | The phone is less secure, and OEM unlocking disables FRP | 314 |
| Updates | Pixel factory-image flashing erases data; Google prefers sideloading the full OTA | 3 |
On Play Integrity, Google's wording matters: the optional basic and strong labels on Android 13 and higher are returned only to apps installed or updated through Google Play, and the basic label only needs a Google-provided attestation root.7 Nobody can promise you a particular verdict after unlocking, and neither do we. If that is your concern, read Play Integrity fix on rooted Android and the SafetyNet to Play Integrity guide with that in mind.
What to do next. If your next step is root, choose between Magisk, KernelSU and APatch with this comparison, and use the right boot or init_boot image. Our general rooting guide ties the steps together. Read rooting risks before you commit.
Relocking the bootloader safely
To lock the bootloader and reset the device, run fastboot flashing lock.1 Google tells Pixel users to relock after using a factory image.3 The rule that keeps you safe: only relock when the phone is running unmodified, official, matching firmware. Locking a phone that still carries a custom or unsigned image can leave it unable to boot, and Wikipedia notes the risk of a soft brick if modifications remain.23
- Pixel: relocking after a full stock flash is the documented path.3
- Motorola: the community record reports some models brick on relock. Do not relock without model-specific confirmation.17
- Samsung: relocking does not undo the Knox trip.23
- Everything else: find a model-specific source that says relocking is supported, then flash the full stock firmware first.
Relocking also erases data, so back up again.
Check whether your bootloader is already unlocked
Look for the unlock warning at boot, or on Samsung read the OEM Lock value in Download mode as described above.213 On many fastboot devices fastboot getvar unlocked reports the state, but behavior varies by vendor and we did not verify it per brand, so use it as a hint rather than proof.
Troubleshooting matrix
| Symptom | Likely cause | Fix |
|---|---|---|
fastboot devices shows nothing |
Charging-only cable, missing Windows driver, or Linux permissions | Try another cable and port; install your vendor's OEM USB driver on Windows; on Linux set up udev rules or run as root for a test.146 See also fastboot device not detected |
adb devices shows unauthorized |
USB debugging prompt not accepted | Revoke authorizations in Developer options, reconnect and accept the prompt |
| Phone boots normally instead of entering fastboot | Wrong key combination for the model | Use adb reboot bootloader, or look up your model's combination.115 |
FAILED (remote: unrecognized command) on flashing unlock |
In fastbootd, or the vendor uses a different command | Make sure you are in the bootloader, then try the legacy fastboot oem unlock, then a model guide.14 |
| Unlock refused ("not allowed") | OEM unlocking off or get_unlock_ability = 0 |
Toggle OEM unlocking again and reboot.1 |
| Motorola code rejected | Typo in the data string or ineligible model | Re-run fastboot oem get_unlock_data, join lines carefully, check the portal's eligibility message |
| Xiaomi says the quota is reached | Community-app daily cap | Retry at the next window; do not pay for "quota tricks".16 |
| Samsung shows no unlock prompt | One UI 8 or later, US/Canada model, or wrong key combination | Check the OEM Lock value; if there is none, stop.1315 |
| Bootloop after you flash something | Wrong or incompatible image | Stop flashing repeatedly; see bootloop after custom ROM and phone stuck on boot screen |
Should you unlock at all?
Unlock if you need a custom ROM, a patched boot image or a custom kernel, and you accept the data wipe, weaker security and loss of features such as some banking, wallet and DRM behavior. Do not unlock if you rely on Samsung Wallet or Secure Folder, if the phone is your only device, or if you only want a single root-level setting. On Pixels, sideloading an official full OTA can avoid factory-image risk without involving root.3 For one-off privileged access on specific builds, the temporary-root article explains what is and is not possible, and should I root my Android? helps you decide.
Need a second pair of hands?
We only discuss unlocking a phone you own or are authorized to administer. Start with a review of your exact model, region, carrier, firmware build and current bootloader state: we check what the manufacturer offers for that variant, whether a carrier or account restriction blocks it, and whether a verified backup exists, before anything is attempted.
We cannot unlock a phone the manufacturer has locked out, and we will say so before any work starts. We do not promise timings, data preservation (unlocking erases data) or any banking-app or Play Integrity outcome. Request a review through the bootloader unlock service, the wider Android rooting service, or the contact page. Send model details only: never passwords, one-time codes or recovery phrases.
The bottom line
Unlocking an Android bootloader is simple when the manufacturer allows it and impossible when it does not. Check the status table first, then enable OEM unlocking, run fastboot flashing unlock or the vendor's code flow, and expect a full wipe.
The 2026 news is subtractive: Samsung's One UI 8 closed the door, Xiaomi's gate is slow and capped, and no app replaces vendor permission. Pick the phone for the policy as well as the specs, back up twice, and do not relock with anything but stock firmware.
If your exact model is unclear, ask us before you wipe it.
Sources and project documentation
-
AOSP: Lock and unlock the bootloader.
fastboot flashing unlock,get_unlock_ability, the factory reset on unlock, RAM clearing,fastboot flashing lock, critical-partition rules andro.oem_unlock_supported. Page showed last updated October 9, 2026. ↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩ -
AOSP: Verified Boot device state. LOCKED and UNLOCKED states. ↩↩↩↩
-
Google: Factory images for Nexus and Pixel devices. Relock after a factory image, data erase, sideloading the full OTA, and the May 2025 and May 2026 bootloader anti-rollback notices. ↩↩↩↩↩↩↩↩↩
-
Android SDK Platform-Tools release notes. Download the current stable release; a newer canary build may also be listed. ↩
-
Android Developers: Configure on-device developer options. Seven taps on Build number and the Build number path for Pixel, Samsung Galaxy S8 and later, and OnePlus 5T and later. ↩↩↩
-
Android Developers: OEM USB drivers. Driver links by manufacturer for Windows. ↩↩
-
Play Integrity API: integrity verdicts. Device and basic integrity requirements on Android 13 and higher; optional labels only for apps licensed through Google Play. ↩↩
-
LineageOS Wiki: Install on OnePlus 13 (dodge). Enable OEM unlock "if present", key combination,
fastboot flashing unlock, data-erase warning. ↩↩↩↩↩↩↩ -
LineageOS Wiki: Install on Pixel 7 (panther). Same flow with Volume Down + Power. ↩↩↩
-
LineageOS Wiki: Install on Nothing Phone (1) (Spacewar). Standard flow, no code. ↩↩↩
-
LineageOS Wiki: Install on a Motorola device (hawao). Up to 7 days online for some newer models and the account-removal note. ↩↩↩↩↩
-
LineageOS Wiki: Install on Sony Xperia 1 II (pdx203). Service menu, IMEI, Sony unlock code and
fastboot oem unlock <code>. ↩↩↩↩↩ -
Magisk installation guide, Samsung section. OEM Lock values, KnoxGuard states, Knox trip, the extra wipe for first install, long-press Volume Up unlock step and the market-limit note. The guide describes the pre-One UI 8 flow. ↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩
-
Bootloader Unlock Wall of Shame: generic unlock guide. Community-maintained; command variants, drivers, udev, and the factory-reset-protection note. Licensed CC BY-NC-SA 4.0; facts are summarized here with attribution. ↩↩↩↩↩↩↩
-
Wall of Shame: Samsung and Samsung unlock guide. One UI 8 removal, MediaTek brick warning, Download-mode combinations, Knox feature list. Community reports. ↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩
-
Wall of Shame: Xiaomi, Redmi, POCO. HyperOS steps, Community-app requirements, quota and countdown reports, China-region and Android One notes. ↩↩↩↩↩↩↩↩↩↩↩↩↩↩
-
Wall of Shame: Motorola. Portal-based code, Unisoc exclusion, eligibility and relock-brick reports. ↩↩↩↩↩↩↩
-
Wall of Shame: Google Pixel. Unlock-token check, carrier restriction and Pixel 9 AI-feature reports. ↩↩↩↩↩
-
Wall of Shame: OnePlus. Standard procedure, T-Mobile and MVNO tokens, China Deep Testing. ↩↩↩↩
-
Wall of Shame: Nothing. No-code fastboot unlock. ↩↩
-
Wall of Shame: Honor. Reported fake unlock command. ↩↩
-
Wall of Shame: OPPO and Realme. Deep Testing route for Realme. ↩
-
Wikipedia: Bootloader unlocking. Brand overview, Samsung One UI 8.0 removal (citing XDA), Knox consequences, Huawei, LG and Asus shutdowns, relocking caveats. Secondary source with a "needs citations" tag in places. ↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩↩
-
XimiTime: Xiaomi global bootloader unlock policy has changed. One device per year policy change. ↩↩↩
-
Xiaomi: Mi Unlock. Mi Unlock tool steps and security notice; a legacy page that does not describe the HyperOS Community-app step. ↩↩
-
OnePlus: unlock token request. Page exists; its policy text did not render when we checked, so eligibility rules come from the community record. ↩↩
Frequently asked questions
Does unlocking the bootloader erase my data?
Is the Samsung bootloader unlockable?
How do I enable OEM unlocking on Samsung?
Why is OEM unlocking greyed out or missing?
Because the phone has not been granted permission to unlock: unsupported firmware, a carrier restriction, a vendor waiting period, a remote lock, or Samsung's One UI 8 policy. If it is greyed out and on, the bootloader may already be unlocked. The matrix above lists each case.