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 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.
I have a Moto G30 (bought in Australia) that I'd like to downgrade from Android 12 to Android 11. I've tried using the LMSA tool, but that just reflashes on Android 12. I'm following the tutorial here: https://www.droidwin.com/downgrade-motorola-moto-g30-from-android-12-to-android-11/
When I come to download the ROM, I'm not sure which one I want. From the list (https://mirrors.lolinet.com/firmware/motorola/caprip/official/RETAPAC/) I know it will be one with XT2129-2 as that's my phone model, and it will have 11 in it rather than 12 for the Android version. But that still leaves 4 choices:
XT2129-2_CAPRIP_RETAPAC_JPTW_11_RRCS31.Q1-3-68-1-3_subsidy-DEFAULT_regulatory-XT2129-2-APEM2_CFC.xml.zip
XT2129-2_CAPRIP_RETAPAC_SA_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM-SAR_CFC.xml.zip
XT2129-2_CAPRIP_RETAPAC_TH_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM_CFC.xml.zip
XT2129-2_CAPRIP_RETAPAC_TW_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM2_CFC.xml.zip
Any ideas which I should pick? Or what the difference is between these?
just different updates, all the ones before S0RC or so, should be 11, all the RRCS ones are android 11 for sure, I'd pick the latest one of those, which would have the latest security patches
also, even for normal updates, I've only used LMSA to download the latest image, and then manually flashed it, I'm pretty sure LMSA will only download the latest version anyway, so unless you figure out how to manually override it, it won't downgrade
Thanks. Have managed to get the phone up and running with XT2129-2_CAPRIP_RETAPAC_SA_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM-SAR_CFC.
The only issue I face now is that Google Pay no longer works.. Although my phone isn't rooted, the bootloader was unlocked during the process of going back to Android 11. Is there a way I can get Google Pay back whilst staying on Android 11?
Hello.
I have heared that once installed Android 13 blows a E Fuse on the device (Fairphone4) that prevents previous bootloaders and therefore previous Android versions
from booting. Does this also apply to the Fairphone 4, and under what circumstances does this E Fuse get triggered?
I need the ability to downgrade, and dont want to blow the E Fuse because then Im locked out from anything below Android 13 as it seems.
Regards
It is not a efus, it is just soemthing in a bootloader. Android 13 has rollback protection. Once you update the bootloader, you can not downgrade. In some limited situations you can run android 12 on an android 13 bootloader, but it’s risky and a bad experience. Only update if yoyou do not need to downgrade.
Arealhooman said:
It is not a efus, it is just soemthing in a bootloader. Android 13 has rollback protection. Once you update the bootloader, you can not downgrade. In some limited situations you can run android 12 on an android 13 bootloader, but it’s risky and a bad experience. Only update if yoyou do not need to downgrade.
Click to expand...
Click to collapse
Actually interesting would be if theres a way to boot Android 13 with the Android 12 bootloader.
Also it would be interesting if the Android 13 bootloader can be modified so it doesnt set the „E Fuse“ that prevents downgrading. Actually as far as I know the rollback protection is E Fuse based. Theres a memory made out of E Fuses in the SOC, and the Android 13 Bootloader will set there a information to lockout any previous bootloder from running.
Flashing a modified bootloader will hardbrick your device.
It would explain a few things as using A13 LineageOS I wanted to go back to A12 FPOS. I followed the updates and did the check and it kept returning 0. Using Calyx OS which is A13 and I can relock bootloader. Use A12 based OS and no go even if security updates match or higher.
I'm in a bit over my head, so apologies if some of this doesn't make sense.
I have a Galaxy S9 that I want to install Android 9 on. For context, I'm an app developer and I have a bug that's been reported to be only on Android 9 - and emulators aren't reproducing the issue.
Unfortunately, it has Android 10 already installed on it, and so far as I can tell, installing Android 9 requires rooting the device.
At first, I tried directly installing an Android 9 firmware onto the phone using Odin - this gives the error "sw rev. check fail(bootloader) device 17 binary 7".
I then installed TWRP - which worked, but now I don't know what I need to do to actually get Android 9 onto the device... any help would be appreciated!
wwnsw said:
I'm in a bit over my head, so apologies if some of this doesn't make sense.
I have a Galaxy S9 that I want to install Android 9 on. For context, I'm an app developer and I have a bug that's been reported to be only on Android 9 - and emulators aren't reproducing the issue.
Unfortunately, it has Android 10 already installed on it, and so far as I can tell, installing Android 9 requires rooting the device.
At first, I tried directly installing an Android 9 firmware onto the phone using Odin - this gives the error "sw rev. check fail(bootloader) device 17 binary 7".
I then installed TWRP - which worked, but now I don't know what I need to do to actually get Android 9 onto the device... any help would be appreciated!
Click to expand...
Click to collapse
Short of installing a custom ROM, I'm not sure what else you can do. I would suggest a GSI but they all seem to be Android 10 and up, unless you want to try something like this.
V0latyle said:
Short of installing a custom ROM, I'm not sure what else you can do. I would suggest a GSI but they all seem to be Android 10 and up, unless you want to try something like this.
Click to expand...
Click to collapse
Thanks - by `custom ROM`, do you mean something like LineageOS? Or are you saying I'd have to build something from source?
(I think the answer here is probably to just get a phone that hasn't/can't been upgraded past Android 9)
wwnsw said:
Thanks - by `custom ROM`, do you mean something like LineageOS? Or are you saying I'd have to build something from source?
(I think the answer here is probably to just get a phone that hasn't/can't been upgraded past Android 9)
Click to expand...
Click to collapse
I mean anything in .zip or .img form. It could be anything from a very slightly modified version of the Android 9 system+kernel for your device, to a full blown GSI.
The reason you can't use Odin to flash the original Android 9 firmware is because of an anti-rollback mechanism in the bootloader.
Since you're a developer, I would suggest finding a developer friendly device, like a Pixel. They have zero bloatware on them - they're meant to be the pure vanilla Android experience. The Pixel 2 launched with 8.0, and you can find it for less than $100. Just make sure you don't get a carrier branded device.