How To Guide March 21, 2024 Platform-Tools v35.0.1 - Root Pixel 6 Pro [Raven]

Search This thread

LanJie

New member
Sep 15, 2022
2
2
Hi guys, I just got my pixel 6, and updated it to android 13 with 220905.004.A1 (the latest version).
Now I try to root the system by magisk (updated to the latest version).
However, it did not work after I flash the modified boot img and said "cannot load android system. your data may be corrupt".
I try to flash back by using the default factory provided boot.img, still not working.
Is there any way to solve it please. I stuck on this issue for a long time.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Hi guys, I just got my pixel 6, and updated it to android 13 with 220905.004.A1 (the latest version).
Now I try to root the system by magisk (updated to the latest version).
However, it did not work after I flash the modified boot img and said "cannot load android system. your data may be corrupt".
I try to flash back by using the default factory provided boot.img, still not working.
Is there any way to solve it please. I stuck on this issue for a long time.
Hello and welcome!

Try dirty flashing the full factory image - not just the boot.img (remove the -w from the flash-all.bat so that it doesn't wipe). If that doesn't help, a wipe may be necessary. If you have to, you could try 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). It has solved things that the factory image hasn't.

FYI, I have no idea why flashing the modified boot image would cause that issue.

Also, you should do this ASAP if you haven't already:
Code:
adb reboot bootloader
fastboot flash bootloader --slot all bootloader.img

Replace bootloader.img with the name of the bootloader file from the inner zip inside the factory image zip. Don't confuse it with the boot.img, which is the kernel. There are several other threads that might help you specifically with rooting. Click the yellow How To Guide quick filter at the top of the list of threads in this section. There are 2 or 3 root process-related threads.
 

LanJie

New member
Sep 15, 2022
2
2
Thanks so much, you are sosososo cool~
Hello and welcome!

Try dirty flashing the full factory image - not just the boot.img (remove the -w from the flash-all.bat so that it doesn't wipe). If that doesn't help, a wipe may be necessary. If you have to, you could try 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). It has solved things that the factory image hasn't.

FYI, I have no idea why flashing the modified boot image would cause that issue.

Also, you should do this ASAP if you haven't already:
Code:
adb reboot bootloader
fastboot flash bootloader --slot all bootloader.img

Replace bootloader.img with the name of the bootloader file from the inner zip inside the factory image zip. Don't confuse it with the boot.img, which is the kernel. There are several other threads that might help you specifically with rooting. Click the yellow How To Guide quick filter at the top of the list of threads in this section. There are 2 or 3 root process-related threads.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
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.
 

roirraW "edor" ehT

Forum Moderator
Staff member

Apparently people on Verizon weren't getting the September Verizon OTA until today (not counting flashing it manually).
 

Nergal di Cuthah

Senior Member
Sep 20, 2013
2,737
1,956
Google Pixel 6 Pro

roirraW "edor" ehT

Forum Moderator
Staff member
I'm on the fully up-to-date Stable v88.x Phone app, and the Beta program is full in the Play Store. I assume you could install the Beta version from another site, but quite often these features are enabled on the server side, so just installing the Beta v90.x Phone app won't necessarily see this feature. I enabled it in Developer Options anyway.


You can test Android 13’s predictive back gesture with the Pixel Phone app today


Abner Li
Sep. 28th 2022 9:33 am PT
@technacity

With Android 13, Google began work on a predictive back gesture to “let users preview the destination or other result of a back gesture before fully completing it,” and you can now preview it with the Phone app on Pixel.

You first need to enable Developer options (Settings > About phone > tap “Build number” — located at the bottom — seven times). Once done, use Settings search to find “Predictive back animations” and enable that toggle.
After that, make sure the Google Phone app is up-to-date and/or part of the beta channel. We’re seeing predictive back gesture support live on version 90.0.x.
Every time you use the back gesture (to exit) while on one of the main views/tabs (Favorites, Recents, Contacts, Voicemail), the app window will shrink down and you’ll see your homescreen in addition to the usual back arrow. The windowing animation used here is nice, and this works on both the left and right edges of the screen.


