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

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member

roirraW "edor" ehT

Forum Moderator
Staff member
i'm new to pixel phones. if I root, then I later unroot, does it leave any trace that i've done so? I know samsung have a fuse trip thing. anything similar on pixel?
No, not if you fully restore the factory image and re-lock the bootloader (in that order). I *think* re-locking the bootloader will factory reset your device (just like it does when you unlock the bootloader), so that's why you should be fully stock before re-locking the bootloader.

Nothing similar on Pixel as on Samsung. Google doesn't gimp your phone for unlocking the bootloader, and no permanent changes whatsoever.
 

whatsisnametake2

Senior Member
No, not if you fully restore the factory image and re-lock the bootloader (in that order). I *think* re-locking the bootloader will factory reset your device (just like it does when you unlock the bootloader), so that's why you should be fully stock before re-locking the bootloader.

Nothing similar on Pixel as on Samsung. Google doesn't gimp your phone for unlocking the bootloader, and no permanent changes whatsoever.
ok thanks very much for the info. I thought I would try root for various things like hbm and substratum whilst it's still in the return period. will google pay and banking apps still work?
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
ok thanks very much for the info. I thought I would try root for various things like hbm and substratum whilst it's still in the return period. will google pay and banking apps still work?
You're welcome!

Yes, if you follow the directions [How To Guide] Working SafetyNet with Pixel 6 Pro Android 12.

I think there are a few people around the world that couldn't get a banking app (I think particular banks) working, but most of us, yes, as long as you fix SafetyNet and add all your banking apps to Magisk Canary 23016's Deny list so they can't see root.
 

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
I personally did not flash A1. I chose the US Carriers version.

Not that you particularly care what I did, simply that I am not seeing any negative externality of that choice. The device is working normally, I applied the safetynet 2.2.1 fix, configured and enforced deny lists, turned on Zygisk, and hid Magisk - with perfect success - including test setups of GPay, Netflix, et al.

I would not personally select the global image because I see no direct benefit in doing so. From what I understand, the US carrier version has specific and updated radio information that the global variant does not.

Hope this relieves a degree of pressure from your choice.
Yes this helps a lot. So no added bloatware or verizon forced lock somehow?

Also Just opened my phone today and when I get to the magisk step I would love a guide for getting it all 100% working. Though I will try myself first.
 

The.Jericho.Initiative

Senior Member
Jan 3, 2009
123
102
Texas
Yes this helps a lot. So no added bloatware or verizon forced lock somehow?

Also Just opened my phone today and when I get to the magisk step I would love a guide for getting it all 100% working. Though I will try myself first.

Once bootloader is unlocked, which you should do literally first thing, I do not believe that a carrier could lock the device even if they wanted to. My experience was that the fastboot process was unreliable and that the step-by-step guide made certain linguistic assumptions that I had difficulty following. I have to imagine those breaks in comprehension led to the problems I experienced, so assuming you think in the same manner as OP was written, you will be fine. I do not, so... I wasn't.

Regardless, it's been several years since I last rooted a device and the landscape has changed drastically, even xda is much harder to navigate intuitively. From what I've read, if you spend enough time playing with the filters it will become easier but, idk. Apparently the old structure was much more computationally taxing, thus expensive, which drove their operational considerations to this new model.

I'm going to spend some time on CalyxOS and Graphene in order to see what the daily experience of their individual security model feels like. It's too bad, because I like the experience of Android 12 - minus Google's fixation on social engineering. It has a few thoughtful QoL features that I would have used if I were able to exist within Google's software ecosystem.

Anyway, good luck.
 
  • Like
Reactions: roirraW "edor" ehT

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
Once bootloader is unlocked, which you should do literally first thing, I do not believe that a carrier could lock the device even if they wanted to. My experience was that the fastboot process was unreliable and that the step-by-step guide made certain linguistic assumptions that I had difficulty following. I have to imagine those breaks in comprehension led to the problems I experienced, so assuming you think in the same manner as OP was written, you will be fine. I do not, so... I wasn't.

Regardless, it's been several years since I last rooted a device and the landscape has changed drastically, even xda is much harder to navigate intuitively. From what I've read, if you spend enough time playing with the filters it will become easier but, idk. Apparently the old structure was much more computationally taxing, thus expensive, which drove their operational considerations to this new model.

I'm going to spend some time on CalyxOS and Graphene in order to see what the daily experience of their individual security model feels like. It's too bad, because I like the experience of Android 12 - minus Google's fixation on social engineering. It has a few thoughtful QoL features that I would have used if I were able to exist within Google's software ecosystem.

