This is how Verified Boot warnings work in Android 6.0 Marshmallow

This is how Verified Boot warnings work in Android 6.0 Marshmallow
Verified Boot has been a part of Android since version 4.4 KitKat, and when it was first introduced it worried the mod community that it would kill the vibrant Android modding scene. That never happened of course (though Xposed framework has become more popular than custom ROMs for many), but it looks like Google is making Verified Boot a bit more aggressive than it has ever been before.

Ron Amadeo posted a picture of what happens when you unlock the bootloader on a new Nexus device (below). A new warning will show when you boot up your device that says, "Your device software can't be checked for corruption. Please lock your bootloader." Then it also has a link to a Google support page. 

On that page, it details three levels of warning that you could see:

  • Yellow warning: "Your device has loaded a different operating system."
  • Orange warning: "Your device software can't be checked for corruption. Please lock your bootloader."
  • Red warning: "Your device is corrupt. It can't be trusted and may not work properly."

The orange warning appears to be the standard message for those who have unlocked their device, but haven't modified anything. From the descriptions on the support page, it sounds the yellow warning would be triggered if you've installed a custom ROM. Then, the red warning is triggered when "The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks."

In each case, the warning should disappear after 10 seconds and regular boot-up will continue. If the warning doesn't disappear and you want to ignore it, you can press the power button once to continue booting. Or, if you think something really is wrong, you can interrupt the boot and turn off your device by holding the power button. Google then suggests contacting the device manufacturer to restore your device. 

What do you think? Are these warnings too much or right on track?

This is how Verified Boot warnings work in Android 6.0 Marshmallow

FEATURED VIDEO

6 Comments

1. ruwie

Posts: 103; Member since: Sep 25, 2014

I hate this interruption. Lol

2. combatmedic870

Posts: 983; Member since: Sep 02, 2015

I think it's a little too much. This is a developer phone...95% of the people that buy this phone are going to unlock it's bootloader. You kind of have to go out of your way to buy a nexus 5x or 6p, and have the money to pay outright for it at that.

4. sprockkets

Posts: 1612; Member since: Jan 16, 2012

Maybe...but newer android phones now require this, in that the /system partition can be verified for integrity. Obviously some couldn't care less, but it does remind you of what you are losing by going non stock.

3. zeeBomb

Posts: 2318; Member since: Aug 14, 2014

I'm 2gud2getredwarning

5. NULUSIOS

Posts: 18; Member since: Jun 18, 2015

I think it is ok. You can "suffer" this if you choose to put a custom ROM, it's not serious (how many times you reboot?). On the other hand I hate KNOX triggers and such. It's my device and I can choose to do whatever with it.

6. superguy

Posts: 428; Member since: Jul 15, 2011

So fine, make it a one time warning and call it good. We don't need to be spammed by it every time we boot the phone.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.