The fix is to uninstall the Pixel Launcher update installed via APK Mirror. That build from APK mirror doesn't play nicely with the QPR1 Beta 1 build.
EDIT: Never mind, didn't see your edit
General March 15, 2023 QPR3 Beta 1 T3B1.230224.005 - Pixel 6 Pro [Raven] - [thread also for future Android QPR Betas]
- Thread starter roirraW "edor" ehT
- Start date
EDIT: Never mind, didn't see your edit
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
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
T-Mobile VoNR is also enabled once again in the carrier config for people that want to experiment with it.
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:
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
Pixel 6 Pro latest image:
| 13.0.0 (TP1A.220905.004, Sep 2022) | Flash | Link | 4dba4ced0ea829e3d334dee55d8b15daa4cd1b57848417a8787d68a0b6ce3793 |
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.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:
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
Pixel 6 Pro latest image:
13.0.0 (TP1A.220905.004, Sep 2022) Flash Link 4dba4ced0ea829e3d334dee55d8b15daa4cd1b57848417a8787d68a0b6ce3793
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.
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.
OPUS! Let's gooooooo. Goodbye Qualcomm, Sony, Fraunhofer, Samsung.
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.
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?
I do indeed. I'm not sure what changed. It was working fine for me at first, however, it decided to stop working two days ago after a device policy update was pushed through in the Play Store.
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.
caitsith810
Senior Member
Adding on to the list of that doesn't work(for me at least), Wavelet does not detect my earbuds at all. It detects my speakers but does not process it.
Did a clean flash and wipe twice, still does not work.
Did a clean flash and wipe twice, still does not work.
Can confirm this, not just adaway but Energized Protection doesnt work either after that device policy update. Very strange
What version of Device Policy do you guys have?
68.38.2 according to the app info
I have the same version and Adaway is working fine for me. Hmmm...
EDIT: I am using root mode, I should add, but it sounds like you are too since you have that Magisk mod installed.
Last edited:
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:
This?How to enable the "battery health" thing in QPR1 that is on twitter?
I assume it will come in the next Beta, or one of the next Betas.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
33
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.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.
Of course, you probably weren't looking for guesses
2
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.
2Looks 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.
Force ramdisk format to lz4_legacy for v4 by vvb2060 · Pull Request #6775 · topjohnwu/Magisk
Seems like Google doesn't want to fix this.
github.com
-
11Pixel 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:
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing...
developer.android.com
Pixel 6 Pro raven-t3b1.230224.005-factory-f1dca87c.zip f1dca87c6b2b072a022800edfadad781c066543ffcdd891a2aff36c8cf4ccd1d
64-bit-only images
Pixel 6 Pro raven_64-t3b1.230224.005-factory-fc005de5.zip fc005de5f615dbe4fb9f0a176a6fbd19d182830061294a54ba69379566e99a27
OTA images for Google Pixel | Android Developers
Instructions for downloading and installing...
developer.android.com
Pixel 6 Pro raven-ota-t3b1.230224.005-21358b57.zip 21358b571506d3a9e3af7e3c63ee9736265dd91b125dc656f4a3cc6869abdcb4
Release notes | Android Developers
Release notes and known issues for the latest...
developer.android.com
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.10Yet another Beta of 13, Beta 3.3:
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing...
developer.android.com
Release notes | Android Developers
Release notes and known issues for the latest...
developer.android.com
Google rolls out Android 13 Beta 3.3 with a bunch of bug fixes
Google is rolling out Android 13 Beta 3.3 to...www.xda-developers.com
8All, 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
Good spot. Seeing as how that's now intended behaviour, I guess wiping and disabling verification is all our best moves from here.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..
Some customized kernels are incompatible with Magisk 24303+ that no longer strips verification flags of early mount partitions · Issue #5777 · topjohnwu/Magisk
Device: Pixel 6 Pro Android version: 12.1...
github.com
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.
