Picture this: you press the power button, the screen flickers to life, and instead of your usual home screen you get a stark black page with the words “your device has been unlocked and can’t be trusted.” No icons. No wallpaper. Just a warning and maybe a pause button. Is your phone broken? Hacked? About to explode? None of the above, most likely. That message is a deliberate security notice from Android, and understanding it takes about five minutes. What you do next depends entirely on how the bootloader got unlocked and what you want from the device.
What the Warning Actually Says and Why It Appears
The message is a bootloader warning. It shows up on Android devices whose bootloader has been unlocked, and it appears during the boot process before the operating system fully loads. Google Pixel and Nexus phones are the most common place people see it, but the exact wording and behavior vary by manufacturer and Android version.
Here is the mechanism behind it. Android uses a feature called verified boot, built on Android Verified Boot (AVB). At every stage of startup, the system checks whether the software about to run is signed with the device’s original trusted key. If the chain of trust holds, the device boots normally and quietly. If the bootloader is unlocked, that enforcement is disabled. An unsigned or re-signed image can boot, so the system warns the user instead of pretending everything is fine.
The concept dates back to Android 4.4, and AVB 2.0 arrived with Android 7.0 in 2016. The warning is not an error message in the traditional sense. It is a design decision: the phone is telling you, honestly, that its security guarantees are weaker than they were out of the box.
The Color States You Might See
Bootloader screens often communicate status through color. A locked, verified device typically shows a green state. An unlocked bootloader shows orange. A failed verification shows red. The exact wording of these states has shifted across Android versions and manufacturers, so treat any single description as device-specific rather than universal.
How the Bootloader Got Unlocked in the First Place
There are only a few realistic paths to this screen.
The first is intentional. Someone ran a command like `fastboot flashing unlock` on a Pixel or used a manufacturer-specific unlock tool on another brand. This is a normal step for installing a custom ROM such as LineageOS, flashing a rooted system image, or loading a factory image for repair. LineageOS install guides assume an unlocked bootloader, which is why the warning is so familiar in that community.
The second is a secondhand purchase. Plenty of people buy a used phone and discover the previous owner had unlocked it. The warning greets them at first boot, and they have no idea what it means.
The third is a repair or reseller who flashed software and left the bootloader open. This happens more often than it should.
What does not cause it: malware, a dropped phone, a bad update, or a drained battery. If you never unlocked anything and never handed the phone to someone who might have, that is worth investigating, but the warning itself is a state indicator, not a symptom of compromise.
Is an Unlocked Bootloader Dangerous?
It depends on your threat model, but the honest answer is: yes, it weakens security, and that is the whole point of the warning.
An unlocked bootloader means the device can run modified software. That cuts both ways. It is what makes custom ROMs, root access, and deep system tweaks possible. It also means malware or a malicious ROM could persist on the device in ways a locked phone would block. The verified boot chain exists precisely to stop that.
The practical fallout shows up in everyday apps. Many banking apps, payment services, and DRM-protected streaming services refuse to run on unlocked devices. Widevine L1, the highest playback security level for services like Netflix, often drops to a lower level or stops working. Some corporate device management profiles will not enroll an unlocked phone. None of this is a bug. It is a deliberate trade-off: the app developers cannot verify the software environment, so they decline to trust it.
A useful distinction: unlocking the bootloader is not the same as rooting. Rooting means gaining superuser access inside Android. Unlocking is usually a prerequisite for flashing a rooted image, but the warning reflects bootloader state, not root status. A phone can be unlocked without being rooted, and the warning will still appear.
Should You Re-Lock the Bootloader?
For most people who see this warning and did not intend to modify their phone, re-locking is the right move. The command is typically `fastboot flashing lock`, and it restores the warning-free boot state, provided the installed software is signed by the device’s original keys.
Here is the part that trips people up. Re-locking with a non-stock image can brick the device or trigger a red state. If a custom ROM or a modified system image is installed, locking the bootloader may leave the phone unable to boot at all. Before locking anything, confirm the software on the device matches the manufacturer’s official signed build.
A sensible order of operations looks like this:
- Identify the exact model and current software build.
- Flash the official factory image for that model if you want a clean, stock system.
- Verify the device boots normally with the bootloader still unlocked.
- Only then run the lock command.
- Reboot and confirm the warning is gone and the phone starts cleanly.
Skipping step two is the most common mistake. People lock first, then discover the phone will not start, and the recovery process is more involved than the original unlock.
What About Warranty and Support?
Many manufacturers treat bootloader unlocking as voiding warranty or support eligibility, though policies differ by region and vendor. Samsung, Xiaomi, and OnePlus have each handled this differently over the years, and carrier policies can add another layer. Before unlocking a phone you might need serviced, check the manufacturer’s current stance for your region. The warning screen itself is a visible flag to any technician that the device has been modified.
If you are weighing whether the trade-off is worth it, it helps to think about what you gain. Unlocking is genuinely useful for privacy-focused users, developers, and anyone extending the life of an older phone with a lighter ROM. It is also the standard first step for anyone learning Android internals. If your goal is simply a working daily driver with banking apps and streaming, staying locked is the smoother path.
Common Mistakes People Make
A few patterns show up again and again.
Panicking at first boot. The warning looks alarming, but it is informational. The phone is not infected. It is telling you its security state.
Locking before checking the installed software. Covered above, and it is the mistake with the worst consequences.
Assuming the warning means the phone is rooted. It does not. It means the bootloader is open.
Ignoring the security implications on a shared or work device. An unlocked bootloader on a phone that handles work email or two-factor codes is a risk worth taking seriously. If you are worried about what else might be on the device, it is worth learning how to check whether your device or account is affected by spyware before you decide to keep it unlocked.
Forgetting that some fixes require different tools entirely. Bootloader state is one layer of device security. Network-level attacks are another, and knowing how to tell if DNS poisoning is hitting your device or account rounds out the picture.
Device-by-Device Differences Worth Knowing
The warning is not standardized across the industry. Here is a rough comparison of how the experience varies.
| Device family | Typical warning behavior | Re-lock notes |
|---|---|---|
| Google Pixel / Nexus | Warning at every boot until re-locked | Re-lock only with official signed images |
| Samsung | Different unlock flow, different messaging | Knox features may be affected permanently |
| Xiaomi | Manufacturer unlock tool and waiting period | Regional policies vary widely |
| OnePlus | Unlock via fastboot, warning on boot | Re-lock behavior varies by model |
| Devices running LineageOS | Warning expected and normal | Re-lock usually requires returning to stock first |
The takeaway from the table: never assume a guide written for a Pixel applies to your phone. The commands may look similar, but the consequences of getting them wrong differ sharply.
When the Warning Is a Symptom of Something Else
Occasionally the bootloader message shows up alongside other odd behavior: apps crashing, battery draining fast, settings changing on their own. In those cases the warning is not the cause, just a visible sign that the device has been modified. It is worth checking whether something else is going on, including whether your device or account has been affected by a man-in-the-middle attack, which can produce strange network and app behavior that has nothing to do with the bootloader.
Similarly, if you have been tinkering with smart home gear and things started misbehaving around the same time, the two issues are probably unrelated. A Matter device going offline after a router restart is a network problem, not a phone security problem, even if both happened in the same week.
The Bottom Line on That Black Screen
The “your device has been unlocked and can’t be trusted” message is Android being honest with you. It means the bootloader is open, verified boot is not enforcing the original software chain, and the phone can run modified code. For developers and custom ROM users, it is a familiar sight and a small price for flexibility. For everyone else, it usually means a used phone came unlocked or a repair left it that way, and the fix is to flash official software and re-lock.
The warning is not a virus alert, and it is not a death sentence for the device. It is a status light. Read it, decide whether you want the trade-off, and act accordingly.
Frequently Asked Questions
Does this warning mean my phone has a virus?
No. The message reflects bootloader state, not malware. It appears because the bootloader is unlocked, which disables verified boot’s enforcement of the original software chain. A locked phone with a virus would not show this warning. That said, an unlocked bootloader does weaken security, so it is reasonable to check the device for other issues if you did not unlock it yourself.
Can I remove the warning without re-locking the bootloader?
On most devices, no. The warning is tied to the unlocked state and appears at every boot until the bootloader is re-locked. Some custom ROMs and bootloader modifications can hide or replace the message, but those changes carry their own risks and vary by device. The clean, supported fix is to return to official software and re-lock.
Will re-locking brick my phone?
It can, if the installed software is not signed by the device’s original keys. Re-locking with a custom ROM or modified image may leave the phone unable to boot. Flash the official factory image first, confirm the device starts normally, and only then run the lock command. Done in that order, re-locking is usually safe.
Is unlocking the bootloader the same as rooting?
No. Rooting means gaining superuser access within Android. Unlocking the bootloader opens the door to flashing modified software, which is usually how people root, but the two are separate states. A phone can be unlocked and unrooted, and the warning will still appear.
Why do my banking and streaming apps stop working?
Many apps check the device’s security state before running. An unlocked bootloader means they cannot verify the software environment, so they refuse to operate or downgrade features. DRM-protected streaming often drops below Widevine L1. This is intentional on the app developers’ part, not a malfunction.
I bought a used phone and saw this message. What should I do?
First, confirm the model and check whether the software is the manufacturer’s official build. If it is, re-locking the bootloader will remove the warning. If a custom ROM is installed, decide whether you want to keep it or flash back to stock. Either way, do not lock the bootloader until you know exactly what software is on the device.
