Database Users

OTA 2.2 update, problems.

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

OTA Update Fails

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.

Phone bricked after Orange UK Gingerbread OTA update?

Hi,
Ive already looked around the forum but cannot find an answer to my question.
I know my phone is not totally bricked, I understand there are probably ways of plugging it into a PC to force an update but i downloaded the OTA update that popped up on my phone last night. As I understand it is meant to update and keep all of your apps and saved data, which I chose to do instead of wiping anything with a manual update to save all the hassle.
The phone was rooted on froyo 2.2.2 orange uk rom but apart from that there were no other mods to the OS.
The phone came up with the "power off" message and now sticks on the black Motorola screen showing
"Failed to boot 2
starting rsd mode"
I can pull the battery out and the phone turns on for about 20 seconds, and I can use the OS in this time but then the "powering off" message comes back up
and it goes back to the error message on the splash screen.
Is there a way I can stop this OTA update from powering off my phone and getting stuck in this loop or do i have to wipe the phone and flash an sbf file?
Can you point me to the sbf file for the new orange gingerbread rom?
Thanks
ryan

Anyone?
When i turn phone on it works for about 20-30 seconds, before it restarts into the splash screen. It seems as if the phone is running some sort of script to continue with the upgrade but when it reboots it cant continue or something...
The OTA update didnt even start flashing, it just downloaded, then i clicked "install now" and it just rebooted to the error.
If i cant fix it easily, can I use RSDLite and an SBF file to go back to stock? Or can you only do this on an unlocked bootloader?
My bootloader is still stock. The only thing I did when I got the phone was root it so that I could install certain apps.
PLEASE HELP!

Link to Orange UK GB SBF is in Atrix 4G Android Dev forum in the Atrix Firmwares Superthread..page 25ish.
I RSDLited this SBF onto my Atrix (unlocked bootloader running Alien #4) with no problems.
This same route may be your only option...not sure about recovery of your apps etc..I have everything backed up via Blur, Google account and Titanium Pro, so no concern for me there.
FYI, this new rom seems to have little Orange bloat and runs great for me in stock form...just rooted...and battery life is very respectable.

After 4.3 update, phone reboots whenever i log in

The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?

Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update

sucinimad said:
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Click to expand...
Click to collapse
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.

deusfaux said:
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
Click to expand...
Click to collapse
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.

deusfaux said:
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
Click to expand...
Click to collapse
In the end, I went through almost the exact experience (including red LED). Running on stock 4.3 image now. Thanks.

my phone is reboot today.
there might be problem with rooted stock kernel?
there are someone has same problem?

Acuity said:
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
Click to expand...
Click to collapse
i got the same issue, look here: http://forum.xda-developers.com/showthread.php?t=2380546

I can't install lollipop.. Have I done something wrong?

Last month I got the update from Android 4.4.4 to Android 5.
I have had problems in the past updating an ASUS Transformer Pad 300 when the update made my device worse and ASUS stopped doing updates. This forced me to learn how to root my ASUS device and install a custom ROM.
Seeing as I got burned installing an OTA update I wanted to ROOT my Nexus 4 and back it up before completing the update to Lollipop. So I followed the instructions from Cynogen Mod Installer. The instructions sounded straight forward in that I followed the on-screen instructions. However all I managed to do was wipe my phone, and from what I can tell DID NOT install any Cynogen Mod Installer.
http://beta.download.cyanogenmod.org/install
Today I have now done two Factory Resets of my Phone to Android 4.4.4. I also get OTA update requests. Each time I try to do the update, I get a message saying that my phone needs to Reboot to continue the procedure.
The phone reboots, and I see the little android robot on his back with a progress bar. When the progress bar reaches the end, I get an error message simply saying 'error'. I then have to hold the power key till the phone shuts down. When I turn the phone on again, I never get any requests to update to Android 5.
Have I done something horribly wrong and that I will never be able to update my Nexus 4 phone?

Instead of doing the factory resets, have you tried flashing the stock images through fastboot? That might fix it.

lolcakes203 said:
Instead of doing the factory resets, have you tried flashing the stock images through fastboot? That might fix it.
Click to expand...
Click to collapse
How do I do that please?

http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Here is a great guide to return back to pure stock.