yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Az Biker:
If anyone finds errors, missing or confusing information while following the steps in the OP, please post it and tag me so I can fix it immediately.

A few things I'm seeing in other threads is users still using disable verity, and not verifying their edit of the falsh-all.bat file, then accidentally wiping their device.

My OP is supposed to be super easy for anyone without much knowledge using fastboot, so if anyone has suggestions, please post them.

Thanks!
[Google Pixel 6 Pro] GivIn2It:
It seems there are a lot of guides to rooting a phone for the first time in these forums, but not much info on updating once rooted. My p6pro is running Nov. update, was rooted with canary. I updated Magisk to 24.1 stable, and I don't want to screw up when I update, like losing data, etc. What is the exact procedure for updating this phone to the latest build?
[Google Pixel 6 Pro] Az Biker:
Follow these instructions in OP (half way down)

UPDATE Factory Image WITHOUT Wiping Data:

I use this exact method every month, no issues.
[Google Pixel 6 Pro] GivIn2It:
Got it, but one more question: most of the downloads listed on https://developers.google.com/android/images have carrier specific labels, but the only one listed for Feb. does not, am I to assume this one works for all variants, including my unlocked one?
[Google Pixel 6 Pro] Az Biker:
Yep, at least for now 👍
[Google Pixel 6 Pro] Az Biker:
Followed the UPDATE Factory Image WITHOUT Wiping Data: in the OP, word for word, installed the latest Magisk 24.0, safetynet remained and didn't need to be re-installed, not a single problem.

Previous config:

Jan factory update

Kirisakura 1.5.0

Magisk 23016

Safetynet 2.2.0

YASNAC 100% pass

Current config:

Feb factory update

Kirisakura 1.7.0

Magisk 24.0

Safetynet 2.2.0

YASNAC 100% pass

Posting this so users can feel confident that the process in the OP works like a charm :p
[Google Pixel 6 Pro] GivIn2It:
UPDATE Factory Image WITHOUT Wiping Data:

1- Within the Platform Tools folder, find the FLASH-ALL (.bat) file

2- Open it with text editor and remove the -w (keep ONE space between remaining text, SAVE file, reopen to verify -w is removed)

3- Verify FASTBOOT DEVICES by typing CMD in the address bar of the same platform tools folder

I had a little hangup at step 3. Windows CMD would not show fastboot devices. I had to run adb reboot bootloader, when I got to fastboot mode, fastboot devices did show the device serial number, I was then able to proceed with your guide, and it worked wonderfully. By the way, what are the main benefits you see from Kirisakura 1.7.0?
[Google Pixel 6 Pro] Az Biker:
I barely ran the stock kernel (maybe a day or two) so I can't compare Kirisakura to stock. My battery life is great, the device rarely gets warm- let alone hot, updates zips are easy to flash with EX Kernel Manager...

