Database Info

[Q] Tiamat 3.1 > 3.2

I have the Tiamat kernel with 3.1 on my US WiFi Xoom.
What is involved in getting the 3.2 update? Do i need to wait for the next version of Tiamat that supports 3.2, or can i upgrade normally and keep Tiamat/root?
Xoom is my first android device, so im not sure on how it all works.

in order to upgrade from 3.1 to 3.2 your gonna have to return to a stock kernel, and rom. Afaik, tiamats kernel does not work with 3.2 yet. But rest assured there will be new kernels for 3.2 soon

Thanks eliteone.
Does that mean if my Xoom says there is an update i should ignore it? Or will it not even detect the update?

Namheul said:
Thanks eliteone.
Does that mean if my Xoom says there is an update i should ignore it? Or will it not even detect the update?
Click to expand...
Click to collapse
You probably won't see the update notification since you're on Tiamat.
If you do see it you should ignore it.

eliteone said:
in order to upgrade from 3.1 to 3.2 your gonna have to return to a stock kernel, and rom. Afaik, tiamats kernel does not work with 3.2 yet. But rest assured there will be new kernels for 3.2 soon
Click to expand...
Click to collapse
xjack said:
You probably won't see the update notification since you're on Tiamat.
If you do see it you should ignore it.
Click to expand...
Click to collapse
Thanks to both of you. Will just wait till the Tiamat kernel supports 3.2.

The current Clockwork update-able 3.2 ffor WiFi will install over a 3.1 with the Tiamet Kernel and will replace the kernel with the stock one. So basically you end up with a stock system that is rooted. I wasn't running their custom ROM, just the custom kernel and the V05 update went flawless.

KerryG said:
The current Clockwork update-able 3.2 ffor WiFi will install over a 3.1 with the Tiamet Kernel and will replace the kernel with the stock one. So basically you end up with a stock system that is rooted. I wasn't running their custom ROM, just the custom kernel and the V05 update went flawless.
Click to expand...
Click to collapse
I had the same setup, and my xoom looped on the boot animation after i flashed. I had to do a factory reset/wipe data from CWM to get my xoom to boot properly. So now I'm reinstalling all my apps and settings.

I tried to flash the tiamat 2.0 yesterday, but my com then just froze at the dual corenscreen. I reflashed the old 1.4.5 tiamat and its back to normal now.
How exactly do I upgrade to 3.2 from 3.1 with tiamat 1.4.5? Its all way too confusing.

Namheul said:
I tried to flash the tiamat 2.0 yesterday, but my com then just froze at the dual corenscreen. I reflashed the old 1.4.5 tiamat and its back to normal now.
How exactly do I upgrade to 3.2 from 3.1 with tiamat 1.4.5? Its all way too confusing.
Click to expand...
Click to collapse
Use this method.
http://forum.xda-developers.com/showthread.php?t=1165998
Copy to your external sd card and rename it update.zip, boot into CWM recovery, wipe user data/factory reset, wipe cache, flash update.zip and reboot. It should work. You could also flash the new Tiamat Katana kernel 2.0 which is only for Honeycomb 3.2 after that.
Good luck!

xjack said:
You probably won't see the update notification since you're on Tiamat.
If you do see it you should ignore it.
Click to expand...
Click to collapse
I am on Tiamat, and just got the 3.2 update notification on my wi-fi only Xoom! I was very surprised since I am on Tiamat, plus removed a ton of "bloatware". I am just ignoring the notification every time it pops up. I suspect if I do go w/ it though, that it will fail... ? Anyone get that far to find out?? lol

I have a dumb question....do you HAVE to use an external microsdhc card to flash updates? You can't use the internal 32GB '/sdcard' ???
I am using CWM 4.0.0.4 and it seems to read the updates and install, but when i reboot nothing has happened....
Also, the ROM install appears to finish in about 5 seconds, way too short for something that is 100MB...

