yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes.

No. The only thing that can lock or unlock the bootloader is you, with local access to your phone via the correct fastboot command.

It's likely the IMEI of the device is what determines whether the bootloader can be unlocked or not, and updates don't affect that.

I think I fooled with the OTA method once or twice after I got my Pixel 1 almost six years ago, but I like the full factory image process instead. OTA method seems so hit and miss - it seemed to depend on hitting the lottery on more variables. It may work flawlessly for months, and then something happens. The rare times I've ever had a problem with the full factory image, all that I can think of but once was my own fault, and even the one time I don't know how exactly it could've been my fault was probably my fault too. :D

Now that I think of it, for quite a while on my Pixel 1 I was using @Chainfire's FlashFire app that allowed me to flash updates and keep root/re-root without using TWRP or a computer. It was awesome.
[Google Pixel 6 Pro] Dragon Kumera:
chainfire seems familiar.

I am one of those who have a verizon pixel xl gen 1 phone still. I unlocked the bootloader before verizon patched the exploit. Its been running solid since with lineage os. Its currently in storage as a backup phone. Replaced the battery in like 2020. Wanted a p6 pro to fiddle with so got one.
[Google Pixel 6 Pro] bush911:
Well, chainfire is the one who is very well known for introducing root to Android.

Has anyone managed to updgrade to July updates without losing root?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, as @bush911 said, @Chainfire is who made SuperSU and plenty of other things that we used before Magisk. Ah, I did the same with my Verizon P1, except I didn't replace the battery, although I did treat the battery gently. I "briefly" (for me) went to the Samsung Galaxy Note 10+. Loved the hardware, and hated the software.

I haven't updated yet, but @foobar66 has.
[Google Pixel 6 Pro] Dragon Kumera:
Ah right. True they did.

I still have the original pixel xl 1 battery. It has 2hr sot. But It had overheating could barely use it since day one. That battery did last from 2016 to 2020. Can last longer if I wanted but I needed a new battery so kept the old one in case.
[Google Pixel 6 Pro] Dragon Kumera:
I did if you count flashing full factory image without -w. Here is the Magisk image I used.
[Google Pixel 6 Pro] Dragon Kumera:
I am so confused right now. Google website showed 2 verizon images for the pixel 6 pro. Both July updates.

12.1.0 (SQ3A.220705.003.A1, Jul 2022, Verizon, Verizon MVNOs)

12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)

My phone been saying there is an update but its on the July security patch.

Also just did the google play system update. But not sure what is going on atm.

edit. Seems google released a 1mb minor update.
[Google Pixel 6 Pro] mko000:
Google delays August security patch for Pixel devices

One US carrier is applying a hotfix still using July's security patch

www.androidpolice.com
[Google Pixel 6 Pro] Dragon Kumera:
Ah ok. That is why. Thanks!
[Google Pixel 6 Pro] GivIn2It:
Az Biker: I like using your simplified guide for updating/rooting. I understand there is some funkiness going on with android 13 concerning the bootloader, and inability to downgrade. This scares me due to having upgraded some phones in the past and finding out the upgrades contained gotchas and couldn't go back. Would you mind updating the guide to show how to keep the downgrade option with 13, or am I worrying for nothing? I'm taking a wait and see for now in case anyone majorly complains about 13, before taking the plunge, but the phone is nagging me.
[Google Pixel 6 Pro] GivIn2It:
Yeah, but I'm not interested in wiping data.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you want to downgrade Android versions, especially between a major version 13 to a previous version 12, then a factory reset is necessary for the phone to work correctly - and in some cases, even to boot.

TL;DR - you're worrying for nothing (your words). Update to Android 13 and enjoy it. :)
[Google Pixel 6 Pro] Az Biker:
I know I'm a "little" late to the 13 update game, but for those who don't know about the bootloader situation when jumping to 13, PLEASE READ THE BELOW LINK FIRST!!!!

READ PRIOR TO UPDATING TO 13
[Google Pixel 6 Pro] mirasgg:
I don't no What's is root
[Google Pixel 6 Pro] Az Biker:
OP has been updated to include flashing Android 13 bootloader to both slots.

