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.

Update this AM in US, but...

Took an OTA update this AM in the US, but nothing seemed to change. Switched back to stock recovery, took update, downloaded, installed (no errors), rebooted, message said somethings about a Pre-Install APK, then nothing. Tablet info says I am now up to date, but nothing else seems to have changed.
I'm still on custom kernel (thor's), still on 3.1. I forget the GEN info, but I don't think that changed either.
Was this a pre-update update?

I got the update too.
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1

Ditto. Used stock recovery and unroot to get it to install. It's Gen 2.
Sent from my ADR6300 using XDA App

Same here, updated with no errors. Didn't lose root and it still says 3.1
With the update to 3.1 they sent out a smaller update a few days earlier. This one may be the same thing.

It's just a small update, about less than 20MB download. But I have no idea what's been changed.

GShyneDM said:
I got the update too.Same thing happaned to me
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Click to expand...
Click to collapse
Same thing happened to me...

System Update
System Update 4.010.13
(14.49MB).
A new system update is available for your device. A network connection is required to download and update your device. You may incur additional charges from your service provider. Thank you for not replacing me with the HP TouchPad.
Click to expand...
Click to collapse
i'm gonna hold off on installing this until i know more of what its all about...

I uploaded the zip in development, I don't think I'm gonna install either...

I also installed the 14MB update today. The tablet was rooted, but otherwise stock. After the update the tablet remains rooted. I have experienced no other issues.
Cheers,
A

I had the same experience as above. So far no issues.

This actually made me worried about the possibility of us to get an update to 3.2 on 8/25. Otherwise, they should just pass this incremental.

[Q] Can't boot after failed update

New stock A500 just out of the box this morning. Booted fine after the recommended 4 hour charge, running 3.0.1. Took the OTA update at the popup and rebooted fine. Checked in system and saw another update was available, downloaded and let it reboot, progress indicater went almost to end and failed. Tab won't boot now, shows status items and clock in lower right and small icon in upper left corner with 2 pulleys labeled "Android System", nothing happens when touching anything or pressing buttons. I've tried the reset button, cleared cache and data, have tried downloading several "update.zip" files and putting them on the SD card then rebooting into recovery. The updates start to install then I get a yellow triangle. I'm sure that there is a solution to this but I couldn't find it!
Thanks in advance,
Bob
EDIT: in addition to not booting since the failed update I have found that the tablet is no longer charging now too. Looks like this thing is going back to the store!

rlt9999 said:
New stock A500 just out of the box this morning. Booted fine after the recommended 4 hour charge, running 3.0.1. Took the OTA update at the popup and rebooted fine. Checked in system and saw another update was available, downloaded and let it reboot, progress indicater went almost to end and failed. Tab won't boot now, shows status items and clock in lower right and small icon in upper left corner with 2 pulleys labeled "Android System", nothing happens when touching anything or pressing buttons. I've tried the reset button, cleared cache and data, have tried downloading several "update.zip" files and putting them on the SD card then rebooting into recovery. The updates start to install then I get a yellow triangle. I'm sure that there is a solution to this but I couldn't find it!
Thanks in advance,
Bob
EDIT: in addition to not booting since the failed update I have found that the tablet is no longer charging now too. Looks like this thing is going back to the store!
Click to expand...
Click to collapse
You most likely could put it into fastboot mode and flash it to fix your problem. BUT I WOULD NOT mess with it if it is brand new and you've done nothing to it.
TAKE IT BACK AND GET A NEW ONE

Thanks for the reply, please tell me more about this fastboot option.I have another 13 days to return it to the store so I don't have anything to lose! All of the stores in the area are out of the a500 right now.
Sent from my DROIDX using XDA App

If you start playing around fastboot and flashing you will void your warranty. Take it back while you can and you can honestly tell them that you did nothing to it.

Yeah, I see that the warranty could be an issue later if I did get this tab running now. I did an online chat with Acer support this evening and they indicated to me that they believe the problem to be a hardware failure, they wanted me to send it in but I told them that it's going back Walmart and they can send it back. Thanks again for your help and advice.
Best regards,
Bob

[Q] Blu Kuban updater issues

