yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! Glad it's rooted and all without trouble (sounds like). I use Google's own backup feature (and I also started paying for Google One a few months ago) so that I can cloud restore most things on a fresh phone. These days to restore from Google's cloud backup, when you tell it you want to restore data from another phone, then answer that you don't actually have the phone available to restore from, and then Google's OOBE (Out of Box Experience) will offer the cloud restore function.

Since I'm rooted, I started using Swift Backup (paid for it) - backing up solely to my free cloud choice of Mega.nz for now so that I can keep my 512 GB of storage free mainly for tons of FLAC-formatted music and temporary storage of recording long videos.

In case anyone's curious why don't I use Google Drive since I'm paying for it, 1) I don't want too many eggs in the same basket, 2) it's possible I'll downgrade my 2 TB plan to fit my immediate needs, as I got the 2 TB plan at the time in order to get the 10% Google Store credit back on all direct purchases, and 3) There isn't much I need to use my free 50 GB Mega.nz for anyway.

I typically still restore my apps using Google Cloud and then I restore selective app data from my cloud backup only for particularly troublesome apps to set back up, and as I need it.
[Google Pixel 6 Pro] bleez99:
Initially I had disabled verity on my 6 Pro. When I downloaded and installed (full image) the January update, out of fear that I would have to wipe, I continued to keep verity disabled. November and the notorious December updates both were installed with verity disabled.

I wanted to confirm, if I flash the January again, or any upcoming updates, will I be OK if I allow verity enabled or will I be stuck with a wipe?
[Google Pixel 6 Pro] dilligaf56:
Thanks! Yes, the root/SafetyNet fix went smoothly after I found a working cable for fastboot (the first two didn't work).

Afterward, I copied the apps, photos, music, other media, etc., over from my V20 but all the passwords and other data did not come over (I had a feeling this would happen). I did do a Titanium Backup of all of the apps and their data on the V20 and will copy it to the Pixel and restore the data. There will still be some system stuff such as SSH keys, Wireguard config files, etc., that I will have to find a way to set up.

I have a 2TB Google Drive also, which I have TiBu back up to as well.

I would like to have Nandroid backup available as well, when possible - as I have enough of the 512GB remaining to create one, then move it over to one of my computers to free up the space. Hopefully, TWRP will come up with a version for this phone.

Thanks again for your excellent guide! Take care - I owe you a beer! Do you guys have a donation link?
[Google Pixel 6 Pro] dilligaf56:
Thanks very much for this info. I was not planning to use the Pixel 5 version unless it was known to be safe. I will wait for a Pixel 6 version to be released. I have other ways to back up apps and data but want to be able to have a system partition, etc., backup as well. Thanks for the come-back!
[Google Pixel 6 Pro] craigacgomez:
Don't really see any point in backing up the "system" partition. You could simply flash the stock image. With root solutions like Magisk, it's extremely unlikely that you'd need to modify the system partition. You'd just use the mirror partition in Magisk.

And since you are likely rooted, if you need a good solution to backup apps and data, I'd recommend OAndBackupX
[Google Pixel 6 Pro] Dragon Kumera:
any chance you got a link? Just updated my p6p from december to january and had to redo the whole root process.
[Google Pixel 6 Pro] Lughnasadh:
A link to the commits? The next Canary has not been released yet.
[Google Pixel 6 Pro] V0latyle:
Please go back and read the top of the OP

I do this completely for free, simply because I enjoy helping others. None of us moderators are paid, either. I have a wife, a house, and a full time job; I do this on my spare time. It isn't very rewarding, especially when people repeatedly ask questions that have been answered in the OP, but at least I'm helping a few people like yourself.

Master Commits
[Google Pixel 6 Pro] Lughnasadh:
Yep. Think that person was actually asking for the link to the next Canary, which of course hasn't been released. yet. I would have put the link to that if I had thought that's what they wanted, but thanks for leaving it here. May help those who don't follow his Github and want to know where the latest commits are.

I personally check them often, just to see what John is up to 🙂
[Google Pixel 6 Pro] Dragon Kumera:
Ya but I would also like to view the commits to. So that link helps :).
[Google Pixel 6 Pro] Az Biker:
tl;dr

free help, moderately salted :p :p :p
[Google Pixel 6 Pro] Lughnasadh:
Right on. If you want to see the pull request for that specific change as well, here it is...

Enable installation to inactive slot on Pixel devices by capntrips · Pull Request #5204 · topjohnwu/Magisk

