General February 1, 2023 - QPR2 Beta 3 (T2B3.230109.002) - Pixel 6 Pro [Raven] - [thread also for future Major Android Betas]

Search This thread

phoenixpb

Senior Member
Dec 18, 2010
104
23
Yes it fixed a bug with the application i use at work.
I have a Pixel 6
Very old bug (was present already in Android 12)

Could not login with finger print in app

Fixed only with QPR1

👍
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Forum Moderator
Staff member
Hi, what the best way without creating damage to go back from android 13 QPR1 beta version to stable andriod 13?
Depends on your definition of "Damage", and also depends on how you achieved beta-testing Android 13 QPR1 Beta 1. If you opted into the Beta program and received the automatic OTA, then you'll have to visit the site again, opt out of the Beta program, but be aware that this will factory reset your device.

If you opted in but you manually flash (without wiping) the Stable Android 13, 1) There may be issues as a full wipe is always recommended when downgrading. QPR1 Beta 1 -> Stable is a downgrade, so if you don't wipe, you can expect some things to not work correctly. 2) You would receive the OTA to the Beta again at some point.

If you manually flashed QPR1 Beta 1 without opting into the Beta program, then just manually flash the stable Android 13 from:


Pixel 6 Pro latest image:
13.0.0 (TP1A.220905.004, Sep 2022)FlashLink4dba4ced0ea829e3d334dee55d8b15daa4cd1b57848417a8787d68a0b6ce3793

Again, if you don't wipe (by removing the "-w" from the Flash-All.bat), then don't be surprised if it doesn't work correctly. It's even possible the phone won't boot correctly.

You can also always use 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).

Check the box for Wipe, you could go ahead and check the box for Force Flash All Partitions if you feel like it (will wipe, too), and uncheck the option to relock the bootloader when done. The Official Google Android Flash Tool is the easiest way to flash. I prefer the factory image because I like to get my hands a little dirtier.

If you don't wipe when re-flashing Stable, and the phone doesn't work correctly, it won't be damaged - just factory reset the phone (or re-flash while allowing it to wipe), and it'll be good.
 

nibera

Senior Member
Apr 19, 2008
237
29
Depends on your definition of "Damage", and also depends on how you achieved beta-testing Android 13 QPR1 Beta 1. If you opted into the Beta program and received the automatic OTA, then you'll have to visit the site again, opt out of the Beta program, but be aware that this will factory reset your device.

If you opted in but you manually flash (without wiping) the Stable Android 13, 1) There may be issues as a full wipe is always recommended when downgrading. QPR1 Beta 1 -> Stable is a downgrade, so if you don't wipe, you can expect some things to not work correctly. 2) You would receive the OTA to the Beta again at some point.

If you manually flashed QPR1 Beta 1 without opting into the Beta program, then just manually flash the stable Android 13 from:


Pixel 6 Pro latest image:
13.0.0 (TP1A.220905.004, Sep 2022)FlashLink4dba4ced0ea829e3d334dee55d8b15daa4cd1b57848417a8787d68a0b6ce3793

Again, if you don't wipe (by removing the "-w" from the Flash-All.bat), then don't be surprised if it doesn't work correctly. It's even possible the phone won't boot correctly.

You can also always use 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).

Check the box for Wipe, you could go ahead and check the box for Force Flash All Partitions if you feel like it (will wipe, too), and uncheck the option to relock the bootloader when done. The Official Google Android Flash Tool is the easiest way to flash. I prefer the factory image because I like to get my hands a little dirtier.

If you don't wipe when re-flashing Stable, and the phone doesn't work correctly, it won't be damaged - just factory reset the phone (or re-flash while allowing it to wipe), and it'll be good.
Hi, thanks for your complete reply, I received the QPR beta because I am registered in the beta program, I know that returning to the Android 13 building I have to delete all the data and start again.
I think the best solution would be to use the Android Tools to return stable Android 13 stock and then unsubscribe from the beta program. This way I avoid having problems.
 
  • Like
Reactions: roirraW "edor" ehT

NippleSauce

