“Device Is Corrupt. It Can't Be Trusted” on Android — What It Means
The Android boot warning “Device is corrupt. It can't be trusted” is an integrity verification message. Learn what it means, what not to assume, and what to do next.
Message shown
“Device is corrupt. It can't be trusted”
Android's verified-boot process could not confirm that the software starting on the phone matches the expected trusted system image.
What it means
This is an integrity and boot-verification state, not a diagnosis that the phone is infected or malicious. It can follow an interrupted update, damaged system files, an unlocked bootloader, a custom operating system, or a hardware/storage problem.
The exact behavior depends on the device. Some phones continue after a warning, while others stop at the boot screen or offer recovery options. Avoid changing recovery settings until you know whether the data is backed up.
What to do
1. Take a photo of the full warning and note what changed immediately before it appeared, such as an update, repair, or bootloader change.
2. If the phone starts, back up important photos and files before trying repairs.
3. Restart once and follow only the recovery instructions supplied by the phone manufacturer or carrier for your exact model.
4. If the warning persists or the phone cannot boot, contact the manufacturer or a qualified repair provider; they may need to reinstall the official system software.
Keep in mind
Do not interpret the warning alone as proof of malware or deliberate tampering.
Do not wipe the phone, unlock the bootloader, or flash an image from an unknown site before checking backup and manufacturer instructions.
A factory reset or system reinstall can erase local data, so ask about data recovery first if the files are not backed up.
Frequently asked questions
Does this warning mean my Android phone has a virus?
No. It means verified boot could not confirm the expected system software. The warning alone does not establish infection or malicious activity.
What can cause the device-corrupt warning?
Possible causes include an interrupted update, damaged system files, an unlocked bootloader, a custom system image, or a storage or hardware problem.
Will a factory reset fix it?
Sometimes a reset is part of a manufacturer recovery process, but it is not a universal first step and can erase local data. Follow the exact instructions for your model.
Can I keep using the phone if it boots past the warning?
Back up important data first and arrange support if the warning repeats. A phone that boots is not proof that the underlying verification issue has been resolved.