Related
Question related to "After updating, you will not be able to downgrade..." message
Hope you guys are safe and well.
Currently my A50 on August update. I have no problems with this update but I like to update to Android 10 for additional features. I'm reluctant to update because of this message. I'm afraid that if I had problems or something wrong with the new update, I won't be able to go downgrade to August update.
So, Is it really impossible to downgrade using Odin with an official firmware?
I'm coming from iOS and hence the fear of updating. As you may know, iOS downgrade is impossible when Apple sign-out the old software.
Thanks in advance.
Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.
pripyaat said:
Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.
Click to expand...
Click to collapse
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.
Screen not responding after update
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!
sheidyly said:
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!
Click to expand...
Click to collapse
Try to flash the ROM manually using ODIN
redymedan said:
Try to flash the ROM manually using ODIN
Click to expand...
Click to collapse
I'm sorry but I'm new to all of this and I seem to read some comments saying the phone was bricked after flashing.
And if I will try flashing, do I use the old firmware or the new one?
Thank you so much!
mistpsn said:
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.
Click to expand...
Click to collapse
I think... and I could be completely wrong, but it keeps track of the highest version of bootloader you installed. So it will not allow you to boot if you flash the older one. However, I am not sure how it behaves if the bootloader is unlocked.
If anyone have the same concerns I had. I found out that only security updates seems to have this message and risk bricking your phone in case you downgrade to lower version. Some people confirms that they were able to downgrade without any problems from android 10 to android 9 on their A50.
It also made sense that there are no problems since the warning message only included with security updates. The android 10 Update change list have no warnings related to downgrading to older versions.
March security update had the warning message. And I had to do the security upgrade before the android 10 update was available OTA.
Hi. I got a Redmi Note 8 Pro Global version and I updated it to Android 10 manually. Problem is I am getting random freezes everyday. I would like to go back to Android 9 because these freezing is very annoying and ruining my experience. I am not sure if this is related to MIUI or Android 10 itself. I've done factory reset and reset via recovery mode as well. Still the same. Are any instructions to go back to Android 9?
I've read in some forums that Android 10 has some issues even in pixel devices where if an app freezes, it brings down the whole OS. Mine freeze about 10 seconds, sometimes more. It's happening very randomly in different apps so it is very difficult to replicate.
joenefloresca said:
Hi. I got a Redmi Note 8 Pro Global version and I updated it to Android 10 manually. Problem is I am getting random freezes everyday. I would like to go back to Android 9 because these freezing is very annoying and ruining my experience. I am not sure if this is related to MIUI or Android 10 itself. I've done factory reset and reset via recovery mode as well. Still the same. Are any instructions to go back to Android 9?
I've read in some forums that Android 10 has some issues even in pixel devices where if an app freezes, it brings down the whole OS. Mine freeze about 10 seconds, sometimes more. It's happening very randomly in different apps so it is very difficult to replicate.
Click to expand...
Click to collapse
use indian version android 10 which is on miui v11.0.2.0.
It works fluently without any problem but keep in mind that preloader and other safety file is for Android 9. If you use them before flashing anything in android 10. Then it might brick your device. Even magisk brick some person device in android 10. So be safe before doing modification in it. Until preloader and lk will be available for it.
Hi. Thanks for the suggestion but what if I want to go back to Android 9 Global version? Just want to back to previous version when I got it out of the box. I don't want to flash or use other region roms. Just want to go back to Android 9. Is there any available steps or instructions out there? Can't seem to find one.
1hekill0r said:
use indian version android 10 which is on miui v11.0.2.0.
It works fluently without any problem but keep in mind that preloader and other safety file is for Android 9. If you use them before flashing anything in android 10. Then it might brick your device. Even magisk brick some person device in android 10. So be safe before doing modification in it. Until preloader and lk will be available for it.
Click to expand...
Click to collapse
joenefloresca said:
Hi. Thanks for the suggestion but what if I want to go back to Android 9 Global version? Just want to back to previous version when I got it out of the box. I don't want to flash or use other region roms. Just want to go back to Android 9. Is there any available steps or instructions out there? Can't seem to find one.
Click to expand...
Click to collapse
You can easily go back to android 9 global version by flashing fastboot rom via fastboot. You can flash fastboot rom just via mi flash tool by flashing lk and preloader before flashing rom or you can easily flash every image one by one manually in fastboot mode, Just by using command like fastboot flash system system.img, fastboot flash cust cust.img and so on. It is very easy. Hope it work for you.
Thanks for this. I've been following instructions from this link https://c.mi.com/ph/miuidownload/detail?guide=2. I think you are also referring to this one. I already followed instructions but I am now stuck in the unlocking method which says I need to wait 168 hours.
You mentioned I can flash img files one by one, is still possible when without unlocking the the device first via miui unlock tool?
1hekill0r said:
You can easily go back to android 9 global version by flashing fastboot rom via fastboot. You can flash fastboot rom just via mi flash tool by flashing lk and preloader before flashing rom or you can easily flash every image one by one manually in fastboot mode, Just by using command like fastboot flash system system.img, fastboot flash cust cust.img and so on. It is very easy. Hope it work for you.
Click to expand...
Click to collapse
joenefloresca said:
Thanks for this. I've been following instructions from this link https://c.mi.com/ph/miuidownload/detail?guide=2. I think you are also referring to this one. I already followed instructions but I am now stuck in the unlocking method which says I need to wait 168 hours.
You mentioned I can flash img files one by one, is still possible when without unlocking the the device first via miui unlock tool?
Click to expand...
Click to collapse
Nope you have to first unlock bootloader. But as I read sp flash tool can work without unlocking bootloader. So if you have fastboot than first flash preloader and lk and then you can use sp flash tool without authorised account. But I am not sure if it work then inform me also. And if it don't work you have to first unlock bootloader.
The experience posted by this user only reinforces my general impression not to do a major upgrade (even an "official" one pushed by the manufacturer) on any phone that one uses for primary use, unless you want to get involved in the whole rooting process and all the time and risk that entails.
In my experience, the original version of android that ships with a device, and subsequent minor fixes, are the most adapted to the phones specs. Despite claims otherwise, every major upgrade involves more resource use, since it was designed with the latest hardware in mind. It will therefore almost certainly degrade the performance of a phone, even one not that old. I have had this happen in every phone I have owned. And unless your phone is rooted, you can not downgrade the OS.
So when MIUI 12 comes out, with Android 10, I will definitely wait for others to do it first and wait for the feedback, maybe I'll just pass on it. Right now my RN8P works great, and the additional "features" of android 10 add no functionality whatsoever. Why screw around with something that already works great?
---------- Post added at 11:25 AM ---------- Previous post was at 11:20 AM ----------
BTW the above is true on Apple devices, too, in my experience.
Hi, I have MIUI 11/ Android 10 11.0.1 (Indonesia ROM) installed on my device and I have rooted it successfully with Magisk without TWRP.
Let me Tell you some Main Points about this device after my months of experience and Lot of Research about this device.
- Latest official TWRP version doesn't work on this device, and device goes into bootloop. Doesn't matter whatever you do, You have to flash ROM again to prevent bootloop.
- After Flashing ROM or Magisk, You must need to disable AVB, to prevent bootloop, you can find the command on TWRP web.
- MediaTek Processor on this device isn't a mess now, as Kernel source code has already released by Xiaomi.
And there are number of developments have been done already to prevent device from brick.
- Cameras on this Device are Great from Hardware side, but Unfortunately MIUI stock cam is garbage, and can't produce Nice quality Pictures.
- I have personally bricked this device many times, and fortunately always found a solution to get out of the mess.
Anybody reading this post, has any type of question, can ask And I will try my best to Help him/her
Overall, This Device is a great Powerhouse and
I request Developers to Kindly plz continue Development regarding Camera and I hope Xiaomi.eu will support this device for their ROM's in near future
Regards,
Moaz-Qudeer
I want to update to A10 but i am afraid i will lose factory preloader.... any ideas? i mean the anti brick preloader
Saadbinaamer said:
I want to update to A10 but i am afraid i will lose factory preloader.... any ideas? i mean the anti brick preloader
Click to expand...
Click to collapse
No, You can update software without worries it would b better if you're updating through OTA, otherwise .zip method is also safe, just make sure that you have removed root access from your device (if rooted) before updating.
Moazqudeer said:
No, You can update software without worries it would b better if you're updating through OTA, otherwise .zip method is also safe, just make sure that you have removed root access from your device (if rooted) before updating.
Click to expand...
Click to collapse
This contradicts some reports on the Megathread. I strongly recommend against OTA and zip sideloading/recovery install, unless you're ok with losing anti-brick preloader.
u8ububu said:
This contradicts some reports on the Megathread. I strongly recommend against OTA and zip sideloading/recovery install, unless you're ok with losing anti-brick preloader.
Click to expand...
Click to collapse
Read my 1st post again, I already said developments have been done in this regard already and there are much less brick risks now, I updated my device Android 9>>10 with recovery .zip method by placing .zip file into "downloaded_rom" folder. And Let me mention that my device had Bootloader unlocked before updating you can check attached screenshot.
Moazqudeer said:
Read my 1st post again, I already said developments have been done in this regard already and there are much less brick risks now, I updated my device Android 9>>10 with recovery .zip method by placing .zip file into "downloaded_rom" folder. And Let me mention that my device had Bootloader unlocked before updating you can check attached screenshot.
Click to expand...
Click to collapse
Yes, you can update Android 9 -> Android 10. The question is: Do you still have the factory preloader? Because that's what @Saadbinaamer was asking about. Otherwise, yeah, sure, you can update any way you want to Android 10.
u8ububu said:
Yes, you can update Android 9 -> Android 10. The question is: Do you still have the factory preloader? Because that's what @Saadbinaamer was asking about. Otherwise, yeah, sure, you can update any way you want to Android 10.
Click to expand...
Click to collapse
Yes, you should have Factory Preloader after Updating, Just make sure your device is not rooted before update.
Moazqudeer said:
Yes, you should have Factory Preloader after Updating, Just make sure your device is not rooted before update.
Click to expand...
Click to collapse
Kindly confirm at your end
Saadbinaamer said:
Kindly confirm at your end
Click to expand...
Click to collapse
Yes, confirmed from my side, I have factory preloader installed after update
Moazqudeer said:
Yes, confirmed from my side, I have factory preloader installed after update
Click to expand...
Click to collapse
Okay so I updated to MIUI 12; Android 10 (China Beta Rom). Though I have TWRP and Magisk installed but I don't have factory pre-loader anymore. I watched a YouTube video in which the uploader said that the new factory pre-loader will be available soon for the said Android version and the former one can't be used.
soleali said:
Okay so I updated to MIUI 12; Android 10 (China Beta Rom). Though I have TWRP and Magisk installed but I don't have factory pre-loader anymore. I watched a YouTube video in which the uploader said that the new factory pre-loader will be available soon for the said Android version and the former one can't be used.
Click to expand...
Click to collapse
I don't know about MIUI 12, as I said already, I have MIUI 11, Android 10 Installed.
My Phone is HARDBRICK and haven't installed preloader lk
How you Unbrick your device without preloader instal before..? In Android 9...
there should be clear tutorials and in execution order because often not very clear and people will not understand everything
Hey, guys! This is my first time posting, so I apologize if my post is missing some key details or isn't of quality in some other way.
I am currently looking into installing LineageOS onto my Samsung Galaxy A7 (SM-A720S); on the LineageOS installation documentation, it said to make sure that my device was running Android Oreo (Android 8.0). Since my device had Android Pie (Android 9.0) installed, I downloaded the Android 8.0 stock ROM for my device and region from SamMobile, and I also downloaded Odin v3.14.1 (un-patched as I am using a ROM for the same region) from the XDA forums.
Furthermore, I turned on developer settings on my phone and enabled OEM unlocking and USB debugging. Attempting to flash Android 8.0 onto my device resulted in the following error message:
SW Rev. Check Fail (Bootloader) Device: 5 Binary: 3
Click to expand...
Click to collapse
From poking around in the forums, I learnt that this means there is a mismatch between the bootloader version and the binary I am trying to flash. Is there any way to either downgrade the bootloader in order to be able to flash Android 8.0 or is there some way to trick the device/odin into thinking that the Android 8.0 has a binary of 5?
I really want to try LineageOS. so I would appreciate any advice on how to work around this issue.
That was a slight oversight on my end, because there aren't many A720S users. Your pie bootloader is fine, you can flash lineage.
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.