Anyway, good luck.
Ok I got to the part I think where I can flash magisk but when trying to sideload apk it says

\Magisk>adb sideload app-release (1).apk
adb.exe: sideload requires an argument

Ok I installed it from phone and rebooted pc. I got it installed now.
Also playstore not certified for some reason but I am guessing cause bootloader unlocked
 
Last edited:

The.Jericho.Initiative

Senior Member
Jan 3, 2009
123
102
Texas
Ok I got to the part I think where I can flash magisk but when trying to sideload apk it says

\Magisk>adb sideload app-release (1).apk
adb.exe: sideload requires an argument

Ok I installed it from phone and rebooted pc. I got it installed now.
Also playstore not certified for some reason but I am guessing cause bootloader unlocked

Once magisk is installed, go into the app's settings and enable Zygist, then hide Magisk and specify a name, enforce a deny list and put whatever banking or commerce apps you feel necessary, then download Safetynet fix 2.2.1, and you should be good to go, if playstore is a problem after this, delete the app data and reboot - then open it.

Also, I don't know my ass from a hole in the ground - I'm just figuring it out as I go - so take this advice in the spirit it's given, but not as an authoritative source. I hope this helps, and I hope you had a Merry Christmas.


Here's a thread that discusses it in depth:

 
  • Like
Reactions: roirraW "edor" ehT

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
Once magisk is installed, go into the app's settings and enable Zygist, then hide Magisk and specify a name, enforce a deny list and put whatever banking or commerce apps you feel necessary, then download Safetynet fix 2.2.1, and you should be good to go, if playstore is a problem after this, delete the app data and reboot - then open it.

Also, I don't know my ass from a hole in the ground - I'm just figuring it out as I go - so take this advice in the spirit it's given, but not as an authoritative source. I hope this helps, and I hope you had a Merry Christmas.


Here's a thread that discusses it in depth:

safetynet-fix-v2.2.0 is the version I got but i gt figure out how to flash it or install it.

Ok got the new version downloaded and installed through modules. Everything good so far. Google play certified.

But where the check safety net button?
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

whatsisnametake2

Senior Member
i currently have 036 firmware on my 6 pro, ie pre dec update. i would like to unlock and root without updating to dec update for the time being. will the latest canary version root this previous firmware ok as well without the need to disable verity\verification?
 

Lughnasadh

Senior Member
Mar 23, 2015
3,327
3,297
Google Nexus 5
Huawei Nexus 6P
i currently have 036 firmware on my 6 pro, ie pre dec update. i would like to unlock and root without updating to dec update for the time being. will the latest canary version root this previous firmware ok as well without the need to disable verity\verification?
Yes and yes. Just be advised your data will be wiped when unlocking the bootloader, in case you weren't aware.

EDIT: There was a change to Magisk 23016 that allowed it to be rooted on the December update (Load fstab from system/etc). I'm actually not sure if the changes would affect rooting on the November update. However, this particular change only affected the rooting process. There is still no need to disable verity/verification.

 
Last edited:

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
Not sure if this is the right place but I have root and am running into a problem. I cannot access system to change bootanimation. It says item root read only. But all my other root apps work fine.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Not sure if this is the right place but I have root and am running into a problem. I cannot access system to change bootanimation. It says item root read only. But all my other root apps work fine.
If I remember correctly, I think for several years now root runs without actually making the system partition writable. Or am I confused? Hopefully, someone who knows better will chime in. :D
 
  • Like
Reactions: Lughnasadh

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
If I remember correctly, I think for several years now root runs without actually making the system partition writable. Or am I confused? Hopefully, someone who knows better will chime in. :D
I been able to do it on my pixel xl gen 1 running custom os (pixelexperience) android 11 fine. Also, I am using fx explorer. But pixel 6 pro i cant.

Might be the new way android 12 is?
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
I been able to do it on my pixel xl gen 1 running custom os (pixelexperience) android 11 fine. Also, I am using fx explorer. But pixel 6 pro i cant.

