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.
Hello,
today I got my Viewpad 10s (same as Advent Vega). I rooted it and installed the new Vegacomb 3.2. Everything worked just fine an Vegacomb was insane! Then I had an bad idea and downloaded Rom Manager to install the newest Clockwork Revocery. In Rom Manager I had to choose between two devices, when I wanted to instal CWM (g tablet Version and something other, I thought they are the same ). When I restarted the device there was just a black screen. I can't go in the recovery anymore and sometimes the backlight comes on. What should I do? Please help
just reflash the stock rom, should be fine.
Just done exactly same thing ref CWM. Have I got to lose everything I had data wise and start from original stock rom?
Sweep29 said:
Just done exactly same thing ref CWM. Have I got to lose everything I had data wise and start from original stock rom?
Click to expand...
Click to collapse
Afraid so.
Ok thanks for the good news. Lol. At least it fixable.
Might as well update to 3.2 v9n then...
thanks for the information, last night I also wrongly installed CWM version 4.x.x.x
HELP PLEASE!!!! I have the Samsung galaxy tab 7.7 verizon LTE sch - i815 version and im losing hope quickly. Im not sure which way to take to get a working tablet again. Im kind of a noob but have rooted and flashed many devices. Sorry if my thoughts are rambling or all over, but its been a long three days trying to get this to function and im not there yet so id appreciate any help I can get!
Here is what my sch i815 can do:
1) Get into recovery
2) Get into download mode
3) Restore backups that end up getting bootlooped with splash page
4) Install roms that end up in blootloop with the splash page.
5) Flash recoveries with odin
6) Charge tablet battery
One issue is when im trying to wipe before I install cm9 for the i815. When im in recovery and ive tried the p6800 and the i815 with same results, when I try to WIPE data / factory reset the tablet gets to “FORMATTING / DATA” AND THE TABLET REBOOTS TO THE SPASH SCREEN AND GETS STUCK THERE.
My problem is I tried to put the p6800 ics on my tablet and didn’t realize it wasn’t compatible with the sch i815. At first some of the p6800 roms would at least get past the Samsung galaxy tab 7.7 screen, but now its basically stuck there. The only rom or anything that boots past that is the cm9 for the i815. But that just boot loops from Samsung flash screen to start of cm9 and then back to flash screen. I had a backup that worked fine but now it installs the backup and get stuck at the flash screen only. I don’t know if I should try to get cm9 to load past the splash screen boot cycle or find a file to flash with odin which I see there really isn’t any for this model. I did find some posts about a cwm backup file 2012-05-06.22.48.58 and I cant get that to restore either.
When I try to do the zip that is floating around for cwm backup, I try to apply the backup 2012-05-06.22.48.58 and it says checking md5 sums… for a few minutes, then it says md5 mismatch!
I guess any help would be greatly appreciated. I see that I could try to get back to 3e recovery but I cant get anything on the internal sd card because I cant get anything to boot. Thanks for everyones time!!
Have nothing else in the subdirectory that has the recovery. Only the recovery. Nothing else.
me too
Same issue almost exactly with mine.
Got ICS installed OK and it was working fine then started to spontaneously reboot
I cannot restore nandroid backups that worked yesterday
Also interesting that when I try to format data in cwm it reboots
Now I can get an install of cm9 to complete but I'm left with a boot loop
This is an i815
I'm thinking partition table got jacked up
Any ideas out there ?
Thanks
schillaj said:
HELP PLEASE!!!! I have the Samsung galaxy tab 7.7 verizon LTE sch - i815 version and im losing hope quickly. Im not sure which way to take to get a working tablet again. Im kind of a noob but have rooted and flashed many devices. Sorry if my thoughts are rambling or all over, but its been a long three days trying to get this to function and im not there yet so id appreciate any help I can get!
Here is what my sch i815 can do:
1) Get into recovery
2) Get into download mode
3) Restore backups that end up getting bootlooped with splash page
4) Install roms that end up in blootloop with the splash page.
5) Flash recoveries with odin
6) Charge tablet battery
One issue is when im trying to wipe before I install cm9 for the i815. When im in recovery and ive tried the p6800 and the i815 with same results, when I try to WIPE data / factory reset the tablet gets to “FORMATTING / DATA” AND THE TABLET REBOOTS TO THE SPASH SCREEN AND GETS STUCK THERE.
My problem is I tried to put the p6800 ics on my tablet and didn’t realize it wasn’t compatible with the sch i815. At first some of the p6800 roms would at least get past the Samsung galaxy tab 7.7 screen, but now its basically stuck there. The only rom or anything that boots past that is the cm9 for the i815. But that just boot loops from Samsung flash screen to start of cm9 and then back to flash screen. I had a backup that worked fine but now it installs the backup and get stuck at the flash screen only. I don’t know if I should try to get cm9 to load past the splash screen boot cycle or find a file to flash with odin which I see there really isn’t any for this model. I did find some posts about a cwm backup file 2012-05-06.22.48.58 and I cant get that to restore either.
When I try to do the zip that is floating around for cwm backup, I try to apply the backup 2012-05-06.22.48.58 and it says checking md5 sums… for a few minutes, then it says md5 mismatch!
I guess any help would be greatly appreciated. I see that I could try to get back to 3e recovery but I cant get anything on the internal sd card because I cant get anything to boot. Thanks for everyones time!!
Click to expand...
Click to collapse
fixed
OK Fixed!
how to:
Download android sdk to get adb.
Once you get adb ( adb is an executable program ).
Put tab in recovery mode ( I'm using CWM recovery ). If in CWM goto mounts and storage but dont mount anything.
then ( with tab connected via usb to computer with adb ) run this command:
adb shell e2fsck -yfDC0 /dev/block/mmcblk0p10
For me this fixed some jacked up inodes
Once this was complete I was able to do a full wipe without reboot, reinstall ics and it came back up all good
Hope this helps
tr2ride said:
Same issue almost exactly with mine.
Got ICS installed OK and it was working fine then started to spontaneously reboot
I cannot restore nandroid backups that worked yesterday
Also interesting that when I try to format data in cwm it reboots
Now I can get an install of cm9 to complete but I'm left with a boot loop
This is an i815
I'm thinking partition table got jacked up
Any ideas out there ?
Thanks
Click to expand...
Click to collapse
tr2ride said:
OK Fixed!
how to:
Download android sdk to get adb.
Once you get adb ( adb is an executable program ).
Put tab in recovery mode ( I'm using CWM recovery ). If in CWM goto mounts and storage but dont mount anything.
then ( with tab connected via usb to computer with adb ) run this command:
adb shell e2fsck -yfDC0 /dev/block/mmcblk0p10
For me this fixed some jacked up inodes
Once this was complete I was able to do a full wipe without reboot, reinstall ics and it came back up all good
Hope this helps
Click to expand...
Click to collapse
OK. Great to hear. I'll try tonight after work. Which ics are I running by the way? Cm9 or the i815?
I'm running the cm9 for i815 from this thread:
http://forum.xda-developers.com/showthread.php?t=1542911
works great except for the lack of GPS and LTE, I can live without LTE by tethering but GPS is a show stopper for me so I'm likely going to revert to Honeycomb
tr2ride said:
I'm running the cm9 for i815 from this thread:
http://forum.xda-developers.com/showthread.php?t=1542911
works great except for the lack of GPS and LTE, I can live without LTE by tethering but GPS is a show stopper for me so I'm likely going to revert to Honeycomb
Click to expand...
Click to collapse
ok, yeah does hdmi work on cm9? if not i will want honeycomb also. Do you havea rom for that? or how would i revert back to that? Thanks for all your time and help!~
i keep getting bootloop from cm9 and i dont know why.....
i got it to work with your command, but i installed cm9 for the i815 and i get a bootloop and now im back to where i was again with the rebooting in cwm and cant restore my backups...
Hello guys,
yesterday i updated my stock 3.2.1 a501 with ota ics 4.0.3 stock and and everything went well.
After this, i tried to root it with afetrota, but because of the lack of attention in doing it, i made an error and i bricked.
Booting i see a message: "boot verified failed" and nothing more happen.
I tried an hard reset and other things but unsuccessful.
In apx mode, i tried to load, alwayas with afterota an update.zip using sono files but on reboot the message is an illegal blob and update stop.
Anyone can help me to get out of this somehow?
I think boot loader in ics now, but i'm not shure...what can i do?
Thanks all in advance
Massimo
p.s. sorry for my bad English
Ok, after a loto of try, errors, ect, I'm back to hc 3.0.1 unstable.
But...a new problem i don't remind the way to back to a501 stock to get ota updates....in a few words to back like my tablet was unpacked first time
Thank for help.
Oh man, your going to either have to run tlss little honey ( stock but rooted) or put on a custom rom, you will need root for this good luck
Sent from my A501 using xda app-developers app
Thank you for your reply.
Now the problem is solved....finally
Regards
This thread could be deleted thanks