Senior Member
Jun 23, 2013
508
343
Thus far with my use, this beta seems pretty similar to the stable, September update release. The only thing that I have noticed is that AdAway no longer works, haha. Anyone else experience the same issue?

I'm guessing that a full wipe, re-flash & reinstallation would resolve the problem.
 
  • Wow
Reactions: roirraW "edor" ehT

Lughnasadh

Senior Member
Mar 23, 2015
4,679
5,291
Google Nexus 5
Huawei Nexus 6P
Thus far with my use, this beta seems pretty similar to the stable, September update release. The only thing that I have noticed is that AdAway no longer works, haha. Anyone else experience the same issue?

I'm guessing that a full wipe, re-flash & reinstallation would resolve the problem.
Adaway working fine for me on QPR1 Beta 1. Do you still have Systemless Hosts enabled in Magisk?
 
  • Like
Reactions: roirraW "edor" ehT

Teet1

Senior Member
Sep 17, 2013
475
353
ZTE Axon 7
Samsung Galaxy S9
Just did a full device wipe. Re-flashed the same beta build, rooted again and set it all up from scratch. AdAway still doesn't work. It looks like that latest device policy changes the location of the hosts file that's utilized...

Very strange indeed.
Can confirm this, not just adaway but Energized Protection doesnt work either after that device policy update. Very strange
 

Lughnasadh

Senior Member
Mar 23, 2015
4,679
5,291
Google Nexus 5
Huawei Nexus 6P
Can confirm this, not just adaway but Energized Protection doesnt work either after that device policy update. Very strange
Just did a full device wipe. Re-flashed the same beta build, rooted again and set it all up from scratch. AdAway still doesn't work. It looks like that latest device policy changes the location of the hosts file that's utilized...

Very strange indeed.
What version of Device Policy do you guys have?
 
  • Like
Reactions: roirraW "edor" ehT

NippleSauce

Senior Member
Jun 23, 2013
508
343
Can confirm this, not just adaway but Energized Protection doesnt work either after that device policy update. Very strange
Yeah. It also seems that web-embedded livestreams don't work in Chrome either. So, if you prefer the web interface or if there is no app for the site you stream from, then you can't watch the streams anymore =/

Edit - This also could have been done by the device health services, as that has also received an update ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

Edit 2.0 - Yes, we're also both using AdAway w/ root =)
 
Last edited:
  • Wow
