• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

How To Guide Unlocking the Pixel 6 Pro bootloader & general central repository of relevant links - January 2022 update available now

Search This thread

Norma Stitz

Senior Member
Jan 2, 2011
180
91
Redmond
LG V10
LG V20
In my upgrade 8 seemed to have lost Google Pay access. It was confirmed working in 0.36.

Can anyone confirm GPay working in 0.37? I figured I'd at least check before starting over.

Screenshot_20211122-130537.png
 

Norma Stitz

Senior Member
Jan 2, 2011
180
91
Redmond
LG V10
LG V20
In my upgrade 8 seemed to have lost Google Pay access. It was confirmed working in 0.36.

Can anyone confirm GPay working in 0.37? I figured I'd at least check before starting over.

View attachment 5465505
Oh wtf? Gpay appears to be working again. I swear it was giving me the bootloader detection error a few days ago, and I've none nothing since then. Maybe it has a short memory.

I'll have to make a purchase later to confirm, but it appears I no longer have a problem.
 
  • Like
Reactions: roirraW "edor" ehT

hanschke

Senior Member
Mar 30, 2007
1,678
218
I got my phone yesterday and have done a full upgrade to latest factory image before I have done anything ;)

I have unlocked the bootloader and maybe I have taken the wrong magisk build but patched the boot.img and stuck on it after flashing it. If I try do disable --disable-verity --disable-verification I stuck on fastboot with I cannot boot into do a wipe. Does I need the wipe?
 

Morgrain

Senior Member
Aug 4, 2015
753
755
I have unlocked the bootloader and maybe I have taken the wrong magisk build but patched the boot.img and stuck on it after flashing it. If I try do disable --disable-verity --disable-verification I stuck on fastboot with I cannot boot into do a wipe. Does I need the wipe?
Which magisk build did you use? There shouldn't be a "maybe" when you tinker with your device - check the guides and then check the version that you downloaded, if you have the incorrect version, that should be obvious rather quickly.

Does the system give you any sort of error message?

Your text is a bit incomprehensible, since there are a couple of information missing (maybe read over it again, add what's missing & iron out the typing errors?)

In case you run into a bootloader message like "failed to load/verify boot images", you forgot to disable verity and verification BEFORE booting (wipe required).

As the OP explains (please always read the guides thoroughly before you attempt to tinker with your phone)

Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.

Likewise, when wanting to root you have to disable verity and verification, after which you'll need to wipe the phone [again], so best just to go ahead and disable these immediately after unlocking the bootloader. See the section below "A list of the other important guides".

As a general statement: Permanent root currently requires a double wipe!

You should also take a look into the linked guides, like that one

 

Dragon Kumera

Senior Member
Mar 14, 2019
277
73
The unlock process works like this;

1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Tap it until it says you're a developer.
4) Back --> Network --> Wifi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
6) # adb reboot-bootloader
7) # fastboot flashing unlock

Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.

Just thought to add something. It wont ask you for anything google sign in related unless connecting to wifi. So if you skip that and then do it, you can bypass that.
 

roirraW "edor" ehT

Forum Moderator
Staff member
https://source.android.com/security/bulletin/pixel/2021-12-01

The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2021-12-05 or later address all issues in this bulletin and all issues in the December 2021 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.

All supported Google devices will receive an update to the 2021-12-05 patch level. We encourage all customers to accept these updates to their devices.

Note: The Google device firmware images are available on the Google Developer site.

Announcements​

  • In addition to the security vulnerabilities described in the December 2021 ndroid Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

Security patches​

Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

Android TV​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2021-1000A-185190688EoPModerate12
CVE-2021-1033A-185247656EoPModerate12

