How To Guide January 3, 2022 firmware (TQ1A.230105.002) - Unlock bootloader / Root Pixel 6 Pro [Raven] / all relevant links

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
Kush M.
Community Manager•Original Poster
3 min. ago


Google Pixel Update - December 2022​

Announcement
Hello Pixel Community,

We have provided the monthly software update for December 2022. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next week 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

Thanks,
Google Pixel Support Team


Software versions

Global
  • Pixel 4a: TQ1A.221205.011
  • Pixel 4a (5G): TQ1A.221205.011
  • Pixel 5: TQ1A.221205.011
  • Pixel 5a (5G): TQ1A.221205.011
  • Pixel 6: TQ1A.221205.011
  • Pixel 6 Pro: TQ1A.221205.011
  • Pixel 6a: TQ1A.221205.011
  • Pixel 7: TQ1A.221205.011
  • Pixel 7 Pro: TQ1A.221205.011

Canada
  • Pixel 4a: TQ1A.221205.011.B1

O2 (UK)
  • Pixel 6a: TQ1A.221205.012
  • Pixel 7: TQ1A.221205.012
  • Pixel 7 Pro: TQ1A.221205.012
What’s included

In addition to new features, the December 2022 software update for Pixel devices includes several fixes and improvements across several areas including device performance, stability, connectivity, and more – see below for some notable improvements.

Apps
  • Fix for issue causing text input to certain fields in the Phone app to display in a darker color
  • Fix for issue occasionally causing playback errors when seeking through video content in certain apps
  • Fix for issue occasionally preventing text messages from restoring from cloud backups during device setup
  • General improvements for background performance in certain Google apps

Audio
  • General improvements for USB audio support for various cables or accessories *[1]
  • General improvements to support various audio codecs with certain devices or accessories *[4]

Battery & Charging
  • Battery usage in Settings displays information since last full charge (up to 7 days)
  • Fix for issue occasionally causing device to power off while Battery Share is active *[4]
  • Fix for issue occasionally causing higher battery usage during media playback with certain apps *[2]
  • Fix for issue occasionally preventing Adaptive charging from working in certain conditions *[2]
  • Fix for issue occasionally preventing wireless charging from working with certain accessories *[2]
  • General improvements for charging, battery usage or thermal performance in certain conditions *[1]

Biometrics
  • Fix for issue occasionally causing audio to skip when played over certain Bluetooth devices or accessories *[2]
  • Fix for issue occasionally delaying when the fingerprint icon is displayed on the lock screen *[1]
  • Fix for issue occasionally preventing fingerprint sensor from detecting touch while always-on display is active *[3]
  • Fix for issue where fingerprint enrollment may occasionally display visual glitches in certain conditions *[1]
  • Improvements for face unlock lock screen helper text shown in certain conditions *[2]

Bluetooth
  • Fix for issue causing music playback to continue without audible sound after ending a call while using certain Bluetooth accessories *[2]
  • Fix for issue occasionally causing audio to skip when played over certain Bluetooth devices or accessories *[2]
  • Fix for issue occasionally preventing audio switching between connected Bluetooth devices in certain conditions
  • Fix for issue occasionally preventing Bluetooth Low Energy devices from displaying a device name during pairing
  • Fix for issue occasionally preventing connection to car head units using older Bluetooth versions
  • Fix for issue occasionally preventing discovery of certain Bluetooth devices or accessories
  • Fix for issue occasionally preventing previously paired Bluetooth devices from reconnecting
  • General improvements for Bluetooth stability and performance in certain conditions

Camera
  • Fix for issue occasionally causing Camera app to crash while zoomed in or switching modes *[2]
  • Fix for issue occasionally causing viewfinder preview to display a blank screen *[2]
  • Fix for issue where video that is recorded while switching between camera modes occasionally shows gaps in playback *[2]
  • General improvements for camera stability and performance in certain conditions

Display & Graphics
  • Fix for issue occasionally causing screen to flicker when waking from always-on display
  • Fix for issue occasionally causing visual artifacts or glitches while using certain apps or games *[3]

Framework
  • Fix for issue occasionally causing notifications to display in a different color theme from the system
  • Fix for issue occasionally causing the wrong character to display after a new line in certain apps or UI elements
  • Fix for issue occasionally causing Work Profile app notifications to appear even if Work Profile is paused
  • Fix for issue occasionally preventing certain apps to rotate to landscape orientation
  • Fix for issue occasionally preventing keyboard from being dismissed while using certain apps

