How to Fix Your Device Has Been Unlocked And Can’t Be Trusted

The message “Your Device Has Been Unlocked And Can’t Be Trusted” can look scary when it appears during startup. Many Android users see it after unlocking the bootloader, rooting the phone, installing a custom ROM, or flashing modified firmware. In most cases, it does not mean your phone is instantly broken. It means the device bootloader is unlocked, so Android cannot fully verify the software before booting.

Still, this warning should not be ignored. It affects device security, data safety, software integrity, warranty support, and sometimes the ability to use banking apps or official updates. The right fix depends on what caused the warning and whether your phone is running official or modified software.

What Does “Your Device Has Been Unlocked And Can’t Be Trusted” Mean?

This warning usually appears when an Android device is in an unlocked bootloader state. The bootloader is a low-level program that starts before Android loads. Its job is to check and launch the operating system.

Google’s Android documentation explains that when a device is unlocked, the bootloader shows a warning and may continue booting even if the operating system is not signed by the trusted root of the device. When a device is locked, the bootloader verifies that the software is properly signed before allowing it to boot.

In simple terms, your phone is saying:

“The bootloader is unlocked, so I cannot guarantee that the system software has not been changed.”

This often happens on phones from brands such as Motorola, Google Pixel, OnePlus, Xiaomi, Realme, Lenovo, and some Android tablets. The wording may vary, but similar messages include:

“Your device software can’t be checked for corruption.”

“The bootloader is unlocked and software integrity cannot be guaranteed.”

“Your device is corrupt. It can’t be trusted and may not work properly.”

Why This Warning Appears

The warning appears because the phone’s bootloader has been unlocked or the system partition has been modified. Android Verified Boot is designed to help protect the device by checking software integrity during startup. Android’s official bootloader documentation states that unlocking allows partitions to be reflashed, while locking is intended to help prevent attackers from installing modified system or boot images.

Common reasons include:

1. You unlocked the bootloader manually through Fastboot.
2. You rooted the device using Magisk or another root tool.
3. You installed a custom ROM.
4. You flashed custom recovery such as TWRP.
5. You installed unofficial firmware.
6. A repair shop or previous owner modified the device.
7. The device was tampered with before resale.

If you intentionally unlocked the bootloader, the warning is expected. If you did not unlock it yourself, treat the device carefully because someone else may have changed the software.

Is the Warning Dangerous?

The warning itself is not malware. It is a security notice. However, the reason behind it can matter a lot.

An unlocked bootloader reduces the protection Android normally provides during startup. In the unlocked state, verification errors are not treated the same way as they are on a locked device. Android Verified Boot documentation describes locked and unlocked modes, where locked mode treats verification issues as fatal, while unlocked mode allows booting with verification errors.

That means your device may still work, but it is less trusted from a security point of view.

You should be more concerned if:

• You bought the phone used and did not unlock it yourself.
• The phone started showing the warning suddenly.
• The phone is stuck in a boot loop.
• Banking apps, payment apps, or security apps stopped working.
• The device runs unknown or unofficial firmware.
• You see other warnings such as “Your device is corrupt.”

For everyday users, the safest fix is usually to return the phone to official stock firmware and lock the bootloader again.

How to Fix Your Device Has Been Unlocked And Can’t Be Trusted

Before you do anything, understand this important point: relocking the bootloader can erase your data and may brick the phone if the wrong firmware is installed. Android’s official bootloader documentation says devices should perform a factory data reset when unlocking, and locking the bootloader is also tied to resetting and securing the device state.

So do not rush. Follow the steps carefully.

Step 1: Back Up Your Data First

Start by backing up everything important. This includes photos, videos, contacts, WhatsApp chats, documents, downloads, app data, and anything stored locally.

Relocking the bootloader often causes a factory reset. Some brands wipe the device automatically. Others may fail to boot if the firmware is not correct.

Use Google Drive, Google Photos, a computer, or an external storage device. If the phone is already unstable, copy your most important files first.

Step 2: Check Whether the Phone Is Running Official Firmware