Framework​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2021-0981A-191981182EoPModerate12
CVE-2021-0984A-192475653EoPModerate12
CVE-2021-0985A-190403923EoPModerate12
CVE-2021-1019A-195031401EoPModerate12
CVE-2021-1024A-191283525EoPModerate12
CVE-2021-0978A-192587406IDModerate12
CVE-2021-0979A-191772737IDModerate12
CVE-2021-0982A-192368508IDModerate12
CVE-2021-0983A-192245204IDModerate12
CVE-2021-0986A-192247339IDModerate12
CVE-2021-0988A-191954233IDModerate12
CVE-2021-1009A-189858128IDModerate12
CVE-2021-1010A-189857801IDModerate12
CVE-2021-1011A-188219307IDModerate12
CVE-2021-1013A-186404356IDModerate12
CVE-2021-1030A-194697001IDModerate12
CVE-2021-1031A-194697004IDModerate12
CVE-2021-1032A-184745603IDModerate12
CVE-2021-0993A-193849901DoSModerate12

Media Framework​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2021-1003A-189857506EoPModerate12
CVE-2021-1027A-193033243EoPModerate12
CVE-2021-1028A-193034683EoPModerate12
CVE-2021-1029A-193034677EoPModerate12
CVE-2021-0976A-199680600IDModerate12
CVE-2021-0998A-193442575IDModerate12
CVE-2021-1001A-190435883IDModerate12
CVE-2021-1002A-194533433IDModerate12
CVE-2021-1018A-194110891IDModerate12

Messaging​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2021-0973A-197328178IDModerate12

System​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2021-0769A-184676316EoPModerate12
CVE-2021-0977A-183487770EoPModerate12
CVE-2021-0992A-180104327EoPModerate12
CVE-2021-0999A-196858999EoPModerate12
CVE-2021-1004A-197749180EoPModerate12
CVE-2021-1016A-183610267EoPModerate12
CVE-2021-1017A-182583850EoPModerate12
CVE-2021-1020A-195111725EoPModerate12
CVE-2021-1021A-195031703EoPModerate12
CVE-2021-0987A-190619791IDModerate12
CVE-2021-0989A-194105812IDModerate12
CVE-2021-0990A-185591180IDModerate12
CVE-2021-0991A-181588752IDModerate12
CVE-2021-0994A-193801134IDModerate12
CVE-2021-0995A-197536547IDModerate12
CVE-2021-0996A-181346545IDModerate12
CVE-2021-0997A-191086488IDModerate12
CVE-2021-1005A-186530889IDModerate12
CVE-2021-1006A-183961974IDModerate12
CVE-2021-1007A-167759047IDModerate12
CVE-2021-1012A-195412179IDModerate12
CVE-2021-1014A-186776740IDModerate12
CVE-2021-1015A-186530496IDModerate12
CVE-2021-1023A-195963373IDModerate12
CVE-2021-1025A-193800652IDModerate12
CVE-2021-1026A-194798757IDModerate12
CVE-2021-1034A-193441322IDModerate12
CVE-2021-1008A-197327688DoSModerate12
CVE-2021-1022A-180420059DoSModerate12

Kernel components​

CVEReferencesTypeSeverityComponent
CVE-2020-25668A-190228658
Upstream kernel
EoPModerateKernel
CVE-2021-23134A-188883590
Upstream kernel
EoPModerateNFC
CVE-2021-33200A-190011721
Upstream kernel [2] [3]
EoPModerateKernel
CVE-2021-39656A-174049066
Upstream kernel
EoPModerateKernel
CVE-2021-39636A-120612905
Upstream kernel [2] [3] [4] [5]
IDModerateKernel
CVE-2021-39648A-160822094
Upstream kernel
IDModerateKernel
CVE-2021-39657A-194696049
Upstream kernel
IDModerateKernel

Pixel​