Pixel Phone predictive back
Pixel Phone predictive back
That is the extent of this feature, and it’s meant to let people “decide whether to continue or stay in the current view.” For example, it prevents accidental app closures while you’re in the middle of a task and could be useful in stopping accidental app closures.
Google calls the predictive back gesture a “multi-year release” as it won’t be enabled by default until Android 14 (API level 34), with only the Pixel’s Phone dialer supporting it today among first-party apps. The preview is meant to spur developer support, and hopefully, there will be wide adoption in roughly a year.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Always on top of things I see! I was gonna post that! :p
:) I try!


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
 
  • Like
Reactions: foobar66

roirraW "edor" ehT

Forum Moderator
Staff member

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
 

Lughnasadh

Senior Member
Mar 23, 2015
6,110
7,567
Google Nexus 5
Huawei Nexus 6P
I'm on the fully up-to-date Stable v88.x Phone app, and the Beta program is full in the Play Store. I assume you could install the Beta version from another site, but quite often these features are enabled on the server side, so just installing the Beta v90.x Phone app won't necessarily see this feature. I enabled it in Developer Options anyway.

I signed up for the Phone beta through this link, even though Play Store said it was full. Maybe it will work for others.
 
  • Love
Reactions: roirraW "edor" ehT

Top Liked Posts

  • 1
    Rooted 6 Pro, A14. To update, the past couple times I've downloaded the zip to my PC, extracted the img, copied to phone, patched img with Magisk, moved back to PC, updated the Flash-All.bat to reference patched img, then ran the Flash-All through Fastboot (or maybe ADB, can't recall). That's been working. I'm updated and keep root, but geez, it's a PITA.
    My phone just alerted me that I have an update and to restart. In the past, I would just install Magisk into the other slot, then reboot. Boom! Updated and root kept.
    I'm assuming that's not possible or else more people would be doing it, yeah?

    Just an update. I gave the old method I mentioned a try...IT WORKED! Disabled my modules in Magisk, unhid Magisk, within Magisk installed image on open slot....then rebooted. Booted back up, was updated and still had root. :)
  • 3
    Am i wrong or is battery optimization gone and replaced by allow background battery use?

    View attachment 6077774
    Tap the "Allow background usage" text and you should see Optimized and Unrestricted options.
    3
    Just a heads-up: on march update iconify refuse to work if trying to hide navbar. Probably because of laposed incompatibility.Pixel expert also doesn't help but mmersive gesture module still alive.

    Thanks!

    I've been using the following since Iconify broke on QPR1, although I had thought about returning since it had been fixed.
    • @DanGLES3's thread Fullscreen/Immersive Gesture Tweaks for Android 10-14 (most up-to-date version available at the GitHub link in his OP). You configure it while flashing the module using the volume keys. I choose:
      • - (Immersive)
      • + (Hide keyboard buttons - Back/Switch keyboard)
      • + (Reduce the size of the keyboard bar)
      • + (Pick the gesture sensitivity - Low/Module Default)
      • + (Enable Gcam fix)
      • - (NOT Wish to disable the back gesture)
    2
    Just a heads-up: on march update iconify refuse to work if trying to hide navbar. Probably because of laposed incompatibility.Pixel expert also doesn't help but mmersive gesture module still alive.
    As the dev of the Fullscreen Gestures module, the breakage on QPR2 is the result of changes made to the framework APK which break the AAPT (used to make the overlays needed to hide the navbar)

    To work around the issue, I had to ship an older framework APK into my module to use it instead of the system one so it could work on QPR2, it's not an optimal solution but it's what's available until an AAPT update releases to address the issue
  • 66
    Pixel 6 Pro [Raven]

    March 4, 2024:







    Here is the blog post with more in-depth info


    February 16, 2024:

    ADB/Fastboot (SDK Platform Tools) v35.0.0

    Direct Windows download link:

    No changelog yet.

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