The features/change log is in the OP.
[Google Pixel 6 Pro] Dragon Kumera:
i got the boot image for pixel 6 pro for magisk here. February patch. Try this flash it in fastboot mode.
[Google Pixel 6 Pro] daveseris:
Thanks. Trying it within minutes (I didn't realize how annoying my P6P can be without adaway!)
[Google Pixel 6 Pro] daveseris:
2 good things to report .. no brick, root restored! You're a lifesaver!
[Google Pixel 6 Pro] Dragon Kumera:
yw!

Adaway was the first thing I did on my phone.
[Google Pixel 6 Pro] Az Biker:
March update to fix WiFi issue, according to Google.

This reportedly only affect a "small number" of devices :unsure::unsure::unsure:
[Google Pixel 6 Pro] Az Biker:
March Factory Images

F5, F5, F5... :p :p :p
[Google Pixel 6 Pro] Lughnasadh:
Monday, Monday, Monday... 🙃😅
[Google Pixel 6 Pro] krystiano:
I finally opted for the root pixel 6 pro but I have a question.

do it today or wait for tomorrow's updates.

I currently have the 12L version on my phone.

if so, which android version to download ??

sorry if i asked in wrong topic
[Google Pixel 6 Pro] Morgrain:
Tomorrow the normal Android 12 update is supposed to drop, that has nothing to do with Android 12L.

There are some rumors that suggest that Google plans to implement A12L into the "normal" A12 build at some point, but these are rumors for now.

Whether or not you can "upgrade" from A12L to March Security Update (normal A12 branch) is unknown at this point. It's possible that you need to do a factory reset, if you want to switch to the normal A12 branch (again) per tomorrows update, but we'll see about that tomorrow.
[Google Pixel 6 Pro] krystiano:
Thank you for replay.

ill back to "normal" android 12 and will do root.
[Google Pixel 6 Pro] Az Biker:
10am here in Arizona and nada yet! :eek::eek::eek:

:p
[Google Pixel 6 Pro] krystiano:
5:15 pm in UK and nothing 🥺🥺🥺
[Google Pixel 6 Pro] Lughnasadh:
I didn't say which Monday 😅😂🤣

"Today’s update marks our tenth Pixel Feature Drop 🎉 🎊. The latest updates begin rolling out to Pixel 3a through Pixel 5a (5G) devices today, while Pixel 6 and Pixel 6 Pro devices will begin receiving their updates later this month."
[Google Pixel 6 Pro] Dragon Kumera:
I am pretty sure you can upgrade from beta to official a12. Google said so themselves when you opt out of beta. Just dirty flash is my guess.
[Google Pixel 6 Pro] krystiano:
I opt out from 12L to official A12.

When you do it it will wipe all data from your phone.

When you opt out u will received OTA update.
[Google Pixel 6 Pro] Jason123420:
Is it possible to use a Chromebook to unlock and root? Haven't unlocked an android bootloader for a very long time. I need guides lol
[Google Pixel 6 Pro] roirraW "edor" ehT:
Theoretically, as long as SDK Platform Tools (I assume you would try the Linux download) work on Chromebooks, then yes. However, months ago I recall several users in this section saying they had trouble. If I remember correctly, the tools worked fine by themselves, but there might've been a problem with the USB connection.

First thread in the search of this section only with "Chromebook" in the title.

Good luck to you - hopefully somehow it has improved.
[Google Pixel 6 Pro] Dragon Kumera:
That is strange as when I signed up they said it did not wipe data after opting out. Maybe I miss read it as opt out when it was opt in.

Couldn't you just swap partition to the other slot and or reflash February image?
[Google Pixel 6 Pro] krystiano:
When I opt out on webside it was information something like : u will receive OTA update and will wipe your data.

About this⬇️ I don't know how 🤔🤔
[Google Pixel 6 Pro] Dragon Kumera:
well I could help you if you havent wiped data yet.
[Google Pixel 6 Pro] Az Biker:
For those ready to hit F5, lemme save you a few seconds

... still no March update :oops:
[Google Pixel 6 Pro] Lughnasadh:
If Fido is right, should come out at 12PM CDST, or in about 2 1/2 hours. That's usually the time Google releases their builds.
[Google Pixel 6 Pro] Dragon Kumera:
actually there is now
[Google Pixel 6 Pro] bleez99:
It's here, rooted with Canary 24304. Boot loops with Magisk stable for me. Others are reporting that Magisk stable works for them.

Go figure. Full flash for me as usual, no OTA.
[Google Pixel 6 Pro] Papote3:
Did you had any magisk modules? I disable all my modules before updating, some may not work with the system updates
[Google Pixel 6 Pro] bleez99:
No need. Just safety net fix and the built-in hosts.
[Google Pixel 6 Pro] Dragon Kumera:
Have you tried to redo the whole get magisk image part and reflash that?
[Google Pixel 6 Pro] bleez99:
Twice. Then I gave up on stable/beta and installed Canary.

Before flashing the new image, I pull and prepare the boot image that's going to be flashed.

I flash without a reboot.

I then flash my prepared boot image.

Stable Magisk bootlooped on me.

I gave up, grabbed Canary and prepped the boot image again with that. No bootloops.
[Google Pixel 6 Pro] dacapho:
Has anybody noticed weaker vibration on the March update?
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://xdaforums.com/t/general-12-1-issues-am-i-the-only-one.4420045/post-86619115

(same user):

https://xdaforums.com/t/notification-vibration-weak-after-march-update.4419685/#post-86620875
[Google Pixel 6 Pro] A.Priori:
which canary version do you have a link?
[Google Pixel 6 Pro] bleez99:
I have done a 360 and tried stable again. So it's not relevant. But Google is your friend. Look for John Wu's GitHub site. It's all there. Currently on 24.3 stable and KiriSakura.

No idea why I bootloped twice but I can't reproduce the issue now.

Careful, there are a lot of fake websites out there for Magisk. Only GitHub.
[Google Pixel 6 Pro] Az Biker:
Updated to April factory image using the same process as previously (outlined in the OP) with the exception of updating Magisk to Stable 24.3 prior to flashing.

The Magisk change has been updated in the OP.

All remaining steps in OP remain business as usual, and I was updated in less than 15 minutes!
[Google Pixel 6 Pro] whatsisnametake2:
so latest magisk canary, which i used for march update, won't work with april update at all? got to be magisk stable? if so whats the simplest way to update magisk canary to stable on my device? just like a regular app update?
[Google Pixel 6 Pro] Lughnasadh:
Latest Canary (24305) is working fine for me on the April update.
[Google Pixel 6 Pro] whatsisnametake2:
good to know cheers
[Google Pixel 6 Pro] Az Biker:
Some users have reported bootloops using anything but stable 24.3, and since I used 24.3 stable, that's what I'm suggesting others use.

But as Lughnasadh said, some are using latest canary with no issues as well.

With instructions aimed at newer members or those unsure of what works and what doesn't, I tend to err on the side of caution and stick with what I've used, and I know works :D
[Google Pixel 6 Pro] whatsisnametake2:
ok thanks for the detailed response. good to know.
[Google Pixel 6 Pro] Lughnasadh:
If you are using the OTA Install to Inactive Slot then don't use Canary 24304/5, as it's causing problems with that method of updating. Canary 24303/4 was causing problems with kernels and multiple modules, but was fixed in Canary 24305...fyi.

EDIT: Apparently there are also problems using Stable 24.3 when using the "Install to Inactive Slot" method to upgrade to April build. Would suggest to not use this method on at all for updating to the April build. A fix appears to be in the works:

New way to mock sepolicy: by controlling seclic by yujincheng08 · Pull Request #5690 · topjohnwu/Magisk

Fix #5685

github.com
[Google Pixel 6 Pro] whatsisnametake2:
I usually use the full factory image without wipe for the updates rather than ota image. I don't do anything with regard slots just let it do it's thing. canary 24305 should still be good for that method? if I were to update to stable from canary, do I just install it over the canary one?
[Google Pixel 6 Pro] Lughnasadh:
Yeah, I use the flash-all method without the -w as well. Since that method replaces the rooted boot image with the stock boot image it really doesn't matter what version of Magisk you are using since once you boot up you won't be rooted anyway and will need to re-root (unless of course you add the patched boot image to the update script, but I personally don't prefer to do that). Just remember to disable any mods that may need updating beforehand.

To update from Stable to Canary, just uninstall the Stable Magisk app and install the Canary Magisk app, then re-root.
[Google Pixel 6 Pro] unboostedzc:
EDIT: Got it.
[Google Pixel 6 Pro] Az Biker:
Sorry it took so long to reply. I was out mountain biking and couldn't respond.

Whatever the problem was, glad you got it figured out!
[Google Pixel 6 Pro] Simba2022:
Had a question. I know I need to get a unlocked carrier version from google so the bootloader is unlocked. However, a friend was telling me that one the device is rooted if i place a T-Mobile sim in the device it will/can re-lock bootloader. Is this true? Anyone experienced this? Just trying to do my homework before buying a device. Thank You
[Google Pixel 6 Pro] mkhcb:
#fakenews
[Google Pixel 6 Pro] roirraW "edor" ehT:
First, I don't want to make any assumptions, so if you don't know, no Pixel comes with the bootloader unlocked. The factory unlocked Pixels - the unlocked is actually referring to "carrier unlocked", which isn't synonymous with being able to unlock the bootloader, although the two can be made to be related such as with T-Mobile where once you pay off the phone, they make the device carrier unlocked, which also enabled you to unlock the bootloader.

Factory unlocked Pixels are able to have the OEM unlocking toggle enabled in Developer options, and then you can use the fastboot command to actually unlock the bootloader in fastboot/bootloader mode. That's the only place and way to either lock or unlock the bootloader.

No SIM card can lock your bootloader, even if you boot into fastboot mode with the SIM in the phone.
[Google Pixel 6 Pro] DanHakimi:
Is it impossible to root / unlock the bootloader for a carrier-locked device? My Pixel 6 is carrier locked and I'm getting the impression that I'd have to actually use the device for 40 days and get an official carrier unlock before I could unlock the bootloader, and I'd need to unlock the bootloader to root.
[Google Pixel 6 Pro] KOLIOSIS:
Sounds like you're on T-Mobile US.......

Typically,the phone needs to be SIM Unlocked 1st .

Some here may have a work-around,but,I recommend getting it SIM Unlocked 1st,this may prevent issues in the future if you end up bricking a SIM Locked phone.

Here's their unlocking policy:

SIM Unlock Policy | Unlock Your Mobile Wireless Device | T-Mobile

Learn how to unlock your wireless mobile device for use on other carriers (formerly SIM Unlock). See device compatibility and unlock requirement.

www.t-mobile.com

Even if you haven't met all the standard requirements listed,you can always hit up T-Force on Twitter & state your need/reasons to SIM Unlock your P6P.
[Google Pixel 6 Pro] Az Biker:
Unless I'm mistaken carrier unlock and bootloader unlock are two completely separate animals.

Some carriers allow carrier unlock (freedom to choose your carrier) after a few months, but lock their bootloaders tight (like Verizon)...
[Google Pixel 6 Pro] DanHakimi:
Somebody implied to me that my bootloader unlock option was grayed out because my phone was carrier locked. Are you syaing that Sprint-T-Mobile locked my bootloader Verizon-style, just to make my life worse? And that there's no way around that?
[Google Pixel 6 Pro] Az Biker:
No.

I'm saying carrier unlock, and bootloader unlock are two completely different things, and carrier unlock doesn't lead to bootloader unlock.

I've seen several members who bought devices that can be carrier unlocked, thinking it meant the bootloader could be unlocked.

Not sure how your carrier handles the bootloader on it's devices. Verizon's are locked down tight...

Just making sure it's understood that one doesn't equate to the other 👍
[Google Pixel 6 Pro] roirraW "edor" ehT:
To add: Once you pay off your device, they can carrier unlock your phone, and also make it possible to enable OEM unlocking (so that you can unlock the bootloader). Many, many others on T-Mobile have reported doing that.

Like @Az Biker, I always try to make sure that others don't assume that carrier unlock = being able to unlock the bootloader. In this case, you will likely be able to once you pay off the device, but as said, they are two completely different things and not always associated with each other.
[Google Pixel 6 Pro] DanHakimi:
My phone is fully paid off. That's not the issue. It's carrier locked because that's just their policy and they apparently just carrier lock everything and refuse to change that until you've been using it, active, for 40+ days. Because they suck.

Yes, I know that carrier locks are not the same thing as bootloader locks, my phone is carreir unlocked and the OEM Unlocking option is grayed out and my understanding is that the OEM Unlocking option is grayed out because the bootloader is only meant to be unlockable once the carrier lock is removed.
[Google Pixel 6 Pro] Az Biker:
If your OEM Unlocking is greyed out, it is most likely because you do not have the option to unlock the bootloader, regardless of whether or not your device is carrier unlocked.

Here's a blurb from Verizon about their devices being carrier unlocked after 60 days;

"Devices that you purchase from Verizon and certain devices purchased from our retail partners are locked for 60 days after activation. After 60 days, we will automatically remove the lock. Following the 60 day lock period following device purchase, we do not lock our phones at any time."

I can assure you that NONE of these Verizon devices has a bootloader that can be unlocked, even after the carrier lock is removed.
[Google Pixel 6 Pro] Dragon Kumera:
So, I was on android 12 beta February build. I decided to dirty flash android 13 (was a no go kept booting into bootloader). I then flashed android 12 stable release dirty flash. (Removed -W) and it worked! I kept all my data and never had to wipe.
[Google Pixel 6 Pro] stoph8n24:
So this method worked well at getting root for me but I somehow lost root (don't ask). My bootloader is already unlocked, would I be better off just getting the OTA update then just flashing the new Magisk patched boot image? Thanks for all your help!
[Google Pixel 6 Pro] Az Biker:
Not sure what caused you to lose root.

I've used this exact process dozens of times without any issues or losing root.

Be sure you disable any modules, patch the correct boot.img from the image you're updating to, and that you reboot into bootloader on step 16. (even though it appears to be a redundant/unnecessary step) before moving forward.
[Google Pixel 6 Pro] probono10:
Like you, I'm one of those "root once per millennium" folks. As a result, it looks like I made a mistake somewhere along the line. I took the steps below, but...bootloop. Is it hopeless or can my Pixel 6 Pro be revived?

1) Downloaded May 2022 "12.1.0 (SP2A.220505.002, May 2022)" image from google

2) Downloaded USB drivers for Windows 10

3) Unlocked bootloader ("Successful" screen returned)

