yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] V0latyle:
Someone want to test this?

Requirement: Pixel 4a, 5, 5a, 6, 6 Pro rooted with Magisk 23016

Reboot into bootloader and reflash vbmeta without flags.

Reboot to system.

Reboot to bootloader again, re-reflash vbmeta with disable flags.

Reboot to system. If you get the Rescue Party corruption message, just reboot to bootloader and reflash vbmeta without flags.

Report results here.
[Google Pixel 6 Pro] hpower1:
Thanks for this guide and the work you put in this. Also thanks to the other users giving helpful info. Just did OTA sideloade of .017. Worked perfect, no issues, kept data and root is good.

Next thing is to open the box for my pixel stand that came today.

edit: Initial reaction after update, I think the FP reader is a bit faster. .037 update was a noticeable improvement for me. This seems like it is a bit better. I didn't like it at all initially, and as of right now, I'm very glad I kept the phone.
[Google Pixel 6 Pro] WhiteReign:
Great Work!!!!!!!

Much Easier then the last method!!
[Google Pixel 6 Pro] marekm69:
Hello. My Google 6 Pro is unlocked version from Best Buy, and I am not 100% sure, which factory image is for my phone: 12.0.0 (SQ1D.211205.016.A1, Dec 2021) or 12.0.0 (SQ1D.211205.017, Dec 2021, US carriers). Thx.
[Google Pixel 6 Pro] hpower1:
with my pixel 4 xl, I had unlocked version, running on Verizon network. Pixel 6 pro now is the same. I had always used the regular build, but on the Dec update for my P6P, I switched over to the US carrier build. No issues. That is what I did, for what that is worth to you.
[Google Pixel 6 Pro] marekm69:
December update include bootloaders, if I'll update wrong bootloader, my P6p will be brick, so, I'm scared, and I want to be 100% sure before any stupid move.
[Google Pixel 6 Pro] hpower1:
I did the regular build for both November updates, via sideload of the OTA. Then for the December update I used the US carrier version, again sideload of OTA. No issues here.
[Google Pixel 6 Pro] marekm69:
OK. Thank You for advice, I'll try later.
[Google Pixel 6 Pro] fmotta61:
I'm quite experienced in rooting but I never had a Pixel.

Not scared by trying but, after reading all the posts, i can't understand if it's possible to relock bootloader to bring phone back to factory condition if I decide to sell it.

Thanks.
[Google Pixel 6 Pro] V0latyle:
If you live in the US (I assume you do as you bought it from Best Buy), use the US firmware.

It doesn't really matter that much which firmware you use; the US version just has radio enhancements and improvements for US carriers.

Updating the bootloader is very very simple.

Reboot phone into bootloader

Update bootloader:

fastboot flash bootloader <drag and drop bootloader.img here>

Reboot to bootloader:

fastboot reboot bootloader

These instructions are in the OP. Follow the instructions and you'll be fine.

Yes, it is.

