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

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
:oops::oops::oops: I need to find a new source! Thanks!
I use Aignes Website Watcher on the computer asking with the Website Watcher app that syncs with it through DropBox, to let me know when certain webpages have new material. 😁

Only using the free versions of stuff for now but that program has been around roughly 20 years or maybe longer. Not cheap for the paid version, but might have to spring for it someday. It might get lifetime updates, at least, and the updates aren't arbitrary.
 

Negan

Forum Moderator / Recognized Themer
Staff member
So I have not rooted since my old Nexus 6P but with losing the fabricated overlays with January update I finally pulled the trigger. Unreal how the process has changed since then. Never have I used magisk or done any of this before. Back in the day it was , unlock, flash twrp, flash SuperSU and bobs your uncle. I think I'm good to go now. And next I gotta see what kind of tinkering I can do. I may have to revive some of my old subs themes or something else.
Screenshot_20220116-122815.png
Screenshot_20220116-123922.png
 

roirraW "edor" ehT

Forum Moderator
Staff member
Will this work for those with a Verizon unlocked device?
You can only root a phone if you can unlock the bootloader. Verizon phones have always come Carrier unlocked from the start, but you can't unlock the bootloader. It's either always been like this or been like this for so long (since before my first Android phone in 12 years ago).

There have been a few lucky ways around it on some Verizon devices but it's nearly impossible anymore unless you just get lucky.

The simple answer is no, you can't do this with a Verizon device. Now if you buy a factory unlocked (meaning unlockable bootloader) and happen to use it with Verizon, then yes, you can still root it since you'll be able to unlock the bootloader.

Folks with the T-Mobile variant of the P6P are also lucky. They just have to talk to the right person in customer service to get their phones permanently carrier unlocked, and by chance that also enables their ability to unlock the bootloader as well.
 

thepersona

Senior Member
Nov 9, 2018
288
33
Google Pixel 4 XL
Sony Xperia 5 II
You can only root a phone if you can unlock the bootloader. Verizon phones have always come Carrier unlocked from the start, but you can't unlock the bootloader. It's either always been like this or been like this for so long (since before my first Android phone in 12 years ago).

There have been a few lucky ways around it on some Verizon devices but it's nearly impossible anymore unless you just get lucky.

The simple answer is no, you can't do this with a Verizon device. Now if you buy a factory unlocked (meaning unlockable bootloader) and happen to use it with Verizon, then yes, you can still root it since you'll be able to unlock the bootloader.

Folks with the T-Mobile variant of the P6P are also lucky. They just have to talk to the right person in customer service to get their phones permanently carrier unlocked, and by chance that also enables their ability to unlock the bootloader as well.
If I called and requested for Verizon to carry your unlock my phone since I'm in Canada a country that doesn't Have Verizon as a carrier. Could that provide me some leverage with them or the representative being able to do it?
 

roirraW "edor" ehT

Forum Moderator
Staff member
If I called and requested for Verizon to carry your unlock my phone since I'm in Canada a country that doesn't Have Verizon as a carrier. Could that provide me some leverage with them or the representative being able to do it?
No. Verizon phones are already carrier unlocked like I said. You don't have to use the Verizon phone with Verizon. You can use it with a carrier in Canada. You just can't unlock the bootloader. Verizon never allows bootloaders to be unlocked.
 
  • Like
Reactions: Az Biker

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs
Staff member
So I have not rooted since my old Nexus 6P but with losing the fabricated overlays with January update I finally pulled the trigger. Unreal how the process has changed since then.
Never have I used magisk or done any of this before. Back in the day it was , unlock, flash twrp, flash SuperSU and bobs your uncle. I think I'm good to go now. And next I gotta see what kind of tinkering I can do. I may have to revive some of my old subs themes or something else.
View attachment 5510199View attachment 5510201


Yep, the days of unlock bootloader, flash, flash, flash in three minutes are over (hopefully not forever, but seemingly).

I'm lazy, only flashing every other update, so I'm prolly waiting for the P6P February update :D
 
Last edited:

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs
Staff member
estoy en rom el 36 de noviembre

yo era root, asi que vea la imagen de arranque de noviembre para perder la raiz
Actualicé a enero por ota adb, falló 7 en 47%
Al reiniciar, perdí las opciones de desarrollador y tocando 7 veces en la compilación no abre las opciones de desarrollador.
como puedo recuperarlos

Edito, por ota en android tampoco se actualiza

No sé cómo, pero he logrado actualizar siguiendo esto
actualice el zip completo y actualice el gestor de arranque antes de actualizar todo
[GUÍA] Rootear Pixel 6 "oriole" con Magisk

Please post in English. If a second language is required, post it below the English comment as I have done here. Thank you. Google Translate

Por favor publique en inglés. Si se requiere un segundo idioma, publíquelo debajo del comentario en inglés como lo he hecho aquí. Gracias.
 

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs
Staff member
Meh.... went ahead and updated to January 007, Kirisakura 1.50, and SafetyNet 2.12

Smooth, silky, easy like Sunday mornin' update!

Not gloating (seriously, I'm not) but since I didn't really have any issues with my device prior to the Jan update, I'm not sure if I'll notice any improvements..

It's good to be the king - Mel Brooks (okay, just a little gloating :p )
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
3,327
3,297
Google Nexus 5
Huawei Nexus 6P
I think I read there's an alpha Magisk version that allows for OTA up and running.

Anyone confirm that, or has anyone used it?

I need to add OTA instructions to the OP but I have never used OTA myself.
The latest Canary does as well. It was tested by someone on the Pixel 5a and 6 with success, but we'll probably have to wait until February for a 100% verification.

Can't really say anything about Alpha but it is usually a step or two ahead of Canary.
 

Dragon Kumera

Senior Member
Mar 14, 2019
323
105
The latest Canary does as well. It was tested by someone on the Pixel 5a and 6 with success, but we'll probably have to wait until February for a 100% verification.

Can't really say anything about Alpha but it is usually a step or two ahead of Canary.
I plan to try February update ota with the 23018 version. Since I already have the January update, I cannot do it.
 

kheltek

Senior Member
Feb 25, 2013
326
157
Question for anyone on Kiri's kernel: can I update magisk directly or do I need to patch the original boot image, flash the new patched img, then reflash the kernel? Many thanks.
 

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