Sensors
  • Fix for issue occasionally preventing "tap to wake" or "lift to wake" from working in certain conditions *[1]
  • Fix for issue occasionally preventing Adaptive brightness from activating in certain conditions
  • Fix for issue occasionally preventing Quick Tap from triggering app or system shortcuts in certain conditions
  • Fix to improve Adaptive brightness transitions during phone calls in certain conditions *[1]
  • General improvements for proximity sensor performance under certain lighting conditions *[1]

System
  • General improvements for system stability and performance in certain conditions
  • General improvements to optimize device thermal performance in certain conditions or use cases *[1]

Telephony
  • Fix for issue causing reduced network or call stability under certain conditions *[2]
  • Fix for issue occasionally preventing network SIM cards from activating in certain conditions *[3]
  • General improvements for network connection stability and performance in certain conditions
  • General improvements for network connectivity after toggling airplane mode off
  • General improvements for switching between 3G to 4G on certain carrier networks
  • General improvements for VPN connection stability and performance on mobile networks under certain conditions
  • General improvements for Wi-Fi calling stability and performance for certain carriers or networks
  • Improve dual SIM network connectivity in certain conditions *[3]
  • Improve RCS messaging stability under certain conditions *[2]

Touch
  • General improvements for touch response and performance in certain conditions *[1]

User Interface
  • Change for home screen search bar behavior to open the Google app when tapping the G logo
  • Fix for issue occasionally causing "Pause work apps" button display over app drawer or in the wrong position
  • Fix for issue occasionally causing certain Settings toggles to appear disabled, or set to the wrong state
  • Fix for issue occasionally causing device color theme to change unexpectedly
  • Fix for issue occasionally causing home screen app icons to appear duplicated after adjusting grid size
  • Fix for issue occasionally causing home screen widgets or icons to appear small or scaled down in certain conditions
  • Fix for issue occasionally causing media player controls to appear invisible or hidden in notification shade
  • Fix for issue occasionally causing notification overflow dot to overlay app icons on lock screen
  • Fix for issue occasionally causing notifications to disappear or appear invisible in notification shade
  • Fix for issue occasionally causing screenshot captures to fail in certain conditions
  • Fix for issue occasionally causing suggested apps in Search to overlap or display over results
  • Fix for issue occasionally causing text to appear incorrectly cutoff or truncated at different font sizes
  • Fix for issue occasionally causing UI to reset after adjusting display resolution
  • Fix for issue occasionally causing wallpaper to appear black or empty in certain conditions
  • Fix for issue occasionally enabling touch interaction during the lock screen transition after screen is turned off
  • Fix for issue occasionally preventing media player album art from updating when content changes
  • Fix for issue occasionally preventing media player controls from displaying on lock screen
  • Fix for issue occasionally preventing screen to appear blank or frozen after launching certain apps
  • Fix for issue where incoming notifications would occasionally display over others listed in the notification shade
  • Fix to improve responsiveness of At A Glance home and lock screen widget for certain conditions or use cases
  • Fix to improve spacing for certain UI modals in device setup and Settings
  • General improvements for performance in certain UI transitions and animationas

Wi-Fi
  • Fix for issue occasionally preventing hotspot from turning on in certain conditions *[1]
  • General improvements for Wi-Fi network connection stability & performance in certain conditions *[1]
---------------------------------------------------------------

Device Applicability

Fixes are available for all supported Pixel devices unless otherwise indicated below.

*[1] Included on Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro
*[2] Included on Pixel 7, Pixel 7 Pro
*[3] Included on Pixel 6, Pixel 6 Pro, Pixel 6a
*[4] Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro


Details
Other
 

roirraW "edor" ehT

Forum Moderator
Staff member
Kush M.
Community Manager•Original Poster

New software features have arrived to the Pixel family​

Announcement
Your Pixel devices get a boost of helpfulness with Feature Drops *[1]. They’re automatic software updates that send new and upgraded features to your phone, earbuds, and watch, making them even better as time goes on. With the latest feature drop, your Pixel phone now has clearer incoming calls *[2], next-level audio with Pixel Buds Pro *[3], speaker labels on recordings *[4], a VPN by Google One for online protection *[5], and more. And it all happens over the air, so you get that new-device feeling without needing to get anything new.

