Database Info

Tiamat help

Hi, a little confused on how 2 install tiamat on my uk xoom 3g.
Basically I followed this guide and rooted my xoom, i flashed using the boot the op listed. - http://forum.xda-developers.com/showthread.php?t=1049901
Ok, now I am looking at tiamat 1.4.1 and it mentions tiamat boot files and tiamat kernels.
My question is this, can I just install tiamat 1.4.1 kernel using CWM on an SDcard, will it work with the boot file i flashed on the site listed above or do I need to flash a tiamat boot file and will this be compatable with the UK 3G XOOM
So confusing.
Anyone please help. Thank you

dhicks19 said:
Hi, a little confused on how 2 install tiamat on my uk xoom 3g.
Basically I followed this guide and rooted my xoom, i flashed using the boot the op listed. - http://forum.xda-developers.com/showthread.php?t=1049901
Ok, now I am looking at tiamat 1.4.1 and it mentions tiamat boot files and tiamat kernels.
My question is this, can I just install tiamat 1.4.1 kernel using CWM on an SDcard, will it work with the boot file i flashed on the site listed above or do I need to flash a tiamat boot file and will this be compatable with the UK 3G XOOM
So confusing.
Anyone please help. Thank you
Click to expand...
Click to collapse
Use this thread. http://forum.xda-developers.com/showthread.php?t=978013
Download the kernel of your choice and one of the two boot images for Verizon 3G. Reports in the thread say it works just fine for Euro 3G as well.
Put both the new kernel and the boot image on your external SD card. Flash the new boot image and then the new kernel in CWM, then reboot. That is all there is to it.

many thanks thats helped quite a bit, one more thing though, it says boot image is for android 3.1 only, the uk xooms have 3.0.1.
I am looking here http://bigrushmods.com/tiamat.html
to download kernel 1.4.2
and then i just download the 3g boot image below it?
Thank!!!

