How To Guide October 3, 2022 Android 13 update (TP1A.221005.002) - PSA about Android 13 in OP - Unlocking the Pixel 6 Pro bootloader & central repository

Search This thread

Lughnasadh

Senior Member
Mar 23, 2015
3,918
4,195
Google Nexus 5
Huawei Nexus 6P
When I connect to my laptop (windows 11 pro insider) it makes a connection sound. The only place I see the phone is in the Devices and Printers section of control panel. Thing is, it shows as USB Root Hub (3.0). When I unplug the phone that disappears. I'm confused.
Well, that's a good sign that at least your computer recognizes it. Still won't power on? Or display just won't come on? Did you hold those buttons down for a long time? What happens if you plug it into a charger?

Maybe if your computer recognizes it, Android Flash Tool will as well.
 
  • Like
Reactions: roirraW "edor" ehT

sas46

Senior Member
Nov 26, 2013
89
13
Florence
I'm willing to flash from the latest SQ3A.220705.001.B2, Jul 2022, EMEA to A13 TP1A.220624.021, Aug 2022

Can I do it or I have to wait the EMEA version?

Also I'm rooted, the best way is still to patch the boot image, boot it and then directly flash it from magisk?
 
  • Like
Reactions: roirraW "edor" ehT

Spookymyo

Senior Member
Well, that's a good sign that at least your computer recognizes it. Still won't power on? Or display just won't come on? Did you hold those buttons down for a long time? What happens if you plug it into a charger?

Maybe if your computer recognizes it, Android Flash Tool will as well.
It recognizes it like I've seen mentioned in EDL articles. It doesn't recognize it as a phone. I've tried the flash tool and it doesn't work. I was just checking EDL instructions and looks like it only works on Qualcomm devices. The P6P is tensor, so I don't know if it'll be possible.
 
  • Wow
Reactions: roirraW "edor" ehT

Lughnasadh

Senior Member
Mar 23, 2015
3,918
4,195
Google Nexus 5
Huawei Nexus 6P
It recognizes it like I've seen mentioned in EDL articles. It doesn't recognize it as a phone. I've tried the flash tool and it doesn't work. I was just checking EDL instructions and looks like it only works on Qualcomm devices. The P6P is tensor, so I don't know if it'll be possible.
Yeah, you won't be able to use the Qualcomm EDL on Tensor. I'm still curious if you tried to hold the power and volume down buttons for a long time. You haven't mentioned if you tried that yet or not.

Also, do you have these drivers installed? If not, wondering if it will make a difference in how your computer sees your phone.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Anyone had a problem with patched magisk not adding zygisk? I used factory patching, ala unzip and run flash-all and also pixel flasher. Whatever reasons magisk 25201 doesnt seem to add zygisk for me so I cant do safetynet etc.
No problems here. Magisk (Stable v25.2, which is the same as Canary 25201) and SafetyNet working great. You've got Zygisk enabled in Magisk's settings?
1660766655887.png

I'm willing to flash from the latest SQ3A.220705.001.B2, Jul 2022, EMEA to A13 TP1A.220624.021, Aug 2022

Can I do it or I have to wait the EMEA version?
Yes, you can do it. There's no knowledge or evidence that there will be split versions for different areas of carriers with this release. That doesn't mean it won't happen, but you can always change to a different build later if one appears. The "Global" one which is out works for everyone.

Also I'm rooted, the best way is still to patch the boot image, boot it and then directly flash it from magisk?
"Best" is subjective, so up to personal preference. If you're asking if it works with Android 13 Stable's kernel (boot.img), yes it does.
 

sas46

Senior Member
Nov 26, 2013
89
13
Florence
No problems here. Magisk (Stable v25.2, which is the same as Canary 25201) and SafetyNet working great.


Yes, you can do it. There's no knowledge or evidence that there will be split versions for different areas of carriers with this release. That doesn't mean it won't happen, but you can always change to a different build later if one appears. The "Global" one which is out works for everyone.


"Best" is subjective, so up to personal preference. If you're asking if it works with Android 13 Stable's kernel (boot.img), yes it does.
You answers are crystal clear, I'll let you know if this goes alright then :ROFLMAO:
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
You answers are crystal clear, I'll let you know if this goes alright then :ROFLMAO:
Awesome! Good luck.

Thanks for the update. Tho i wonder if the factory reset is part of the problem. Forgot to edit the flash-all bat prior. bleh
You're welcome. I doubt it - a factory reset shouldn't cause that issue.