The latest features will begin rolling out to Pixel devices starting on December 5, with rollout continuing over the next few weeks. Be sure to update to the latest Android version and update your Android apps, then look out for a notification from the Pixel Tips app to learn more about all of the ways your Pixel just got more helpful.

Hear voices clearly.
Pixel enhances the other caller’s voice and reduces their background noise to help you hear them when they’re in a noisy place *[2].

Surround yourself with sound (coming January 2023).
Feel like you’re at the center of the action in your favorite movies and shows. When paired with Pixel Buds Pro, your Pixel supports spatial audio with head tracking for immersive surround sound all around *[3].

Note taking just got easier.
Pixel helps you keep track of who said what in meetings and lectures with more than one participant. It transcribes recordings of multiple speakers by labeling each one and adding line breaks when speakers change *[4].

Extra protection when you’re online.
With VPN by Google One, Pixel 7 and Pixel 7 Pro help protect your online activity no matter what app or web browser you use. With no added cost to you *[5].

Wallpaper that wows.
Bring your Pixel screen to life with the new Live Bloom wallpaper collection. Explore the latest set of custom designs featuring vibrant images that shift and sway when your phone moves *[6].

New cultural wallpapers.
Keep your Pixel screens culturally relevant with the latest Curated Culture wallpapers. This new installment, illustrated by Morgan Harper Nichols, celebrates the International Day of Persons with Disabilities. Morgan is an artist, poet, podcaster, and author whose work is inspired by real-life interactions and stories.

Find it. Fast.
Bring the power of Google Search to your Pixel to search your entire phone and the web, so you can quickly find what you’re looking for – a contact, app, screenshot, setting, and more. Now available for Pixel 4a and later.

Security and privacy, simplified.
Now Pixel makes it easier to protect your phone, accounts, and passwords by having all your security and privacy settings in one place. This includes new action cards that notify you of any safety risks and provide easy steps to enhance your privacy and security.

More ways to lift language barriers.
Live Translate can now translate texts in your messaging apps into more languages, including Arabic, Persian, Swedish, Vietnamese, and Danish *[7].

Understand how you sleep.
Pixel can help you understand what affects your sleep, like coughing, snoring, or how much you’re on your phone at bedtime *[8], now available for Pixel 6 & Pixel 6 Pro.

Get smarter about your sleep.
Gain a better understanding of your sleep quality with helpful insights from Sleep Profile on Pixel Watch *[9]. It looks beyond your nightly sleep patterns and tracks your habits and trends over a month-long period. You’ll get a sleep analysis based on 10 key metrics, be matched with one of six sleep animals representing distinct sleeper types, and receive education and personalized metric ranges so you can understand what to focus on to get better rest.
Summary of availability per device
thread-191508448-8769439867867785176.png



† Only available in English (US).

----------------------------------------------------------------

Disclaimers
*[1] Your Pixel will generally receive Feature Drops during the applicable Android update and support periods for the phone. See g.co/pixel/updates for details. Availability of some Feature Drops may vary.
*[2] Available only on Pixel 7 and Pixel 7 Pro. Not available on VOIP calls. Call quality of incoming call depends on the environment, carrier network conditions, and other factors. Actual results may vary.
*[3] Coming in January 2023. Available only on Pixel 6, Pixel 6 Pro, Pixel 7 and Pixel 7 Pro. Requires compatible app and supported content. See
g.co/pixelbudspro/help for details. Pixel Buds Pro sold separately.
*[4] Available only on Pixel 6 or newer Pixel phones. Not available in all languages.
*[5] Available only on Pixel 7 and Pixel 7 Pro. Restrictions apply. Some data is not transmitted through VPN. Not available in all countries. All other Google One membership benefits sold separately. This VPN offer does not impact price or benefits of Google One Premium plan. Use of VPN may increase data costs depending on your plan. See
g.co/pixel/vpn for details.
*[6] Available only on Pixel 6 or newer Pixel phones.
*[7] Available only on Pixel 6 or newer Pixel phones. Not available in all languages or countries. Not available on all media or apps. See
g.co/pixel/livetranslate for more information.
*[8] Not intended to diagnose, cure, mitigate, prevent or treat any disease or condition. Consult your healthcare professional if you have questions about your health. See
g.co/pixel/digitalwellbeing for details.
*[9] Requires Fitbit account and mobile app, and Fitbit Premium membership. Not intended for medical purposes. Consult your healthcare professional for questions about your health. Feature not available in all countries or languages.