4) Disabled verity and verification using "fastboot flash vbmeta -- disable-verity --disable-verification vbmeta.img" ("Ok" sending/writing screen returned)

5) Download Magisk 24.3

6) Patched boot image ("Succesful" screen returned)

7) Copied boot image from Pixel to folder containing ADB AND "12.1" image from google

8) Flashed patched boot image: fastboot flash boot .\magisk_patched-24300_ZeVXf.img

9) Phone enters bootloop - never gets past "Google" screen and goes to the "hit power to pause" screen

9a) Rescue and recovery yield the same results
[Google Pixel 6 Pro] Az Biker:
If you're stuck at G, you're not dead in the water.

Start fresh.

I'd reco a fresh install wiping everything (leaving the -w in the flash-all script).

Follow the step by step in the OP, disregard verity blah blah blah, that language is no longer needed.

You should be right as rain 👍
[Google Pixel 6 Pro] probono10:
Started again at the "flash-all" step since the bootloader is already unlocked and I have the patched boot image using the image: image-raven-sd1a.210817.036.zip, but started getting messages like:

archive does not contain "init_boot.img"

archive does not contain 'dt.img'

archive does not contain 'pvmfw.img'

archive does not contain 'recovery.img'

Phone is on the "fastbootd" screen currently, but it hasn't been able to boot.

