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.
Related
Many users reported TWO different variants of the April Security Update. One which is labeled April 1st and another April 5th. I am confused by this as well, I want to get all the hotfixes but my build does not match Google's OTA page.
I'm using a Pixel XL 2 and I have April 1st version on TELUS network. I got it yesterday night, the download was 46.6 MB My build number is OPM4.171019.015.A1 BUT per Google official OTA website it says I should have 8.1.0 (OPM2.171019.029, Apr 2018)
Can anyone shed some light on these TWO variants? Many Rogers users got April 1st but a few got April 5th. Bell seems to be all on April 5th. Telus/Koodo seems to be a mixed bag also.
The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.
ilal2ielli said:
The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.
Click to expand...
Click to collapse
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants
Waibashi said:
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants
Click to expand...
Click to collapse
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5
Two versions a couple of days apart of actually pretty common.
ilal2ielli said:
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5
Click to expand...
Click to collapse
That's explained a lot, thanks!
BUT for the Pixel security update. That means im missing on all the bugfixes if I understood correctly... It says here that all the hotfixes are included in. The 2018-04-05 version.
https://source.android.com/security/bulletin/pixel/2018-04-01
The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.
stevemw said:
The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.
Click to expand...
Click to collapse
So what would explain I have only received the April 1st update ? Is it possible to have two updates in one month? I never noticed that.
This is the first time I get the 1st patch too. I'm not the only one
I was able to update to the 4/5 patch at 8PM, 4/4. I'm on the Pixel 2 XL. Which model do you have? Have you done anything to the stock software?
Pixel 2 XL 64GB Stock OS.
I used the Beta Enrollment in the past, but this is a fresh phone from RMA.
Unable to update Latest Pack
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL
navi_j said:
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL
Click to expand...
Click to collapse
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:
Badger50 said:
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:
Click to expand...
Click to collapse
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks
navi_j said:
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks
Click to expand...
Click to collapse
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update ?
Badger50 said:
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update
Click to expand...
Click to collapse
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.
navi_j said:
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.
Click to expand...
Click to collapse
Just put your phone in bootloader mode, connect to pc, open up your command prompt, and run the command...fastboot flashing unlock_critical....
Again, this Will completely wipe your phone! ?
Has GPS lock issue been fixed?
Seems my thread got hijacked
Hi everyone, these may be of help to you. I'm not a dev so all I was doing here was using a rooted Sirocco to pull OTA files off the phone (data/ota_package). Using logcat/android bug report doesn't catch OTA URL on this device. It's my understanding they will need to be unpacked.
Files are in order of download/installation from A1N-310B-0-00WW-B03-OST604 onwards. That full firmware can be obtained here thanks to Hikari (Under Sirocco) https://hikaricalyx.com/fih-android-firmware/
The boot image for the firmware above can be found in the zip. It's already unpacked (A1N-0-310B-00WW-boot.img).
OTA 1 (Changelog - https://i.imgur.com/EeQeHyR.png)
https://mega.nz/#!SA1U3SzR!WAUtzV5AH2g6jYUYqhrUfMNh_tOe7ziNhNwZ8eZBxew
Boot image - https://mega.nz/#!2J8wBaBR!PbYVY4Ysr4l9idxReLrJe6wWu83KRy5tO29j0H2b3Ew
OTA 2 (Changelog - https://i.imgur.com/AOvs4Ps.png)
https://mega.nz/#!mB0EgCRa!oEKAxCl5iGnR3rHC91te0mgU3JgW3AXAO991kR4nj9g
Boot image - https://mega.nz/#!iU1WlKxT!mz1VrSGS987BbiPj1nvyUQzb4GEBw3686onS6ymctJI
OTA 3 (Changelog - https://i.imgur.com/nEpvMq2.png)
https://mega.nz/#!rNNAhASA!5_CdYQIym6iqc5ycN6wMqG0XvzrsCf70I3VQsy8bjFg
Boot image - https://mega.nz/#!SJt0WSxK!UkG4DbsDmUwIzExcmG1qo2xqhRk4lJlylhWHfMFJxfM
OTA 4 (Changelog - https://i.imgur.com/QH6Dnox.png)
https://mega.nz/#!HF8WlKDS!OpfBdAEUJSe_vzTebdCGg_DN_8Kzj5UZVG29x8aG6Q8
Boot image - https://mega.nz/#!7Usw1aKS!jEoZDlj5mtu5tqVpVG7XFaHLdDleiq3M6GBfy7_IUzc
OTA 5 (Changelog - https://i.imgur.com/bDSCAqX.png)
https://mega.nz/#!XUlWFKiC!_trT2aVmGQVhD-lzeZjWEn2LlmRZ4d6CMrKuAB41kkw
Boot image - https://mega.nz/#!KVl2WKqT!AcDI4YSOSo6vBe4Jb3FrOBsKGzO-KM5a8gowgNQXHog
OTA 6 (Changelog - https://i.imgur.com/ColEcRJ.png)
https://mega.nz/#!DE8QxSDQ!G1xRrjN9do28trYeQT-E9jAYmP7dszuXMKZ8kpmhcMI
Boot image - https://mega.nz/#!XB9EnY4A!UxLAX0hBabbKy09pGQz_BLQW9Hy5Lz0K4y15uVJcY7o
OTA 7 (Changelog - https://i.imgur.com/Tll0QuI.png)
https://mega.nz/#!zUsAzKLZ!TngURPA1pDUFjrmsrWvVglLmkE3GGGE4qX53-Vp38iU
Boot image - https://mega.nz/#!jck0iAjI!nEd890ZxQS1OaXX4ELNtdsIsa3TJZxddC1D7faPOB9U
OTA 8 (Changelog - https://i.imgur.com/HsZLwV4.png)
https://mega.nz/#!3dtEXQwY!CY6J3auoDeMelGSDmQiAJgOBHw3eH-sxrA3x51gXQ-U
Boot image - https://mega.nz/#!SQsUUYSD!iBwTMYd4OEDJJ7Me-zb2SnfPghc2me_ZEYR6SrdOkgU
OTA 9 (Changelog - https://i.imgur.com/eLVqDrM.png)
https://mega.nz/#!CEc1GQ7L!EiZYCubGDf5C97NNQDLZxmjcEaw555FbxHKvMNveZDw
Boot image - https://mega.nz/#!mNFzVCbD!RNTJI1_oPiHSapyykE0szjosBo_QnIoJiGZ0EQtmzqY
OTA 10 - Pie (Changelog - https://us.v-cdn.net/6031042/uploads/editor/je/y2ok3dg0norb.png)
https://mega.nz/#!fYUAgQJY!p6kO-B-IFwz0NhDv4ZlrDCQYKQGakH3fy9GbfG_kmDM
Boot image - https://mega.nz/#!qANy1a7b!ODh8ol97h8qJwZGndUCHqyG3qifnsfT7ILkggDaVoFA
Magisk patched boot - https://mega.nz/#!HYVimArR!m7BHM2iYVZVstTFx0W-zB01cSN-bb4lquKiYUmXoIm4
edit: TWRP removed, buggy
OTA 3 zip was corrupt, it has been replaced.
Also for helping out anyone who gets their Sirocco unlocked, this is a pre-rooted boot image for A1N-310B-0-00WW-B03-OST604
You can use this to do fastboot boot patched_boot.img and then use Magisk to root your device.
https://mega.nz/#!6dMgjCjL!KRkB39ppPp4RA0Wj57yjIjiXaE6B21f-B488yQFc61s
You can, of course, do the above yourself if you have a second phone that is rooted and go into Magisk and patch one of the stock file boot images above.
Now you can do OTAs and keep root
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390
If anyone is already on the November security update with this device and wants to root without downgrading, here is a magisk patched boot image
https://mega.nz/#!HBcHzYCB!KpqytpNth0Vfu3K9eX0vbP7heJ3MFPm6MX4ozC5L_qk
December security update added as OTA 9.
No Pie yet
Audioboxer said:
December security update added as OTA 9.
No Pie yet
Click to expand...
Click to collapse
Its a shame.
December patched boot for anyone who's had this phone unlocked and has done OTAs up to December without rooting
https://mega.nz/#!6R8RCIoB!ZPR7s-w4LWDXO1UcI7GBuhf7U0U3fujHLQIc6qlqx2g
As always, fastboot boot this image to root your phone with Magisk direct install. Do not flash my boot images, otherwise, you won't be able to do the OTA trick above with Magisk.
Removed: Oreo homebrew packages by Hikari are buggy, avoid.
So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...
marccoppers said:
So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...
Click to expand...
Click to collapse
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.
Audioboxer said:
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.
Click to expand...
Click to collapse
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.
marccoppers said:
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.
Click to expand...
Click to collapse
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.
Audioboxer said:
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.
Click to expand...
Click to collapse
That was my guess to. Thanx for the info.
You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk
rajeev.rao87blr said:
You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk
Click to expand...
Click to collapse
My advice was just following what Nokia devs like Calyx Hikari state. If you do not have an unlocked bootloader its best not to install internal OTAs because there is no way to revert to retail FW. The Nokia 8 had an official beta test so there was a way to rollback off of the beta Pie firmware to Oreo again, to then install the final Pie OTA.
Otherwise you need an unlocked bootloader to flash an Oreo/Pie retail package with LA OST.
I don't mean to offend anyone, I just don't want anyone installing these leaked OTAs on their bootloader locked device and being stuck.
Currently, there's no way to roll back to Android 8.1 for Nokia 8 Sirocco by yourself, so use these packages at your own risk.
It will be better if you're using prototype device or a retail device with unlocked bootloader.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...stall-android-pie-build-t3885834/post78591840
Nokia 8 Sirocco doesn't need any bootloader to be unlocked.
Nokia 8 Sirocco doesn't need bootloader to be unlocked. Like I got it and others who installed got it without doing the same. You just have to downloaded the A1N 4200 file and reboot the phone to safe mode and the phone automatically detects the update. So I assume that's pretty much official and valid .
Don't know why people end up spreading rumours without knowing the real picture. Just because one device works in a specfic way doesn't mean every device functions the same way.
Plus Nokia 8 Sirrocco gets all the features a full fledged android one device gets including the below
1. Adaptive Battery
2. Gestures
3. Digital Wellbeing
I myself wanted to write a review and a video but never written one for mobile devices, I have done for vehicles.
And most importantly Nokia 8 and Nokia 8 Sirocco are different mobiles . The only common point is The processor.
Pie OTA Rom
Now that the official PIE OTA has been released can anyone capture it and post a link to the file? It can take weeks to reach people over the air sometimes!
Thanks
Let's say they will be captured, can i install them with a locked bootloader?
marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
I did on the Nokia 8 and the Nokia 7 plus by downloading to the device, renaming the file and using the phone keypad ( *#*#874#*#*) so I assume it will be the same on the Sirocco?
marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
Sideloading the OTA via ADB can be done on a locked bootloader. The method by EGGMEN should work as well. :good:
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, I'm on 210817.036 (Nov. 2021) on an unlocked Pixel 6 Pro.
I was finally able to unlock it today from AT&T and wondering if I should update to the latest Android update before rooting.
Thanks for any advice!
I wouldn't bother, because OTAs take longer than flashing full firmware. i.e. As part of the rooting process, I would go ahead and flash the latest full firmware instead.
SDK Platform Tools
Get the Google USB Driver
Official Google Android Flash Tool
Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.
DevanteWeary said:
Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.
Click to expand...
Click to collapse
You're welcome!
I never had any issues at all, even with the fingerprint reader, from the end of October when I received mine through the second February patch. Hopefully, yours will be the same way.
At worst, once you unlock the bootloader if you have any issues with how things run, you can always flash any firmware you like. Be careful. You can also accidentally flash the wrong firmware. Coincidentally, I accidentally gave you a link to the official flashing site, which is good for staying stock unrooted, but if you're going to be rooted, I actually recommend the Pixel 6 Pro Factory Images. Just only ever use images that have Raven in the name as flashing the wrong thing can make it so that your phone would be unrecoverable.
Forgive me if I'm repeating anything you already know.
Hi guys,
The question is in the title.
Now, I know it's probably not recommended to downgrade without unlocking the bootloader. But this is not about what's recommended. It's about what's possible.
Also, I've got a weird theory, but it's only a theory. I feel like it should be possible to downgrade if the security patch of the ROM you're coming from is lower or equal to the one of the ROM you're about to flash. In other words, as long as you're not downgrading your security patch. I've experimented with this with my old Moto One Action, and, while this was a long time ago, I remember this to be the case. But maybe my memory is not as good as it used to be, so I could be wrong. So don't take this as fact, but rather an open discussion.
Anyway, I'm curious if anybody tried to downgrade stock ROM from Android 12 to Android 11 and succeeded, without unlocking the bootloader.
I'm guessing you should erase userdata, since I don't think you can boot into the OS with Android 12 data on Android 11.
Also, I'm curious if anybody noticed a relevance for my theory above. Does it have anything to do with the security patch? Can anyone confirm this working?
Looking forward to your answers.
i think its possible if you can find Android 11 rom in anotjer websites or you can try to find a device that is not upgraded and then took rom backup from that and then use it in your device but i think you need to unlock bootloader in all cases
godslayer.04 said:
i think its possible if you can find Android 11 rom in anotjer websites or you can try to find a device that is not upgraded and then took rom backup from that and then use it in your device but i think you need to unlock bootloader in all cases
Click to expand...
Click to collapse
The ROM is not a problem. I already have a backup from before the update. Also, there are third party mirror sites for that. So that's not a problem.
The only thing I was curious about is whether or not it would be (theoretically) possible to downgrade an Android version (in this case, let's say it's 12 down to 11) without unlocking the bootloader.
I guess the answer is no then...
If I had another Moto G60, I'd try this myself. But I only have one... So I can't really test.
I was hoping someone already tried before. Or at least knows the theory around it.
Thank you very much for your reply!
arsradu said:
The ROM is not a problem. I already have a backup from before the update. Also, there are third party mirror sites for that. So that's not a problem.
The only thing I was curious about is whether or not it would be (theoretically) possible to downgrade an Android version (in this case, let's say it's 12 down to 11) without unlocking the bootloader.
I guess the answer is no then...
If I had another Moto G60, I'd try this myself. But I only have one... So I can't really test.
I was hoping someone already tried before. Or at least knows the theory around it.
Thank you very much for your re
arsradu said:
The ROM is not a problem. I already have a backup from before the update. Also, there are third party mirror sites for that. So that's not a problem.
The only thing I was curious about is whether or not it would be (theoretically) possible to downgrade an Android version (in this case, let's say it's 12 down to 11) without unlocking the bootloader.
I guess the answer is no then...
If I had another Moto G60, I'd try this myself. But I only have one... So I can't really test.
I was hoping someone already tried before. Or at least knows the theory around it.
Thank you very much for your reply!
Click to expand...
Click to collapse
you can try one more thing you can go to service center and then ask them to do so once i got downgrade my realme narzo 20 from android 11 to 10 and they did so and my bootloader is locked already
Click to expand...
Click to collapse
Yeah... Thing is, you can unlock and relock the bootloader. Also, is it the same phone (same IMEI) with the one you sent for repair? Cause they sometimes just replace the phone entirely.
If they really downgraded your OS, it would be interesting to know how they did it. Simple reflash of the OS? Or unlocked bootloader, flashed and then relocked? Cause that will work for sure. )
Now, there's also another thing. That was a Realme, this is a Motorola. Different manufacturers might have different ways/tools to achieve the same thing.
But the idea remains, of course. It should be possible to downgrade the OS, if you bring your phone to a repair center. However, what I'm trying to understand here is if you can do it yourself, at home, with a simple data cable and the OS itself, ooor...if you need special tools for that.
Also the question is hypothetical. I don't plan on actually bringing the phone to a repair service for downgrade. I just wanna know if it's possible, so I can eventually do it myself at home. Sending the phone for repair to a repair center usually takes time. So...if it's not a hardware issue, I'm trying to fix it at home.
arsradu said:
Yeah... Thing is, you can unlock and relock the bootloader. Also, is it the same phone (same IMEI) with the one you sent for repair? Cause they sometimes just replace the phone entirely.
If they really downgraded your OS, it would be interesting to know how they did it. Simple reflash of the OS? Or unlocked bootloader, flashed and then relocked? Cause that will work for sure. )
Now, there's also another thing. That was a Realme, this is a Motorola. Different manufacturers might have different ways/tools to achieve the same thing.
But the idea remains, of course. It should be possible to downgrade the OS, if you bring your phone to a repair center. However, what I'm trying to understand here is if you can do it yourself, at home, with a simple data cable and the OS itself, ooor...if you need special tools for that.
Also the question is hypothetical. I don't plan on actually bringing the phone to a repair service for downgrade. I just wanna know if it's possible, so I can eventually do it myself at home. Sending the phone for repair to a repair center usually takes time. So...if it's not a hardware issue, I'm trying to fix it at home.
Click to expand...
Click to collapse
Dude, I relocked my bootloader and guess what, now I cannot do anything.
Booting into the OS is not working as it says no OS found
Flashing images does not work since the bootloader is locked.
ankurpandeyvns said:
Dude, I relocked my bootloader and guess what, now I cannot do anything.
Booting into the OS is not working as it says no OS found
Flashing images does not work since the bootloader is locked.
Click to expand...
Click to collapse
Do you also happen to have an answer to the question in this topic?
ankurpandeyvns said:
Dude, I relocked my bootloader and guess what, now I cannot do anything.
Booting into the OS is not working as it says no OS found
Flashing images does not work since the bootloader is locked.
Click to expand...
Click to collapse
SAME issue with mine - we have all talked about this in the other posts. Unlocking bootloader on Moto phones seem to be risky. ONCE UNLOCKED, I SUGGEST PEOPLE DO NOT RE-LOCK THE BOOTLOADER AGAIN ON ANY ANDROID PHONE FOR THAT MATTER !!
arsradu said:
Do you also happen to have an answer to the question in this topic?
Click to expand...
Click to collapse
I have searched everywhere on the net and there's no solution to rollback an android 12 to 11 (i.e. without unlocking OEM)
Just curious - my G60 is on android 11 right now and I'm really hesitating in updating it to 12.
Why are you and other people talking about a rollback? Is the performance/bugs on 12 that bad?!!
KayaNN said:
I have searched everywhere on the net and there's no solution to rollback an android 12 to 11 (i.e. without unlocking OEM)
Just curious - my G60 is on android 11 right now and I'm really hesitating in updating it to 12.
Why are you and other people talking about a rollback? Is the performance/bugs on 12 that bad?!!
Click to expand...
Click to collapse
No it's not. But Android 12 comes with a few design choices not many people would like. So...I would suggest searching online for a review of the Android 12 update (there are plenty of them on YouTube for example) and see you're ok with those changes.
arsradu said:
No it's not. But Android 12 comes with a few design choices not many people would like. So...I would suggest searching online for a review of the Android 12 update (there are plenty of them on YouTube for example) and see you're ok with those changes.
Click to expand...
Click to collapse
I did check them out and the negative reviews were aplenty. I wanted a few reviews from the XDA community on Motog60 having Android12.
Which design choice did you find cumbersome/unwieldy?
KayaNN said:
I did check them out and the negative reviews were aplenty. I wanted a few reviews from the XDA community on Motog60 having Android12.
Which design choice did you find cumbersome/unwieldy?
Click to expand...
Click to collapse
For example the quicksettings toggles. They are bigger in Android 12, they take more space, and in terms of connectivity toggle, Google combined Mobile Data and WiFi, which...I personally would have preferred them to be separated (like in Android 11 and previous ones), but...it is what it is. It's not that bad.
Also, something else you might like or dislike, is the new Material You design. Which takes colors from your wallpaper. In my opinion, it doesn't work very well. I mean, it tends to give you very little contrast between the icons and backgrounds. It's not that bad, you can customise it...to a certain extent, but...it's a design choice I wish Google would have thought more about. It looks like something that still needed more time to mature. It looks a bit rushed and unpolished. But you can get it to look decent.
And one more thing, and I have no idea why they did that, they removed the ability to customise fonts and icon shapes.
Motorola still kept them in their version of Android 12, but it's been removed by Google from AOSP.
If you watched those reviews and you're ok with those changes, just go for it.
arsradu said:
For example the quicksettings toggles. They are bigger in Android 12, they take more space, and in terms of connectivity toggle, Google combined Mobile Data and WiFi, which...I personally would have preferred them to be separated (like in Android 11 and previous ones), but...it is what it is. It's not that bad.
Also, something else you might like or dislike, is the new Material You design. Which takes colors from your wallpaper. In my opinion, it doesn't work very well. I mean, it tends to give you very little contrast between the icons and backgrounds. It's not that bad, you can customise it...to a certain extent, but...it's a design choice I wish Google would have thought more about. It looks like something that still needed more time to mature. It looks a bit rushed and unpolished. But you can get it to look decent.
And one more thing, and I have no idea why they did that, they removed the ability to customise fonts and icon shapes.
Motorola still kept them in their version of Android 12, but it's been removed by Google from AOSP.
If you watched those reviews and you're ok with those changes, just go for it.
Click to expand...
Click to collapse
Thanks for elaborating dude It makes sense now - I thought those very same customizable features were a bomb. Now after understanding your point to view, I'd rather stay in 11
Cheers!
And also, good luck in rolling back to 11 without unlocking the bootloader. Keep us updated when you do find a way to do so!
arsradu said:
Hi guys,
The question is in the title.
Now, I know it's probably not recommended to downgrade without unlocking the bootloader. But this is not about what's recommended. It's about what's possible.
Also, I've got a weird theory, but it's only a theory. I feel like it should be possible to downgrade if the security patch of the ROM you're coming from is lower or equal to the one of the ROM you're about to flash. In other words, as long as you're not downgrading your security patch. I've experimented with this with my old Moto One Action, and, while this was a long time ago, I remember this to be the case. But maybe my memory is not as good as it used to be, so I could be wrong. So don't take this as fact, but rather an open discussion.
Anyway, I'm curious if anybody tried to downgrade stock ROM from Android 12 to Android 11 and succeeded, without unlocking the bootloader.
I'm guessing you should erase userdata, since I don't think you can boot into the OS with Android 12 data on Android 11.
Also, I'm curious if anybody noticed a relevance for my theory above. Does it have anything to do with the security patch? Can anyone confirm this working?
Looking forward to your answers.
Click to expand...
Click to collapse
Hi,
I have a Moto One action XT2013-2 RETIN running on Android 11 July 2022 security update. I want to downgrade it to Android 10. After 11, the HDR function of the camera and NFC stopped working. Can I safely downgrade it to Android 10 without unlocking the bootloader ?.
Do you still have the One Action with you? If so, I kindly request you to confirm whether it is safe to do so with One Action.
Also one more question, can i fix the NFC and camera HDR issue without downgrading to Android 10 ?. I had a look into the dtbo file, opened in Notepad and found out some chip level instructions and found something regarding camera HDR and NFC. Is there a safe way to modify the file to get back HDR and NFC
working?
zankdroid said:
Hi,
I have a Moto One action XT2013-2 RETIN running on Android 11 July 2022 security update. I want to downgrade it to Android 10. After 11, the HDR function of the camera and NFC stopped working. Can I safely downgrade it to Android 10 without unlocking the bootloader ?.
Do you still have the One Action with you? If so, I kindly request you to confirm whether it is safe to do so with One Action.
Also one more question, can i fix the NFC and camera HDR issue without downgrading to Android 10 ?. I had a look into the dtbo file, opened in Notepad and found out some chip level instructions and found something regarding camera HDR and NFC. Is there a safe way to modify the file to get back HDR and NFC
working?
Click to expand...
Click to collapse
No, I don't think you can downgrade to Android 10 without unlocking the bootloader. I'm trying to confirm that myself. But so far, no, I don't recommend it. You can try if you want, but most likely, it's not gonna work.
I don't know what the issue with NFC and HDR is, but I would recommend trying to figure that out instead of thinking about downgrading. I don't think the issue is the update to Android 11. I think the issue is somewhere else (possible hardware).
arsradu said:
No, I don't think you can downgrade to Android 10 without unlocking the bootloader. I'm trying to confirm that myself. But so far, no, I don't recommend it. You can try if you want, but most likely, it's not gonna work.
I don't know what the issue with NFC and HDR is, but I would recommend trying to figure that out instead of thinking about downgrading. I don't think the issue is the update to Android 11. I think the issue is somewhere else (possible hardware
Click to expand...
Click to collapse
I have seen another guy on Lenovo forums with the same issue. His phone was a RETGB version. He says the Android 11 September 2021 patch caused the HDR issue. The problem is same as mine.
If I try to downgrade to 10 , will it result in a hard brick which even the Rescue software wouldn't be able to save ? like a permanent brick?
I have gone through the dtbo file and searched for NFC and HDR. Found some differences here
Android 9
sec-nfc, ldo_en exynos,block-type exynos
Android 11
sec-nfc,ldo_en sec-nfc,pmic-ldo exynos
I have found some lines in the dtbo file like
HDR Max Luma, Average Luma and Min luma etc which represents the three exposure images that the camera captures to produce an HDR image
Android 10 dtbo also has some differences compared to 11
Is there any way to port the old camera software to Android 11 and also to fix the NFC issue?
Can I replace the Android 11 dtbo file with Android 10 dtbo and then reflash Android 11?
zankdroid said:
I have seen another guy on Lenovo forums with the same issue. His phone was a RETGB version. He says the Android 11 September 2021 patch caused the HDR issue. The problem is same as mine.
If I try to downgrade to 10 , will it result in a hard brick which even the Rescue software wouldn't be able to save ? like a permanent brick?
I have gone through the dtbo file and searched for NFC and HDR. Found some differences here
Android 9
sec-nfc, ldo_en exynos,block-type exynos
Android 11
sec-nfc,ldo_en sec-nfc,pmic-ldo exynos
I have found some lines in the dtbo file like
HDR Max Luma, Average Luma and Min luma etc which represents the three exposure images that the camera captures to produce an HDR image
Android 10 dtbo also has some differences compared to 11
Is there any way to port the old camera software to Android 11 and also to fix the NFC issue?
Can I replace the Android 11 dtbo file with Android 10 dtbo and then reflash Android 11?
Click to expand...
Click to collapse
"If I try to downgrade to 10 , will it result in a hard brick which even the Rescue software wouldn't be able to save ? like a permanent brick?"
Never tried, so I don't know. If you do it with an UNLOCKED bootloader, it should be fine. I don't know about locking the bootloader after that.
But what I would recommend, if you want to attempt this, is boot into Android 10 (after flashing), BEFORE locking the bootloader, and make sure the OEM Unlocking option is still ON (meaning bootloader is still unlockable)! Yes, even if the bootloader is currently unlocked. That option is very important.
If it's still ON, THEORETICALLY you should be able to lock the bootloader back. And, even if there would be issues, since the bootloader is still unlockABLE, you should be able to fix them by unlocking the bootloader and flashing whatever it needs to be flashed to fix this. I repet, this is only a THEORY. Attempt this on your own risk!
My Moto Action is on July security patch right now (RETEU). So...I can't confirm anything regarding September security patch.
"Android 10 dtbo also has some differences compared to 11
Is there any way to port the old camera software to Android 11 and also to fix the NFC issue?"
Never tried it. It should be possible. But also, I have a feeling the camera software is actually the same. So, if it's a bug with the camera, it should be present in both. But I don't think the camera is the problem here. I think the actual OS is the problem.
Are you using the correct build for your region? Have you ever flashed something else? This is weird, for a stock ROM.
"Can I replace the Android 11 dtbo file with Android 10 dtbo and then reflash Android 11?"
You can try... I never tried it, so I don't know if it works or not.
HOWEVER, all these things seem like a very complicated way to fix these issues, in my opinion.
IF the problem is hardware (NFC for example, which I still don't know what's wrong with it), you need to fix it on a hardware level. If it's software, you need to submit a bug report to Motorola, so they can fix it in an update.
If the HDR thing is a software issue, and it's been intriduced by an update, you need to let Motorola know about it, submit a bug report (with logs) so they can fix it with a future update!
What I'm trying to say is that downgrading is NOT the way to go!
It's not easy. It will break your warranty (if you have any), because you will likely need to unlock the bootloader, in order to downgrade, and if it's a hardware issue, it will not fix it.
Is your
arsradu said:
"If I try to downgrade to 10 , will it result in a hard brick which even the Rescue software wouldn't be able to save ? like a permanent brick?"
Never tried, so I don't know. If you do it with an UNLOCKED bootloader, it should be fine. I don't know about locking the bootloader after that.
But what I would recommend, if you want to attempt this, is boot into Android 10 (after flashing), BEFORE locking the bootloader, and make sure the OEM Unlocking option is still ON (meaning bootloader is still unlockable)! Yes, even if the bootloader is currently unlocked. That option is very important.
If it's still ON, THEORETICALLY you should be able to lock the bootloader back. And, even if there would be issues, since the bootloader is still unlockABLE, you should be able to fix them by unlocking the bootloader and flashing whatever it needs to be flashed to fix this. I repet, this is only a THEORY. Attempt this on your own risk!
My Moto Action is on July security patch right now (RETEU). So...I can't confirm anything regarding September security patch.
"Android 10 dtbo also has some differences compared to 11
Is there any way to port the old camera software to Android 11 and also to fix the NFC issue?"
Never tried it. It should be possible. But also, I have a feeling the camera software is actually the same. So, if it's a bug with the camera, it should be present in both. But I don't think the camera is the problem here. I think the actual OS is the problem.
Are you using the correct build for your region? Have you ever flashed something else? This is weird, for a stock ROM.
"Can I replace the Android 11 dtbo file with Android 10 dtbo and then reflash Android 11?"
You can try... I never tried it, so I don't know if it works or not.
HOWEVER, all these things seem like a very complicated way to fix these issues, in my opinion.
IF the problem is hardware (NFC for example, which I still don't know what's wrong with it), you need to fix it on a hardware level. If it's software, you need to submit a bug report to Motorola, so they can fix it in an update.
If the HDR thing is a software issue, and it's been intriduced by an update, you need to let Motorola know about it, submit a bug report (with logs) so they can fix it with a future update!
What I'm trying to say is that downgrading is NOT the way to go!
It's not easy. It will break your warranty (if you have any), because you will likely need to unlock the bootloader, in order to downgrade, and if it's a hardware issue, it will not fix it.
Click to expand...
Click to collapse
I am from India . When I bought the phone and booted it for the first time, the default language was English United States. NFC and HDR were working fine, Auto HDR very well responded to changing light conditions and produced well optimized HDR images.
Got Android 10 after a few months and even after that everything was fine.
Following one Android 10 security update (can't remember which update), the file manager started crashing.
Then for the first time I tried a Rescue using the official Lenovo rescue Software for a clean software installation. The software detected my phone and downloaded the correct firmware and installed it.
After rescue when the phone booted up to the setup screen, the default language was English India.
The File manager crashing issue was fixed. NFC and HDR continued to work fine. Everything was perfect until I received Android 11. After that NFC stopped working.
Auto HDR is now not detecting ambient light conditions very well and with HDR ON mode it is not optimizing the bright and dark areas of the image.
As I have told earlier, In Lenovo forums I found another guy who is having RETGB version of One Action with the same HDR issue. He didn't mention anything about NFC. I have also contacted Lenovo regarding the issue but of no use.
Is NFC and Camera HDR working well in your phone with RETEU firmware?.
If it's working can I install RETEU firmware in my phone?. I don't know about the carrier frequencies in Europe and India.
I am currently on July 2022 RETIN
RSBS31.Q1-48-36-26 version and I believe July security patch is the last update for the phone.
arsradu said:
Hi guys,
The question is in the title.
Now, I know it's probably not recommended to downgrade without unlocking the bootloader. But this is not about what's recommended. It's about what's possible.
Also, I've got a weird theory, but it's only a theory. I feel like it should be possible to downgrade if the security patch of the ROM you're coming from is lower or equal to the one of the ROM you're about to flash. In other words, as long as you're not downgrading your security patch. I've experimented with this with my old Moto One Action, and, while this was a long time ago, I remember this to be the case. But maybe my memory is not as good as it used to be, so I could be wrong. So don't take this as fact, but rather an open discussion.
Anyway, I'm curious if anybody tried to downgrade stock ROM from Android 12 to Android 11 and succeeded, without unlocking the bootloader.
I'm guessing you should erase userdata, since I don't think you can boot into the OS with Android 12 data on Android 11.
Also, I'm curious if anybody noticed a relevance for my theory above. Does it have anything to do with the security patch? Can anyone confirm this working?
Looking forward to your answers.
Click to expand...
Click to collapse
The problem is the firmware. You must check for the right firmware version for that Android release.
Let's say for example: I flash a custom rom A10 based and I take a nandroid backup with TWRP. Then some time later I flash the upgrade for this custom rom to A11 (flashing the correct firmware for this release) and I take a nandroid backup also for this rom upgrade. Now I have 2 nandroid backup, one is old A10 and other is for the new A11. Well, if I try to RESTORE the old A10 based rom, it don't works, because I previously flash the firmware to flash A11 rom.