So, I was finally offered the 1.8.3 update from the glorious AT&T, OTA. My Atrix is currently rooted on 1.5.7 with Gingerblur 2.5 installed, as well as the HUSPA radio mod. I went to download the 1.8.3 udpate with no problems. Here's where it gets interesting... when I went to install the update, my phone rebooted as expected, but when it came back up with the little android installation logo and the progress bar, after about 25% I get a spinning traingle with a exclamation point in it and the install freezes. I did a battery pull and tried the install again, but same results. Is anyone else experiencing this problem? Does it have anything to do with my phone being rooted? Any comments/suggestions will be appreciated.
wesglbrt said:
So, I was finally offered the 1.8.3 update from the glorious AT&T, OTA. My Atrix is currently rooted on 1.5.7 with Gingerblur 2.5 installed, as well as the HUSPA radio mod. I went to download the 1.8.3 udpate with no problems. Here's where it gets interesting... when I went to install the update, my phone rebooted as expected, but when it came back up with the little android installation logo and the progress bar, after about 25% I get a spinning traingle with a exclamation point in it and the install freezes. I did a battery pull and tried the install again, but same results. Is anyone else experiencing this problem? Does it have anything to do with my phone being rooted? Any comments/suggestions will be appreciated.
Click to expand...
Click to collapse
IIRC, you cannot install OTA updates while on GingerBlur as your OS is modified (root shouldn't matter, it is the fact that GB is DEODEXED). You will need to flash back to stock and update.
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
open /cache/recovery/last_log on your tablet use root explorer
ypu will know whats wrong
I'm in Melb too, and that particular update has failed to download about 5 times now, and when it finally downloaded, it came up with a message saying "update invalid" or something along those lines. I'm gonna wait til I get home to try and update again.
altering WPA_Supplicant file is something you would've done so your tab would connect to ad hoc networks. Must be something else.. did you alter any other files? I'm working on this same issue. frustrating as f*#%
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
acorsino said:
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
Click to expand...
Click to collapse
Same for me. Had to go back to stock recovery for the OTA update to work.
Mine failed the first time. I rebooted and it worked the second time.
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
mashilu said:
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
Click to expand...
Click to collapse
If you see the little bee fail screen, it is not the stock recovery, but still CWM.
mashilu said:
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
Click to expand...
Click to collapse
Hi .. try to do that...
the uploaded file helped and solved my issue..i'm now running Honeycomb 3.1
Solution posted by Bob here: (correct the link below "www")
w w w.androidtablets.net/forum/acer-iconia-tab-a500-forum/18444-update-failed-help.html
Here's the WPA_Supplicant from my A500, after the 3.1 update. Hope this works for you guys.
I'm not sure what the extension is for the A500, but I had to add .zip to be able to upload it. Try removing the .zip before using it. Also, remove the 'original'. I added that to keep it straight on my tablet.
Good Luck.
Bob
p.s: sorry i'm a newbie here and can't post link outside the forum at the moment..
just follow the steps described by Bob!
I did see that different logo, which I subsequently rebooted as I thought it's frozen again.
Interestingly, I tried to push for another system update, attempt no. 7, and now, it progresses and complete update!!! Woo hoo!
Thanks for all the help. I still don't know which one sorts what out though... Cheers!
Im running a 4g xoom with 3.2.2 with custom kernal and running great . Can anyone guide me in the right direction to turn of the annoying ota update
The thing that worked for me...just go ahead and click install. Your Xoom will reboot and try to install the update. It will then freeze. Hold Vol Up and Power to reboot the tablet. Update doesn't work but the notification is gone! The problem, if you turn off the tablet and reboot, the notification will pop back up. But, how often do you need to turn off the tablet?
The other option, install the new Tiamat 4G ROM.
I updated, Tab rebooted and all is good, I was worried that I would loose something but nothing went wrong.
Trying to update my phone to 4.2.1 via system update it download and then when it reboots and tries to install i get a green android with a red triangle saying error? my phone is rooted but nothing else! anyone else getting this?
I successfully rooted my phone and was about to delete the annoying OTA Update notification but my palm accidentally hit the install when it popped up again... and the my phone just immediately rebooted and it's in recovery mode trying to install the update. I removed the battery right away but every time I put it back in, it shows that Android mascot trying to install and update... I DO NOT WANT KITKAT!! How can I get out of that when booting up or am I doomed in having that install all the way through and I have to use ODIN to flash Jellybean??
boamuro said:
I successfully rooted my phone and was about to delete the annoying OTA Update notification but my palm accidentally hit the install when it popped up again... and the my phone just immediately rebooted and it's in recovery mode trying to install the update. I removed the battery right away but every time I put it back in, it shows that Android mascot trying to install and update... I DO NOT WANT KITKAT!! How can I get out of that when booting up or am I doomed in having that install all the way through and I have to use ODIN to flash Jellybean??
Click to expand...
Click to collapse
I just had the exact same thing happen. Wasn't paying attention when the update popped up. I immediately pulled my battery as well and everytime I try to boot the phone back up it tries to install the Kitkat update. I don't want to upgrade to KK either, I'm perfectly happy on Eclipse. Anyone have any suggestions as what we can do to fix this problem?