How To Guide March 20, 2023 TQ2A.230305.008.E1 Global | .F1 WINDTRE/Canada - Root Pixel 6 Pro [Raven] / all relevant links

[roirraW "edor" ehT]

Pixel 6 Pro [Raven]​

March 9, 2023
I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them.
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).

Anyone that updated their platform tools and needs to downgrade can use these links.

Windows

https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip

Mac

https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip

Linux

https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip

Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them.

Spoiler

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

SDK Platform Tools release notes | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

Platform-Tools v34.0.1 is up!
Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them.

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

https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip

34.0.1 (March 2023)​

• adb
  • macOS: Reverted "unstable connectivity (MacBook high speed cable)" resolution due to adb install hang (issue #270205252).
• fastboot
  • Windows: Fixed "mke2fs: Illegal or malformed device name while trying to determine filesystem size" error introduced in Platform tools 34.0.0 (issue #271039230).

March 20, 2023

Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers

developers.google.com

13.0.0 (TQ2A.230305.008.E1, Mar 2023)	Flash	Link	def2deefd33b1d70f9d800cb297cf6a8437b73d959cf531300ee40b924c3d369
13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)	Flash	Link	0d60c5da557bba63a78d6c5c10e22c4d0f8399a1a0e29451571567cfb6cb506c

Google Pixel Update - March 2023 - Google Pixel Community

https://support.google.com/profile/79501506

Kush M.
Community Manager•Original Poster
40 min. ago
Google Pixel Update - March 2023
Announcement
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

Thanks,
Google Pixel Support Team


Software versions

Global

• 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

Canada

• Pixel 7: TQ2A.230305.008.A1
• Pixel 7 Pro: TQ2A.230305.008.A3

WINDTRE (Italy)

• Pixel 7: TQ2A.230305.008.A1
• Pixel 7 Pro: TQ2A.230305.008.A3

What’s included

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.

Apps

• Fix for issue causing Live Translate feature to prompt for translation too frequently in certain apps *[1]
• 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 *[2]
• General improvements for charging, battery usage or performance in certain conditions *[1]
• General improvements for wireless charging stability or performance in certain conditions *[2]

Biometrics

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

Bluetooth

• 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

Camera

• General improvements for camera stability and performance in certain conditions *[1]
• Improvements for color accuracy or exposure level while using the front camera in certain conditions *[3]

Display & Graphics

• Fix for issue occasionally causing display flicker or artifacts in certain apps or conditions *[1]
• Fix for issue occasionally causing instability or playback errors with certain media apps or content *[1]
• Fix for issue occasionally causing video preview to flicker in certain apps *[1]

Framework

• Fix for issue occasionally preventing keyboard from displaying in certain apps or conditions

Sensors

• Additional tuning for haptics intensity and response in certain conditions *[4]
• General improvements for adaptive brightness response in certain conditions

System

• Fix for issue preventing device bootloader from being unlocked in certain conditions *[4]
• Fix for issue preventing device from booting to Android in certain conditions *[4]
• General improvements for system stability and performance in certain conditions
• Kernel updates to 4.14.295 *[5], 4.19.261 *[6], 5.10.149 *[1]

Telephony

• General improvements for network connection stability and performance in certain conditions

Touch

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

User Interface

• 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

Wi-Fi

• 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 *[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 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
*[3] Included on Pixel 7, Pixel 7 Pro
*[4] Included on Pixel 6a
*[5] Included on Pixel 4a
*[6] Included on Pixel 4a (5G), Pixel 5, Pixel 5a (5G)



Details
Other

Android Security Bulletin—March 2023 | Android Open Source Project

source.android.com

(revised v1.1 March 8, 2023)

Android Security Bulletin—March 2023​

bookmark_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 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-03-01 security patch level vulnerability details​

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

Framework​

The 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 [2]	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 [2]	DoS	High	12, 12L, 13

System​

The 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 [2] [3]	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 updates​

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

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

Kernel​

The 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 [2] [3]	EoP	High	Frame Buffer

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.

CVE	References	Severity	Subcomponent
CVE-2023-20620	A-264149248 M-ALPS07554558 *	High	adsp
CVE-2023-20621	A-264208866 M-ALPS07664755*	High	tinysys
CVE-2023-20623	A-264209787 M-ALPS07559778 *	High	ion

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.

CVE	References	Severity	Subcomponent
CVE-2022-47459	A-264598465 U-2032124 *	High	Kernel
CVE-2022-47461	A-264834026 U-2066617 *	High	system
CVE-2022-47462	A-264834568 U-2066754 *	High	system
CVE-2022-47460	A-264831217 U-2044606 *	High	Kernel

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.

CVE	References	Severity	Subcomponent
CVE-2022-22075	A-193434313 QC-CR#3129138 QC-CR#3112398 [2] [3]	High	Display
CVE-2022-40537	A-261468700 QC-CR#3278869 [2] [3] [4]	High	Bluetooth
CVE-2022-40540	A-261470730 QC-CR#3280498	High	Kernel

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.

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

Device manufacturers that include these updates should set the patch string level to:

• [ro.build.version.security_patch]:[2023-03-01]
• [ro.build.version.security_patch]:[2023-03-05]

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.

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

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.

Abbreviation	Definition
RCE	Remote code execution
EoP	Elevation of privilege
ID	Information disclosure
DoS	Denial of service
N/A	Classification 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.

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

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​

Version	Date	Notes
1.0	March 6, 2023	Bulletin Published
1.1	March 8, 2023	Bulletin revised to include AOSP links

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.

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.

Spoiler: Warnings / FYI

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?
  • 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) #

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

@Az Biker's thread [How To Guide] [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root.​

OR

@V0latyle's thread [How To Guide] Root Pixel 6 Pro with Magisk

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.

• Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub. The most recent Magisk Stable is what's recommended these days.
• @sean222's thread Restore WiFi and Cellular Data in Quick Settings (Root Required)
• @rickysidhu_'s thread HBM (High Brightness Mode)
• @gururoop's thread Probable method to upgrade every month, without wiping data and retaining root
• @rickysidhu_'s thread Limit Charge
• @Typhus_' thread [MOD][MAGISK][ANDROID 12] Addon Features for Pixel Devices - Pixel 6 Pro Thread
• @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ - a mod that compliments @Typhus_' mod above, and may eventually completely replace it.
• @TotallyAnxious' thread [MOD] Collection of "Anxious" Modules for Pixel 6/Pro Series
• Every single one of @foobar66's posts.

TWRP (not made for the Pixel 6 Pro yet - will update when it has)

I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 6 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel6pro.html.

Custom kernels for stock ROM(s)

@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

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)

