yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I updated without removing Magisk or any modules. I'm running Magisk Canary 23015, with MagiskHide Props Config v6.1.2, Systemless Hosts v1.0, and Universal SafetyNet Fix v2.2.0.

Here is exactly how I updated:

Download factory zip

Extract boot.img from update image, copy boot.img to phone

Patch boot.img in Magisk

Copy patched boot image back to PC

Reboot to bootloader

Update bootloader:

fastboot flash bootloader <bootloader.img>

Update radio:

fastboot flash radio --slot=all <radio.img>

Reboot to bootloader:

fastboot reboot bootloader

Apply update:

fastboot update --disable-verification --disable-verity --skip-reboot <image-redfin-buildnumber.zip>

When update completes, reboot to bootloader:

fastboot reboot bootloader

Boot patched boot image:

fastboot boot <patched boot.img>

Allow system to boot, open Magisk and use Direct Install to patch the boot image

Reboot, all is well.
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
Unfortunately that doesn't work for me. It is still getting stuck at the G logo with the loading bar and does not progress any further. I can use ADB on it if that is of any use.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Do you still have the stock boot image flashed? Try re-patching the boot image from the update zip. Make sure it's the right one.

You can also try booting the image instead of flashing it. If it boots successfully, just use Direct Install in Magisk.
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
I'll try repatching it but it won't boot off of the one I patched before.

Edit: Making another patched image still does not work. Stuck at the G and will not progress.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What version of Magisk are you using?

Do you still have the patched boot image from the November update?
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
Latest canary, I do have the one from November but it is for version 23000.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Hmm. What Magisk modules do you have installed? I don't think this would be the problem, but just for the sake of curiosity...

I assume you updated Magisk before you updated Android? Did you update the boot patch too?

See if you can boot the patched November image, check Magisk to see if you still have root.
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
The one I do remember was the Addon Features for Pixel module, but I tried uninstalling them while I was at the G logo using the magisk remove-modules command. All it did was reboot and end up at the same spot. When I update I re-patch the boot img so it usually is fine, but in this case it is not.

Edit: Booting from November caused a bootloop, told me my data was corrupt (but it is in fact not).
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
So to make sure I understand correctly, you can boot OK with the unpatched boot image, but the patched image doesn't complete boot? How long have you waited on the G logo to see if it's successful? Give it 5-10 minutes and see what happens.

The only other thing I can think of is removing Magisk and starting over, but doing so requires root (do NOT try to remove Magisk simply by uninstalling the app).
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
Yep, stock boot image works just fine but if I try to boot from the magisk one it gets suck at the G logo. I've waited probably 2-3 minutes for it to think about it but I guess I can try for longer.

Edit: I tried again but waited for much longer (its been about 7 minutes) and it is stuck at the logo still.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What happens when you try to boot the patched November image?

BTW, when I say "boot" I mean using fastboot boot <patched boot image>, not fastboot flash

The first temporarily boots the image via ADB, the second actually flashes it to the boot partition
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
Right, I understood what you meant.

It boot loops, doesn't get past the word Google before it gives me a menu saying that my phone data is corrupt. It could be that my patched img is from an earlier attempt that failed when on the November update.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Well...the only thing I can think of is try to dirty flash the November update again and use the November patched image.

Failing that, I think you're going to have to wipe /data and start over.
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
I was hoping there would still be a way, but oh well. I might wipe it but today is not that day.

Edit: November update doesn't work either it seems. I don't know what I did wrong but I guess I have to start over if I want root.
[Google Pixel 5 Guides, News, & Discussion] Darkeligos:
I just picked up the Pixel 6 with Android 12 installed. Do I just need to follow the Patch Boot Image steps? Or are there other steps I should take from a previous Android 11 root thread? Thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Follow the instructions in the OP.
[Google Pixel 5 Guides, News, & Discussion] k1984228:
If i disabled verity and verification, can i OTA Security Patch every month or i also need to update Security Patch by Android Flash Tool?
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Same question, for the arrival updates, simply do an installation via OTA or redo a method of op ?
[Google Pixel 5 Guides, News, & Discussion] kfhughes:
From the original post in this thread:

The OTA does not have a way to set the disable flags for vbmeta, so if you update via OTA, you will have to reflash vbmeta with the disable flags every time you update.
[Google Pixel 5 Guides, News, & Discussion] k1984228:
What's the OTA means?

OTA from A11 to A12 or

A12 monthly security updates?
[Google Pixel 5 Guides, News, & Discussion] Regys:
Just check only in Android Flash Tool, "Disable Verity" and "Disable Verification"

