Database Users

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.

XXUAMDN or XXUAME2

Does anyone know which is newer, and what changed between the two?

I have XXUAME2, and I've updated my firmware through Kies. I don't remember what I had before. This one must be newer.
Haven't noticed any change, apart from the blue default background in the wallpapers is now a bit darker without the sun flare. I might've noticed a few very minor things in the settings, though I don't remember what they were.

Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.

StuartTheFish said:
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
Click to expand...
Click to collapse
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.

Tozenator said:
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Click to expand...
Click to collapse
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.

StuartTheFish said:
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
Click to expand...
Click to collapse
Interesting, very interesting. I might look into rooting one more time, then. Thanks!
Funny how you helped me instead of the other way around. Thanks again, I hope more people notice your thread and maybe you'll get your answer!

where is this new firmware xxuamdn, havent found anything about it..
im having camera, battery drain, slowness issuess still hope it fixes..
Sent from my GT-I9500 using xda app-developers app

I have none of those issues, but never did even on the older version. All I did was Google for galaxy s4 update and I found a download link for it along with Odin. But there's also XXUAME2 out there and I don't know which one I'd be better having. Unless the only difference is the radio depending on where in the world you are?

[Q] Lost root but not unlocked BL after .78 update. How can I root again?

I could really use some help here. Hang with me as I explain what I've done and what's happening.
About a month ago, I checked for OTA update. .78 showed up, but, before installing, I went online to see that the new update didn't jive with rooted and BL unlocked Razr Ms. So....I've basically been hitting "remind me later", twice a day, since then. So my alarm goes off this morning and, in my foggy eyed and foggy head state, I hit install update while trying to turn the alarm off.
Obviously, I lost root but BL is still unlocked. Thinking it would be easy to reroot, I uninstalled the superuser app that I got when I rooted with motochopper. Well I tried to reroot with no luck. I run the bat file and it gets here and progresses no further. *daemon started successfully*
When I try to boot into recovery I just get the android guy, on his back, with the red triangle over him. My recovery was TWRP 2.6, IIRC.
Any help would be greatly appreciated.

jabo052 said:
I could really use some help here. Hang with me as I explain what I've done and what's happening.
About a month ago, I checked for OTA update. .78 showed up, but, before installing, I went online to see that the new update didn't jive with rooted and BL unlocked Razr Ms. So....I've basically been hitting "remind me later", twice a day, since then. So my alarm goes off this morning and, in my foggy eyed and foggy head state, I hit install update while trying to turn the alarm off.
Obviously, I lost root but BL is still unlocked. Thinking it would be easy to reroot, I uninstalled the superuser app that I got when I rooted with motochopper. Well I tried to reroot with no luck. I run the bat file and it gets here and progresses no further. *daemon started successfully*
When I try to boot into recovery I just get the android guy, on his back, with the red triangle over him. My recovery was TWRP 2.6, IIRC.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
someone asked the same question you did (after yours): http://forum.xda-developers.com/showthread.php?t=2419648

[Q] Rooting MH8 kind of worked...but not quite. How come?

Hi,
I foolishly accepted an OTA update last night that took me from MGA to MH8 firmware. Of course I lost root, but thought ah well, I'll just re-root and that will be fine. Annoyingly, I flashed CF-Auto-Root as described for MH8, but it only seems to have partially worked. SuperSU seems to now be missing (even though I can see it's installed). I have tried to uninstall/reinstall, but to no avail. I ran the command recommended in adb shell (pm disable com.sec.knox.seandroid) and after a bunch of text flew past (which scared me), all that seemed to happen is that I lost root completely.
Strangely, Titanium Backup seems perfectly happy that I have root, but all other apps aren't really convinced.
So my question is, can I just flash back to MGA from MH8, or is a downgrade not possible? I've read a few bits about the bootloader being new and it being a one way deal, but I'm a bit sketchy on that.
Alternatively, can anyone suggest why the root hasn't taken properly or where I can get a pre-rooted MH8 rom that I can flash with Odin? The MGA one I flashed was a Djemby one, but I can't seem to see a MH8 one that I can do with Odin rather than a custom recovery. I might just be blind though!
Any help/advice gratefully accepted!

There was an easy solution to this in the end. For some reason, my supersu binary wasn't updated. I installed the free one and suddenly it appeared and recognised I had paid for the pro version. Suddenly everything works as expected.
Sent from my GT-I9505 using Tapatalk 4

monkeonman said:
There was an easy solution to this in the end. For some reason, my supersu binary wasn't updated. I installed the free one and suddenly it appeared and recognised I had paid for the pro version. Suddenly everything works as expected.
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
I 've had a similar porblem with the SuperSU, so you mean with the pro version it did work or the free one?

I already had the pro version, but that wasn't accessible after root. It was only once i installed the free version that it appeared again. It was odd though, because even though I installed the free version, it immediately recognised I had paid for pro and upgraded it.
Sent from my GT-I9505 using Tapatalk 4

[Q] Nexus 7 2013 Lollipop update, downloaded but no update.

Hi All,
On Tuesday i downloaded the OTA after getting the notification. The download completed but update paused because of low power. I plugged the Nexus into the mains and went to bed. In the morning i found that the 7 had not updated........any idea? My Nexus 5 updated no problem and i LIKE it.....A LOT!
John.

Are you rooted?

Same thing happened to my daughters 7. Update downloaded plugged in to let it charge up, came back and the update was gone, and tablet shows no system updates are available.

Similar happened to me. I got notification about update available. I downloaded the update successfully, confirmed to reboot and install the update but nothing happened after reboot. Update not installed. When I check for update now it shows that it's up to date... I'm running on completely stock ROMs only since beginning, installing OTA updates only as they come...
Sent from my Nexus 7 using XDA Premium 4 mobile app

ferro_sk said:
Similar happened to me. I got notification about update available. I downloaded the update successfully, confirmed to reboot and install the update but nothing happened after reboot. Update not installed. When I check for update now it shows that it's up to date... I'm running on completely stock ROMs only since beginning, installing OTA updates only as they come...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same thing happened to me.
100% stock unrooted and unmodified (SO's tablet), downloaded and rebooted and no L - boo

- Clearing the device cache might help. The OTA is usually stored there so that would delete any partial or full downloads, and might restart the whole process.
- You could always sideload the OTA from your computer. The option is in the stock recovery mentioned in the link above. Just Google how. And you don't need to be rooted for that.
- You might consider waiting for the next update. A lot of users are complaining about performance of 5.0, especially on 2012 model. Personally mine runs great. First couple of days had a bit of lag but now it's as smooth as it was on 4.4.4

Rooted Nexus 4 Lollipop Update
Hi All,
My nexus 4 is rooted & i just got the lollipop update. However, during installation of the same, i got a question, Fix Root, with a red color exclamation sign on android robot. As i didnt know what was going on, I selected no. It rebooted my phone & I am still on 4.4.4 Now there is no OTA available. I have tried clearing cache memory, still its showing, System is up date. Please help as i dont mind loosing my root privileges over lollipop update.
---------- Post added at 12:41 AM ---------- Previous post was at 12:17 AM ----------
Update:
I have got the download option back & the update is available. Hence, during installation what i am suppose to select for below message.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix