Database Users

[Q] OTA update keeps failing to download

My wife got me a brand new A500 off ebay a couple of months ago for a Christmas gift(for me it's only three days old). So far I love it but it will not take the OTA update that it keeps bugging me about. The download starts fine but then stalls out mid download. I looked here http://forum.xda-developers.com/showthread.php?t=1113878 but did not see my current version there. Can anyone point me in the direction of the OTA I need to download and flash with recovery? My build is Acer_a500_1.145.09_com_gen1 I'm running 3.0.1. It looks like it's trying to download 4.010.11.
Further info:
According to the log the file name is Acer_A500_1.145.09_4.010.11_com_gen1_1311243587838_bd1ab95c.zip
I can't find that file anywhere on the net.

The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
If that's not the case, then you can just install the update manually. Download the update you want and put it on your external SDCard and then enter recovery (using power and volume). The recovery will install the update for you.

timmyDean said:
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
Click to expand...
Click to collapse
It said it was brand new. My wife would not buy something like this used. The weird thing is it knows it has an update and it starts to download and get's up to half way downloaded and then it just stops. It shows that it still is pulling data but the downloaded file size doesn't increase anymore after it stalls.
Ive been looking into rooting it and since I'm on 3.0.1 it appears Gingerbreak is all I need. The next question is what rom should I get and how do I go about installing it? I've never rooted droid before and most instructions on XDA are written for the experienced level and not the new guy. I'd like to stay fairly stock but rooted.
Sent from my A500 using Tapatalk

There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14

timmyDean said:
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
Click to expand...
Click to collapse
Just to make sure I'm getting it right: I go here http://forum.xda-developers.com/showthread.php?p=20680452 download that to my PC and follow the instructions contained within and I end up with a stock rooted 3.2.1? I don't need to download anything else right? A soft reset for this tab is pusing the little red button on the end by the USB port?
Sent from my A500 using Tapatalk

Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.

timmyDean said:
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
Click to expand...
Click to collapse
Sweet. You're a life saver. Thanks for translating it all to noob for me. Will I need to reinstall all of my apps and such afterwards?
Sent from my A500 using Tapatalk

Yes, the flashing tool makes it just like new, out of the box, but with root.

timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
OK that's not a big deal. The SD card will remain intact though right?
Sent from my A500 using Tapatalk

Jds method does work. But you can also trybthis.
http://forum.xda-developers.com/showthread.php?t=1410802
Simple easy no computer needed

timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
I tried your method and I get stuck at the serial number part. It says ADB server out of date. What do I do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Never mind. I got my steps out of order. I was clicking next before running test.cmd
Last edit: It appears to have worked. I'm back to the initial setup screens just like when I first got it.

[Q] What's that ... Developer Firmware???

Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Kroenen66 said:
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
Click to expand...
Click to collapse
Yes it would appear you have a developer Rom and I doubt it would be useful to anyone. Basically you have two options:
1) Send it back to Google for a replacement. (Could end up waiting a number of weeks)
2) Flash the Factory Image for the Nexus 10 which can be found at:
https://developers.google.com/android/nexus/images#mantaray
This will load the final release of JB which should be already on your device and you could be up and running in 15 mins.

dr9722 said:
Yes it would appear you have a developer Rom and I doubt it would be useful to anyone. Basically you have two options:
1) Send it back to Google for a replacement. (Could end up waiting a number of weeks)
2) Flash the Factory Image for the Nexus 10 which can be found at:
https://developers.google.com/android/nexus/images#mantaray
This will load the final release of JB which should be already on your device and you could be up and running in 15 mins.
Click to expand...
Click to collapse
If I flash the factory image .... I have restrictions? in comparison .....to take it back to Google for a replacement???
What is the better option?
When the flash is just as good .... how / with what do I flash it?