My recommendation for doing this is using the Android Flash Tool. You would want to check the "Wipe data", "Lock bootloader" and "Force flash all partitions" boxes. This returns everything to factory stock and locks the bootloader, so you don't have to do anything else.
[Google Pixel 6 Pro] Dragon Kumera:
I guess waiting for christmas was a good idea so all this info can be sorted out and streamlined process can happen
[Google Pixel 6 Pro] V0latyle:
Considering the fix we now have, it's a lot better than it could be.
[Google Pixel 6 Pro] wulfgarfang:
ok so i patched the boot.img and then flashed the patched img but all i get is a bootloop. so i reflashed the original boot.img and im back but no root. so now what?
[Google Pixel 6 Pro] Golf c:
Are you using canary magisk 23016 to patch the stock boot image?
[Google Pixel 6 Pro] wulfgarfang:
yes thats correct.
[Google Pixel 6 Pro] Golf c:
Weird. Worked for me without disabling vbmeta on stock boot image
[Google Pixel 6 Pro] Golf c:
I remember talk of deleting remnants of other magisk, like that alpha build floating around. Also if you renamed the magisk app you have to delete that.
[Google Pixel 6 Pro] WorldOfJohnboy:
I just got my Pixel 6 Pro today. Unlocked the bootloader, disable verity/verification. Installed Magisk safely and correctly. Then when I tried flashing the full December update, my phone now bootloops. (This is after I flashed vbmeta.img with disabling verity/verification) So, I tried flashing (without wipe) the Full November, then disable verity/verification, still bootloops. Finally, I flashed the full November with Wipe. Still bootlooped. Disabled verity/verification. Still bootlooped. Flashed the Magisk Patched boot (for November) and it STILL bootloops. Please help me, I am at a complete loss.
[Google Pixel 6 Pro] WorldOfJohnboy:
Just to note, I'm unsure of my Magisk version. Was going to install 23016 but I'm stuck with stock recovery and fastboot only. The only thing I can think of is possibly getting someone to send me a boot.img for December that is Magisk modified?
[Google Pixel 6 Pro] WorldOfJohnboy:
The Magisk I had installed on my November imaged phone was downloaded from https://github.com/topjohnwu/Magisk clicking the Magisk Canary button under "Downloads"
[Google Pixel 6 Pro] WorldOfJohnboy:
OK, I don't know exactly where I went wrong, but I suspect my fastboot was too old. I finally flashed the November image (wiped) and it booted. So, I decided to take the leap and did the same with the Full December (wiped and put in to disable verity/verification). Now I am at the point that I'm wiped and on December update. Do I dare install Magisk Canary 23016 and then try to patch my boot?
[Google Pixel 6 Pro] Dragon Kumera:
you dont need to do the disable verify thing anymore. Reflash stock december image then root with magisk latest build that been listed here on front page 1. I think you got to patch the boot image still not sure.
[Google Pixel 6 Pro] wulfgarfang:
Okay so I'll explain everything in as much details I can. This is how it went. I flashed December update and edited the flash all file so that the whole process was automatic including flashing the patched boot.image file. But I got a boot loop and I realize it turns out that I flashed the wrong update. So I was able to get back into fast boot and then subsequently flashed the correct update taking the w away and it booted right up. No problems. I even kept all my data. Now I updated magisk version to 23016 patched the boot. Image file and when I flash the patched file I get a boot loop. My question is that I screw something up along the way because I really want my root back. Should I just start the whole process over and wipe it?
[Google Pixel 6 Pro] WorldOfJohnboy:
My problem was similar except I didn't flash the wrong update. I'm 99% certain my fastboot was an older version (I've had a Galaxy Note 20 Ultra 5G, so I didn't update my platform-tools files). As soon as I updated ADB and Fastboot, my problems went away and I'm on December's update with Magisk Root.
[Google Pixel 6 Pro] wulfgarfang:
solved! I had a module that was causing the bootloop. Member P6P pointed out to me that it could be a module and he was right the tulsadiver mod. To solve it i flashed the original boot.img which allowed me to get into the system. i activated safe mode and booted right to bootloader. I then flashed patched boot.img and booted to system which was in safe mode. this deactivated all magisk mods. i then Booted back to system and BOOM! no bootloop! unistalled the tulsa mod and rebooted back to rooted dec update! Thanks P6P for that input.
[Google Pixel 6 Pro] galaxys:
Yeh, those modules can cause chaos! Glad you posted your recovery steps! Cheers
[Google Pixel 6 Pro] Dragon Kumera:
That good to know! Ya modules are a pain to trouble shoot some times
[Google Pixel 6 Pro] Project_WHaT:
I just attempted to sideload the OTA and in the Recovery I got the following error:

Finding update package...
Verifying update package...
Update package verification took 97.2 s (result 0).
Installing update...
Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
E: Error in /sideload/package.zip (status 1)

Install from ABD completed with status 1
Installation aborted.

At the top of the screen it says in red

WARNING: Previous installation has failed.
Your device may fail to boot if you reboot or power off now.

At this point, what should I do?
[Google Pixel 6 Pro] fil3s:
No need to disable vbmeta or verification. Just get the canary magisk and flash.

Edit: disregard , I was reading page 15.
[Google Pixel 6 Pro] fil3s:
I just use the Android flash tool.

Android Flash Tool

flash.android.com
[Google Pixel 6 Pro] Project_WHaT:
I believe I've bricked my device. I followed the instructions here (https://developers.google.com/android/images) to flash the factory system image. I did lose all my data unfortunately, but that is what happens.

