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.

Android's previous OS, Marshmallow, had an older version of boot verification program. But now, if a device has a corrupt boot image or verified partition, the phone will not boot at all or will boot only in limited capacity, explained Sami Tolvanen, Google software engineer, on the Android Developers Blog.

As a way to counter this inconvenience, Google developers have introduced additional code that cuts down on data corruption so this issue surfaces less frequency. The post refers to the technique, which allows the OS to recover from corrupted blocks of code, as “interleaving.”