Kroenen66 said:
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
Click to expand...
Click to collapse
Kroenen66 said:
If I flash the factory image .... I have restrictions? in comparison .....to take it back to Google for a replacement???
What is the better option?
When the flash is just as good .... how / with what do I flash it?
Click to expand...
Click to collapse
if you flash the factory image you will then be the same as everyone else, no restrictions whatsoever.
Follow this guide:
http://androidtobe.blogspot.co.uk/2011/12/galaxy-nexus-installing-ics-402-from.html
That is for the Galaxy Nexus however the same commands still apply. Just ensure you download the correct Factory Image and change the file name where appropriate.

dr9722 said:
if you flash the factory image you will then be the same as everyone else, no restrictions whatsoever.
Follow this guide:
http://androidtobe.blogspot.co.uk/2011/12/galaxy-nexus-installing-ics-402-from.html
That is for the Galaxy Nexus however the same commands still apply. Just ensure you download the correct Factory Image and change the file name where appropriate.
Click to expand...
Click to collapse
The Factory Image is no Problem:
https://developers.google.com/android/nexus/images
If I make an error in an entry, I can restart the process again or is my Nexus 10 dead/Bricked/paperweight?

Isn't there any solution to "reset" to normal state without going to unlock process and flashing all partitions manually ?
what is the normal way to get back to org. Image when "normal Nexus 10" devices are out of order ?
We urgently need root and CWM on this tablet ...8)

fogbav said:
Isn't there any solution to "reset" to normal state without going to unlock process and flashing all partitions manually ?
what is the normal way to get back to org. Image when "normal Nexus 10" devices are out of order ?
We urgently need root and CWM on this tablet ...8)
Click to expand...
Click to collapse
The normal way is to restore the device using the correct nexus factory image for your device then executing the flash all script included with the factory image. This script will flash all the necessary partitions for you and reset your device to factory stock. This method doesn't require unlocking the bootloader and doesn't require root.
Sent from my SCH-I535 using xda premium

shimp208 said:
The normal way is to restore the device using the correct nexus factory image for your device then executing the flash all script included with the factory image. This script will flash all the necessary partitions for you and reset your device to factory stock. This method doesn't require unlocking the bootloader and doesn't require root.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So - can you give us the link to the "right" image - and write 2-3 lines how to flash ? Volume up/down Power to stock recovery etc. Copy image to where ... etc ... this would be wonderful ... thank you so much ...

Nexus 10 Factory Image:
https://developers.google.com/android/nexus/images#mantarayjop40c
You also need to set up the Android SDK, especially adb and fastboot.
Reboot to bootloader:
adb reboot-bootloader
When in fastboot mode, you can start flashing the factory images.
flash-all.bat does all the work for you.
But make sure, adb AND fastboot is working inside CMD!

Thank you very much ... we will give it a try ... even if i don't know how many user get a developer version of the Nexus 10 ... this order was normaly done ... and we were some kind of surprised when the tab was started ...8)
Oh Google .. something went realy wrong this time ... 8)

Interesting that you're the second person to have this debug ROM installed and both of you are in Germany.

Me too, same here, living in Germany.

Unable to install 4.2.2 upodate

I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using xda app-developers app

Here is the error I am getting.
sent from my nexus 4 using google mind control

The OTA installer checks every single file it intends to patch before anything happens.
If a single file that is checked has been changed by even one byte, not one patch operation will occur.
The message you are getting means you did something to change or remove that file compared to how it was in the stock ROM.
Note that the installer halts on the first error of this type; there could be zero or many more of these errors awaiting you.
In short, OTAs are not meant for patching random non-Stock ROMs.

I installed beats from play store. Gutted. Just backing up all my data and gonna factory reset and try again
sent from my nexus 4 using google mind control

R: Unable to install 4.2.2 upodate
I had error 7 with TWRP recovery. Then I installed clockworkmod and it worked.
Nexus 7 3G - Tapatalk

Androll79 said:
I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phoneView attachment 1728828
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i have the same problem.but i flash stock recovery with WugFresh toolkit and wait until OTA update notification.and you will get your android running 4.2.2 version.

Odp: Unable to install 4.2.2 upodate
Guys, guys, guys. You need STOCK recovery for official updates.
Sent from my BMW E34 using XDA App

I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?

There is modified OTA floating somewhere that skips check, worked for me since it reported that GoogleCalendar.apk was different than it should be....