It's raining, but all is apparently not "right". Any thoughts?
[Google Pixel 6 Pro] Az Biker:
I think initially getting the 'does not contain " text is normal. At least I recall seeing it every time.

Without intending to be insulting at all, make sure you have the latest factory image for 6Pro, and you're pulling the boot.img out of the SECOND ZIP file and patching THAT one.

I have followed the OP since the beginning of the 6P without any issues, but I'm OCD and even reread my own steps a few times before doing them :D

And IIRC, there's a new version of SDK TOOLS available over the last few months, make sure you're on them although that may not matter since I still use the previous version of SDK, but some people are the windshield, and some are the bug :p
[Google Pixel 6 Pro] State.of.mind:
Can anyone confirm that Magisk 30 (24314) works on the P60…
[Google Pixel 6 Pro] Lughnasadh:
Yes it works but when on A13B2.1 and updating from 24313, direct installing caused a bootloop for me and one or two others. Patching the boot image, however, worked fine for updating from 24313 to 24314.
[Google Pixel 6 Pro] Dragon Kumera:
I think your mistake is including magisk boot image during the factory install wipe. Try first boot without any magisk modifications to the boot image then once booted go to bootloader and flash the boot image
[Google Pixel 6 Pro] R2DeeTard:
Doing this on the Pixel 6 Pro for the first time. Unlock worked fine but when I try to flash the updated boot.img I get this error.