Full OTA Images for Nexus and Pixel Devices

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.

 

[roirraW "edor" ehT]

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

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

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

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

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

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

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

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

Yes - this is covered on Android Source.

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

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

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

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

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

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

 

[roirraW "edor" ehT]

Regarding P6P 5G model numbers and capabilities:

There are three hardware versions:

• G8VOU (AU, US); also listed as G8V0U - zero instead of "oh" on some sites, Google shows the former, G8VOU) - has mmWave 5G support
• GF5KQ (JP) - has mmWave 5G support
• GLUOG (CA, DE, FR, GB, IE, TW) - no mmWave 5G support

For instance, my factory unlocked direct from Google in the United States Pixel 6 Pro 512 GB is a G8VOU. As far as I know, all other variations in each individual phone are controlled by software (which firmware is loaded) and over the internet (which IMEIs are Carrier Unlocked or not, and OEM Unlockable or not).

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

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

 

[roirraW "edor" ehT]

My personal advice for how to get your device back up and running like you had it previously after a factory reset:

1. I use Nova Launcher Prime, so I do backups anytime I change my home screen or app drawer/tabs setup, so widgets and app icons and other Nova-specific configurations are easier to restore.
2. Go to Android Settings and use Settings' search box for Backup. Make sure that your Google account is set up to backup your apps (and app data for the apps that developers have configured to use Google's Backup API). Make sure things are backed up. Note, this doesn't backup the apps themselves, only the list of apps, so only applies to apps installed from the Play Store. As I said in parentheses, developers have to choose to integrate Google's Backup API into their app, and those apps only will get their app data backed up into Google's cloud.
3. If you're rooted also, then you could use something like Swift Backup to backup to the cloud. I do so, although I still restore as much as possible through Google's backup, and I only restore through Swift on a case-by-case basis, as needed when I discover an app that's tough to set back up doesn't have it's data restored by Google.
4. If you've used Google Photos to backup your photos to Google's cloud, then hit the button in Google Photos to free up space. This will automatically and only delete your local copies of photos and videos that it's already backed up.
5. Once that ^ is done, look at your internal storage with your favorite File Manger and see if there's anything left that you want to back up manually, since a factory reset will wipe everything. Copy them to your computer or a flash drive.
6. When you're just starting the out of the box setup after the reset, when it asks you if you want to use a cable to restore things from an old phone, choose No, and that will lead you to Google's cloud backup where you can choose to restore everything, or you can select what you want to restore.
7. I think you can figure out the rest.

 

[roirraW "edor" ehT]

Reserved.

 

[roirraW "edor" ehT]

Reserved.

 

[roirraW "edor" ehT]

Reserved.

 

[roirraW "edor" ehT]

Reserved.

 

[dj24]

If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.

 

[roirraW "edor" ehT]

If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.

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

Good luck!

 

[dj24]

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

Good luck!

This is great. I won't be getting mine for a while as well so please come back and update this thread.

 

[Pekempy]

If you have any reputable youtube links that you think might be of help as well for complete noobs like me, that would be great.

Generally YouTube video guides for software related things aren't particularly helpful, as they can often get outdated very quickly; especially in the early days of a device as they can't be updated when new things are found out.
It would probably be best to carefully read through guides

 

[roirraW "edor" ehT]

@sidhaarthm reports here (be sure to thank him on his original post):

Bootloader successfully unlocked. I will just run everything stock for now - this is just so I don't have to wipe the device later after I have completed full setup and transferred all my data.

View attachment 5441915

 

[roirraW "edor" ehT]

This is great. I won't be getting mine for a while as well so please come back and update this thread.

FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone, otherwise, you'll have to back up anything that doesn't normally get backed up, and go through the initial setup process again. Not a big deal for some, but would likely not be optimal for a new user.

• Instructions for Locking/Unlocking the Bootloader (note that unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device).

 

[Ghisy]

FYI, I'm reminded by several members in these forums that unlocking the bootloader (the first step before being able to root your Carrier-Unlocked Pixel 6 Pro) wipes the device - so does re-locking it. So I highly recommend unlocking it as the first step when you get the phone

This! It's the first thing you should do out of the box if you plan on rooting later.

 

[roirraW "edor" ehT]

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

 

[galaxys]

That's great news about Unlocking the bootloader! I'll be doing that first thing to be ready for the future...

 

[biTToe]

Does this mean to say there is no OEM unlocking switch in the developer options screen?

 

[96carboard]

Does this mean to say there is no OEM unlocking switch in the developer options screen?

There is, its there and you need to flip it.

 

[96carboard]

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.