[Essential Phone ROMs, Kernels, Recoveries, & Other] chaseadam:
boot.img from AOSP 12 fails to boot (AOSP 11 imgs (vendor, system) and AOSP 12 images). It also triggers the corruption message regardless of dm-verity state.

This message appears to remain present regardless of flashing until dm-verity is re-enabled. Attempts to go back to AOSP 11 (with boot.img from AOSP 11) still show the corruption message, but pressing "power" allows boot to continue.

Flashing AOSP 12 boot.img

➜ AOSP12 sudo fastboot flash boot_a boot.img
Sending 'boot_a' (26984 KB) OKAY [ 0.787s]
Writing 'boot_a' OKAY [ 0.166s]
Finished. Total time: 0.969s
➜ AOSP12 sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.050s

Results in a boot which looks good, then restarts before animation, then gives "corruption message". Pressing power to continue results in a "reboot" before animation.

I am able to boot into recovery and attempt to "re-enable" dm-verity, but the result is the same.

Recovery to AOSP after messing with boot.img AOSP 12:

may also be good to take a look at MuddyDog above

➜ AOSP11 sudo fastboot set_active a
Setting current slot to 'a' OKAY [ 0.037s]
Finished. Total time: 0.038s
➜ AOSP11 sudo fastboot flash boot_a boot.img
Sending 'boot_a' (25057 KB) OKAY [ 0.803s]
Writing 'boot_a' OKAY [ 1.008s]
Finished. Total time: 1.823s
➜ AOSP11 sudo fastboot flash vendor_a vendor.img
Sending 'vendor_a' (392296 KB) OKAY [ 12.198s]
Writing 'vendor_a' OKAY [ 8.251s]
Finished. Total time: 20.452s
➜ AOSP11 podman run --name mainnet-validator -it --rm -v /home/achasen/lighthouse/mainnet/validators:/root/.lighthouse/mainnet/validators:Z localhost/lighthouse:latest lighthouse --network mainnet validator --beacon-nodes http://m720t.827.chasen.name:5054
➜ AOSP11 sudo fastboot format userdata
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 26766167 4k blocks and 6692864 inodes
Filesystem UUID: 05fed42a-f361-4da8-a263-a365dea996ce
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (5197 KB) OKAY [ 0.241s]
Writing 'userdata' OKAY [ 0.051s]
Finished. Total time: 0.403s
➜ AOSP11 sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.150s
➜ AOSP11 adb root
restarting adbd as root
➜ AOSP11 adb shell
mata:/ # reboot "dm-verity enforcing"

I also get this concerning message from AOSP 11 when it reboots unexpectedly after a minute.

"Cannot load Android system. Your data may be corrupt."

After re-applying *all* images from AOSP11 and formatting user (step 5 in instructions), seems to be ok so far.

➜ AOSP11 sudo fastboot flash boot_a boot.img
[sudo] password for achasen:
Sending 'boot_a' (25057 KB) OKAY [ 0.851s]
Writing 'boot_a' OKAY [ 1.039s]
Finished. Total time: 1.902s
➜ AOSP11 sudo fastboot set_active a
Setting current slot to 'a' OKAY [ 0.031s]
Finished. Total time: 0.032s
➜ AOSP11 sudo fastboot flash vendor_a vendor.img
Sending 'vendor_a' (392296 KB) OKAY [ 11.732s]
Writing 'vendor_a' OKAY [ 8.029s]
Finished. Total time: 19.763s
➜ AOSP11 sudo fastboot flash system_a system.img
Sending sparse 'system_a' 1/4 (458752 KB) OKAY [ 13.818s]
Writing 'system_a' OKAY [ 17.390s]
Sending sparse 'system_a' 2/4 (458752 KB) OKAY [ 13.833s]
Writing 'system_a' OKAY [ 16.287s]
Sending sparse 'system_a' 3/4 (458752 KB) OKAY [ 14.096s]
Writing 'system_a' OKAY [ 14.392s]
Sending sparse 'system_a' 4/4 (494420 KB) OKAY [ 14.854s]
Writing 'system_a' OKAY [ 15.637s]
Finished. Total time: 120.332s
➜ AOSP11 sudo fastboot format userdata
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 26766167 4k blocks and 6692864 inodes
Filesystem UUID: 3efd1585-b4a1-42bc-a861-cf52ac13ccd3
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (5197 KB) OKAY [ 0.246s]
Writing 'userdata' OKAY [ 0.292s]
Finished. Total time: 0.672s
➜ AOSP11 sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.050s