Related
I had my Iconia working well with OTA 3.1 unrooted and it all started when I decided to update it 3.2 and then root it but after updating i realised that there was no root for 3.2 so i searched for a way to do so and i found the "downgrade to 3.0.1(unstable) then root" way and followed it and got my Iconia with the 3.0.1(unstable) downgrade and rooted it with "gingerbreak" and downloaded "acer recovery installer" and got "virtuous galaxy 1.0.5" rom and that's when every thing went wrong after i flashed it with the recovery mode it booted but was unusable it kept on force closing and lagging and nothing worked it didn't even respond to my touches.
I reseted the device many times but in vain so i decided to reflash the downgrade file "3.0.1(unstable)" and remove the root and re-update to 3.2 as if nothing happened but just when i reflashed the downgrade it booted but didn't even give me the chance to do anything it became really "unstable" it kept on force closing the launcher as if i'm stuck in a loop and i don't know what to do as i don't have that much knowledge so i left it closed as it is (so as not to ruin it more ) and want anyone to PLZ HELP me to return back to stock 3.2 (totally stock as if i just bought it) with no roms or root .
Thanks in advance to anyone who did or didn't help
I solved it i managed to get to settings in the 1 second interval between the successive force closes and then pressed factory default and like magic every thing was good as new at last.
Thanks to everybody helped me ...... no one even replied
Well 46 minutes isn't that long in forum-reply terms
Anyways. Good you got it fixed. Did you install Clockworkmod from Acer Recovery Installer, a full wipe followed by a fresh ROM from here flashed using CWM would likely have fixed it.
i think your mistake is , you didnt wipe data before lashing virtuous galaxy
interqd said:
i think your mistake is , you didnt wipe data before lashing virtuous galaxy
Click to expand...
Click to collapse
Exactly but I learned the lesson and now I rooted and wiped and got everything right with virtuous galaxy rom flashed and working
Peter Baher said:
I solved it i managed to get to settings in the 1 second interval between the successive force closes and then pressed factory default and like magic every thing was good as new at last.
Thanks to everybody helped me ...... no one even replied
Click to expand...
Click to collapse
Next time, you can reset your tablet by going: power button + right volume button (when held landscape with power button on top left corner)
power button + left volume button boots to recovery.
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!
Well I'm coming over to the Xoom area now. Picked up two Xoom's (32 gb/WiFi) on Amazon for a good price and looking fwd to all the development you guys have going on over here. Currently been pretty hooked on my Razr w/ the latest round of soaks and OTA's for 4.0.4 along w/ the custom roms.
Right now just reading as much as I can so when both tabs get here on Tuesday I'll be ready to go, have all my files in place, etc.
I promise I won't ask any stupid questions in your guys' section w/ out searching, searching, searching!!!
Figure I'll run one stock 4.0.4 and the other w/ CM9 or EOS. Whichever I like better I'll put on the stock 4.0.4 and give to my g/f. As you can see I've had a variety of tabs/devices and always wanted a Xoom. Thought about getting some of the latest and greatest like the Excite or TF300 but I'm a sammy and moto fanboi and just can't bring myself to do it. I'd rather Moto give up on the Xyboard and release a front runner soon since Sammy looks like they have no intentions of going for performance, and instead focusing on price (ala Galaxy Tab 2, nothing wrong with that btw).
Hey young man
Nice to see another one coming to the dark... *cof**cof*... light side of the force lol
Just kidding... Anyway, if you want root I recommend my tool (LordAIOTool), as many people it's easy and good to do that kind of stuff on Xoom, one guy even mentioned it as "The Ultimate Xoom Tool". Hope you have fun here
Sent from my 3G Xoom using XDA HD - 1st Xoom Recognized Contributor
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
got556 said:
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
Click to expand...
Click to collapse
You don't want stock recovery on the Xoom...can't really do anything with it.
got556 said:
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
Click to expand...
Click to collapse
adb'ing the recovery isn't the best way to go about it. Use fastboot (fastboot flash recovery recovery.img) should work fine.
What I'm saying is guys, I have added custom recoveries (by way of fastboot flashing the .img recovery file). Tried both Rogue and EOS recoveries. They work fine the first time I flash them, but then no matter if I try to use the hard buttons or just use commands to get into recovery it always reverts back to the stock recovery. (As in, dead android, red triangle, then I have to hit power + vol up which brings up stock recovery).
It's as if the custom recoveries aren't sticking.
With stock recovery, do you have the option , "install zip from sd card"?
If you do, I will send you a recovery zip, not image, to be installed from within recovery, not adb... let me know.
Sent from my MZ601 using Tapatalk 2
There you go, http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.zip
Just boot into your existing recovery,
Choose install zip from sd card and flash this.
If it doesn't work, I am afraid you need to to unlock your bootloader again and flash the recovery image again. If that is needed, will help you with steps. Try this first and let me know.
Good luck.
Sent from my MZ601 using Tapatalk 2
We're gtg all. Don't think I did anything different but Rogue recovery works every time now.
Thanks for all the help and suggestions! W/ being on EOS 2.0 my g/f has practically streamed Netflix non stop all day starting at 71% battery life and she just plugged the charger in a little bit ago. It was one of those lazy days and she's in the middle of a season on one of her shows.
Crazy good battery life.
got556 said:
We're gtg all. Don't think I did anything different but Rogue recovery works every time now.
Thanks for all the help and suggestions! W/ being on EOS 2.0 my g/f has practically streamed Netflix non stop all day starting at 71% battery life and she just plugged the charger in a little bit ago. It was one of those lazy days and she's in the middle of a season on one of her shows.
Crazy good battery life.
Click to expand...
Click to collapse
Oh yeah, and the wifi Xoom is slated to get the jelly bean os update next month! You really made a great choice!
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
So I've read through a lot of the forums, it doesn't look like anyone has had this problem yet so it here it goes. I was trying to flash the build three of the unofficial cm10 ROM on my tablet with using team win 2.1.3, I put it on internal SD card, made a backup, but after flashing it, it will say success and then when I reboot it only goes to the Acer screen. I left it for ten minutes straight and it wouldn't go to the second boot animation. I was coming from the collective build of honeycomb. I can still boot it to recovery and when I tried to load my backup it did the same thing as being stuck on the Acer screen when being loaded. If anyone could help me it'd be greatly appreciated.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app