The warning can appear even when the phone works normally, but you need to know whether it is running official stock software or modified software.

Check these signs:

Go to Settings > About phone and look at the Android version, build number, and security patch level.

Look for custom ROM names such as LineageOS, Pixel Experience, Evolution X, crDroid, or unofficial builds.

Check whether Magisk, SuperSU, TWRP, or root-related apps are installed.

Restart the phone and see whether it shows custom recovery instead of stock recovery.

If the phone is running a custom ROM or rooted software, do not simply lock the bootloader. You may need to flash the correct official firmware first.

Step 3: Decide Whether You Actually Need to Remove the Warning

Some advanced users intentionally keep the bootloader unlocked because they use root, custom ROMs, kernel modifications, or development tools. In that case, the warning is normal.

You may not need to fix it if:

You unlocked the bootloader yourself.

You understand the security trade-off.

You are using a trusted custom ROM.

You need root access for development or customization.

You do not store sensitive data on the device.

However, for most normal users, especially those using banking apps, work accounts, mobile wallets, or private documents, a locked bootloader with official firmware is safer.

Step 4: Flash the Correct Official Stock Firmware

If the phone has modified software, the best fix is to restore official firmware. This step varies by brand.

For Google Pixel, users usually use the official Android Flash Tool or factory images.

For Motorola, users often need the correct stock firmware package for the exact model and region.

For Xiaomi, users may use Mi Flash Tool with official fastboot ROMs.

For Samsung, bootloader warnings work differently, and Odin firmware flashing may be required depending on the model.

For OnePlus and Realme, official firmware packages or recovery tools may be needed.

The key rule is simple: use firmware made for your exact model number, region, and variant. Flashing the wrong firmware can cause boot loops, network issues, or a hard brick.

Step 5: Relock the Bootloader Only After Stock Firmware Is Restored

Once the phone is back on official stock firmware, you can consider locking the bootloader. Android’s official documentation lists the Fastboot command for locking as:

fastboot flashing lock

The same Android documentation explains that devices intended for retail should be shipped in the locked state to help prevent attackers from compromising the device by installing a new system or boot image.

For some older devices, the command may be:

fastboot oem lock

But this depends on the manufacturer and Android version.

A typical process looks like this:

Turn off the phone.

Boot into Fastboot or bootloader mode.

Connect the phone to a computer.

Open a command window in the platform-tools folder.

Run fastboot devices to confirm the phone is detected.

Run the correct locking command for your device.

Confirm the warning on the phone screen.

Wait for the device to reset and reboot.

Again, only do this after confirming that the phone is running official, unmodified firmware.

Step 6: Factory Reset After Locking

After locking the bootloader, the phone may factory reset automatically. If it does not, you may still want to reset it manually for a clean start.

Go to Settings > System > Reset options > Erase all data, depending on your Android version.

This helps remove leftover data, app conflicts, root traces, or configuration problems from the previous modified state.

Step 7: Update Android and Security Patches

After the phone boots normally, check for updates.

Go to Settings > System > Software update and install any available Android updates or security patches.

This matters because Verified Boot and bootloader security work best when the device is running supported, up-to-date firmware. If the phone is too old and no longer receives updates, it may still work, but it will not be as secure as a currently supported model.

What If the Warning Still Appears After Relocking?

If “Your Device Has Been Unlocked And Can’t Be Trusted” still appears after you tried to fix it, one of these problems may be present:

The bootloader did not actually lock.

The firmware is not fully stock.

The wrong firmware was flashed.

A partition is still modified.

The device has rollback protection issues.

The phone has a damaged or corrupted boot partition.

In this case, boot into Fastboot and check the device state. Depending on the device, commands such as fastboot oem device-info or similar manufacturer-specific commands may show whether the bootloader is locked or unlocked.

If the device says locked but still shows integrity warnings, you may need to reflash the full stock firmware package, including boot, vendor, vbmeta, recovery, and system partitions.

Can You Remove the Warning Without Locking the Bootloader?