All other steps remain the same (y)(y)(y)
[Google Pixel 6 Pro] Dragon Kumera:
neat. I still havent updated my phone to a13 lol. I have been pretty busy.
[Google Pixel 6 Pro] julerobb:
Does this apply to the raven model of pixel 6 pro? I want to remove Verizon's lock on it so I can reflash the os to do a clean install of android.
[Google Pixel 6 Pro] Az Biker:
If you have a Verizon device, the bootloader is locked and this method will not unlock the bootloader (there is no known method to unlock a Verizon device, and probably won't be for the foreseeable future)

Sorry to be the bearer of bad news
[Google Pixel 6 Pro] julerobb:
I don't see the point in why the carrier would lock the bootloader, how does that even work? Like how does that even increase security of the device? That's like the shelf display at best buy for PCs.
[Google Pixel 6 Pro] Az Biker:
Verizon has been locking their bootloaders for several years now. I think since the Note 3 maybe.

Them locking their bootloaders might deal with excessive tethering, or use of hotspot which used to be premium features?

If you want to root/ unlock your device's bootloader and are on the Verizon network, buy direct from Google. I've purchased my last 4 devices directly from Google and I'm on Verizon 👍
[Google Pixel 6 Pro] liquidraven:
Sorry if this was already asked or not in the right forum. Wondering if the P7 Pro unlocked will be able to get root and custom image(s) as well? Do not have a pixel yet but contemplating trading for a 7 pro.
[Google Pixel 6 Pro] Az Biker:
As long as the 7Pro keeps in line with previous Google pixel devices, I would say YES.

If you do go to a 7Pro and look forward to unlocking the bootloader, flashing Roms, kernels, etc. * * * DO NOT BUY A VERIZON variant * * * .

Purchase straight from Google. They have 0% financing if a user doesn't want to pay in full.
[Google Pixel 6 Pro] liquidraven:
thanks i just did that through google store and my unlocked note20 ultra 5g is giving me a 550 off trade-in value.
[Google Pixel 6 Pro] mhrussell1:
I would offer another option to buy an unlocked Pixel from Amazon. They had a better price by $100 when it was still full price at Google and the customer service experience 1000% better.
[Google Pixel 6 Pro] Az Biker:
Does Amazon offer warranty on rooted devices?
[Google Pixel 6 Pro] GivIn2It:
Amazon also often includes their own spinware free of charge. Go with Google.
[Google Pixel 6 Pro] mhrussell1:
Zero "extra" software on P6pro.
[Google Pixel 6 Pro] GivIn2It:
Good to know. Thanks.
[Google Pixel 6 Pro] Az Biker:
Anyone with a 6 PRO jump to the 7 / 7PRO?

Pros and cons compared to the 6 Pro?
[Google Pixel 6 Pro] Lughnasadh:
Based on my usage, set up, etc... :

Pros: Better battery life for me, modem and the camera upgrades, slightly less-curved display

Cons: Doesn't natively support 32-bit apps
[Google Pixel 6 Pro] Az Biker:
Thanks for your 'review'. I highly value your opinions 👍

I was under the impression the 7Pro camera was unchanged or minimally changed.

Scale of 1 -10 on how much better the 7Pro is vs the 6Pro?
[Google Pixel 6 Pro] Lughnasadh:
The Macro Focus and the increase in zoom to 30x are the biggest camera upgrades for me. I take a lot of pictures, especially of wildlife, so the zoom upgrade is particularly helpful for me. And the Macro Focus is pretty cool.

If it wasn't for the camera and modem updates, I may not have upgraded. I also traded in a phone, so that with the $200 store credit I got made it worth it for me, financially.

With 1 being barely an upgrade an 10 being a huge upgrade, I would say a 3, maybe 4, at least for me.
[Google Pixel 6 Pro] Lughnasadh:
Also forgot to mention the 7 Pro has a brighter display.
[Google Pixel 6 Pro] Az Biker:
If it's not a huge upgrade in your opinion, I'm glad I decided to wait for the 8 Pro 😁
[Google Pixel 6 Pro] Lughnasadh:
Yeah, I think the 8 Pro will be a significant upgrade.
[Google Pixel 6 Pro] idkwhothatis123:
It's been a long, long time since I've been on here. Looking to root my p6p, on 13 QPR2.

I've had several beta updates (of course QPR1, various security updates, etc.)

Does this mean I do not need to flash 13 to both slots manually, ahead of root? Or do I still need to do this ahead of the process?
[Google Pixel 6 Pro] Az Biker:
AFAIK you still need to flash the bootloader to each slot.

I only update every other month or so, and I've only done this for November's update.
[Google Pixel 6 Pro] idkwhothatis123:
Perfect. That is the clarification I was looking for. Thanks!
[Google Pixel 6 Pro] Az Biker:
January 2023 factory image is HERE !

If you are still on Android 12 PLEASE READ OP regarding flashing Android 13 bootloader to BOTH slots BEFORE updating to Android 13 factory image (y)(y)(y)
[Google Pixel 6 Pro] dlwhdrlf:
Hi, so I haven't unlocked my bootloader yet so I'll have to have my data wiped if I want to root. Is there an easy way to back up and restore my phone while I go through with the root process?
[Google Pixel 6 Pro] iwearthebelt:
Not that I'm aware of. That's the only thing I miss about not having a custom recovery. I know that you can create a backup with Adb but I've never done it before.
[Google Pixel 6 Pro] wildfirebill:
Just got my pixel 6 pro 512 it already has a13 installed on it. I just want to verify that I can follow this guide to root stock image using this guide
[Google Pixel 6 Pro] Az Biker:
Outside of a Google account and/or Drive, I don't think there is.

When jumping to an entire new version (from 11 to 12) I prefer to do a complete clean install and reinstall my apps individually to prevent conflicts and incompatibilities between new software and older apps.

tl;dr

I don't think a complete backup in the traditional sense is sn option, might be best to start from scratch with new Android version.

I don't think it'd be necessary since 13 should be on both slots, but I also don't think it'd hurt to do it anyway just so you know 100% 👍
[Google Pixel 6 Pro] raeee1:
Hi after updating my pixel 6 to android 13,when flashing a patched boot.img I keep getting an error failed remote partition (boot) how can I fix this to achieve root?
[Google Pixel 6 Pro] Az Biker:
A few things to verify first.

Did you flash the android 13 bootloader to both slots BEFORE you updated to Android 13 factory image (per OP instructions)?

Did you pull the boot image from the SECOND folder within the first unzipped factory image folder, save it to your device storage, then patch that boot image with the latest canary Magisk?
[Google Pixel 6 Pro] abalam:
Just a question, why does this topic say that we need to flash the patched boot.img and also to both slots? I read on another thread we need to boot the patched boot.img and then directly run install in magisk manager. What's best now?
[Google Pixel 6 Pro] Az Biker:
I just updated to January factory image following the steps in the OP.

Zero problems. The only thing needed flashed to both slots AFAIK is the Android 13 bootloader (if coming from an Android 12 image). I did that on my first 13 install and haven't done it since.

Hope that helps.
[Google Pixel 6 Pro] abalam:
But what best now, flash the patched boot or boot into it and direct install in magisk app? This confuses me.
[Google Pixel 6 Pro] Az Biker:
You patch the boot.img in magisk, put that patched image back on your pc, in fastboot flash the patched boot.img, let it boot, reboot and you're done.

Like I said, follow the below instructions in the OP.

9- After the install, it will reboot into system, let everything settle, skip start up options and get to where you can download the latest MAGISK apk on your device (downloads folder)

***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***

10- Connect your device and PC and put the extracted BOOT.img file (from the CURRENT factory image you are flashing FOUND IN THE SECOND ZIP FOLDER) that you placed on your PC, put it on your mobile device where you can easily find it (I created a folder FILES TO FLASH)

11- Install Magisk (use Canary 24310 linked above), follow instructions to allow files like this to be installed) ***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***

