Related
As the title states, has anyone's 2013 n7 bricked after the 5.0.2 update when flashing a factory image instead of the OTA? Mine bricked after taking the 5.0.1 OTA, but i now have it back from Asus after repair and am wanting to flash the factory image to 5.0.2. However, if anyone has experienced bricking as a result of this (or 5.0.1 or 5.0) being flashed and not just the OTA, which we know is bricking devices, then I will stick with 4.4.4 for now.
Thanks
You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.
khaytsus said:
You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.
Click to expand...
Click to collapse
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.
Norcalz71 said:
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.
Click to expand...
Click to collapse
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.
graphdarnell said:
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.
Click to expand...
Click to collapse
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP
Norcalz71 said:
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP
Click to expand...
Click to collapse
Given previous experiences with Asus JB on another model, I'd avoid anything "official" like the plague, and wait till major bugs are swatted. Clearly, I'm not saying "LP Roms/factory images should be just fine." But I've been flashing custom roms based off LP, and nothing out of the ordinary has happened. They work fine. What I don't get is people would insist on flashing the crappy OTAs Asus has been putting out in the face of so much bricking.
Asus doesn't put out updates for the N7; Google does.
Telyx said:
Asus doesn't put out updates for the N7; Google does.
Click to expand...
Click to collapse
I don't see the difference. Just because Google funded and marketed the device doesn't make it less Asus. An Asus is an Asus is an Asus, whether you buy it at Staples or in China. I seriously doubt the firmwares are 100% (or 10% for that matter) Google unless one can prove to the world otherwise.
I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.
You're saying Asus makes aosp? No. Google makes the software for nexus devices.
Asus assembled the hardware. Google makes the software (aside from proprietary drivers, of which Asus made only audio and "sensors").
Asus has very little to do with the n7 aside from the fact that they put it together.
jshamlet said:
I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.
Click to expand...
Click to collapse
Mine will remain unlocked from now on. I took it from 4.4.2 back to 4.4.4 (since after repair it was back to original and wiped) via fastboot, and will probably wait awhile longer to update it via fastboot to 5.0.2. No more OTA for me though.
I have tried to update my chinese XT1635-03 to 7.1.1 with OTA through ADB sideload and unfortunately it is not working.
I have sucessfully flashed the phone with reteu latest firmware with April security patch (ADDISON_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) through fastboot.
But once I try to sideload 7.1.1 OTA (Blur_Version.26.1.22.addison.retail.en.US) the process terminates at 47% with notification that the package expects product name "addison" but actual value is "addison_retcn"
Is it possible to either change the product name or disable such check of product name? It seems to me, that at the moment there is no way to flash OTA and I need to wait for full 7.1.1 image.
Reading similar questions around, I have to ask. Why you people cannot wait couple of weeks to get OTA? Instead of risking to brick your device?
New update is not bringing revolutionary/awesome/amazing/mind blowing... new features. I understand if it's update to completely new Android version or that your device/region will not get update at all.
Sent from my XT1635-02 using Tapatalk
You have XT1635-03 and the update is for XT1635-02. So if you have a reteu phone you can really update over sideload without issues. And yes, I need android 7.1.1 and I wouldn't wait one day longer. I need app-shortcuts, because I had this on my old phone, too. There was android 7.1 since the first day. But if you don't have it before you can't miss it. So you can wait much easier For me it was important for other issues, too. For example Wifi problems and stability fixes and over 100 security fixes. Many reasons for the update
Edit: And one more reason for the update: To help google to get more than 0.6% for android 7.1 We should update all, otherwise android 7.1 will never get 1%
Everybody should help to get this 1% maybe next month. So update, just do it for the 1%, yes xD
:silly::good:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
The point is, how can you change the channel...
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
OK, makes sense for you but for many/most others is just matter of time.
I'm not blaming anyone. Do whatever you want with your phone, just be ready if something goes wrong
The surprise was a different phone name. Different channel is usually not a problem
freeman_g said:
The surprise was a different phone name. Different channel is usually not a problem
Click to expand...
Click to collapse
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
flashallthetime said:
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
Click to expand...
Click to collapse
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
allrightlite said:
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
Click to expand...
Click to collapse
I have no idea
flashallthetime said:
I have no idea
Click to expand...
Click to collapse
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
allrightlite said:
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
Click to expand...
Click to collapse
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
dandrumheller said:
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
Click to expand...
Click to collapse
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
allrightlite said:
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
Click to expand...
Click to collapse
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
dandrumheller said:
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
Click to expand...
Click to collapse
It feels not like a beta. It's more like a big bug fix with much patches. For example my Wifi is now stable as hell and never reconnections anymore. Hope it keeps stable, but looks very very good. I think this beta will be the final release in few months, or weeks? But it's much better than 7.0. And better than LOS14.1, which is not so stable (on my other phone). And I have no app crashes anymore. Gboard was crashing with 7.0 one time and few other apps like firewall. So, 7.1.1 is pure stable as hell and must have :laugh:
Afaik, it's not beta. It's soak. So, if test users reported as stable, it will be pushed to all as the final build. If not, Moto has to fixed and not all users around the world will be affected.
Regular and recommend way of releasing update.
Sent from my LG-V940n using Tapatalk
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
If you are on XT1635-03 with reteu frmware you will not receice any OTA. My experience told that you can't even sideload an update. So no worry about bricks.
Very often devices are hardbricked when you are downgrading bootloader but once I have hardbricked my Nexus 6 with OTA (sideloading it). Well, it was not full brick, but I can't load the system (only fastboot) and my bootloader was locked. Without system loaded you can't allow unlocking procedure so the first thing I do with new phone is unlocking.
allrightlite said:
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
Click to expand...
Click to collapse
I know the build is not a beta. I'm referring to the fact that once you leave the official upgrade path, taking any update is a scenario not tested by Moto. So you are testing for them. Maybe you win, maybe you brick.
It seems that the problem with "addison_retcn" may be fixed with editing build.prop but in this case systemless root is required (AFAIK there us no systemless root for Nougat)
Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/
We already know this
Bugz1 said:
We already know this
Click to expand...
Click to collapse
I knew about this since previous update and this April security patch really f**ked bad
Fair Warning ...
P.S data lost
Abish4i said:
Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/
Click to expand...
Click to collapse
This has already been fixed, updating to stock Android 10. The first release had the battery issue and was hard bricking the a70, samsung suspended the update and rolled out a new fixed android 10 update. Alls good now.
MarvinMod said:
This has already been fixed, updating to stock Android 10, samsung suspended.
Click to expand...
Click to collapse
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:
[/COLOR]
Abish4i said:
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:
Click to expand...
Click to collapse
Im saying, the issue with pcb is fixed. Try downloading the update now and flash. Fyi, you cant downgrade from 10 to 9 once you have updated to 10. Samsungs efuse will be triggered. It's been said that a device affected with the PCB bug is hardbricked, however, that is not entirely true.
MarvinMod said:
[/COLOR]
Im saying, the issue with pcb is fixed. however, that is not entirely true.
Click to expand...
Click to collapse
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downgrade without breaking efuse
Abish4i said:
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downloadgrade without breaking efuse
Click to expand...
Click to collapse
Efuse is popped during an update not a downgrade. Idk if ota pops it but i know updating with odin sure does and no, once the efuse is provisioned, there is no going back. If you or anyone else has found a way besides opening the device and making jumpers, please explain or provide links.
Device never went to 10 since the update with 10 has this error to ppl can still switch back to 9 hassle-free.
Thx for heads up!
Overall, Android 10 upgrade was a big disappointment for me, and pushed towards rooting it first, and then to installing LineageOS 17.1.
So, after rooting I disabled auto updates as I knew things can go bad.
But now I'm lucky LOS user!
I flashed my A705MN using Odin to get around the bootloop and it worked but now my wifi and bluetooth doesn't turn on. -_- I'm kinda new at this flashing business. How can I activate them both again?
MarvinMod said:
This has already been fixed, updating to stock Android 10. Alls good now.
Click to expand...
Click to collapse
Not good yet ;
I did some research with certified service centres this problem can't be fixed with software though it can be fixed with as a manual upgradation of PCB board is required
Ultrachamo said:
I flashed my A705MN using Odin to get around kinda new at this flashing business. How can I activate them both again?
Click to expand...
Click to collapse
If still error do following
Are you sure abt manufacturing unit place of origin is India it's fine ... Still if you used HOMECSC and it worked
you need to format it first thing in
If not manufactured in India Search for country origin specific file ... for odin flash
Why does this count as "development"?
DroidGTV said:
Why does this count as "development"?
Click to expand...
Click to collapse
Idk maybe it cuz the bug is related to PCB bridge code error in software which might be fixed with either downgrading FW ver or Hardware upgradation...
Hi guys, I just bought a brand new note 10+ N975W (canada version). I'm on stock firmware. It keep asking me to update. Shall I update? which version is best to keep the battery last as long as possible?
Also, can i downgrade to previous versions or stock if i dont like the upgraded firmware?
Yes update. It's probably just security updates at this point, so there would be no reason to go back. The Note 10 firmware is fairly mature by now.
chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.
Belimawr said:
chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.
Click to expand...
Click to collapse
my phone is still running on android 9.0.
aznboix said:
my phone is still running on android 9.0.
Click to expand...
Click to collapse
Since the phone is new. Before getting to far into configuration, run the update, then do a factory reset. It'll do a fresh install of Android 10 and any security updates.
That will give you a nice clean install you can then setup.
Sent from my SM-N976V using Tapatalk
You should always update. They are mostly Security Updates, these are for security reasons (Hence the name ). Yeah there are some system modifications and enhancements too but the main reason is to ensure the device is as secure as possible
Is there a custom firmware that works perfectly?
can i root my device?
can i flash to another firmware? Asia firmware for exemple
what are the apps that i can't miss on note 10+?
which firmware that has vietnamese language?
thanks
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.