CVEReferencesTypeSeverityComponent
CVE-2021-39639A-198291476 *EoPHighBootloader
CVE-2021-39640A-157294279 *EoPHighUSB
CVE-2021-39644A-199809304 *EoPHighBootloader
CVE-2021-39645A-199805112 *EoPHighBootloader
CVE-2021-1047A-197966306 *IDHighTitan M2
CVE-2021-39638A-195607566 *EoPModerateCamera
CVE-2021-39641A-126949257 *EoPModerateBootloader
CVE-2021-39642A-195731663 *EoPModerateCamera
CVE-2021-39643A-195573629 *EoPModerateTitan M2
CVE-2021-39649A-174049006 *EoPModerateAudio
CVE-2021-39650A-169763055 *EoPModerateKernel
CVE-2021-39651A-193438173 *EoPModerateBiometrics
CVE-2021-39652A-194499021 *EoPModerateTouch
CVE-2021-39653A-193443223 *EoPModerateBootloader
CVE-2021-39655A-192641593 *EoPModerateKernel
CVE-2021-1046A-195609074 *IDModerateCamera
CVE-2021-39637A-193579873 *IDModerateSystem
CVE-2021-39646A-201537251 *IDModerateBootloader
CVE-2021-39647A-198713939 *IDModerateBootloader

Qualcomm components​

CVEReferencesSeverityComponent
CVE-2021-30298A-190408641
QC-CR#2873209 [2]
ModerateKernel

Functional patches​

For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

Common questions and answers​

This section answers common questions that may occur after reading this bulletin.

1. How do I determine if my device is updated to address these issues?

Security patch levels of 2021-12-05 or later address all issues associated with the 2021-12-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.

2. What do the entries in the Type column mean?

Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.

AbbreviationDefinition
RCERemote code execution
EoPElevation of privilege
IDInformation disclosure
DoSDenial of service
N/AClassification not available
3. What do the entries in the References column mean?

Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.

PrefixReference
A-Android bug ID
QC-Qualcomm reference number
M-MediaTek reference number
N-NVIDIA reference number
B-Broadcom reference number
U-UNISOC reference number
4. What does an * next to the Android bug ID in the References column mean?

Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.

5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?

Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

Versions​

VersionDateNotes
1.0December 6, 2021Bulletin Released

@henihazbay posted a better format post about the December update here:

https://support.google.com/pixelphone/thread/139017133/google-pixel-update-december-2021?hl=en:


Camille V.Community Manager
1 hr
Google Pixel Update - December 2021
Hello Pixel Community,
We have provided the monthly software update for December 2021. All supported Pixel devices running Android 12 will receive these software updates as part of the December 2021 update, which begins rolling out to users today. The rollout will continue over the next month in phases depending on carrier and device. The rollout will start on Pixel 6 and Pixel 6 Pro later this month. We will provide an update to this post once it is available. Users will receive a notification once it becomes available. We encourage you to check your Android version and update to receive the latest software.
Details of this month’s security fixes can be found on the Android Security Bulletin:
https://source.android.com/security/bulletin
Thanks,
Google Pixel Support Team

Software versions
Global

  • Pixel 3a (XL): SQ1A.211205.008
  • Pixel 4 (XL): SQ1A.211205.008
  • Pixel 4a: SQ1A.211205.008
  • Pixel 4a (5G): SQ1A.211205.008
  • Pixel 5: SQ1A.211205.008
  • Pixel 5a (5G): SQ1A.211205.008
What’s included
In addition to new features, the December 2021 update includes several fixes and improvements across many areas including device performance, stability, connectivity, and more – see below for some notable improvements.
Apps
  • Fix for issue causing Assistant to unintentionally start a phone call in certain conditions *[1].
  • Fix for stuck or frozen app UI in certain conditions *[7].
Audio
  • General fixes & improvements for audio playback issues in certain apps *[1].
  • Fix for issue causing audio noise in videos captured while using certain phone cases *[1].
  • Fix for issue causing microphone to cut out during calls in certain conditions *[1].
  • Fix for issue causing occasional audio glitch when adjusting volume levels *[1].
  • Fix for issue occasionally preventing audio playback from speaker in certain conditions *[1].
  • Fix for issue preventing Now Playing to search for unrecognized music *[1].
