I thought I'd start a thread solely dedicated to problems with the upgrade since the announce thread seems to be getting loaded fast.
I'm one of those with problems, but don't know why. The first boot was great. I rebooted, and now stuck in endless boot loop. My tablet is encrypted, so I have to type password initially, then type it again, and I'm at my desktop, but while it's loading apps, it freezes, crashes, and begins all over again. I'm going to try to wipe data to solve this, which sucks because I spent a lot of time putting my app collection together (well, it seemed like a lot of time ) but I need to unstick this.
I would try cold booting it...it may help.
I downloaded the update this morning, it stopped at 95%. I then rebooted and the download finished...went to install it, passed the integrity check but errored our on installing (android with red triangle).
So it booted back into ICS. Went to check for update again and no Update found message....rebooting,cold rebooting, removing the . blob file isnt working...i am stock rooted with stock build.prop.....only thing not stock is the boot animation. Someone help me out or let me know how to manually update this thing....I would really hate to have to factory reset but I am willing to do it as a last resort.
Edit: I had some frozen apps that I forgot to defrost...so anyone that renamed system apps or froze them with titanium...you need to get them back working then reboot before applying the update. Learn from my experience.
stuck on a boot loop too :/ it boots and it after a couple of seconds restarts. Tried doing cold boot once and keeps doing it
Fixed it unnistalling EZoverclock
jgaf said:
stuck on a boot loop too :/ it boots and it after a couple of seconds restarts. Tried doing cold boot once and keeps doing it
Fixed it unnistalling EZoverclock
Click to expand...
Click to collapse
Wish I would have seen that earlier. The wipe helped in the loop regard, but I'm having trouble getting my root back. Checker says no, voodoo acts like it doesn't need to restore anything. I do seem to still have root access via ADB though.
Anyone got any command line knowledge to get things back in order so root checker will show green again?
So far my I/O benchmark scores seem worst than before :/
jgaf said:
So far my I/O benchmark scores seem worst than before :/
Click to expand...
Click to collapse
but does it feel more responsive?
For now it feels about the same, I had a bunch of tweaks that helped the past FW be better, so right now without those tweaks it feels pretty good
I'm wondering if the update changed something on the file system. I have such inside system/cabin but it still says no root access.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I'm experiencing major issues since the update. was rooted w/ a modified build prop file. restored original build.prop file and saved root w/ OTA rootkeeper and unrooted before I upgraded. I even rebooted the tab. The download & install of the JB firmware went flawlass. But now I keep getting the same error messages/force close boxes, one right after the other - process.com.google.gapps, Google Account Manager, among other Google apps (Google Talk, Picassa), also saw an Asus Sync in there. They all appear to be sync and account related apps. I did a factory reset figuring it would clear out all accounts, syncing & whatever is causing the force closings and they still pop up as soon as I boot up to the JB screen. I cant re-add my account b/c Google Account Manager has force closed. Not sure what my options are besides using my warranty and trading this one in. anyone experiencing the same issue and have any ideas on how to solve it?
I haven't tried to get into recovery yet, usually turn off device and power on pressing either volume up or down + power button and see if you can factory reset / wipe dalvik cache from there
tried a factory reset a few times that way, no dice. my bootloader is still locked so I never installed TWRP or CWM to keep my warranty intact or else I'd reflash the JB update. but as it came as an OTA, i think I'm pretty screwed here
This may sound crazy to you, but if you've already wiped then it doesn't matter. Go and get the .30 firmware from Asus, extract the first zip into root of sdcard, the extract will be a zip too. Tablet should pick it up, think its a downgrade and prompt you to continue. It reloads, but when finished you will still be on jellybean. That's what I did to solve another problem and that was the result. Not what I wanted but it might help you.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
This may sound crazy to you, but if you've already wiped then it doesn't matter. Go and get the .30 firmware from Asus, extract the first zip into root of sdcard, the extract will be a zip too. Tablet should pick it up, think its a downgrade and prompt you to continue. It reloads, but when finished you will still be on jellybean. That's what I did to solve another problem and that was the result. Not what I wanted but it might help you.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
that does sound pretty crazy, but I'm crazy enough to try it. what issue were you having that you thought to try this method? and did it solve it. "not what I wanted" makes me think it didn't help you. so you say it picks it up like a downgrade, but doesn't actually downgrade anything? i'm thinking the upgrade didn't go thru correctly and some system apps didn't update properly causing all my issues. I even called ASUS to RMA this pad, they didn't even know the JB update was rolling out, telling me the lastest OTA was still ICS. they are clueless.
Is it possible to downgrade to previous firmware to restore all of my originally installed apps? It seems if you root, then uninstall system apps the jellybean update fails. I factory reset, but it seems that whatever you uninstall or modify doesn't get restored that way. I'm reluctant to go through pushing .30 over via adb. Is there a way I can just drop an update.zip on my internal sdcard and reboot into recovery somehow? Any help would be greatly appreciated. I'm pretty confident I can root jelly bean by manipulating the file system. I'll leave that for later. Just waiting for CM10 to become a bit more stable before pulling that trigger. The asus firmware isn't so bad anyways. So....how do I "downgrade" to .30 or even .29 and restore the tablet to pure factory???
AFAIK you can't, you need to find out what system apps you removed and push them back using adb then reboot
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
AFAIK you can't, you need to find out what system apps you removed and push them back using adb then reboot
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Surely I can take a factory blob and push it over. I'm looking at a downgrade guide now. The blob is over 300 megs. Surely it has all the system apps with it.
The full ICS blob was 800MB. The upgrade.zip for the JB update alone was 300MB using patch.
The problem I am having is some weird force closes in the Settings app. But nothing too major there.
I came from a fully stock ICS, so the improvement in browsing (Chrome, especially) is much better.
There are still some stuttering in the OS, but overall I am pleased with the improvements.
I am finding that I cannot change the keyboard locale when attached to the dock. THis isn't a huge deal for me though.
paedz718 said:
that does sound pretty crazy, but I'm crazy enough to try it. what issue were you having that you thought to try this method? and did it solve it. "not what I wanted" makes me think it didn't help you. so you say it picks it up like a downgrade, but doesn't actually downgrade anything? i'm thinking the upgrade didn't go thru correctly and some system apps didn't update properly causing all my issues. I even called ASUS to RMA this pad, they didn't even know the JB update was rolling out, telling me the lastest OTA was still ICS. they are clueless.
Click to expand...
Click to collapse
My issue was...
I was rooted on .30. After the update to jb I got stuck in a reboot loop. It got to the desktop then crashed.
Thought I could resolve by wiping data. When I did that, lost root and cannot get it back due to updates to the permissions of the /data folder.
So I thought why not try and reinstall .30. And you know my result.
I learned later my looping was most likely caused by the ezoverclock app, but I read that too late. So I'm on jb without root and appear to be stuck that way until another exploit is found or I unlock the boot loader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
gotcha. I can't even get past the Google account screen, that crashes immediately. I tried loading the .30 firmware on the SD card but since I can't get to the desktop, it won't pick it up to update. I can only get to the settings screen. I could probably unlock the bootloader and flash another ROM to get me thru this, but I'd like to keep it locked. going to get this RMA'd as soon as their system gets back up.
paedz718 said:
gotcha. I can't even get past the Google account screen, that crashes immediately. I tried loading the .30 firmware on the SD card but since I can't get to the desktop, it won't pick it up to update. I can only get to the settings screen. I could probably unlock the bootloader and flash another ROM to get me thru this, but I'd like to keep it locked. going to get this RMA'd as soon as their system gets back up.
Click to expand...
Click to collapse
Perhaps there is one more thing you can try.
As part of the update the bootloader got updated. I was playing with this last night and I see a new USB graphic to choose. If you select it you can engage the tablet via fastboot. Now other than initial contact and a couple of minor test commands I didn't do anything with it, but perhaps you could flash the ROM with that?? It will load USB drivers for boot loader interface when you do this the first time.
BTW if you don't know, hold power and vol down to get to it, then when you see the graphics keep pressing vol down until the USB symbol lights up, then press vol up.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Related
Hey folks, I've read through all the JI6 OTA threads here and on the TMo forums and while I've seen a few people guess as to the cause of soft bricks, dosen't seem like anyone has nailed down the actual cause. I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN so knowing what if anything can be done to prep my phone before accepting the OTA (that is sitting in my notification bar as we speak) would be immensely helpful.
So far the two best guesses I've seen are the existence of other update.zip files on SD and removal of bloatware, specifically Media Hub and possibly edited startup/shutdown screens.
Since I've got all these going on, I guess I'm staring down the barrel of a brick. But obviously one of these is easily rectified while the others, not so much.
Aside from those claiming bricks on vigin phones. Can we hear from those who have made mods to their rooted devices and either did or did not experience an OTA brick? I think this info will be helpful to many in sorting out what exactly is going on here.
I have black bar mod, I have naked swype, removed most t-mob app except media hub no change to start up or shut downtried to update. 50 % through it said update failed. Then rebooted fine. But I had an extra update.zip on my sd so maybe that's why. But no firmware now? Maybe I'm sol.
Sent from my SGH-T959 using XDA App
Mine wouldn't complete the update Rooted, most of the bloat removed, had an update on the sd. Was able to get into clockwork after the failed update and am performing a nandroid restore now.
this is great, thank you. beginning to look more like an issue with extra update.zip files than media hub. any successful OTA's with media hub removed prior to accepting the update?
Sent from my SGH-T959 using XDA App
I never uninstalled Media Hub. I have seen a correlation of about 5 people who had ROM manager installed and used that to install Recovery. Whether it be the installation of Recovery or a possible permissions issue with how it generates the update.zip that may have caused my issue.
just a question, why do people remove media hub? Does the application make the phone slow?
iynfynity said:
just a question, why do people remove media hub? Does the application make the phone slow?
Click to expand...
Click to collapse
Because up until now, it was a non-functional app. I didn't remove it, I use LauncherPro so I just removed it from my drawer. I'm still not touching this update. I got my Vibrant used so I would be out of luck if it jacked my phone up and I hate using ODIN. Too much hassle when my phone runs great on Bionix 1.4 as it is.
Wife's phone was toasted by OTA. Stuck at Vibrant screen. Rooted, unlocked, she did have an update.zip, if that turns out to be the culprit. Also had some apps removed, replacement startup animations, and removed shutdown junk.
She was set for always-on WiFi, too.
My rooted Vibrant soft bricked yesterday and I had to flash stock with Odin. I had the (what seems to be infamous) update.zip, removed Kindle, Mobi TV, Avatar Icon, Gogo. I had RyanZAOneClickLagFixV1+ installed but removed it. I also had the EXT2 Tools installed. @ the time of the update I was @ work and had a full charge on the phone. I flashed back to stock last night after work, and I haven't recieved the update notificaiton again...maybe TMo crossed me off some type of "update list"?
There are also different possible symptoms.
In my case the update appeared to have completed its cycle, except the tail end of the download of the new update wnt really fast then the system rebooted. System came back up into the Black Vibrant screen. I could start 'adb logcat' and the system had SurfaceFlinger repeatedly crashing.
Attempts in Recovery Mode after this to reinstall files didn't resolve the issue, reboots would still lead to a crashing SurfaceFlinger.
2 separate users in a thread, 1 had removed Boot Animations + Sounds, I only had removed Sounds.
Quite a few people had Stock Roms + Root, but some with Root didn't have any issues. Only correlation was with Titanium + Rom Manager, which a lot of people would have installed since it's listed in the Tips and Tricks thread. Titanium shouldn't do anything to the system unless you generate a backup Update.zip or install LZO support busybox.
One guess is that ROM Manager and Titanium can create a update.zip file that doesn't have the proper permissions. An OTA update that attempts to overwrite this file may get confused. Simply removing the file in advance may alleviate this issue. Another issue is ROM Manager installs ROM Recovery, which may change how the OTA perceives the phone.
Bionix 1.4...
I was running Bionix 1.4 KK OC/UV yesterday morning... Was a little dumbfounded when I received the update message from Tmo. Figured it wouldn't show w/ modded handset. Delayed install until I could read everything on here about it. Tried installing over Bionix last night just to see, and had no joy. I had removed all crapware, mediahub included. Hit 50%, said flash failed, rebooted and was back to my homescreen in no time. No ill effects to phone except being denied upgrade.
So I Odined back to Stock JFD FW (and wiped device for S&G), rooted, and updated from JI6 tar posted. Flashed perfectly, no ill effects as I've noticed. Reception is improved (for me anyway), and GPS functions similar to Bionix... No real incentive for update, but was curious.
I see Bionix 1.7 updated so it was all for nothing.
Now to play with other stuff...
Cheers
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
I got the soft brick and had to flash back to stock via Odin and then I flashed the JI6 tar file from the forum. All is working fine now.
I had root but no update.zip file on the sdcard root, had removed startup an shutdown sounds, had used both ROM Manager and Titanium (with LZO compression turned on), and had removed bloatware including the non-functioning Media Hub.
Next time I'll flash back to stock before doing an OTA update.
I am rooted have Titanium backup, ROM Manager, and clockwork mod. I also had an update.zip but I think it was from OCLF not from another source. My update went fine and I'm running without any problems on the new update.
PepeLasNoches said:
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
Click to expand...
Click to collapse
Woo, got it unbricked! finally got into download mode and ODIN saved the day.
this video was helpful for me: http://www.youtube.com/watch?v=AnY7P14JSWQ
^ODIN walkthrough
paxton said:
I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN
Click to expand...
Click to collapse
there is a cross platform tool being developed called 'Heimdall'. It is currently a command line tool and is in beta. however people are successfully flashing their phones using it. It is obviously not a 'one click' solution, so you will have to go find the proper files and type out the command.
It can be found here http://forum.xda-developers.com/showthread.php?t=755265#
If you are the type of person with access to both a windows machine and a linux machine, I suggest you check this out. Testers are needed. Of course you can test if you don't have windows, but it's nice to have Odin as a back up. ;-) just incase....
-p
I had a failed update twice using Odin. It wasn't until I went back to stock T959JFD for the second time and deleted update.zip and all clockwork back ups that it finally worked. Runs perfect with no issues.
Sent from my SGH-T959 using XDA App
Was rooted with OCLF, Captive camera, gps fix, rom manager, titanium backup and add removal. Removed the OCLF and unrooted, ran the update, looked like it got to 100% (not sure cause I looked away and then back at it right before reboot) but said update failed. Got stuck at the vibrant screen blah blah. I'm pretty sure I had an update.zip on the sd, but not 100% on that. After pushing the update with ODIN I have noticed my phone lagging quite a bit.... Thoughts?
Sent from my Rooted Samsung Vibrant using XDA App
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
swampy67 said:
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
Click to expand...
Click to collapse
Would someone (aka moderator) simply sticky a bold
DO NOT REMOVE ANY FACTORY FILES, u goty plenty of room.......
to prevent this kinda stuff
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
dr1337 said:
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
Click to expand...
Click to collapse
but how do i reinstall when im stuck in a boot loop? is there some way to execute adb?
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
anubis13 said:
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
Click to expand...
Click to collapse
Thanks I'll give it a shot
Sent from my PC36100 using XDA Premium App
thanks this worked like a charm. Gotta love the XDA community.
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Chaz36 said:
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Click to expand...
Click to collapse
Okay so this is what i did as directed by the guys above.
1. Download this file. have to warn you though this service is horribly slow http://api.viglink.com/api/click?fo...ww.filesonic.com/file/958397...pdate.zip.html
2. Put your external SD card into your computer, and copy over the file to the root of the card.
3. Rename the file update.zip(make sure it isn't named update.zip.zip)
4. Put the SD card back it the tab.
5. Make sure your tab is completely shut down.
6. Hold down the volume down button and press the power button.( dont let go of the volume down button till the screen turns on)
7. The recovery will boot and the update should hopefully restore your tab.
8.(optional but recommended) follow these steps in order to revert back to the latest OTA american version so that your able to upgrade to 3.1 when it comes out.http://forum.xda-developers.com/showthread.php?t=1101859
Hope this helps.
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Chaz36 said:
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Click to expand...
Click to collapse
Well sorry that didn't work, i am not to experienced with development for this tab, so im fresh out of ideas. It might help to start a new thread explaining that you tried to un-brick your tab via this method and that a boot loop still occurs. Maybe some super smart devs can help you.
Crsdr37 said:
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Click to expand...
Click to collapse
yeah i did that right after i un-bricked it, but thanks for the heads up anyways.
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
SmittyRN said:
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
Click to expand...
Click to collapse
Dude, you just made my day.
Thanks.!!!!!
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Same question here
Sent from my A500 using XDA
3d0rr said:
Same question here
Sent from my A500 using XDA
Click to expand...
Click to collapse
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
tu3218 said:
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
Click to expand...
Click to collapse
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
Yeah I think so as well. I flashed stock via the Acer recovery tool but I get nothing when I boot into recovery except what I stated above. I'm not sure if that's right or not.
Sent from my Galaxy Nexus using XDA
I was happily running timmydean's rooted 3.2.1 based on the leaked OTA. The ICS upgrade came through and installed just fine. No loss of data and the programs I tried all worked. I was on stock 4.0.4 unrooted.
However, I'm now borked. I rebooted into recovery (Power, Vol -) to see about rooting via the backdoor I'd installed. I had thor's 1.7 Touch CWM recovery installed. I got some weird message that recovery was broken. (Don't recall the exact msg.)
After that, it hung on the "android" screen. Soft-bricked.
So I did a factory reset (Power, vol+, rock screen switch) and ended up back on 3.2.1. Now, the Settings > About > Check update results in the "Network coverage is currently poor. Please move to a location with better coverage to continue." message.
My WiFi is fine, speedtest.net reports a 20 Mbps download. All other apps function well. I'm pulling a DCHP address from my router.
I'm fairly sure this is a badly-worded error message from Acer and actually refers to server overload or some other issue on their end.
Also, installing the latest Acer Iconia Update preps the system for ICS. At one point, installing it allowed the update to proceed, but not to ICS. Uninstalling/reinstalling that update seemed to jog the system at one time.
So I tried wiping data/cache/dalvik and went back to stock 3.2. Same error message when updating. Wiped again and went back to stock 3.0.1. Same error message.
So I'm stuck and am going to give it a few days to see if Acer can sort out their upgrade path. If not, I will probably load CM9 or Thor's ICS ROM. (I do have a Nandroid, so I can get back to where I was pre-ICS.)
All in all, I'm very disappointed in Acer for borking my tablet.
________
Update: So now a day later, the "poor coverage" message was replaced by an "update available". Installed A500_7.014.03_com_gen1, after reboot, another update A500_7.014.15_com_gen1 installed. I am now on stock 3.2.1.
System update shows "Your device is up to date".
Will see what tomorrow brings, but this is certainly frustrating.
thorne75 said:
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
********************************************
Could you guys running the backdoor and still rooted please try this:
1) Try and capture the build no. of the update
2) See if the update will download BUT do not install yet
3) Go to /cache/fota/ and find the zip -
4) copy it to yr external sd
5) post back the build no.
thanks!!!
Procedure for manual install:
1/ rename the file as : update.zip
2/ place the file on the micro sd card
3/ turn off the tablet
4/ press the down volume key and the power button at the same time untill the tablets turns on
5/ the iconia will start the upgrade process by itself.
OR just redownload the update and it install
*********************************************
I had trouble when i reverted to stock in the weekend
and it was a bit of a process to get the OTA's to 3.2.1.
I did manage to hold "full root" but had to revert a couple of times
by putting stock recovery back and using backdoor .
I accidentally factory reset and everything went a bit pear shaped from there...oops!!
Im still waiting for the OTA ICS - getting network coverage error -one good thing
is my partners tab is only 5 days old and still pure factory,
her tab shows same error so at least we know its not root/backdoor problem
So yeah if u gonna take the OTA best to get rid of the backdoor unless you wanna play guinea pig for us all>>>>
dunno why we aint found one of those yet
I dont think you can cause too much of a problem where a "hard reset" pwr/vol -/rotation lock/ combo wont fix...you can then root from there.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
dibb_nz said:
********************************************
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
Click to expand...
Click to collapse
Dibb_nz, I was stock gen 2. I don't wanna take OTA until be sure it's safe. Unless now I know that a hard factory reset may save my tab if something happen.
Can you tell us where did you read that post about 'gens'? I still a little confuse about that
Sent from my A500 using XDA
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
3d0rr said:
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
Click to expand...
Click to collapse
oh sounds promising, although I just read another post from someone across the ditch in OZ he reckoned acer said they were working on a patch for the problems theyre havin with the first update...who knows
now m8, sorry to confuse you, that wasnt my intention, but i try to make sure that i;m not suggesting things which may end with you or others borkin or brickin yr tab. Ive spent the last few days reading thousands of posts (just like everyone else) thankfully we are fortunate in being able to learn from the mistakes of others I know a bit more about ics than i did 3 days ago let me tell you, lol.
i just finished helpin out a fellow "timmy-ite" stuck with no way of getting in to apx mode to get un-borked...well didnt really help just a sounding board more than anything
he got himself up and running, used the apx tool in my sig, unlocked the bootloader, rooted, flashed custom recovery did a nand and is now running flexreaper - with the tools and knowledge he gained he now has the choice to go back to HC to get the OTA or not....he's one happy camper!!!
Have a read have a read thru the threadhere. ask him a question or two if you want - but dont get too hung up "maybe doing something wrong" you won't be the only person ever to experience that uhh-ohh sinking feeling when you know you shouldnt have just done whatever it was that u just did
Theres always someone round here who will help - usually cos they done the same silly lthings themselves - why ya think i'm always posting
what is the backdoor program you guys talk about?
tu3218 said:
what is the backdoor program you guys talk about?
Click to expand...
Click to collapse
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
jpinsl said:
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
Click to expand...
Click to collapse
timmyDean How to root stock 3.2.1
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Click to expand...
Click to collapse
beat me to it
its a completely stock gen2 rooted and cwm - you can use to unbrick, or go back to stock. only for HC bootloaders though.....
This worked to me
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method.
1) Go to play market and install Acer Recovery Installer.
2) Open Acer Recovery and verify with recovery do you have. In my case it was CWM recovery by thor2002ro 1.5
3) Install stock recovery. Make a backup of your old recovery when ask.
4) Factory reset: in my case, I made a backup of all my data and used Titanium to backup some apps. Then I harded reset my tab by turning it off and the combo pwd + vol(+) then lock-unlock switch 3 times until I saw "eraing user data" in the top-left corner.
5) turn on the tab and go to google play. Search for acer and install Update enhancement.
6) Go to settings-> about-> system update and aply the OTA update.
You will lost root, but everything should work fine.
To gain root access again, you can follow this thread -> http://forum.xda-developers.com/showthread.php?t=1546593
Now I have rooted stock ICS and I'm so happy
Hey great write up, will try this as soon as I'm off work. Anyway to confirm stock recovery is installed? Because I have done what you said(just the flash stock recovery part) an when I boot into recovery I just get a triangle an exclamation point. Not sure if thats right or not. But I will definitely give this a go since you were running exactly what I'm running now.
Sent from my Galaxy Nexus using XDA
3d0rr said:
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method...
...To gain root access again, you can follow this thread - ...xda-developers.com/showthread...
Now I have rooted stock ICS and I'm so happy
Click to expand...
Click to collapse
yay for 3d0rr you finally took the plunge congrats!!!!!
@tu3218
That download link is no longer available
instead download blackthund3r's one-click-root,
google "ICS Root for Windows"
At step 3 - After you have backed up -
Copy the uid.txt file from the backup folder - this holds your cpu id -
you're probably gonna need it at sum stage
I followed your instructions and it went perfect!!! Rocking ics now. Thanks for the help. First thing I notice, soooo much faster an full of butter.
Sent from my Galaxy Nexus using XDA
I was running Thor Rom, but I installed the update, but from This thread and others, even the ones I had to decrypt first. The update always went smooth and ICS looks and works great; except....
Any time the screen goes to sleep, or I press the power button to turn off the screen, the screen won't wake up. OK, correction, it WILL wake up if I turn it on within ~10 seconds, but wait longer than ~20 seconds and it won't come back on. I have to press and hold the power button to apparently shut it down (hard to tell because you can't see anything and there are no indicator lights). Then I have to press and hold it again and it boots back up.
Hence, I have to press and hold the power button for several seconds twice each time I want to use it.
I'm not sure if it's shutting down or just hard freezing. I can't seem to shake this. It didn't do this with the old stock rom or Thor.
Ideas?
Currently Running the following on my A500 1.0
Image: Acer_AV041_A500_RV05RC01_PA_CUS1
Build: Acer_AV041_A500_1.033.00_PA_CUS1
same problem
I have the same problem, I updated my tablet via the acer update and now it does that :/
First I thought it was some problem with a program I had installed, but then did a factory reset and left a couple programs and still doing that.
Im going to try to hold the reset button to see what happens.
This issue is known to occur with several custom ROMs and is referred to as the Sleep of Death or SoD. It occurs when the tablet goes into deep sleep and refuses to wake up. Thor has suggested those affected and using his ROM to increase the voltages of their CPU or flash his performance kernel. If you are using Stock ICS from Acer then I think there's a thread documenting issues with it. You can check that, it should be in the general section. Hope this helps. It happened to me only once and I can't recall which ROM, but it never happened again.
Sent from my Iconia A500 using Tapatalk 2 Beta-6
That's just the thing, I want the stock ICS and I thought I had it (still think I do!). I'd like to go back to stock to make things work correctly. However, there is no 'check update' button for me in my settings. I have no way of looking for an OTA update that I can find. I'm dumb at times, but not that dumb.
I have the same problem and I'm running CM9 now. I started with the same ICS update that you listed in your first post. I have two GEN1 ICS updates I think I'm going to try. Since the problem has transcended roms (Stock ICS to CM9) I'm thinking this is a firmware issue with the CUS update. I read a thread that said (man I'm rhyming tonight...) the CUS didn't come with some firmware images that the GEN ones did.
EDIT: Since I'm on the V3 Bootloader I don't think I can install these updates. I decrypted them, but it's still failing to install. Probably have to be on the stock bootloader for these to work.
Frostcall said:
That's just the thing, I want the stock ICS and I thought I had it (still think I do!). I'd like to go back to stock to make things work correctly. However, there is no 'check update' button for me in my settings. I have no way of looking for an OTA update that I can find. I'm dumb at times, but not that dumb.
Click to expand...
Click to collapse
I downgraded my tablet back to 3.2 using info in one of the Dev threads. Then I let it update with OTA updates to 3.2.1. I then had to install the Acer Update Helper app on the play store in order to get it to update to ICS. The point of all this is that until I went back to a stock 3.2 I could not do an OTA update as the roms were not stock.
Then once I was on stock 4.0.3 ICS I was STILL getting SoDs. I put in a trouble ticket to Acer and the response I got was to do a full hardware reset (power off, hold power and volume up until it vibrates, then toggle the screen lock switch a couple times.) I finally got back to installing a custom rom (flexreaper r13) and I now no longer have SoDs. A lot of work but I think I'm finally stable.
Sent from my A500 using XDA Premium HD app
BakaNeko59 said:
I downgraded my tablet back to 3.2 using info in one of the Dev threads. Then I let it update with OTA updates to 3.2.1. I then had to install the Acer Update Helper app on the play store in order to get it to update to ICS. The point of all this is that until I went back to a stock 3.2 I could not do an OTA update as the roms were not stock.
Then once I was on stock 4.0.3 ICS I was STILL getting SoDs. I put in a trouble ticket to Acer and the response I got was to do a full hardware reset (power off, hold power and volume up until it vibrates, then toggle the screen lock switch a couple times.) I finally got back to installing a custom rom (flexreaper r13) and I now no longer have SoDs. A lot of work but I think I'm finally stable.
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse
I wonder if this will work with the V3 bootloader?
naviathan said:
I wonder if this will work with the V3 bootloader?
Click to expand...
Click to collapse
That's what I had installed when I started the process. Of course it eventually got overwritten with the unpatched stock bootloader, but that was easily fixed.
Sent from my A500 using XDA Premium HD app
How did you manage that? I need to figure something out because right now I can't set my tablet down for two minutes without doing a hard reset. Over clocking helps, but it's got limits. Not to mention the wifi...Man it's horrible now!
i have a nexus thats completely stock( out of the box) worked fine for about a month, let the tablet die and has been unplugged for about a week. got it charged up and and would not turn on. using the nexus root toolkit i was able to get to turn on. unlocked the device( unlock logo below google icon on startup) was unable to get past that point. now finally i can get past the nexus boot logo but it gets stuck on aindroid is upgrading " optimizing app 1 of 11" i cant root using the root tool kit bc when i unlocked device it got rid of developer options ( by what the msg said before i unlocked). im simply trying to get my device to turn back on. i dont plan to root or install a rom, im fine with the stock rom. i just want to damn device to turn back on. when i was able to power on the device when i first got it i did upgrade to the newest jelly bean rom. any one can help me on this issue ??
thanks
Boot into temporary custom recovery using Nexus root toolkit(Advance menu). Now wipe cash and devlock than try rebooting into system. If it doesn't work you can try factory reset. Last but not the least will be Flash Stock + Unroot(Soft brick/boot loop).
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
dac2009 said:
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
Click to expand...
Click to collapse
If the factory reset doesn't work just go for the Flash. I don't think you are much worried about the data so it's not a big deal for you. and I'm quit sure this is gonna work. Best of luck.
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
dac2009 said:
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
Click to expand...
Click to collapse
Okay, that's weird!!!
Are you using Nexus Root Toolkit?? If yes are you using pre-downloaded android??
Try Automatically download + Extract.....
Last of all I'm really confused how there could be a problem when you got a fresh OS and Stock.
I agree with the messing thing that you told... Try checking and double checking everything... Check if you have selected the correct device or not.
And do a full wipe(including system) using TWRP before flashing again.
Edit: Make sure you are using the latest toolkit. You can get it from the link bellow.
http://forum.xda-developers.com/showthread.php?t=1766475
Try flash stock image throught toolkit.
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
dac2009 said:
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
Click to expand...
Click to collapse
I don't see a way how the problem still exists... :S
Whatever the problem is it's seems to be with android OS. But how it exists in completely new android. Sorry can't find a reason behind the problem. You can still try flashing any older android (like 4.1.2).
ok i got a zip of stock 4.1.2 and using the root tool kit i can install a zip via the twrp but it wont let me bc it says adb device not found and that developer options need to be turned on. im un able to turn it on bc i cant even get into the rom on the device.
thanks
ok i got it working. i was able to flash the older rom to my device and its working so far. no force closes yet.
thanks for everyone's help
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21%2018.37.24.jpg
dac2009 said:
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21 18.37.24.jpg
Click to expand...
Click to collapse
I can't just think of anything else. Just telling you the things that I'd have done if I were you.
* reinstall boot
* change kernel
* turn off the auto update of android.
* try some costume room.
Don't throw it out the window you call always donate it to me if you really wanna throw it or make a drop test video...
Last of all just don't lose hope keep trying. you'll find out something surely and share it with us.
Sent from my Nexus 7 using XDA Premium HD app
Daft question, but the few times you managed to get it running, was your Wifi on?
Sent from my GT-I9300 using xda app-developers app
yes my wifi was on and was able to stream . spotify among other things
Not the exact same situation, but I found certain Wifi router's would trip my nexus into reboots until I rooted
Sent from my GT-I9300 using xda app-developers app
Phone is stuck in "Android is upgrading. Optimizing application 1 of 1" HELP!!!!!!!!!
hey guys, my phone is stuck in "Android is upgrading. Optimizing application 1 of 1"
and all I can do is
1. apply sdcard/update.zip
2. reboot system now ( does NOT work coz it brings me back to optimizing apps )
3. apply update from external storage
4. wipe data / factory reset
5. wipe cache partition
6. apply update from cache
is there a way i can backup first all my files before factory resetting my phone (if thats the only option i have)????
help me please