I believe what happened was I thought in the original post where it said "Due to this fix, Pixel 6 / Pro users MUST use 23016 or newer for root." I thought it only meant the Magisk app and not the actual installed boot image needed to be on version 23016. I believe this needs to be clarified to say that both the app and the installed boot image should be on the correct version and not just say "use 23016".

In addition, although I did not get to this step in my failed update, I was confused when it says "Boot the master root image". Does this mean the master root image from the Rooting spoiler directions? If so, that should also be clarified as I would not have looked there if I was only updating
[Google Pixel 6 Pro] V0latyle:
Are you able to get into bootloader? Your device isn't truly bricked until it has as much function as a rock.

That would have no bearing on your ability to update. Additionally, this is covered in the OP.

I'll make a note. However:
[Google Pixel 6 Pro] gerard_f:
If you have a PC and adb, a easier method is to use that command while booting

adb shell magisk --remove-modules
[Google Pixel 6 Pro] crisco654:
So I'm not a novice at rooting/updating, but not an expert either lol. So just wanted to ask for some clarification on a couple things. First, after patching the boot.img the first time(and renaming it to master boot.img), I can use that same one for future updates(without having to keep repatching boot.imgs)? Secondly, in the past I've learned you shouldn't update via automatic OTA if rooted, but you can do it now, and just flash the patched boot.img + direct install to reroot again? Am I understanding that correct; is that the safest way? Thanks!
[Google Pixel 6 Pro] roirraW "edor" ehT:
Not really, no (you can't keep re-using it). The kernel (boot.img) changes every month. Plus, Magisk (and Magisk Canary, such as 23016 that we have to use for the December update) changes especially to keep root working for new updates, so you should always patch the new boot.img each month with the newest Magisk (not necessarily Canary, but for now, yes the latest Canary build).

It has certainly been dangerous to try to take automatic OTAs in the past, some folks say you can now but I'm going to remain cautious. I always update manually using the full firmware zip. You need the full firmware zip to get the new boot.img out of anyway. That is safer.
[Google Pixel 6 Pro] crisco654:
Ok cool. Yeah I've always patched my boot.img when updating/rerooting in the past, but had to ask b/c the guide mentioned making a master root.img and was just curious about it. And yeah, as much as taking automatic OTAs sound more convenient lol, I think I'm going to stick with the more proven method of just manually flashing updates(which I've in the past). Thanks for the quick response!
[Google Pixel 6 Pro] Lughnasadh:
Interesting you've heard some folks say you can now. I have a friend, who was on a Pixel 3aXL at the time, who said he got an automatic OTA update while rooted and I think everything went fine except he lost root. This was either for Nov. or Dec. update, I think. I'm wondering if something indeed has changed 🤔

I am like you and flash the factory images every month so I really don't need to worry about it, but it is interesting that we're getting some anecdotal statements that say it may be working now. But as you say, I still wouldn't trust it as of now though.
[Google Pixel 6 Pro] Project_WHaT:
I was in the recovery at that point. Would have I been able to get back into a working state at that point? If so what steps would I have needed to take? It was late at night so I sort of panicked and flashed the factory image.

Then what could have caused the error?

I understand that I am responsible and I do take full responsibility for what happened, but it's still imperative that instructions are clear and understandable
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! I'm guessing they wanted to make sure you name it something that will stand out.

I haven't kept too close a track on how many people, or who in particular, said what about (insert anything here that I don't do :D ), and it might've been as few as one person saying "you should be able to take automatic OTAs", and whoever it was, I think they were knowledgeable enough about other things that I would accept their statement as indeed a possibility, but I'm just not interested in that anyway.

It may also depend on many factors such as whether you're using a custom kernel, or what other root modifications are being used. Whatever it is, I will always make a blanket statement that no one should use automatic OTAs (I have them turned off in developer options) even if they're offered. There have definitely been some phones I've had in the past which IIRC, were soft-bricked by a user taking an automatic OTA while rooted. These might've been all Verizon devices, however, so at least in some cases, they didn't officially/properly have their bootloader unlocked, rather root was achieved via vulnerabilities.

Maybe it is indeed safer taking an OTA on Pixels. I'm sure no matter what it's recoverable, but perhaps requiring a full wipe, and since I have 400 GB of FLAC music on my phone that takes hours to copy over any time I wipe, I'm cautious about anything that might even soft brick me.

I will continue waiting each month for reports that x version of Magisk successfully rooted the new update and probably disable all Magisk Modules except Universal SafetyNet Fix before updating, and then waiting until my kernel and mods of choice are updated or reported okay to use on the latest update.

I just need my phone to work the way I want it to and I don't have time to start from scratch when possible. This almost sounds like I turned this into a mini-rant so just know that's not my intention.
[Google Pixel 6 Pro] V0latyle:
As it so happens, that's what I was going to suggest. I would have tried wiping cache in bootloader then attempting to sideload the OTA again; failing that, I would have dirty flashed the factory image.

Not sure. How exactly did you try to install the OTA - via sideload or from storage? Either way, it's possible the OTA image was corrupted when it was sent to your phone.

"Clear and understandable" can be subjective terms. To someone who is familiar with Android device partitions, ADB, boot image patching, etc, the directions are quite clear. This guide requires a minimum degree of knowledge, and it is the individual user's responsibility to ensure they indeed have a clear understanding of the instructions. Never hurts to ask questions if you're unsure. There is no imperative that any guide or instructions on a forum such as this be written in such a way so as to be utilizable by people who do not have any understanding of the above concepts. There are indeed some tutorials in other parts of this forum that are way beyond my own scope of understanding. Regardless, it is still the individual user's responsibility to understand what they're doing, as well how to fix it if something goes wrong, because modding device firmware carries an inherent risk, and you alone assume that risk when you choose to attempt it.
[Google Pixel 6 Pro] V0latyle:
Before the Magisk fix, running a patched boot image required disabling verity and verification - something that cannot be done when updating via automatic OTA. Prior to the fix, I had recommended that the only way someone should update was via the factory image, because verity and verification could be disabled at flash time.

The "danger" was that disabling verity/verification, if they were not disable before, required /data to be clean. So, if someone was rooted and took the automatic OTA, they would not be able to regain root without wiping data.

This is no longer an issue as of Magisk 23016, thankfully.
[Google Pixel 6 Pro] Lughnasadh:
Yes, I understand all that as I am up-to-date on the latest ongoings. My comment was more about being able to successfully take an OTA update automatically while being rooted at all. In the past OTA updates would fail while being rooted.

Of course John had a workaround in Magisk where you could install an OTA successfully while preserving root by "Restore images → Install OTA → Install Magisk on the other slot → Reboot with Magisk installed". However, around September 2020 Google changed the way they pushed OTAs via GMS to Pixels and his previous workaround would lead to a bootloop. Therefore he removed the "Install to inactive slot" option at that time.

But that's not what I was really talking about. My comment was aimed at actually about having an automatic OTA update take place while being rooted and be successful, and not about the changes to the boot image header and the verified boot process. My friend was on a Pixel 3aXL so the vbmeta fiasco didn't even apply to him.
[Google Pixel 6 Pro] crisco654:
So, everything is rooted and updated(to the december update). However, every time I boot now, it says "your device is corrupted". Should I be concerned about this? Everything else on the phone works fine.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Someone else in this section very, very recently reported having the same problem. I'm not sure if they solved it or not, but search this section for "corrupted" and you should find the beginning post fairly fast. Maybe they'll least you to the solution.
[Google Pixel 6 Pro] crisco654:
Nevermind I see it. V0latyle mentioned it could give you this message, but just recommends to factory rest and redo the process, and it should go away.
[Google Pixel 6 Pro] crisco654:
So, I get the corrupted error, and have factory reset a few times now, and it hasn't gone away. Everything else works perfectly. So, is this a problem, or can I just ignore it for now(although it's kinda annoying when I boot up my phone lol)?
[Google Pixel 6 Pro] ilatimer1:
So I had the exact problem. The only way I was able to resolve it was to flash the Novemner image and the DID the OTA to December update. The error went away the second I started the November image installation. Even before it finished installing.
[Google Pixel 6 Pro] V0latyle:
The only time you should be getting a "Your data might be corrupted" screen post update is if you disabled verity/verification when it wasn't disabled before.