Hey I'm running the Blu Kuban 1.0.0.2 ROM on my Sprint Galaxy S4, I went straight from MDL ---> Blu Kuban after completely wiping my phone as instructed, everything seems to be working fine except there's one small problem, when I go into the updater to try mods or add-ons, the package will download and ask me to restart so it can flash it automatically, it reboots into recovery and it starts to load but a few seconds later an error along the lines of 'path not found' shows up (I honestly can't read it exactly, all the text disappears from the screen a moment after the error and I'm left with a blank screen save for the android symbol and a triangle with an "!" hovering over it) the phone reboots itself after a while and functions normally, but whatever I was trying to install won't work. I figure I could just flash the packages manually but I think it'd be really great if I could use the automatic updater, I've searched high and low but as far as I can tell this is the first time anyone has asked about this problem.
Any ideas? I'd appreciate any help.

Supahx said:
Hey I'm running the Blu Kuban 1.0.0.2 ROM on my Sprint Galaxy S4, I went straight from MDL ---> Blu Kuban after completely wiping my phone as instructed, everything seems to be working fine except there's one small problem, when I go into the updater to try mods or add-ons, the package will download and ask me to restart so it can flash it automatically, it reboots into recovery and it starts to load but a few seconds later an error along the lines of 'path not found' shows up (I honestly can't read it exactly, all the text disappears from the screen a moment after the error and I'm left with a blank screen save for the android symbol and a triangle with an "!" hovering over it) the phone reboots itself after a while and functions normally, but whatever I was trying to install won't work. I figure I could just flash the packages manually but I think it'd be really great if I could use the automatic updater, I've searched high and low but as far as I can tell this is the first time anyone has asked about this problem.
Any ideas? I'd appreciate any help.
Click to expand...
Click to collapse
The reboot into recovery thing doesn't work for me either, although I don't get an error like you stated. It could be that your TWRP version is different than what they programmed Kuban Updater to work with... I dunno..
What I do is just download the mod, then manually reboot into recovery and install it myself using TWRP. All mods I've done that way have worked perfectly.

Cytality said:
The reboot into recovery thing doesn't work for me either, although I don't get an error like you stated. It could be that your TWRP version is different than what they programmed Kuban Updater to work with... I dunno..
What I do is just download the mod, then manually reboot into recovery and install it myself using TWRP. All mods I've done that way have worked perfectly.
Click to expand...
Click to collapse
Ah I see. I figured that would work but I just wanted to check, thanks for the quick reply

Supahx said:
Hey I'm running the Blu Kuban 1.0.0.2 ROM on my Sprint Galaxy S4, I went straight from MDL ---> Blu Kuban after completely wiping my phone as instructed, everything seems to be working fine except there's one small problem, when I go into the updater to try mods or add-ons, the package will download and ask me to restart so it can flash it automatically, it reboots into recovery and it starts to load but a few seconds later an error along the lines of 'path not found' shows up (I honestly can't read it exactly, all the text disappears from the screen a moment after the error and I'm left with a blank screen save for the android symbol and a triangle with an "!" hovering over it) the phone reboots itself after a while and functions normally, but whatever I was trying to install won't work. I figure I could just flash the packages manually but I think it'd be really great if I could use the automatic updater, I've searched high and low but as far as I can tell this is the first time anyone has asked about this problem.
Any ideas? I'd appreciate any help.
Click to expand...
Click to collapse
I had a similar problem.. I am running Rom manager to add zip files and once it reboots into the flash part I just manually find the zip it is in the 0/kubandownload/(whatever your zip file name is) and install is that way. Idk if that is what you need to know but hope it helps somewhat.

Error when installing update (JSS15Q?)

I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).

Godders11 said:
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Click to expand...
Click to collapse
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268

Many thanks, I'll give that a try.

sfhub said:
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Click to expand...
Click to collapse
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up

doggie123 said:
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
Click to expand...
Click to collapse
Hmm, I wasn't expecting that to happen, just expecting some file corruption to be overwritten, but it looks like you potentially had some bad sectors in the eMMC as well that got blocked out automatically by the erase.
This reminds me of the eMMC problem we had on Samsung where they changed wipe data to do a secure erase and that triggered an eMMC bug that left people with megabytes of unusable sectors.
If I were you, I would only run my system using a JSS15Q kernel because that has the fixes for the type of issue your unit seems susceptible to.
http://forum.xda-developers.com/showthread.php?p=44954087#post44954087