techs1200 said:
I have a dumb question....do you HAVE to use an external microsdhc card to flash updates? You can't use the internal 32GB '/sdcard' ???
I am using CWM 4.0.0.4 and it seems to read the updates and install, but when i reboot nothing has happened....
Also, the ROM install appears to finish in about 5 seconds, way too short for something that is 100MB...
Click to expand...
Click to collapse
No (I need to create a macro, or cut and paste, I've said this so many times) you really need an external microsd card and you need to install the Tiamat CWM Recovery R4c 3.2.0.0. That's the one that works with the external micro sdcard and works with the Tiamat kernels and roms. The 4.x.x.x. version does not see your micro sdcard and won't flash anything to your Xoom.

[Q] Rooted Stock 3.1 Xoom to Team Tiamat Manta Ray Kernel

Hello,
I am very confused as to whether or not it is possible to go from my rooted US Xoom Wifi only running rooted stock 3.1 directly to the Manta Ray rom, or do I go to stock rooted 3.2 first? Whatever the case, could someone link me to the correct procedure? I cannot find something that matches my exact setup, and the Rom's thread is unclear whether I have to update first. Yes, I know, this is probably a noob question, but I am pretty new to rooting in general.
Does anyone how to do this?

merauder75 said:
Hello,
I am very confused as to whether or not it is possible to go from my rooted US Xoom Wifi only running rooted stock 3.1 directly to the Manta Ray rom, or do I go to stock rooted 3.2 first? Whatever the case, could someone link me to the correct procedure? I cannot find something that matches my exact setup, and the Rom's thread is unclear whether I have to update first. Yes, I know, this is probably a noob question, but I am pretty new to rooting in general.
Does anyone how to do this?
Click to expand...
Click to collapse
Since you're rooted your bootloader is already unlocked
Just flash CWM 3.2.0.0 RC4
Wipe from CWM
Load Tiamat.
It should be that easy.

Ok, so the manta ray package is the whole system image for 3.2? Will it work essentially like an update?
EDIT: Also, just for clarification, I use wipe data/factory reset, and then put the rom on a microSD, then flashing it by doing what, exactly?

merauder75 said:
Ok, so the manta ray package is the whole system image for 3.2? Will it work essentially like an update?
EDIT: Also, just for clarification, I use wipe data/factory reset, and then put the rom on a microSD, then flashing it by doing what, exactly?
Click to expand...
Click to collapse
If you're downloading the Team Tiamat Mantay Ray 2.0.1 ROM - Yes, it includes everything.
You will boot into CWM recovery 3.2.0.0 RC4, do you have that installed? If not, please flash it first.
Then you flash the rom from CWM itself, after booting into CWM. Have the rom zip package on the flash card.
If you need more explicit instructions, they can be pieced together from the CWM thread and the Tiamat rom thread

Alright, got CWM 3.2.0.0 RC4 installed, now, for the part that scares me..Im gonna flash the Tiamat img now.

merauder75 said:
Alright, got CWM 3.2.0.0 RC4 installed, now, for the part that scares me..Im gonna flash the Tiamat img now.
Click to expand...
Click to collapse
dont be scared
wipe first (from recovery menu option)
then load the rom .img
join #xoom on irc.freenode.net if you need help

[Q] Downgrade From Android 3.2 to 3.0.1

Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!

mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Look, there's obviously something else going on with your Xoom that is not related to the Honeycomb version you have updated to. My suggestion is to very logically figure out what may have happened to get you stuck so we can get you unstuck.
Of course, if you go to the Moto Dev site you can download the stock images for your Xoom model (be careful to choose the correct model) and flash them through fastboot.
Don't relock.
You can reroot at HC3.01 or you can OTA update to 3.1/3.2 as desired and then root.
It's all up to you.

I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?

mattberman said:
I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?
Click to expand...
Click to collapse
Quick question: are you using CWM Recovery to flash the zip files, and if so what version of recovery do you have installed?
The version which works best for the Xoom is v3.2.0.0 R4c. However if you "updated" through Rom Manager to v4.0.0.X, that version is incompatible with the external sdcard and if you are trying to flash from your internal sdcard, it will seem like it's working but will not work, will just hang or revert to previous state. So maybe I'm really off base...you seem to know a lot...but I've seen similar problems caused by that bad recovery version.

I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.

mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.

mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Worst logic EVAR

mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot

rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
He doesn't have his microsd card yet. But might as well get ready.

okantomi said:
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.
Click to expand...
Click to collapse
Sorry if I was unclear, I am not using any zip files anywhere in the flashing process, except when dealing with the ramdisk. I've done this many times before with other devices, I'm not completely new to the process.

rockhumper said:
Worst logic EVAR
Click to expand...
Click to collapse
How is that bad logic? If something isn't working as it should, go back to the last stable point when it did.
rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
I could try this but how would that help? Do I need a custom recovery image to flash a new kernel? It won't work with stock? I'll give it a shot, thanks for the input. Okantomi, he's talking about the recovery .img file (flashed via fastboot), and not the .zip via CWM (I think).

Just get a 2gb or 4gb sd card, or borrow one from a phone, it's pretty simple...

To go back just grab the stock images from my sticky. Fastboot flash them, wipe cache and start over.
Sent from my PG86100 using Tapatalk

Stuck in boot loop after rooting Xoom 32GB Wifi (Cdn model)

Hi guys,
I followed the guide here after confirming I had Android 3.1 installed on my Xoom 3.2GB wifi only (Cdn market):http://forum.xda-developers.com/showthread.php?t=1078019&highlight=bootloop
I am able to load ClockworkMod no problem, and I flashed the WiFi_RootTool_3.1.zip no problem and it scrolled through it's text and told me it was done. I then told ClockworkMod to reboot.
However, upon reboot my Xoom is stuck in infinite 'boot loop' - Can anyone provide some thoughts on how to Root it? I've returned it to stock and tried doing it again, but with the same problem....

am0rak said:
Hi guys,
I followed the guide here after confirming I had Android 3.1 installed on my Xoom 3.2GB wifi only (Cdn market):http://forum.xda-developers.com/showthread.php?t=1078019&highlight=bootloop
I am able to load ClockworkMod no problem, and I flashed the WiFi_RootTool_3.1.zip no problem and it scrolled through it's text and told me it was done. I then told ClockworkMod to reboot.
However, upon reboot my Xoom is stuck in infinite 'boot loop' - Can anyone provide some thoughts on how to Root it? I've returned it to stock and tried doing it again, but with the same problem....
Click to expand...
Click to collapse
Check your version of CWM recovery. You are best off using the Tiamat custom recovery 3.2.0.0 R4c from here: http://forum.xda-developers.com/showthread.php?t=1074979 with an external microsd card. containing the file you want to flash in your Xoom. If you use Rom Manager, it will install v4004 which doesn't recognize the microsd card, and won't let you flash from it or back up to it. From your description, I'm guessing that that is your problem.
If this is not the problem and you have the right recovery file, and you are using the external microsd card in your Xoom to flash, then it may be that the zip file you are flashing is either a bad download or incomppatible with the 3.1 update on your Xoom. At any rate, once we figure out the cause we can solve the problem.

okantomi said:
If this is not the problem and you have the right recovery file, and you are using the external microsd card in your Xoom to flash, then it may be that the zip file you are flashing is either a bad download or incomppatible with the 3.1 update on your Xoom. At any rate, once we figure out the cause we can solve the problem.
Click to expand...
Click to collapse
My guess would be that the user is trying to use the Wifi root tool for the US 3.1 rom, to try to root the Canadian 3.1 rom, which is very different. There will definitely be problems with this method.
My suggestion would be to just install the Tiamat Hammerhead Rom, which will turn his xoom into a USA 3.2 xoom, and give him lots of useful features which the stock roms are lacking

also be patient...the screen loops for a good few minutes after a new root or ROM flash. Try waiting for five minutes...I was surprised at how patient I needed to be

Rom not installing

Hi I am a follower of LeeDroid on Sensation and thus far have always been able to find the answers to my questions without any issues. But now I am starting to dabble with root on Xoom. Needless to say I had a LOT of issues as it's not nearly as straight forward as my Sensation. I resolved most of my issues and am finally ready to install Team Tiamat's rom. Reboot into recovery, choose the zip and it freezes on Unpacking New Files.... I've been at this all night and really would like to go to bed knowing that it's installed and I can mess with it tomorrow. Any ideas?
Thanks so much for the anticipated help!

Like what excatly is happening? You do have the CWM recovery flashed to the recovery partition, right? What have you've done so far? What guide you've followed thus far?
Pretty much rooting the XOOM is pretty straight forward, unlock the bootloader (adb reboot bootloader, fastboot oem unlock, on xoom press volume down then up and repeat once to unlock), boot back into the bootloader and flash the recovery (adb reboot bootloader, fastboot flash recovery recovery_image_name.img, fastboot reboot), then reboot into the recovery and flash either the root files or the ROM you want to use.

^^^
Totally agree. Once custom recovery is installed flashing rom is same as with other devices:
Boot into recovery.
wipe data/reset
install zip
choose zip file
Done
................
Avoid flashing through rom manager.
You need to have custom recovery tailored for Xoom (not what is available through rom manager)
.................

The rooting process is done and I also have already flashed cwm. The problem is when I go into cwm through recovery and attempt to load the tiamat rom it freezes at the step "unpacking new files"....
Sent from my HTC Sensation 4G using Tapatalk

please check the md5 checksum (given from where you downloaded tiamat).
also flashing takes some time.
do not inturrupt.
Yesterday i flashed it and it took some time(even i thought it is doing nothing).
But it flashed ok.

rickm8384 said:
The rooting process is done and I also have already flashed cwm. The problem is when I go into cwm through recovery and attempt to load the tiamat rom it freezes at the step "unpacking new files"....
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
Have you checked your downloaded file. It may be corrupt.

It seems post no#5 & 6 posted at same time

rohit3192 said:
It seems post no#5 & 6 posted at same time
Click to expand...
Click to collapse
Great minds and all that!

Hehe...
BTW I have flashed international stock version over US MZ604.
It has last update of 3.1 with micro sd support.
It gives a choice of what to mount(internal or sd card)
2 extra wallpaper also there.
Let's see how it performs.

Are you using the correct version of the recovery? This seems to be a common mistake made by quite a few people. You need to be using this version and loading the ROMs and kernels to a Microsd card. "Newer" versions do not use the microsd card so you would be flashing from the same internal memory that you are trying to flash over.

HuckFinn said:
Are you using the correct version of the recovery? This seems to be a common mistake made by quite a few people. You need to be using this version and loading the ROMs and kernels to a Microsd card. "Newer" versions do not use the microsd card so you would be flashing from the same internal memory that you are trying to flash over.
Click to expand...
Click to collapse
What he said, read the pre-requisites very carefully on the ROM page. Also what ROM are you trying to download and what version of honeycomb are you currently running? What xoom? Wifi or 3g?

I was finally able to get it done. The issue it turns out was my own impatience coming out. I just had to be patient and eventually it installed.
Thanks for all the help everyone!!!
Sent from my HTC Sensation 4G using Tapatalk

rickm8384 said:
I was finally able to get it done. The issue it turns out was my own impatience coming out. I just had to be patient and eventually it installed.
Thanks for all the help everyone!!!
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
I'm glad it worked. I know what you mean about being impatient...sometimes it seems like nothings happening and in fact, you just need to hang in a little longer.