TPB4 is the last Android 13 beta (Beta 4). They are no longer listed on the website because Android 13 went stable in August. What exactly are you trying to do?What OTA image do i use for TPB4 build number i only see TP1A available for download on the website
unlock bootloader and rootTPB4 is the last Android 13 beta (Beta 4). They are no longer listed on the website because Android 13 went stable in August. What exactly are you trying to do?
Follow the guide in the OP.
i can't extract boot.img because i can't find the ota image to download for TPB4 build number
Update to a newer build. You are on a very old build. And after you do, extract the boot.img from the factory image, not the OTA image (although you can but that's more complicated).i can't extract boot.img because i can't find the ota image to download for TPB4 build number
Tpb4 is dead, as said above it was 13 beta.i can't extract boot.img because i can't find the ota image to download for TPB4 build number
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)
What’s included
- Pixel 6a: TQ1A.221205.012
- Pixel 7: TQ1A.221205.012
- Pixel 7 Pro: TQ1A.221205.012
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
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
![]()
† 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
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
CVE References Type Severity Updated AOSP versions CVE-2022-20504 A-225878553 EoP Moderate 13 CVE-2022-20512 A-238602879 EoP Moderate 13 CVE-2022-20514 A-245727875 EoP Moderate 13 CVE-2022-20524 A-228523213 EoP Moderate 13 CVE-2022-20553 A-244155265 EoP Moderate 13 CVE-2022-20554 A-245770596 EoP Moderate 13 CVE-2022-20510 A-235822336 ID Moderate 13 CVE-2022-20511 A-235821829 ID Moderate 13 CVE-2022-20513 A-244569759 ID Moderate 13 CVE-2022-20523 A-228222508 ID Moderate 13 CVE-2022-20530 A-231585645 ID Moderate 13 CVE-2022-20538 A-235601770 ID Moderate 13 CVE-2022-20559 A-219739967 ID Moderate 13 CVE-2022-20543 A-238178261 DoS Moderate 13 CVE-2022-20526 A-229742774 EoP Low 13 Media Framework
CVE References Type Severity Updated AOSP versions CVE-2022-20548 A-240919398 EoP Moderate 13 CVE-2022-20528 A-230172711 ID Moderate 13 System
CVE References Type Severity Updated AOSP versions CVE-2021-39771 A-224545390 EoP Moderate 13 CVE-2022-20503 A-224772890 EoP Moderate 13 CVE-2022-20505 A-225981754 EoP Moderate 13 CVE-2022-20506 A-226133034 EoP Moderate 13 CVE-2022-20507 A-246649179 EoP Moderate 13 CVE-2022-20508 A-218679614 EoP Moderate 13 CVE-2022-20509 A-244713317 EoP Moderate 13 CVE-2022-20519 A-224772678 EoP Moderate 13 CVE-2022-20520 A-227203202 EoP Moderate 13 CVE-2022-20522 A-227470877 EoP Moderate 13 CVE-2022-20525 A-229742768 EoP Moderate 13 CVE-2022-20529 A-231583603 EoP Moderate 13 CVE-2022-20533 A-232798363 EoP Moderate 13 CVE-2022-20536 A-235100180 EoP Moderate 13 CVE-2022-20537 A-235601169 EoP Moderate 13 CVE-2022-20539 A-237291425 EoP Moderate 13 CVE-2022-20540 A-237291506 EoP Moderate 13 CVE-2022-20544 A-238745070 EoP Moderate 13 CVE-2022-20546 A-240266798 EoP Moderate 13 CVE-2022-20547 A-240301753 EoP Moderate 13 CVE-2022-20549 A-242702451 EoP Moderate 13 CVE-2022-20550 A-242845514 EoP Moderate 13 CVE-2022-20556 A-246301667 EoP Moderate 13 CVE-2022-20557 A-247092734 EoP Moderate 13 CVE-2022-20558 A-236264289 EoP Moderate 13 CVE-2022-42542 A-231445184 EoP Moderate 13 CVE-2022-20199 A-199291025 ID Moderate 13 CVE-2022-20515 A-220733496 ID Moderate 13 CVE-2022-20516 A-224002331 ID Moderate 13 CVE-2022-20517 A-224769956 ID Moderate 13 CVE-2022-20518 A-224770203 ID Moderate 13 CVE-2022-20527 A-229994861 ID Moderate 13 CVE-2022-20531 A-231988638 ID Moderate 13 CVE-2022-20535 A-233605242 ID Moderate 13 CVE-2022-20541 A-238083126 ID Moderate 13 CVE-2022-20552 A-243922806 ID Moderate 13 CVE-2022-20555 A-246194233 ID Moderate 13 CVE-2022-42535 A-224770183 ID Moderate 13 CVE-2022-20521 A-227203684 DoS Moderate 13 CVE-2022-20545 A-239368697 DoS Moderate 13 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.
CVE References Type Severity Subcomponent CVE-2022-0500 A-228560539
Upstream kernelEoP Moderate Kernel CVE-2022-1116 A-234020136
Upstream kernelEoP Moderate Kernel CVE-2022-1419 A-235540888
Upstream kernelEoP Moderate Kernel CVE-2022-20565 A-160818461
Upstream kernelEoP Moderate Kernel CVE-2022-20566 A-165329981
Upstream kernel [2]EoP Moderate Bluetooth L2CAP CVE-2022-20567 A-186777253
Upstream kernelEoP Moderate Kernel CVE-2022-20568 A-220738351
Upstream kernelEoP Moderate io_uring CVE-2022-20571 A-234030265
Upstream kernelEoP Moderate dm-verity CVE-2022-20572 A-234475629
Upstream kernel [2]EoP Moderate dm-verity CVE-2022-28390 A-228694391
Upstream kernelEoP Moderate Kernel CVE-2022-30594 A-233438137
Upstream kernel [2] [3]EoP Moderate Kernel CVE-2022-34494 A-238479990
Upstream kernelEoP Moderate Kernel CVE-2022-34495 A-238480163
Upstream kernelEoP Moderate Kernel CVE-2022-20573 A-235183128
Upstream kernel [2]ID Moderate Kernel Pixel
CVE References Type Severity Subcomponent CVE-2022-20582 A-233645166 * EoP Critical LDFW CVE-2022-20583 A-234859169 * EoP Critical LDFW CVE-2022-20584 A-238366009 * EoP Critical TF-A CVE-2022-20585 A-238716781 * EoP Critical LDFW CVE-2022-20586 A-238718854 * EoP Critical LDFW CVE-2022-20587 A-238720411 * EoP Critical LDFW CVE-2022-20588 A-238785915 * EoP Critical LDFW CVE-2022-20597 A-243480506 * EoP Critical LDFW CVE-2022-20598 A-242357514 * EoP Critical LDFW CVE-2022-20599 A-242332706 * EoP Critical Pixel firmware CVE-2022-42534 A-237838301 * EoP Critical TF-A CVE-2022-20498 A-249998113 * ID Critical libfdt CVE-2022-20589 A-238841928 * ID Critical LDFW CVE-2022-20590 A-238932493 * ID Critical LDFW CVE-2022-20591 A-238939706 * ID Critical LDFW CVE-2022-20592 A-238976908 * ID Critical LDFW CVE-2022-20603 A-219265339 * RCE High Modem CVE-2022-20607 A-238914868 * RCE High Cellular Firmware CVE-2022-20610 A-240462530 * RCE High Pixel cellular modem CVE-2022-20561 A-222162870 * EoP High Audio CVE-2022-20564 A-243798789 * EoP High libufdt CVE-2022-42531 A-231500967 * EoP High TF-A CVE-2022-20562 A-231630423 * ID High Audio processor CVE-2022-20574 A-237582191 * ID High LDFW CVE-2022-20575 A-237585040 * ID High LDFW CVE-2022-20602 A-211081867 * ID High Modem CVE-2022-20604 A-230463606 * ID High Exynos Firmware CVE-2022-20608 A-239239246 * ID High Cellular firmware CVE-2022-42529 A-235292841 * ID High Kernel CVE-2022-42530 A-242331893 * ID High Pixel firmware CVE-2022-42532 A-242332610 * ID High Pixel firmware CVE-2022-20563 A-242067561 * EoP Moderate Bootloader CVE-2022-20569 A-229258234 * EoP Moderate Pixel Thermal Control Driver CVE-2022-20576 A-239701761 * EoP Moderate Telephony CVE-2022-20577 A-241762281 * EoP Moderate sitril CVE-2022-20578 A-243509749 * EoP Moderate rild_exynos CVE-2022-20579 A-243510139 * EoP Moderate rild_exynos CVE-2022-20580 A-243629453 * EoP Moderate libufdt CVE-2022-20581 A-245916120 * EoP Moderate Pixel camera driver CVE-2022-20594 A-239567689 * EoP Moderate Wireless Charger CVE-2022-20596 A-239700400 * EoP Moderate Wireless Charger CVE-2022-20600 A-239847859 * EoP Moderate LWIS CVE-2022-42501 A-241231403 * EoP Moderate rild_exynos CVE-2022-42502 A-241231970 * EoP Moderate rild_exynos CVE-2022-42503 A-241231983 * EoP Moderate rild_exynos CVE-2022-42504 A-241232209 * EoP Moderate rild_exynos CVE-2022-42505 A-241232492 * EoP Moderate rild_exynos CVE-2022-42506 A-241388399 * EoP Moderate rild_exynos CVE-2022-42507 A-241388774 * EoP Moderate rild_exynos CVE-2022-42508 A-241388966 * EoP Moderate rild_exynos CVE-2022-42509 A-241544307 * EoP Moderate rild_exynos CVE-2022-42510 A-241762656 * EoP Moderate rild_exynos CVE-2022-42511 A-241762712 * EoP Moderate rild_exynos CVE-2022-42513 A-241763204 * EoP Moderate rild_exynos CVE-2022-42518 A-242536278 * EoP Moderate rild_exynos CVE-2022-42519 A-242540694 * EoP Moderate rild_exynos CVE-2022-42520 A-242994270 * EoP Moderate rild_exynos CVE-2022-42521 A-243130019 * EoP Moderate rild_exynos CVE-2022-42523 A-243376893 * EoP Moderate rild_exynos CVE-2022-42525 A-243509750 * EoP Moderate rild_exynos CVE-2022-42526 A-243509880 * EoP Moderate rild_exynos CVE-2022-20560 A-212623833 * ID Moderate Kernel CVE-2022-20570 A-230660904 * ID Moderate Modem CVE-2022-20593 A-239415809 * ID Moderate gralloc CVE-2022-20595 A-239700137 * ID Moderate Wireless Charger CVE-2022-20601 A-204541506 * ID Moderate Modem CVE-2022-20605 A-231722405 * ID Moderate Modem CVE-2022-20606 A-233230674 * ID Moderate Modem CVE-2022-20609 A-239240808 * ID Moderate Cellular firmware CVE-2022-42512 A-241763050 * ID Moderate rild_exynos CVE-2022-42514 A-241763298 * ID Moderate rild_exynos CVE-2022-42515 A-241763503 * ID Moderate rild_exynos CVE-2022-42516 A-241763577 * ID Moderate rild_exynos CVE-2022-42517 A-241763682 * ID Moderate rild_exynos CVE-2022-42522 A-243130038 * ID Moderate rild_exynos CVE-2022-42524 A-243401445 * ID Moderate Modem CVE-2022-42527 A-244448906 * DoS Moderate Modem Qualcomm components
CVE References Severity Subcomponent CVE-2022-25677 A-235114749
QC-CR#3122626
QC-CR#3103567Moderate Bootloader Qualcomm closed-source components
CVE References Severity Subcomponent CVE-2021-30348 A-202032128 * Moderate Closed-source component CVE-2022-25675 A-208302286 * Moderate Closed-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.
3. 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.
4. 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 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
Version Date Notes 1.0 December 5, 2022 Bulletin Published
You're welcome!@roirraW "edor" ehT, thanks for posting all the links for the December image.
I have upgraded, kept data & root.
Yes
They changed the time stamp of the zip again, but it's the same file as earlier today.The platform-tools at https://dl.google.com/android/repository/platform-tools-latest-windows.zip still comes out as v34.0.1, but the zip file is dated today (May 10, 2023) and the file size of the zip is 5.79 MB instead of 5.84 MB as the zip was for 34.0.1 previously.
The SHA-256 hash of the fastboot.exe in each are different, too, so something has been definitely changed.
Now the question: Who is brave enough to test?
I understand!Smh the things i have to do to get better signal. Flash again, thanks vzw.
(but sincerely thanks @roirraW "edor" ehT )
tried to flash the latest build of AncientOS with it, did not work. Back to r33.0.3 and it worked fine
platform-tools_r34.0.1-windows is not functioning properly. Back to 33.0.3 we go...
Add me to the list of users that had a problem with platform-tools 34.0.1. I got into a bootloop after running flash-all.bat. Downgraded to 33.0.3, reran the new (old) flash-all.bat, and was all good.
Using 34.0.1, the phone never even got to the fastbootd part of the process
Update
I tested SDK Platform-tools r. 34.0.1 it is not fixed. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
Anyone that updated their platform tools and needs to downgrade can use these links.
Windows
Mac
Linux
Developer Support Android images
if you want to find them.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.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.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.
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.
OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.
- 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:adb reboot-bootloader
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).
@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.
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.
@Freak07's Kirisakura-Kernel for the Pixel 6 Pro (and possibly the Pixel 6)
@DespairFactor's Despair Kernel (I believe also for both the P6P and P6)
@tbalden's CleanSlate Kernel
@acuicultor's Radioactive Kernel
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
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
- 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
I may append these first four posts with further useful information or links as needed.
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.
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 useI'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)
update_engine
. I did boot into Android 13 so the ARB counter did get incremented.