Folks,
You need to stare at the actual error message.
If the failed assert() is complaining about a file (e.g. see the OP's 2nd image attachment) then THAT FILE IS THE PROBLEM. It means that it was altered or removed by a root-privileged operator from the way it was in the stock ROM.
If the failed assert is complaining about a build number, then it is possible that using a different recovery will allow the OTA to succeed.
So you have a couple of choices:
A) Go and find the stock version of the file and put it back into your ROM (with the correct file ownership and permission modes) and repeat the OTA install. Seems like a dumb idea though, as the installer stops on the first error encountered - you will need to keep repeating this process until you have restored all changed files. Could be only one file, could be a few, could be many. Note also that this applies to the boot image, too. Got a custom kernel? You'll need to put the stock boot image back in place, too.
B) Back up your apps using TiB or Carbon. While you are at it, take a nandroid backup too. Install the Factory 4.2.2 ROM, reinstall your fave custom recovery, and root the factory ROM. Boot it up, enter your Google creds, restore your apps & data (Carbon or TiB). Yep, you are gonna have to redo your homescreens. Big deal; that's something you would do anyway when hopping between ROMs (unless you have this covered already by using a non-stock Home/Launcher app which has its' own backup/restore capability)
C) Just wait a little bit - your ROM Dev will probably release a version based on 4.2.2. At that time you can do some stupid thing like overflashing the replacement ROM without wiping.
Unless you know exactly what you are doing, running a modified OTA with *all checks* suppressed is a seriously brain-dead idea. (Removing only the build version check should allow alternate recovery use - but for goodness sake, the OTA nukes the recovery anyway, so what's the big deal about putting the 4.2.1 stock recovery back in place ahead of the OTA?)
Look, running the Stock OTA is going to remove your recovery and very likely disable your root. You are going to need to put your recovery back and re-root anyway. Doing things the right way is barely more effort than what you are going to need to do the crufty way.
good luck

5.0.2 - Experience and Discussion

Thought it would be good to have a thread dedicated to 5.0.2, instead of sifting through the 5.1.x Rolling Out and Stock OTA threads.
Got the prompt and updated this morning. Took about 10 minutes -- 3-4 minutes to install the updat and then a good 6-7 to go through app optimization (for 120+ apps).
Haven't had a chance to put it through its paces yet, but interested in what others experiences are. Improvement? Same old?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Screen flicker possibly gone? Was pretty bad before on mine, haven't had it since update now.

This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.

b1bub4bu said:
This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.
Click to expand...
Click to collapse
You basically have two choices:
1) Flash the stock 5.0.1 system.img (this will install stock recovery) and boot.img, then vendor. Img then take the OTA.
2) Wait until Google posts the factory image.

Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
and if you have TWRP, then also recovery.img
once all these are stock, then you can take the OTA.
After the OTA, you can either reflash TWRP, or just simply fastboot boot it, then apply the latest SuperSU zip from chainfire's web site, and you'll be back to stock and rooted.

Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.

Ive tried the ota 3 times now and every time it 'errors' in recovery while flashing, I'm flabber gasted this is how Google now treats its nexus customers.

Ok I'm going to update my vendor
if any one wants it just tell me

Something else ... if you attempt the OTA once, you're done ... you can't re-attempt it unless you reflash back to original 5.0.1 stock.
It checks System first, and updates it ...
Then it checks Vendor, and updates it ...
Then it checks the boot image, and updates it.
So you you fail the vendor test, it's already updated System, and it won't run again.
You have to reflash system.img, vendor.img, AND boot.img before you can try again.
A much smarter method would have put the three verification steps one after the other, but obviously Google did not write the script that way.

Roxas598 said:
Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.
Click to expand...
Click to collapse
I think it's just some bug fixes. This is the only Nexus not moved to 5.1.1 by now, it's also the only Nexus using the K1 chipset. Not sure if the two are related, but it seems reasonable that they are running into some nVidia issues. 5.1.1 isn't out for the Shield tablet either.

ok guys updated to 5.0.2 just to get the vendor.img. it was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79