Details
Other
 

roirraW "edor" ehT

Forum Moderator
Staff member

Pixel Update Bulletin—December2022​

bookmark_border
Published December 5, 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-12-05 or later address all issues in this bulletin and all issues in the December 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-12-05 patch level. We encourage all customers to accept these updates to their devices.
Note: The Google device firmware images are available on the Google Developer site.

Announcements​

  • In addition to the security vulnerabilities described in the December 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.

Framework​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2022-20504A-225878553EoPModerate13
CVE-2022-20512A-238602879EoPModerate13
CVE-2022-20514A-245727875EoPModerate13
CVE-2022-20524A-228523213EoPModerate13
CVE-2022-20553A-244155265EoPModerate13
CVE-2022-20554A-245770596EoPModerate13
CVE-2022-20510A-235822336IDModerate13
CVE-2022-20511A-235821829IDModerate13
CVE-2022-20513A-244569759IDModerate13
CVE-2022-20523A-228222508IDModerate13
CVE-2022-20530A-231585645IDModerate13
CVE-2022-20538A-235601770IDModerate13
CVE-2022-20559A-219739967IDModerate13
CVE-2022-20543A-238178261DoSModerate13
CVE-2022-20526A-229742774EoPLow13

Media Framework​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2022-20548A-240919398EoPModerate13
CVE-2022-20528A-230172711IDModerate13

System​

CVEReferencesTypeSeverityUpdated AOSP versions
CVE-2021-39771A-224545390EoPModerate13
CVE-2022-20503A-224772890EoPModerate13
CVE-2022-20505A-225981754EoPModerate13
CVE-2022-20506A-226133034EoPModerate13
CVE-2022-20507A-246649179EoPModerate13
CVE-2022-20508A-218679614EoPModerate13
CVE-2022-20509A-244713317EoPModerate13
CVE-2022-20519A-224772678EoPModerate13
CVE-2022-20520A-227203202EoPModerate13
CVE-2022-20522A-227470877EoPModerate13
CVE-2022-20525A-229742768EoPModerate13
CVE-2022-20529A-231583603EoPModerate13
CVE-2022-20533A-232798363EoPModerate13
CVE-2022-20536A-235100180EoPModerate13
CVE-2022-20537A-235601169EoPModerate13
CVE-2022-20539A-237291425EoPModerate13
CVE-2022-20540A-237291506EoPModerate13
CVE-2022-20544A-238745070EoPModerate13
CVE-2022-20546A-240266798EoPModerate13
CVE-2022-20547A-240301753EoPModerate13
CVE-2022-20549A-242702451EoPModerate13
CVE-2022-20550A-242845514EoPModerate13
CVE-2022-20556A-246301667EoPModerate13
CVE-2022-20557A-247092734EoPModerate13
CVE-2022-20558A-236264289EoPModerate13
CVE-2022-42542A-231445184EoPModerate13
CVE-2022-20199A-199291025IDModerate13
CVE-2022-20515A-220733496IDModerate13
CVE-2022-20516A-224002331IDModerate13
CVE-2022-20517A-224769956IDModerate13
CVE-2022-20518A-224770203IDModerate13
CVE-2022-20527A-229994861IDModerate13
CVE-2022-20531A-231988638IDModerate13
CVE-2022-20535A-233605242IDModerate13
CVE-2022-20541A-238083126IDModerate13
CVE-2022-20552A-243922806IDModerate13
CVE-2022-20555A-246194233IDModerate13
CVE-2022-42535A-224770183IDModerate13
CVE-2022-20521A-227203684DoSModerate13
CVE-2022-20545A-239368697DoSModerate13

Kernel components​

