“Your device software can’t be checked for corruption. Please lock the bootloader” means your Android phone’s bootloader is unlocked, so Android’s Verified Boot can’t confirm the system software is the one the maker signed. It isn’t a virus alert, and your phone isn’t broken: the screen goes away after about ten seconds and the phone boots normally. To get rid of it for good, put the official firmware back and relock the bootloader, which erases everything on the phone.
Newer Android versions word the same screen differently (“The bootloader is unlocked and software integrity cannot be guaranteed”), and some phones say “cannot” instead of “can’t”. Same warning, same cause.
What owners ask when this screen shows up
“It appears on every power-on after I installed a custom ROM. How do I remove it?”
That’s the exact situation in an /e/OS community thread about a Nexus 5X. The replies explained that the message shows whenever the bootloader is unlocked, on stock or custom software, and that the phone carries on booting after a short pause. The only way to make it go away was to relock, and the phone offered a factory reset at that point. The owner chose to live with it. That matches Google’s own design: the orange screen is meant to be shown on every boot while the device is unlocked.
“Does the message matter if I want to keep using the phone?”
An LG G5 owner asked this on the /e/ forum and was told the message is normal for an unlocked bootloader and nothing to worry about. The same thread warned that relocking a phone that runs a third-party ROM is difficult. That warning is the important part, and the section on relocking below explains why.
“The phone boots fine after five seconds. Is there anything to fix?”
On a thread about a BQ Aquaris X Pro running /e/OS, the answer was no: it’s the “orange state” warning from Android Verified Boot, and the owner ended up calling it “a minor issue.” The reply also mentioned hex-editing boot files on MediaTek phones to hide it. Skip that unless you know exactly what you’re doing; editing boot firmware is an easy way to brick a phone.
“I tried to lock the bootloader and now it says it’s corrupt”
A Pixel 6a owner on the GrapheneOS forum hit this after a flash that only half finished. The advice from that thread: a corruption message means the install didn’t complete, so don’t lock yet. Redo the flash from start to finish, try another USB cable or port if it stalls, and lock only once the phone boots cleanly.
What does “can’t be checked for corruption” actually mean?
It means Verified Boot is switched off because the bootloader accepts any software. Every time an Android phone starts, the bootloader checks that the system it’s about to load is signed by a trusted key. When you unlock the bootloader (the step needed to root a phone or install a custom ROM), that check stops protecting you, so Android shows a warning instead.
Google’s Verified Boot documentation sorts devices into colour states. Android Authority reported the original wording back in 2015, which is the version in the search box above:
| State | What you see | What it means | Can you keep using the phone? |
|---|---|---|---|
| Green | No warning | Locked bootloader, maker’s signed software | Yes, this is normal |
| Yellow | “Your device is loading a different operating system” | Locked bootloader, but running an OS signed with your own key (for example a custom OS that supports relocking) | Yes |
| Orange | “Your device software can’t be checked for corruption. Please lock the bootloader” (older) or “The bootloader is unlocked and software integrity cannot be guaranteed” (newer) | Unlocked bootloader | Yes, it boots after about 10 seconds |
| Red | “Your device is corrupt. It can’t be trusted and may not work properly” | System files fail the integrity check | Maybe; you must press power within 30 seconds or it shuts down |
| Red | “No valid operating system could be found” | Nothing bootable is installed | No, it powers off |
The newer orange screen adds two lines worth taking seriously: any data on the phone “might be available to attackers,” and you shouldn’t store sensitive data on it. An unlocked phone that’s lost or stolen is easier to tamper with.
Should you fix it, or ignore it?
It depends on one question: did you, or someone you trust, unlock the bootloader on purpose?
- Yes, you unlocked it to root or install a ROM. You can leave it. The message is the price of an unlocked bootloader, and Google’s Android Help page on operating system safety says you can keep using the device, with the risk that it may not work properly and your data is more exposed.
- No, it just appeared, or you bought the phone second-hand like this. Treat it as a problem. Google’s advice for that case is to contact support (Pixel) or the phone’s manufacturer. A Hovatek article on orange state warnings makes the same point more bluntly: if you didn’t authorise the unlock, unknown software could be on the phone, so don’t use it for banking or anything private until it’s restored to official firmware.
How to remove the warning by relocking the bootloader
The fix is two steps: restore official software, then lock. Do them in that order. Locking while modified or half-installed software is on the phone can leave it unable to boot, because the bootloader will then refuse anything that isn’t signed.
- Back up first. Locking resets the phone. Android’s bootloader locking documentation says fastboot flashing lock resets the device, and Google’s factory image page warns that installing a factory image erases all data. Save photos, chats and any authenticator codes before you start.
- Put the official firmware back. On a Pixel, the easiest route is the Android Flash Tool, which runs in Chrome or Edge 79 and newer and supports Pixel 2 and later. Turn on Settings > System > Developer options > USB debugging (tap Settings > About phone > Build number seven times to reveal Developer options), open flash.android.com, choose your device and a public build, and click Install. On other brands, use the maker’s own firmware tool or service centre.
- Check that the phone boots normally on the official build. If you see “Your device is corrupt” or it sticks on the logo, the flash didn’t finish. Redo it before going further.
- Boot into bootloader (fastboot) mode, connect to a computer with Android platform-tools, and run fastboot flashing lock.
- Confirm on the phone. Use the volume keys to move from “Don’t lock” to the lock option and press power. The confirmation screen closes and cancels if you don’t respond within 30 seconds.
- Let it reset and set it up again. With a locked bootloader and Google-signed software, the phone is back in the green state and the warning is gone.
Custom OS users have one exception. A few projects, GrapheneOS for example, are built to be relocked with their own signing key, and their installers lock the bootloader as the last step. If your ROM’s instructions don’t explicitly say relocking is supported, don’t lock it.
If your phone runs official software and you only wanted to fix a broken update, you don’t need to unlock anything. Google’s full OTA images restore factory firmware through recovery “without the need to wipe the device or unlock the bootloader.”
Not on a Pixel and just want a clean start once the firmware is official? The steps in our guide on how to factory reset an Android tablet work the same way on most Android phones.
Can you hide the message and keep the bootloader unlocked?
On Pixel and most big-brand phones, no. The warning is drawn by the bootloader itself, which you can’t edit without the maker’s signing keys. On some MediaTek and Unisoc phones, people patch boot components (the LK or U-Boot image) to hide it, as Hovatek describes. That only hides the text; the phone is exactly as unprotected as before, and a bad patch can stop it from booting. For almost everyone, leaving the ten-second screen alone is the smarter choice.
Frequently asked questions
Will my phone still work with this warning?
Yes. The orange warning closes by itself after about ten seconds, or when you press the power button, and Android then boots as normal. It returns on every restart for as long as the bootloader stays unlocked.
Does locking the bootloader erase my phone?
Yes. Android’s documentation says running fastboot flashing lock resets the device, so back up photos, chats and 2FA codes first.
Can I hide the message without locking the bootloader?
Not on most phones. Some MediaTek and Unisoc devices can be patched to hide it, but that means editing boot firmware, which can brick the phone and leaves the security problem in place.
What does g.co/ABH mean on the warning screen?
It’s Google’s short link to an Android Help page about operating system safety. It tells you to restore the original software if you changed it on purpose, or to contact the maker if you didn’t.
Is this the same as “Your device is corrupt”?
No. “Can’t be checked for corruption” only means the bootloader is unlocked. “Your device is corrupt” is the red warning, shown when Android finds the system files damaged or altered.
Sources
- Android Open Source Project: Verified Boot boot flow
- Android Open Source Project: Locking and unlocking the bootloader
- Android Help: Understand warning about operating system safety
- Android Open Source Project: Android Flash Tool
- Google: Factory images for Nexus and Pixel devices
- /e/OS community: Nexus 5X boot warning thread
- GrapheneOS forum: Can’t lock the bootloader
Featured image: RaBiTeC / Wikimedia Commons