No need to uninstall Magisk or make a wipe ?
[Google Pixel 5 Guides, News, & Discussion] kfhughes:
It applies to both the A11->A12 and the A12 monthly security updates. The big difference is that for the A11->A12 OTA you also need to wipe data.
[Google Pixel 5 Guides, News, & Discussion] kfhughes:
I haven't used the flash tool so I'm not sure, since I sideload the OTA.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No. Simply dirty flash the update, making sure you disable verity and verification; once the update is complete, patch and flash the new boot image.

If you're rooted, I don't recommend using OTA sideload, simply because of the additional steps and files you'd need to download. The best way is to download and dirty flash the factory image.
[Google Pixel 5 Guides, News, & Discussion] kfhughes:
It's been a while since I use the factory image method. After "fastboot update image-xxxxx.zip", does the phone automatically reboot or does it stay in fastboot?
[Google Pixel 5 Guides, News, & Discussion] elong7681:
You must add fastboot --disable-verity --disable-verification --skip-reboot update image-redfin-xxxxxxxxxxxx.zip to keep it from booting and the flags disabled
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
When you update using the factory image, it reboots to system by default. This in of itself isn't a problem as long as you disable verity and verification while flashing the image. If you have patched the boot image beforehand and want to flash it, you can use --skip-reboot, in which case it will leave you in fastboot once the update finishes.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Yes, simply, it works !
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you try this!

Q: "If verity/verification are disabled, do I need to enable them now?"

A: No. The only thing you have to do is update to Magisk 23016.

Q: "Will enabling verity/verification wipe my data?"

A: No.

I will be updating the OP to reflect this.
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
Hey @V0latyle, I managed to get root again by running magisk --remove-modules a second time, and I think I have found the culprit. It seems like the Addon Features module is causing my issue of booting. Thank you for your time and assistance!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This thread is no longer relevant and will be closed. Please use this guide instead.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay, to make sure I'm understanding correctly....

When you first updated, did you flash the Android 12 factory image coming from the beta, or Android 11?

Which process did you follow before you got the system corrupt message? Where exactly did the message appear, was it in recovery?

When you flashed the system image the second time, did you wipe?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
To clarify, you did wipe?
[Google Pixel 5 Guides, News, & Discussion] creezalird:
yes i did, i was on protonaosp 11.60

So basically I copied 4 files into my platform-tools folder (flash-all.bat, bootloader, image, radio)

Then edited the flash-all.bat a little bit (highlighted blue below) based on your guide

PATH=%PATH%;"%SYSTEMROOT%\System32"

fastboot flash bootloader bootloader-bramble-b5-0.4-7617461.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-bramble-g7250-00147-210811-b-7631450.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot --disable-verity --disable-verification -w update image-bramble-sp1a.210812.015.zip

echo Press any key to exit...

pause >nul

exit

Then

adb reboot bootloader

flash-all

Wait, done. Follow the usual magisk patched setup

PS :

Pixel 4a 5(G) phone owners need to know for the initial upgrade (Android 11 to Android 12),

with above method by flashing the factory image with the disable flags, it flashes /vbmeta with the disable flags, so reflashing vbmeta is not necessary,

which means that they do not need the fastboot flash --disable-verity --disable-verification --slot-all vbmeta vbmeta.img additionally.

Thanks V0latyle for the heads up.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay, thank you
[Google Pixel 5 Guides, News, & Discussion] pappy97:
So to clarify, you have to wipe to root Android 12 and every month when there is an update, you'll have to wipe to get root?
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Thanks for confirming the wipe is necessary. :)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No.

Data wipe is only required if you're trying to flash the factory image AND are coming from a different version of Android.

Data wipe is NOT required with the OTA.

Data wipe is NOT required with the factory image if you're already on Android 12.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Only for the factory image. Wipe is not necessary for the OTA, nor is it necessary if you're coming from the 12 Beta.
[Google Pixel 5 Guides, News, & Discussion] rester555:
Agreed with @V0latyle... I only wiped since I was coming from A11... when it comes to monthly updates, I don't wipe and I hope we won't ever have to do it at that frequency. That would suck!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I wiped when I installed the 12 Beta 5, and I took the OTA today. I'll report in the discussion thread when I get home and attempt to re root.
[Google Pixel 5 Guides, News, & Discussion] rester555:
FYI @V0latyle... When I flashed the vbmeta boot image without --slot=all, powershell in windows only confirmed to me slot a was written. So that's what sparked me to use the --slot=all command. Not sure if this helps.

