Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

paa79594

Well-known member
Nov 9, 2009
271
4
0
So I got this message after a random reboot (I'm getting them every other day now):

Your device is corrupt. It can't be trusted and may not work properly." (Red)

After looking it up, I get to this page: https://support.google.com/nexus/answer/6185381?hl=en Which really doesn't help me at all. I've never rooted, or done any of that business. The ONE thing that I did do was enable the System UI Tuner setting. So, I turned that off, and powered off the phone. Upon boot the message returned. Does anyone know what I should do? Google didn't really help, they told me to flash the stock image. Don't I have the stock image already?
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

Did the article suggestions (copied below) work?

Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.

If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

So I got this message after a random reboot (I'm getting them every other day now):

Your device is corrupt. It can't be trusted and may not work properly." (Red)

After looking it up, I get to this page:Which really doesn't help me at all. I've never rooted, or done any of that business. The ONE thing that I did do was enable the System UI Tuner setting. So, I turned that off, and powered off the phone. Upon boot the message returned. Does anyone know what I should do? Google didn't really help, they told me to flash the stock image. Don't I have the stock image already?

Check if you have a unlocked bootloader
Check if you have enabled developer mode, some of the settings there might trigger the screen you are seeing
There is also a slight chance that one of the img file was corrupted due to whatever reason, but hitting power key in that screen should easily get you pass it with no problem.
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

So basically I can ignore the message? I think I did enable developer mode a week back or so.
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

So basically I can ignore the message? I think I did enable developer mode a week back or so.

I have enabled Developer Mode on every Nexus device I have owned, including the 6P, and have never seen that message during boot. I think you have something else going on.
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

I have enabled Developer Mode on every Nexus device I have owned, including the 6P, and have never seen that message during boot. I think you have something else going on.

That message is new to Marshmallow.

The suggestion to flash the factory image again, should fix the issue. Its possible you got some malware, which caused your reboot. Flashing the stock images should fix that.
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

That message is new to Marshmallow.

The suggestion to flash the factory image again, should fix the issue. Its possible you got some malware, which caused your reboot. Flashing the stock images should fix that.

And that's fine, but I have Marshmallow on my current Nexus 6p, I had it on my previous Nexus 6, it is on my Nexus 7 2013 LTE and also on my wife's Nexus 5. All have Developer Mode enabled and none display that error on boot.
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

Because its not developer mode that makes the message display.
 
Re: Got this at boot: Your device is corrupt. It can't be trusted and may not work properly." (Red)

Because its not developer mode that makes the message display.

Yes, I understand that. I jumped in only because it was suggested earlier in the thread that developer mode was the cause and I was pointing out that that is most assuredly NOT the case.
 

Trending Posts

Members online

Forum statistics

Threads
954,042
Messages
6,960,346
Members
3,162,908
Latest member
suranjanpaulmanik