How To Guide Unlocking the Pixel 6 Pro bootloader & central repository of relevant links

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
See this post about Magisk Stable v25.1.

June 2022 update is here:
12.1.0 (SQ3A.220605.009.A1, Jun 2022, Verizon)FlashLink2b4b1d476a6e80fd9fe09ace45e8abbd654a4d4a6fc51d39f0fd76f5a2c6a024
12.1.0 (SQ3A.220605.009.B1, Jun 2022)FlashLink157e22840d4d4fde9f90d7de3d6ba6930922e9376096040d68501d155c997cb2


June 6, 2022 1:00pm Comment Adam Conway

June Feature Drop for Google Pixels includes At a Glance improvements, Pocket Operator, and more​

Every three months, Google rolls out new features to Pixel phones outside of the usual Android OS updates for years, and the company refers to them as “Feature Drops.” They’re usually released alongside a security patch, and the most recent one brought improvements to live caption, night mode in Snapchat, and a whole lot more. Now the June Feature Drop is now available (alongside June security patches), and it packs a ton of cool stuff you can try out on any Pixel smartphone release between the Pixel 4 and the latest Pixel 6 series.
In case you’re wondering, the June feature drop is based on the QPR3 builds that Google has been testing over the last few months. It’s currently unknown if Google will continue to beta test quarterly platform releases in the future.

Pocket Operator​

june feature drop teenage engineering pocket operator

Made in collaboration with teenage engineering, Pocket Operator is a new app that will let you shoot videos and “turn them into fun music and video cut-ups.” You can layer sounds, add visual effects, create patterns and beats, and mix it all together to make your own unique tracks. It’s available on the Google Play Store now, and you can check it out down below. It works on the Pixel 5 and newer, and currently, it’s only available in English.

The app was not found in the store.
Go to store Google websearch

Vaccination Cards​

COVID vaccination card google pay shortcut

Google has had the ability to add a vaccine card to your Google Pay for quite a while now, but now the company says you can add a shortcut to it to your home screen to quickly and easily get access to it at any time. It’s available in Australia, Canada, and the U.S.

More “At a Glance” alerts​

Video Player


00:00

00:33


The Pixel 6 series debuted a revamped “At a Glance” widget, which can display your calendar events, flight boarding pass, workout stats, and more on your home screen and lockscreen. Since its release, Google has added several new features to the widget to further expand its capabilities. Now the company is adding three new features to it.

Nest Doorbell video feed​

June feautre drop nest doorbell

Google added Nest Doorbell alerts back in January to the At a Glance widget, and they can tell you if “Someone’s at your door”. This can help you find out if a package has arrived, or if someone is just trying to get your attention out the front of your house. Now you can see an actual video feed from your doorbell too, right on your home screen.

Flashlight reminder​

Ever left your flashlight turned on on your phone? It’s pretty embarrassing, but I’m pretty sure that we’ve all been there. Now you’ll be able to see if it’s on straight from your home screen, without needing to turn your phone around to catch it.

Coming soon: Air Quality alerts​

If you live in the U.S., Australia, or India, soon you’ll get Air Quality alerts in your At a Glance widget for your current location.

Conversation Mode exits beta​

Sound Amplifier app Conversation mode

Google previously added “Conversation Mode” to the Sound Amplifier app in the December feature drop, and it’s been in beta since then. It uses on-device machine learning to block out surrounding noise. Conversation Mode is exclusively available to Pixel phone owners, and now it’s exiting beta. It’s designed for people with hearing loss to filter out sounds around them. It amplifies their voice, and you uses the camera to focus on whatever their phone should be properly listening to.

More features​

Real Tone Filters​

Google introduced Real Tone with the Pixel 6 series last year to help users accurately capture various skin tones. The Real Tone functionality used an updated face detection algorithm capable of recognizing more diverse faces in a wider array of lighting conditions, resulting in a better representation of different skin tones.
At I/O this year, Google expanded on the functionality and announced that it would implement Harvard professor Dr. Ellis Monk’s scale in Search and Photos to achieve similar results across all its products. These filters are now rolling out to users of Google Photos.

Car Crash Detection comes to Canada​

Google’s Car Crash Detection is rolling out in Canada now to Google Pixel 3 users and above, though excluding the Pixel 3a. It can, as the name suggests, detect if you’re in a car crash and act accordingly. It’s a safety feature that could potentially save lives.

More Chat translation languages​

Chat translation in messages will now be available in Traditional Chinese, Dutch, Korean, Thai, and Turkish for Pixel 6 and Pixel 6 Pro.

Download and install the June feature drop​

The June feature drop is now available for all eligible Pixel smartphones, and you can download it by checking for an update in your device’s settings.


Pixel Update Bulletin—May 2022​


Published May 2, 2022
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 2022-05-05 or later address all issues in this bulletin and all issues in the May 2022 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 2022-05-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 May 2022 Android 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.

Pixel​

CVEReferencesTypeSeverityComponent
CVE-2022-20120A-203213034*RCECriticalBootloader
CVE-2022-20117A-217475903*IDCriticalTitan-M
CVE-2021-4083A-216408350
Upstream kernel
EoPHighKernel
CVE-2022-20118A-205707793*EoPHighKernel
CVE-2022-20119A-213170715*IDHighDisplay/Graphics
CVE-2022-20121A-212573046*IDHighUSCCDMService

Qualcomm components​

