Database Users

Help! stuck in boot animation after trying to update to 3.2

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.

[Q] Still having sleep of death

I have been trying out a couple Ics roms, all of which claim have no SOD, but I'm still having problems. I have tried
Lightspeed 4.2
Latest icylicious
Tabooney 3.0.1
I guess to be sure, what I'm experiencing is every seems to work fine, but if the screen goes off for more than a couple seconds, it won't come back on. I have to hold the power button for a few seconds, then let go, the hold down the button again it turns on again fine.

What bootloader did you flash?

FloatingFatMan said:
What bootloader did you flash?
Click to expand...
Click to collapse
I guessed that I still have the boot loader that I installed back when I got my a500 last summer. I thought the ICS boot loader was unstable or something. Should I try the other bootloader that is posted?
Edit: I checked in thee Acer Recovery Installer app and it says I have bootloader 3.01

The SoD is usually caused by the bootloader, but it's possible you didn't wipe something when you flashed one of the ROMs. Personally, I'm running the version of AmonRA we have (though that's not fully compatible with Acer Recovery Installer), and on top of that I have Vache's ICS leak, complete with his 3.0.1 patch. I have no SoD issues at all with this configuration.
You DID do a full wipe, right?

veidt_industries said:
I have been trying out a couple Ics roms, all of which claim have no SOD, but I'm still having problems. I have tried
Lightspeed 4.2
Latest icylicious
Tabooney 3.0.1
I guess to be sure, what I'm experiencing is every seems to work fine, but if the screen goes off for more than a couple seconds, it won't come back on. I have to hold the power button for a few seconds, then let go, the hold down the button again it turns on again fine.
Click to expand...
Click to collapse
I tried both icylicious and flexreaper and could not get rid of the SOD either. I have the 3.01 bootloader and have wiped and formatted and wiped some more. Everyone keeps saying the SOD is because I didn't do a full wipe. I'm back on 3.2.1 now.

Did you check if an ICS incompatible app might be the reason?
Best regards, maris

maris__ said:
Did you check if an ICS incompatible app might be the reason?
Best regards, maris
Click to expand...
Click to collapse
I thought an app might have been at fault so I did fresh formats/wipes and didn't restore any apps to be sure but still got SOD. The screen goes to sleep normally then after a short time reboots and gets stuck until I press power to turn off, then power back on.

Thanks everybody, it was the bootloader. Just for closure, here is what I did.
Install leaked ICS from here
Fix the bootloader and recovery from this thread
Install ROMs like normal
Thanks again

Had SOD all the time with flexreapper, installed newest thor's and all SODs gone. I guess the issue is specific to ICS' ROMs based on the leak.

Whats the newest version of thor clockworkmod recovery for Iconia a500?

veer01_42 said:
Whats the newest version of thor clockworkmod recovery for Iconia a500?
Click to expand...
Click to collapse
NEXT time, Google should become a resource for you..... But this time, V1.7.1 I believe is latest 'touch' version.

SOD ain't there on LEAK version...
ROOT can be done on LEAK version...
the problem for sure is from CUSTOM

There's no SOD in the custom ROM's built from the leaks, either; as long as you followed the instructions properly.

Try this out. Finally worked for me.
Hey a little late here, but I have had SoD for months. I have tried everything (new bootloader, several roms), but nothing seemed to work. I finally tried flashing a custom kernel separately after I flash the rom and it seems to be working now.
Here is the ezterry A500 rom, http://forum.xda-developers.com/showthread.php?t=1703590 and its a zip so you flash just like a rom. Good luck everyone who has the same problem.

[Q] Bootloaders problem

I'm running a FLEXREAPER ROM RF1, with HC 3.01 BL. Everything is OK, but today i wanted to flash a V4 ulocked bootloader, following civato's guide. Everything was OK, except autorotation stopped working... I restored my backup through CWM, with 3.01 BL, and everything became normal again... Can some1 help me to flash a V4 BL?
P.S. also after restore i found another problem? the ACER logo during the loading turned into this any way to fix this?

Civatos guide worked well for me. I too am running RF1 with ics bl v4.
His guide has 2 methods. Are you using the nvflash method or the blackthunder apx tool method?
That screen is a common issue running hc bl's on ics roms, nothing to worry about really.