9c93fe6 updated the bootctl binary, which was the only thing preventing installation to the inactive slot from working on Pixel devices. This removes the check that hides the button on those device...

github.com
[Google Pixel 6 Pro] V0latyle:
Oh sorry, thought it was a question.

You don't get away from me that easily :D

Holding the Vol Down button while rebooting halts at bootloader, then user can select recovery from menu

Oh, I get pretty salty sometimes, my wife thinks I'm nuts for even bothering.

There's times I want to show people just how lucky they are I put up with them
[Google Pixel 6 Pro] bleez99:
I read the original post, I always read, and with all due respect, it's still unclear to me whether I have to deal with a corrupted device if I go forward flashing without the verity flags in the command line. That's why I asked. My device currently has it disabled, and I'm trying to avoid the aggravation of a wiped device.

I'm a contrubuter here too.
[Google Pixel 6 Pro] Nergal di Cuthah:
The short of it is no you no longer need to do that, magisk does it for you IF YOU USE CANARY MAGISK
[Google Pixel 6 Pro] bleez99:
Thank you. I went through that pain with my Pixel 5. As far as Canary, is there really another version? :)
[Google Pixel 6 Pro] Dragon Kumera:
Ya I remember hearing about that. Hopefully an updated canary build happens so I can move on from 23016 or whatever number it was and not have to reflash all the time for magisk. (Also, would like to update through system update menu one day if possible, with magisk).
[Google Pixel 6 Pro] V0latyle:
Did you read this part?

There is only 1 way to end up with an accidentally wiped device, and that's using the flash-all script without editing it. But, since I know that's not quite what you're asking...

You simply do not need to worry about verity/verification anymore. Period. Just update your device, patch the new boot image with Magisk 23016, and chive on.

Specificity is important here - Canary 23016 incorporates the boot image header fix. Magisk Canary has been around for a long time, and anything older than 23015 won't work.

Not yet, current Canary is still 23016, but an update is well on the way - and it will support patching to inactive slots, simplifying the update for users who prefer OTA.

OTAs on rooted Pixels have always been iffy. I don't know exactly what causes them to fail, but they usually require a few tries.

Sideloading should always work, though.
[Google Pixel 6 Pro] Dragon Kumera:
I decided to sideload (as I have had the update since last week and it just never wanted to install no matter how many times I tried).

I had to refresh my memory for recovery since I am so used to twrp and lineage os recovery I forgot I needed to unhide the command window to sideload the ota. But once done it went smoothly and I just had to redo the whole magisk patch boot image and flash.
[Google Pixel 6 Pro] roirraW "edor" ehT:
For my part, I too help folks for free. I used to take donations, but I also needed the money more at the time. I don't even remember if I ever officially removed the way to donate to me from XDA. I haven't bothered to check for the way I had set to donate to me in XDA's settings since they changed their software the other year. I wasn't very active for several years until recently as well. I'm just always glad when I can help someone.

I have pretty low expectations these days, too. I'm happy just when there's no drama going on, especially if it's not drama coming from me! 🤣

For what it's worth, TWRP for one phone 99.99999% of the time will not work on any other phone, but especially not different years' phones from the same manufacturer, and on top of that, the Pixel 6/Pro uses a completely different CPU than the Pixel 5 and previous. I'm sure there were exceptions, and I even have some ideas of what they were, but they were a drop of rain in the sea, relatively speaking. Besides all this, TWRP has to be gotten to work on Android 12 in general - for any phone - first. If/when that is done (could be months, could be a year, could be never), then work getting TWRP to work on the P6 & P6P could start in earnest. So it's a long road... :D

🥂 😂
[Google Pixel 6 Pro] Az Biker:
I thought the user was asking for instructions to get into the bootloader. I answered, then reread his comment and realized I misread it.

You're quick on the copy/paste, musta already been quoting the other comments and grabbed mine. Wasn't even live for 20 seconds before I deleted it (unless you used secret squirrel stuff to get it) 😛😛😛
[Google Pixel 6 Pro] Dragon Kumera:
Now I may be completely and totally wrong.

But couldnt we just do fastboot boot twrp.img and if it works it boots if not just turn phone off and reboot? As long as its not flashed we should be able to recover.
[Google Pixel 6 Pro] bleez99:
My comment on Canary was completely tongue in cheek!

