How To Guide Android 13 is OUT! (August 15, 2022 - TP1A.220624.021) - Unlocking the Pixel 6 Pro bootloader & central repository of relevant links

Search This thread

LLStarks

Senior Member
Jun 1, 2012
1,917
1,126
Since new does not equal better, please let us know your thoughts on that as well! Your insights have been excellent thus far!
Only thing I've spotted so far is the n71_n71 combo being back again. Not very useful.

Vo5G is still present for T-Mobile, Metro, and Assurance. Other T-Mobile MVNOs like Simple, Red Pocket, Tracfone, etc might not be far behind with references like the below.

Code:
ims.ims_user_agent_string > T-Mobile VoNR-ePDG-IR94-RTT-ussd #MANUFACTURE#/#MODEL# #BUILD#
 

roirraW "edor" ehT

Forum Moderator
Staff member
Any wagers yet on how soon this new feature will get the axe? Let's see...we have to wait long enough for it to start to become popular, so maybe two years or so, then they can kill it. 😜

Or maybe it will be just unpopular enough that it sticks around forever and Google just never updates it.

YZBbyXz2w73kAyoTiBRF7Adhyb6friCk-34kfMDA6hdjjcDENW_WDpeSNhN7ObQwh5NkhUnSn9dTMH-v7WJrzdClQ9HicwFU-T_5FSkR8hDiULmgXHXlI8zXVlbLTR6ceTWx5n2uFQWscd32KG_6vaxBvsO2TC10HgB5659J47cR_l9za8mANr4gtCbU98328gb017i4CeUp5ihC4CiD6uuktGkBLvCL1VBdxqhOuaYPhEqdZyH_fhrJOShFWfbDZ5ECGiz6rGiHUhFtAOIfVRdNP04aV3Pho7ZIUEdEIYwyWygxPtw6GQkQ23ADaAuB0DQQXiSvEOyKAHEO6L02ceSfz1tHB1NGvAbV9ycbViZTLnIa7SUykEQzrin8n2hCe-LXH0sEgBx1QwcZF5qhLUi6osyMAKJSF5EDsSUjE1HN4q1C2PRcQCJvGHKwtECxjIbtHN4uj0TRfq9_OzdNf41usJHeQIpDR1nr6G3bAEEzUutii-YWuVckdAnc_rOoCvcCnI7LRZXiidJViF8uziNyt7ooPiCu1UEHZ9p0kjzMytXJsD_TMrDW51yNiPkhtqceX7M7bcjR1H901Hs66f2ou2p6mXJoKHzGnrGdyR_JcD-q7EUGRhrNo4iqUEeZwKRN5pWMEU8wZEqnKtTEajXbfolnJlQkcQYnwa2tlNICEOQv6HKABW7PlRX9Fo02nCrBNIdnV_7Dj1weMFAcVKBmaL_8_2tu8YRr2KIvAFCmW0lgJI_545xJkUc2TbiXwhNbsSink8ru5PwZnUK4WIfgpPPSyoQ1hFCRqKGqBjBvm1Zel7K7b-zzU49MZdA6fi2nykoHtXOeRdi87npCiZBj8bOOmTWff_zxAc--Xu5DCSfdk06QtpwXP8qQ8bdNx7DyyGuxgAF2PcebljXk7McWyKiZklogPznjivrAPuuqacM9sZlqCNVrXyuKKw4aZk4kOA2-ENw46dyHtCQrlHq0N31y=w557-h1206-no
 
  • Haha
Reactions: Lughnasadh and jcp2

roirraW "edor" ehT

Forum Moderator
Staff member
Magisk Stable v25.1 is out.

Magisk Changelog​

v25.1​

  • [MagiskBoot] Fix ramdisk backup being incorrectly skipped
  • [MagiskBoot] Add new feature to detect unsupported dtb and abort during installation
  • [Zygisk] Change binary hijack paths
  • [App] Fix incorrect recovery mode detection and installation
  • [MagiskInit] Fix config not properly exported in legacy SAR devices
  • [General] Enforce the Magisk app to always match or be newer than magiskd

