Strictly enforced veirfied boots in Android 7.0 Nougat won't let phone boot if software is corrupt

Google is tightening security in Android 7.0 by strictly enforcing verified boot. This means if a device with locked bootloader has malware or corrupt data in the boot image or a verified partition, it will either start in limited use mode or not start at all.

Enforcing verified boot will prevent viruses and malware from taking advantage of the corrupt software. This will also make it harder to root or install custom ROMs on devices, and to create custom software as well.

Besides causing problems for the loading of custom firmware, Google says “Such strict checking, though, means that non-malicious data corruption, which previously would be less visible, could now start affecting process functionality more.”

However, Devices with unlocked bootloaders will not be affected by the implementation of strictly enforced verified boot.

This is a step above the boot verification process implemented in Marshmallow, which warned users of corrupt boot image, but allowed them to boot up their device. 

Via

Kaiser Bey

Kaiser is a tech enthusiast who likes to write, read and talk about tech. He dreams of going to Mars and never come back. We hope that you find his posts on AndroGuider helpful and informative