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

Search This thread

Lughnasadh

Senior Member
Mar 23, 2015
4,942
5,691
Google Nexus 5
Huawei Nexus 6P
WIll Magisk 22.5 will work to root tq1a.221205.012 image on Pixel 6 Pro? It didn't work on my 7 Pro thus asking...
Do you mean 25.2? If so, it will work on the Pixel 6 Pro (also works on my Pixel 7 Pro).

If you actually mean 22.5, I don't think there is a version with that version number (maybe Canary?). Also, Magisk 22 is very old and likely won't work on either phone.
 
  • Like
Reactions: roirraW "edor" ehT

73sydney

Senior Member
Yes, sorry, version 25.2

Is there any newer version of this?


Watch/bookmark this page - this is where up to date Magisk is discussed.


Links to magisk (and other related tools) are on it

Example...Magisk repos:

Stable:


Shows the current version info in release name and will be xx.x


(Canary):


go to notes.md and you can see the version info (xx.xxx - currently 25205 or 25.205)
 
  • Like
Reactions: roirraW "edor" ehT
So just a note: when unrooting/updating/re-rooting I typically

uninstall root through Magisk
Take the update
Download the new image and extract boot.img
Patch the new boot.img
Reboot to fastboot
fastboot boot <magisk patched image> (not flash)
And then let magisk apply the patch to the boot images through magisk (ensures I have the files to uninstall the patch for the next system update).

However, this time when I tried fastboot boot <magisk patched boot images> I got an error that the command was not found. I ended up flashing the magisk patched boot images, but it seems Google does not want people booting from fastboot.

Anyone else notice this?

Cheers,
B.D.
 

73sydney

Senior Member
So just a note: when unrooting/updating/re-rooting I typically

uninstall root through Magisk
Take the update
Download the new image and extract boot.img
Patch the new boot.img
Reboot to fastboot
fastboot boot <magisk patched image> (not flash)
And then let magisk apply the patch to the boot images through magisk (ensures I have the files to uninstall the patch for the next system update).

However, this time when I tried fastboot boot <magisk patched boot images> I got an error that the command was not found. I ended up flashing the magisk patched boot images, but it seems Google does not want people booting from fastboot.

Anyone else notice this?

Cheers,
B.D.

interesting, i normally (on my previous Pixel 2XL, before i sadly departed, wrongly back to Samsung - glad im back) always fastboot booted the magisk patched image just as a test, before rebooting and flashing it

i havent yet done the update but will try as you did when i get time...

but the previous and current A13 build im on lets me fastboot boot my current magisk patched boot image at least...there is a delay after the image is sent and before it reboots, and i didnt think it was going to do it :)

fastboot.jpg


also its just nice to see you B.D. and not talk about, well, you know :)
 
  • Like
Reactions: BostonDan

Lughnasadh

Senior Member
Mar 23, 2015
4,942
5,691
Google Nexus 5
Huawei Nexus 6P
I just downloaded the Dec 5 update for my P6P
Every time I attempt to copy the boot.img file to my phone for magisk, defender pops up with this message:
WARNING Trojan:Script/Wacatac.H!ml
and then it deletes it.

It didn't matter if I took the download from the OP page 1 or went directly to https://developers.google.com/android/images#raven
always the same warning.

thoughts?
ƒ
False positive. Just disable Defender temporarily.
 

Nergal di Cuthah

Senior Member
Sep 20, 2013
2,022
1,078
Google Pixel 6 Pro
I just downloaded the Dec 5 update for my P6P
Every time I attempt to copy the boot.img file to my phone for magisk, defender pops up with this message:
WARNING Trojan:Script/Wacatac.H!ml
and then it deletes it.

It didn't matter if I took the download from the OP page 1 or went directly to https://developers.google.com/android/images#raven
always the same warning.

thoughts?
ƒ
Yes defender thinks boot.img from December as a 2019 Trojan. Rstore it from defender's quarantine and copy it to your phone. As far as i can tell it's a false positive but there is no way in defender, that i found, to report it as such.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,836
2,421
Curious.

Can I go to settings and do a factory reset without losing root, or would I have to have the original boot.img?
Factory reset just resets the data partition, if you are currently rooted, you will retain root.
I believe Magisk Manager will automatically get installed, but if it does not, you should install it so that you can manage root.
 
  • Like
Reactions: mcwups1

rocketj

Member
Jun 15, 2010
49
8
Boca Raton
Hey guys hope someone can give me some pointer to get my phone going again.
I was doing the December factory update and got this message:
2022-12-15_16-55-06.png


