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

[roirraW "edor" ehT]

I personally did not flash A1. I chose the US Carriers version.

Me too, since as far as my understanding, the main differences between the versions are radio optimizations for the carriers available in the region the firmware is intended for.

 

[Nergal di Cuthah]

I too, chose US carriers, as far as I've seen A1 is for Canada (and Australia before they got their own branch)

 

[whatsisnametake2]

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?

 

[roirraW "edor" ehT]

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]

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?

 

[roirraW "edor" ehT]

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]

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]

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.

 

[Dragon Kumera]

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

 

[The.Jericho.Initiative]

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.

Release v2.2.1 (Zygisk) · kdrag0n/safetynet-fix

Changes Fixed under-display fingerprint sensor on Realme devices (thanks @osm0sis, @byxiaorun, @Jowat97) Clarified definition of "basic attestation" in readme Add check to prevent installation on ...

github.com

Here's a thread that discusses it in depth:

Working SafetyNet with Pixel 6 Pro Android 12

This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...

forum.xda-developers.com

 

[Dragon Kumera]

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.

Release v2.2.1 (Zygisk) · kdrag0n/safetynet-fix

Changes Fixed under-display fingerprint sensor on Realme devices (thanks @osm0sis, @byxiaorun, @Jowat97) Clarified definition of "basic attestation" in readme Add check to prevent installation on ...

github.com

Here's a thread that discusses it in depth:

Working SafetyNet with Pixel 6 Pro Android 12

This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...

forum.xda-developers.com

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?

 

[The.Jericho.Initiative]

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?

I downloaded YASNAC and GPay to verify the status.

 

[whatsisnametake2]

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]

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.

Load fstab from system/etc · topjohnwu/[email protected]

Caused by this commit: https://cs.android.com/android/_/android/platform/system/core/+/e98afa2687eb56184dad8569b929eba04fb93068 Fix #5057

github.com

 

[Dragon Kumera]

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]

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.

 

[Dragon Kumera]

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.

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?

 

[roirraW "edor" ehT]

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]

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.

 

[roirraW "edor" ehT]

Might be the explorer I use for file management just not upgraded to android 12 support yet. Not sure what ones are out there.

I use X-plore File Manager (including for root access - you have to enable in it's Settings), but as I said, I haven't tried doing what you're doing...yet.