This ZIP package is designed to be flashed via a custom recovery (like TWRP) to modify Android's boot image. Its purpose is to disable two specific security features: dm-verity and forced encryption.
It is entirely legal to modify your own device in most jurisdictions (provided you are not circumventing lawful access orders). However, a few points: Disable-Dm-Verity-ForceEncrypt-03.04.2020.zip
Modifying device software, especially at a fundamental level, comes with risks. Some of these include: This ZIP package is designed to be flashed
Even with this specialized zip, things can go wrong. Here are the most frequent problems and their solutions. Without that ZIP
Disable-Dm-Verity-ForceEncrypt-03.04.2020.zip
│
├── META-INF/
│ └── com/
│ └── google/
│ └── android/
│ ├── update-binary
│ └── updater-script
│
├── tools/
│ ├── magiskboot (binary – ARM64)
│ ├── awk / sed (busybox utilities)
│ └── fstools (custom binary for fstab patching)
│
├── patches/
│ ├── fstab_patch.sh
│ ├── verity_remove.sh
│ └── encryption_disable.sh
│
├── boot_repack.sh
├── disable_dmverity
├── disable_forceencrypt
└── README.txt
To understand the purpose of Disable-Dm-Verity-ForceEncrypt-03.04.2020.zip, you must first understand the two Android security features it targets.
If you were installing a ROM back then, your ritual looked exactly like this:
Without that ZIP? Step 6 was an infinite boot animation.