After rebooting the phone goes directly into fastboot.
How can I get going again?
Thanks.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,836
2,421
Hey guys hope someone can give me some pointer to get my phone going again.
I was doing the December factory update and got this message:
View attachment 5786145

After rebooting the phone goes directly into fastboot.
How can I get going again?
Thanks.
It looks like something happened to the connection should flashing.
Make sure the connection is solid, cable is good, the port preferably usb 2 and don't touch until it completes.
Flash again, if it completes, your phone should boot ok.
 

rocketj

Member
Jun 15, 2010
49
8
Boca Raton
It looks like something happened to the connection should flashing.
Make sure the connection is solid, cable is good, the port preferably usb 2 and don't touch until it completes.
Flash again, if it completes, your phone should boot ok.
Thanks for responding.
I tried another cable.. same problem.
Tried a few other things with no luck.
Used android flash tool to load the december patch and flashed patched boot to get root back.
All good now. Hopefully I won't have to go through this process again in january.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    For what it's worth, someone on Reddit posted a screenshot of their conversation with Google Support where Google Support said the March security update for the Pixel 6 series won't drop until March 20th. Haven't seen this verified elsewhere.
    4

    Anyone know if it's ok to upgrade with this release?
    Changelog doesn't mention the fastbootd issue (268872725), so it may not be ok to use the new release for flashing factory images.
    4
    Changelog doesn't mention the fastbootd issue (268872725), so it may not be ok to use the new release for flashing factory images.
    Also, the download links are downloading SDK Platform-tools rev. 34.0.0 not rev. 34.0.1.
    4

    Anyone know if it's ok to upgrade with this release?
    Changelog doesn't mention the fastbootd issue (268872725), so it may not be ok to use the new release for flashing factory images.
    Also, the download links are downloading SDK Platform-tools rev. 34.0.0 not rev. 34.0.1.

    I confirm that link still only gives the v34.0.0 zip. Besides the same version number in the filename, I've checked the hash of the zip file, and it's the same as the 34.0.0 that was released on February 10th.

    I have Aignes Website-Watcher set to let me know when the direct link below leads to an updated file:

    https://dl.google.com/android/repository/platform-tools-latest-windows.zip
    (https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip also gives a 404 error)

    Thanks for the heads-up about the possible impending release, though. Hopefully it actually fixes all the issues everyone had with using 34.0.0 once it is made available.
    4

    My mistake. I just checked the link.
    The download links there are still to the 34.0.0 version as well. Confirmed it's the same zip file, still today.
  • 62
    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).


    Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them.
    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


    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.



    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
    13.0.0 (TQ2A.230305.008.E1, Mar 2023)FlashLinkdef2deefd33b1d70f9d800cb297cf6a8437b73d959cf531300ee40b924c3d369
    13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)FlashLink0d60c5da557bba63a78d6c5c10e22c4d0f8399a1a0e29451571567cfb6cb506c

    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

    (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.
    CVEReferencesTypeSeverityUpdated AOSP versions
    CVE-2023-20906A-221040577EoPHigh11, 12, 12L, 13
    CVE-2023-20911A-242537498EoPHigh11, 12, 12L, 13
    CVE-2023-20917A-242605257 [2]EoPHigh11, 12, 12L, 13
    CVE-2023-20947A-237405974EoPHigh12, 12L, 13
    CVE-2023-20963A-220302519EoPHigh11, 12, 12L, 13
    CVE-2023-20956A-240140929IDHigh12, 12L, 13
    CVE-2023-20958A-254803162IDHigh13
    CVE-2023-20964A-238177121 [2]DoSHigh12, 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.
    CVEReferencesTypeSeverityUpdated AOSP versions
    CVE-2023-20951A-258652631RCECritical11, 12, 12L, 13
    CVE-2023-20954A-261867748RCECritical11, 12, 12L, 13
    CVE-2023-20926A-253043058EoPHigh12, 12L, 13
    CVE-2023-20931A-242535997EoPHigh11, 12, 12L, 13
    CVE-2023-20936A-226927612EoPHigh11, 12, 12L, 13
    CVE-2023-20953A-251778420EoPHigh13
    CVE-2023-20955A-258653813EoPHigh11, 12, 12L, 13
    CVE-2023-20957A-258422561EoPHigh11, 12, 12L
    CVE-2023-20959A-249057848EoPHigh13
    CVE-2023-20960A-250589026 [2] [3]EoPHigh12L, 13
    CVE-2023-20966A-242299736EoPHigh11, 12, 12L, 13
    CVE-2022-4452A-251802307IDHigh13
    CVE-2022-20467A-225880741IDHigh11, 12, 12L, 13
    CVE-2023-20929A-234442700IDHigh13
    CVE-2023-20952A-186803518IDHigh11, 12, 12L, 13
    CVE-2023-20962A-256590210IDHigh13
    CVE-2022-20499A-246539931DoSHigh12, 12L, 13
    CVE-2023-20910A-245299920DoSHigh11, 12, 12L, 13

    Google Play system updates​

    The following issues are included in Project Mainline components.
    SubcomponentCVE
    Media CodecsCVE-2023-20956
    Permission ControllerCVE-2023-20947
    TetheringCVE-2023-20929
    WiFiCVE-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.
    CVEReferencesTypeSeveritySubcomponent
    CVE-2021-33655A-240019719
    Upstream kernel [2] [3]
    EoPHighFrame 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.
    CVEReferencesSeveritySubcomponent
    CVE-2023-20620A-264149248
    M-ALPS07554558 *
    Highadsp
    CVE-2023-20621A-264208866
    M-ALPS07664755*
    Hightinysys
    CVE-2023-20623A-264209787
    M-ALPS07559778 *
    Highion

    Unisoc components​

    These vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.
    CVEReferencesSeveritySubcomponent
    CVE-2022-47459A-264598465
    U-2032124 *
    HighKernel
    CVE-2022-47461A-264834026
    U-2066617 *
    Highsystem
    CVE-2022-47462A-264834568
    U-2066754 *
    Highsystem
    CVE-2022-47460A-264831217
    U-2044606 *
    HighKernel

    Qualcomm components​

    These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
    CVEReferencesSeveritySubcomponent
    CVE-2022-22075A-193434313
    QC-CR#3129138
    QC-CR#3112398 [2] [3]
    HighDisplay
    CVE-2022-40537A-261468700
    QC-CR#3278869 [2] [3] [4]
    HighBluetooth
    CVE-2022-40540A-261470730
    QC-CR#3280498
    HighKernel

    Qualcomm closed-source components​

    These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
    CVEReferencesSeveritySubcomponent
    CVE-2022-33213A-238106224 *CriticalClosed-source component
    CVE-2022-33256A-245402790 *CriticalClosed-source component
    CVE-2022-25655A-261469326 *HighClosed-source component
    CVE-2022-25694A-235102547 *HighClosed-source component
    CVE-2022-25705A-235102507 *HighClosed-source component
    CVE-2022-25709A-235102420 *HighClosed-source component
    CVE-2022-33242A-245402503 *HighClosed-source component
    CVE-2022-33244A-245402728 *HighClosed-source component
    CVE-2022-33250A-245403450 *HighClosed-source component
    CVE-2022-33254A-245403473 *HighClosed-source component
    CVE-2022-33272A-245403311 *HighClosed-source component
    CVE-2022-33278A-245402730 *HighClosed-source component
    CVE-2022-33309A-261468683 *HighClosed-source component
    CVE-2022-40515A-261469638 *HighClosed-source component
    CVE-2022-40527A-261470448 *HighClosed-source component
    CVE-2022-40530A-261471028 *HighClosed-source component
    CVE-2022-40531A-261469091 *HighClosed-source component
    CVE-2022-40535A-261470732 *HighClosed-source component

    Common questions and answers​

    This section answers common questions that may occur after reading this bulletin.
    1. How do I determine if my device is updated to address these issues?
    To learn how to check a device's security patch level, see Check and update your Android version.
    • Security patch levels of 2023-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.
    AbbreviationDefinition
    RCERemote code execution
    EoPElevation of privilege
    IDInformation disclosure
    DoSDenial of service
    N/AClassification not available
    4. What do the entries in the References column mean?
    Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
    PrefixReference
    A-Android bug ID
    QC-Qualcomm reference number
    M-MediaTek reference number
    N-NVIDIA reference number
    B-Broadcom reference number
    U-UNISOC reference number
    5. What does an * next to the Android bug ID in the References column mean?
    Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
    6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
    Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.

    Versions​

    VersionDateNotes
    1.0March 6, 2023Bulletin Published
    1.1March 8, 2023Bulletin 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. 😹

    Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.


    Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.

    There are no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.


    All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. There are at least one or two other How To Guide threads in this section in which folks discuss how to get around banking app restrictions when you're rooted or just have an unlocked bootloader. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
    If users persist in discussing banking apps in this thread, I will have this thread locked and only update this first post when there is new and updated information regarding the subjects of the title of the thread: Unlocking the Pixel 6 Pro bootloader, rooting, and TWRP. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12

    Honorable mention to @Jawomo's aodNotify - Notification Light / LED for Pixel 6 Pro! (XDA link) / Notification light / LED for Pixel - aodNotify (Play Store link), which in my opinion restores useful functionality missing in most phones these days. It also solves some subjective issues some folks have with AOD (Always On Display), and/or solves/works around the problem where AOD is required for the optical fingerprint reader to work without the screen being on.​


    Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
    Official Google Pixel Update and Software Repair (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro yet)

    Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.

    Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen
    Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
    OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.

    ADB/Fastboot, Windows Drivers, and unlocking the bootloader (thanks @sidhaarthm for confirming unlocking the bootloader works as intended, be sure to thank him in his post)
    • You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
    • For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
    • Thanks to @96carboard for posting the details of unlocking the bootloader, be sure to thank him in his post. Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device. Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, or your local bank's app. If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it. My experience on my Pixel 1 was that there were no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. All of this should still be the case. You will also continue to receive updates. Unlike Samsung, Sony, et cetera, which have major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to keep root/re-root.:


      The unlock process works like this:

      1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on (you can put a SIM card if you want, you just don't have to).
      2) When it starts harassing you to join Google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
      3) Settings --> About --> Build number. Repeatedly tap it until it says you're a developer.
      4) Back --> Network --> WiFi and connect it.
      5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize on the phone when requested.

      Using the Platform Tools previously mentioned in command line/terminal:
      6) #
      Code:
      adb reboot-bootloader
      7) #
      Code:
      fastboot flashing unlock

      Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.

      Official Instructions for Locking/Unlocking the Bootloader
    Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
    I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).

    Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.

    Fastboot/ADB Driver Interface - Official Download Link:
    When flashing a full image or unlocking your bootloader, the fastboot interface is being used.

    First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.

    Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.

    Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
    Official Download Page
    "Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"

    It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).

    Rooting-related


    No longer applies - Things that make rooting more complicated on Android 12
    @V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.

    A list of the other important guides - be sure to thank the respective OPs
    For all relevant guide threads just click the yellow "How To Guide" quick filter above the list of threads in the Pixel 6 Pro section.


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

    Custom kernels for stock ROM(s)

    Factory Images (requires an unlocked bootloader)
    It's also handy to have to the full official firmware available, whether it's to recovery from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 6 Pro (Raven) section: Pixel 6 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.

    Note: You can still get the December 2021 Factory Images and OTA from this thread, if you need them for any reason: Alternate links to December - all full factory images and OTAs available

    Full OTA Images (doesn't require an unlocked bootloader)

    The usefulness of having Verity and Verification enabled (now that it's not needed for root) - post #2 below.

    Regarding P6P 5G model numbers and capabilities - post #3 below.

    List of all Pixel monthly security bulletins and Play System Updates - post #4 below.

    How I root and update (which is identical whether rooting the first time or updating):
    • Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
    • Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
    • Extracted the new boot.img
    • Copied new boot.img to the phone
    • Patched the new boot.img with Magisk Stable
    • Renamed Magisk'd boot.img so I know what version of firmware it's for
    • Copied the Magisk'd boot.img back to the computer
    • Disabled all my Magisk Modules
    • Removed the "-w " from the flash-all.bat
    • Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
    • Open a Command Prompt, navigated to S:\platform-tools
    • adb reboot bootloader
    • flash-all.bat
    • Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
    • adb reboot bootloader
    • fastboot flash boot kernel.img (renamed Magisk'd boot.img)
    • fastboot reboot
    • Unlock, check everything's working
    • Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
    • Reboot, unlock, made sure everything's working
    Back to modding!

    I may append these first four posts with further useful information or links as needed.
    15
    SDK Platform Tools updated to v33.0.1 (March 2022):

    33.0.1 (March 2022)​

    • adb
      • Fixes Windows mdns crashes.
      • Fixes enable-verity/disable-verity on old devices.
      • Fixes "install multiple" on old devices
      • Improves the help output to include all supported compression methods.
    15
    The unlock process works like this;

    1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on.
    2) When it starts harassing you to join google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
    3) Settings --> About --> Build number. Tap it until it says you're a developer.
    4) Back --> Network --> Wifi and connect it.
    5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize when requested.
    6) # adb reboot-bootloader
    7) # fastboot flashing unlock

    Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
    13
    Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.

    Canary 23014

    EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4 👍
    12
    I'm less concerned about the steps/commands as I am with how you updated (auto OTA, sideload, factory image), whether you booted to Android 13, and what happened when you rolled back (I assume using the factory image)
    Used a factory image and booted into Android 13. Auto OTA and a sideload of the full OTA will end in the same result as both use update_engine. I did boot into Android 13 so the ARB counter did get incremented.
    Downgraded by just forcing Android 12 system image with a wipe, switched slots, and did it again. It might be able to be done with a full OTA, but I didn't test it because of the following issue:

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

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

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