dhicks19 said:
many thanks thats helped quite a bit, one more thing though, it says boot image is for android 3.1 only, the uk xooms have 3.0.1.
I am looking here http://bigrushmods.com/tiamat.html
to download kernel 1.4.2
and then i just download the 3g boot image below it?
Thank!!!
Click to expand...
Click to collapse
Ah...yes you would need to upgrade to 3.1 first. Either use one of the methods found in the forum (such as http://forum.xda-developers.com/showthread.php?t=1089695) or wait until the Euro upgrade reaches the UK.

Ok, so there is not way I can get taimat on 3.0.1? I have read and people have done this. Just need to find how.
So if I flash just the kernel without the tiamat boot file will that work? Its rooted and unlocked.
:S
sorry for all the questions, just this is so confusing for a new user.
Cheers mate much appreciated

dhicks19 said:
Ok, so there is not way I can get taimat on 3.0.1? I have read and people have done this. Just need to find how.
So if I flash just the kernel without the tiamat boot file will that work? Its rooted and unlocked.
:S
sorry for all the questions, just this is so confusing for a new user.
Cheers mate much appreciated
Click to expand...
Click to collapse
No the kernel is for 3.1. You will need to upgrade to 3.1 first, one way or another.
Sent from my GT-I9000 using XDA Premium App

For instance:
http://www.xoomforums.com/forum/motorola-xoom-development/3068-kernel-tiamat-1-4-1-3-0-1-only.html
That version will work on 3.0.1.
So can I flash that version of kernel without the taimat boot file?
Or is there a version of boot file that works on the 3.0.1.
Thanks for helping clearing this up for me.

dhicks19 said:
For instance:
http://www.xoomforums.com/forum/motorola-xoom-development/3068-kernel-tiamat-1-4-1-3-0-1-only.html
That version will work on 3.0.1.
So can I flash that version of kernel without the taimat boot file?
Or is there a version of boot file that works on the 3.0.1.
Thanks for helping clearing this up for me.
Click to expand...
Click to collapse
On the Xoom forum search for tiamat 1.3.1 and follow the instructions for flashing it. That will give you SD support and overclocking with android 3.0.1.
Then if you wish to, flash tiamat 1.4.1 according to instructions on zoom forum.
No new boot image is needed for either, it appears.
Sent from my GT-I9000 using XDA Premium App

Right, i tried flashing the 1.3.1 taimat as suggested and it locked up at dual core screen again.
So i took a stab in the dark and went straight to install the 1.4.1 from micro sd and its working fine, wifi, 3g and its overclocked.
thanks for your help

Sorry to jump into this thread at such a late stage. I have a similar issue in that when I flash the boot.img for the Tiamat 1.3.1 rom, I get stuck at the boot screen (dual core etc).
How did you manage to install 1.4.1 from the micro sd if you are running a kernel that does have sd support yet? What steps did you take?
Thanks

wazzosan said:
Sorry to jump into this thread at such a late stage. I have a similar issue in that when I flash the boot.img for the Tiamat 1.3.1 rom, I get stuck at the boot screen (dual core etc).
How did you manage to install 1.4.1 from the micro sd if you are running a kernel that does have sd support yet? What steps did you take?
Thanks
Click to expand...
Click to collapse
Will try and help here from what i remember.
First follow these instructions to get it working again >
Download his boot and flash - http://forum.xda-developers.com/showthread.php?t=1049901
I then downloaded and flashed clockworkmod.
I then put an sd card in my pc, put the tiamat 1.4.1 file on it, booted into clockworkmod recovery mode and then simply selected the sd card installed the tiamat from there.
Thats the basics of it and to my suprise it worked.
Hope this helps a little, just research clockworkmod and how to install etc.

I found the easiest way was to go to the AU 3.1 first, then root and clockworkmod it, then go to tiamat 1.1 then finally 2.0, then the 2.0.1 update for maps. went very smoothly.
Lordao

I took a guess yesterday and went for it. I ended up using the boot.img from the Tiamat 1.4.0 package. My xoom was happy with this and didn't get stuck at the bootloader screen. Then I installed the rest of the 1.3.1 Rom, then upgraded to 1.4.1. So I am all good on 1.41.
However I'm thinking about applying the 3.1 upgrade and then trying a newer tiamat kernel.
EDIT - I did end up using clockwork recovery. That thing is awesome.

Nothing happens when I flash anything

I have tried, through Clockwork Recovery, to flash several ROMs and kernels.
I tried a Tiamat ROM. Looked promising. After flashing it and rebooting, the screen showed the proper custom boot animation and then it went into Honeycomb. Everything was the same as before. Looking in system information, it still says that I'm on stock 3.1 and using the stock kernel. I tried the Tiamat kernel and the Blue ROM, same thing, it just never changes anything except the boot animation.
Troubleshooting I've done:
Tried to flash it with older versions of CW recovery
Tried to flash it through ROM manager
Anybody know why it's doing this ****? It's rooted 3.1.

How did you root?

I used this
http://forum.xda-developers.com/showthread.php?t=1073884
I can confirm that the root is working perfectly fine.

Do you have access to your external SD card from honeycomb os?

The U.S. 3.1 doesn't work with MicroSD cards...does it?
EDIT: Nope, it doesn't work still. Just tested.

Do you have superuser? If not, you may want to reroot again. Something, may not have worked properly the first time.

cam30era said:
Do you have superuser? If not, you may want to reroot again. Something, ay not have worked properly the first time.
Click to expand...
Click to collapse
Yep, I got superuser. ROM Manager even makes Superuser ask for root privileges before rebooting to flash, so I know that the root method I know isn't the issue.

I'm having the same problem.
I tried flashing the kernel, ROM, anything - it won't work. It just boots back to stock. But now I have a problem my wifi has an error.

Arrgh! The problem is RomManager's CWM. You actually CAN get it to flash things if you go into "mounts and storage" and mount /system and /data and all of that but DON'T. It will not work out well because it can not properly wipe system and you will wind up with a wifi kernel version mismatch (which will display as "wifi error" in settings). You need to flash the Tiamat CWM recovery from fastboot. I detailed the process for another person in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo
By the way, you will have to do a full wipe of ALL of your internal storage (so make a backup on your computer) and flash the ROM from an SD card.
Sent from my Xoom using Tapatalk

mikeserv said:
Arrgh! The problem is RomManager's CWM. You actually CAN get it to flash things if you go into "mounts and storage" and mount /system and /data and all of that but DON'T. It will not work out well because it can not properly wipe system and you will wind up with a wifi kernel version mismatch (which will display as "wifi error" in settings). You need to flash the Tiamat CWM recovery from fastboot. I detailed the process for another person in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo
By the way, you will have to do a full wipe of ALL of your internal storage (so make a backup on your computer) and flash the ROM from an SD card.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thanks mikeserv, I'm so glad you are helping people who get snagged by that CWM recovery. It was a nightmare, and I've on a tear about it.

[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

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.

[Q] Stuck in CWM Loop 5.8.3.4

Hi Guys,
After flashing Revolver in CWM , it started putting me on a reboot loop. I've searched and all the fixes require some sort of .zip file and a reflash. This is not working for me as CWM does not detect my SD card thus I am unable to put these fixes onto my device.
What can I do to get out of this horrible reboot loop ?
Cheers
Firmin

welcome Firminator,
did you try this?
http://forum.xda-developers.com/showthread.php?t=1688012

Thanks,
I managed to fix it through a cold boot + one of the patches.
However no matter how many times I try it. Revolver still doesn't flash properly and I still end up with the stock ROM.

I have the same problem, how do you do a patch? Im pretty new so any help would be greatfull. I see where roach has a code that supposedly fixes this but i don't know how to use it. Thank you

Firminator said:
Hi Guys,
After flashing Revolver in CWM , it started putting me on a reboot loop. I've searched and all the fixes require some sort of .zip file and a reflash. This is not working for me as CWM does not detect my SD card thus I am unable to put these fixes onto my device.
What can I do to get out of this horrible reboot loop ?
Cheers
Firmin
Click to expand...
Click to collapse
Where is this CWM 5.8.3.4 coming from? If it's ROM Manager then that is probably your biggest problem. ROM Manager is known to bring mostly problems to the Transformer. Use either Roach's latest fixed version Touch Recovery if you can get by with only internal sdcard access or Rogue XM's latest Touch Recovery if you need access to internal and external sdcards.
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
Richbyrd1981 said:
I have the same problem, how do you do a patch? Im pretty new so any help would be greatfull. I see where roach has a code that supposedly fixes this but i don't know how to use it. Thank you
Click to expand...
Click to collapse
This post explains how to fix the boot loops:
http://forum.xda-developers.com/showpost.php?p=23339963&postcount=249
It requires that you have adb setup and are able to access your device through adb while in Recovery.

Used Easyflasher and flashed CWM for a permanent fix.
Installed Megatron , OCed . All is well.

I give up - selling tablet on ebay
For those of you who can fix this problem, have an otherwise perfectly functional Asus TF101 up for sale on eBay, seller "wiegie." I only hope that someone can get it working and usable again.