How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root-Update

[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.

 

[KOLIOSIS]

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.

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

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.

 

[Az Biker]

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.

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)...

 

[DanHakimi]

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)...

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?

 

[Az Biker]

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?

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

 

[roirraW "edor" ehT]

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?

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.

 

[DanHakimi]

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.

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.

 

[Az Biker]

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.

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.

 

[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.

 

[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!

 

[Az Biker]

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!

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.

 

[probono10]

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)...

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

 

[Az Biker]

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

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

 

[probono10]

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

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?

 

[Az Biker]

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?

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

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

 

[State.of.mind]

Can anyone confirm that Magisk 30 (24314) works on the P60…

 

[Lughnasadh]

Can anyone confirm that Magisk 30 (24314) works on the P60…

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.

 

[Dragon Kumera]

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

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

 

[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

 

[Az Biker]

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

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!