Hi all,
My AT&T Atrix is running 4.5.91. I unrooted it to update to 4.5.141 OTA (I understood it was risky to do an OTA update while rooted).
After I finished downloading the update, I started installing but during installation, the package icon changed to a warning icon (with no error message) and the phone rebooted on 4.5.91 with a message saying the update failed
I think the package may have been corrupted in the download as it was interrupted. Although, I did try this 3 times (redownloading each time)
Any tips?
Thanks
You must have frozen and/or deleted some Blur apps as well as being rooted. Unless you have all the stock files from the firmware you are updating from, the install will fail.
I have unrooted the phone
However, I did use the "integrate system apps updates into ROM" option on TB.
I did not freeze anything
Will this work:
http://www.motorola.com/Support/US-EN/Atrix+Upgrade/Atrix-Gingerbread-Update
If not, what must I do?
Edit: Oh, and I also have AdFree installed and enabled. Should I revert?
mickeycohen said:
I have unrooted the phone
However, I did use the "integrate system apps updates into ROM" option on TB.
I did not freeze anything
Will this work:
http://www.motorola.com/Support/US-EN/Atrix+Upgrade/Atrix-Gingerbread-Update
If not, what must I do?
Edit: Oh, and I also have AdFree installed and enabled. Should I revert?
Click to expand...
Click to collapse
The sd card method will fail for you as well. Undo everything that required root access, including adfree...not sure if it will restore the modified files back to stock though, never used that app.
Exactly what happened to me. Successfully updated using Motorola Software Update
Hi
You have succeeded?
I am stuck for months trying to do this update...
It's absolutely frustrating...
I actually stopped trying. I got a RAZR a few weeks after I started this thread...
I might unlock the BL and install some ROMs to play with the Atrix but basically I don't use it anymore...
Anyway, I think the problem I was having was because I integrated updates into the ROM and I don't think it can be undone
Bootloader Unlocked?
If your bootloader is unlocked the update will most likely not work. Regardless, the link below has some useful information.
http://forum.xda-developers.com/showthread.php?t=1501532
My Nexus 9 is stock, un-rooted with an unlocked bootloader.
I have received the OTA update but when it reboots it gets part way through then shows "error" with and android on his back. I have downloaded the OTA file from AndroidPolice and tried flashing via adb sideload.
It attempts to verify the current system but then errors with the following message:
Package expects build fingerprint of google/volantis/flounder:5:/LRX21L/1546449:user/release-keys or google/volantis/flounder:5:/LRX21Q/1573789:user/release-keys; this device has google/volantis/flounder:L:/LFW73W/1491895:user/release-keys
Click to expand...
Click to collapse
Why have I got a different build?! Is there a different OTA that i need?
I have the same issue, any one any idea?
same here. tried factory reset just to eliminate didn't help
https://plus.google.com/110305043896789356373/posts/bHyo4UazRpH
As I have an unlocked bootloader i've just flashed the recovery from the factory image and then applied the OTA update (mostly to see if it would work, otherwise i'd have continued with factory image). It's booting up now. I guess Google will need to push a new OTA that updates from this version... a bit of a screw up though!
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.
I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
AstroDigital said:
I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
Click to expand...
Click to collapse
Install could have failed for a variety of reasons. If you are rooted, or have a custom kernel, or are unencrypted, of there is any modification to the system.
You can sideload the OTA, but really? That's as much work as fastboot flashing the system image.
So, if your bootloader is unlocked, I'd suggest that you just fastboot flash the individual .img files, extracted from the system image.
.... I did a manual install, I have not had much luck with OTAs
I've looked and tried what other people tried in threads, but:
Still getting "Error" on the flashing screen when doing the upgrade to 3.2.5.
Verified that it is unrooted, framework removed, ota updates re-enabled, safestrap is removed. Also factory reset and cleared caches. However whether I download the 3.2.5 upgrade file or I let the kindle download it, it will verify the file ok, start the upgrade, reboot into the regular upgrade/flashing screen, go a little ways on the progress bar, and then Error, and eventually reboot back into the regular OS.
So something else is causing it to hang up, is there anything I missed on getting it back in condition ready to take the 3.2.5 upgrade? ANy help appreciated> Thanks.
PaulieP said:
I've looked and tried what other people tried in threads, but:
Still getting "Error" on the flashing screen when doing the upgrade to 3.2.5.
Verified that it is unrooted, framework removed, ota updates re-enabled, safestrap is removed. Also factory reset and cleared caches. However whether I download the 3.2.5 upgrade file or I let the kindle download it, it will verify the file ok, start the upgrade, reboot into the regular upgrade/flashing screen, go a little ways on the progress bar, and then Error, and eventually reboot back into the regular OS.
So something else is causing it to hang up, is there anything I missed on getting it back in condition ready to take the 3.2.5 upgrade? ANy help appreciated> Thanks.
Click to expand...
Click to collapse
Why do you want to update to 3.2.5 anyway? Versions below 3.2.4 (i.e. 3.2.3.2 and lower) give you the chance to install TWRP recovery (a lot better than Safestrap) and to unlock the bootloader. Both would open the wonderland of HDX ROMs for you.
So I'd suggest to install TWRP (must remove Safestrap first!), update to 3.2.3.2 (can and should be done from TWRP, may be just update the bootloader to 3.2.3.2), unlock the bootloader and flash Nexus, CM11 or CM12 (note that CM12 is NOT Safestrap compatible, read the installation notes and requirements carefully!).
If in doubt, ask first, i.e. before you brick your HDX.