In addition to the platform fixes described above, Pixel also ingested the upstream kernel security fixes associated with snapping to LTS version 5.10.107.
More information is available at the Android Common Kernels page.
CVEReferencesTypeSeveritySubcomponent
CVE-2022-0500A-228560539
Upstream kernel
EoPModerateKernel
CVE-2022-1116A-234020136
Upstream kernel
EoPModerateKernel
CVE-2022-1419A-235540888
Upstream kernel
EoPModerateKernel
CVE-2022-20565A-160818461
Upstream kernel
EoPModerateKernel
CVE-2022-20566A-165329981
Upstream kernel [2]
EoPModerateBluetooth L2CAP
CVE-2022-20567A-186777253
Upstream kernel
EoPModerateKernel
CVE-2022-20568A-220738351
Upstream kernel
EoPModerateio_uring
CVE-2022-20571A-234030265
Upstream kernel
EoPModeratedm-verity
CVE-2022-20572A-234475629
Upstream kernel [2]
EoPModeratedm-verity
CVE-2022-28390A-228694391
Upstream kernel
EoPModerateKernel
CVE-2022-30594A-233438137
Upstream kernel [2] [3]
EoPModerateKernel
CVE-2022-34494A-238479990
Upstream kernel
EoPModerateKernel
CVE-2022-34495A-238480163
Upstream kernel
EoPModerateKernel
CVE-2022-20573A-235183128
Upstream kernel [2]
IDModerateKernel

Pixel​

CVEReferencesTypeSeveritySubcomponent
CVE-2022-20582A-233645166 *EoPCriticalLDFW
CVE-2022-20583A-234859169 *EoPCriticalLDFW
CVE-2022-20584A-238366009 *EoPCriticalTF-A
CVE-2022-20585A-238716781 *EoPCriticalLDFW
CVE-2022-20586A-238718854 *EoPCriticalLDFW
CVE-2022-20587A-238720411 *EoPCriticalLDFW
CVE-2022-20588A-238785915 *EoPCriticalLDFW
CVE-2022-20597A-243480506 *EoPCriticalLDFW
CVE-2022-20598A-242357514 *EoPCriticalLDFW
CVE-2022-20599A-242332706 *EoPCriticalPixel firmware
CVE-2022-42534A-237838301 *EoPCriticalTF-A
CVE-2022-20498A-249998113 *IDCriticallibfdt
CVE-2022-20589A-238841928 *IDCriticalLDFW
CVE-2022-20590A-238932493 *IDCriticalLDFW
CVE-2022-20591A-238939706 *IDCriticalLDFW
CVE-2022-20592A-238976908 *IDCriticalLDFW
CVE-2022-20603A-219265339 *RCEHighModem
CVE-2022-20607A-238914868 *RCEHighCellular Firmware
CVE-2022-20610A-240462530 *RCEHighPixel cellular modem
CVE-2022-20561A-222162870 *EoPHighAudio
CVE-2022-20564A-243798789 *EoPHighlibufdt
CVE-2022-42531A-231500967 *EoPHighTF-A
CVE-2022-20562A-231630423 *IDHighAudio processor
CVE-2022-20574A-237582191 *IDHighLDFW
CVE-2022-20575A-237585040 *IDHighLDFW
CVE-2022-20602A-211081867 *IDHighModem
CVE-2022-20604A-230463606 *IDHighExynos Firmware
CVE-2022-20608A-239239246 *IDHighCellular firmware
CVE-2022-42529A-235292841 *IDHighKernel
CVE-2022-42530A-242331893 *IDHighPixel firmware
CVE-2022-42532A-242332610 *IDHighPixel firmware
CVE-2022-20563A-242067561 *EoPModerateBootloader
CVE-2022-20569A-229258234 *EoPModeratePixel Thermal Control Driver
CVE-2022-20576A-239701761 *EoPModerateTelephony
CVE-2022-20577A-241762281 *EoPModeratesitril
CVE-2022-20578A-243509749 *EoPModeraterild_exynos
CVE-2022-20579A-243510139 *EoPModeraterild_exynos
CVE-2022-20580A-243629453 *EoPModeratelibufdt
CVE-2022-20581A-245916120 *EoPModeratePixel camera driver
CVE-2022-20594A-239567689 *EoPModerateWireless Charger
CVE-2022-20596A-239700400 *EoPModerateWireless Charger
CVE-2022-20600A-239847859 *EoPModerateLWIS
CVE-2022-42501A-241231403 *EoPModeraterild_exynos
CVE-2022-42502A-241231970 *EoPModeraterild_exynos
CVE-2022-42503A-241231983 *EoPModeraterild_exynos
CVE-2022-42504A-241232209 *EoPModeraterild_exynos
CVE-2022-42505A-241232492 *EoPModeraterild_exynos
CVE-2022-42506A-241388399 *EoPModeraterild_exynos
CVE-2022-42507A-241388774 *EoPModeraterild_exynos
CVE-2022-42508A-241388966 *EoPModeraterild_exynos
CVE-2022-42509A-241544307 *EoPModeraterild_exynos
CVE-2022-42510A-241762656 *EoPModeraterild_exynos
CVE-2022-42511A-241762712 *EoPModeraterild_exynos
CVE-2022-42513A-241763204 *EoPModeraterild_exynos
CVE-2022-42518A-242536278 *EoPModeraterild_exynos
CVE-2022-42519A-242540694 *EoPModeraterild_exynos
CVE-2022-42520A-242994270 *EoPModeraterild_exynos
CVE-2022-42521A-243130019 *EoPModeraterild_exynos
CVE-2022-42523A-243376893 *EoPModeraterild_exynos
CVE-2022-42525A-243509750 *EoPModeraterild_exynos
CVE-2022-42526A-243509880 *EoPModeraterild_exynos
CVE-2022-20560A-212623833 *IDModerateKernel
CVE-2022-20570A-230660904 *IDModerateModem
CVE-2022-20593A-239415809 *IDModerategralloc
CVE-2022-20595A-239700137 *IDModerateWireless Charger
CVE-2022-20601A-204541506 *IDModerateModem
CVE-2022-20605A-231722405 *IDModerateModem
CVE-2022-20606A-233230674 *IDModerateModem
CVE-2022-20609A-239240808 *IDModerateCellular firmware
CVE-2022-42512A-241763050 *IDModeraterild_exynos
CVE-2022-42514A-241763298 *IDModeraterild_exynos
CVE-2022-42515A-241763503 *IDModeraterild_exynos
CVE-2022-42516A-241763577 *IDModeraterild_exynos
CVE-2022-42517A-241763682 *IDModeraterild_exynos
CVE-2022-42522A-243130038 *IDModeraterild_exynos
CVE-2022-42524A-243401445 *IDModerateModem
CVE-2022-42527A-244448906 *DoSModerateModem

