Got myself a Redmi Note 5 Global version and want to update MIUI and possibly try a custom ROM. Just came here to make sure i'm not falling for any common mistakes before i do anything especially after reading a lot of folks that have bricked these devices due to Anti Roll-back so thats the last thing i want to do. The device came boxed with MIUI 9.5.6.0(OEIMIFA) and i've just ignored the update notification up to now so i presume i've avoided ARB and i would like to keep it that way.
So just to confirm are these the correct steps.
1. Unlock the bootloader
2. Flash a custom recovery (TWRP or the equivalent)
3. Update MIUI / Flash custom rom package without ARB and flash through TWRP
Is there anything i'm missing or anything i need to specifically avoid other than ARB?
drkdeath5000 said:
Got myself a Redmi Note 5 Global version and want to update MIUI and possibly try a custom ROM. Just came here to make sure i'm not falling for any common mistakes before i do anything especially after reading a lot of folks that have bricked these devices due to Anti Roll-back so thats the last thing i want to do. The device came boxed with MIUI 9.5.6.0(OEIMIFA) and i've just ignored the update notification up to now so i presume i've avoided ARB and i would like to keep it that way.
So just to confirm are these the correct steps.
1. Unlock the bootloader
2. Flash a custom recovery (TWRP or the equivalent)
3. Update MIUI / Flash custom rom package without ARB and flash through TWRP
Is there anything i'm missing or anything i need to specifically avoid other than ARB?
Click to expand...
Click to collapse
Just don't update your firmware (or update it with a ARB-less firmware), that's what will trigger ARB. Most of the customs rom don't contain firmware, only LOS advises you to flash a specific version, but MIUI roms do.
So you either steer away from those and flash fw-less roms, or you just delete the firmware-files folder from the rom and flash it without them.
This is my advice, before flashing anything, open the zip and check for the firmware folder. If it has it, delete it (unless is specified by the dev to flash that along the rom, in that case, just avoid it, there's a plethora of custom roms to choose from).
Ok thanks so i'll just stay clear of any roms containing the firmware folder for now. I do like LOS but if theres any risk associated i'll just give it a miss for now.
I also assume its easy to recover from a bad flash following the no firmware folder rule since theres no real risk associated with flashing just a ROM(no firmware)?
Finally, what about kernels and bootloader updates is there anything specific i need to watch out for there? I only ask because my previous device included a sneaky OTA update which locked the bootloader and i'd obviously like to avoid anything like that here.
Sorry for all the questions i'm just a bit behind on the flashing front, my previous device was a Motorola Razr HD and flashing seems to have changed quite a bit since then.
drkdeath5000 said:
Ok thanks so i'll just stay clear of any roms containing the firmware folder for now. I do like LOS but if theres any risk associated i'll just give it a miss for now.
I also assume its easy to recover from a bad flash following the no firmware folder rule since theres no real risk associated with flashing just a ROM(no firmware)?
Finally, what about kernels and bootloader updates is there anything specific i need to watch out for there? I only ask because my previous device included a sneaky OTA update which locked the bootloader and i'd obviously like to avoid anything like that here.
Sorry for all the questions i'm just a bit behind on the flashing front, my previous device was a Motorola Razr HD and flashing seems to have changed quite a bit since then.
Click to expand...
Click to collapse
No problems, happy to help if I can.
And yes, no risk if you don't flash firmware. Worst case scenario, you'll have to reflash a miui rom with MiFlash, which means losing your data, but imo it's better than bricking the device.
As for kernels and bootloader, you're good to go. Nothing will relock your bootloader (except flashing with MiFlash and selecting that specific option) and a kernel in the worst case will just give you a bootloop. Use backups. ?
And as far as LOS goes, you can flash it without the specified firmware (even tho I'm pretty sure it's an ARB3 firmware) but I guess there might be some small issues.
Good luck with unlocking the bootloader, that thing takes from 720 to 1440 hours, just got my rn5p in a week now i have to wait a month before rooting...
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
I have the same problem. I can't even downgrade
New version 22.0.0.0 and no signal bug. Omfg
Having trouble since open beta 1 in receiving and placing calls, crazy what 1+ is releasing
12 sounds is shaky at best
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
I'm still hoping they will release 12.0.0.1 this night
Jomsha said:
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
Click to expand...
Click to collapse
Same issues here
Indian version
Eslam.hanafy said:
Same issues here
Indian version
Click to expand...
Click to collapse
Ob2 did that already. No sim if 5g is turned on..Gonna root later, no big deal
Jomsha said:
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
Click to expand...
Click to collapse
try this method i posted in a thread, and let me know..
OOS 12.0.0 Stable Update Cellular Network Fix
Hi, As you may know most of us is having this issue after the OOS 12.0.0 Stable Update, Cellular Network lost, No Signal, Outgoing call, and SMS. The below method worked at least for me, let me know if worked with anyone of you please. Please...
forum.xda-developers.com
h8Aramex said:
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
Click to expand...
Click to collapse
How did you get into edl mode running A12?
My network doesn't work on OOS12 stable for some reason. I spent 2 days flashing different oos12 builds (eu, global, indian) to try to see if the network comes back, tried literally everything but no luck
Very disappointed. Had to come back to OOS11. Everything works perfectly, except the fact that I'm not running the latest android version on my flagship 9 Pro.
Read my post here. And back through a few others.
jruizdesign said:
I was getting the same issue, but flashing a different variant of your current c.44 should do the trick.
Ex: I have a LE2127 (TMO), I converted with a11 to use LE2123(EU) software updates. When android 12 hit my phone wouldn't give me data on the 2123 update, so I had to download the LE2125(global/NA) update and flash using the the system update app that was so generously given in the following post:
Post in thread '[TMO] 9 PRO MODEM RETENTION' https://forum.xda-developers.com/t/tmo-9-pro-modem-retention.4292445/post-86328243
I don't know what software or model your phone is now, so I am NOT suggesting you switch if you are not already on 2123 or 2125. Those two are interchangeable without problem so it should be fine
Click to expand...
Click to collapse
I don't know anything about the Indian variant so I'm not sure if the same fixed will work.
But I can tell you I have tried every msm tool and almost every possible variant an no matter what goes wrong there has been a fix here in the these forums already.
Currently running lastest c.44 global LE2125 A12 on my TMo LE2127 model device with ZERO bugs so far. Data works flawlessly
khanboy619 said:
My network doesn't work on OOS12 stable for some reason. I spent 2 days flashing different oos12 builds (eu, global, indian) to try to see if the network comes back, tried literally everything but no luck
Very disappointed. Had to come back to OOS11. Everything works perfectly, except the fact that I'm not running the latest android version on my flagship 9 Pro.
Click to expand...
Click to collapse
Did you read the data retention thread and msm using the given tool in that thread ONLY? If you use that msm tool, the take the local update to 11.2.9.9 then update the your variant of C44 you should have no issues.
jruizdesign said:
Did you read the data retention thread and msm using the given tool in that thread ONLY? If you use that msm tool, the take the local update to 11.2.9.9 then update the your variant of C44 you should have no issues.
Click to expand...
Click to collapse
Are you sure about this?? Because I flashed OOS12 by first flashing OS 11.2.8.8 through MSM tool and then updating to android 12.
Do you think flashing 11.2.9.9 will actually work, because I'll have to through the hastle of downgrading and then updating again. (As I'm running 11.2.10.10 atm)
The help is much appreciated.
h8Aramex said:
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
Click to expand...
Click to collapse
The easiest way to crashdump after this update is trying to flash your modem files like you would of you of on a11.
jruizdesign said:
The easiest way to crashdump after this update is trying to flash your modem files like you would of you of on a11. Easy fix with msm to stock and try again
Click to expand...
Click to collapse
khanboy619 said:
Are you sure about this?? Because I flashed OOS12 by first flashing OS 11.2.8.8 through MSM tool and then updating to android 12.
Do you think flashing 11.2.9.9 will actually work, because I'll have to through the hastle of downgrading and then updating again. (As I'm running 11.2.10.10 atm)
The help is much appreciated.
Click to expand...
Click to collapse
No 11.2.10.10 you get the same result no need to downgrade.
Amd4life said:
How did you get into edl mode running A12?
Click to expand...
Click to collapse
Same way you would in android 11.
Make sure the phone is completely off. Hold volume up and volume down buttons, and plug it in.
Make sure you already have the msm tool fully opened and ready to click enum.
As soon as you plug it in it should say ok ok in the tool, click enum then start.
I stress that point to do it quickly because it will fail with different errors if it's not done quick enough after the device is plugged in.
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.