ALSO... my environment is Windows 11 with latest plaform tools and google USB drivers from google's repository...
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's really odd that we have to do this, but I guess it's better than being stuck in a bootloop or something.
[Google Pixel 5 Guides, News, & Discussion] rester555:
Agreed, there was a time when I was flashing patched magisk over and over from monthly updates on my pixel 2 xl and I remember getting a bootloop that returned me to fastboot... I stumbled upon another thread on XDA where they suggested --slot=all when it came to flashing the patched magisk boot so now I do that for both the magisk patched boot image and the disable flags.

But I am not sure if there is a downside to flashing to slot a and b for the disable flags and for magisk patched boot images.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
For vbmeta, it should make absolutely no difference at all.
[Google Pixel 5 Guides, News, & Discussion] pappy97:
Thanks. I followed the steps from the OP (did that fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img), but after flashing my magisk patched boot image, it would only boot to a device corrupt screen that gave me an option to try again (Which brought me back here) or factory reset. Any ideas? Thanks!!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Try

fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img

Then flash your patched boot image
[Google Pixel 5 Guides, News, & Discussion] pappy97:
Do you mean literally

(1)fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img

then (2) flash patched boot image

WITHOUT "fastboot reboot bootloader" in between steps 1 and 2?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's not really necessary but I've always done it after flashing a partition.
[Google Pixel 5 Guides, News, & Discussion] pappy97:
I'll try it without, thanks!
[Google Pixel 5 Guides, News, & Discussion] pappy97:
Followed these steps, still the same issue. I went ahead and double checked to make sure my patched boot image is the correct one, and it is. No matter what, I get to that Device Corrupt screen with the option to try again factory reset.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay. Before I give you more instructions I want to ensure I'm on the same page here, so please correct me if I'm wrong:

- You initially took the OTA update after using Magisk (what version of Android were you on previously?)

- You then downloaded the factory zip, then extracted and patched the boot image, but you got the "Unable to load/verify boot image" error

- You dirty flashed the factory image to get your phone working again

- You have tried reflashing vbmeta with both the disable flags and the slot=all flag but now get a device corrupt error

For now, I would say reflash vbmeta to both slots without the disable flags, and reflash the stock boot image. That should get you back to unrooted Android 12.
[Google Pixel 5 Guides, News, & Discussion] pappy97:
Yes to all of your bullet points, was on Android 11 before that. I only take stock OTAs.

So now that this failed once again, I dirty flashed the factory image and back to a working phone, but unrooted. Right now I have Android 12 unrooted.

When you say reflash vbmeta to both slots without disable flags, you mean:

fastboot flash --slot=all vbmeta vbmeta.img

and then for flash stock boot

fastboot flash boot boot.img

?

And once I do that, boot up to system, and then try the steps again?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If your phone is working, there's no point to flashing vbmeta or boot again. I would say you can either hold tight and wait to see if we find some sort of solution, or you can make sure your phone is backed up, then factory flash again with a data wipe and try the steps to flash vbmeta and a patched boot image.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I was on Android 11 and I flash the Android 12 factory image without the -w to upgrade to Android 12.

Now, that I am on Android 12 what are the steps for me to root with Magisk?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You dirty flashed the factory image, and you were able to boot into system?

The steps to root would be:

- Reflash vbmeta with disable verity / disable verification

- Patch and flash boot image
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
@V0latyle

Yes, I dirty flash the factory image and booted into the system.

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

Fastboot flash boot magisk patched.img

Is that correct?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes, that is correct.

I am honestly surprised you didn't get a corrupted data error.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Nope, it booted flawlessly. When, I flashed the magisk_patched.img it looped back to the bootloader/fastboot mode. I flashed the stock boot.img and it booted flawlessly again. :)
[Google Pixel 5 Guides, News, & Discussion] Rumsfield:
Same here. No corruption error, just a stuck at fastboot when I did the old magisk method. Re-flashing A12 boots fine but no root. (Dirty flashed from A11, P5)
[Google Pixel 5 Guides, News, & Discussion] jnss98b:
From what I'm reading, looks like you can't really safely update from A11 to A12 and then successfully root without wiping even if you use the OTA update method? @V0latyle
[Google Pixel 5 Guides, News, & Discussion] Rumsfield:
None of that worked for me, now I cant reflash to get back to system as I am getting a data error.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I use SDK Platform-tools.

I put the vbmeta in the Platform-tools folder, open a Command prompt in that folder, type or paste the command (fastboot flash vbmeta

--disable-verity --disable-verification vbmeta.img) at the prompt and press enter.

What phone?

Bootloader unlocked?
[Google Pixel 5 Guides, News, & Discussion] Rumsfield:
Pixel 5, Unlocked BL.

I dirty flashed 12 from 11 but magisk obviously didnt work. I could flash the boot.img to at least get the phone to run normally, just with no root. Now I just tried what you said as I was thinking you got root to work?