CVEReferencesSeverityComponent
CVE-2021-35084A-204909067
QC-CR#3001178
ModerateWLAN
CVE-2021-35085A-204012850
QC-CR#3001331
ModerateWLAN
CVE-2021-35092A-204909309
QC-CR#2985885 [2]
ModerateModem
CVE-2021-35098A-190503256
QC-CR#2966419
ModerateAudio

Qualcomm closed-source components​

CVEReferencesSeverityComponent
CVE-2021-35079A-204908838*ModerateClosed-source component

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 2022-05-05 or later address all issues associated with the 2022-05-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.0May 2, 2022Bulletin Published

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 (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)

Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.

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.

How I root and update (which is identical whether rooting the first time or updating):
  • Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
  • Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
  • Extracted the new boot.img
  • Copied new boot.img to the phone
  • Patched the new boot.img with Magisk Stable
  • Renamed Magisk'd boot.img so I know what version of firmware it's for
  • Copied the Magisk'd boot.img back to the computer
  • Disabled all my Magisk Modules
  • Removed the "-w " from the flash-all.bat
  • Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
  • Open a Command Prompt, navigated to S:\platform-tools
  • adb reboot bootloader
  • flash-all.bat
  • Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
  • adb reboot bootloader
  • fastboot flash boot kernel.img (renamed Magisk'd boot.img)
  • fastboot reboot
  • Unlock, check everything's working
  • Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
  • Reboot, unlock, made sure everything's working
Back to modding!

I may append these first four posts with further useful information or links as needed.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
Disabling Verity and Verification isn't required except for use with some custom kernels, but just rooting those custom kernels with the latest Magisk Stable v24.1 or higher should make them not require disabled Verity and Verification anymore.

A reminder that disabling Verity and Verification, at least if you've never disabled them before, will cause you to need to factory reset the device otherwise there will be corruption.

if you didnt disable before then it is enabled since the beginning. Disabling requires a full wipe.
It will show this image if you try to disable.

You can also verify it using adb shell with:
adb shell
su
avbctl get-verity
avbctl get-verification
1636658711744-png.5455805

The usefulness of having Verity and Verification enabled (now that it's not needed for root but IS still required for some custom kernels):

1. DM-Verity ( VB 1.0 ) verifies /system and /vendor - it was introduced with Android 4.4, modified with Android 7
2. Android Verified Boot ( VB 2.0 aka AVB ) additionally verifies /boot - it was introduced with Android 8, works on Project Treble enabled devices

Both are running a hash on the memory blocks mentioned of your device to ensure the integrity of your software and help prevent rootkits and the like.

If you disable VB 1.0 and/or VB 2.0 your Android device becomes vulnerable to malware of any type: IMO only those do it who do not care about the built-in protection.

Yes - this is covered on Android Source.

The basics:
Android Verified Boot ensures that the boot code is legitimate, by using a boot image "signature" compared to a signature stored in the key registry.

Dm-verity is a method by which the code on the block devices is hashed; this hash is then compared to a reference hash to determine its authenticity before the image is loaded, thereby preventing rootkits from declaring themselves legitimate.

Vbmeta verification is a method of storing those reference hashes to which the generated hashes are compared. This can be and often is used for any critical partition, such as /boot and /system.

These aren't new concepts and indeed have been integral to Android for some time. What is new is how the Android 12 AVB headers were handled.

We still don't know exactly where in the process the problem occurred when trying to run custom boot images with Android 12. I suspect that the issue wasn't custom software itself - after all, you could still flash a custom ROM and run it without issues - but rather, trying to use a modified boot image with otherwise stock Android 12 system. Don't take my word for it, though, because I don't know for sure.

It has nothing to do with the kernel itself. The anykernel.zip uses magiskboot to "repack" the kernel during the flashing kernel.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
Regarding P6P 5G model numbers and capabilities:

There are three hardware versions:
  • G8VOU (AU, US); also listed as G8V0U - zero instead of "oh" on some sites, Google shows the former, G8VOU) - has mmWave 5G support
  • GF5KQ (JP) - has mmWave 5G support
  • GLUOG (CA, DE, FR, GB, IE, TW) - no mmWave 5G support
For instance, my factory unlocked direct from Google in the United States Pixel 6 Pro 512 GB is a G8VOU. As far as I know, all other variations in each individual phone are controlled by software (which firmware is loaded) and over the internet (which IMEIs are Carrier Unlocked or not, and OEM Unlockable or not).

Check carriers, their 5G networks & their 5G roaming support for Pixel phones. Make sure and choose your country from the drop-down to see the list of carriers beneath.

There's also the section above that Learn which Pixel phones can work with which kinds of 5G.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
List of all Google Play System Updates

January 2022​

Critical Fixes​

  • [Tablet, Wear OS, Phone] Bug fixes for device connectivity, safety & emergency, system management & diagnostics and media related services.[1]

Google Play Store

  • Play-as-you-download feature to let gamers start playing mobile games while the app download continues to reduce waiting times. [3]
  • New Features to help you discover the Apps & Games you love.[3]
  • Optimizations allowing faster and more reliable download and installation.[3]
  • New features to the Play Pass and Play Points programs. [3]
  • Enhancements to Google Play Billing. [3]
  • Continuous improvements to Play Protect to keep your device safe. [3]
  • Various performance optimizations, bug fixes and improvements to security, stability and accessibility. [3]

System Management​

  • With updates to the timezone management system, added support for new daylight savings time transition changes in various countries.[1]
  • Updates to system management services that improve device connectivity, network usage, stability, security and updatability. [1]
[1] Available through Google Play system update for January.
[3] Available through Google Play Store v28.7 updated on 01/06/2022.

Critical Fixes​

  • [Auto, Tablet, TV, Wear OS, Phone] Bug fixes for device connectivity, safety & emergency, system management & diagnostics and media related services.[1][2]

Games​

  • [Phone, TV] With updates to Play Games Services, you can now sign in and manage your Google Play Games Profile and your privacy and sign-in settings without having to install the Google Play Games app.[2]

Google Play Store

  • Play-as-you-download feature to let gamers start playing mobile games while the app download continues to reduce waiting times.[3]
  • New Features to help you discover the Apps & Games you love.[3]
  • Optimizations allowing faster and more reliable download and installation.[3]
  • New features to the Play Pass and Play Points programs.[3]
  • Enhancements to Google Play Billing.[3]
  • Continuous improvements to Play Protect to keep your device safe.[3]
  • Various performance optimizations, bug fixes and improvements to security, stability and accessibility.[3]

Support​

  • [Auto, Tablet, TV, Wear OS, Phone] With updates to the new version of mobile data plan UI, you can have a better experience of selecting the data plan.[2]

Utilities

  • [Auto, Phone] With update to Autofill, for some users in US, we have added risk-based authentication to Virtual card transactions.[2]
  • [Auto, Tablet, TV, Wear OS, Phone] With the update to Contacts, users can import contacts from SIM card to your google account from the google contacts sync setting page.[2]

Wallet

  • [Phone, Tablet] Added support for Israel, Kazakhstan, and the Netherlands.[2]
  • [Phone] With digital car key, you can lock, unlock and start your car with just your phone (requires compatible car and phone model).[2]

System Management​

  • Updates to system management services that improve battery life, device connectivity, network usage, privacy, stability, security and updatability. [1][2]

Developer Services​

  • New developer features for Google & 3rd party app developers to support analytics & diagnostics and device connectivity related developer services in their apps.[2]

[1] Available through Google Play system update for December.
[2] Available through Google Play services v21.45.13 updated on 12/10/2021.
[3] Available through Google Play store v28.3 updated on 12/13/2021.

List of all Pixel monthly security bulletins
January 2022 Update bulletin
https://source.android.com/security/bulletin/pixel/2022-01-01

feedback

Pixel Update Bulletin—January 2022​


Published January 4, 2022
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 2022-01-05 or later address all issues in this bulletin and all issues in the January 2022 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 2022-01-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 January 2022 Android 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.

Pixel

CVEReferencesTypeSeverityComponent
CVE-2021-39678A-171742549 *EoPHighGboard
CVE-2021-39679A-188745089 *EoPHighDisplay/graphics
CVE-2021-39682A-201677538 *EoPHighDisplay/graphics
CVE-2021-39683A-202003354 *EoPHighTitan M2
CVE-2021-39684A-203250788 *EoPHighBootloader
CVE-2021-40490A-199579676 *EoPHighKernel
CVE-2021-39680A-197965864 *IDHighTitan M2
CVE-2021-39681A-200251074 *EoPModerateTelephony

Qualcomm components

CVEReferencesSeverityComponent
CVE-2021-30313A-178720043
QC-CR#2878995
ModerateKernel

Qualcomm closed-source components

CVEReferencesSeverityComponent
CVE-2021-30314A-193072178 *ModerateClosed-source component

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 2022-01-05 or later address all issues associated with the 2022-01-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.0January 4, 2022Bulletin Released
https://support.google.com/pixelphone/thread/143968432/google-pixel-update-january-2022?hl=en
Google Pixel Update - January 2022
Hello Pixel Community,
We have provided the monthly software update for January 2022. All supported Pixel devices running Android 12 will receive these software updates starting today, with the exception of the Pixel 6 and 6 Pro, which will receive the update later this month. For more information on the delay, click here. The rollout will continue over the next week in phases depending on carrier and device. We will provide an update to this post once it is available. Users will receive a notification once the OTA becomes available for their device. 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.220105.002
  • Pixel 4 (XL): SQ1A.220105.002
  • Pixel 4a: SQ1A.220105.002
  • Pixel 4a (5G): SQ1A.220105.002
  • Pixel 5: SQ1A.220105.002
  • Pixel 5a (5G): SQ1A.220105.002

What’s included
The January 2022 update includes bug fixes and improvements for Pixel users – see below for some notable improvements.
Framework
  • Fix for issue causing screen to unlock after missed call when no screen lock is set *[1].
Network & Telephony
  • General fixes & improvements for network
  • Fix for issue preventing emergency calls in certain conditions while some third-party apps are installed *[4].
Power
  • Fix for issue preventing Pixel Stand setup to start after updating apps in certain conditions *[2].
System
  • Fix for issue causing incorrect data usage accounting in Network menu on some networks *[1].
User Interface
  • Fix for issue causing a black frame to appear when dismissing the Assistant overlay on the lock screen
  • Fix for issue causing memory leak in system UI under certain conditions *[1].
  • Fix for issue causing navigation bar to be hidden when switching device orientation in certain conditions *[1].
  • Fix for issue causing PIP window to render incorrectly for certain apps *[1].
Wi-Fi
  • Fix for issue causing Wi-Fi network to drop connection in certain conditions *[3].

---------------------------------------------------------------
Device Applicability
*Updates for PIxel 6 and 6 Pro are delayed until later in January, as noted above
*[1] 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
*[2] Included on Pixel 4 / XL, Pixel 5, Pixel 6 & Pixel 6 Pro
*[3] Included on Pixel 6 & Pixel 6 Pro
*[4] Included on Pixel 3, Pixel 3 XL, 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
Details
Other, Google Pixel 6 Pro

XDA article: January 2022 Android security update now rolling out, fixes bug that prevented emergency calls
January 4, 2022 2:40pm Corbin Davenport

January 2022 Android security update now rolling out, fixes bug that prevented emergency calls​

There’s a lot happening this week, thanks to the flurry of CES 2022 events and announcements, but that hasn’t prevented Google from releasing its security patches on time — so long as you don’t have a Google Pixel 6. The company just released the January 2022 Android Security Update Bulletin, though the Pixel 6 and Pixel 6 Pro will have to wait a bit longer.
Perhaps the most important non-security change in this update is a system-level fix for the bug that allowed Microsoft Teams to break emergency calling, known as CVE-2021-39659. Microsoft already rolled out a fix for its Android application, but this security patch addresses it for good.
This update also patches a loophole in Android 12 that allowed third-party applications with shell access to change the colors and dimensions of certain system elements, which in turn permitted some system customization without root access or other device modifications. The issue was already fixed in the developer builds of Android 12L, but Google has now backported the fix back to Android 12.

January 2022 Android Security Update Bulletin​

The January 2022 Android Security Bulletin can be viewed here. The core 2022-01-01 security patch covers five vulnerabilities in the Android Framework and Media Framework, and 11 issues for the core Android System. The additional 2022-01-05 security patch contains one fix for the Android runtime and four for the kernel, as well as a handful of fixes specific to certain chipsets from Qualcomm, MediaTek, and other chipmakers.
For more information on how the monthly Android security update process works, we recommend reading our explainer available here.

Pixel Update Bulletin/Functional Update​

The January security update with patch level 2022-01-05 is rolling out for the Pixel 3a series, Pixel 4 series, Pixel 4a series, Pixel 5, and Pixel 5a. The update is not yet ready for the Pixel 6 and Pixel 6 Pro — Google paused the rollout of the buggy December update for the Pixel 6 series, and the company said a new update with all the fixes (and the January security patches) wouldn’t arrive until later in January.
  • Global:
    • Pixel 3a: SQ1A.220105.002
    • Pixel 3a (XL): SQ1A.220105.002
    • Pixel 4 (XL): SQ1A.220105.002
    • Pixel 4a: SQ1A.220105.002
    • Pixel 4a (5G): SQ1A.220105.002
    • Pixel 5: SQ1A.220105.002
    • Pixel 5a (5G): SQ1A.220105.002
    • Pixel 6: N/A
    • Pixel 6 Pro: N/A
If you don’t want to wait for Google to push the update to you, you can manually flash it to your device using either the OTA files (if you’re on the previous update already) or the factory images (if you’re behind on updates, or want to switch back to the stock ROM). The links to both options are below. We’ll be sure to update this article with more build numbers as we get them.

December 2021 Update Paused
Hey Pixel Community,

The Pixel team paused the December software update to Pixel 6 and Pixel 6 Pro devices after some users reported calls were dropping or disconnecting. We have now identified a fix that will roll out in a software update by late January. This update will also include all the fixes and improvements that were originally planned in December. If you received the December software update on Pixel 6 or Pixel 6 Pro and are still experiencing mobile connectivity issues, you can revert to the previous software version using the Android Flash Tool (flash.android.com) and performing a factory reset. Please back up your phone before restoring to the previous software version. If you are not experiencing mobile connectivity issues, no action is required. We sincerely apologize for the inconvenience and appreciate your patience as we roll out the fix.

Your Pixel Community Manager,
Camille

12/5/2021 security update (released 12/13/2021 for the Pixel 6 Pro / 6.
More technical source for changes below:
https://source.android.com/security/bulletin/pixel/2021-12-01

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

Functional patches​

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

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.

Copy of Verizon changelogs in case they disappear

System Update 2​


The details:

Release date: 12/16/2021
Android™ Security Patch Level: December 2021
Software Version: SQ1D.211205.017

What's changing:

The December update includes the most up to date security patch, and improvements across many areas including performance, stability, battery, and more.

New features introduced in the Pixel December Feature drop:

Now Playing: Favorites
Remember the good tracks you hear around you by adding them to your favourites.

Expand Car Crash Detection & Assisted Emergency Dialer
Expand support for Car Crash Detection using Automated Emergency Dialing to Italy, Taiwan and France.

December 2021 Cultural Wallpaper Collection
Wallpapers added to the Curated Culture collection to celebrate the "International Day of People with Disabilities."

Nearby Sharing support
With Nearby Share, you can share photos, videos, links, and more with devices around you.

Quick Tap to Snap
Quickly tap the back of your device twice to open Snapchat, even when the device is locked.

Bass EQ Slider for Pixel Bud A series
Added an EQ to adjust the bass level to different scales/magnitudes in addition to the default level.

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.

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.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.
This one's kinda long for what it is, and this is for the Pixel 1, but it should be similar for the Pixel 6/Pro. I won't add it to the first post just yet in case there are differences, and I don't want to recommend something I can't actually try on the 6 Pro (since I won't get mine for likely another two days). Unlocking the Bootloader of the Pixel and Pixel XL

Good luck!
 
  • Like
Reactions: dj24 and galaxys

dj24

Senior Member
Jun 23, 2018
390
144
Samsung Galaxy Note 20 Ultra
This one's kinda long for what it is, and this is for the Pixel 1, but it should be similar for the Pixel 6/Pro. I won't add it to the first post just yet in case there are differences, and I don't want to recommend something I can't actually try on the 6 Pro (since I won't get mine for likely another two days). Unlocking the Bootloader of the Pixel and Pixel XL

Good luck!
This is great. I won't be getting mine for a while as well so please come back and update this thread.
 
  • Like
Reactions: roirraW "edor" ehT

Pekempy

Senior Member
Aug 22, 2011
660
319
UK
Google Pixel 6 Pro
If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.
Generally YouTube video guides for software related things aren't particularly helpful, as they can often get outdated very quickly; especially in the early days of a device as they can't be updated when new things are found out.
It would probably be best to carefully read through guides
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
This is great. I won't be getting mine for a while as well so please come back and update this thread.
FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone, otherwise, you'll have to back up anything that doesn't normally get backed up, and go through the initial setup process again. Not a big deal for some, but would likely not be optimal for a new user.
  • Instructions for Locking/Unlocking the Bootloader (note that 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).
 

Ghisy

Senior Member
Mar 27, 2010
1,689
487
FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone
This! It's the first thing you should do out of the box if you plan on rooting later.
 

96carboard

Senior Member
Jul 17, 2018
669
374
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.
 

96carboard

Senior Member
Jul 17, 2018
669
374
Thanks. I was confused because I didn't see that mentioned in the OP

Steps 6 & 7 are new to me. -not something I did on my 6XL

Thanks again

ƒ

6 is just an easier way to reboot it into recovery than trying to shut it down and fiddle with volume+power buttons to start in the right mode. You had to do 7, no choice. Some older phones used "fastboot oem unlock". You'd have to ask google why they changed it.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
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.

Thanks. I was confused because I didn't see that mentioned in the OP

Steps 6 & 7 are new to me. -not something I did on my 6XL

Thanks again

ƒ
Good point. I'll add to the OP. You might not remember 6 and 7, but you had to have done them one way or another, whether using a third-party tool to help automate that part or something else.
 
  • Like
Reactions: biTToe

biTToe

Senior Member
6 is just an easier way to reboot it into recovery than trying to shut it down and fiddle with volume+power buttons to start in the right mode. You had to do 7, no choice. Some older phones used "fastboot oem unlock". You'd have to ask google why they changed it.
Ahhh...
to be fair, B/L unlock was a long time ago for me.
My P6P arrives tomorrow and I am hoping for root as well.
ƒ
 
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Magisk Stable v25.1 is out.

    Magisk Changelog​

    v25.1​

    • [MagiskBoot] Fix ramdisk backup being incorrectly skipped
    • [MagiskBoot] Add new feature to detect unsupported dtb and abort during installation
    • [Zygisk] Change binary hijack paths
    • [App] Fix incorrect recovery mode detection and installation
    • [MagiskInit] Fix config not properly exported in legacy SAR devices
    • [General] Enforce the Magisk app to always match or be newer than magiskd

    v25.0​

    • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
    • [MagiskInit] Introduce new sepolicy injection mechanism
    • [MagiskInit] Support Oculus Go
    • [MagiskInit] Support Android 13 GKIs (Pixel 6)
    • [MagiskBoot] Fix vbmeta extraction implementation
    • [App] Fix stub app on older Android versions
    • [App] [MagiskSU] Properly support apps using sharedUserId
    • [MagiskSU] Fix a possible crash in magiskd
    • [MagiskSU] Prune unused UIDs as soon as system_server restarts to prevent UID reuse attacks
    • [MagiskSU] Verify and enforce the installed Magisk app’s certificate to match the distributor’s signature
    • [MagiskSU] [Zygisk] Proper package management and detection
    • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
    • [Zygisk] Fix Zygisk’s self code unloading implementation
    • [DenyList] Fix DenyList on shared UID apps
    • [BusyBox] Add workaround for devices running old kernels

    2022.6.19 Magisk v25.1​

    v25.1 fixes some minor bugs over v25.0. The following are the same as v25.0 release notes.
    Another major release! A lot of the changes aren’t visible at the surface, but v25 is actually a really substantial upgrade!

    MagiskInit Rewrite​

    A significant portion of magiskinit (the critical software that runs before your device boots up) is completely rewritten from scratch. Ever since Android introduced Project Treble in Android 8.0, Magisk has been constantly fighting against the increasingly complex partitioning and early mount setups of all kinds of devices, sometimes with weird OEM specific implementations. It got to a point that magiskinit had become so complicated that few people (including myself!) were aware of every detail, and maintaining this piece of software like this was clearly not sustainable. After many months of planning (yes, this whole re-architecture has been in my head for a long time) and some help from external contributors, a whole new sepolicy injection mechanism is introduced into Magisk, solving the “SELinux Problem” once and for all.

    Since this is a full paradigm shift on how Magisk hot-patch the device at boot, several behaviors that many developers implicitly relied on might not exist. For example, Magisk no longer patches fstabs in most scenarios, which means AVB will remain intact; some custom kernels rely on AVB being stripped out for them by Magisk.

    MagiskSU Security Enhancements​

    The superuser functionality of Magisk has not seen much changes ever since its introduction. v25 focuses on making root permission management more accurate and secure:

    • Add a whole new package tracking system to ensure malicious UID reuse attack cannot be performed
    • Properly support and implement the UX in the Magisk app for packages using sharedUserId
    • Enforce root manager APK signature verification to combat the rampant unofficial Magisk app “mods”
    Many might not realize, but using a trusted, unmodified Magisk app is really important. Magisk’s root daemon treats the Magisk app differently and gives it blanket root access without any restrictions. A modded Magisk app can potentially backdoor your device.

    And in case some of you are about to put on your tin foil hats, this is not designed to “vendor lock-in”; the goal is to make sure your root management app comes from the same developer of the underlying root implementation. Magisk’s build system allows custom distributors to use its own signing keys, and in addition, I am also providing official debug builds which skips any signature verification for development.
    6
    Platform Tools is updated to v33.0.2 everyone! No updated changelog yet, and 33.0.1 worked for me (and others) for the June update. And thanks to @jcp2 for the discovery.
    • 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.
    6
    Finally the changelog for the SDK Platform Tools 33.0.2 (May 2022):

    Revisions​

    33.0.2 (May 2022)​

    • fastboot
      • Support for the vendor_kernel_boot partition.
    5
    Grrr...I had put the May updates' links here previously.

    June 2022 update is here:
    12.1.0 (SQ3A.220605.009.A1, Jun 2022, Verizon)FlashLink2b4b1d476a6e80fd9fe09ace45e8abbd654a4d4a6fc51d39f0fd76f5a2c6a024
    12.1.0 (SQ3A.220605.009.B1, Jun 2022)FlashLink157e22840d4d4fde9f90d7de3d6ba6930922e9376096040d68501d155c997cb2


    June 6, 2022 1:00pm Comment Adam Conway

    June Feature Drop for Google Pixels includes At a Glance improvements, Pocket Operator, and more​

    Every three months, Google rolls out new features to Pixel phones outside of the usual Android OS updates for years, and the company refers to them as “Feature Drops.” They’re usually released alongside a security patch, and the most recent one brought improvements to live caption, night mode in Snapchat, and a whole lot more. Now the June Feature Drop is now available (alongside June security patches), and it packs a ton of cool stuff you can try out on any Pixel smartphone release between the Pixel 4 and the latest Pixel 6 series.
    In case you’re wondering, the June feature drop is based on the QPR3 builds that Google has been testing over the last few months. It’s currently unknown if Google will continue to beta test quarterly platform releases in the future.

    Pocket Operator​

    june feature drop teenage engineering pocket operator

    Made in collaboration with teenage engineering, Pocket Operator is a new app that will let you shoot videos and “turn them into fun music and video cut-ups.” You can layer sounds, add visual effects, create patterns and beats, and mix it all together to make your own unique tracks. It’s available on the Google Play Store now, and you can check it out down below. It works on the Pixel 5 and newer, and currently, it’s only available in English.

    The app was not found in the store.
    Go to store Google websearch

    Vaccination Cards​

    COVID vaccination card google pay shortcut

    Google has had the ability to add a vaccine card to your Google Pay for quite a while now, but now the company says you can add a shortcut to it to your home screen to quickly and easily get access to it at any time. It’s available in Australia, Canada, and the U.S.

    More “At a Glance” alerts​

    Video Player


    00:00

    00:33


    The Pixel 6 series debuted a revamped “At a Glance” widget, which can display your calendar events, flight boarding pass, workout stats, and more on your home screen and lockscreen. Since its release, Google has added several new features to the widget to further expand its capabilities. Now the company is adding three new features to it.

    Nest Doorbell video feed​

    June feautre drop nest doorbell

    Google added Nest Doorbell alerts back in January to the At a Glance widget, and they can tell you if “Someone’s at your door”. This can help you find out if a package has arrived, or if someone is just trying to get your attention out the front of your house. Now you can see an actual video feed from your doorbell too, right on your home screen.

    Flashlight reminder​

    Ever left your flashlight turned on on your phone? It’s pretty embarrassing, but I’m pretty sure that we’ve all been there. Now you’ll be able to see if it’s on straight from your home screen, without needing to turn your phone around to catch it.

    Coming soon: Air Quality alerts​

    If you live in the U.S., Australia, or India, soon you’ll get Air Quality alerts in your At a Glance widget for your current location.

    Conversation Mode exits beta​

    Sound Amplifier app Conversation mode

    Google previously added “Conversation Mode” to the Sound Amplifier app in the December feature drop, and it’s been in beta since then. It uses on-device machine learning to block out surrounding noise. Conversation Mode is exclusively available to Pixel phone owners, and now it’s exiting beta. It’s designed for people with hearing loss to filter out sounds around them. It amplifies their voice, and you uses the camera to focus on whatever their phone should be properly listening to.

    More features​

    Real Tone Filters​

    Google introduced Real Tone with the Pixel 6 series last year to help users accurately capture various skin tones. The Real Tone functionality used an updated face detection algorithm capable of recognizing more diverse faces in a wider array of lighting conditions, resulting in a better representation of different skin tones.
    At I/O this year, Google expanded on the functionality and announced that it would implement Harvard professor Dr. Ellis Monk’s scale in Search and Photos to achieve similar results across all its products. These filters are now rolling out to users of Google Photos.

    Car Crash Detection comes to Canada​

    Google’s Car Crash Detection is rolling out in Canada now to Google Pixel 3 users and above, though excluding the Pixel 3a. It can, as the name suggests, detect if you’re in a car crash and act accordingly. It’s a safety feature that could potentially save lives.

    More Chat translation languages​

    Chat translation in messages will now be available in Traditional Chinese, Dutch, Korean, Thai, and Turkish for Pixel 6 and Pixel 6 Pro.

    Download and install the June feature drop​

    The June feature drop is now available for all eligible Pixel smartphones, and you can download it by checking for an update in your device’s settings.


    Pixel Update Bulletin—May 2022​


    Published May 2, 2022
    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 2022-05-05 or later address all issues in this bulletin and all issues in the May 2022 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 2022-05-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 May 2022 Android 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.

    Pixel​

    CVEReferencesTypeSeverityComponent
    CVE-2022-20120A-203213034*RCECriticalBootloader
    CVE-2022-20117A-217475903*IDCriticalTitan-M
    CVE-2021-4083A-216408350
    Upstream kernel
    EoPHighKernel
    CVE-2022-20118A-205707793*EoPHighKernel
    CVE-2022-20119A-213170715*IDHighDisplay/Graphics
    CVE-2022-20121A-212573046*IDHighUSCCDMService

    Qualcomm components​

    CVEReferencesSeverityComponent
    CVE-2021-35084A-204909067
    QC-CR#3001178
    ModerateWLAN
    CVE-2021-35085A-204012850
    QC-CR#3001331
    ModerateWLAN
    CVE-2021-35092A-204909309
    QC-CR#2985885 [2]
    ModerateModem
    CVE-2021-35098A-190503256
    QC-CR#2966419
    ModerateAudio

    Qualcomm closed-source components​

    CVEReferencesSeverityComponent
    CVE-2021-35079A-204908838*ModerateClosed-source component

    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 2022-05-05 or later address all issues associated with the 2022-05-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.0May 2, 2022Bulletin Published
    5
    are people sticking with 24.2 Magisk instead of updating while still on stock A12 firmware?
    or is Magisk 25 fine and does not need you to disable verity and vbmeta?
    Depends on your reason to disable verity and verification. Magisk no longer strips avb from fstab so custom kernels had a problems booting on Canary 24303+, including Beta 25, but that has been fixed and incorporated into the kernels/AK3 themselves now so you can use Beta 25 with custom kernels, even though Magisk continues to strip avb from fstab.

    There may be other reasons you want to disable verity and verification, such as avoiding the corrupt message issue, although there are now ways to overcome that as well.

    Also, it has been discovered that disabling verity alone, without disabling verification, avoids the problems of the current Magisk version as it relates to custom kernels (or modifying any of the avb partitions in fstab) without having to wipe.

    I'm one of those who continue to disable verity and verification just because Magisk and Google are continuously changing things, but whether you do or not is up to you. It's not required.
  • 53
    See this post about Magisk Stable v25.1.

    June 2022 update is here:
    12.1.0 (SQ3A.220605.009.A1, Jun 2022, Verizon)FlashLink2b4b1d476a6e80fd9fe09ace45e8abbd654a4d4a6fc51d39f0fd76f5a2c6a024
    12.1.0 (SQ3A.220605.009.B1, Jun 2022)FlashLink157e22840d4d4fde9f90d7de3d6ba6930922e9376096040d68501d155c997cb2


    June 6, 2022 1:00pm Comment Adam Conway

    June Feature Drop for Google Pixels includes At a Glance improvements, Pocket Operator, and more​

    Every three months, Google rolls out new features to Pixel phones outside of the usual Android OS updates for years, and the company refers to them as “Feature Drops.” They’re usually released alongside a security patch, and the most recent one brought improvements to live caption, night mode in Snapchat, and a whole lot more. Now the June Feature Drop is now available (alongside June security patches), and it packs a ton of cool stuff you can try out on any Pixel smartphone release between the Pixel 4 and the latest Pixel 6 series.
    In case you’re wondering, the June feature drop is based on the QPR3 builds that Google has been testing over the last few months. It’s currently unknown if Google will continue to beta test quarterly platform releases in the future.

    Pocket Operator​

    june feature drop teenage engineering pocket operator

    Made in collaboration with teenage engineering, Pocket Operator is a new app that will let you shoot videos and “turn them into fun music and video cut-ups.” You can layer sounds, add visual effects, create patterns and beats, and mix it all together to make your own unique tracks. It’s available on the Google Play Store now, and you can check it out down below. It works on the Pixel 5 and newer, and currently, it’s only available in English.

    The app was not found in the store.
    Go to store Google websearch

    Vaccination Cards​

    COVID vaccination card google pay shortcut

    Google has had the ability to add a vaccine card to your Google Pay for quite a while now, but now the company says you can add a shortcut to it to your home screen to quickly and easily get access to it at any time. It’s available in Australia, Canada, and the U.S.

    More “At a Glance” alerts​

    Video Player


    00:00

    00:33


    The Pixel 6 series debuted a revamped “At a Glance” widget, which can display your calendar events, flight boarding pass, workout stats, and more on your home screen and lockscreen. Since its release, Google has added several new features to the widget to further expand its capabilities. Now the company is adding three new features to it.

    Nest Doorbell video feed​

    June feautre drop nest doorbell

    Google added Nest Doorbell alerts back in January to the At a Glance widget, and they can tell you if “Someone’s at your door”. This can help you find out if a package has arrived, or if someone is just trying to get your attention out the front of your house. Now you can see an actual video feed from your doorbell too, right on your home screen.

    Flashlight reminder​

    Ever left your flashlight turned on on your phone? It’s pretty embarrassing, but I’m pretty sure that we’ve all been there. Now you’ll be able to see if it’s on straight from your home screen, without needing to turn your phone around to catch it.

    Coming soon: Air Quality alerts​

    If you live in the U.S., Australia, or India, soon you’ll get Air Quality alerts in your At a Glance widget for your current location.

    Conversation Mode exits beta​

    Sound Amplifier app Conversation mode

    Google previously added “Conversation Mode” to the Sound Amplifier app in the December feature drop, and it’s been in beta since then. It uses on-device machine learning to block out surrounding noise. Conversation Mode is exclusively available to Pixel phone owners, and now it’s exiting beta. It’s designed for people with hearing loss to filter out sounds around them. It amplifies their voice, and you uses the camera to focus on whatever their phone should be properly listening to.

    More features​

    Real Tone Filters​

    Google introduced Real Tone with the Pixel 6 series last year to help users accurately capture various skin tones. The Real Tone functionality used an updated face detection algorithm capable of recognizing more diverse faces in a wider array of lighting conditions, resulting in a better representation of different skin tones.
    At I/O this year, Google expanded on the functionality and announced that it would implement Harvard professor Dr. Ellis Monk’s scale in Search and Photos to achieve similar results across all its products. These filters are now rolling out to users of Google Photos.

    Car Crash Detection comes to Canada​

    Google’s Car Crash Detection is rolling out in Canada now to Google Pixel 3 users and above, though excluding the Pixel 3a. It can, as the name suggests, detect if you’re in a car crash and act accordingly. It’s a safety feature that could potentially save lives.

    More Chat translation languages​

    Chat translation in messages will now be available in Traditional Chinese, Dutch, Korean, Thai, and Turkish for Pixel 6 and Pixel 6 Pro.

    Download and install the June feature drop​

    The June feature drop is now available for all eligible Pixel smartphones, and you can download it by checking for an update in your device’s settings.


    Pixel Update Bulletin—May 2022​


    Published May 2, 2022
    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 2022-05-05 or later address all issues in this bulletin and all issues in the May 2022 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 2022-05-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 May 2022 Android 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.

    Pixel​

    CVEReferencesTypeSeverityComponent
    CVE-2022-20120A-203213034*RCECriticalBootloader
    CVE-2022-20117A-217475903*IDCriticalTitan-M
    CVE-2021-4083A-216408350
    Upstream kernel
    EoPHighKernel
    CVE-2022-20118A-205707793*EoPHighKernel
    CVE-2022-20119A-213170715*IDHighDisplay/Graphics
    CVE-2022-20121A-212573046*IDHighUSCCDMService

    Qualcomm components​

    CVEReferencesSeverityComponent
    CVE-2021-35084A-204909067
    QC-CR#3001178
    ModerateWLAN
    CVE-2021-35085A-204012850
    QC-CR#3001331
    ModerateWLAN
    CVE-2021-35092A-204909309
    QC-CR#2985885 [2]
    ModerateModem
    CVE-2021-35098A-190503256
    QC-CR#2966419
    ModerateAudio

    Qualcomm closed-source components​

    CVEReferencesSeverityComponent
    CVE-2021-35079A-204908838*ModerateClosed-source component

    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 2022-05-05 or later address all issues associated with the 2022-05-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.0May 2, 2022Bulletin Published

    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 (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)

    Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.

    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.

    How I root and update (which is identical whether rooting the first time or updating):
    • Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
    • Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
    • Extracted the new boot.img
    • Copied new boot.img to the phone
    • Patched the new boot.img with Magisk Stable
    • Renamed Magisk'd boot.img so I know what version of firmware it's for
    • Copied the Magisk'd boot.img back to the computer
    • Disabled all my Magisk Modules
    • Removed the "-w " from the flash-all.bat
    • Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
    • Open a Command Prompt, navigated to S:\platform-tools
    • adb reboot bootloader
    • flash-all.bat
    • Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
    • adb reboot bootloader
    • fastboot flash boot kernel.img (renamed Magisk'd boot.img)
    • fastboot reboot
    • Unlock, check everything's working
    • Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
    • Reboot, unlock, made sure everything's working
    Back to modding!

    I may append these first four posts with further useful information or links as needed.
    15
    SDK Platform Tools updated to v33.0.1 (March 2022):

    33.0.1 (March 2022)​

    • adb
      • Fixes Windows mdns crashes.
      • Fixes enable-verity/disable-verity on old devices.
      • Fixes "install multiple" on old devices
      • Improves the help output to include all supported compression methods.
    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 👍
    11
    SDK Platform Tools have been updated to v32.0.0 (January 2022). Update now before you forget and flashing the February update on the 7th gives you hassles. :)

    Direct download for Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

    Revisions​

    32.0.0 (January 2022)​

    • adb
      • Fixed adb w/o args SEGV regression.
    • fastboot
      • Reinstated recovery execution from b/158156979 (removal of preprocessor guards for root/secure).