Battery & Power
  • Additional improvements for battery charging information shown in notification shade *[4].
  • General improvements for battery & thermal performance in certain conditions *[7].
  • General improvements for wireless charging in certain conditions *[5].
  • Improvements for alignment detection on Pixel Stand in certain conditions *[5].
  • Fix for issues occasionally causing incorrect Battery usage accounting to display in Settings *[7].
Biometrics
  • General improvements for fingerprint sensor stability & performance *[1].
  • Additional fixes for issues preventing enrollment of new fingerprints in certain conditions *[1].
  • General improvements for face unlock stability & performance *[6].
Bluetooth
  • General Bluetooth stability improvements for certain conditions *[3].
  • Fix for distorted audio over Bluetooth in certain scenarios *[1].
  • Fix for issue causing Bluetooth to turn on after disabling in certain conditions *[7].
  • Fix for volume adjustment issues with certain Bluetooth audio devices *[7].
Camera
  • General image quality improvements in camera preview/capture *[1].
  • General improvements for camera stability & performance *[1].
  • General improvements for auto-focus response in certain capture modes *[1].
  • General improvements for color consistency in viewfinder preview *[1].
  • Fix for issue causing blank viewfinder preview in certain conditions *[1].
Display & Graphics
  • Enable ANGLE graphics support library for certain apps and games *[1].
  • Add additional example images for display color options in Settings *[7].
  • General improvements to keep the screen on after multiple manual wakes *[7].
  • General improvements for Adaptive brightness response in certain conditions *[7].
  • Fix for occasional screen flicker during brightness adjustment *[1].
  • Fix for issue preventing Smooth Display to switch display refresh rate in certain conditions *[1].
  • Fix for issue causing screen flicker after locking or unlocking device in certain conditions *[1].
  • Fix for occasional white screen flash after display goes to sleep *[7].
Framework
  • Fix for issue causing app icons to display as pending downloads after installation completes *[7].
  • Fix for issue causing Play store app installation to pause indefinitely in certain conditions *[7].
  • Fix for issue occasionally preventing Work Profile setup to complete in certain conditions *[7].
  • Fix for issue preventing all settings or apps to be restored from backup during setup in certain conditions *[7].
Media
  • Fix for issue causing system crash during media playback in certain conditions *[7].
Network & Telephony
  • General improvements for network connection stability & performance *[7].
  • Fix for crash in Settings when toggling Airplane mode on certain network configurations *[7].
  • Fix for issue that disabled call features on certain devices or networks in certain conditions *[1].
Sensors
  • General improvements for sensor stability & response in certain conditions *[2].
  • General improvements for Quick Tap response & performance *[2].
  • General improvements for Auto-rotate response in certain device orientations *[4].
  • General improvements for Adaptive brightness response in certain conditions *[7].
  • Fix for issue preventing lift to wake and double tap to wake in certain conditions *[1].
  • Fix for issue preventing Always-on-display from turning on in certain conditions *[1].
  • Fix for issue causing unexpected haptics or vibration in certain conditions *[1].
System
  • Kernel update to 4.9.279 for Pixel 3a & Pixel 3a XL.
  • Kernel update to 4.14.243 for Pixel 4, Pixel 4 XL & Pixel 4a.
  • Kernel update to 4.19.202 for Pixel 4a (5G), Pixel 5 & Pixel 5a (5G).
  • General improvements for system stability & performance *[7]
  • Fix for issue causing device to freeze after sleeping while charging in certain conditions *[1].
  • Fix for issue occasionally preventing OTA updates to install *[7].