Usually, you should not try to remove the warning by editing logo files, boot images, or system partitions. Some online guides suggest hiding the warning screen, but that does not fix the actual security state.

Removing the message cosmetically is risky because it can:

Hide a real security warning.

Break boot files.

Cause boot loops.

Make resale misleading.

Create more problems during updates.

The correct fix is not to hide the warning. The correct fix is to restore trusted software and lock the bootloader safely.

What If You Bought a Used Phone With This Warning?

If you bought a used phone and see this message, take it seriously.

Ask the seller whether the bootloader was unlocked, whether the phone was rooted, and whether custom firmware was installed. If the seller cannot explain it, be careful.

A used phone with an unlocked bootloader may be harmless, but it may also have modified software. You should not store banking details, passwords, work files, or private data on it until you restore official firmware and lock the bootloader.

If the phone was sold as “new” or “factory sealed” but shows this warning, contact the seller immediately.

Will This Warning Affect Banking Apps?

Yes, it can. Some banking apps, payment apps, streaming apps, and corporate security tools check device integrity. If the bootloader is unlocked or the device is rooted, these apps may refuse to run.

Even if the apps open, the device may not meet the security level required for sensitive use. That is why users who rely on mobile banking or work profiles should generally avoid using an unlocked bootloader unless they fully understand the risks.

Can a Factory Reset Fix the Warning?

A factory reset alone usually does not fix this warning.

A factory reset deletes user data, apps, and settings. It does not automatically lock the bootloader. If the bootloader remains unlocked, the warning can continue appearing after every restart.

To fix the actual warning, you usually need to restore stock firmware and relock the bootloader.

Common Mistakes to Avoid

Do not lock the bootloader while running a custom ROM.

Do not flash firmware from a different model.

Do not ignore the warning on a used phone.

Do not remove the warning image without fixing the bootloader state.

Do not rely on random files from unknown forums.

Do not skip backups.

Do not assume every Android brand uses the same Fastboot commands.

These mistakes can turn a simple warning into a serious boot problem.

Best Practice: Match the Fix to Your Situation

If you unlocked the phone for root or custom ROM use, the warning is expected. You can continue using the device, but avoid storing highly sensitive data unless you understand the security trade-off.

If you want a normal, secure Android experience, return to official firmware and lock the bootloader.

If you bought the phone used and did not authorize the unlock, restore it before trusting it.

If the phone is stuck on the warning screen or boot looping, flash the correct stock firmware or get help from an authorized repair center.

FAQs About Your Device Has Been Unlocked And Can’t Be Trusted

Why does my phone say “Your Device Has Been Unlocked And Can’t Be Trusted”?

It says this because the bootloader is unlocked or the phone’s software has been modified. Android cannot fully verify the operating system before booting.

Is my phone hacked if I see this message?

Not always. If you unlocked the bootloader yourself, it is expected. If you did not unlock it, the phone may have been modified by someone else, so you should restore official firmware before trusting it.

Can I fix it without losing data?

Usually, no. Locking or unlocking the bootloader often involves a factory reset. Back up your data before attempting any fix.

Is it safe to lock the bootloader?

It is safe only if the phone is running official stock firmware for the exact device model. Locking the bootloader on modified firmware can cause a boot loop or brick the phone.

Does rooting cause this warning?

Rooting often requires bootloader unlocking, so yes, rooted devices commonly show this warning at startup.

Can I still use the phone normally?

Yes, many phones still boot and work normally. However, security is reduced, and some apps may not work properly.

Conclusion

The warning “Your Device Has Been Unlocked And Can’t Be Trusted” means your Android phone is in a less secure boot state, usually because the bootloader has been unlocked. It does not always mean the phone is broken, but it does mean Android cannot fully guarantee the integrity of the software during startup.

The safest fix is to back up your data, restore the correct official stock firmware, and relock the bootloader only when you are sure the software is clean and compatible. If you intentionally use root or custom ROMs, the warning may be normal, but you should understand the risks before storing sensitive information on the device.