I bought this tablet just a few weeks ago and there have been 2 new ota updates out. every few minutes it pops up and tells me there is a new update ready to install. It downloads, verifies, then reboots and trying to install gets about 1/3 of the way though and ends up with the red exclamation mark over the dead android. This tablet is completly stock i have not moddifed anythng since i have gotten it. I even downloaded the newest rom and tried to do it manually and still nothing. Im stumped. Someone plz send some help my way. My current version is 9.4.2.14 US
Related
ok, so a month or two ago I rooted my Motorola Atrix so I could install Gingerblur which went well at first. It was working great for me and then I noticed that once and a while i would look at my hone and see an exclamation point and an android icon..I would have to pop the batter out and put it back in to restart...what I think happened is that my phone tried installing an automatic update which failed maybe due to my hacked phone not being compatible...bc after awhile I would notice my phone installing an update and then automatically rebooting to the error screen.
I tried installing GreyBlur the other day..and it didn't work well..so I flashed back to 1.5.6..but now I don't know how to upgrade to 1.8.3..when I scan for a system update it says that my phone is up to date..how can I update to the latest firmware and how come my phone isn't automatically installing it? Have I lost my opportunity to do this since to all the hacking I've done to my phone? or am I missing something? please help =(
Have you tried downloading it from the Motorola website? You should be able to just follow the directions on there to update it.
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=9098bc50a569f210VgnVCM10000081bbb00aRCRD
I used the "second method" and just let the Moto installer do it's thing. It will take some time and look like it may be freezing occasionally, but just let it go. It should work.
Hope this helps.
-Doogs™
I'm updating right now through the second method. I'm surprised I didn't find that sooner..I should of just went to the website to begin with..but I searched google and couldn't find any information on how to download it without going through an automated update.
I was also wondering if I should do a factory reset after updating
I have a 80 G9 (16GB) . It came with 3.2.79, I updated to 3.2.80 when it came out.
I successfully rooted 3.2.80 using information from this site.
This weekend I tried to update to the new 4.0.4. The update seemed to "hang", and I ended up forcing a power-off.
I subsequently used the recovery menu to do a full system format, and then tried to reinstall the 4.0.4 firmware - I've tried this a few times and each time it *seems* to be successful. After copying the AOS file to the device over USB, and selecting "ok", it says to leave the USB connected, a progress bar winds its way across the bottom of the screen, and then it reboots.
However, each time when it tries to boot, it just sits at the animated boot logo and never proceeds further. I've even tried letting it sit overnight - when I checked it in the morning after allowing it 6+ hours, it was STILL just sitting there rolling that bright bar across the "ARCHOS" logo..
I've tried to go back to 3.2.80, it gives an "update failed" on that every time I try.
I did the "remove developer edition" in the recovery menu, thinking perhaps the official firmware was balking on a 'rooted' device. Reformat, recopy AOS file, reboot, still no cigar..
I tried downloading the AOS file again, no luck..
Am I now the not-so-proud owner of a flat shiny brick? Is there some other procedure I can try? Has anyone else experienced this?
ANY advice or suggestions will be greatly appreciated.
If anyone needs more details or other info just let me know.
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
gen_scheisskopf said:
1. Download update .aos again (just to be sure)
2. Boot to recovery
3. Select Reset Android option
4. Install update
I hope this helps
Click to expand...
Click to collapse
I've already done 2,3,4 several times. I managed to get a hold of someone at Archos that said that the file gets validated when it goes to update, and I'd get an error if it was corrupt. It doesnt give me an error there, it accepts the file.
As I'm currently on a slow hotel Internet connection, does anyone have an md5sum or sha1sum of their ICS .aos file I can use to validate mine against? (Annoying that Archos doesnt include a hash on their site)
Update .aos file is digitally signed (this also includes checksums of contents). If signature check fails recovery will not flash it.
My guess is that you'll have to give tablet to service unfortunately
tapatalked from Desire
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Megadave123 said:
In case anyone cares, I did in fact end up sending it back, and they sent me a replacement.
The replacement had ICS on it, and has in fact since OTA's another update without any problem.
Click to expand...
Click to collapse
I cant believe you got through to support. I have been trying for the best part of 3 months and got no reply. I am new to XDA since I recently got a HTC Sensation. Saw that we have this section here for Archos G9s. Got my ''broken'' one out of storage and rooted and flashed it with a custom ROM. And it works again. Surprised since I had the exact same issue you got but I was not rooted when updating.
Stuck in "loop" after OTA 2.3.5 update on rooted Photon. Any way to get out of this?
Just curious if anyone knows any trick to get out of this loop.
I've got a rooted photon with 2.3.4, and I've been getting the notification to update to 2.3.5 from Sprint.
The message states that "a new update is available for your phone", and I've just been clicking the "install later" option because I know it doesn't work if my phone is rooted and I have a custom boot loader.
So I think this morning when my alarm was buzzing to wake me up the software update screen popped up and I accidentally clicked "Install now" when I was trying to snooze the alarm.
It rebooted into my bootloader, says it's trying to apply the update, and then says that it failed.
When I reboot the phone, it boots up like everything is normal, I get to my regular homescreen and then it realizes that the update didn't apply so it restarts immediately into bootloader, and the update fails all over again.
Does anyone know of any way to get out of this loop? Like, there has to be some flag flipped in the main system that's telling it that it needs to reboot to apply the OTA update. Is there a way to turn this flag off so I can keep using my phone like it was?
In the mean time I did a nandroid backup of the current state, and then restored an old nandroid backup from several months ago so I could use the phone for now (which sucks cuz I've made alot of little changes since then).
I haven't been on the site for a while, and I'm really busy throughout the day so I don't really have that much time to search through dozens of old threads, even through I tried looking for similar issues (considering if a fix for this problem exists it was probably discussed when this OTA update first popped up several months ago).
I'm sure this question has been asked a bunch so flame away if you must, but I'm just hoping someone can point me in the right direction if a fix or trick exists to get out of this situation without having to completely wipe my whole phone and start over.
Thank you,
--Hammy
I HAVE TRIED EVERYTHING OMG!!! I'm currently running MJ2 and am trying to update to MK2. When i do the OTA update it downloads, restarts, goes into recovery the bar goes half way for 2 seconds and says ERROR! Then just restarts. Using Kies it downloads the firmware goes to 100% stays like that for like 10 seconds then closes the download window! The main Kies window stays but is greyed out, the process is still running no errors no windows NOTHING!!! This **** is soo annoying I even flashed stock rom from this post http://forum.xda-developers.com/showthread.php?t=2507253 and still nothing! Please somone figure out a solution or i might shoot my self!
P.S. Every time my phones reboots it says "CUSTOM" even after the Emergency Recovery soo idk if thats the reason its failing???
I kept getting update errors, so I flashed this non-wipe MJ7
http://forum.xda-developers.com/showthread.php?t=2507217
I took the update, it did not work the first time, but the 2nd time it took. I just did a reboot or two.
I have my s4(remanufactured with no verizon branding) as my backup phone that i have not toched in months, did a full factory reset to prepare to update it to lollipop and all was well. Phone kept saying "update not available" so i looked up somd possible solutions and tried another reset. I was rooted but upon the reset finishing my custom unlock was gone and my phone said it was official software. So the ota failed again repeatedly so i figured i would try it with kies.
Kies or kies 3 both say phone is incompatible. Tried uninstall/reinstall of drivers, no go. Uninstall/reinstall of kies, no go. Phone is still unknown. Tried Verizon repair, gets stuck at 83% for over an hour. Tried it again, 83%. Tried to do verizon update, 83%. So i figure ok, lets do odin and flash stock 4.4.2 kitkat under download, stops almost instantly in odin. I try 4.3, mk2, all kinds of other official roms, will not go.
I figured for the hell of it let's try the full stock lollipop with the pit file (was using it the whole time) and that actually makes it to the 83%. Its been about 6 months since i have even touched this phone, the only memory i have of what i did is that a while ago i wanted kitkat with root so i downgraded to nc5 then reupgraded with kitkat to keep root on it. Something like that anyways. Am i missing something? I must be right?
Also, it says sw rev fused : 7 binary : 6 if that helps anything. Been looking for a few days, no one seems to have had the numbers in the error I am having.
Thanks guys, i hope i gave enough info. I appreciate the help.
Make sure you are flashing the image for the version of the software you are currently on, or that it was on before all of this.