Did you see my question about if you have Zygisk enabled in Magisk's settings?
 
Since I'm reading stuff about this, a note when I first updated to Android 13, when the other slot still had Android 12 the phone REFUSED to stay on the Android 12 slot after "fastboot reboot-bootloader".
To describe it better, slot A was 12, slot B was 13, I was unable to reflash 12 bootloader on slot A even though slot A still had the 12 bootloader. Only after flashing 13 bootloader on slot A could I switch the slot to A and B freely.
A big part of experimentation before flashing 13 to both slots was to see if having the phone on 12 allowed the bootloader to be downgraded, short answer no. So if 13 bootloader is on 1 slot it needs to be on both or else the 12 slot will be unusable.

Fyi when I said 12 I meant Android 12L July and 13, Android 13 August

Edit: fixed grammar and errors when accidentally hit post

My main reason for posting this is maybe it could explain why some people are having bootloops.
 
Last edited:
Awesome! Good luck.


You're welcome. I doubt it - a factory reset shouldn't cause that issue.

Did you see my question about if you have Zygisk enabled in Magisk's settings?
You are the man! I totally forgot to check that one thing. The last update didnt load your complete update and I overlooked the last sentence.
 
  • Love
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Since I'm reading stuff about this, a note when I first updated to Android 13, when the other slot still had Android 12 the phone REFUSED, to switch to the Android 12 slot.
To describe it better, slot A was 12, slot B was 13, I was unable to reflash 12 bootloader on slot A even though slot A still had the 12 bootloader. Only after flashing 13 bootloader on slot A could I switch the slot to A and B freely.
A big part of experimentation before flashing 13 to both slots was to see if having the phone on 12 allowed the bootloader to be downgraded, short answer no. So if 13 bootloader is on 1 slot it needs to be on both or else the 12 slot will be unusable.

Fyi when I said 12 I meant Android 12L July and 13, Android 13 August

Edit: fixed grammar and errors when accidentally hit post
That's strange. Monday I manually flashed the full factory image of Android 13 Stable using flash-all.bat with the "-w" removed, and then Tuesday I switched slots (to the slot that still had Android 12) and did the flash-all.bat yet again.
 
That's strange. Monday I manually flashed the full factory image of Android 13 Stable using flash-all.bat with the "-w" removed, and then Tuesday I switched slots (to the slot that still had Android 12) and did the flash-all.bat yet again.
That's true, it will switch the slot when you type "fastboot --slot a" but if you were to do "fastboot reboot-bootloader" without flashing the 13 bootloader it would have switched back to slot b.
 
  • Like
Reactions: roirraW "edor" ehT

mko000

Senior Member
Jul 27, 2011
465
237
Google Nexus 4
Huawei Nexus 6P
My two pence...Between the Flash Tool and Pixel Flasher, I'd recommend the latter for those looking to update via the factory image. The only thing the Flash Tool can do that Pixel Flasher can't is force flash all partitions. However, Pixel Flasher can't patch a boot image without root.
Pixel Flasher has an option to "Flash on both slots". Isn't that what you mean/what is needed?
Never mind, I mixed up partitions and slots.
 
Last edited:
  • Like
Reactions: roirraW "edor" ehT