Reactions: roirraW "edor" ehT

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Pixel 6 Proraven-t2b2.221216.006-factory-8e0c382f.zip8e0c382f9e55c898c045eb2426798b4a8f4ecd1cd8477212a919278697642aaa

    Pixel 6 Proraven-ota-t2b2.221216.006-e69abcb0.zipe69abcb00f54b2426fdee0850c944ad9fe8c8a0338b3accff389162f33eb43d3

    ARM64+GMSgsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip12a8e1935c6ef46d2d44dea6ea331fa238cb6240bd6df607f6ccb849d619b25c
    ARM64aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zipe508d63f27da01889734d36171dec11f226e2f2bc538526379e2184d51e9ffd3
    x86_64+GMSgsi_gms_x86_64-exp-T2B2.221216.006-9443277-5255002f.zip5255002f0d1249bb08725c06e3a264d8caaf2d84cdb9c40c7a7a8954249d6493
    x86_64aosp_x86_64-exp-T2B2.221216.006-9443277-02d675fb.zip02d675fb15c962fa7e35f494edfbfa2da7b886ef3f6e4709b73b1c57fb96b8ab

    Release notes​

    bookmark
    Beta 2Beta 1
    Release dateJanuary 9, 2023
    BuildT2B2.221216.006
    Security patch levelJanuary 2023
    Google Play services22.41.13

    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 2​

    You can install Android 13 QPR2 Beta 2 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 resolved issues​

    The following issues have been resolved in Android 13 QPR2 Beta 2:
    • Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
    • Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.

    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 it to crash from a null pointer exception.

    Previous beta releases​

    Android 13 QPR1 Beta 1​

    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 1/8x and 1/4x while in Slow Motion mode.
    3
    Does root works fine on new beta?
    You have to use the Pixel 7 Pro boot image to patch, like it was with QPR2 Beta 1.
    3
    Wonder if we can just use the p6p boot this time
    Seen a couple users report that using the Pixel 6 Pro boot image to root is now working again on QPR2 Beta 3, for whatever that's worth.
    2
    Anyone faced the problem of disconnected calls after 20.02 mins?
    My calls get disconnected always after this time period.
    Nope. Calls have been pretty great. Maybe whoever you're talking to can't stand talking to you more than that 😂
    2
    Seen a couple users report that using the Pixel 6 Pro boot image to root is now working again on QPR2 Beta 3, for whatever that's worth.
    I can confirm this on a Pixel 6 (non-Pro), it does indeed work as intended again.
  • 11
    February 1, 2023:
    QPR2 Beta 3
    Pixel 6 Proraven-t2b3.230109.002-factory-a8b7d332.zipa8b7d33243440ed011cd037f5ef25fe5b38678c699b33edd8832cc777808e73e

    64-bit-only images​

    Pixel 6 Proraven_64-t2b3.230109.002-factory-64adaa76.zip64adaa76f18899034aa3066d82c3f30a5b6a80de0816a0a50bf6e6e7be971529

    https://developer.android.com/about/versions/13/release-notes#beta3

    Release notes​

    bookmark
    Beta 3Beta 2.1Beta 2Beta 1
    Release dateFebruary 1, 2023
    BuildT2B3.230109.002
    Security patch levelJanuary 2023
    Google Play services23.03.13

    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 3​

    You can install Android 13 QPR2 Beta 3 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 resolved issues​

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

    Developer-reported and user-reported issues​

    • Fixed an issue where notifications in a notification group were sometimes displayed with straight corners instead of rounded corners. (Issue #264287776, Issue #265529116)
    • Fixed an issue where the message in the notification shade that indicates an active VPN connection overlapped with the message about apps with active foreground services. (Issue #266075977)
    • Fixed an issue where the overflow menu couldn't be accessed when editing Quick Settings tiles. (Issue #263484657)
    • Fixed an issue that sometimes caused a device with vibration enabled to vibrate for too long after it received a notification. (Issue #239676913)

    Other resolved issues​

    • Fixed an issue that sometimes caused messaging apps to crash or fail to send notifications.
    • Fixed a GPU issue that prevented apps from using certain visual effects.
    • Fixed an issue where Quick Settings tiles for a work profile were not added after setting up a new device.
    • Fixed an issue that sometimes caused the Pixel launcher to crash when using the Search bar in the app drawer.
    • Fixed an issue that sometimes prevented a device from being unlocked using a pattern after the Google Assistant was activated.
    • Fixed an issue in the com.android.qns system process that sometimes caused crashes.
    • Fixed an issue with the Pixel launcher that prevented Chinese text input from being recognized when typing in the Search bar in the app drawer.
    • Fixed an issue where when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashed with a "Settings keeps stopping" message and then the system Settings app couldn't be opened.
    • Fixed an issue with the System UI that sometimes caused it to crash from a null pointer exception.
    • Fixed an issue where the connection status of a Bluetooth device sometimes did not match the actual device state.
    • Fixed an issue where the Pixel launcher crashed when a user tapped a web search suggestion for a query term.
    • Fixed an issue that caused status bar icons to overlap with the date text when font and display settings were set to their maximum level on a device.

    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.

    Previous beta releases​

    Android 13 QPR1 Beta 2​

    Android 13 QPR2 Beta 2.1 (January 2023)
    This minor update to Android 13 QPR2 Beta 2 includes the following fixes:
    • Fixed an issue that sometimes prevented devices from automatically connecting to a 5G network even when it was available. (Issue #265093352)
    • Fixed an issue where devices did not drop or reset an existing, encrypted Bluetooth connection after receiving a command to disable link-layer encryption for that connection.

    Top resolved issues​

    The following issues have been resolved in Android 13 QPR2 Beta 2:
    • Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
    • Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.

    Other known issues​

    Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 2. 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 it to crash from a null pointer exception.

    Android 13 QPR1 Beta 1​

    Other known issues​

    Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 1. 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 1/8x and 1/4x while in Slow Motion mode.
    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