This is no longer necessary - as of Magisk 23016, you can simply patch and flash the boot image.
[Google Pixel 6 Pro] crisco654:
This fixed it! Flashed the Nov again, and then flashed the Dec update(didn't do the OTA method). And voila, the "corrupted" message went away! Thanks for the help!

Yeah, I never disabled verity/verification, so not sure why the corrupted message came up. Anyway, I just reflashed the Nov update, and then flashed the Dec update again, and it went away.
[Google Pixel 6 Pro] WorldOfJohnboy:
Just wanted to drop a thank you to those that helped me the other day with this. I was able to update to December and root with Magisk Canary, however I hadn't realized the Dev took away Magisk Hide.

Unfortunately, I am back to unlocked bootloader and no Root as I have Corporate Apps on my phone that I need and they are blocked if they see root. Sucks as I wanted to run AdAway, but for daily use, I can live without it I suppose.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Working SafetyNet with Pixel 6 Pro Android 12

And you can still hide root from apps with Zygisk on Magisk Canary.
[Google Pixel 6 Pro] diesteldorf:
V0latyle,​

Just updated to the newest December build and want to thank you again for maintaining this thread.

The last time I updated was prior to Magisk 23016 and I was a little nervous that I would end up losing data.

The whole process took less than 5 minutes and everything was intact.

Happy Holidays.
[Google Pixel 6 Pro] V0latyle:
Merry Christmas!
[Google Pixel 6 Pro] dilruk:
Denylist does the same if not better. Try it if you want to be rooted.
[Google Pixel 6 Pro] card13:
I'm a little confused (the last 2 pages talked a lot about those who were not yet on Dec Patch).

I understand we don't need to use the command "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" anymore. However I rooted prior to that fix coming out and I'm currently on the Dec update w/Magisk 23016.

What I am confused about is not the why I would want Verity and Verification on, but do I need to do it manually. Meaning will Magisk turn those back on for me automatically or do I have to flash the vbmeta.img back to the phone to turn it back on? Also if I do flash the vbmeta.img back to the phone, has anyone done it and did you experience any negative effects (trying to determine if a backup is required or optional)?
[Google Pixel 6 Pro] Lughnasadh:
No you don't need to enable Verity and Verification manually. Having it disabled right now is not a problem. When the January update comes out just don't disable them again and they will be enabled automatically and then flash Magisk (Canary 23016+) as usual.

When you update to a new monthly security build, a new vbmeta image is flashed to your phone. Since it is an unmodified vbmeta image (meaning you didn't disabled those 2 flags), by default verity and verification are enabled, and therefore you don't have to enable them manually. Magisk (Canary 23016+) will recognize this, do it's thing, and still allow you to boot.

So don't worry about flashing vbmeta.img manually. The next update will automatically do that with verity and verification enabled unless you specifically disable those 2 flags, which of course is no longer needed.

Hope this makes sense...
[Google Pixel 6 Pro] roirraW "edor" ehT:
Edit: Better to stick with what @Lughnasadh said.

Previous reply: Yes, you need to do it manually. "fastboot flash vbmeta vbmeta.img" is what you want to re-enable them. If you're using or going to use a custom kernel, you might want to verify with the developer that their latest version uses the same fixes that Magisk Canary 23016 does, otherwise the custom kernel would still need those disabled.

Several folks here have re-enabled them here (but not myself because I'm not sure about the custom kernel I use). I haven't read about any bad side effects when there aren't complications such as custom kernels that might not have been updated the same as Magisk did.
[Google Pixel 6 Pro] Lughnasadh:
And what @roirraW "edor" ehT said about some custom kernels may need verity and verification disabled is true and good advice, although by now I think most, if not all, have adjusted and you don't need to disable those 2 flags anymore for a custom kernel, especially those that are now using zips instead of flashing the separate images. But always best to check with the kernel dev and make sure before flashing a custom kernel.

I should have mentioned that earlier 🙃
[Google Pixel 6 Pro] card13:
@Lughnasadh and @roirraW "edor" ehT Thank you both! That makes much more sense! The majority of me was hoping it was an auto process, but the experienced part of me went "It's never that easy" lol.
[Google Pixel 6 Pro] V0latyle:
As @Lughnasadh pointed out, verity and verification are enabled by default. They cannot be manually enabled; they can only be manually disabled.

Now that disabling them is not necessary, you simply do not need to worry about them. They don't need to be re-enabled. All you have to do next update is not think about them - it's literally that simple.

For the sake of information, those flags are set when the /vbmeta partition is written. Magisk is not involved in that process in any way.