How to Check if Your Android Bootloader is Unlocked (Fast & Easy)
Checking whether your phone’s bootloader is unlocked tells you whether the device can accept unsigned or modified boot, recovery, or system images. For most Android users, the safest way to check bootloader status is to boot into Fastboot mode and read the lock state there; ADB helps you reboot into that mode, but Fastboot usually provides the actual answer.
This guide walks through visual checks, button-based checks, and the most reliable adb check bootloader status workflow without pushing you into unlocking anything by accident.
What does an unlocked bootloader mean?
Tester's Note: In my hands-on testing, I treat an unlocked bootloader as a “flash-ready” state, not as proof that the phone is rooted. Always check root, recovery, and bootloader status separately when buying or testing a used Android device.
An unlocked bootloader means the phone is allowed to boot or flash software that may not be signed by the device maker’s normal trusted chain. Android’s own boot flow documentation describes the bootloader as the stage that checks device state and can warn the user when the device is unlocked before continuing to boot. In plain English, the phone may still work normally, but the security assumptions are different because modified images can be loaded more easily.
A locked bootloader is the standard retail state for most Android phones. It helps prevent unauthorized changes to protected partitions, which is why it matters for banking apps, enterprise policies, resale checks, warranty conversations, and custom ROM work. An unlocked bootloader is common among Android modders, kernel testers, ROM reviewers, and repair technicians, but it is not something to ignore on a daily-driver phone.
The key point is that bootloader status is not the same as “is this phone hacked?” or “is this phone rooted?” A phone can have an unlocked bootloader and no root access. It can also be rooted through a patched boot image, custom recovery, or other modification after the bootloader has been unlocked.
The safest checks before connecting to a computer
Pro Tip: From personal experience, I first reboot the phone normally and watch the first five seconds of startup before touching ADB. Many unlocked test units reveal themselves with a boot warning before any cable or driver troubleshooting is needed.
Start with the simplest visual clues. Many Android devices show a warning screen during boot if the bootloader is unlocked, often saying the device software cannot be checked for corruption or that the bootloader is unlocked. Android Verified Boot documentation describes visible boot states and warnings as part of the boot process, although the exact wording and color vary by device maker.
If you see a clear unlocked bootloader warning every time the phone starts, that is strong evidence that the bootloader is unlocked. If you do not see a warning, do not assume the bootloader is locked. Some devices display the message briefly, some use different wording, and some carrier or regional variants make the state harder to identify from the normal boot screen.
You can also check Developer Options for the OEM unlocking toggle. This setting does not directly prove the current bootloader state, but it tells you whether the phone may allow a transition to unlocking. AOSP notes that devices should deny fastboot flashing unlock unless get_unlock_ability is set to 1, and enabling OEM unlocking is the usual user-facing way to set that ability.
Useful pre-checks:
Restart the phone and watch for boot warnings.
Open Settings and look for About phone to confirm the model.
Enable Developer Options only if you need ADB access.
Check whether OEM unlocking is present, grayed out, enabled, or missing.
Do not tap any unlock, erase, or reset prompt unless you are intentionally changing the device.
How do you check bootloader status with ADB and Fastboot?
Tester's Note: In my hands-on testing, the cleanest workflow is ADB for rebooting and Fastboot for reading the result. If adb devices works but fastboot devices does not, the problem is usually a driver or cable issue, not the phone’s bootloader state.
The practical android check bootloader status method is to connect the phone, use ADB to reboot into the bootloader, then use Fastboot to query the lock state. AOSP explicitly lists adb reboot bootloader as one way to enter bootloader mode, and Fastboot’s getvar command is designed to display bootloader variables.
Before you start, install platform tools from a trusted source, use a data-capable USB cable, and unlock the phone’s screen so you can approve USB debugging. On the phone, go to Developer Options and enable USB debugging. When you connect the device, accept the RSA debugging prompt if it appears.
Use this sequence:
Connect the phone to your computer.
Open Terminal, Command Prompt, or PowerShell in your platform-tools folder.
Run adb devices.
If the device appears as authorized, run adb reboot bootloader.
Wait for the Fastboot or bootloader screen.
Run fastboot devices.
Run one or more Fastboot status commands.
Common status commands include:
fastboot oem device-info
fastboot getvar unlocked
fastboot getvar secure
fastboot getvar all
The exact command that works depends on the phone. On many devices, fastboot getvar unlocked returns a simple yes/no or true/false style result. On some older or brand-specific devices, fastboot oem device-info is more useful. On others, fastboot getvar all shows several variables, and you have to scan the output for lock, unlock, flashing, secure, or verified boot fields.
Reading the Fastboot result correctly
Pro Tip: A quick workaround I discovered during device reviews is to save the full Fastboot output to a text file, then search it for “unlock,” “lock,” “secure,” and “flash.” It prevents missing a useful line that scrolls past too quickly.
Fastboot output is not perfectly standardized across every Android phone, so read it carefully. You may see a line such as unlocked: yes, Device unlocked: true, or Device unlocked: false. In those cases, the meaning is direct: yes or true means unlocked, while no or false means locked.
You may also see references to flash lock state. AOSP’s bootloader guidance says devices that support flashing unlock should indicate lock status with a boot variable where androidboot.flash.locked is 1 when locked and 0 when unlocked, though implementation details can differ by Android version and device.
Treat these patterns as practical clues:
unlocked: yes, unlocked: true, or Device unlocked: true means the bootloader is unlocked.
unlocked: no, unlocked: false, or Device unlocked: false means the bootloader is locked.
flash.locked: 1 usually points to a locked flashing state.
flash.locked: 0 usually points to an unlocked flashing state.
secure: yes does not always mean the bootloader is locked; compare it with the unlock-specific field.
FAILED remote: unknown command means that command is not supported, not that the bootloader is locked.
When I test phones, I avoid relying on a single ambiguous line. If one command fails, I run another. If Fastboot says the command is unknown but the bootloader screen itself says “unlocked,” the screen is often the clearer signal. If Fastboot shows multiple conflicting-looking fields, prioritize the one that directly mentions unlocked, device unlocked, flashing unlock, or flash locked.
Checking from the bootloader screen itself
Tester's Note: From personal experience, physical-button bootloader checks are a lifesaver on phones with broken Android installs. If the OS will not boot, Fastboot mode may still tell you whether the device is locked.
You do not always need ADB. Many phones can boot to the bootloader with a button combination, commonly by powering off and holding a volume key while pressing power. The exact combination varies, so use the device maker’s support material when available.
Once in the bootloader, read the on-screen text. Pixel-like devices often show status lines for locked state, secure boot, product name, slot, and bootloader version. Other devices may show a smaller Fastboot screen with less detail. If the screen says unlocked, device state: unlocked, or similar, you have your answer.
This method is especially useful when USB debugging was never enabled. ADB requires Android to boot far enough to authorize your computer, but the bootloader screen is outside the normal Android interface. That makes it valuable for used-phone inspections, soft-bricked devices, and lab testing where the installed OS may not be trustworthy.
The drawback is that not every manufacturer exposes the same status text. Some phones show the lock state clearly. Others only show Fastboot mode without enough detail, which means you still need the check bootloader status command path through Fastboot.
Why does the result sometimes look different across phones?
Pro Tip: In my hands-on testing, I keep a small note for each brand’s preferred command because Fastboot wording changes more than people expect. If one command fails, do not panic; switch commands before drawing a conclusion.
Bootloader status checks differ because Android devices are built by different manufacturers, use different bootloader interfaces, and may ship with carrier restrictions. AOSP defines expected behaviors, such as requiring physical interaction for unlocking and using Fastboot commands for state changes, but device makers still control many user-facing details.
Some phones support fastboot flashing unlock; older ones may use fastboot oem unlock. Some expose fastboot getvar unlocked; others hide that field but show device info through an OEM command. Some carrier models do not allow unlocking at all, even if similar unlocked retail models do.
There is also a difference between bootloader mode and FastbootD. AOSP describes FastbootD as a userspace Fastboot environment used for certain flashing tasks, while bootloader Fastboot handles lower-level bootloader operations. If you are trying to read lock state and the output looks limited or strange, rebooting back to the bootloader Fastboot screen can remove confusion.
A practical troubleshooting checklist:
Try a different USB cable, preferably the original or a known data cable.
Switch USB ports, especially from a hub to a direct motherboard port.
Reinstall or update Android platform tools.
On Windows, check Device Manager for driver problems in Fastboot mode.
Run both fastboot getvar unlocked and fastboot oem device-info.
If you land in FastbootD, use the on-screen option or command to reboot to bootloader.
Compare command output with the phone’s own bootloader screen.
Avoiding accidental unlocks, wipes, and lock problems
Tester's Note: From personal experience, the riskiest moment is not checking status; it is rushing through a prompt you did not read. I keep my hands off the volume and power buttons whenever an unlock confirmation screen appears unexpectedly.
Checking bootloader status should not wipe your phone. Commands like adb devices, adb reboot bootloader, fastboot devices, and fastboot getvar unlocked are read-only or reboot-focused in normal use. The dangerous line is when you run an unlock or lock command and confirm it on the device.
AOSP states that when fastboot flashing unlock is sent, the device should warn the user and perform a factory data reset after confirmation to prevent unauthorized data access. That means you should never test unlock commands casually on a phone with data you care about.
Locking can be risky too. If a phone is running modified boot, recovery, vendor, or system images, relocking the bootloader may stop it from booting correctly. As a reviewer, I only relock after restoring the correct factory firmware and confirming the device boots cleanly.
Before making any change, use this safety list:
Back up photos, downloads, messages, authenticator recovery codes, and app data.
Confirm the exact model and regional variant.
Download the correct factory firmware before changing lock state.
Charge the battery well above the low-battery warning range.
Read every on-device confirmation screen.
Do not relock a modified phone unless factory images are restored.
Best method for used phones, repairs, and testing benches
Pro Tip: In my hands-on testing, I run the same three-part check on every used Android phone: boot warning, bootloader screen, then Fastboot output. That sequence catches more edge cases than relying on Settings alone.
If you are inspecting a used phone, start with the boot screen because it is fast and does not require trusting the installed Android system. Then boot into the bootloader and read the device state. Finally, use Fastboot commands to capture the result in text, which is helpful if you need to document the condition.
For repair work, bootloader status helps you choose the right recovery path. A locked phone may require official recovery tools, signed update packages, or manufacturer service software. An unlocked phone may allow more direct flashing, but that does not mean every image is safe or compatible.
For gaming and performance testing, bootloader status matters because custom kernels, modified thermal profiles, and rooted tools can affect benchmark behavior. If you compare phones, note the bootloader state in your test log. A stock locked phone and an unlocked modified phone should not be treated as identical test conditions.
The most reliable final answer comes from combining signals. A warning at boot, an unlocked state on the bootloader screen, and a Fastboot result showing unlocked make the case clear. If the signals disagree, slow down and verify the exact model, command support, and current boot mode before making a call.
Key takeaways for checking bootloader status
Tester's Note: From personal experience, the best habit is to separate checking from changing. I type only read-only commands first, then copy any unlock or lock command manually later if I truly intend to modify the device.
To check bootloader status, use ADB only as the bridge into bootloader mode, then let Fastboot report the state. The core workflow is adb devices, adb reboot bootloader, fastboot devices, and then a status command such as fastboot getvar unlocked or fastboot oem device-info. That is the most practical answer for anyone searching for adb check bootloader status or android check bootloader status.
Remember that command wording varies by device. A failed or unknown Fastboot command is not a verdict. Try another status command, read the bootloader screen, and compare the results.
Most importantly, do not run unlock or lock commands just to check the status. Checking should be low-risk; changing the bootloader state can wipe data, affect security, and create boot problems if the software on the phone is not stock. Treat the bootloader like a lab switch: read it carefully, document it clearly, and flip it only when you already know why you need to.