How To Guide April 2, 2024 AP1A.240405.002 Global - Root Pixel 6 Pro [Raven]

Search This thread

roirraW "edor" ehT

Senior Moderator
Staff member
Thanks for providing. Came here from your Reddit posts. What's the best way to flash these, is there a guide? I'm on completely stock, no unlocked bootloader or anything.
Besides @Nergal di Cuthah's good advice, also just click the yellow "How to guide" quick filter at the top of the list of threads in this section. You'll see a few root how-to guides. Note that any time you unlock your bootloader (or relock the bootloader), it will factory reset your phone, so be prepared and have backups of what you need to keep including what's on your internal storage.

There's no way around that, ever.
 
  • Like
Reactions: Nemosfate

hpower1

Senior Member
Jan 24, 2012
218
113
Did anyone else have trouble opening today's magisk canary on the May A12 update? it opened fine before I updated to May (granted I installed it min before I started A12 update), but it only hit the load screen after. Stable and Beta work fine but whenever I download Canary same thing no pass of splash screen. I guess I could report this in Magisk board but wanted to see if anyone else loaded it and fail/succeeded in updating to the latest canary.
I had the same today. I just uninstalled and reinstalled 24306, tried again and all worked fine.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Senior Moderator
Staff member

1652623197316.png
 
  • Like
Reactions: Lughnasadh and jcp2

roirraW "edor" ehT

Senior Moderator
Staff member
Grrr...I had put the May updates' links here previously.

June 2022 update is here:
12.1.0 (SQ3A.220605.009.A1, Jun 2022, Verizon)FlashLink2b4b1d476a6e80fd9fe09ace45e8abbd654a4d4a6fc51d39f0fd76f5a2c6a024
12.1.0 (SQ3A.220605.009.B1, Jun 2022)FlashLink157e22840d4d4fde9f90d7de3d6ba6930922e9376096040d68501d155c997cb2


June 6, 2022 1:00pm Comment Adam Conway

June Feature Drop for Google Pixels includes At a Glance improvements, Pocket Operator, and more​

Every three months, Google rolls out new features to Pixel phones outside of the usual Android OS updates for years, and the company refers to them as “Feature Drops.” They’re usually released alongside a security patch, and the most recent one brought improvements to live caption, night mode in Snapchat, and a whole lot more. Now the June Feature Drop is now available (alongside June security patches), and it packs a ton of cool stuff you can try out on any Pixel smartphone release between the Pixel 4 and the latest Pixel 6 series.
In case you’re wondering, the June feature drop is based on the QPR3 builds that Google has been testing over the last few months. It’s currently unknown if Google will continue to beta test quarterly platform releases in the future.

Pocket Operator​

june feature drop teenage engineering pocket operator

Made in collaboration with teenage engineering, Pocket Operator is a new app that will let you shoot videos and “turn them into fun music and video cut-ups.” You can layer sounds, add visual effects, create patterns and beats, and mix it all together to make your own unique tracks. It’s available on the Google Play Store now, and you can check it out down below. It works on the Pixel 5 and newer, and currently, it’s only available in English.

The app was not found in the store.
Go to store Google websearch

Vaccination Cards​

COVID vaccination card google pay shortcut

Google has had the ability to add a vaccine card to your Google Pay for quite a while now, but now the company says you can add a shortcut to it to your home screen to quickly and easily get access to it at any time. It’s available in Australia, Canada, and the U.S.

More “At a Glance” alerts​

Video Player


00:00

00:33


The Pixel 6 series debuted a revamped “At a Glance” widget, which can display your calendar events, flight boarding pass, workout stats, and more on your home screen and lockscreen. Since its release, Google has added several new features to the widget to further expand its capabilities. Now the company is adding three new features to it.

Nest Doorbell video feed​

June feautre drop nest doorbell

Google added Nest Doorbell alerts back in January to the At a Glance widget, and they can tell you if “Someone’s at your door”. This can help you find out if a package has arrived, or if someone is just trying to get your attention out the front of your house. Now you can see an actual video feed from your doorbell too, right on your home screen.

Flashlight reminder​

Ever left your flashlight turned on on your phone? It’s pretty embarrassing, but I’m pretty sure that we’ve all been there. Now you’ll be able to see if it’s on straight from your home screen, without needing to turn your phone around to catch it.

Coming soon: Air Quality alerts​

If you live in the U.S., Australia, or India, soon you’ll get Air Quality alerts in your At a Glance widget for your current location.

Conversation Mode exits beta​