I just had a bad experience with my 5 before the latest canary was released with the fstab fix. Wipe was forced due to a corrupted device, I landed in recovery with try again or wipe. Of course try again didn't work, and I'd rather not have to sit for an hour or three restoring my phone.

Thanks to those that responded.
[Google Pixel 6 Pro] roirraW "edor" ehT:
On paper, everything sounds great. I'm not a betting man, though. I wouldn't do this if I were you (or anyone reading this). I could be wrong but I'm given to understand that no phone that has Android 12 has a working TWRP yet.
[Google Pixel 6 Pro] Dragon Kumera:
Ya ofc we will need a working android 12 twrp. (But from my experience with pixel xl gen 1 that had twrp from like android 8.0 and before still worked even on android 11 kinda). Though Maybe significant changes were made in 12 to make this null and void.

I would love a way to back up everything local side like twrp did but guess I will have to be careful :).
[Google Pixel 6 Pro] V0latyle:
Yep. If it doesn't work, it doesn't work. Won't hurt anything.

Interesting. I had no such issue on my P5. I rooted the 12 Beta with 23001, then updated to 23015 when USNF was ported to Zygisk.

I SEE EVERYTHING

Nah but for real mods have the godlike ability to see deleted posts...and they can still be replied to even in Deleted Purgatory
[Google Pixel 6 Pro] Az Biker:
That's the secret squirrel stuff I was talking about 😁
[Google Pixel 6 Pro] dilligaf56:
Yes, I'm rooted. Magisk really has come a long way since I first started using it on my rooted V20. Back then, you really needed nandroid backups in case something got b0rked on a re-flash.

Took a quick look at OAndBackupX. Once I get everything sorted and tweaked, I will install it and give it a shot. Thanks!
[Google Pixel 6 Pro] Dragon Kumera:
*now to be evil and delete mod* mhahahahahahahahahahha.

ok offtopic but i couldnt resist.
[Google Pixel 6 Pro] dilligaf56:
Yes, I have two LG V20s - one running rooted stock Oreo (8) and the other Lineage 18 (11); the same version of TWRP works great with both OS; but of course, they were running on the same hardware. I'm finding that Android 12 and the Pixel 6/pro are horses of a completely different color. Still, I hope that TWRP does come out with a working version for us, even if the use-case is less obvious.
[Google Pixel 6 Pro] V0latyle:
The running joke is that I'm on the hook for multiple bans, never knowing when they'll hit :D
[Google Pixel 6 Pro] n3owin:
TLDR > Cant update from Nov to Jan update on my Rooted Pixel 6 Pro

Hey there! first timer here

Im trying to update my rooted Pixel 6 Pro from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022). I can see the update when i manually search for it on the phone but when it downloads it fails and says "Couldn`t update. Installation problem" with no further explanation.

So i tried the sideload method from this thread. No luck here as well. I got the 12.0.0 (SQ1D.220105.007, Jan 2022) update from the OTA link (Not sure if thats the right one but its the only one available that says JAN 2022) and when i get to the recovery i adb sideload drag file, the file uploads and fails with the following error > error applying update 7 kinstalldeviceopenerror

From googling that error it says that im trying to upload an update meant for another phone. Im sure that im downloading the "raven" one for the pro model.

Any advice would be helpful since i have been scratching my head for the last 6 hours.

A bit more info >

im using the same PC, usb cable, usb port that i used when rooting for the first time.

I rooted the phone following this thread without disabling Android Verified Boot since it said its not needed.

I have the Canary Magisk 23016. Disabled all modules and super rights to apps before trying both methods of update.

Im using the "Tiny ADB & Fastboot" to upload the update to the phone.

Its have not done any previous updates on this phone, rooting was done on Nov update since it came with it.

Extra question > Somebody posted that they had similar problem to mine and they updated with the <Update and Root Factory Image>. (1)If i try that will the phone revert to factory settings and (2) can i use the master root.img that i saved from the first root or do i need to patch it again?

