Related
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
fayettec said:
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
Click to expand...
Click to collapse
Did you install the Flexreeper new bootloader? This is probably why you still have SOD. If I am not mistaken, Flexreeper has 2 or 3 different versions of bootloader that you need to use. Depending on which version of the rom you want to install.
Scary Bootloader
Moscow Desire said:
Did you install the Flexreeper new bootloader? This is probably why you still have SOD. If I am not mistaken, Flexreeper has 2 or 3 different versions of bootloader that you need to use. Depending on which version of the rom you want to install.
Click to expand...
Click to collapse
Thanks for the reply.
I thought that the img file was for people with ICS bootloaders, I thought that I had HC3.0.1
I'm afraid if i flash the ICS img file that I won't beable to get back to HC or that because I have 3.0.1 bootloader that the ICS bootimage file they have there will brick my a500
If you formatted and wiped everything as you were instructed . I am wondering if when you get to the google setup screen something is being restored from the old system.. When it gets to where you setup your google account. Uncheck the backup and restore boxes .
Do not restore any apps or settings from say TI BACKUP. Install only a few apps that you MUST HAVE and know work with google ics. run for a few days and see what happens.
if you still have a issue go back to 3.2 for a week and see if it works. it could be just coincidence that hardware fail-or at the same time as you flashed your tab. ..
just a though thou unlikey
Thanks
I went ahead and tried the ICS Boot.img file after reading some new post in the thread. It worked! Interesting side note, be fore the flash at boot up the display showed:
ACER.
After it was:
ACER ACER
Thanks again!
fayettec said:
I went ahead and tried the ICS Boot.img file after reading some new post in the thread. It worked! Interesting side note, be fore the flash at boot up the display showed:
ACER.
After it was:
ACER ACER
Thanks again!
Click to expand...
Click to collapse
You running an a500 or an a501?
Last time I saw the double Acer, was when the leak first came out. The 500 had issues, but not the 501 (except for double acer).
The double Acer is normal. Be glad you don't get the AFU screen like the rest. It's a BETA release, and it has..... issues. Hopefully Acer will release an official build that will do away with a lot of the issues in the near future.
fayettec said:
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
Click to expand...
Click to collapse
I came from ezterry's acer7.014.14_CUST_ROOT_BBv4_S. I just flashed Flexreaper R11 this morning. I've noticed SOD at least three times today. My bootloader version is 3.01 like in the OP. I noticed he ended up flashing the ICS bootloader. Is this the only known fix? And if so, will ICS bootloaders prevent me from restoring a HC NAND? Thanks.
How do we find our boot loader version? When I do, what does that mean for ROMs I can flash? I have flexreaper r11 and it is consistently SOD badly. :'(
Sent from my SGH-I777 using xda premium
bigwilly90210 said:
How do we find our boot loader version? When I do, what does that mean for ROMs I can flash? I have flexreaper r11 and it is consistently SOD badly. :'(
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
To me a favor and flash the kernel for ICS boot loader users.
Its in the thread , section kernels.
The rom got a auto script for installing the correct boot.img but even for some the ICS boot.img is needed.
Worst that can happen is stuck on Acer logo, if you got that just reboot into recovery and flash the boot.img or kernel for HC boot loader users.
The thing is that even for some people that got HC bootloadr they still need to flash the Kernel for ICS boot loader users, strange yes but no harm in trying.
I'm wondering if something in the cmdline for the LP0 changed in the latest leak causing the kernels packed for the old bootloader to have SoD again.
Also, some of you guys, please don't confuse bootloader with boot.img. They are not the same thing. FLEXREAPER does not contain any bootloaders. It contains 2 different boot.img's and trys to install the correct one based on the bootloader you have.
The bootloader only gets changed if you flash it via nvflash (or flash a stock leak but then it would be locked).
@someone who asked above. if you flash the ICS bootloader(0.03.11-ICS), you would not be able to run HC ROMs, unless you went back to the HC bootloader (3.01).
But apparently, the ICS boot.img is working for some on the old HC bootloader and resolving the SoD issue for them.
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
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 was running the FlexReaper Relix v7 and suddenly yesterday my a500 just froze. Nothing worked, homescreen, back arrow, nothing. So I restarted it, and it was stuck in bootloader, twice. So then I held down the volume and power to get to recovery. It took me several times trying that to finally get to recovery but while in recovery I couldn't do anything. I can't wipe any data, or install anything. In fact it won't even ready ANY of my SD Cards. I have the TWRP recovery 2.1.3.
Edit: Now I can't even get to the recovery screen. Would love some help
SugarCoatedAngel said:
I was running the FlexReaper Relix v7 and suddenly yesterday my a500 just froze. Nothing worked, homescreen, back arrow, nothing. So I restarted it, and it was stuck in bootloader, twice. So then I held down the volume and power to get to recovery. It took me several times trying that to finally get to recovery but while in recovery I couldn't do anything. I can't wipe any data, or install anything. In fact it won't even ready ANY of my SD Cards. I have the TWRP recovery 2.1.3.
Edit: Now I can't even get to the recovery screen. Would love some help
Click to expand...
Click to collapse
Hmmm have you got a hammer ?
twistedknickers said:
Hmmm have you got a hammer ?
Click to expand...
Click to collapse
Yes, I also have a lake in my back yard. I'm ready to give up on it and buy a new tablet, but don't want to spend unnecessary money.
SugarCoatedAngel said:
Yes, I also have a lake in my back yard. I'm ready to give up on it and buy a new tablet, but don't want to spend unnecessary money.
Click to expand...
Click to collapse
I think you need cwm 1.7.3 if you can get it on to the machine
I'm actually sending it to my friend, he says he knows how to fix. I dont have the time for this anymore....lol Thanks though