Related
Im sorry...this is probably a dumb question, but can't confirm one way or another, even when searching...
I was under the assumption when I signed up for 8.1 beta, that when the official release rolled out it's automatically install and I'd be back to the official version and then keep getting the monthly security updates.
I haven't gotten the January update and it still says I'm enrolled on the website. I understand if unenroll before the official release, my phone will be wiped... Does this still apply, assuming I'm on the final release?
Screenshot attached of info. Thank you for any help!
InfiniteReality said:
Im sorry...this is probably a dumb question, but can't confirm one way or another, even when searching...
I was under the assumption when I signed up for 8.1 beta, that when the official release rolled out it's automatically install and I'd be back to the official version and then keep getting the monthly security updates.
I haven't gotten the January update and it still says I'm enrolled on the website. I understand if unenroll before the official release, my phone will be wiped... Does this still apply, assuming I'm on the final release?
Screenshot attached of info. Thank you for any help!
Click to expand...
Click to collapse
If you unenroll before the official release, the yes, your phone would have been wiped. However, you should be ok now. This is from reading things in the P2XL forums, not personal experience.
Badger50 said:
If you unenroll before the official release, the yes, your phone would have been wiped. However, you should be ok now. This is from reading things in the P2XL forums, not personal experience.
Click to expand...
Click to collapse
Thanks for the reply! That's my assumption as well, I just can't 100% confirm it. It wouldn't be the worse thing if it wiped it, but would rather not have to copy 100gb worth of stuff just in case.....and would rather not have to set it up again.
Anyone 100% know?
Took the gamble anyways, so wanted to update in case anyone else happened to be searching for the same answer.
It does NOT wipe your phone, just have to make sure you are indeed are on the official release and all should be good.
I updated my Google Edition Pixel 3XL to 10 two nights ago. Now today, I received a notification that an update failed to install.
I am thrown off because I turned off updates, but regardless of that, if I just updated to 10 two nights ago, what is with this update wanting to install in my device?
I am on vzw OG unlimited data plan, the build # of my currently installed Android version 10 is: QP1A.190711.020.C3. Anyone can enlighten me on this?
Thanks in advance
You're on andriod 10. But you're on the sept, 2019 update. So your phone is probably trying to update to a more current version.
statustray said:
I updated my Google Edition Pixel 3XL to 10 two nights ago. Now today, I received a notification that an update failed to install.
I am thrown off because I turned off updates, but regardless of that, if I just updated to 10 two nights ago, what is with this update wanting to install in my device?
I am on vzw OG unlimited data plan, the build # of my currently installed Android version 10 is: QP1A.190711.020.C3. Anyone can enlighten me on this?
Thanks in advance
Click to expand...
Click to collapse
If your bootloader is unlockable, look at this Guide:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Prerequisites: Factory Images
Then do #4 'keep data' to install the latest Factory image. Do #9 to root.
Thanks for the replies. I appreciate it
I have since updated my device again. I used the "OTA" method to do the update. All-in-all it took about 15 minutes or so. Now the security patch level is: October 5, 2019. I suspect that it will tell me sooner or later that there is an even newer update. Hmmm...
I'm still waiting in the even newer updates to come down to my device. I do like the fact though that I can install an ota with magisk and don't have to connect to a computer.
I just wish I could speed up the updates using that method too. I was thinking that it would install the latest/greatest the first time out of the gate. Lol
I'm still waiting in the even newer updates to come down to my device. I do like the fact though that I can install an ota with magisk and don't have to connect to a computer.
I just wish I could speed up the updates using that method too. I was thinking that it would install the latest/greatest the first time out of the gate. Lol
Update: I managed to figure out that the Beta 08 predated the latest stable release 10.0.13, which I also found by searching. Since 10.0.13 is newer than Beta 08, I'm good.
This 7T is making me feel like I haven't spent the last six years reading XDA threads.
So I bought a 1907 converted to global firmware with the bootloader unlocked from Swappa. Now that it's here I find it has the open beta on it (OP7T_02_BETA_08) which I would prefer to roll back to stable. Something tells me there is not yet a roll back zip for this beta but a preliminary search didn't help. So if you know of a zip, tia.
Android 10 introduced a lot of powerful new tools to the Oneplus space and the only one I am familiar with is the fastboot roms (thanks! They're a lifesaver). I have not used the MSM tool, etc. I have never rolled back an OP beta. I can't even find a page about the OP 7T betas, although I assume the seller has the latest one on this phone. I'm ok using one of these tools if I do it now, since I have not yet put any personal data on the device.
As I see it these are my options from most desirable down:
1) Roll back to 10.0.12 or 10.0.13 assuming there is a roll back zip and I have instructions on how to use it.
2) Use a tool that is new to me to roll back.
3) Live with beta and simply root it via the fastboot flash method.
As for rooting the beta, can I use any of the prepatched boot img's here, which was my intention when I thought I was getting global stable? Or is the easiest thing to do just to boot the unofficial twrp and flash the latest Magisk zip (20.4?)? I think that's probably easiest.
So assuming a roll back to stable isn't possible now, and I root the beta by whatever means, how do I get back to stable eventually? I know this has been answered very often but I have never wanted to deal with betas over 3 different OP phones so if you'd indulge me with basic explanations/links I'd appreciate it. Thanks.
Download the OnePlus 7T - Global
Flash from your phone in the system settings then reboot, it will wipe everything after it boots back up go thru the setup quickly and do a factory reset one more time from the settings and your set. After that just download Oxygen Updater and catch up to the current update.
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.O.10_OTA_010_all_2002022101_downgrade_0ab28576e1914b50.zip
Having issues installing beta 3.3 on my 6 pro.. did a factory reset then tried installing it. First time it took forever to install and phone rebooted and had missing operating system so I had to factory reset.. second time I got a failed to install message.. rebooted the phone and it said no operating system please visit this link from another device.. rebooted then phone worked normal.. what is going on here ? Phone is purchased from att, so idk if it's considered global version but whatever either way . Is there something stopping it from being installed? Was trying to do all this OTA.. thanks kinda new to it
I'm not sure if it being an att version has anything to do with it or not.. maybe the version google releases is only working on unlocked global models?? Someone shine some light on this..
You can use https://flash.android.com/ to flash with a computer.
So why would the flash tool work but not the ota method ?? Really curious cause when the official comes out hopefully I can flash that ota without any issues.. right now I opted out of the beta cause I really want the ota method to work and it doesn't ..
Can someone tell me why the ota wouldn't install ? Installed it the way I installed any other update on the phone through check for updates.. Id rather get ota working vs hassling with a computer to install it. That can mess things up if done wrong .
Is it failing to ota install the beta cause of a locked bootloader ? It does fine with install ota security patches on Android 12. Trying to install 13 ota on the phone itself fails.. I don't see why that would be though ?
@Redbeardkevv Welcome to XDA. Instead of posting multiple times in a row, please use the Edit button to edit your post and just add to it, in the future.
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)
^ That Google site has saved many users on XDA. It has revived or corrected a mistake on their devices (mine too, once) when even flashing the full factory image didn't fix the problem. I have no idea what exactly it does that manually flashing doesn't. I normally use the full factory image zip, and that alone sometimes fixes issues that users have when they have issues flashing via the OTA method.
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Redbeardkevv said:
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Important excerpt:
Android Flash Tool guides you step-by-step through the process of flashing your device—there's no need to have tools installed—but you will need to unlock your device and enable USB Debugging in Developer options.
Click to expand...
Click to collapse
If I remember correctly from other AT&T variant Pixel 6 Pro users in this section, once you pay off the phone and/or own the phone for long enough, AT&T should carrier unlock the phone, and that will likely make it so that you can OEM Unlocking and unlock the bootloader. (this also applies to T-Mobile, but does not apply to Verizon)
Well it's a far ways from being paid off I'll just add that .. what are my flashing options ? Also why would a security patch install just fine, then I enroll into beta ,try to install it, and bam it won't install and is corrupt install. Just doesn't seem right to me.. should I just wait until official release early August and then the OTA install from phone will work ?
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Redbeardkevv said:
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Click to expand...
Click to collapse
Firstly, unlocked bootloader is required to flash custom or beta firmware. While you can sideload OTA packages on a locked bootloader, I would highly recommend against doing so as you may end up with no way to recover your device.
When installing a beta, it is generally best to wipe and perform a clean flash. OTA is not recommended because beta software by nature is not yet suitable for public release, and may not appropriately handle everything correctly coming from older firmware.
As has been mentioned before, I recommend you use the Android Flash Tool to flash the beta. To ensure you have a fresh start, tick the Wipe device and Force flash all partitions boxes. Do not re-lock the bootloader.
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Redbeardkevv said:
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Click to expand...
Click to collapse
Most likely. I doubt the beta will pass signature verification until it is updated to public release.
So not passing signature verification would be the reason it won't install ( ota ) most likely ? I'm just confused why a patch will install ota but the beta cannot .. must have something to do with bootloader being locked and it not being an official verified release or something
Just curious
Redbeardkevv said:
Just curious
Click to expand...
Click to collapse
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
NippleSauce said:
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
Click to expand...
Click to collapse
Well that explains it not installing and saying corrupted install ... Lol
Redbeardkevv said:
Well that explains it not installing and saying corrupted install ... Lol
Click to expand...
Click to collapse
It's a beta, so there will be issues for sure (but your last comment said you are getting an error [device is corrupt] that was common a few months ago so read on). You don't need to have an unlocked bootloader to enroll in the beta. Tons of users on Verizon and AT&T with a locked BL have installed the beta. Most are fine, some have had issues.
I wouldn't install a Beta on a locked BL. Why risk it? If something goes wrong, you'll need to get a warranty replacement. Seems like such a hassle.
For your issue, since you said you're getting a device corrupt message. This message is caused by q few different things (there's a thread on here about it). To fix it, users needed to do a factory reset in recovery mode. If you really wanted to try installing the beta (and you understand the risks), you'd probably need to: go to recovery mode and perform a wipe/factory reset.
From there, you could install the latest stable ota (via recovery mode) then see if the beta will update for you (via beta enrollment like you are trying to do), or directly flash the beta ota (link below). I'm just not sure if you can flash a beta ota image, over a stable build. I haven't tried it but according to xda, you can be on Android 12, and flash the Beta 13 ota (instructions found here).
There's two ways to flash an Android image: ota builds via recovery mode (doesn't require BL unlock) and factory image via fastboot which can be done manually or using Google's web flash tool (flash.android.com) - both if these require BL unlock.
You can find all the latest image downloads here. Google strongly recommends to flash the beta with an unlocked bootloader using their flash web tool. It's a beta so I would stay away until you can unlock your bootloader. Don't risk it. But I still think it might be a good idea for you to eventually perform a factory reset from recovery mode, since you are seeing the device is corrupt error message.
Had same problem, tried installing it twice and gave up
Hi there,
Just like the title says.
Xprivacylua won't' work on Android 13 for me. what I was wondering is whether I can downgrade without flashing the bootloader.
I am going to follow the following guide but am afraid to get a bricked phone
How to Bypass Anti Rollback Mechanism in Pixel 6A/6/6 Pro
This guide will show you how to bypass Anti Rollback Mechanism while doing a downgrade from Android 13 to Android 12 on Pixel 6A/6/6 Pro.
www.droidwin.com
Thank you all
------------------------add---
finally managed to downgrade to Android 12, just add --force before update:
fastboot --force update image-oriole-sq3a.220705.001.b2.zip (m phone is pixel6)
then reboot, then choose factory reset.
credits @Bunnehbunn
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
smokejumper76 said:
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
Click to expand...
Click to collapse
You've made my day
I am going to wait and see for several days before proceeding as I just know how to flash-all, I have never flashed step by step or flashed to the specific slots.
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
roirraW edor ehT said:
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine.
Click to expand...
Click to collapse
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
roirraW edor ehT said:
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
Click to expand...
Click to collapse
Is downgrading on both slots a must? I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
bush911 said:
Is downgrading on both slots a must?
Click to expand...
Click to collapse
If you want to run Android 12 instead of 13, and you've already flashed 13 to both slots, or at least 13's bootloader to both slots (which you should definitely do if you haven't), then yes, you should downgrade both slots and wipe to start fresh.
You can't expect both Android 12 and Android 13 to operate with the same app data, so having a different version of Android on the other slot isn't going to do you any favors.
bush911 said:
I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
Click to expand...
Click to collapse
Try a factory reset?
Lughnasadh said:
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
Click to expand...
Click to collapse
Here my friend. Also in the OP.
Partial quote:
I tried this as soon as I upgraded to 13 and yes you can downgrade down to Android 12 after upgrading with no noticable issues. The radio and every other image but the bootloader can be downgraded. But I only tried 003, 004 July images for oriole so I don't know about anything lower personally.
Click to expand...
Click to collapse
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Lughnasadh said:
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Click to expand...
Click to collapse
You can join the ranks of such like my boss at work (where we use Google officially for everything including company mail). They chat me to ask me for a link to a particular file that's in Google Drive, or to find a particular email for them.
Just kidding about joining the ranks! You're welcome!
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Lughnasadh said:
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Click to expand...
Click to collapse
Absolutely, I agree on both parts.
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
enderdzz said:
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
Click to expand...
Click to collapse
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April. Also I'm surprised you weren't bricked after booting Android 13 because it does increment the anti-rollback counter.
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
drivers/soc/google/boot_control/boot_control_sysfs.c - kernel/gs - Git at Google
I'm guessing your bootloader version is old enough to not have the bits implemented so it just doesn't care, but that's weird because the July Android 12 bootloaders do have the bits and will not load if the counter is incremented by Android 13.
I wouldn't recommend continuing to run like this and would update to the August Android 13 bootloader because there's no telling what might be happening wrong under the hood. Example is that the August Android 13 bootloader it is able to boot Android 12 but because of interface differences it is a broken experience.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
So yeah if you're correct then it's possible you did get away with it as your firmware is too old to have implemented it. However this is not a supported firmware-software configuration.
Thank you for your reply!
Namelesswonder said:
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April.
Click to expand...
Click to collapse
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
Namelesswonder said:
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
Click to expand...
Click to collapse
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
enderdzz said:
Thank you for your reply!
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
Click to expand...
Click to collapse
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Namelesswonder said:
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much! I'm much more clear now.
enderdzz said:
Thank you very much! I'm much more clear now.
Click to expand...
Click to collapse
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Namelesswonder said:
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Click to expand...
Click to collapse
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
enderdzz said:
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
Click to expand...
Click to collapse
If WebView applications didn't crash within minutes of launching them then that means the DRM library should either be working or just not segfaulting like it does with Android 12 on 13 bootloader.
The fingerprint scanner HAL not working is completely understandable, part of the bootloader flash also carries the fingerprint scanner's firmware, and we know that one of the big things with Android 13 is that the fingerprint scanner is somewhat more reliable, so it definitely has changed between Android 12 to 13.
Interesting stuff, will be cool to see where it can go, but man is it sketchy to recommend people still on Android 12 to downgrade to April and then try flashing the Android 13 system images, real possibility of making bricks.