Sound Amplifier app Conversation mode

Google previously added “Conversation Mode” to the Sound Amplifier app in the December feature drop, and it’s been in beta since then. It uses on-device machine learning to block out surrounding noise. Conversation Mode is exclusively available to Pixel phone owners, and now it’s exiting beta. It’s designed for people with hearing loss to filter out sounds around them. It amplifies their voice, and you uses the camera to focus on whatever their phone should be properly listening to.

More features​

Real Tone Filters​

Google introduced Real Tone with the Pixel 6 series last year to help users accurately capture various skin tones. The Real Tone functionality used an updated face detection algorithm capable of recognizing more diverse faces in a wider array of lighting conditions, resulting in a better representation of different skin tones.
At I/O this year, Google expanded on the functionality and announced that it would implement Harvard professor Dr. Ellis Monk’s scale in Search and Photos to achieve similar results across all its products. These filters are now rolling out to users of Google Photos.

Car Crash Detection comes to Canada​

Google’s Car Crash Detection is rolling out in Canada now to Google Pixel 3 users and above, though excluding the Pixel 3a. It can, as the name suggests, detect if you’re in a car crash and act accordingly. It’s a safety feature that could potentially save lives.

More Chat translation languages​

Chat translation in messages will now be available in Traditional Chinese, Dutch, Korean, Thai, and Turkish for Pixel 6 and Pixel 6 Pro.

Download and install the June feature drop​

The June feature drop is now available for all eligible Pixel smartphones, and you can download it by checking for an update in your device’s settings.


Pixel Update Bulletin—May 2022​


Published May 2, 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-05-05 or later address all issues in this bulletin and all issues in the May 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-05-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 May 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-20120A-203213034*RCECriticalBootloader
CVE-2022-20117A-217475903*IDCriticalTitan-M
CVE-2021-4083A-216408350
Upstream kernel
EoPHighKernel
CVE-2022-20118A-205707793*EoPHighKernel
CVE-2022-20119A-213170715*IDHighDisplay/Graphics
CVE-2022-20121A-212573046*IDHighUSCCDMService

Qualcomm components​

CVEReferencesSeverityComponent
CVE-2021-35084A-204909067
QC-CR#3001178
ModerateWLAN
CVE-2021-35085A-204012850
QC-CR#3001331
ModerateWLAN
CVE-2021-35092A-204909309
QC-CR#2985885 [2]
ModerateModem
CVE-2021-35098A-190503256
QC-CR#2966419
ModerateAudio

Qualcomm closed-source components​

CVEReferencesSeverityComponent
CVE-2021-35079A-204908838*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-05-05 or later address all issues associated with the 2022-05-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.0May 2, 2022Bulletin Published
 
Last edited:

roirraW "edor" ehT

Senior Moderator
Staff member
My phone is from Google. My carrier is Verizon. Guess that I install the A1 version for the June update.

I wonder why last month there was one version for all carriers and this month there is a separate version for VZ.
More than likely there were more changes to the Verizon radio.img (modem) than they had time to integrate into the universal factory image's radio.img. I'm sure it'll go back down to one image per month in the near future.
 

LLStarks

Senior Member
Jun 1, 2012
2,264
1,690
There is a difference between subversions for the modem firmware for Verizon compared to the global. But the modem itself looks like it's the same major version as the latest betas.

It's never been clear what the subversion even means. I'm guessing it's just a carrier modem config update and not a core modem config update. I always thought subversion bumps were just timestamp bumps.

It's also not clear how to effectively diff the modems without actually testing them and checking logs. If there's anything beneficial in the Verizon firmware, I wouldn't be able to identify it.
 

hpower1

Senior Member
Jan 24, 2012
218
113
Sigh.... Still no face unlock it seems
i saw those rumor posts, and I didn't get excited, I thought no way. Maybe some day.

I can't remember what I did last time, as I have phone from google but running on VZW. I have been having a ton of network issues lately, so I'm gonna try the VZW variant first this time and see. I hope it helps.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I did go through and successfully flashed my PX6 pro to AP1A.240405.002 with KSU using PixelFlasher 6.8.3.0
    I gather you're all good now?
    In the future please create post PF issues in PF thread to keep this thread tidy and focused, and always provide a support file.
    2
    I did go through and successfully flashed my PX6 pro to AP1A.240405.002 with KSU using PixelFlasher 6.8.3.0
  • 66
    Pixel 6 Pro [Raven]

    April 2, 2024:





    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 👍