v25.0​

  • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
  • [MagiskInit] Introduce new sepolicy injection mechanism
  • [MagiskInit] Support Oculus Go
  • [MagiskInit] Support Android 13 GKIs (Pixel 6)
  • [MagiskBoot] Fix vbmeta extraction implementation
  • [App] Fix stub app on older Android versions
  • [App] [MagiskSU] Properly support apps using sharedUserId
  • [MagiskSU] Fix a possible crash in magiskd
  • [MagiskSU] Prune unused UIDs as soon as system_server restarts to prevent UID reuse attacks
  • [MagiskSU] Verify and enforce the installed Magisk app’s certificate to match the distributor’s signature
  • [MagiskSU] [Zygisk] Proper package management and detection
  • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
  • [Zygisk] Fix Zygisk’s self code unloading implementation
  • [DenyList] Fix DenyList on shared UID apps
  • [BusyBox] Add workaround for devices running old kernels

2022.6.19 Magisk v25.1​

v25.1 fixes some minor bugs over v25.0. The following are the same as v25.0 release notes.
Another major release! A lot of the changes aren’t visible at the surface, but v25 is actually a really substantial upgrade!

MagiskInit Rewrite​

A significant portion of magiskinit (the critical software that runs before your device boots up) is completely rewritten from scratch. Ever since Android introduced Project Treble in Android 8.0, Magisk has been constantly fighting against the increasingly complex partitioning and early mount setups of all kinds of devices, sometimes with weird OEM specific implementations. It got to a point that magiskinit had become so complicated that few people (including myself!) were aware of every detail, and maintaining this piece of software like this was clearly not sustainable. After many months of planning (yes, this whole re-architecture has been in my head for a long time) and some help from external contributors, a whole new sepolicy injection mechanism is introduced into Magisk, solving the “SELinux Problem” once and for all.

Since this is a full paradigm shift on how Magisk hot-patch the device at boot, several behaviors that many developers implicitly relied on might not exist. For example, Magisk no longer patches fstabs in most scenarios, which means AVB will remain intact; some custom kernels rely on AVB being stripped out for them by Magisk.

MagiskSU Security Enhancements​

The superuser functionality of Magisk has not seen much changes ever since its introduction. v25 focuses on making root permission management more accurate and secure:

  • Add a whole new package tracking system to ensure malicious UID reuse attack cannot be performed
  • Properly support and implement the UX in the Magisk app for packages using sharedUserId
  • Enforce root manager APK signature verification to combat the rampant unofficial Magisk app “mods”
Many might not realize, but using a trusted, unmodified Magisk app is really important. Magisk’s root daemon treats the Magisk app differently and gives it blanket root access without any restrictions. A modded Magisk app can potentially backdoor your device.

And in case some of you are about to put on your tin foil hats, this is not designed to “vendor lock-in”; the goal is to make sure your root management app comes from the same developer of the underlying root implementation. Magisk’s build system allows custom distributors to use its own signing keys, and in addition, I am also providing official debug builds which skips any signature verification for development.
 

EastonCo

New member
Jun 9, 2022
3
2
(y) yeah, it may not be possible to remove the greyed out oem unlocking just by removing a package with these phones. IIRC, previously it didn't work to unlock bootloader just with the temp sim unlock, but if it does for you that would be great news! It's much easier to obtain a temp sim unlock than a perm unlock 😂

What you do in this case is call your provider and tell them you need to unlock the phone for an international sim as you are traveling. Make all the temporary things they do, such as tmobile's app, not work (Just tell them its not working). Eventually they will just unlock it fully.
 

Lughnasadh

Senior Member
Mar 23, 2015
3,577
3,686
Google Nexus 5
Huawei Nexus 6P
...Wait for it...wait for it...

Wah. Next Monday?
Oh no! They "usually" release it the next day, or sometimes the next day or two.

Important: The Android Security Bulletins are published on the first Monday of each month unless that Monday falls on a holiday. If the first Monday of the month is a holiday the bulletins will be published on the following work day.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
Oh no! They "usually" release it the next day, or sometimes the next day or two.

Important: The Android Security Bulletins are published on the first Monday of each month unless that Monday falls on a holiday. If the first Monday of the month is a holiday the bulletins will be published on the following work day.

Looks like July 7.

  • For July, the Android public security bulletin will be released on July 7, 2021
Thanks! I didn't realize they ever mention when the next update will come out in those bulletins.
 
  • Like
