[Guide] Flash Magisk on Android 12

[V0latyle]

I would like to recognize @ipdev for finding this:

To add to V0latyle's post.

Pixel 4a [sunfish] has no issue updating and installing Magisk on Android 12.

The issue starts with Pixel 4a (5G) [bramble].
This is also the first Pixel using Boot Header v3.
Boot image header, version 3 - source.android - Link
Vendor boot header - source.android - Link

The 3, 3a, and 4 series along with 4a are using header v2.

4a (5G), 5 and 5a are using header v3.

Just downloaded and checked.
6 and 6 Pro are using header v4.

I am not sure if that is the problem but, it is quite a distinguishing line between Pixels that have this issue with Magisk and those that do not on Android 12.

After a little more testing on my 5 [redfin], I will open an issue on GitHub.
Magisk - GitHub - Issues - Link

Cheers all.

We still don't know if this has something to do with our issue, but there's a huge chance it does.

 

[elong7681]

I would like to recognize @ipdev for finding this:

We still don't know if this has something to do with our issue, but there's a huge chance it does.

You had stated earlier that you can disable rollback protection, do you think it would be possible to go from stable a12 back to a12 beta 5, flash magisk_patched.img and then update via OTA sideload and keep root without a wipe?

 

[V0latyle]

You had stated earlier that you can disable rollback protection, do you think it would be possible to go from stable a12 back to a12 beta 5, flash magisk_patched.img and then update via OTA sideload and keep root without a wipe?

I don't know the command to disable rollback protection. I don't know if it's actually the problem here.

Yes, you could dirty flash beta 5 over stable, then upgrade via OTA sideload and keep root.

 

[elong7681]

I don't know the command to disable rollback protection. I don't know if it's actually the problem here.

Yes, you could dirty flash beta 5 over stable, then upgrade via OTA sideload and keep root.

Ok tks

 

[elong7681]

I don't know the command to disable rollback protection. I don't know if it's actually the problem here.

Yes, you could dirty flash beta 5 over stable, then upgrade via OTA sideload and keep root.

I found this https://android.googlesource.com/platform/external/avb/+/master/README.md about AVB 2.0 and rollback protection being included together. There might also be something in this link that may help us with the wipe data for permanent root.

 

[V0latyle]

So, here's what we have been doing wrong, according to @Anonshe .

When we update, we must disable verity and verification prior to booting system. Update method shoould not matter.

If verity and verification are already disabled, you should be able to reflash /vbmeta as long as you don't boot into system.

 

[Homeboy76]

@Anonshe posted ths method in the Pixel 6 Pro thread. Does this work for the Pixel 4a 5(G), Pixel 5 or the Pixel 5a?

 

[Anonshe]

@Anonshe posted ths method in the Pixel 6 Pro thread. Does this work for the Pixel 4a 5(G), Pixel 5 or the Pixel 5a?

Just updated my Pixel 5 to the November Sec Patch without any data loss. Since I'd disabled vbmeta before, steps were simple:
- Used Payload Dumper to extract the boot and vbmeta images. Patched the former.
- Rebooted to Recovery
- Sideloaded the OTA package
- Reboot to bootloader from the recovery menu

fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img

fastboot boot magisk_patched.img

After it booted up, opened Magisk Manager, installed via Direct Install. All works fine.

 

[V0latyle]

Just updated my Pixel 5 to the November Sec Patch without any data loss. Since I'd disabled vbmeta before, steps were simple:
- Used Payload Dumper to extract the boot and vbmeta images. Patched the former.
- Rebooted to Recovery
- Sideloaded the OTA package
- Reboot to bootloader from the recovery menu

fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img

fastboot boot magisk_patched.img

After it booted up, opened Magisk Manager, installed via Direct Install. All works fine.

I did the same, except I extracted the images from the factory zip.

I successfully did both OTA sideload and dirty factory flash with no issues.

Oddly, I'm still seeing a software update available...

 

[prgopala]

