roirraW "edor" ehT
- May 8, 2010
Pixel 7 Pro [Cheetah]
Note that more than three users have said that 34.0.1 did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes)
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).
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
The download links for 33.0.3:
Anyone that updated their platform tools and needs to downgrade can use these links.
March 13, 2023
Download links working now, and thanks to @Ghisy for making me aware the links were up:
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
|13.0.0 (TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada)||Flash||Link||da1d99156fa03162ee8216277a8ff06b626f16efbc7e8b5d12096c5a10ede1ef|
|13.0.0 (TQ2A.230305.008.C1, Mar 2023)||Flash||Link||cefc4e564cb920af510a44a9cdb982ba4e8af879f6796490e03128f12f92189e|
Community Manager•Original Poster
40 min. ago
Google Pixel Update - March 2023
Google Pixel Update - March 2023
Hello Pixel Community,
We have provided the monthly software update for March 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
Google Pixel Support Team
- Pixel 4a: TQ2A.230305.008.C1
- Pixel 4a (5G): TQ2A.230305.008.C1
- Pixel 5: TQ2A.230305.008.C1
- Pixel 5a (5G): TQ2A.230305.008.C1
- Pixel 7: TQ2A.230305.008
- Pixel 7 Pro: TQ2A.230305.008.C1
T-Mobile & MVNOs, Google Fi (US)
- Pixel 4a (5G): TQ2A.230305.008.A3
- Pixel 5: TQ2A.230305.008.A3
- Pixel 5a (5G): TQ2A.230305.008.A3
- Pixel 7: TQ2A.230305.008.A1
- Pixel 7 Pro: TQ2A.230305.008.A3
- Pixel 7: TQ2A.230305.008.A1
- Pixel 7 Pro: TQ2A.230305.008.A3
In addition to new features, the March 2023 software update for Pixel devices includes several fixes and improvements across several areas, including device stability, connectivity, performance and more – see below for some notable improvements.
- Fix for issue causing Live Translate feature to prompt for translation too frequently in certain apps *
- Fix for issue occasionally keeping display on while certain app activities are active
- Fix for issue occasionally preventing screenshots from being captured in certain apps
- Fix for issue occasionally preventing Wallpaper & style settings to open
Battery & Charging
- Fix for issue occasionally causing app-specific battery restriction settings to be reset after a software update
- Fix for issue occasionally preventing Battery Share from charging certain devices or accessories *
- General improvements for charging, battery usage or performance in certain conditions *
- General improvements for wireless charging stability or performance in certain conditions *
- Additional improvements for fingerprint recognition and response in certain conditions *
- Fix for issue occasionally preventing Android Auto to connect wirelessly with certain vehicle head units
- Improvements for connection stability with certain Bluetooth LE headsets or accessories
- General improvements for camera stability and performance in certain conditions *
- Improvements for color accuracy or exposure level while using the front camera in certain conditions *
Display & Graphics
- Fix for issue occasionally causing display flicker or artifacts in certain apps or conditions *
- Fix for issue occasionally causing instability or playback errors with certain media apps or content *
- Fix for issue occasionally causing video preview to flicker in certain apps *
- Fix for issue occasionally preventing keyboard from displaying in certain apps or conditions
- Additional tuning for haptics intensity and response in certain conditions *
- General improvements for adaptive brightness response in certain conditions
- Fix for issue preventing device bootloader from being unlocked in certain conditions *
- Fix for issue preventing device from booting to Android in certain conditions *
- General improvements for system stability and performance in certain conditions
- Kernel updates to 4.14.295 *, 4.19.261 *, 5.10.149 *
- General improvements for network connection stability and performance in certain conditions
- General improvements for touch response and performance in certain conditions *
- Fix for issue causing certain on-device search results to launch apps in work profile
- Fix for issue causing certain text entries in Battery Usage settings to overlap each other while scrolling
- Fix for issue causing home screen UI to appear blurred in certain conditions
- Fix for issue causing lag or delay with switching between apps while third-party launcher apps are in use
- Fix for issue occasionally causing inner launcher icons to appear clipped after closing a folder
- Fix for issue occasionally causing input text to overlap inside search bar
- Fix for issue occasionally causing media player notification to appear cut off or trimmed
- Fix for issue occasionally causing navigation UI to display over Assistant interface
- Fix for issue occasionally causing notification drawer to appear empty or blank
- Fix for issue occasionally causing Overview screen panels to display over home screen
- Fix for issue occasionally causing Quick Settings tiles to be activated while menu is not pulled down
- Fix for issue occasionally causing screen unlock to overlap with notifications, home screen or other UI elements
- Fix for issue occasionally causing silent mode icon to appear hidden or missing from status bar
- Fix for issue occasionally preventing app icon size to scale correctly when changing display size
- Fix for issue occasionally preventing screenshot sharing or editing to work when tapping overlay buttons
- Fix for issue preventing haptic feedback when interacting with notification drawer in certain conditions
- General improvements for performance in certain UI transitions and animations
- Improvements for home screen icon behavior when switching between different grid sizes
- Improvements for status bar layout and response in certain device orientations
- General improvements for Wi-Fi network connection stability & performance in certain conditions
- Improvements for connection stability with certain Wi-Fi 6E-capable routers or networks *
Fixes are available for all supported Pixel devices unless otherwise indicated below.
* Included on Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro
* Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
* Included on Pixel 7, Pixel 7 Pro
* Included on Pixel 6a
* Included on Pixel 4a
* Included on Pixel 4a (5G), Pixel 5, Pixel 5a (5G)
Android Security Bulletin—March 2023bookmark_border
Published March 6, 2023 | Updated March 8, 2023
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-03-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 have been released to the Android Open Source Project (AOSP) repository and linked from this bulletin. This bulletin also includes links to patches outside of AOSP.
The most severe of these issues is a critical security vulnerability in the System component that could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. 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.
Android and Google service mitigationsThis is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.
- Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
- The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
2023-03-01 security patch level vulnerability detailsIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-03-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.
FrameworkThe most severe vulnerability in this section could lead to local escalation of privilege after updating an app to a higher Target SDK with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE References Type Severity Updated AOSP versions CVE-2023-20906 A-221040577 EoP High 11, 12, 12L, 13 CVE-2023-20911 A-242537498 EoP High 11, 12, 12L, 13 CVE-2023-20917 A-242605257  EoP High 11, 12, 12L, 13 CVE-2023-20947 A-237405974 EoP High 12, 12L, 13 CVE-2023-20963 A-220302519 EoP High 11, 12, 12L, 13 CVE-2023-20956 A-240140929 ID High 12, 12L, 13 CVE-2023-20958 A-254803162 ID High 13 CVE-2023-20964 A-238177121  DoS High 12, 12L, 13
SystemThe most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE References Type Severity Updated AOSP versions CVE-2023-20951 A-258652631 RCE Critical 11, 12, 12L, 13 CVE-2023-20954 A-261867748 RCE Critical 11, 12, 12L, 13 CVE-2023-20926 A-253043058 EoP High 12, 12L, 13 CVE-2023-20931 A-242535997 EoP High 11, 12, 12L, 13 CVE-2023-20936 A-226927612 EoP High 11, 12, 12L, 13 CVE-2023-20953 A-251778420 EoP High 13 CVE-2023-20955 A-258653813 EoP High 11, 12, 12L, 13 CVE-2023-20957 A-258422561 EoP High 11, 12, 12L CVE-2023-20959 A-249057848 EoP High 13 CVE-2023-20960 A-250589026   EoP High 12L, 13 CVE-2023-20966 A-242299736 EoP High 11, 12, 12L, 13 CVE-2022-4452 A-251802307 ID High 13 CVE-2022-20467 A-225880741 ID High 11, 12, 12L, 13 CVE-2023-20929 A-234442700 ID High 13 CVE-2023-20952 A-186803518 ID High 11, 12, 12L, 13 CVE-2023-20962 A-256590210 ID High 13 CVE-2022-20499 A-246539931 DoS High 12, 12L, 13 CVE-2023-20910 A-245299920 DoS High 11, 12, 12L, 13
Google Play system updatesThe following issues are included in Project Mainline components.
Subcomponent CVE Media Codecs CVE-2023-20956 Permission Controller CVE-2023-20947 Tethering CVE-2023-20929 WiFi CVE-2022-20499, CVE-2023-20910
2023-03-05 security patch level vulnerability detailsIn the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-03-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
KernelThe vulnerability in this section could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE References Type Severity Subcomponent CVE-2021-33655 A-240019719
Upstream kernel  
EoP High Frame Buffer
MediaTek componentsThese vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.
CVE References Severity Subcomponent CVE-2023-20620 A-264149248
High adsp CVE-2023-20621 A-264208866
High tinysys CVE-2023-20623 A-264209787
Unisoc componentsThese vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.
CVE References Severity Subcomponent CVE-2022-47459 A-264598465
High Kernel CVE-2022-47461 A-264834026
High system CVE-2022-47462 A-264834568
High system CVE-2022-47460 A-264831217
Qualcomm componentsThese vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
CVE References Severity Subcomponent CVE-2022-22075 A-193434313
QC-CR#3112398  
High Display CVE-2022-40537 A-261468700
QC-CR#3278869   
High Bluetooth CVE-2022-40540 A-261470730
Qualcomm closed-source componentsThese vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
CVE References Severity Subcomponent CVE-2022-33213 A-238106224 * Critical Closed-source component CVE-2022-33256 A-245402790 * Critical Closed-source component CVE-2022-25655 A-261469326 * High Closed-source component CVE-2022-25694 A-235102547 * High Closed-source component CVE-2022-25705 A-235102507 * High Closed-source component CVE-2022-25709 A-235102420 * High Closed-source component CVE-2022-33242 A-245402503 * High Closed-source component CVE-2022-33244 A-245402728 * High Closed-source component CVE-2022-33250 A-245403450 * High Closed-source component CVE-2022-33254 A-245403473 * High Closed-source component CVE-2022-33272 A-245403311 * High Closed-source component CVE-2022-33278 A-245402730 * High Closed-source component CVE-2022-33309 A-261468683 * High Closed-source component CVE-2022-40515 A-261469638 * High Closed-source component CVE-2022-40527 A-261470448 * High Closed-source component CVE-2022-40530 A-261471028 * High Closed-source component CVE-2022-40531 A-261469091 * High Closed-source component CVE-2022-40535 A-261470732 * High Closed-source component
Common questions and answersThis section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
To learn how to check a device's security patch level, see Check and update your Android version.
Device manufacturers that include these updates should set the patch string level to:
- Security patch levels of 2023-03-01 or later address all issues associated with the 2023-03-01 security patch level.
- Security patch levels of 2023-03-05 or later address all issues associated with the 2023-03-05 security patch level and all previous patch levels.
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-03-01 security patch level. Please see this article for more details on how to install security updates.
2. Why does this bulletin have two security patch levels?
This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.
Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
- Devices that use the 2023-03-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-03-05 or newer must include all applicable patches in this (and previous) security bulletins.
3. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
4. What do the entries in the References column mean?
Abbreviation Definition RCE Remote code execution EoP Elevation of privilege ID Information disclosure DoS Denial of service N/A Classification not available
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
5. What does an * next to the Android bug ID in the References column mean?
Prefix Reference A- Android bug ID QC- Qualcomm reference number M- MediaTek reference number N- NVIDIA reference number B- Broadcom reference number U- UNISOC reference number
Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.
Version Date Notes 1.0 March 6, 2023 Bulletin Published 1.1 March 8, 2023 Bulletin revised to include AOSP links
Here there be dragons. I am not responsible for anything at all.
VERY IMPORTANT - On the Pixel 7/Pro, we use Magisk to patch Thanks to @edcsxz, @Lughnasadh, and @AndyYan for news about that and confirming it.
init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition.
Moved @mariusnoor's provided zero-day OTA.zip to Post #8 - Old news from the OP.
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 Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers.
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 permanent negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while your bootloader is unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that it's 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.
- Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
- How to Root the first time / aka How to unlock the Bootloader
- TL;DR - for the seasoned repeat users
- Unlocking Bootloader (required in order to root)
- How to update each month (and also how to root)[requires an unlocked bootloader for updating via this factory image method]
- OPTIONAL: If you want to flash both slots, after this first time, then after do the following
- Optional steps when updating - flashing custom kernels
- The two schools of thought on disabling Verity and Verification
- ADB/Fastboot and Windows USB Drivers - direct download links and the most recent changelog
- Post #3 - Other, most important resources:
- A list of other important apps
- TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
- Factory Images (requires an unlocked bootloader)
- Full OTA Images(doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
- @mariusnoor's provided official URL to download the zero-day OTA to
- @mariusnoor's provided official URL to download the zero-day OTA to
- Check warranty status
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)
- 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 - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
- Find problem apps, Magisk, and LSposed Modules by (three different methods)
- Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
- How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
- How to unroot
- Post #4 - Build ID definitions
- Post #5 - Blank
- Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version
- Post #7 - My personal advice for how to get your device back up and running as you had it before a factory reset
- Post #8 - Old news from the OP
Thank you to the following users who have all contributed greatly to my knowledge of Pixels since I came back to XDA a year ago after a few years of mostly inactivity. Apologies if I miss anybody. In alphabetical order:
- @Az Biker
- @[email protected]
- And many others from all of the previous years who I thanked in my previous OPs.