Reactions: Lughnasadh

DespairFactor

Recognized Developer / Inactive RC
Mar 13, 2013
6,030
13,138
Toronto
Oh no! They "usually" release it the next day, or sometimes the next day or two.

Important: The Android Security Bulletins are published on the first Monday of each month unless that Monday falls on a holiday. If the first Monday of the month is a holiday the bulletins will be published on the following work day.

Looks like July 7.

  • For July, the Android public security bulletin will be released on July 7, 2021
this is 2021...
 

Top Liked Posts

  • 8
    I think this just means you won't be able to downgrade the bootloader itself. Don't take my word for it but I suspect that one could still run older versions on the new bootloader.

    To test this, just download the factory zip and update the bootloader only.
    You are correct.

    I did:

    Code:
    adb reboot bootloader
    fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img
    fastboot reboot

    And I'm booted into Android 12 still just fine. Below is the command prompt output:
    S:\platform-tools>adb reboot bootloader
    * daemon not running; starting now at tcp:5037
    * daemon started successfully

    S:\platform-tools>fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img
    Sending 'bootloader_b' (11554 KB) OKAY [ 0.047s]
    Writing 'bootloader_b' (bootloader) Flashing pack version slider-1.2-8739948
    (bootloader) flashing platform gs101
    (bootloader) Validating partition ufs
    (bootloader) Validating partition ufs
    (bootloader) Validating partition partition:0
    (bootloader) Validating partition partition:1
    (bootloader) Validating partition partition:2
    (bootloader) Validating partition partition:3
    (bootloader) Validating partition bl1_b
    (bootloader) Validating partition pbl_b
    (bootloader) Validating partition bl2_b
    (bootloader) Validating partition abl_b
    (bootloader) Validating partition bl31_b
    (bootloader) Validating partition tzsw_b
    (bootloader) Validating partition gsa_b
    (bootloader) Validating partition ldfw_b
    (bootloader) Flashing partition ufs
    (bootloader) Flashing partition ufs
    (bootloader) Flashing partition partition:0
    (bootloader) Flashing partition partition:1
    (bootloader) Flashing partition partition:2
    (bootloader) Flashing partition partition:3
    (bootloader) Flashing partition bl1_b
    (bootloader) Flashing partition pbl_b
    (bootloader) Flashing partition bl2_b
    (bootloader) Flashing partition abl_b
    (bootloader) Flashing partition bl31_b
    (bootloader) Flashing partition tzsw_b
    (bootloader) Flashing partition gsa_b
    (bootloader) Flashing partition ldfw_b
    (bootloader) Loading sideload ufsfwupdate
    OKAY [ 2.766s]
    Finished. Total time: 2.825s

    S:\platform-tools>fastboot reboot
    Rebooting OKAY [ 0.001s]
    Finished. Total time: 0.002s

    S:\platform-tools>

    Note to anyone, if after upgrading to 13 you want to downgrade to 12 using a full factory image's flash-all.bat, you'll at minimum have to either remove Android 12's bootloader flash line from the file, or replace it with fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img (and have the right bootloader file in the same folder). Either should work fine.
    6
    For those of you that updated to A13 - Has Google removed the ability in A13 to sideload non GP apps?
    No, but they've restricted a few permissions for sideloaded apps (e.g. Notification Listener and Accessibility permissions). But those restrictions can be disabled by going to the app info page and clicking on the 3 dot menu on top right.
    5
    Android 13 looks to be OUT!

    13.0.0 (TP1A.220624.021, Aug 2022)FlashLinkd8ddfdca3af0b97b3b99460afdab3cf95a741f988dccd5122564c855a64baa36
    5
    The real trick will be if you can still flash the old factory image. Try to re-flash the July image (just the system image) and see if the bootloader rejects it.
    There's no way I'll test that. Downgrading without wiping (because of updated app data, especially for system apps) is too much risk for me. I don't have the time to recover from. 😁

    Anyone else?
    5
    There's no way I'll test that. Downgrading without wiping (because of updated app data, especially for system apps) is to much risk for me. I don't have the time to recover from. 😁

    Anyone else?
    Leaving the past in the rear view mirror, sir... 😜
  • 8
    I think this just means you won't be able to downgrade the bootloader itself. Don't take my word for it but I suspect that one could still run older versions on the new bootloader.

    To test this, just download the factory zip and update the bootloader only.
    You are correct.

    I did:

    Code:
    adb reboot bootloader
    fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img
    fastboot reboot

    And I'm booted into Android 12 still just fine. Below is the command prompt output:
    S:\platform-tools>adb reboot bootloader
    * daemon not running; starting now at tcp:5037
    * daemon started successfully

    S:\platform-tools>fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img
    Sending 'bootloader_b' (11554 KB) OKAY [ 0.047s]
    Writing 'bootloader_b' (bootloader) Flashing pack version slider-1.2-8739948
    (bootloader) flashing platform gs101
    (bootloader) Validating partition ufs
    (bootloader) Validating partition ufs
    (bootloader) Validating partition partition:0
    (bootloader) Validating partition partition:1
    (bootloader) Validating partition partition:2
    (bootloader) Validating partition partition:3
    (bootloader) Validating partition bl1_b
    (bootloader) Validating partition pbl_b
    (bootloader) Validating partition bl2_b
    (bootloader) Validating partition abl_b
    (bootloader) Validating partition bl31_b
    (bootloader) Validating partition tzsw_b
    (bootloader) Validating partition gsa_b
    (bootloader) Validating partition ldfw_b
    (bootloader) Flashing partition ufs
    (bootloader) Flashing partition ufs
    (bootloader) Flashing partition partition:0
    (bootloader) Flashing partition partition:1
    (bootloader) Flashing partition partition:2
    (bootloader) Flashing partition partition:3
    (bootloader) Flashing partition bl1_b
    (bootloader) Flashing partition pbl_b
    (bootloader) Flashing partition bl2_b
    (bootloader) Flashing partition abl_b
    (bootloader) Flashing partition bl31_b
    (bootloader) Flashing partition tzsw_b
    (bootloader) Flashing partition gsa_b
    (bootloader) Flashing partition ldfw_b
    (bootloader) Loading sideload ufsfwupdate
    OKAY [ 2.766s]
    Finished. Total time: 2.825s

    S:\platform-tools>fastboot reboot
    Rebooting OKAY [ 0.001s]
    Finished. Total time: 0.002s

    S:\platform-tools>

    Note to anyone, if after upgrading to 13 you want to downgrade to 12 using a full factory image's flash-all.bat, you'll at minimum have to either remove Android 12's bootloader flash line from the file, or replace it with fastboot flash bootloader bootloader-raven-slider-1.2-8739948.img (and have the right bootloader file in the same folder). Either should work fine.
    6
    For those of you that updated to A13 - Has Google removed the ability in A13 to sideload non GP apps?
    No, but they've restricted a few permissions for sideloaded apps (e.g. Notification Listener and Accessibility permissions). But those restrictions can be disabled by going to the app info page and clicking on the 3 dot menu on top right.
    6
    Woah! Not August but two new July images here. (not saying that @spotmark isn't getting the August OTA)

    12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)FlashLink5651ee94a61222e2c03ca55b76f4aa452c5eed9e43ad8aabb7060739177e1689
    12.1.0 (SQ3A.220705.004.A1, Jul 2022, Softbank)FlashLink6b60f5a6401b35c635408494b54323825a8bcf5c85384a7cc2c241849a2d7413
    5
    Magisk Stable v25.2 is out.
    Direct link to downlod: https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk


    v25.2​

    • [MagiskInit] Fix a potential issue when stub cpio is used
    • [MagiskInit] Fix reboot to recovery when stub cpio is used
    • [MagiskInit] Fix sepolicy.rules symlink for rootfs devices
    • [General] Better data encryption detection
    • [General] Move the whole logging infrastructure into Rust
    5
    Android 13 looks to be OUT!

    13.0.0 (TP1A.220624.021, Aug 2022)FlashLinkd8ddfdca3af0b97b3b99460afdab3cf95a741f988dccd5122564c855a64baa36
  • 57
    Android 13 looks to be OUT!

    13.0.0 (TP1A.220624.021, Aug 2022)FlashLinkd8ddfdca3af0b97b3b99460afdab3cf95a741f988dccd5122564c855a64baa36

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