You can check your active slot with fastboot getvar current-slot .
When you install Magisk, it needs to integrate itself into the boot image to function correctly. However, Magisk's integration requires modifying the boot image, which can conflict with the verified boot process. To overcome this, Magisk patches the vbmeta region in the boot image. This patching process effectively tells the device to bypass the verified boot checks, allowing Magisk to modify the boot image without triggering any warnings or preventing the device from booting. patch vbmeta in boot image magisk
To boot successfully with a modified image, you often need to disable the Android Verified Boot (AVB) checks stored in Reboot to Fastboot : Connect your phone to your PC and run: adb reboot bootloader Flash the Patched Boot Image fastboot flash boot magisk_patched_[random_strings].img (Note: Use instead of if your device requires it) Flash VBMeta with Disable Flags You can check your active slot with fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img To overcome this, Magisk patches the vbmeta region
Recent devices (like the Pixel 6 and newer) have started moving the ramdisk to a separate init_boot partition. On these devices, you will patch the init_boot.img instead of the boot.img . An unpatched vbmeta often prevents an init_boot -patched device from booting. In this situation, you will need to run the same fastboot command on your vbmeta :
Cryptographic hashes of the boot, system, and vendor images. Specific boot flags (verification properties).
When you install Magisk, it alters the boot.img file. During the next startup, the bootloader compares the altered boot image against the original hashes stored in vbmeta . Because the hashes do not match, the verification fails, resulting in a or a "Device corrupted" warning. Prerequisites Before You Begin