starkiller86 said:
Civatos guide worked well for me. I too am running RF1 with ics bl v4.
His guide has 2 methods. Are you using the nvflash method or the blackthunder apx tool method?
That screen is a common issue running hc bl's on ics roms, nothing to worry about really.
Click to expand...
Click to collapse
That display is common on the hc version of boot loader. Its because the kernel needed to be patched to allow root. Also you may see some display flicker on occasion. Normal.
Ver4 boot loader and new ics kernel fixes this..known issues with current ics is auto-rotate. May have to reinstall the from again. Not sure about flexreaper, but the stock ota updates have a lot of this. Usually they reset their tabs. But for you, I would reinstall the rom.

Moscow Desire said:
That display is common on the hc version of boot loader. Its because the kernel needed to be patched to allow root. Also you may see some display flicker on occasion. Normal.
Ver4 boot loader and new ics kernel fixes this..known issues with current ics is auto-rotate. May have to reinstall the from again. Not sure about flexreaper, but the stock ota updates have a lot of this. Usually they reset their tabs. But for you, I would reinstall the rom.
Click to expand...
Click to collapse
So, if I'm right, i should install a new v4 bootloader and a kernel? But as i remember the flexreaper rom since RF1 has an already patched kernel... In which order should i do this steps? Sry, it's my first android device, so im a newb for now.

kakodemon said:
So, if I'm right, i should install a new v4 bootloader and a kernel? But as i remember the flexreaper rom since RF1 has an already patched kernel... In which order should i do this steps? Sry, it's my first android device, so im a newb for now.
Click to expand...
Click to collapse
No, leave the bootloader alone. It;s ok, and has absolutely no effect on the auto-rotation.
I suggest, re-install the rom again till it works. This is an Acer thing. And it doesn;t effect all tablets. But it seems, the Acer OTA effected a lot of users.
Even on my 501 rom, I had 1 user out of 1000+ downloads, had the same issue. He re-installed the rom a few times, then magically 1 day, it started working correctly.

Moscow Desire said:
No, leave the bootloader alone. It;s ok, and has absolutely no effect on the auto-rotation.
I suggest, re-install the rom again till it works. This is an Acer thing. And it doesn;t effect all tablets. But it seems, the Acer OTA effected a lot of users.
Even on my 501 rom, I had 1 user out of 1000+ downloads, had the same issue. He re-installed the rom a few times, then magically 1 day, it started working correctly.
Click to expand...
Click to collapse
OK, ty, ill try it and tell u tomorrow what i've got

So, I flashed the ROM again - no effect, restored a backup and changed the kernel, which is aviable at flexreaper's page - no effect, autorotation still wont work(( Any ideas?

kakodemon said:
So, I flashed the ROM again - no effect, restored a backup and changed the kernel, which is aviable at flexreaper's page - no effect, autorotation still wont work(( Any ideas?
Click to expand...
Click to collapse
One person said put in portrait mode before flash.