C:\platform-tools>fastboot flash boot --slot=all C:\platform-tools\magisk_patched-24314_zbwXC.img

Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).

Sending 'boot_a' (98304 KB) OKAY [ 2.315s]

Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...

FAILED (remote: 'failed to flash partition (boot_a)')

fastboot: error: Command failed
[Google Pixel 6 Pro] Az Biker:
See the last few posts above.

Magisk must be done in a very specific manner, and IMHO is the hardest part of the entire process.

Make sure you're using the boot.img within the second zip folder after unzipping the first factory zip folder.

Then you must make sure you have the proper version of magisk, install it first, then follow the patch boot.img steps.

While I cannot promise you what went wrong with your magisk install, I CAN promise you my step by step in the OP works 100%, as do the guides also mentioned in the OP.

Start fresh right after unlock. Read every step, understand it, then perform it. I know the impulse to just go balls to the wall and get a device rooted, but manufacturers, even Google to a degree, have made root harder to achieve, requiring more difficult methods to install. THANK GOD FOR DEVS!!!

Make sure you have the following;

Latest SDK Tools

Proper version of magisk

Correct factory image

Correct boot.img file

All this is mentioned, with links, in the OP 👍👍👍

Best of luck!
[Google Pixel 6 Pro] Dragon Kumera:
For those who need the magisk image already patched for May 2022 security update.
[Google Pixel 6 Pro] sjgoel:
Unlocked the bootloader today. What magisk version works for the June 2022 security update? I used 24310 as in OP link but somehow have issues.
[Google Pixel 6 Pro] Lughnasadh:
Stable 25.1 or Canary 25101.
[Google Pixel 6 Pro] sjgoel:
Thanks.

Can i just patch the boot.img with this magisk version and flash the patched img? Or need to start from earlier steps?
[Google Pixel 6 Pro] Lughnasadh:
Patch and flash. Of course, disable any modules that may need updating beforehand.
[Google Pixel 6 Pro] kp72204:
Thanks to everybody here especially the OP AZ Biker for doing these kinds of posts for people like me. Jun2022 and Magisk 25.1 did the trick.
[Google Pixel 6 Pro] Dragon Kumera:
What july update do we install? There are 3 versions.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you're using Verizon, install the Verizon one. If you're in a EMEA/APAC area (Google Search - more details at that search hit here), install that one. If neither of those, install the other one.
[Google Pixel 6 Pro] Dragon Kumera:
So phone bought from google, bootloader unlocked. I should go verizon since my carrier is verizon? That wont interfere with bootloader?

ota updates never work for me lol. I tried uninstalling magisk rematching original image. Disabled all modules. Update installed but when installing magisk to inactive slot and rebooting it caused corrupt device. So now gt install factory image without -w