|13.0.0 (TQ1A.230105.002, Jan 2023)||Flash||Link||924ad4baa13f6611a85bf3d1b2f26f8f61e4e90230b7b69618208323e47a94bb|
Android Security Bulletin—January 2023bookmark_border
Published January 3, 2022
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-01-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.
Android partners are notified of all issues at least a month before publication. Source code patches for these issues will be released to the Android Open Source Project (AOSP) repository in the next 48 hours. We will revise this bulletin with the AOSP links when they are available.
The most severe of these issues is a high security vulnerability in the Framework component that could lead to local escalation of privilege with no additional execution privileges needed. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.
Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform.
Note: Information on the latest over-the-air update (OTA) and firmware images for Google devices is available in the January 2023 Pixel Update Bulletin.
Android and Google service mitigationsThis is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.
- Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
- The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
2023-01-01 security patch level vulnerability detailsIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated 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. Devices with Android 10 and later may receive security updates as well as Google Play system updates.
FrameworkThe most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed.
CVE References Type Severity Updated AOSP versions CVE-2022-20456 A-242703780 EoP High 10, 11, 12, 12L, 13 CVE-2022-20489 A-242703460 EoP High 10, 11, 12, 12L, 13 CVE-2022-20490 A-242703505 EoP High 10, 11, 12, 12L, 13 CVE-2022-20492 A-242704043 EoP High 10, 11, 12, 12L, 13 CVE-2022-20493 A-242846316 EoP High 10, 11, 12, 12L, 13 CVE-2023-20912 A-246301995 EoP High 13 CVE-2023-20916 A-229256049 EoP High 12, 12L CVE-2023-20918 A-243794108 EoP High 10, 11, 12, 12L, 13 CVE-2023-20919 A-252663068 EoP High 13 CVE-2023-20920 A-204584366 EoP High 10, 11, 12, 12L, 13 CVE-2023-20921 A-243378132 EoP High 10, 11, 12, 12L, 13 CVE-2022-20494 A-243794204 DoS High 10, 11, 12, 12L, 13 CVE-2023-20908 A-239415861 DoS High 10, 11, 12, 12L, 13 CVE-2023-20922 A-237291548 DoS High 11, 12, 12L, 13
SystemThe most severe vulnerability in this section could lead to local escalation of privilege of BLE with no additional execution privileges needed.
CVE References Type Severity Updated AOSP versions CVE-2022-20461 A-228602963 EoP High 10, 11, 12, 12L, 13 CVE-2023-20904 A-246300272 EoP High 12L, 13 CVE-2023-20905 A-241387741 EoP High 10 CVE-2023-20913 A-246933785 EoP High 10, 11, 12, 12L, 13 CVE-2023-20915 A-246930197 EoP High 10, 11, 12, 12L, 13
Google Play system updatesThe following issues are included in Project Mainline components.
Subcomponent CVE MediaProvider CVE-2023-20912
2023-01-05 security patch level vulnerability detailsIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated 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.
KernelThe most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
CVE References Type Severity Subcomponent CVE-2022-42719 A-253642087
Upstream kernel             
RCE Critical mac80211 CVE-2022-42720 A-253642015
Upstream kernel             
RCE Critical WLAN CVE-2022-42721 A-253642088
Upstream kernel             
RCE Critical Multiple Modules CVE-2022-2959 A-244395411
EoP High Pipe
Kernel componentsThe most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
CVE References Type Severity Subcomponent CVE-2022-41674 A-253641805
Upstream kernel             
RCE Critical WLAN CVE-2023-20928 A-254837884
EoP High Binder driver
Kernel LTSThe following kernel versions have been updated. Kernel version updates are dependent on the version of Android OS at the time of device launch.
References Android Launch Version Kernel Launch Version Minimum Launch Version A-224575820 12 5.10 5.10.101
Imagination TechnologiesThis vulnerability affects Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of this issue is provided directly by Imagination Technologies.
CVE References Severity Subcomponent CVE-2022-20235 A-259967780 * High PowerVR-GPU
MediaTek componentsThese vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.
CVE References Severity Subcomponent CVE-2022-32635 A-257714327
High gps CVE-2022-32636 A-257846591
High keyinstall CVE-2022-32637 A-257860658
High hevc decoder
Unisoc componentsThese vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.
CVE References Severity Subcomponent CVE-2022-44425 A-258731891
High Kernel CVE-2022-44426 A-258728978
High Kernel CVE-2022-44427 A-258736883
High Kernel CVE-2022-44428 A-258741356
High Kernel CVE-2022-44429 A-258743555
High Kernel CVE-2022-44430 A-258749708
High Kernel CVE-2022-44431 A-258741360
High Kernel CVE-2022-44432 A-258743558
High Kernel CVE-2022-44434 A-258760518
High Android CVE-2022-44435 A-258759189
High Android CVE-2022-44436 A-258760519
High Android CVE-2022-44437 A-258759192
High Android CVE-2022-44438 A-258760781
Qualcomm componentsThese vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
CVE References Severity Subcomponent CVE-2022-22088 A-231156521
Critical Bluetooth CVE-2022-33255 A-250627529
Qualcomm closed-source componentsThese vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
CVE References Severity Subcomponent CVE-2021-35097 A-209469821 * Critical Closed-source component CVE-2021-35113 A-209469998 * Critical Closed-source component CVE-2021-35134 A-213239776 * Critical Closed-source component CVE-2022-23960 A-238203772 * High Closed-source component CVE-2022-25725 A-238101314 * High Closed-source component CVE-2022-25746 A-238106983 * High Closed-source component CVE-2022-33252 A-250627159 * High Closed-source component CVE-2022-33253 A-250627591 * High Closed-source component CVE-2022-33266 A-250627569 * High Closed-source component CVE-2022-33274 A-250627236 * High Closed-source component CVE-2022-33276 A-250627271 * High Closed-source component CVE-2022-33283 A-250627602 * High Closed-source component CVE-2022-33284 A-250627218 * High Closed-source component CVE-2022-33285 A-250627435 * High Closed-source component CVE-2022-33286 A-250627240 * High Closed-source component
Common questions and answersThis 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?
To learn how to check a device's security patch level, see Check and update your Android version.
Device manufacturers that include these updates should set the patch string level to:
- Security patch levels of 2023-01-01 or later address all issues associated with the 2023-01-01 security patch level.
- Security patch levels of 2023-01-05 or later address all issues associated with the 2023-01-05 security patch level and all previous patch levels.
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-01-01 security patch level. Please see this article for more details on how to install security updates.
2. Why does this bulletin have two security patch levels?
This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.
Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
- Devices that use the 2023-01-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.
- Devices that use the security patch level of 2023-01-05 or newer must include all applicable patches in this (and previous) security bulletins.
3. 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.
4. What do the entries in the References column mean?
Abbreviation Definition RCE Remote code execution EoP Elevation of privilege ID Information disclosure DoS Denial of service N/A Classification not available
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
5. What does an * next to the Android bug ID in the References column mean?
Prefix Reference A- Android bug ID QC- Qualcomm reference number M- MediaTek reference number N- NVIDIA reference number B- Broadcom reference number U- UNISOC reference number
Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.
Version Date Notes 1.0 January 3, 2022 Bulletin Published
Community Manager•Original Poster
Google Pixel Update - January 2023Announcement
Hello Pixel Community,
We have provided the monthly software update for January 2023. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next few weeks in phases depending on carrier and device. 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
This update also includes support for static spatial audio, which will provide surround sound for any connected headset. Another update will roll out to Pixel Buds Pro in the coming weeks that will enable spatial audio with head tracking.
Google Pixel Support Team
- Pixel 4a: TQ1A.230105.001
- Pixel 4a (5G): TQ1A.230105.001
- Pixel 5: TQ1A.230105.001
- Pixel 5a (5G): TQ1A.230105.001
- Pixel 6: TQ1A.230105.002
- Pixel 6 Pro: TQ1A.230105.002
- Pixel 6a: TQ1A.230105.001.A2
- Pixel 7: TQ1A.230105.001.A2
- Pixel 7 Pro: TQ1A.230105.002
- Pixel 4a: TQ1A.230105.001.B1
- Pixel 7: TQ1A.230105.001.A3
- Pixel 7 Pro: TQ1A.230105.002.A1
The January 2023 update includes bug fixes and improvements for Pixel users – see below for details.
- Add support for Spatial Audio with certain devices and accessories *
- Additional improvements for fingerprint recognition and response in certain conditions *
- Fix for issue occasionally preventing certain Bluetooth Low Energy devices or accessories from pairing or reconnecting
- Fix for issue preventing audio from playing over certain headphones or accessories while connected in certain conditions
- Fix for issue occasionally causing captured photos to appear corrupted or distorted while zoomed in *
Display & Graphics
- Fix for issue occasionally preventing display from waking or appearing turned off while device is powered on *
- Fix for issue occasionally causing UI to display in landscape layout while device is held in portrait mode
Fixes are available for all supported Pixel devices unless otherwise indicated below.
* Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
* Included on Pixel 6a, Pixel 7
* Included on Pixel 7, Pixel 7 Pro
Regarding Developer Support Android 12 images, see @Lughnasadh's post here.
I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google search
Developer Support Android imagesif you want to find them.
Platform Tools has been updated slightly to v33.0.3:
Release Notes https://developer.android.com/studio/releases/platform-tools:
33.0.3 (Aug 2022)
- Don't retry adb root if first attempt failed.
- Fix track-devices duplicate entry.
- Add receive windowing (increase throughput on high-latency connections).
- More specific error messages in the "more than one device" failure cases.
- Reject unexpected reverse forward requests.
- Fix install-multi-package on Windows.
- Remove e2fsdroid as part of SDK platform-tools.
- Print OemCmdHandler return message on success.
TL;DR regarding the PSA. If you update one slot to Android 13, you can
fastboot reboot bootloaderafter and then
fastboot --set-active=otherto change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.
At a minimum, do this first:
fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img(change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.
IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.
You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.
My tiny, early, very mini-review of Android 13 is here.
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.
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
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.
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)
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?
- You can alternately use the tools from the SDK Manager, but most of us will want to stick to the basic tools-only without the complications of the full development manager.
- 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) #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).
No longer applies -
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.
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
- @sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
- @rickysidhu_'s thread HBM (High Brightness Mode)
- @gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
- @rickysidhu_'s thread Limit Charge
- @Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
- @TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
- Every single one of @foobar66's posts.
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):
Back to modding!
- 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
- 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