shaun298 said:
One person said put in portrait mode before flash.
Click to expand...
Click to collapse
Already tried, no effect((

Sadly, i still cant make i work with unlocked ICS bootloader

go back to stock ics non-rooted?

I'm probably gonna have to send in my tablet for repair and I've rooted and installed flexreaper's R14 from for ics.I bought the tablet about a month ago it had honeycomb idk if there's a way I can get back to that if not can I get back to stock ics and how can I unroot my tab?

The better way is restore the official rom, you can do it with the downgrade to 3.0.1 unstable.. Which bootloader? HC or ICS?
If you have HC, make the downgrade and then the OTA update or flash a totally stock non-rooted rom (Androonay - vache's site), everything will be stock..
I've done the same 2 days ago e no issues

I think I have the ice boot loader I'm not sure though how can I tell?

rcraig617 said:
I think I have the ice boot loader I'm not sure though how can I tell?
Click to expand...
Click to collapse
Launch Acer Recovery Installer v2.74, it should show which bootloader you have.
If is 3.01 -> HC

Boot loader Version=0.03.12-unl is what it says

rcraig617 said:
Boot loader Version=0.03.12-unl is what it says
Click to expand...
Click to collapse
It's an ICS bootloader unlocked
Sent from my Packard Bell [email protected] v169 using Tapatalk

So can I go back to stock ics and if so how? Also will they know I rooted if I send in my tab if so I wanna unroot also if any can help me.

I'm wondering the same thing. CWM rev1.3.4 by thor2002ro bootloader version is 3.01 is what I have on mine.

Use one of the TimmyDean APX Packages with your UID and you can flash the unstable 3.0.1 build. Then install Acer Update Enhancement (either from the market or from the Acer website via the APK download) and update to OTA ICS

http://forum.xda-developers.com/showthread.php?t=1632392&highlight=timmydean
would this work?

rcraig617 said:
http://forum.xda-developers.com/showthread.php?t=1632392&highlight=timmydean
would this work?
Click to expand...
Click to collapse
That's the rooted package. On second thoughts - head to vache's download link thread and scroll down to the EUU section
Sent from my Iconia A500 using Tapatalk 2

Similar situation... almost
I am in a very similar situation as the OP except my hardware problem is that both the USB and microUSB have quit on me. Without being able to use APX mode, I'm pretty hosed... right? Anyone want to place an over/under on Acer ignoring the unlocked bootloader and fixing the defective USB module?

You could also use afterOTA found here.
http://forum.xda-developers.com/showthread.php?t=1675939
and it walks you through going completely stock, although why are you sending it in? I have sent a couple things back for screen replacements and they didn't care it was running custom ROMS. But that tool should do the trick for you.

I just got the tab a month ago and my speakers randomly stopped working on me I wanna send it in while I still have warranty

mastashake said:
I am in a very similar situation as the OP except my hardware problem is that both the USB and microUSB have quit on me. Without being able to use APX mode, I'm pretty hosed... right? Anyone want to place an over/under on Acer ignoring the unlocked bootloader and fixing the defective USB module?
Click to expand...
Click to collapse
You can fix that. MicroSD
Stick on a MicroSD a stock Acer ICS Leak ROM and flash it in CWM
Then once flashed, it'll automatically flash the stock bootloader and when it boots it'll flash the stock recovery back! Then reboot it and do the Volume Up / rotation lock toggle to wipe all your data off then it's completely stock!
Sent from my Iconia A500 using Tapatalk 2

[Q] A500 Kills battery in a day of no use after flashing ICS BL v8

Hi guys, hoping someone could help me out here.
I was running my tablet on ICS before with the HC bootloader (I believe it was Tablooney) and of course I was stupid and didn't make a backup.
long story short I flashed the bootloader and started experiencing random issues where the tablet would not wake up, thought ok maybe I missed a wipe of cache, battery stats, or dalvik-cache, or something. did the wipes that wouldn't kill my rom and still had the same problem.
did a full wipe and used a JB rom, still same issue
had some weird issue, restored to HC BL and rom, tried to do OTA to ICS (used EUU to go back) Tablet would not see the OTA ICS update.
so tried a third rom, still same problem. does anyone have any suggestions or insight as to why this is happening?
Thanks!

BlueWyvern said:
Hi guys, hoping someone could help me out here.
I was running my tablet on ICS before with the HC bootloader (I believe it was Tablooney) and of course I was stupid and didn't make a backup.
long story short I flashed the bootloader and started experiencing random issues where the tablet would not wake up, thought ok maybe I missed a wipe of cache, battery stats, or dalvik-cache, or something. did the wipes that wouldn't kill my rom and still had the same problem.
did a full wipe and used a JB rom, still same issue
had some weird issue, restored to HC BL and rom, tried to do OTA to ICS (used EUU to go back) Tablet would not see the OTA ICS update.
so tried a third rom, still same problem. does anyone have any suggestions or insight as to why this is happening?
Thanks!
Click to expand...
Click to collapse
Maybe I have an answer.
1. After returning to stock, you should have installed Acer Update Enhancer from the Play Store. Without it, you won't get OTA.
2. Early release of the ICS had some SOD issues kernel related. The current ICS roms shouldn't have this anymore. However they require the V8 unlocked bootloader. Also, they use modified kernels.
Make sure you have V8 installed, An appropriate CWM recovery like Thor 1.7.2 or .3. Do your wipes, then install one of Civato's Roms. His are current builds. And, Do ALL your wipes in CWM as per the OP instructions.
MD

Moscow Desire said:
Maybe I have an answer.
1. After returning to stock, you should have installed Acer Update Enhancer from the Play Store. Without it, you won't get OTA.
2. Early release of the ICS had some SOD issues kernel related. The current ICS roms shouldn't have this anymore. However they require the V8 unlocked bootloader. Also, they use modified kernels.
Make sure you have V8 installed, An appropriate CWM recovery like Thor 1.7.2 or .3. Do your wipes, then install one of Civato's Roms. His are current builds. And, Do ALL your wipes in CWM as per the OP instructions.
MD
Click to expand...
Click to collapse
That Update enhancer did the trick to take me to ICS. Then I used afterota to get rooted (which also flashed my boot loader) and now I have ICS, root, and the v8 BL!
Thanks MD!