Database Users

[Q] Continue to fail updates 4.010.24

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!

[Q] {FIXED}Problem with new OTA update..??....software"failed to update" message....

[Q] {FIXED}Problem with new OTA update..??....software"failed to update" message....
I have downloaded the update and clicked update now three times, and keep getting a failed to update message??.....any ideas..??.....I am rooted, but have used Voodoo to unroot......edit (now have tried 7 times......gets to the little android, and about one third of the way through installing, I get the triangle of death)
EDIT: See response below.......

Same thing is happening to me, except the phone is useless, because if I pull the battery and let it start up normally, the auto-update shutdown happens, and the cycle starts all over again.
If it matters, I'm on a stock AT&T rom with an unlocked bootloader.

FINALLY!!!
Finally got it......went to Moto.....tried through manual update with sd card......didn't work.......tried Autoupdater......didn't work the first time......ran Autoupdater a second time and IT WORKED........try that......

Still not working for me, what do you mean by Autoupdater? I've tried the SD card method and the downloaded method.

I'm having the same problem. Stock rom, rooted. the only modding i've done is the webtop over hdmi hack. tried both the manual and auto update.

There are two options on Moto......one is sd card.....the other is Auto......
http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page

But Voodoo did not save root......gotta find another way to root......not unlocking bootloader......maybe Pete's OneClick will update to 2.3.6 soon......

i factory reset to see if it would fix the update. ew ew ew ew motoblur ew ew ew ew ew. kill it with fire. oh the things i do for updates....

iM having problems with ota updates... phone is on 2.3.4 unlocked bootloader, i do the ota update... ended up failed to boot 4starting rsd.. flashing the 2.3.4 unlocked sbf brings phone back to life... i USED THE MOTOROLA SOFTWARE UPDATERand phone is on offical 2.3.6 software and firmware. with locked bootloader.

I keep trying the auto updater but How do I make my phone stop the auto shutdown. I cant make it stay on for more than 30 seconds I do a battery pull reboot the phone boots up fine works then 30 seconds later shuts-down and tries to install the update again and it gives me the exclamation with the android. Never mind I did a factory reset via recovery phone works fine.

acondie13 said:
I'm having the same problem. Stock rom, rooted. the only modding i've done is the webtop over hdmi hack. tried both the manual and auto update.
Click to expand...
Click to collapse
THAT.
this is the same problem that's happened literally every time there has been a carrier update. search on how to restore webtop hack to stock and you'll be able to update after that.

rooted, locked bootloader, some hacks like HDMI webtop got fail to update massage
Those who don't know how to restore some hacks to stock, just go to http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
choose Automated upgrade, download Motorola_Software_Update.exe, follow the steps to update.
Good luck!

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] N7 4.4 update issues?

Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.

Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart

StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.

Yeah I have the latest OTA also, but I am still having the same issue!!

StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.

Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?

manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.

JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days

manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:

Motorola update , stuck at TWRP. Will tip for help!

Hi ,
to make a long story short, my phone is stuck at the TWRP screen, since today I installed the new Motorola update to Nougat. After researching the problem some threads suggested to delete the Motorola update file, but I cannot find this file or what its name is?
Any help appreciated and willing to tip to help me restore phone urgently as need it to go out.
Longer story:
My friend helped me root the phone in the first place because after about every 2 months of usage it would come to a crawl it was so slow. And he did warn me not to install updates, but I mistakenly thought that meant major updates not releases. So yesterday the first time I installed the update, the phone got stuck at TWRP. I couldnt find any way to revive the phone, so I went through the process of using Recovery bootloader to factory reset. Reinstalled all my apps, configured everything, which takes hours as i'm very particular about my setup. And then ran root checker which said "your phone is NOT rooted". So my friend had suggested once its backup and running to install the update as it would be ok. Well I did and it is isnt. It's stuck back at TWRP again.