_litz said:
Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
.
Click to expand...
Click to collapse
I appreciate this. Coming from Nexus 6, vendor.img doesn't exist.
And on Nexus 6 when flashing the stock system.img it checks recovery and if not stock will automatically flash recovery.img. Is Nexus 9 the same?

When will my Nexus 9 LTE Model get this?

USBhost said:
ok guys updating to 5.0.2 just to get the vendor.img was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79
Click to expand...
Click to collapse
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...

stadicon said:
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...
Click to expand...
Click to collapse
I was going to
But got lazy

The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?

stadicon said:
The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?
Click to expand...
Click to collapse
I know man I'm crying inside

Ok so I got my ota update and downloaded it. Now my Nexus 9 keeps trying to come on,then saying android updating apps, then shutting off and restarting , and then repeats the same thing ! I never rooted or flashed anything ! Its completely stock ! WTH ! Help !!!!!!!

Update showed up when I turned mine on, ended up bricking my device.
Would show the spinning balls and nothing else, tried wiping cache, factory reset and still ended up at the spinning balls. Google sent me a new one, but I really wish I could just return the stupid thing.
I'll never buy another "premium" Nexus tablet again, the only way I buy another is if they give us another Nexus 7 like device.

I'm doing a factory reset .It seems it still on android deleting screen for 10 min already. Is it frozen ??

Phone crashes on boot - even flashed new stock rom

I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk

chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Sounds like you didn't factory reset your device. Before you factory reset, I recommend flashing TWRP recovery, mount your phone in recovery so you can back up important files to your PC if required.
After you've backed-up your files
Reboot (yes reboot, so switch your device off first) into the recovery menu (hold vol up + home + power), then select wipe data. This will wipe all data from your phone.

chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Where you cumming frop lolipop rom and flashed marshmallow or nougat rom ? If yes have you tick bootloader update in odin ? Rom will never boot without this update ! Try this if the previous good advice from Saber didn't help .

Everything is wiped. This is what happens when booting. Lines going across the screen. What originally happened was the person I got it from he had tried to do a update and the phone turned off. So I just flashed stock firmware but still get these lines.. Something is corrupted?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G900I using Tapatalk

When it boots in everything crashes in setup, get the error message unfortunately has stopped
Sent from my SM-G900I using Tapatalk

Looks like your phone needs a new main logic board because of defective memory.

chainzy said:
When it boots in everything crashes in setup, get the error message unfortunately has stopped
Click to expand...
Click to collapse
Here's my two cents if you've done what @Saber and @1981sebas suggested and still had no luck.
First, make sure the stock you've flashed is the latest MM XSA version to ensure you have the latest bootloader and modem. You can get it from sammobile or updato. It may take a couple of attempts so don't panic if it doesn't stick first time.
If it's still not right, hunt up the PIT files for your device and repartition it. Make sure you get legit files that others have used and had success with. You don't want to flash the wrong PIT. Then try flashing stock again.
Incidentally, have you tried flashing a solid custom ROM like RR or Cosmic? Maybe it's just an issue with your stock file being a bit corrupt if you haven't checked the md5 and any intact ROM will work fine.
My last option would be to try KIES because I personally find it iffy but others have had success with the recover phone option or whatever it's called. If you have KIES installed, just make sure it's disabled when you're using Odin and vice versa.
If none of this works, it may be a hardware issue. Good luck.
Sent from my Samsung SM-G900I using XDA Labs

I have tried a pit file I have but it didn't seem to do anything with that and re partition checked. I have tried several stock roms. Even tried the firmware with kies and still the same thing happens. Custom rom does the same.. The lines only come up on the screen when its booting.. They never come up in recovery or anything like that
Sent from my SM-G900I using Tapatalk

Dirty Flasher said:
hunt up the PIT files for your device and repartition it
Click to expand...
Click to collapse
That may be the case.
I'd try to download the latest "low_ship" factory firmware via Samfirm.
It contains a proper pit file in the CSC so it's necessary simply to flash it via Odin to repartition the device and clean everything on it.