User Interface
  • Add Material You dynamic theming support for the device boot animation *[7].
  • Improvements for Internet tile in Quick Settings *[7].
  • Improvements for Quick Settings layout in certain device orientations *[7].
  • Fix for issue causing display to stay on during wireless charging *[5].
  • Fix for issue causing Game Dashboard icon to display over lock screen *[7].
  • Fix for issue causing incorrect colors or theme to display in Quick Settings in certain conditions *[7].
  • Fix for issue causing lock screen icons to display in notification shade in certain conditions *[7].
  • Fix for issue causing notification History & Clear all buttons to occasionally display incorrectly *[7].
  • Fix for issue causing persistent app media controls in notification shade in certain conditions *[7].
  • Fix for issue causing persistent call notification in certain conditions *[7].
  • Fix for issue causing persistent Turn off work apps button in app drawer *[7].
  • Fix for issue causing screen flicker after locking or unlocking device in certain conditions *[7].
  • Fix for issue causing Settings to crash in Conversations menu in certain conditions *[7].
  • Fix for issue causing undismissable Game Dashboard button during gameplay in certain conditions *[7].
  • Fix for issue causing app drawer to scroll to the top after clearing search query *[7].
  • Fix for issue causing certain home screen icons to appear misaligned in certain conditions *[7].
  • Fix for issue enabling Quick Settings toggles to be tapped from home screen in certain conditions *[7].
  • Fix for issue hiding date or time in Quick Settings in certain conditions *[7].
  • Fix for issue occasionally causing blank background on home screen after setting wallpaper *[7].
  • Fix for issue occasionally causing Quick Settings to pull down after unlocking device *[7].
  • Fix for issue occasionally causing UI elements to display with transparent backgrounds *[7].
  • Fix for issue occasionally displaying Work Profile badge icon on personal apps or contacts *[7].
  • Fix for issue preventing conversation bubble to be dismissed in certain conditions *[7].
  • Fix for issue preventing search results to display in Settings in certain conditions *[7].
  • Fix for occasional screen flicker in notification shade when dragging from top of screen *[7].
  • Fix for occasional flickering when quickly switching between apps in certain conditions *[7].
Wi-Fi
  • General improvements for Wi-Fi stability & performance *[7].
  • Fix for issue that would occasionally disconnect device from Wi-Fi in certain conditions *[1].
----------------------------------------------------------------
Device Applicability
*[1] Included on Pixel 6 & Pixel 6 Pro
*[2] Included on Pixel 4a (5G), Pixel 5, Pixel 5a (5G), Pixel 6 & Pixel 6 Pro
*[3] Included on Pixel 4a (5G), Pixel 5, Pixel 5a (5G)
*[4] Included on Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a (5G), Pixel 6 & Pixel 6 Pro
*[5] Included on Pixel 4 / XL, Pixel 5, Pixel 6 & Pixel 6 Pro
*[6] Included on Pixel 4 & Pixel 4 XL
*[7] Included on Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a (5G), Pixel 6 & Pixel 6 Pro
 

Morgrain

Senior Member
Aug 4, 2015
753
755
  • Fix for issue causing microphone to cut out during calls in certain conditions *[1].
I was starting to wonder if I was insane, having to reboot my phone every couple of days because of no outgoing audio.
I've seen that fix with two Pixel phones before. Classic Google. Re-implementing old bugs that are already fixed, just to fix them again.
 
  • Like
Reactions: dr_rick13

roirraW "edor" ehT

Forum Moderator
Staff member
@magooo said here:

This latest Feature Drop will roll out to users over the next few weeks, starting today with relevant updates coming to Pixel 3a through Pixel 5a (5G) devices - see g.co/pixel/updates for details. Pixel 6 and Pixel 6 Pro devices will begin receiving their updates next week.
 

Blade22222

Senior Member
Oct 12, 2012
186
62
Quick question, the only way to relock the bootloader is with the fastboot command right? I'm on verizon and want to flash that factory image for the modems and dont want to end up with a locked bootloader.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Quick question, the only way to relock the bootloader is with the fastboot command right? I'm on verizon and want to flash that factory image for the modems and dont want to end up with a locked bootloader.
Correct. It doesn't matter what you flash, it can't relock your bootloader.
 
  • Like