But as soon as the commands went through the phone will no longer even get to the startup screen.

I am getting data may be corrupt error, the last thing I want to do is wipe as the photos on this phone apparently were not backed up. I just want to get it functional to save the photos at this point.

edit: reflashing vbmeta got it going again. :that was close:
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I know the first thing you did is back up all those pictures. :)
[Google Pixel 5 Guides, News, & Discussion] Rumsfield:
You sir would be correct. This particular pixel is not my phone. Just about half done backing them up to my external HDD lol.
[Google Pixel 5 Guides, News, & Discussion] Rumsfield:
But hey getting back to the topic. did you get root working with the method you were talking about or were you just stating you got the system up and working with a dirty flash but still have no root. I may have gotton confused and thought you had a work around for dirty flashers such as myself. (not the nude kind, the phone kind).
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I was looking for a work around that is why I was communicating with the thread starter: V0latyle. His solution for dirty phone flashers is to reflash vbmeta.img then flash the magisk patched boot.img. I was about to give it a try, when I read your post that made me hesitate. I was happy when you edited your post and said reflashing the vbmeta.img fixed your phone. I think I'll do some mor reading berore I proceed.

Now, that you have successfully flashed the vbmeta.img. Are you going to try flashing the magisk patched.img after you finish backing the phone up?
[Google Pixel 5 Guides, News, & Discussion] Rumsfield:
Heck no I was going to wait for you to do it first haha. I am going to wait and tell the owner of the P5 root will be on hiatus until I have every single peice of data backed up on this phone in case I brick it.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
There are only two solutions for XDA members who dirty flashed Android 12 and want root.

Reflash Android 12 with an edited flash-all.bat file that disables verity, disables verification and wipes the phone:

Post in thread '[GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**' https://xdaforums.com/t/guide-update-to-and-re-root-android-12-read-the-notes.4345627/post-85805653

:(

Temporaily live boot a magisk_ patched.img: Post in thread '[GUIDE] Update to and Re-Root Android 12 **READ THE NOTES**' https://xdaforums.com/t/guide-update-to-and-re-root-android-12-read-the-notes.4345627/post-85811561

I'm thinking about wiping my phone to root it, but I'm going to wait until the November 2021 factory image drops. Why? I want to know if

wiping the phone will be required with each factory/OTA image update

.
[Google Pixel 5 Guides, News, & Discussion] Zorga:
Alright so I got the update through OTA and updated with no problems, tried reflashing VBmeta but got the corrupt message in recovery of try again or factory reset. tried a couple of times with no luck then used the command ( fastboot flash vbmeta vbmeta.img ) and the phone booted normally but no root obviously

what should I do now if I want root and don't want to wipe my phone? suggestions?
[Google Pixel 5 Guides, News, & Discussion] thecompany:
How did you get the OTA? Did you unroot first by flashing the unpatched boot.img and then checking for updates in system settings?
[Google Pixel 5 Guides, News, & Discussion] Zorga:
nope just checked for updates while being rooted and got it and installed it
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It almost seems that way.

Reflashing vbmeta is a solution we found to work on the 12 Beta. I'm glad it worked for some of you; it didn't work for me, as I continually got a corrupt data error until I performed a factory reset.

It is extremely advisable to back up all your photos and data before any update.

For those of you who haven't been able to recover from the "data corrupted" error, see if you can ADB sideload the OTA.
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Hi ! I have flash fhe Fi and do wipe data but Always when flash patch boot doesn't work !? I'm on Android 12 work but how can root it now ? I don't understand ? Please ?

Do flash ota again and vmbeta and patch boot ?

Thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Many users are experiencing issues and we are still trying to figure out the problem. If you need root, you may need to perform a factory flash and wipe data. If you don't need root, try to ADB sideload the OTA.
[Google Pixel 5 Guides, News, & Discussion] PablosCorner:
I ended up having that "corruption" screen when I tried to flash the vbmeta, glad to know I wasn't the only one who dealt with that (and that was before the post got updated to address the issue).
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I've been trying to stay on top of it.

Currently the only fix seems to be to perform a factory reset. Everything seems to work just fine after that.
[Google Pixel 5 Guides, News, & Discussion] PablosCorner:
I was able to sideload the OTA update to restore my phone back to normal with my data intact. At least this time, if I really want root back, I can prepare myself to back up all my important data before wiping it.

EDIT: In order to be able to do the OTA sideload to recover from that error, when you press "Try again" on the error screen, quickly press the button combo to boot to bootloader, and then you should be able to access the recovery menu and be able to sideload the OTA update.