Qualcomm components​

CVEReferencesSeveritySubcomponent
CVE-2022-25677A-235114749
QC-CR#3122626
QC-CR#3103567
ModerateBootloader

Qualcomm closed-source components​

CVEReferencesSeveritySubcomponent
CVE-2021-30348A-202032128 *ModerateClosed-source component
CVE-2022-25675A-208302286 *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-12-05 or later address all issues associated with the 2022-12-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
2. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
AbbreviationDefinition
RCERemote code execution
EoPElevation of privilege
IDInformation disclosure
DoSDenial of service
N/AClassification not available
3. What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
PrefixReference
A-Android bug ID
QC-Qualcomm reference number
M-MediaTek reference number
N-NVIDIA reference number
B-Broadcom reference number
U-UNISOC reference number
4. What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

Versions​

VersionDateNotes
1.0December 5, 2022Bulletin Published
 

hanschke

Senior Member
Mar 30, 2007
1,743
234
Network manager aml_net_331110020 (arm64-v8a) (480-640dpi) (Android 10+) is not updatet from the image. How to update it If I take the apkm from apkmirror because I got an Error.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 62
    13.0.0 (TQ1A.230105.002, Jan 2023)FlashLink924ad4baa13f6611a85bf3d1b2f26f8f61e4e90230b7b69618208323e47a94bb

    Android Security Bulletin—January 2023​

    bookmark_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 mitigations​

    This 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 details​

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

    Framework​

    The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed.
    CVEReferencesTypeSeverityUpdated AOSP versions
    CVE-2022-20456A-242703780EoPHigh10, 11, 12, 12L, 13
    CVE-2022-20489A-242703460EoPHigh10, 11, 12, 12L, 13
    CVE-2022-20490A-242703505EoPHigh10, 11, 12, 12L, 13
    CVE-2022-20492A-242704043EoPHigh10, 11, 12, 12L, 13
    CVE-2022-20493A-242846316EoPHigh10, 11, 12, 12L, 13
    CVE-2023-20912A-246301995EoPHigh13
    CVE-2023-20916A-229256049EoPHigh12, 12L
    CVE-2023-20918A-243794108EoPHigh10, 11, 12, 12L, 13
    CVE-2023-20919A-252663068EoPHigh13
    CVE-2023-20920A-204584366EoPHigh10, 11, 12, 12L, 13
    CVE-2023-20921A-243378132EoPHigh10, 11, 12, 12L, 13
    CVE-2022-20494A-243794204DoSHigh10, 11, 12, 12L, 13
    CVE-2023-20908A-239415861DoSHigh10, 11, 12, 12L, 13
    CVE-2023-20922A-237291548DoSHigh11, 12, 12L, 13

    System​

    The most severe vulnerability in this section could lead to local escalation of privilege of BLE with no additional execution privileges needed.
    CVEReferencesTypeSeverityUpdated AOSP versions
    CVE-2022-20461A-228602963EoPHigh10, 11, 12, 12L, 13
    CVE-2023-20904A-246300272EoPHigh12L, 13
    CVE-2023-20905A-241387741EoPHigh10
    CVE-2023-20913A-246933785EoPHigh10, 11, 12, 12L, 13
    CVE-2023-20915A-246930197EoPHigh10, 11, 12, 12L, 13

    Google Play system updates​

    The following issues are included in Project Mainline components.
    SubcomponentCVE
    MediaProviderCVE-2023-20912

    2023-01-05 security patch level vulnerability details​

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

    Kernel​

    The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
    CVEReferencesTypeSeveritySubcomponent
    CVE-2022-42719A-253642087
    Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
    RCECriticalmac80211
    CVE-2022-42720A-253642015
    Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
    RCECriticalWLAN
    CVE-2022-42721A-253642088
    Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
    RCECriticalMultiple Modules
    CVE-2022-2959A-244395411
    Upstream kernel
    EoPHighPipe

    Kernel components​

    The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
    CVEReferencesTypeSeveritySubcomponent
    CVE-2022-41674A-253641805
    Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
    RCECriticalWLAN
    CVE-2023-20928A-254837884
    Upstream kernel
    EoPHighBinder driver

    Kernel LTS​

    The following kernel versions have been updated. Kernel version updates are dependent on the version of Android OS at the time of device launch.
    ReferencesAndroid Launch VersionKernel Launch VersionMinimum Launch Version
    A-224575820125.105.10.101

    Imagination Technologies​

    This 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.
    CVEReferencesSeveritySubcomponent
    CVE-2022-20235A-259967780 *HighPowerVR-GPU

    MediaTek components​

    These vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.
    CVEReferencesSeveritySubcomponent
    CVE-2022-32635A-257714327
    M-ALPS07573237 *
    Highgps
    CVE-2022-32636A-257846591
    M-ALPS07510064 *
    Highkeyinstall
    CVE-2022-32637A-257860658
    M-ALPS07491374 *
    Highhevc decoder

    Unisoc components​

    These vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.
    CVEReferencesSeveritySubcomponent
    CVE-2022-44425A-258731891
    U-2028856 *
    HighKernel
    CVE-2022-44426A-258728978
    U-2028856 *
    HighKernel
    CVE-2022-44427A-258736883
    U-1888565 *
    HighKernel
    CVE-2022-44428A-258741356
    U-1888565 *
    HighKernel
    CVE-2022-44429A-258743555
    U-1981296 *
    HighKernel
    CVE-2022-44430A-258749708
    U-1888565 *
    HighKernel
    CVE-2022-44431A-258741360
    U-1981296 *
    HighKernel
    CVE-2022-44432A-258743558
    U-1981296 *
    HighKernel
    CVE-2022-44434A-258760518
    U-2064988 *
    HighAndroid
    CVE-2022-44435A-258759189
    U-2064988 *
    HighAndroid
    CVE-2022-44436A-258760519
    U-2064988 *
    HighAndroid
    CVE-2022-44437A-258759192
    U-2064988 *
    HighAndroid
    CVE-2022-44438A-258760781
    U-2064988 *
    HighAndroid

    Qualcomm components​

    These 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.
    CVEReferencesSeveritySubcomponent
    CVE-2022-22088A-231156521
    QC-CR#3052411
    CriticalBluetooth
    CVE-2022-33255A-250627529
    QC-CR#3212699
    HighBluetooth

    Qualcomm closed-source components​

    These 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.
    CVEReferencesSeveritySubcomponent
    CVE-2021-35097A-209469821 *CriticalClosed-source component
    CVE-2021-35113A-209469998 *CriticalClosed-source component
    CVE-2021-35134A-213239776 *CriticalClosed-source component
    CVE-2022-23960A-238203772 *HighClosed-source component
    CVE-2022-25725A-238101314 *HighClosed-source component
    CVE-2022-25746A-238106983 *HighClosed-source component
    CVE-2022-33252A-250627159 *HighClosed-source component
    CVE-2022-33253A-250627591 *HighClosed-source component
    CVE-2022-33266A-250627569 *HighClosed-source component
    CVE-2022-33274A-250627236 *HighClosed-source component
    CVE-2022-33276A-250627271 *HighClosed-source component
    CVE-2022-33283A-250627602 *HighClosed-source component
    CVE-2022-33284A-250627218 *HighClosed-source component
    CVE-2022-33285A-250627435 *HighClosed-source component
    CVE-2022-33286A-250627240 *HighClosed-source component

    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?
    To learn how to check a device's security patch level, see Check and update your Android version.
    • 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.
    Device manufacturers that include these updates should set the patch string level to:
    • [ro.build.version.security_patch]:[2023-01-01]
    • [ro.build.version.security_patch]:[2023-01-05]
    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.
    • 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.
    Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
    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.
    AbbreviationDefinition
    RCERemote code execution
    EoPElevation of privilege
    IDInformation disclosure
    DoSDenial of service
    N/AClassification not available
    4. 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
    5. 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 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.

    Versions​

    VersionDateNotes
    1.0January 3, 2022Bulletin Published

    Kush M.

    Community Manager•Original Poster


    Google Pixel Update - January 2023​

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

    Thanks,
    Google Pixel Support Team


    Software versions

    Global
    • 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

    Canada
    • Pixel 4a: TQ1A.230105.001.B1

    Telstra (AU)
    • Pixel 7: TQ1A.230105.001.A3
    • Pixel 7 Pro: TQ1A.230105.002.A1
    What’s included

    The January 2023 update includes bug fixes and improvements for Pixel users – see below for details.

    Audio
    • Add support for Spatial Audio with certain devices and accessories *[1]

    Biometrics
    • Additional improvements for fingerprint recognition and response in certain conditions *[2]

    Bluetooth
    • 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

    Camera
    • Fix for issue occasionally causing captured photos to appear corrupted or distorted while zoomed in *[3]

    Display & Graphics
    • Fix for issue occasionally preventing display from waking or appearing turned off while device is powered on *[3]

    User Interface
    • Fix for issue occasionally causing UI to display in landscape layout while device is held in portrait mode
    ---------------------------------------------------------------

    Device Applicability

    Fixes are available for all supported Pixel devices unless otherwise indicated below.

    *[1] Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
    *[2] Included on Pixel 6a, Pixel 7
    *[3] Included on Pixel 7, Pixel 7 Pro

    Details
    Other

    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 images if you want to find them.

    Platform Tools has been updated slightly to v33.0.3:

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

    Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

    Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip

    Release Notes https://developer.android.com/studio/releases/platform-tools:

    33.0.3 (Aug 2022)​

    • adb
      • 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.
    • fastboot
      • 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 bootloader after and then fastboot --set-active=other to 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. 😹

    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, 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 👍
    12
    I'm less concerned about the steps/commands as I am with how you updated (auto OTA, sideload, factory image), whether you booted to Android 13, and what happened when you rolled back (I assume using the factory image)
    Used a factory image and booted into Android 13. Auto OTA and a sideload of the full OTA will end in the same result as both use update_engine. I did boot into Android 13 so the ARB counter did get incremented.
    Downgraded by just forcing Android 12 system image with a wipe, switched slots, and did it again. It might be able to be done with a full OTA, but I didn't test it because of the following issue:

    Android 12 doesn't work properly on the Android 13 bootloader.

    It boots up just fine, appears to work just fine, made and received calls and texts, however the issue @bush911 had with WebView crashing is true. It's more than just WebView, the media DRM APEX immediately crashes. WebView crashes sometime after launch when it tries to find out if ClearPlay or WideVine are functional, and DRM Info crashes immediately when I try to launch it. Without DRM working that means you won't be able to play some music or movies and won't be able to use Netflix or any other streaming app.
    There might be more systems or modules nonfunctional, but without working browsers your smartphone isn't going to be more useful than a dumbphone.

    @roirraW "edor" ehT
    So I guess it's time to retract that you can revert to Android 12, because until a modder comes along to cook up a custom Android 12 ROM with Android 13 APEXs or patched ones it won't work.