Updates Android N won't boot with Malware - Strictly Enforced Verified Boot

Not open for further replies.


Staff member
Jan 8, 2011
Android Developers Blog: Strictly Enforced Verified Boot with Error Correction | Android Developers Blog

"Android uses multiple layers of protection to keep users safe. One of these layers is verified boot, which improves security by using cryptographic integrity checking to detect changes to the operating system. Android has alerted about system integrity since Marshmallow, but starting with devices first shipping with Android 7.0, we require verified boot to be strictly enforcing. This means that a device with a corrupt boot image or verified partition will not boot or will boot in a limited capacity with user consent. Such strict checking, though, means that non-malicious data corruption, which previously would be less visible, could now start affecting process functionality more."​

In other words:

"A system integrity feature that prohibits Android mobile devices from booting when the presence of malware is suspected will now be strictly enforced in version 7.0 (Nougat). Unfortunately, the function is so sensitive, it also prevents perfectly legitimate boot attempts when a harmless, non-malicious data corruption surfaces during the start-up process."​

Via scmagazine


Level 85
Mar 15, 2011
Nice feature, for sure attacks will decrease the risk of Android however is not yet the so called 'primary causes'.

The issues are came from common ones like in Play Store malicious programs which should tighten more up.
Not open for further replies.