How To Guide May 2022 firmware is out - Unlocking the Pixel 6 Pro bootloader & central repository of relevant links

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
Magisk Canary 23018 is out at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.

Unhide the Magisk app before updating.

New magisk update 😊
screenshot_20220123-174919_mana-png.5516527
 
Last edited:

Ghisy

Senior Member
Mar 27, 2010
1,681
480
Last edited:
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Do you usually re-patch the boot.img with the newest Magisk before upgrading Magisk itself? I know I don't but I wonder if I should. Although, I guess "direct install" in Magisk does that?
My steps for updating are:
  1. Unhide Magisk.
  2. Update from within the app.
  3. Then yes, I use Direct Install.
  4. Reboot and re-hide the app. :)
 

roirraW "edor" ehT

Forum Moderator
Staff member
Modified the OP to indicate the official repair site is still being reported as not having been updated for the P6/P, and also to give a link to the official boot to safe mode instructions. Most other sites including major carriers only tell how to boot from safe mode from a working Android UI using the power menu - which is of no help for a boot-looping device.

I just used safe mode for the first time that I remember to solve a Magisk Module problem of mine - but I might've done so on my Pixel 1 before and it's just been too long ago. It's definitely the first time I did so on the P6P.

Please, anyone, let us know somewhere when/if the repair site has been updated for use with the P6P if you notice it first.

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.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Magisk Canary 23019 is out at Magisk Downloads on GitHub, or direct download link https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk.

Unhide the Magisk app before updating.

My steps for updating are:
  1. Unhide Magisk. Edit: I've heard it reported that this wasn't necessary for them. It's possible it was only a problem on Canary 23015, or it was fixed on one of the later Canarys (Canaries?). I still intend on doing it this way, though - it really doesn't hurt me.
  2. Update from within the app.
  3. Then yes, I use Direct Install.
  4. Reboot and re-hide the app. :)
Also, with these more frequent releases, I often wait to see if new version-releasing doesn't settle down (also to see if anyone else reports trouble because I don't have as much time to allow my phone not to work the way I want, as I used to have time for). So I had never updated to Canary 23018, and here's 23019 already, and I reset my waiting time. No particular waiting time - just whatever feels right.

This is sorta a manual updating procedure to promote the Canary release to an imaginary release channel between Canary and Beta. LOL!


Screenshot_20220125-082350_Twitter.png
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
So uh quick question...

I have a Google-unlocked P6 Pro. Not tied to any carrier, I bought it purely unlocked from Google.

If I pop in a Verizon SIM will it disable OEM unlocking?
What @Nergal di Cuthah said. :) No. Personally, I would always unlock the bootloader first thing before I got through the process very far, though, since unlocking the bootloader factory resets the phone.
 

roirraW "edor" ehT

Forum Moderator
Staff member
To note, i did root before i inserted the sim, so that might be a factor idk
It really shouldn't, I believe you were 110% correct in your post. :) If it did gray out the OEM unlocking while using the factory unlocked Pixel 6 Pro and having a Verizon SIM in, I would consider it a very rare fluke that's probably easily rectified, or even self-rectified in a short time, but I've never heard of this happening. I am old, though, so every new thing I learn, something old has to fall out to make room.
 

TheForceUnleashed

Senior Member
Feb 11, 2012
472
296
27
Louisiana
Xiaomi Mi 11 Ultra
To note, i did root before i inserted the sim, so that might be a factor idk
You are probably right. The unlocked devices I’ve used all were under a different server (Google’s own server I believe) for firmware updates + OEM unlocking so I doubt a Verizon SIM would change that.

I haven’t had a Pixel since the Pixel 2 so I was getting extra clarification that everything was the same.
 

Nergal di Cuthah

Senior Member
Sep 20, 2013
1,762
844
Google Pixel 6 Pro
You are probably right. The unlocked devices I’ve used all were under a different server (Google’s own server I believe) for firmware updates + OEM unlocking so I doubt a Verizon SIM would change that.

