Bubba The Hack said:

Pardon me, but you've used that term a couple times. What does "no verity" mean?

Starting back with Android 4.4.4 KitKat, the Android kernel has been implemented with a security protocol known as dm-verity (device mapper verity), which performs a block mapping integrity check during each boot sequence. You will often here this called verified boot or secure boot. This feature is premised upon establishing a chain of trust beginning with the bootloader, all the way up to the Android system image. More recent implementations of dm-verity include AVB (Android Verified Boot) 1.0 & 2 0. The root key used by dm-verity is stored in the boot image ramdisk. As a consequence of using dm-verity, the system image can no longer be mounted read-write, since doing so will write to the superblock, thus invalidating the block-level hashes maintained by dm-verity. Consequently, on the majority of Android devices that are rooted and modified, dm-verity is triggered and causes boot failure. The solution is to modify the boot image ramdisk and disable dm-verity/AVB. By "no-verity," I am referring to a boot image in which this security feature has been disabled.