Top Liked Posts

  • 4
    No modem update. We'll see what QPR1 Beta 2 brings on Wednesday.
    3
    13.0.0 (TP1A.221005.002, Oct 2022)
    Flash / Link
    d61dff29d5c9ba513a959d1b87be08df59432c7c0dc17092ab462d12492adfd5
    2
    Yeah, when you update via flashing the factory image it always stays on the same slot. Updating via OTA updates the inactive slot and switches to that slot afterward. But I was more curious if you did the Install to Inactive Slot method, which you didn't.
    I flashed my Pixel 6 to inactive slot using PF 4.1, it worked.
    2
    Removing the -w but also adding the patched boot image I presume, since you kept root?
    No, I first did the full upgrade, then reboot (without root), let the phone 'settle' for 2 minutes, reboot to bootloader, flash patched boot image, reboot. Then reinstall Magisk app, reboot again. Reinstall Magisk modules (USNF, Shamiko, my own module). Final reboot.
    2

    Pixel Update Bulletin—October 2022​

    bookmark_border
    Published October 3, 2022
    The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-10-05 or later address all issues in this bulletin and all issues in the October 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
    All supported Google devices will receive an update to the 2022-10-05 patch level. We encourage all customers to accept these updates to their devices.
    Note: The Google device firmware images are available on the Google Developer site.

    Announcements​

    • In addition to the security vulnerabilities described in the October 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

    Security patches​

    Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

    Pixel​

    CVEReferencesTypeSeverityComponent
    CVE-2022-20231A-211485702 *EoPCriticalTrusty
    CVE-2022-20364A-233606615 *EoPCriticalKernel
    CVE-2022-20397A-223086933 *EoPHighlibsitril-se
    CVE-2022-20464A-236042696 *IDHighAudio processor

    Qualcomm components​

    CVEReferencesSeveritySubcomponent
    CVE-2022-22078A-228096042
    QC-CR#2784147 [2]
    ModerateBootloader
    CVE-2022-25664A-228095839
    QC-CR#3092515
    ModerateDisplay
    CVE-2022-25666A-228095650
    QC-CR#3097037
    ModerateKernel

    Qualcomm closed-source components​

    CVEReferencesSeveritySubcomponent
    CVE-2022-25662A-228096097 *ModerateClosed-source component
    CVE-2022-25665A-228096044 *ModerateClosed-source component

    Functional patches​

    For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

    Common questions and answers​

    This section answers common questions that may occur after reading this bulletin.
    1. How do I determine if my device is updated to address these issues?
    Security patch levels of 2022-10-05 or later address all issues associated with the 2022-10-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
    2. What do the entries in the Type column mean?
    Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
    AbbreviationDefinition
    RCERemote code execution
    EoPElevation of privilege
    IDInformation disclosure
    DoSDenial of service
    N/AClassification not available
    3. What do the entries in the References column mean?
    Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
    PrefixReference
    A-Android bug ID
    QC-Qualcomm reference number
    M-MediaTek reference number
    N-NVIDIA reference number
    B-Broadcom reference number
    U-UNISOC reference number
    4. What does an * next to the Android bug ID in the References column mean?
    Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
    5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
    Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

    Versions​

    VersionDateNotes
    1.0October 3, 2022Bulletin Published
  • 5
    Looks like they finally updated the "Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time" section on the download page to include the correct command for Option 2 (adb reboot bootloader rather than adb reboot fastboot).
    5
    This thread confuses me. Can one root a device that is currently sim locked?
    SIM locking, which locks your SIM card to your device, i.e. can't move that same SIM card with another device, is not the same as being Carrier locked. The ability to lock your SIM card to your device is controlled by you only - by default, SIM cards are not locked to the device. You can use the search field in the device Settings to find "SIM card lock", which is in the "More security settings" submenu.

    As the others have said, Carrier unlocking and having the ability to bootloader unlock are two separate things, but typically if a device is not carrier unlocked, then you are also not able to unlock the bootloader. Being carrier unlocked does not necessarily mean you can unlock the bootloader. Example 1: Verizon. Example 2: All Samsung devices bought in the United States that can have mobile data connections. Samsung WI-Fi-only tablets can be bootloader unlocked (at the cost of tripping KNOX permanently), but obviously, in that case, there's no carrier involved.
    5

    BulletinLanguagesPublished dateSecurity patch level
    September 2022Coming soonSeptember 6, 20222022-09-05

    Pixel Update Bulletin—September 2022​


    Published September 6, 2022
    The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-09-05 or later address all issues in this bulletin and all issues in the September 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
    All supported Google devices will receive an update to the 2022-09-05 patch level. We encourage all customers to accept these updates to their devices.
    Note: The Google device firmware images are available on the Google Developer site.

    Announcements​

    • In addition to the security vulnerabilities described in the September 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

    Security patches​

    Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

    Kernel components​

    CVEReferencesTypeSeverityComponent
    CVE-2022-28388A-228694483
    Upstream kernel
    EoPModerateKernel

    Pixel​

    CVEReferencesTypeSeverityComponent
    CVE-2022-20231A-211485702*EoPCriticalTrusty
    CVE-2022-20364A-233606615*EoPCriticalKernel

    Qualcomm components​

    CVEReferencesSeverityComponent
    CVE-2022-25654A-223230190
    QC-CR#3075470
    ModerateKernel

    Qualcomm closed-source components​

    CVEReferencesSeverityComponent
    CVE-2022-25653A-223230071*ModerateClosed-source component

    Functional patches​

    For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

    Common questions and answers​

    This section answers common questions that may occur after reading thisulletin.
    1. How do I determine if my device is updated to address these issues?
    Security patch levels of 2022-09-05 or later address all issues associated with the 2022-09-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
    2. What do the entries in the Type column mean?
    Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
    AbbreviationDefinition
    RCERemote code execution
    EoPElevation of privilege
    IDInformation disclosure
    DoSDenial of service
    N/AClassification not available
    3. What do the entries in the References column mean?
    Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
    PrefixReference
    A-Android bug ID
    QC-Qualcomm reference number
    M-MediaTek reference number
    N-NVIDIA reference number
    B-Broadcom reference number
    U-UNISOC reference number
    4. What does an * next to the Android bug ID in the References column mean?
    Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
    5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
    Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

    Versions​

    VersionDateNotes
    1.0September 6, 2022Bulletin Published
    4
    @roirraW "edor" ehT Thank you, I was just curious in case a situation appeared again where I needed to have both slots the same (I like to ask before I get stuck up a creek w/o a paddle).
    You're welcome. Understood.

    Just at minimum do (and you should do first thing):
    Code:
    fastboot flash bootloader --slot all bootloader.img
    And that'll prevent you from getting stuck. Not doing that, you could wind up being bricked to a point where only Google could repair the phone.
    4
    Changes in this month's build - quoted directly from the Google Pixel Community post (as couldn't see them anywhere).
    Thanks!

    Am I missing something though? I thought September was meant to be a feature drop update?
    No. There should be a new Beta sometime this month, which would be QPR1 Beta 1. I'll have a separate thread for that, or will maybe revive my Beta thread.
  • 59
    13.0.0 (TP1A.221005.002, Oct 2022)
    Flash / Link
    d61dff29d5c9ba513a959d1b87be08df59432c7c0dc17092ab462d12492adfd5

    Kush M.

    Community Manager•Original Poster

    Google Pixel Update - October 2022​

    Announcement
    Hello Pixel Community,

    We have provided the monthly software update for October 2022. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next week in phases depending on carrier and device. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.

    Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin

    Thanks,
    Google Pixel Support Team


    Software versions

    Global
    • Pixel 4 (XL): TP1A.221005.002
    • Pixel 4a: TP1A.221005.002
    • Pixel 4a (5G): TP1A.221005.002
    • Pixel 5: TP1A.221005.002
    • Pixel 5a (5G): TP1A.221005.002
    • Pixel 6: TP1A.221005.002
    • Pixel 6 Pro: TP1A.221005.002
    • Pixel 6a: TP1A.221005.003
    What’s included

    The October 2022 update includes bug fixes and improvements for Pixel users – see below for details.

    Audio
    • Fix for issue occasionally causing audible humming or noise artifacts during calls while using wired headsets *[1]
    • Fix for issue preventing device volume controls in media player notification to work under certain conditions

    Connectivity
    • Fix for issue causing launcher crash when connecting to VPN in certain conditions

    User Interface
    • Fix for issue causing compatibility issues with certain app widgets in Android 13
    • Fix for issue causing media player to display default icon for certain media apps
    • Fix for issue occasionally causing device crash when playing audio from local storage
    • Fix for issue occasionally causing empty Quick Settings tiles to display in notification shade
    • Fix for issue occasionally causing Work Profile toggle button to appear truncated in app drawer

    Wi-Fi
    • Fix for issue occasionally preventing available Wi-Fi networks from displaying in network selection menu in certain apps
    ---------------------------------------------------------------

    Device Applicability

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

    *[1] Included on Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5 and Pixel 5a (5G)
    Details
    Other

    Pixel Update Bulletin—October 2022​

    bookmark_border
    Published October 3, 2022
    The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-10-05 or later address all issues in this bulletin and all issues in the October 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
    All supported Google devices will receive an update to the 2022-10-05 patch level. We encourage all customers to accept these updates to their devices.
    Note: The Google device firmware images are available on the Google Developer site.

    Announcements​

    • In addition to the security vulnerabilities described in the October 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.

    Security patches​

    Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.

    Pixel​

    CVEReferencesTypeSeverityComponent
    CVE-2022-20231A-211485702 *EoPCriticalTrusty
    CVE-2022-20364A-233606615 *EoPCriticalKernel
    CVE-2022-20397A-223086933 *EoPHighlibsitril-se
    CVE-2022-20464A-236042696 *IDHighAudio processor

    Qualcomm components​

    CVEReferencesSeveritySubcomponent
    CVE-2022-22078A-228096042
    QC-CR#2784147 [2]
    ModerateBootloader
    CVE-2022-25664A-228095839
    QC-CR#3092515
    ModerateDisplay
    CVE-2022-25666A-228095650
    QC-CR#3097037
    ModerateKernel

    Qualcomm closed-source components​

    CVEReferencesSeveritySubcomponent
    CVE-2022-25662A-228096097 *ModerateClosed-source component
    CVE-2022-25665A-228096044 *ModerateClosed-source component

    Functional patches​

    For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.

    Common questions and answers​

    This section answers common questions that may occur after reading this bulletin.
    1. How do I determine if my device is updated to address these issues?
    Security patch levels of 2022-10-05 or later address all issues associated with the 2022-10-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
    2. What do the entries in the Type column mean?
    Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
    AbbreviationDefinition
    RCERemote code execution
    EoPElevation of privilege
    IDInformation disclosure
    DoSDenial of service
    N/AClassification not available
    3. What do the entries in the References column mean?
    Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
    PrefixReference
    A-Android bug ID
    QC-Qualcomm reference number
    M-MediaTek reference number
    N-NVIDIA reference number
    B-Broadcom reference number
    U-UNISOC reference number
    4. What does an * next to the Android bug ID in the References column mean?
    Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
    5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
    Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.

    Versions​

    VersionDateNotes
    1.0October 3, 2022Bulletin Published

    Regarding Developer Support Android 12 images, see @Lughnasadh's post here.

    I am not linking directly to the Developer Support Android 12 images because I don't want them to be confused with Stable Android 12, and since the Developer Support images won't receive any OTAs...ever. They likely also will never be manually updated on the Developer Support images site, so they will forever be stuck with the security patch level they're currently on, which will become further out of date every month. You can Google search Developer Support Android images if you want to find them.

    Platform Tools has been updated slightly to v33.0.3:

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

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

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

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

    33.0.3 (Aug 2022)​

    • adb
      • Don't retry adb root if first attempt failed.
      • Fix track-devices duplicate entry.
      • Add receive windowing (increase throughput on high-latency connections).
      • More specific error messages in the "more than one device" failure cases.
      • Reject unexpected reverse forward requests.
      • Fix install-multi-package on Windows.
    • fastboot
      • Remove e2fsdroid as part of SDK platform-tools.
      • Print OemCmdHandler return message on success.

    TL;DR regarding the PSA. If you update one slot to Android 13, you can fastboot reboot bootloader after and then fastboot --set-active=other to change slots in order to flash Android 13 to the new slot, but IF you have Android 13 on one slot and still have Android 12 (including Android 12 bootloader) on the other slot and you try to fully boot into Android 12, you will be permanently bricked and have to seek repair from Google. No one has yet found a way to repair this on our own. I will update if there is any progress. At least a small handful, and probably more, people have done this already.

    At a minimum, do this first: fastboot flash bootloader --slot all bootloader-devicename-slider-1.2-3456789.img (change the name of the bootloader file to the one for your device), then you *should* be much safer than without doing that first. Also note that the bootloader is NOT the same as boot.img (kernel). The bootloader image file has "bootloader" in the filename.

    IF you have already bricked your phone and the screen is blank - there is likely nothing we can do to help. You should seek to get a repair from Google, possibly under warranty.


    You CANNOT go back to Android 12 Stable. It *seems* as if you can, but Android 12 will not work 100% correctly after updating to the Android 13 bootloader.

    My tiny, early, very mini-review of Android 13 is here.

    Note that this is mainly for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store. All of this will also apply to any other (carrier-specific) variant of the Pixel 6 Pro which you can achieve an unlocked bootloader on. This includes T-Mobile and AT&T variants. It's likely Verizon variants will never be able to unlock their bootloader, or if so it will require paying the right person to do so.

    Feel free to ask about general questions, but for anything that's specific to your variant, you should use one of the other already existing threads. You'll find Verizon, AT&T, and T-Mobile-related threads in those respective search results.

    Here there be dragons. 🐉 I am not responsible for anything at all. 😹

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


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

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

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


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

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


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

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

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

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


      The unlock process works like this:

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

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

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

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

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

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

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

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

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

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

    Rooting-related


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

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


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

    Custom kernels for stock ROM(s)

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

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

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

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

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

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

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

    I may append these first four posts with further useful information or links as needed.
    15
    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.
    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.
    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 👍
    11
    SDK Platform Tools have been updated to v32.0.0 (January 2022). Update now before you forget and flashing the February update on the 7th gives you hassles. :)

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

    Revisions​

    32.0.0 (January 2022)​

    • adb
      • Fixed adb w/o args SEGV regression.
    • fastboot
      • Reinstated recovery execution from b/158156979 (removal of preprocessor guards for root/secure).