Might be the new way android 12 is?
I thought it depended on the method of root and/or may be related to "systemless root". I'm grasping at straws because unfortunately, I don't remember the details since I rarely try that level of customization anymore.
 

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
I thought it depended on the method of root and/or may be related to "systemless root". I'm grasping at straws because unfortunately, I don't remember the details since I rarely try that level of customization anymore.
Might be the explorer I use for file management just not upgraded to android 12 support yet. Not sure what ones are out there.
 
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    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.
    1
    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:

    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.
    1
    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)...
    1
    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 👍
    1
    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.
  • 61
    Ready to Unlock, Root, and Update factory images on your Pixel 6 Pro?

    There are some really good guides by V0latyle here & here, and by roirraW "edor" ehT here which are great for veteran/regular users who are really familiar with adb/fastboot and the commands, steps used in the unlocking, rooting environment.

    This step by step is for people like ME who are not adb/fastboot gurus, who need every step spelled out so we don't brick our over-priced flagship devices :D


    What
    You Need On Your PC:

    Factory Image
    MAGISK - Stable 24.3 (for April update) Some are using latest CANARY with no issues - YMMV)
    SDK Platform Tools & USB Drivers (first time installation)

    (additional files I use: optional)

    Working SafetyNet @Pekempy
    Kirisakura Kernel @Freak07


    -download latest factory image, unzip the MAIN image.zip, then unzip the SECONDARY image.zip , copy the contents of the SECOND image.zip into the same platform tools folder that has the fastboot application in it, then open the image.zip you just copied into the fastboot folder and copy the boot.img and paste it somewhere on your PC.

    Device Setup PRIOR To Starting Fastboot:

    Settings>About phone>Build Number (click build number until you see YOU ARE NOW A DEVELOPER)
    Settings>System>Advanced>Developer Options
    Enable OEM Unlocking & USB Debugging & USB Configuration> enable FILE TRANSFER

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


    Unlock the Bootloader, Update Factory Image, and Get Root:

    1- Boot your device into bootloader/fastboot (hold power / vol down)

    2- Connect USB cable to device and PC ( have diff USB cables available for troubleshooting)

    3- From address bar in the platform tools folder where the fastboot application is located on your PC, type CMD to open command prompt window

    4- Type FASTBOOT DEVICES, if you see a serial number(s) you are ready, if you don't, verify you've properly set up platform tools folder, change cable, check command, try again)

    5- TO UNLOCK BOOTLOADER- type fastboot reboot bootloader
    (***YOUR DATA WILL BE WIPED***)

    6- Type fastboot flashing unlock

    7- Type fastboot reboot bootloader


    PRIOR TO FLASHING THE FACTORY IMAGE:

    -if you want a clean install, WIPING ALL DATA, skip to step #8
    -if you want to SAVE data, edit the FLASH ALL.bat file, REMOVING the -w (leaving just ONE space between the remaining text) and SAVE the file (reopen file to verify -w is removed)

    8- Flash the factory image by typing FLASH-ALL

    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)


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

    11- Install Magisk (for April update use Stable 24.3, but some are using latest 24.3 CANARY with no issues - YMMV)), follow instructions to allow files like this to be installed)

    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


    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

    4- Type FLASH-ALL

    5- Let it boot into system and settle for a minute

    6- Patch the boot image (follow steps 10, 12 -18 above)


    *** Thanks to V0latyle, roirraW "edor" ehT, and Lughnasadh for the foundations of these instructions! ***

    Please let me know if any part of this process is incorrect, has been updated, or is no longer necessary (y) (y) (y)
    5
    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!
    5
    Right, I wanted to wipe. It's a brand new phone that was on .036, and not yet activated. I'm wondering if I did wipe, with the --disable-verity --disable-verification into the .bat file, am I good to go ahead and install Magisk, and from now on, not wipe on future updates, or do I have to do this extra step after (fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img)?
    Oh, you wanted to wipe, lol. My misunderstanding. Yeah, what @Az Biker said.
    It appears that everything is fine. I have Magisk installed after patching image. I'm not getting any modules to pop up in the search though, so I guess I'll head to Magisk thread to see what's up there.
    The Magisk Repo has been removed from the Magisk app. You can use this instead...

    4
    You shouldn't need to flash to both slots. So you can just do fastboot flash boot <nameofpatchedbootimage.img>.

    You should be able to rename the patched boot image (although I have never done it). I usually just put it in a labeled folder and copy and paste the name into the command prompt.

    You should be patching the boot.img that you extracted from the factory image. It's located in the image-raven-sd1a.210817..037 zip file within the factory image (assuming you are on build .037).

    If you are still having problems, then 2 things to check:
    1. Make sure your Platform Tools are up-to-date. Latest I believe is 31.0.3
    2. Make sure you have the correct (and latest) USB drivers installed on your computer... https://developer.android.com/studio/run/win-usb

    EDIT: Oh, one very important thing. Make sure you are using the latest Canary version of Magisk.
    Root has been achieved, thank you for your time & assistance, it's much appreciated. ✌️
    4
    Maybe it makes more sense to combine and improve upon existing tutorials, instead of creating a load of new ones. It's getting a bit confusing here, ESPECIALLY since we don't have any sub-threads/forums.

    Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!