I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
jaredkent said:
I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
Click to expand...
Click to collapse
You can not update a rooted phone. Go to my post on updating 2.2 made easy and you canupdate to 2.2 and reroot the phone. This is the OTA update.
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Either take it to Verizon for them to push it onto the phone or use one of the methods here.
fygar66 said:
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/showthread.php?t=771178
Hello all,
I am usually a reader of this forum, first time post. I have done a search on this but I can't get it to install.
My current phone is running Froyo 2.2.1 system version 2.3.340. I have rooted it with the Z4mod root version 1.3.0.
Now, when I saw the update come down I uninstalled all my root applications and removed my root from my phone. It downloaded in no time flat. About 11 minutes yesterday morning at 9:49AM. (first attempt) And then I started the install and it shut down correctly and turned back on. When it turned back on it did what it was supposed to, had the unbox with android icon. The load bar gets to about 35% then the unbox changes to the triangle with the ! in the middle. Then it boots up Froyo and states the install failed. I attempted about 5 more times then said lets see what verizon says. This was probably the worst thing to do cause they did jack. The store I went to had 25 bricked droid X's yesterday. I was the only one to just have it fail and Froyo to work correctly. To quickly shorten this story they refused to assist in installing Gingerbread.
Any Ideas on getting it installed?
Try wiping data through stock recovery and if that doesn't work, you could try an SBF
Thank you for info. I ended up SBF'ing the phone. Says I need to re-activate the phone because there is a blue triangle next to the signal bars.
I know this is probably a repeated question but how do i re-activate the phone. Do I need to take it to Verizon?!
NVM, figured it out.
same thing happened to me. however i did not remove my z4root on froyo. install failed. did not try sbf, was hoping i wouldn't have to.
biggest reason ive found thus far amongst several different threads/ and friends with droids, root really didnt have much to do with it, as long as you were unrooted again the update went well, bloatware seemed to be the issue. myself i had uninstalled a lot of dumb memory eating stuff while i was on froyo such as the nfl and nfs games, blockbuster app so on, when i pulled the update originally it didnt detect that so it fubared me on getting the ota update. sbf the way to go, im so in love with my DX for being idiot proof atm i could dance lol
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.
I just purchased the A500 and have successfully updated 7.014.01 and then when I try and update to 7.014.02 I get Update Failed message. Anyone have any ideas as to how to fix it? Tech Support recommends that I send it back, but it will take 2-3 weeks and it will be a royal pain and will be my last resort.
sonjamin said:
I just purchased the A500 and have successfully updated 7.014.01 and then when I try and update to 7.014.02 I get Update Failed message. Anyone have any ideas as to how to fix it? Tech Support recommends that I send it back, but it will take 2-3 weeks and it will be a royal pain and will be my last resort.
Click to expand...
Click to collapse
I'll assume this is the 3.2.1 update as it usually comes in 2 update files.
I'll guess your 2nd update download was corrupted somehow. Probably a good thing, as some people had bricked tab's as a result of a failed update.
If your tab runs fine, don't worry about it, and ignore the update. They'll probably just give you another tab, and you'll go through the same thing again.
Not really a whole lot in the 3.2.1 update anyhow. Only thing I noticed, is a slight difference in screen sensitivity and just a touch smoother in the app drawer. Other than that, no other real performance gains.
In a few months, they'll push the ICS update. So it will all be moot.
But, if you really want to do this small update, you'll have to root, install CWM recovery, then flash a rooted update manually. I think TimmyDean posted these awhile back, but not sure.
Or, you can just flash a 3.2.1 custom rom.
But if your tab runs ok, and you don;t want to come to the dark side, then forget about it and wait for ICS.
Hi guys, so i recieved the OTA a few hours back and it required me to have more battery life in order to continue with it.
I was charging it and realised that it would allow to me to continue as long as it was charging, so i continued with the operation.
It rebooted my nexus (everything stock, rooted using mskips all in one root) and then required a confirmation to continue. in my excitement i pressed power instead of vloume down (in order to scroll down to yes). i thought that i should just rather reboot my nexus and start the whole process again, but now it doesnt show that there is a update available, system update says my system is uptodate but i am still running 4.1.1
does anyone know how long it will take for OTA to come through again? or how i can "induce" it?
I would just flash the update manually. Check out links to download from Google site.
Rootbrain
yeah i guess, i was gonna do so anyway by monday if i hadnt gotten the OTA by then XD still would prefer OTA though....