P.S. Thanks a lot for the original guide!
[Google Pixel 6 Pro] roirraW "edor" ehT:
First, you shouldn't try to take an actual over-the-air update when you're rooted. It's rare that it would work while rooted, and at least with some phones, there's a chance trying to take the OTA while rooted will soft-brick your device (recoverable, obviously, because it's a soft-brick).

In Developer Options, you can disable the automatic OTA update check.

I recommend the other set of instructions in the OP "Spoiler: Update and Root Factory Image". I know there are folks who use the OTA file. I've always found it simpler and never had a problem in the last five years using the full factory image method.

You shouldn't use any modified/repackaged ADB/Fastboot. As the OP says, always use the (official) very Latest SDK Platform Tools. You should check for new Platform Tools every single month before you manually update your phone. Also always check to make sure you have the latest official Google USB Driver installed, at least if you're using Windows.

If you follow the instructions in the OP, you won't factory reset your phone. The key is to remove the "-w" from the flash-all.bat (I'm assuming you're using Windows), or the same from the flash-all.sh if you're using Linux.

I can't answer your (2) because I don't do it that way and never have. I'm sure someone else who is knowledgeable about that method will chime in.
[Google Pixel 6 Pro] V0latyle:
Or don't use the script at all and learn the commands...but I'm old fashioned like that
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm old without as much fashion! 😁
[Google Pixel 6 Pro] Lughnasadh:
I don't know....that new purple looks pretty fashionable on you 😅👍
[Google Pixel 6 Pro] Carousser:
Hope the below helps you and anyone else in a similar spot as I just was in the last hour.

I just updated from Nov 2021 patch (SD1A.210817.036) to Jan 2022 patch (SQ1D.220105.007) using factory image method. I was previously rooted on the Nov 2021 build using community/alpha magisk. Below was what I did

1. Download the factory image zip for the .007 build and extract some where on machine (for me, Win10)

2. On phone (still on .036 build), Copy over the boot.img file to phone

3. Open magisk app (I installed canary 23016 over the previous alpha/community version from Nov when root was still in flux), Magisk -> Install -> Select and Patch a File -> Select boot.img you copied over (for the SQ1D.220105.007 build) and let it patch

4. Copy over the newly patched image file to some local machine. Make a copy and call it like master-boot.img

5. Reboot into bootloader

6. Update bootloader from bootloader image in .007 directory (bootloader-raven-slider-1.0-8013568.img); reboot into bootloader

7. Update radio from radio imagein .007 directory (radio-raven-g5123b-93368-211225-b-8029609.img); reboot into bootloader

8. Update the update zip (image-raven-sq1d.220105.007.zip); it went into fastbootd immediately for me, watch terminal to know when update is done. When done, reboot to bootloader

9. Boot into the master-boot.img made from step 3/4

10. Open magisk and do Magisk -> Install -> Direct Install

11. Once done rebooting, open Magisk app

12. Disable riru; Enable Zygisk in settings and configure denylist if applicable; hide magisk app; reboot

13. Install MagiskHide Props Config (6.1.2) and safetynet-fix (2.2.1) from GH links in first post; reboot

I am updated on the SQ1D.220105.007 build from the SD1A.210817.036 build, have persistent root, pass safetynet, and did not need to wipe phone (thank god lol).

Pretty much, on your current build, patch the SQ1D.220105.007 boot.img using updated magisk app, then follow the steps for factory image/safetynet.

Btw - I am on a carrier unlocked P6P, 256GB.
[Google Pixel 6 Pro] Az Biker:
Meh... erase two characters VS type in a bunch of characters from memory...

I'm taking the poor memory, lazy, fewer clicks equals more chicks route!

Remove the -w, live longerer and prosperer :p
[Google Pixel 6 Pro] V0latyle:
*scoff* Troglodyte. :P
[Google Pixel 6 Pro] Ghisy:
I'm with Az on this one!! But again, I work in IT. We're usually pretty lazy when it comes to that stuff :P
[Google Pixel 6 Pro] Lycidias:
New magisk canary 😀

Spoiler content hidden.

mod edit: FIFY (y)
[Google Pixel 6 Pro] V0latyle:
Good stuff. This should simplify things for those of you who prefer to update via OTA.

Just updated my P5. Tried the "inactive slot" for poops and giggles, device bootlooped back to slot A.
[Google Pixel 6 Pro] V0latyle:
Please spoiler your photo, thanks!
[Google Pixel 6 Pro] Lughnasadh:
Wait, so you went into the Magisk App, restored images, went into System settings and updated via System Update (OTA), then before rebooting went back into Magisk and updated Magisk via "inactive slot" method and then hit reboot in Magisk and it bootlooped in the same slot you started with?

Just trying to understand if there is a problem with the Magisk update. Magisk should have made your phone switch to the updated slot after doing all that and rebooting.

Of course, if you didn't update via OTA and just updated Magisk via "inactive slot", then bootlooping back to slot A (assuming you started with slot A) makes sense.
[Google Pixel 6 Pro] V0latyle:
Nope, I updated to January by dirty flashing the factory image.

Other slot wasn't "updated", was just the same version.

I mean yeah, assuming that Magisk just commands system to perform the same reboot process it would do after OTA, in which case system would be looking for a "newer" version on slot B. Question is whether I could manually change to slot B and successfully boot.

Just found this, maybe worth a try

Edit: nope, bootlooped
[Google Pixel 6 Pro] Lughnasadh:
Ok, makes sense now. Since you flashed the factory image you stayed on the same slot. Magisk didn't detect your inactive slot was updated (because it wasn't) so it didn't force the phone to switch slots upon reboot.