I haven’t had a Pixel since the Pixel 2 so I was getting extra clarification that everything was the same.
No problem, i came from a 2xl that was still on Android 8 because i was afraid of losing root and not having a software based helper (can't remember the name of it). So i came to p6p with worries over root
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
You are probably right. The unlocked devices I’ve used all were under a different server (Google’s own server I believe) for firmware updates + OEM unlocking so I doubt a Verizon SIM would change that.

I haven’t had a Pixel since the Pixel 2 so I was getting extra clarification that everything was the same.
I'm under the impression that all updates still come from Google directly even on a Verizon variant - it's the IMEI of the device which changes the behavior, how soon you get the update, et cetera, according to the carrier's wishes, but I don't think changes where the update comes from.
 

TheForceUnleashed

Senior Member
Feb 11, 2012
472
296
27
Louisiana
Xiaomi Mi 11 Ultra
I'm under the impression that all updates still come from Google directly even on a Verizon variant - it's the IMEI of the device which changes the behavior, how soon you get the update, et cetera, according to the carrier's wishes, but I don't think changes where the update comes from.
That does make sense.

It can honestly get confusing. Especially since direct from Verizon variants AND Verizon variants you set up from Google themselves are permanently bootloader locked. It makes you think anything that touches Verizon can get fused shut, lol.

I had to do extra due diligence to make sure I got the right variant. This year it seems pretty easy to get the wrong one and from what I read it appears a lot of people have
 

roirraW "edor" ehT

Forum Moderator
Staff member
Magisk Beta (non-Canary) v24 is out at Magisk Downloads on GitHub, or at the Releases page there, or direct download link https://github.com/topjohnwu/Magisk/releases/download/v24.0/Magisk-v24.0.apk.

Unhide the Magisk app before updating.

My steps for updating are:
  1. Unhide Magisk. Edit: I've heard it reported that this wasn't necessary for them. It's possible it was only a problem on Canary 23015, or it was fixed on one of the later Releases. I still intend on doing it this way, though - it really doesn't hurt me.
  2. Update from within the app.
  3. Then yes, I use Direct Install.
  4. Reboot and re-hide the app. :)
Official Installation Guide:
John Wu
@topjohnwu
Oh and BTW, I have revised the installation guide with additional info and updated instructions.

Magisk v24.0 Release Info

topjohnwu released this 2 hours ago
· 3 commits to master since this release
v24.0
b34c477
It has been a while since the last public release, long time no see! A personal update for those unaware: I am now working at Google on the Android Platform Security team. Without further ado, let's jump right into it!

MagiskHide Removal​

I have lost interest in fighting this battle for quite a while; plus, the existing MagiskHide implementation is flawed in so many ways. Decoupling Magisk from root hiding is, in my opinion, beneficial to the community. Ever since my announcement on Twitter months ago, highly effective "root hiding" modules (much MUCH better than MagiskHide) has been flourishing, which again shows that people are way more capable than I am on this subject. So why not give those determined their time to shine, and let me focus on improving Magisk instead of drowning in the everlasting cat-and-mouse game 😉.

Sunsetting Magisk-Modules-Repo​

Due to lack of time and maintenance, the centralized Magisk-Modules-Repo was frozen, and the functionality to download modules from the repo is removed in v24.0. As a supplement, module developers can now specify an updateJson URL in their modules. The Magisk app will use that to check, download, and install module updates.

Introducing Zygisk​

Zygisk is Magisk in Zygote, the next big thing for Magisk! When this feature is enabled, a part of Magisk will run in the Zygote daemon process, allowing module developers to run code directly in every Android apps' processes. If you've heard of Riru, then Zygisk is inspired by that project and is functionally similar, though the implementation is quite different internally. I cannot wait to see what module developers can achieve using Zygisk!

Documentation​

For developers, details about updateJson and building Zygisk modules can all be found in the updated documentation.

Magisk Changelog

