Hi there. I think what I'm having is a network issue but I'm not entirely sure yet. I was hoping some of the good folks here might be able to help me figure it out.
So I have used the steps (to the letter) from the post titled "Free Sprint Moto Z2 Force carrier unlock quick and painless" by @Jessoocaca. (Many thanks to you @Jessooca, I'm actually running MetroPCS! YAY!) But I'm running into a problem. Motorola keeps telling me to run an update, and I'm not entirely sure how to deal with it. It states that it was a Jan 2019 update, version OCXS27.109-48-15.
My question is this. I've read as much as I can about the update and what it entails. My bootloader is still unlocked, Magisk is still on my phone, TWRP is also still on my phone. Also, as this is the XTXT1789-03, the Sprint version, I'm not entirely sure what to even do about the update. Is it something I actually need?
In System it does say that I'm still on the Sprint software variant and the Sprint software channel. Is that something I can change in order to get the update? Would it require a different ROM?
Auuugghhh. *headdesk*
Please advise! I would be much much obliged. Thanks in advance.
Don't update since you are rooted and has TWRP.
Only update when you are fully stocked (no TWRP, no root)..
Monstroquodlucet said:
Hi there. I think what I'm having is a network issue but I'm not entirely sure yet. I was hoping some of the good folks here might be able to help me figure it out.
So I have used the steps (to the letter) from the post titled "Free Sprint Moto Z2 Force carrier unlock quick and painless" by @Jessoocaca. (Many thanks to you @Jessooca, I'm actually running MetroPCS! YAY!) But I'm running into a problem. Motorola keeps telling me to run an update, and I'm not entirely sure how to deal with it. It states that it was a Jan 2019 update, version OCXS27.109-48-15.
My question is this. I've read as much as I can about the update and what it entails. My bootloader is still unlocked, Magisk is still on my phone, TWRP is also still on my phone. Also, as this is the XTXT1789-03, the Sprint version, I'm not entirely sure what to even do about the update. Is it something I actually need?
In System it does say that I'm still on the Sprint software variant and the Sprint software channel. Is that something I can change in order to get the update? Would it require a different ROM?
Auuugghhh. *headdesk*
Please advise! I would be much much obliged. Thanks in advance.
Click to expand...
Click to collapse
Don't update since you are rooted and has TWRP.
Only update when you are fully stocked (no TWRP, no root)..
Monstroquodlucet said:
Hi there. I think what I'm having is a network issue but I'm not entirely sure yet. I was hoping some of the good folks here might be able to help me figure it out.
So I have used the steps (to the letter) from the post titled "Free Sprint Moto Z2 Force carrier unlock quick and painless" by @Jessoocaca. (Many thanks to you @Jessooca, I'm actually running MetroPCS! YAY!) But I'm running into a problem. Motorola keeps telling me to run an update, and I'm not entirely sure how to deal with it. It states that it was a Jan 2019 update, version OCXS27.109-48-15.
My question is this. I've read as much as I can about the update and what it entails. My bootloader is still unlocked, Magisk is still on my phone, TWRP is also still on my phone. Also, as this is the XTXT1789-03, the Sprint version, I'm not entirely sure what to even do about the update. Is it something I actually need?
In System it does say that I'm still on the Sprint software variant and the Sprint software channel. Is that something I can change in order to get the update? Would it require a different ROM?
Auuugghhh. *headdesk*
Please advise! I would be much much obliged. Thanks in advance.
Click to expand...
Click to collapse
Will I have device issues if I don't update?
Also will I lose service if I unroot and re-lock my bootloader?
Monstroquodlucet said:
Also will I lose service if I unroot and re-lock my bootloader?
Click to expand...
Click to collapse
Just run an official flash all, reboot, take update and reroot. No reason to relock.
My wife had been on whatever stock ROM came on her Pixel 2 since i bought it with no issues. She ran into a problem after maxing out her storage that the phone wouldn't boot and stayed stuck at the "G" boot screen. I got that fixed by sideloading an OTA of what seems to be some pre-release version of Android. it says "R" version. Many vital apps aren't working correctly - messaging, gmail, can't search from google bar, camera stopped working properly. So i am thinking i should start fresh and install something else now that at least the OS is back booting properly and hopefully everything will work ok.
I just want to make sure if anyone can help tell me what i'm dealing with, i believe this was a locked bootloader? not sure i can or need to unlock it.... > Install twrp... > Flash stock rom...? she doesn't need a fancy rom just something simple and stable.
Here's some of her vital info, any tips greatly apprecaited as i'm out of the loop on this stuff and an old pedestrian user at best.
Android Version
R
Baseband version
g8998-00020-1912200251
kernel version
4.4.210-gf13e65034114-ab6213703
Build Number
Rpp2.20227.009
Since your phone boots now. Simply wiping out everything should do the trick i guess.
Yeah. You can a factory reset. Your are currently on Android 11(R) preview ROM, it's still in the early phases and not suitable as a daily driver.
If all fails you can always flash a factory image, just remember to backup your data first.
Is this device a carrier device and if so, which carrier? You can only flash factory images with an unlocked bootloader so you need to figure that out first.
To figure out if you can unlock the bootloader you will first have to figure out if you have a Google or Verizon variant. Google variants can be unlocked. Verizon variants, for the most part, can't (although there is a thread where I believe someone may have done it on a Verizon variant). To figure out if you have a Google or Verizon, go here... https://www.imeipro.info/check_lg.html
Under "Buyer Name", if it says Google you're good to go. If it says Verizon or VZW, then you can't unlock the bootloader (unless the method in the thread I mentioned above actually works).
If you find you have a Google variant then via fastboot unlock the bootloader and fastboot flash the latest Q factory image.
https://9to5google.com/2020/04/23/h...d-11-dp1-to-android-10-on-google-pixel-video/
u need check ur phone can or not unlock bootloader.
if can... first thing u need to do is enable " oem unlock" in "development options"
when u unlock u can flash whatever firmware you want.
.
the problem u in android 11 . this very much bug.
Once you unlock, it'll wipe the phone.
You say you're running 11 DP1... At this point, I'd suggest signing up for the beta program and let the system update to I'd imagine the latest preview. Doing this should not wipe the phone.
From there you should have a working device and can back up what you want.
You should be given the option to unenroll on the beta website. Doing that, will downgrade the phone to the latest 10 release. it WILL also wipe the phone.
Go here. I see there's a link that could help you out.
google.com/android/beta
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.