Think we should still be good when updating via OTA (System Update) as long as this method is followed:

Magisk app → Uninstall → Restore Images (Do not reboot)

Apply OTA (Settings → System → System Update) (Do not reboot or restart)

Magisk app → Install → Install to Inactive Slot

Reboot

But I guess we'll find out for sure in February. The new changes to Magisk were tested on both the Pixel 5 and 6 with success before the changes were merged so we should be good. 👍 (famous last words 🙃)
[Google Pixel 6 Pro] V0latyle:
It did - device attempted to boot slot B, started to load kernel, then bootlooped back to slot A.

Shouldn't have to restore images. Just apply OTA, install to inactive slot, reboot.
[Google Pixel 6 Pro] Lughnasadh:
You need to restore images first in order to pass pre-OTA block verifications. Then apply OTA, then install to inactive slot and reboot.

And bootlooping back to slot A still makes sense to me because an OTA wasn't applied.
[Google Pixel 6 Pro] V0latyle:
I could have sworn I was able to OTA update at some point without restoring stock images. What you're saying makes sense though. Because things.
[Google Pixel 6 Pro] straumli:
I am a new owner trying to root my Pixel 6 pro but after patching boot.img I fail to flash the image, kindly advise where I made a mistake. I extracted boot.img from raven-sd1a.210817.015.a4-factory-bd6cb030.zip\\image-raven-sd1a.210817.015.a4.zip\\

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [ 0.032s]
finished. total time: 0.033s

C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot "master root.img"
target reported max download size of 261095424 bytes
sending 'boot_a' (131072 KB)...
OKAY [ 3.137s]
writing 'boot_a'...
FAILED (remote: failed to flash partition (boot_a))
finished. total time: 3.172s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "master root.img"
downloading 'boot.img'...
OKAY [ 3.059s]
booting...
OKAY [ 0.032s]
finished. total time: 3.091s

Booting the image and opening Magisk does not show a direct install option (only allows me to patch an image)
[Google Pixel 6 Pro] Lughnasadh:
You should be using the latest Platform Tools. https://developer.android.com/studio/releases/platform-tools

Also, are you using Canary Magisk 23017? If not, you should be. Will still work on your October build.

If still not working after this, try a different cable(s).

EDIT: I assume you are the October build since you are using the October boot image?
[Google Pixel 6 Pro] WorldOfJohnboy:
Seeing as how January's update dropped (sooner than Google had initially said), I think I'm going to go for the update. Typically, I'm a guy that likes to flash the full update (not OTA) without a WIPE and then "re-Magify" root after. Anyone done the update this way and any tips or tricks?

It should be noted that I use Zygisk (have to for corporate apps) so any helpful hints knowing that is appreciated as well. My thought was to:

-Patch January boot.img in Magisk and copy to my PC

-Run the flash-all.bat file with "-w" removed

-Flash the Patched January Boot image and boot it up.

-Done.
[Google Pixel 6 Pro] Dragon Kumera:
even more dangerous willing to say this in public on a forum :).
[Google Pixel 6 Pro] Dragon Kumera:
connect phone to pc. reboot to recovery and press top volume button to enter recovery option then sideload update and continue through commands of adb
[Google Pixel 6 Pro] V0latyle:
That's more or less how I updated, although I didn't use the script.

That's why it's a running joke...

Please read the thread before you post, as the question had already been answered some time ago.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I do it this way every time. I flash the full factory image with the "-w " removed, I go ahead and boot as is just to make sure there's no problems on 100% stock, then I Magisk the boot.img that I've extracted from the inner zip file, then flash that rooted boot.img, boot, and confirm everything's still working.
[Google Pixel 6 Pro] Dragon Kumera:
Sorry. I realized my mistake.