• 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 - news is December OTA isn't coming until later this month

Search This thread

sean222

Senior Member
Oh ok, that means I can't root because I did the day 1 update and there are no images for it yet
Correct. I didn't do the Day 1 update. You need the boot.img from that update to patch it with Magisk.
You can probably google ways to extract the boot.img from an OTA, but it's probably not worth the time and effort.
 
  • Like
Reactions: roirraW "edor" ehT

hrdc69

Member
Apr 4, 2010
32
12
Does anyone know if you get the Pixel 6 Pro directly from T-Mobile does is come with the ability to unlock the bootloader like if you buy directly from the Google store?
 
  • Like
Reactions: roirraW "edor" ehT

Zilla0617

Senior Member
Does anyone know if you get the Pixel 6 Pro directly from T-Mobile does is come with the ability to unlock the bootloader like if you buy directly from the Google store?
Their unlock policy includes paying off the device and having the device on their network for 40 days. At that time, they will sim unlock your phone enabling you to unlock the bootloader. I've heard people reaching out to customer service to bypass the 40 day rule.

I have TMobile as well and decided to go thru the Google store to avoid the situation.
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

plasticarmyman

Senior Member
Apr 13, 2011
627
172
Long Beach
Does anyone know if you get the Pixel 6 Pro directly from T-Mobile does is come with the ability to unlock the bootloader like if you buy directly from the Google store?
You can always tell them you're travelling internationally and will be needing to use another SIM for service on the phone, they will usually SIM unlock at least temporarily so you can do so.
 
  • Like
Reactions: roirraW "edor" ehT

allenjthomsen

Senior Member
Nov 17, 2010
2,501
3,261
35
Oregon
OnePlus 7T Pro
OnePlus 7T Pro McLaren
Their unlock policy includes paying off the device and having the device on their network for 40 days. At that time, they will sim unlock your phone enabling you to unlock the bootloader. I've heard people reaching out to customer service to bypass the 40 day rule.

I have TMobile as well and decided to go thru the Google store to avoid the situation.
Can you tell me if this command works

adb shell

then type or copy this line below

pm uninstall --user 0 com.qualcomm.qti.uim

then go into developer options and oem unlocking should be togglable

If it doesnt let me know
 
  • Like
Reactions: roirraW "edor" ehT

allenjthomsen

Senior Member
Nov 17, 2010
2,501
3,261
35
Oregon
OnePlus 7T Pro
OnePlus 7T Pro McLaren
Can you tell me if this command works

adb shell

then type or copy this line below

pm uninstall --user 0 com.qualcomm.qti.uim

then go into developer options and oem unlocking should be togglable

If it doesnt let me know
if you have the device that is
im curious if it will work like on other tmobile devices @Zilla0617
 
  • Like
Reactions: roirraW "edor" ehT

Zilla0617

Senior Member
  • Like
Reactions: roirraW "edor" ehT

The MAZZTer

Member
Feb 1, 2015
19
20
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.
 
Last edited:

Olorin92

Member
Nov 11, 2015
49
12
Yep I've gotten about as far - rooted my 6 pro fine, however safetynet is the sticking point. Have tried USNF + MHPC with no luck.
 

aygul12345

Senior Member
Jan 14, 2011
759
48
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. 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. Use adb to push boot.img to phone somewhere in /sdcard.
12. Use adb to install magisk APK.
13. Run magisk and patch the boot.img.
14. Use adb to pull the patched magisk*.img down.
15. Reboot to bootloader
16. Use fastboot to flash the magisk'd boot.img.
17. Boot device.

You should be rooted now.

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.
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.
Totally argee, Ive seen so much SafetyNet Workarrounds, but its not working.
 

mkhcb

Senior Member
Nov 2, 2012
246
249
Stupid question time: I know OnePlus still honors your warranty if you unlock your phone. Will Google do the same? I doubt they would, but I figured I should ask.
 

loxacodito

New member
Aug 1, 2018
3
3
Stupid question time: I know OnePlus still honors your warranty if you unlock your phone. Will Google do the same? I doubt they would, but I figured I should ask.
There are no official sources, but based on peoples' anecdotal experiences, it seems that un-rooting and re-locking the bootloader will preserve warranty.
 
  • Like
Reactions: mkhcb

Top Liked Posts

  • 2
    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
    1
    • 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.
    1
    I was starting to wonder if I was insane, having to reboot my phone every couple of days because of no outgoing audio.
    One does not preclude the other 😜 (applies to me too).
    1
    • 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.
    1
    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.
  • 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 👍
    5
    New factory images and OTA images .037 and .037.A1 are available. Pixel 6 Pro Factory Images

    Manually mashing my Check for update button results in nothing, so give it some time to OTA for those who aren't rooted (yet). Or wait to see if it makes anything worse for anyone who gets the OTA first. 😜

    Everyone, make sure your phone is charged enough for whether you'll take the OTA or flash manually.
    4
    Thanks for your quick answer. How to I use adb sideload? When I go to recovery, there's an Android icon with 'No command' text. cmd on Windows 11 states that adb is unauthorised.
    Had that as well, when you see the Android icon you are actually not in the recovery - you need to short press the "power" button and the "volume up" button directly one after the other to get into the actual recovery menu where you can select adb sideload (see video here for details) - took me a few approaches to get the timing correct, though ;)
    4
    BTW with 037 the flickering screen while the device is off and you shortly press the power button (without starting the phone) has been fixed - at least on my device :)
  • 35
    Note that this is only for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store.

    Some of the information here applies to other variants, but I won't necessarily update information in the OP for them. 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, 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.


    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.
    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.

    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.​


    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

    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

    Rooting-related


    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
    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.

    List of all Pixel monthly security bulletins

    TBD for 12/1/2021 security update:
    TL;DR:
    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.
    @Ghisy posted here:

    From Android Police:

    It's coming to supported Pixel devices today, but Pixel 6 and 6 Pro users will have to wait a little longer. Google says those phones are getting their updates sometime later this month.

    @henihazbay posted a link 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


    Other source for changes (more technical) below:
    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


    Copy of Verizon changelogs in case they disappear
      • System Update 1​


      The details:

      Release date: 11/16/2021
      Android™ Security Patch Level: October 2021
      Software Version: SD1A.210817.037.A1

      What's changing:

      The current software update improves the performance of your device's fingerprint sensor.

      • System Update​


      The details:

      Release date: 10/28/2021
      Android Security Patch Level: October 2021
      Software Version: SD1A.210817.036.A8

      What's changing:

      The current software update provides performance improvements and the most up to date Android security patches on your device.

    Full OTA Images

    I may append this first post with further useful information or links as needed.
    13
    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.