Just updated my Pixel 5 to the November Sec Patch without any data loss. Since I'd disabled vbmeta before, steps were simple:
- Used Payload Dumper to extract the boot and vbmeta images. Patched the former.
- Rebooted to Recovery
- Sideloaded the OTA package
- Reboot to bootloader from the recovery menu

fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img

fastboot boot magisk_patched.img

After it booted up, opened Magisk Manager, installed via Direct Install. All works fine.

Assume this only works where you have wiped and clean installed android 12 for the first time.
I had updated from Android 11 -> Android beta 12.5 -> Android 12 and had those 'data corrupt' warnings. I have not wiped my phone yet and was using temp root by booting the magisk boot image.

I followed the above steps with the Nov security update and alas the 'data corrupt' warnings still pop up.
So i think a wipe is required at some point.

 

[Homeboy76]

Just updated my Pixel 5 to the November Sec Patch without any data loss. Since I'd disabled vbmeta before, steps were simple:
- Used Payload Dumper to extract the boot and vbmeta images. Patched the former.
- Rebooted to Recovery
- Sideloaded the OTA package
- Reboot to bootloader from the recovery menu

fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img

fastboot boot magisk_patched.img

After it booted up, opened Magisk Manager, installed via Direct Install. All works fine.

Nevermind, I found the answer I needed.

 

[V0latyle]

Assume this only works where you have wiped and clean installed android 12 for the first time.
I had updated from Android 11 -> Android beta 12.5 -> Android 12 and had those 'data corrupt' warnings. I have not wiped my phone yet and was using temp root by booting the magisk boot image.

I followed the above steps with the Nov security update and alas the 'data corrupt' warnings still pop up.
So i think a wipe is required at some point.

Yes - if boot verification was not disabled the last time Android System was running, a data wipe is required.

 

[State.of.mind]

Are you all able to get the Magisk repo to load on the Canary build? Also, does the magisk hide function no longer work?

 

[V0latyle]

Are you all able to get the Magisk repo to load on the Canary build? Also, does the magisk hide function no longer work?

MagiskHide has been deprecated for DenyList on Magisk 23010+.

 

[State.of.mind]

MagiskHide has been deprecated for DenyList on Magisk 23010+.

Thanks, and I'm assuming that older versions of Magisk are not compatible with Android 12

 

[V0latyle]

Thanks, and I'm assuming that older versions of Magisk are not compatible with Android 12

Not true, I'm using 23001 on my Pixel 5 with MagiskHide, Riru and Universal SafetyNet Fix 2.1.1 for Safetynet pass.

23010 is the first build that "officially" supports Android 12, though.

Also please refer to @topjohnwu 's State of Magisk. He details some of the changes that are happening and why. This includes the module repo.

 

[State.of.mind]

Not true, I'm using 23001 on my Pixel 5 with MagiskHide, Riru and Universal SafetyNet Fix 2.1.1 for Safetynet pass.

23010 is the first build that "officially" supports Android 12, though.

Also please refer to @topjohnwu 's State of Magisk. He details some of the changes that are happening and why. This includes the module repo.

Thanks this is great info. I'm on Magisk 23012. If I want to downgrade to 23001 is it as simple as flashing the patched boot image or would I have to uninstall Magisk?

 

[V0latyle]

Thanks this is great info. I'm on Magisk 23012. If I want to downgrade to 23001 is it as simple as flashing the patched boot image or would I have to uninstall Magisk?

I would recommend restoring the boot image (do this in Magisk) then a complete uninstall (also do this in Magisk); only then should you install 23001. It's not as simple as the boot image and the app.

 

[State.of.mind]

I would recommend restoring the boot image (do this in Magisk) then a complete uninstall (also do this in Magisk); only then should you install 23001. It's not as simple as the boot image and the app.

Thanks. Final question.. How did you find the APK for 23001? The APK I'm using keeps defaulting to 23012

 

[V0latyle]

Thanks. Final question.. How did you find the APK for 23001? The APK I'm using keeps defaulting to 23012

It's not easy, you basically have to look at the canary channel commits, and they're all named "app-debug"

Magisk 23001