v24.0​

  • [General] MagiskHide is removed from Magisk
  • [General] Support Android 12
  • [General] Support devices that do not support 32-bit and only runs 64-bit code
  • [General] Update BusyBox to 1.34.1
  • [Zygisk] Introduce new feature: Zygisk
  • [Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes
  • [MagiskBoot] Support patching 32-bit kernel zImages
  • [MagiskBoot] Support boot image header v4
  • [MagiskBoot] Support patching out skip_initramfs from dtb bootargs
  • [MagiskBoot] Add new env variable PATCHVBMETAFLAG to configure whether vbmeta flags should be patched
  • [MagiskInit] Support loading fstab from /system/etc (required for Pixel 6)
  • [MagiskInit] Support /proc/bootconfig for loading boot configurations
  • [MagiskInit] Better support for some Meizu devices
  • [MagiskInit] Better support for some OnePlus/Oppo/Realme devices
  • [MagiskInit] Support init.real on some Sony devices
  • [MagiskInit] Skip loading Magisk when detecting DSU
  • [MagiskPolicy] Load *_compat_cil_file from system_ext
  • [MagiskSU] Use isolated devpts if the kernel supports it
  • [MagiskSU] Fix root shell if isolated mount namespace is set
  • [resetprop] Deleted properties are now wiped from memory instead of just unlinking
  • [App] Build a single APK for all ABIs
  • [App] Switch to use standard bottom navigation bar
  • [App] Downloading modules from the centralized Magisk-Modules-Repo is removed
  • [App] Support user configuration of boot image vbmeta patching
  • [App] Restore the ability to install Magisk on the other slot on some A/B devices
  • [App] Allow modules to specify an update URL for in-app update + install


 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
This is interesting. I'm not on Magisk v24 Beta yet. Does anyone else have any observations about this?

Forgive me if i miss it, does fpr on this kernel disabled during aod? It works fine once the screen is on. But not at all while on aod.

Update: turns out its the new magisk 24. Back to canary build now.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    New modem again for the Pixel 6 series with QPR3 Beta 3. I'll be checking signal, 5G combos, and carrier settings later today.

    Beta 3: g5123b-100840

    Beta 2: g5123b-100383

    May stable: g5123b-97927 (also 12L Beta, 13 DP2, March, April, etc)
    4
    No new modem. Maybe the QPR beta later in the week will have some goodies.
    4
    NOTE! I had the wrong firmware pasted in my previous post (for the 5A instead of 6 Pro). Corrected now.

    Edit: I would expect someone to hopefully have noticed if they used the link in what I pasted since the filename would start with barbet instead of raven but still sorry about that. Mea culpa!
    4
    May’s Pixel 6 and 6 Pro update primarily improves haptic feedback
    Like last month, the May security update is rolling out for the Pixel 6 series on the same day as all other supported Google devices.



    Compared to previous months, there are just three fixes. Exclusive to the Pixel 6 is haptic feedback “improvements” after complaints that emerged with Android 12L. Some found that vibrations were reduced so much that they missed calls, notifications, and other alerts, while tweaking settings did nothing to increase intensity. We noted at the time:

    The issue seems to be hit or miss, with some users affected, but not others. Some also claim vibrations just feel different in terms of patterns, with a softer start but the same high-end
    Sensors

    • Improvements for haptic feedback under certain conditions and use cases *[2].
    Meanwhile, all current devices — Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a (5G), Pixel 6 & Pixel 6 Pro — benefit from:

    Display / Graphics

    • Fix for issue occasionally causing display to wake without user interaction *[1].
    User Interface

    • Fix for issue causing launcher crash after restarting device in certain conditions *[1].
    Those particular issues were not too common in the grand scheme. Android 12 QPR3 next month, which has been in beta since early March, should fix more way bugs, which was the case for 12L.

    The Pixel 6 series and older phones are on the same Android 12.1 build for this May update: SP2A.220505.002.
    3
    I wouldn't mind if the bootloader checked for official device specific builds and warned for anything else.

    Google makes a way too easy to put the phone in a bad state. And that's before we even get into beta enrolling a locked phone.
  • 53
    May firmware is out Pixel 6 Pro Factory Images.
    12.1.0 (SP2A.220505.002, May 2022)FlashLinke12665088bb6f6aa4d1064e95daf6f2f47fcf4f1ca4e7e93dcb772651cefb3a1


    Kush Mittal
    Community Manager•Original Poster

    Google Pixel Update - May 2022​

    Announcement
    Hello Pixel Community,

    We have provided the monthly software update for May 2022. All supported Pixel devices running Android 12 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 3a (XL): SP2A.220505.002
    • Pixel 4 (XL): SP2A.220505.002
    • Pixel 4a: SP2A.220505.002
    • Pixel 4a (5G): SP2A.220505.002
    • Pixel 5: SP2A.220505.002
    • Pixel 5a (5G): SP2A.220505.002
    • Pixel 6: SP2A.220505.002
    • Pixel 6 Pro: SP2A.220505.002

    What’s included

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

    Display / Graphics
    • Fix for issue occasionally causing display to wake without user interaction *[1].
    Sensors
    • Improvements for haptic feedback under certain conditions and use cases *[2].
    User Interface
    • Fix for issue causing launcher crash after restarting device in certain conditions *[1].
    ---------------------------------------------------------------

    Device Applicability
    *[1] Included on Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a (5G), Pixel 6 & Pixel 6 Pro
    *[2] Included on Pixel 6 & Pixel 6 Pro

    Details
    Other


    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.


    Likewise, when wanting to root you have to disable verity and verification, after which you'll need to wipe the phone, so best just to go ahead and disable these immediately after unlocking the bootloader. See the section below "A list of the other important guides".


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

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

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


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

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


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

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

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

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


      The unlock process works like this:

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

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

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

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

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

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

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

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

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

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

    Rooting-related


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

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


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

    Custom kernels for stock ROM(s)

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

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

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

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

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

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

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

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

    33.0.1 (March 2022)​

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

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

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

    Canary 23014

    EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4 👍
    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).