12- Open Magisk and choose SELECT AND PATCH FILE (select the BOOT.img you just put on your device

13- Copy the new PATCHED BOOT.img from your download folder back into your PLATFORM TOOLS folder where the fastboot application is located on your PC

14- Boot device into fastboot/bootloader, connect device and PC

15- Type CMD in address bar and verify fastboot connection (step 4)

16- Type fastboot reboot bootloader

17- Type fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img)

18- Reboot into System
[Google Pixel 6 Pro] abalam:
I understand the whole operation, but my question is why one flashes the patched boot.img and the other boots the patched in fastboot. I know back in the day you had to boot the proton kernel too and not flash it. Furthermore the continue installation in magisk by direct install. Do you understand my question, yes my english in not my native language
[Google Pixel 6 Pro] Az Biker:
Patching the boot.img IN MAGISK is required for magisk to remain active after the device boots up. The patched magisk boot.img replacs the original factory image boot.img file.

Otherwise, you would lose root tghe next time you booted up.

Flashing that patched boot.img in fastboot installs the patched image to both slots so regardless of which slot your device boots from, it will retain magisk (root).

If I am not understanding your question, my apologies.
[Google Pixel 6 Pro] abalam:
Never mind bro.
[Google Pixel 6 Pro] morphvale:
But you are, that is what he was trying to say.

I can't speak about other phones but, for my previous OP7T the root process was as follows:

1. Install Magisk

2. Patch boot image with Magisk and copy to PC

3. Fastboot boot patched image