Reactions: Blade22222

Top Liked Posts

  • 4
    Magisk Canary 23018 is out at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.

    Unhide the Magisk app before updating.

    3
    Do you usually re-patch the boot.img with the newest Magisk before upgrading Magisk itself? I know I don't but I wonder if I should. Although, I guess "direct install" in Magisk does that?
    My steps for updating are:
    1. Unhide Magisk.
    2. Update from within the app.
    3. Then yes, I use Direct Install.
    4. Reboot and re-hide the app. :)
    2

    Magisk has come a long way. I remember back in the CyanogenMod days where there was the built in su manager , or SuperSU 😅 good ol days
    1
    Magisk Canary 23018 is out at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.

    Unhide the Magisk app before updating.
    Do you usually re-patch the boot.img with the newest Magisk before upgrading Magisk itself? I know I don't but I wonder if I should. Although, I guess "direct install" in Magisk does that?
  • 4
    Magisk Canary 23018 is out at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.

    Unhide the Magisk app before updating.

    4
    January update coming Monday, January 17th, 2022 available now!

    Monday
    3
    Do you usually re-patch the boot.img with the newest Magisk before upgrading Magisk itself? I know I don't but I wonder if I should. Although, I guess "direct install" in Magisk does that?
    My steps for updating are:
    1. Unhide Magisk.
    2. Update from within the app.
    3. Then yes, I use Direct Install.
    4. Reboot and re-hide the app. :)
    3
    Sorry that I need to confirm this statement:

    1. If I want to clean flash ROM, I don't need to key-in comment "fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img" before flashing magisk patched boot img file, right ?
    Correct, not needed as of Magisk Canary build 23016. (Unless you plan on using a custom kernel that hasn't been updated with the same fixes that Magisk 23016 has. If you're going to use the stock kernel, you're fine.)

    2. If I receive ROM OTA, I download OTA file and extracting boot img and then use magisk v236016 to patch boot img
    file. Then I also needless to key in comment " "fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img" before flashing magisk patched boot img file, right ?
    If you root, do not attempt to take actual over-the-air updates. You should disable that in Developer Options.

    Personally, I use the full factory image zip every time (with "-w " removed so it doesn't wipe). There are other ways to do it as well using Google's OTA zip file, but to some others and myself, it makes more sense to just use the full factory image zip. You need the full boot.img that's inside the second zip that's inside the full firmware zip anyway, to run Magisk on it.

    3. Any magisk new version updated, I just need to update it directly in magisk manager, right ?
    Correct. Always unhide the Magisk app if you've used its option to hide it, update the Magisk app, and then use the new Magisk app to root the new boot.img. I manually flash the new rooted boot.img myself. Your mileage may vary if you attempt Direct Install.
  • 40
    Note that this is mainly for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store. All of this will also apply to any other (carrier-specific) variant of the Pixel 6 Pro which you can achieve an unlocked bootloader on. This includes T-Mobile and AT&T variants. It's likely Verizon variants will never be able to unlock their bootloader, or if so it will require paying the right person to do so.

    Feel free to ask about general questions, but for anything that's specific to your variant, you should use one of the other already existing threads. You'll find Verizon, AT&T, and T-Mobile-related threads in those respective search results.

    Here there be dragons. 🐉 I am not responsible for anything at all. 😹

    Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.


    Likewise, when wanting to root you have to disable verity and verification, after which you'll need to wipe the phone, so best just to go ahead and disable these immediately after unlocking the bootloader. See the section below "A list of the other important guides".


    Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.

    There are no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.


    All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. There are at least one or two other How To Guide threads in this section in which folks discuss how to get around banking app restrictions when you're rooted or just have an unlocked bootloader. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
    If users persist in discussing banking apps in this thread, I will have this thread locked and only update this first post when there is new and updated information regarding the subjects of the title of the thread: Unlocking the Pixel 6 Pro bootloader, rooting, and TWRP. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    Honorable mention to @Jawomo's aodNotify - Notification Light / LED for Pixel 6 Pro! (XDA link) / Notification light / LED for Pixel - aodNotify (Play Store link), which in my opinion restores useful functionality missing in most phones these days. It also solves some subjective issues some folks have with AOD (Always On Display), and/or solves/works around the problem where AOD is required for the optical fingerprint reader to work without the screen being on.​


    Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
    Official Google Pixel Update and Software Repair
    Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
    Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
    OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.

    ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
    • You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
    • For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
    • Thanks to @96carboard for posting the details of unlocking the bootloader, be sure to thank him in his post. Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device. Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, or your local bank's app. If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it. My experience on my Pixel 1 was that there were no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. All of this should still be the case. You will also continue to receive updates. Unlike Samsung, Sony, et cetera, which have major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to keep root/re-root.:


      The unlock process works like this:

      1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on (you can put a SIM card if you want, you just don't have to).
      2) When it starts harassing you to join Google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
      3) Settings --> About --> Build number. Repeatedly tap it until it says you're a developer.
      4) Back --> Network --> WiFi and connect it.
      5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize on the phone when requested.

      Using the Platform Tools previously mentioned in command line/terminal:
      6) #
      Code:
      adb reboot-bootloader
      7) #
      Code:
      fastboot flashing unlock

      Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.

      Official Instructions for Locking/Unlocking the Bootloader
    Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
    I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).

    Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.

    Fastboot/ADB Driver Interface - Official Download Link:
    When flashing a full image or unlocking your bootloader, the fastboot interface is being used.

    First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.

    Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.

    Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
    Official Download Page
    "Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"

    It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).

    Rooting-related


    No longer applies - Things that make rooting more complicated on Android 12
    @V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.

    A list of the other important guides - be sure to thank the respective OPs
    For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.


    TWRP (not made for the Pixel 6 Pro yet - will update when it has)
    I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 6 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel6pro.html.

    Custom kernels for stock ROM(s)

    Factory Images (requires an unlocked bootloader)
    It's also handy to have to the full official firmware available, whether it's to recovery from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 6 Pro (Raven) section: Pixel 6 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.

    Note: You can still get the December 2021 Factory Images and OTA from this thread, if you need them for any reason: Alternate links to December - all full factory images and OTAs available

    Full OTA Images (doesn't require an unlocked bootloader)

    The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.

    Regarding P6P 5G model numbers and capabilities - post #3 below.

    List of all Pixel monthly security bulletins and Play System Updates - post #4 below.

    I may append these first four posts with further useful information or links as needed.
    15
    The unlock process works like this;

    1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
    2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
    3) Settings --> About --> Build number. Tap it until it says you're a developer.
    4) Back --> Network --> Wifi and connect it.
    5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
    6) # adb reboot-bootloader
    7) # fastboot flashing unlock

    Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
    13
    Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.

    Canary 23014

    EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4 👍
    10
    I was able to root my Pixel 6 Pro on Project Fi. I had the Day 1 update applied. Wiping /data was required for the vbmeta thing (and was a good idea in general since I was downgrading the OS version).

    My steps:

    1. Download appropriate factory image for my device.
    2. Download magisk canary (v23 stable fails to patch the boot.img).
    3. Boot phone and run through OOB setup if needed, skip everything.
    4. Enable developer options, then OEM unlock.
    5. Reboot into bootloader.
    6. Modify flash-all script in factory image ZIP and add --skip-reboot to the image flash command (remove the pause and exit commands in the BAT as well if you're using that). You need to keep the -w flag in to wipe /data or else the phone won't boot the rooted image. Normally you don't need to reflash everything but the latest version is not available as a factory image, and doing this ensures every partition is kept the same version. Plus you need to wipe /data anyway.
    7. Connect your phone to PC via USB and run script.
    8. Extract vbmeta.img and boot.img from the image ZIP.
    9. Use fastboot to flash vbmeta.img with the flags listed above.
    10. Reboot and unlock device. Go through OOB experience, you can set up your phone properly this time.
    11. Push the boot.img and app_debug.apk (magisk) to your phone and install the APK., You can use ADB if you enable USB debugging or just find your phone in Windows Explorer and drag and drop (open APK in Files app and enable app install from Files).
    12. Run magisk and patch the boot.img.
    13. Use adb (or Explorer) to pull the patched magisk*.img down to your PC.
    14. Reboot to bootloader
    15. Use fastboot to flash the magisk'd magisk*.img to boot partition.
    16. Boot device.

    You should be rooted now. If something goes wrong go back to step 14 but flash the original boot.img on step 15 instead, that should get you back unrooted and you can see if things are working again (else go back to step 5 to start over).

    Issues/comments:
    1. Magisk Canary removes SafetyNet bypass as well as MagiskHide. Apps which check SafetyNet won't work now.
    2. Magisk won't offer modules for install, not sure if this is normal canary behavior or if the modules aren't compatible due to magisk changes.
    3. OTA updates won't install. I've had this issue with Magisk forever on other devices too. Some people say they should work but I've never seen them work.
    4. Elevation dialog works EXCEPT if you use su from an adb shell. The dialog seems to try to display but it doesn't actually display; probably the overlay is being blocked due to android security thinking it's an uninvited popup, I speculate it's a magisk bug. Terminal won't show up in the list of superuser apps either in Magisk so you can't just toggle it on in there as a workaround. EDIT: I figured out if you Hide Magisk Manager the elevation dialog will no longer work. Unhide as a workaround and grant elevation forever to any apps you need, then rehide. Automatic elevation of whitelisted apps still works (and I assume you can still toggle in the Superuser tab.)
    5. If I understand it correctly /data wipe should only have to happen once (reflashing vbmeta with the special flags still needs to happen whenever vbmeta is updated).
    6. Magisk has added a "DenyList" which sounds like MagiskHide but a) it has a different name which suggests it's different and b) SafetyNet is sitll a problem. So not sure if it is doing anything since apps just check SafetyNet anyway.
    7. I copied my /sdcard from my old phone to my new. I could not get Android to allow me to drop files in /sdcard/Android/data or /sdcard/Android/obb though. I think that is a new thing. Even with Solid Explorer getting permissions granted to write to those folders it was still denied. As said su in adb shell doesn't work so I couldn't try that.
    8. I tried to install Universal SafetyNet Fix module but it wanted Riru installed first. That rabbit hole did not seem safe to go down so I aborted at that point; someone else can give it a go.
    9. Gnirehtet and ScrCpy work fine if you like using those tools (you may need newer Android 12 compatible versions). However it's worth noting Play Store thinks you're on mobile data if Gnirehtet is active so it will pause installing apps if you do that in the OOB setup (eg apps from another device) and I couldn't get it to unpause without disabling Gnirehtet.
    10. Titanium Backup works fine for restoring app data, so I can verify root works.

    SafetyNet workaround would be appreciated if anyone has figured it out.
    8
    I wouldn't count on any particular day for them to release the factory images.
    I did a bit of research and noticed that Google first released the factory images/OTA files for the

    Pixel 2 - 4 days after launch (Oct. 23th 2020 factory image, Oct. 19th launch)
    Pixel 3 - on "official" launch day (shipout) (Oct. 18th 2018)
    Pixel 4 - on launch day (Oct. 24th 2019)
    Pixel 4a - 4 days after launch (available Oct. 16th 2020, release of the phone Oct. 20th 2020)
    Pixel 5, 4a 5G - on launch day (October 15, 2020)

    So, if Google doesn't stray too far from it's previous release schedule, we should expect the factory image today or in the next few days.