[Android Software/Hacking General [Developers Only]] ipdev:
I have been waiting for the November update to test updating Android 12.

We will find out in a few days when it is released. ;)

Currently I think we have a good chance to update from the Android 12 October build to the November build without having to wipe data. :unsure:

As long as you disabled verity, verification and wiped data when initially updating to (or clean flash) Android 12.

I have mentioned before (in a different thread), I update using the full factory image and modify the flash-all script.

This is what I plan to try. 🙃

fastboot --disable-verity --disable-verification --skip-secondary --skip-reboot update image-redfin-NameOfUpdate.zip
fastboot reboot bootloader

The skip-reboot option will leave the device in fastboot_d so I add a reboot to bootloader.

If nothing else needs to be flashed after the update, I just fastboot reboot.

Long (still continuing) story short. :rolleyes:

Once Android 12 is installed, verity and verification are disabled and data is wiped.

You can flash the boot partition as much as you want on Android 12.​

​

You can dirty-flash Android 12 again using the above fastboot command without having to wipe data again.​

The --skip-secondary is not needed, I just included it to speed up the flash a bit. ;)​

I still do not know what the trigger is for the corruption error. :(

---

As I mentioned in the post you quoted.

The corruption issue has to do with verifying the boot partition on Android 12.

Unless data is wiped after disabling verity and verification.

Since Magisk lives in boot, it unpacks, modifies, repacks and flashes the modified boot image to the boot partition.

It is not Magisk itself that triggers the corruption error, it is simply just a different boot image installed.

The same happens with a repacked (non modified) version of the stock boot image.

I used AIK to unpack and repack the stock boot image with no modification.​

Cheers. :cowboy:

PS.

@osm0sis

I know you are aware of this issue with Magisk but, it also affects AIK and probably AK3.

Basically anything that modifies the installed boot partition.

[ip@lost AIK-Linux]$ ./unpackimg.sh redfin-sp1a.210812.015-boot.img

Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: redfin-sp1a.210812.015-boot.img

Setting up work folders...

Image type: AOSP

Signature with "AVBv2" type detected.

Splitting image to "split_img/"...
ANDROID! magic found at: 0
BOARD_KERNEL_CMDLINE
BOARD_PAGE_SIZE 4096
BOARD_OS_VERSION 12.0.0
BOARD_OS_PATCH_LEVEL 2021-10
BOARD_HEADER_VERSION 3
BOARD_HEADER_SIZE 1580

Unpacking ramdisk (as root) to "ramdisk/"...

Compression used: lz4-l
4937 blocks

Done!
[ip@lost AIK-Linux]$ ./repackimg.sh --original --origsize

Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers

Repacking with original ramdisk...

Getting build information...
kernel = redfin-sp1a.210812.015-boot.img-kernel
ramdisk = redfin-sp1a.210812.015-boot.img-ramdisk.cpio.lz4
cmdline =
os_version = 12.0.0
os_patch_level = 2021-10
header_version = 3

Building image...

Using format: AOSP

Padding to original size...

Done!

Also the modified boot image can not boot into fastboot_d while failing verification.

We are droped back to bootloader or recovery's Rescue Party when verification fails.

As noted above, the only way to disable verity and verification includes wiping data. 🤬

PPS.

Quick note for those trying to following along. :)

fastboot_d is part of the boot image (not the bootloader) and is the boot mode used to flash critical partitions.

The successor to fastboot flashing unlock_critical​