Confirm what now!?Can you please confirm that you don't need to do the vbmeta thing in order to boot?
This guide here seems to indicate that it's not possible to use a modified boot image unless you also disable boot image verification: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/
I dunno. Maybe it's something affecting the betas only?
Thanks for the answer! The upgrade via OTA was successful.In the entire time I have owned my Pixel 4a I have never once been offered an OTA. I have no idea why.
I used sideload OTA after reading warnings about "dirty flashing", which I think is what happens when you install the factory image without -w.
If you are offered the OTA and Google sends you the full OTA then it should be fine to install via settings. You'll lose root but you can get it back again afterwards (or possibly do the after update but before reboot "patch other slot" from Magisk).
If you get an incremental OTA it'll fail to apply unless you temporarily or permanently unroot.
My last phone (Mi A2 Lite) always got incremental updates so I'd temporarily unroot, install the OTA and then root the other slot before rebooting.
Can you list the actual steps you took for success?Thanks for the answer! The upgrade via OTA was successful.
There were some problems when rerooting though: after flashbooting the patched Magisk image, phone was in a bootloop. Had to flashboot original boot.img, uninstall Magisk app, flashboot patched boot.img again, and then it was fine.
Had to reinstall all Magisk modules too, but now it works.
apply OTA update via system settings -> power off -> enter fastboot mode -> fastboot boot flash boot magisk_patched.img -> reboot -> here is when bootloop started happening (couldn't get past lock screen without the phone restarting) -> power off -> enter fastboot mode -> fastboot boot flash boot.img -> reboot -> uninstall Magisk app -> power off -> enter fastboot mode -> fastboot boot flash magisk_patched.img -> reboot -> install Magisk app
Flashing the patched.img is the same as magisk install direct.. the latter requires root - which I don't have for some reason.
Still waiting myself, but ready to proceed. Any thoughts or issues w/ Android 12 on the 4a?Flashing the patched.img is the same as magisk install direct.. the latter requires root - which I don't have for some reason.
I'm now on a clean install of A12, flashed patched boot img, Magisk detects that its Installed but nothing detects root except Magisk Manager, where I can do a direct install...
Edit: Weird, I had to have the manager app uninstalled first. So for A12 my steps for successful root were:
1. Create patched boot.img using Magisk 23
2. Uninstall Magisk Manager + Magisk related stuff (Lsposed etc)
3. Flash A12, boot into A12 and enable usb debugging
4. Fastboot flash boot patched_boot.img
5. Boot and install Magisk Manager.
I missed the part in your 5 steps where you did a full wipe. I thought uninstalling Magisk and then reflashing afterwards did the trick. That's a shameIt's working smooth.. I'm probably behind in the 'hide root' game, but still using Magisk 23, USNP + Magisk Props. Lets me pass safteynet. Just spent an hour getting it configured, apps restored, accounts setup again etc. Google really sucks at restoring your data - I even have a Google One subscription and it only restored 1/4 of my text messages. Good thing I use a 3rd party backup app. Apple definitely has Google beat when it comes to getting a new device or upgrading OS versions.
Added for clarity. I'd hazard a guess that doing the OTA sideload will have better success rate.. I always just do full flash without -w by default and didn't think about doing differently when going from 11 to 12.
What version of Magisk and the Magisk app do you have installed (you could simply post a screenshot of the main window of the app)? Lately there's been some reports of similar issues where users have had mismatching versions installed...
That was exactly your issue... You have the Canary installed (build 23011), that doesn't have MagiskHide. But, you have the stable app (build 23000). Mismatch.
USNF v2.2.0 is currently available as a paid pre-release on @kdrag0n's Patreon. It should soon be released for free though... The v2.1.1 release won't work on the Magisk Canary because of incompatibilities between Riru and Zygisk.
Depends on a bunch of things...
adb reboot bootloader
fastboot erase boot
fastboot flash boot magisk_patched_boot-sunfish-rq2a.210405.005.img
adb reboot bootloader
fastboot erase boot
fastboot flash boot magisk_patched_boot-sunfish-rq3a.210705.001.img