General March 15, 2023 QPR3 Beta 1 T3B1.230224.005 - Pixel 6 Pro [Raven] - [thread also for future Android QPR Betas]

Search This thread

roirraW "edor" ehT

Forum Moderator
Staff member
Pixel 6 Proraven-ota-t1b3.221003.008-2f799487.zip2f7994875425cbe924afae7da68ae876b7ce0545f831f052f3a27635a8f3f82e

Release notes​

Beta 3.1 Beta 3 Beta 2 Beta 1
Release dateNovember 7, 2022
BuildT1B3.221003.008
Security patch levelNovember 2022
Google Play services22.36.16
Android 13 QPR1 Beta 3.1 (November 2022)
This minor update to Android 13 QPR1 Beta 3 includes the following fixes:
  • Fixed a platform issue that caused apps to crash when they were using a MediaSession to handle input from hardware media playback buttons. (Issue #251798994, Issue #252665746, Issue #251381423, Issue #251513135, Issue #255500998)
  • Fixed issues where a device's GPU drivers sometimes caused the system UI to freeze during normal device use.
  • Fixed an issue where Pixel phones sometimes displayed an incorrect "Missed call" notification instead of "Call answered on another device" when the call was answered remotely by Pixel Watch (in untethered mode).
  • Fixed an issue that sometimes caused the Google Camera app to crash.
  • Fixed an issue that prevented Google Assistant from being activated by hotword on some devices.
  • Fixed an issue that prevented motion-based gestures, such as "Lift to check phone" or "Flip to Shhh", from working on some devices.
  • Fixed an issue that sometimes caused artifacts to display when recording or viewing video on some devices.
  • Fixed an issue that sometimes caused the Google Camera app to launch slowly.
  • Fixed an issue for Pixel 6a devices that sometimes caused the CarrierSettings to crash when inserting a SIM card.
  • Fixed that issue that prevented the "Go to browser" option in the notification shade from working while using an instant app.

About Android 13 QPR1​

Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR1 builds on the updates in the Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.

How to get QPR1 Beta 3.1​

You can install Android 13 QPR1 Beta 3.1 on any of the following Google Pixel devices:
  • Pixel 4a and 4a (5G)
  • Pixel 5 and 5a
  • Pixel 6 and 6 Pro
  • Pixel 6a
  • Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.

General advisories​

Be aware of these general advisories about the release:
  • This release might have various stability, battery, or performance issues.
  • For users with accessibility needs, this release might not be appropriate for daily use.
  • Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
  • Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.

Get support​

Two primary support channels are available to you when developing and testing with Android 13 QPR1. The channel you should use to get support depends on where you are encountering your issue.
  • Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
    Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue.
    See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
  • Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.

Top resolved issues​

The following issues have been resolved in Android 13 QPR1 Beta 3:

Developer-reported and user-reported issues​

  • Fixed an issue for some devices where the screen unlock UI was displayed over notifications and other lock-screen content. (Issue #254163754)

Other resolved issues​

  • Fixed an issue that prevented the "Flip camera for selfie" gesture from working on some devices.
  • Fixed an issue that sometimes caused the screen to go blank while attempting to unlock a device.
  • Fixed an issue that sometimes prevented a device from being unlocked using either Face Unlock or Fingerprint Unlock when the device had been idle for multiple hours.
  • Fixed an issue that sometimes caused fullscreen video playback to flicker after enabling always-on-display features and locking the screen.

Top open issues​

See top open issues for the latest list of top open issues that have been reported.

Other known issues​

Based on our testing, you might encounter the following issues when using Android 13 QPR1. These issues are already known, so there’s no need to file additional reports for similar issues.

Android Platform​

  • (Fixed in Beta 3.1) In some cases, issues with a device's GPU drivers cause the system UI to freeze during normal device use. To work around this issue, try restarting the device.

Pixel​

  • (Fixed in Beta 3.1) In some cases, Pixel phones display an incorrect "Missed call" notification instead of "Call answered on another device" when the call is answered remotely by Pixel Watch (in untethered mode).

Previous beta releases​

Android 13 QPR1 Beta 1​

Top resolved issues​

The following issues have been resolved in Android 13 QPR1 Beta 1:

Developer-reported issues​

  • Fixed an issue for some devices that mistakenly caused a user's emergency contact to be dialed from the lock screen when the device was in their pocket. (Issue #233159557)

Other resolved issues​

  • Fixed various issues for Pixel 6a devices that made it difficult for users to unlock their device or to set up Fingerprint Unlock.
  • Fixed an issue that caused the system UI to crash in certain cases, such as gesturing from the edge of the screen to go back.
  • Fixed an issue that sometimes caused the 5G icon to be displayed instead of the 5G UW icon, even when the affected device was already successfully connected to a 5G UW network.
 
Last edited:

scott.hart.bti

Inactive Recognized Developer
Mar 19, 2012
2,560
17,384
Reading
Awesome. Switched to qpr1 beta 3 a few days after it came out and was a little buggier than I expected it would be... Mainly camera/media related... Looks like a lot of these fixes listed in the minor update should address them.
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Pixel 6 Proraven-t2b1.221118.006-factory-58c7ef5d.zip58c7ef5d1046627cfedf6fe53e7dca554001893d4c5f27a685a50e77c635a8ec

64-bit-only image:
Pixel 6 Proraven_64-t2b1.221118.006-factory-1a296844.zip1a2968448da3484cdde71faa66bd71ba2fdd051cc88e02cbae548c32e8d658e7

Release notes​

bookmark
Beta 1
Release dateDecember 12, 2022
BuildT2B1.221118.006
Security patch levelDecember 2022
Google Play services22.39.10

About Android 13 QPR2​

Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.

How to get QPR2 Beta 1​

You can install Android 13 QPR2 Beta 1 on any of the following Google Pixel devices:
  • Pixel 4a and 4a (5G)
  • Pixel 5 and 5a
  • Pixel 6 and 6 Pro
  • Pixel 6a
  • Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.

General advisories​

Be aware of these general advisories about the release:
  • This release might have various stability, battery, or performance issues.
  • For users with accessibility needs, this release might not be appropriate for daily use.
  • Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
  • Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.

Get support​

Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
  • Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
    Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
    See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
  • Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.

Top open issues​

See top open issues for the latest list of top open issues that have been reported.

Other known issues​

Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.

Android Platform​

  • The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
  • In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
  • An issue with the System UI can sometimes cause the Home screen to become unresponsive.

Google Apps​

  • After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between the 1/8x and 1/4x while in Slow Motion mode.
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
4,945
5,703
Google Nexus 5
Huawei Nexus 6P
  • Like
Reactions: Radon7 and moffa~

kylothow

Senior Member
Jan 3, 2014
1,014
1,729
Brescia
Has anyone here tested the 64-bit-only builds? Do they receive OTAs as well or each and every update is manual? What happens at the end of the QPR beta period, does it switch to stable or is it stuck until a new beta is out? I've looked through the official info but this isn't specified.
If it doesn't get OTAs and/or has "blackout" periods where no updates are released it could be an issue even for me.
 
Last edited:

onesolo

Senior Member
Apr 18, 2006
2,567
222
Nexus 7 (2013)
Google Nexus 5
Has anyone here tested the 64-bit-only builds? Do they receive OTAs as well or each and every update is manual? What happens at the end of the QPR beta period, does it switch to stable or is it stuck until a new beta is out? I've looked through the official info but this isn't specified.
If it doesn't get OTAs and/or has "blackout" periods where no updates are released it could be an issue even for me.
You get stuck until new beta. I was on the last beta, but not enrolled and two days ago I flashed the stable December factory image without -w and everything is working fine.
 
  • Like
Reactions: yyz71 and kylothow

kevp75

Recognized Contributor
Apparently patching the Pixel 7 Pro boot image and flashing that patched boot image on the Pixel 6 Pro works for root as a temporary workaround.

Didnt work for me.
 

stmm

Member
Nov 20, 2018
35
22
So after trying my best to figure out how to get root back on my phone after taking the QPR2 Beta 1 update, I finally figured it out!

Unfortunately, if you're taking the update as an OTA, you will lose your root. Even if you try to downgrade back to the previous OTA, you will still be unable to get root access. It's like it just completely breaks. I tried every single thing I could do without having to do a fresh wipe of the phone... but unfortunately, it just doesn't seem like it's possible.

So finally, I caved and decided to download the full Factory Zip file of the new QPR2 Beta 1 update. I flashed it and wiped everything as well (kept the -w in the flash-all.bat). Then I downloaded the lastest Magisk Canary (25205) and did what people were reporting to work, which was patch the boot.img from the Pixel 7 Pro, and flashed that through fastboot.

Finally, I have root again! Hope this helps anyone else out there figure it out. Feel free to message me if you have any questions!
 

stmm

Member
Nov 20, 2018
35
22
Can't you just download and install the ota, but DON'T press reboot, instead go into magisk and select the install option 'install to inactive slot (after ota) and then reboot?
Yep, that's exactly what I did. I always use that method when taking updates so that I can retain my root. But I lost my root regardless.
 

amritpal2489

Senior Member
Oct 3, 2010
353
63
Can somebody provide me Pixel 7 Pro's magisk patched boot img from the latest QPR2 Beta 1 update?
The one which succesfully roots the Pixel 6 Pro
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Thx, I'm on 25206 now add all is working
    3
    3
    Thank you, but that's not what I was asking. :) Google's instructions regarding the QPR2 Beta 3.2 / Stable March firmware / QPR3 Beta 1 situation instructed users to opt out of the QPR Beta, and then just don't accept/take the OTA that's offered (taking it would indeed wipe the phone before returning to Stable), until the OTA to the Stable March firmware is offered instead, then take that one - which won't result in a wipe.

    But I haven't found anywhere that explicitly says what happens when going from any QPR Beta to a whole new Android version (14) Beta. After all, Android 14 is "newer" than any current QPR Beta, but I wouldn't assume that means it won't wipe going from one Beta program to a different one.

    It might be fine, or it might not. I've been recommending caution.
    My guess is if you opt out of the A13 QPR Betas and opt in to the A14 DP/Betas it probably won't wipe you. It's usually only when you're downgrading that you'll get wiped.

    Of course, you probably weren't looking for guesses 🙃
    2
    What's the status of root in this build?
    Hopefully, someone will report back in this thread, but in my Pixel 7 Pro QPR thread, @kiekan rooted the QPR just fine. As far as I know, using the Stable Magisk v25.2 since they don't mention otherwise.
    Just flashed t3b1.230224.005 using the factory image. Successfully rooted and got AOSP mods working.

    Does anyone else notice that screen looks significantly darker when using the adaptive display color setting?
    2
    Looks like the problems with patching the boot image on the Pixel 6 series when on the QPR3 beta(s) (and other betas) and A14 DPs may have been fixed. Patching the Pixel 7 boot.img may no longer be needed when the next Canary is released.

  • 11

    Pixel 6 Pro [Raven] QPR Betas


    QPR stands for "Quarterly Platform Release". Android 13 QPR1 went final in December 2022. See main thread here for final/non-beta releases.

    You can officially opt into the Android Beta Program there, or use the factory image or OTA below.

    March 15, 2023:

    Other known issues​

    Based on our testing, you might encounter the following issues when using Android 13 QPR3. These issues are already known, so there's no need to file additional reports for similar issues.

    Android Platform​

    • If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
    • In some cases when a work profile is switched on or off, the device reboots instead.
    • The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.

    Pixel 6 Proraven-t3b1.230224.005-factory-f1dca87c.zipf1dca87c6b2b072a022800edfadad781c066543ffcdd891a2aff36c8cf4ccd1d

    64-bit-only images​

    Pixel 6 Proraven_64-t3b1.230224.005-factory-fc005de5.zipfc005de5f615dbe4fb9f0a176a6fbd19d182830061294a54ba69379566e99a27

    Pixel 6 Proraven-ota-t3b1.230224.005-21358b57.zip21358b571506d3a9e3af7e3c63ee9736265dd91b125dc656f4a3cc6869abdcb4

    Release notes​

    bookmark
    Beta 1
    Release dateMarch 15, 2023
    BuildT3B1.230224.005
    Security patch levelMarch 2023
    Google Play services23.08.15

    About Android 13 QPR3​

    Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
    Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
    Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
    Android 13 QPR3 builds on the updates in Android 13 QPR2 and the initial Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.

    How to get QPR3 Beta 1​

    You can install Android 13 QPR3 Beta 1 on any of the following Google Pixel devices:
    • Pixel 4a and 4a (5G)
    • Pixel 5 and 5a
    • Pixel 6 and 6 Pro
    • Pixel 6a
    • Pixel 7 and 7 Pro
    See Get Android 13 QPR beta builds for details on how to get started.

    General advisories​

    Be aware of these general advisories about the release:
    • This release might have various stability, battery, or performance issues.
    • For users with accessibility needs, this release might not be appropriate for daily use.
    • Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
    • Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.

    Get support​

    Two primary support channels are available to you when developing and testing with Android 13 QPR3. The channel you should use to get support depends on where you are encountering your issue.
    • Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
      Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
      See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
    • Support for issues with other apps: Contact the app developer directly.
    To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.

    Top resolved issues​

    The following issues have been resolved in Android 13 QPR3 Beta 1:
    • Fixed an issue where the clock text on the lockscreen was the wrong color.
    • Fixed an issue where Bluetooth audio wasn't working on some devices.
    • Fixed an issue where the fingerprint icon that is normally displayed on screen to indicate the position of the fingerprint sensor erroneously changed to an exclamation point (!).
    • Fixed an issue where live wallpapers could not be selected or used.
    • Fixed an issue where widgets, app icon positions, and other configurable options on the home screen were reset after installing an OTA update.
    • Fixed an issue that caused a device to be unenrolled from Face Unlock after installing an OTA update.

    Top open issues​

    See top open issues for the latest list of top open issues that have been reported.

    Other known issues​

    Based on our testing, you might encounter the following issues when using Android 13 QPR3. These issues are already known, so there's no need to file additional reports for similar issues.

    Android Platform​

    • If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
    • In some cases when a work profile is switched on or off, the device reboots instead.
    • The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.

    I don't plan on testing Betas of any sort, but feel free to use this thread for everything about the QPR Betas or major Android version betas for the Pixel 6 Pro. I'll update the information in the OP when necessary. See Post #1 in my main thread for general information (Unlocking Bootloader / Rooting / Updating | SafetyNet working again | ADB/Fastboot & Windows USB Drivers) but ask questions or make observations about all betas in this thread, please.

    Once a QPR or major Android version goes final, I'll take those discussions to my main thread.
    10
    Yet another Beta of 13, Beta 3.3:


    Pixel 6 Proraven-tpb3.220617.002-factory-1acb43a3.zip1acb43a3d082b8d2cd16cba834c1b1de25042c5d5122483bbf54ff4a16682186


    Android 13 Beta 3.3 (June 2022)
    Release date: June 27, 2022
    Build: TPB3.220617.002
    Emulator support: x86 (64-bit), ARM (v8-A)
    Security patch level: June 2022
    Google Play services: 22.21.16
    API diff:


    If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 3.3.

    This minor update to Android 13 Beta 3 includes stability and performance improvements as well as the following fixes:

    • Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
    • Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
    • Fixed an issue where devices couldn't connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
    • Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
    • Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
    • Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
    • Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.


    June 27, 2022 2:30pm Comment Skanda Hazarika

    Google rolls out Android 13 Beta 3.3 with a bunch of bug fixes​

    The beta branch of Android 13 just picked up a new bug-squashing update. Following in the footsteps of Android 13 Beta 3’s earlier incremental updates, this new release fixes a whole bunch of issues, including slow UI rendering, inability to connect to a Wi-Fi network, system UI crashes, and a few other problems.
    The build number of Android 13 Beta 3.3 is TPB3.220617.002. There is no change in the security patch level, though, hence it’s still June 2022 on this release. You can find the full list of published fixes in this update below:
    • Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
    • Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
    • Fixed an issue where devices couldn’t connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
    • Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
    • Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
    • Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
    • Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.
    Apart from the aforementioned bug fixes, the update also bumps the Google Play services version from 22.18.19 to 22.21.16.
    In case your Google Pixel device is already enrolled in the Android 13 beta program, you will automatically receive an over-the-air update to Beta 3.3. You can also download the full OTA or the factory image from the link below if you want to manually upgrade to the latest beta release.
    Download Android 13 Beta 3.3

    Source: Android Beta Program on Reddit
    8
    All, this is not a thread for opinions about the Pixel 6/Pro in general, nor is it a thread made for rants. Opinions specifically about Android 13 are fine. I know there have been a few posts that have nothing specific to do with Android 13 and I've let it go. If anyone wants to make posts that don't address anything specifically about Android 13, there are many, many threads in this section where that has taken place.

    I know, because I used to read every post in this section but now I avoid the threads that contain those kinds of posts, and I'd like to not see them here in this thread. Any further posts of those types will be deleted as off-topic.
    6
    I think Magisk removed the need to pass the vbmeta disable verity/verification flag with Canary 24303. Here's a quote related to a kernel issue from yujincheng08 (LoveSy):

    "Let me clarify the things.
    Magisk was used to modify the fstab to inject Magisk components, and in the meantime, Magisk stipped avb_key and avb flags for all partitions. So, that 24300 works is just a side effect and has no insurance.
    Now Magisk changed its way of injecting Magisk components, and it will no longer modify the fstab, and the side effect was thus gone together with the refactorization. Some configurations that rely on the fact that Magisk will strip those verification flags will no longer work, and that's expected. Users should disable the verification themselves since they are expected to have unlocked bootloaders."

    This all relates to problems with custom kernels and Magisk, but may have further implications for us. Check out more in the issue here..

    Good spot. Seeing as how that's now intended behaviour, I guess wiping and disabling verification is all our best moves from here.

    I'll take this moment to suggest investing in Swift Backup and setting up an automatic backup that runs periodically, so long as you have root it makes wiping pretty much a non-issue.
    6
    New Pixel 6 modem included!

    g5123b-102852-220609-b-8701566