4. Open Magisk and Install - Direct Install

5. Reboot. You are now rooted

While for Pixel 6 the process is, as described:

1. Install Magisk

2. Patch boot image with Magisk and copy to PC

3. Fastboot flash boot image

No more steps, you are now rooted

Note the difference in step 3 and and missing extra step.

So he's asking why the difference for the Pixel in step 3.
[Google Pixel 6 Pro] Az Biker:
I'm not sure why the difference outside of diff manufacturers...

That's more of a question for a developer. I just post the process that works for my device 👍
[Google Pixel 6 Pro] Lughnasadh:
Even though you aren't the one asking the question, I'm quoting your post because you describe the differences well and just makes for a good segue.

Either way will work. Some people like to fastboot boot the patched boot.img (gives you temporary root) first just to make sure everything is good and Magisk mods, etc. are working. If not, you can just reboot and you won't be rooted. If all is good then you can install "permanently" via direct install.

Others just like to fastboot flash the patched boot.img so it's "permanently" installed in one step (disabling Magisk mods that may potentially need updating beforehand is always good practice using this method).

Either way, it will only be installed to your current/active slot. Also know that if for some reason you want to flash the patched image to both slots you can't just switch slots and boot up you inactive slot (for a couple of reasons). You can only boot the slot in which the last firmware was installed. Therefore, say your current slot is slot A. If you flash the patched image to both slots you can't just switch to slot B and boot up and be rooted. You would first have to flash the firmware again to slot B to be able to boot up in slot B and then re-root while that slot is active in this scenario.
[Google Pixel 6 Pro] Nergal di Cuthah:
Neither is better than the other. Booting allows you to preview that boot prior to comitting. Flashing gets it in right away.

Personally i always flash with zero problem. I use a hybrid of @Az Biker and @V0latyle methods and have no problem.
[Google Pixel 6 Pro] RicoMartins:
Hey guys! I was successful in the process, thanks for sharing. Someone was successful in everything, saftnet passed banks, Google play and I have Widevone L1, hob and Disney hdr but Netflix was in FHD and HDR is now in SD Widevone L1. Any suggestion?
[Google Pixel 6 Pro] RicoMartins:
After many attempts, I managed to solve it... To whom it may concern: UNSF 2.40 was my problem, I went back to 2.31 and everything works fine now.
[Google Pixel 6 Pro] Nergal di Cuthah:
I assume you mean usnf 2.40 and 2.31, as those are the versions of usnf not magisk which is version 25 i believe
[Google Pixel 6 Pro] RicoMartins:
Perfect, sorry for the mistake I'm Brazilian and my English is only by translator. I will edit, thanks!
[Google Pixel 6 Pro] dacapho:
Hey guys, first time needing to downgrade and I need a bit of help. Going from the Feb '23 rooted update to the Jan '23. and then re-root. What is the correct process to avoid a bootloop or corrupt data while avoiding wiping or performing a factory reset?
[Google Pixel 6 Pro] Az Biker:
AFAIK, once you're updated to Android 13 on both slots (per OP) you should be able to flash the January Android 13 factory image using the same process as updating to the latest factory image.

The only thing you can't fo from Android 13 is go back to Android 12 or earlier. Again, this is my understanding.

Luckily there are several people watching this thread who know way more than I do, abd csn correct me if I'm wrong.

@V0latyle @Lughnasadh any insight either of you?
[Google Pixel 6 Pro] Lughnasadh:
Correct. Just remove the -w from the flash-all.bat script (to keep data) and flash the January image, then re-root.

As for the red eio dm-verity corruption message, people have gotten this in all sorts of circumstances. It's not a big deal when you get this as usually there is just a hash mismatch and it usually goes away after an update. It's mostly a "cosmetic" warning and won't impact you in a negative way. You can safely ignore it. Probably the best way to avoid getting the message, though, is to disable verity and verification, but that will wipe your phone.

@dacapho
[Google Pixel 6 Pro] dacapho:
Ok, so I disabled Magisk modules, copied all the files back over into my folder from the Jan zip, removed the -w and saved. Ran the flash all script and all seemed fine except when it went to reboot, it bootlooped to the red corruption message cannot load Android system, data may be corrupt..blah blah. Try try again, still the same screen. It wont ever boot to the OS.

So then I did the whole thing over with the current Feb 23 files and it boots like normal and all is fine. Confucius

@Lughnasadh
[Google Pixel 6 Pro] Az Biker:
Make sure you're patching the boot.img from the January factory image, and not recycling the Feb image. The patched boot.img must match the factory image it came from.
[Google Pixel 6 Pro] Lughnasadh:
Odd. Should have worked as I've done it before and I know several people who are always go back and forth to different builds with no problems.

Wondering if you booted into the bootloader (or even recovery mode) and then rebooted from there if it would have booted...
[Google Pixel 6 Pro] V0latyle:
When downgrading it's generally smart to do a data wipe, although it probably wouldn't be required. If you don't flash the old bootloader and radio, you'll need to use the --force flag when flashing the image package: fastboot update image-device-buildnumber.zip --force

You can use this same method to flash the Android 12 builds on the Android 13 bootloader. They won't work properly but it can be done.
[Google Pixel 6 Pro] dacapho:
Thanks for the help guys, although nothing worked, I will just stick with the Feb update as I am definitely not willing to wipe data.
[Google Pixel 6 Pro] BROKEN1981:
I haven't rooted since the T-Mobile LG V30. I see I need to download the factory image. Issue is, I don't see it listed.

This is what I am currently on.View attachment 5831581
[Google Pixel 6 Pro] iwearthebelt:
Let me make things easy for you, there's a program called Pixel Flasher that a guy named Badabing2003 created that makes the whole process simple and almost fully automated for you. It even downloads the file for you. I highly recommend using it. It takes me 4 minutes every month to flash the latest release. It's easy to find on xda. You'll never go back to manually rooting your device (unless you enjoy doing it that way).
[Google Pixel 6 Pro] BROKEN1981:
I've tried it, but when I scan for my device, it never sees it.
[Google Pixel 6 Pro] Az Biker:
I know it's been a while, but did you resolve this? How? Good to post here for others who might be in the same situation (y)
[Google Pixel 6 Pro] BROKEN1981:
I got it to work after I reset windows. I remember at the time windows was acting up. Found out that my 2700X was going bad. Only way to install windows, I had to OC. If I didn't, the installation would hang. Put in a 5800X and now I'm good. It was just hardware related.
[Google Pixel 6 Pro] Az Biker:
Glad you got everything up and running!
[Google Pixel 6 Pro] Az Biker:
Steps in the OP work 100% (y)

Just flashed the Aug 23 factory image, super fast and easy, no problems!
[Google Pixel 6 Pro] Blue Sun:
If I get my Pixel 7 Pro (or the new Pixel 8 Pro due in a couple of weeks) through T-Mobile instead of buying it directly through Google, will I still be able to root the new phone immediately in factory set or will I have to wait until I have paid off the phone & ask T-Mobile to unlock the bootloader the way I had to do with my curreent Samsung 2020 Galaxy Ultra 5G 512 GB? I was planning to upgrade to the Samsung 23 Ultra (having used Samsung since Galaxy 2S, but this my Ultra was the first Samsung I couldn't root for 2 years. I used to root all my Motorola Droids before that. I'm NOT HAPPY about having an unrooted phone.
[Google Pixel 6 Pro] Az Biker:
As I understand it, if you want to root your new Pixel 7 or 8 Pro, you'll have to purchase it through the Google website directly.

Most carriers advertise their devices as "unlockable" but this ONLY refers to the ability to use your device on any network after 60 days. They will unlock your device so you're able to use it on any carrier BUT this has nothing to do with the BOOTLOADER being unlockable.

tl;dr

If you want to be able to unlock your device's bootloader and root it, you MUST buy your pixel from the Google directly.

Carrier 'unlock' only means the ability to switch your device to another carrier after 60 days, and has nothing to do with the bootloader being unlocked..
[Google Pixel 6 Pro] Lughnasadh:
I believe T-Mobile's policy is you have to pay off the phone and wait 40 days from the time of purchase before they will unlock your sim. Once the sim is unlocked you should be able to unlock the bootloader.

Sometimes if you talk to the right person and make up a story such as you need to unlock your sim because you are traveling to a different country, or something like that, they will unlock your sim without the two requirements above being met.
[Google Pixel 6 Pro] Az Biker:
I was under the impression that sim unlock (carrier switching) and bootloader unlock (rooting) were two completely separate things.
[Google Pixel 6 Pro] Nergal di Cuthah:
They are, especially verizon imei, but many carrier unlocks include the ability to now oem unlock
[Google Pixel 6 Pro] Lughnasadh:
They are, but in these situations you need to unlock your carrier/sim before you can toggle "OEM Unlocking" in Developer Options on so you can unlock your bootloader.
[Google Pixel 6 Pro] Nergal di Cuthah:
Easier to just buy google direct though :rolleyes: