yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] mr_wrong_0:
This rom has the Desktop User Agent as default. Jetflicks checks to make sure you are using a mobile device so you need to change your user agent to show a phone. Just type in "about:debug" into the address bar of the browser. It will seem like nothing changed that unlocked some specific options in settings. So just click on the drop down menu and choose settings, then choose debug from the left side of the screen, you can then change your UA or User Agent to an Android device.

I love Jetflicks BTW!
[Xoom Android Development] cam30era:
Wifi tethering does work with no problems. But I prefer not to share my network when in a public place (like an airport). And USB tethering is faster than wifi tethering, in my experience. Thanks for asking.
[Xoom Android Development] fcoco32:
The 3g fix does fix the problem with the contacts on the wifi only model.
[Xoom Android Development] shmigao:
Cool

That means building a full euro 3g rom should be fairly easy

Wish one dev could pick it up..... :/ I can donate....
[Xoom Android Development] idkwhothatis123:
Wiped before flash. Can't get past dual core screen
[Xoom Android Development] xlGmanlx:
so i think Bwcorvus said we should wipe in clockwork right?
[Xoom Android Development] cam30era:
No. Do not wipe in CWM. There is a bug with CWM wipe that will prevent you from installing apps.
[Xoom Android Development] strat_player:
I agree with you on the not sharing comment. Thats why I use WPA/WPA2-PSK encryption on my wireless tether. I'll have to look into the USB tethering although I dont like the idea of having another cable to tote around but if its faster...

Any links to tuts on how to set up USB tethering?
[Xoom Android Development] cam30era:
Read the OP for the Tiamat 1.4.4 kernel. Basically, there's nothing to do besides plugging your android phone into the host cable and enabling USB tethering on your phone, and running the script that BRD posted. I updated my original post to indicate that I got it working. My bad, I forgot to run the script.
[Xoom Android Development] Elysian893:
edit: Disregard, I got it figured out finally without having to wipe.

BRD enjoy that $10 beer money I sent :cool:
[Xoom Android Development] ClydeB1:
I'm not sure what the actual power requirements of my drive are, but I have heard of users that can't get their drives to power up directly from the Xoom, so I guess it does depend on the drive itself. It's also only a USB2 device.
[Xoom Android Development] Brenardo:
i am running into a problem... It appears I have lost root access...
[Xoom Android Development] lpasq:
Much appreciated. Followed OP and enjoying rom as expected. Works as advertised. My US WiFi Zoom was already rooted w/bigrushdog3.1

...xoom posted...
[Xoom Android Development] Turkawa:
guys

for sake of making it clear,

i have already

CWM installed

1.4.4 kernel loaded an OC'ed

ad hoc flashed

usb mod flashed

do i need this rom?
[Xoom Android Development] headcheese:
No... But it sounds like you want it.

I flashed it cause it said winning in the op.
[Xoom Android Development] adamtuba:
Yes I had to push those files over too. I did it straight after installing the ROM though, before flashing the 3G fix zip.

And yeah, still stuck on 2 bars.
[Xoom Android Development] lpasq:
Dude. I flashed it because that's why I bought a xoom. To flash and run bleeding edge Android whatever. These devs have shown epic xoom love since day one while moto swims in quicksand. I didn't need to flash it same as you. My main two reasons: 1) I need a flash fix for my Android addiction and 2) I am excited to be prepped now to flash 1.x and beyond and to ride the hack/tweak/mod wave as it incrementally builds.

...xoom posted...
[Xoom Android Development] lokidokie:
My Experience...

Ok. I didn't exactly have a 'clean' install of this ROM either.

I just thought I'd post this in case it happens to help anyone in a similar situation.

Please... This is just my personal experience/insights.

I still recommend everyone follows Team Tiamat's instructions at first!!!

Then if you run into troubles similar to mine, try what I did...

I was coming from a rooted US Wifi-Only 3.1. I followed the suggested steps on page 1.

I did a nandroid.

Flashed the ROM.

Then got stuck on a bootloop.

Bugger. I need to wipe.

So I restored my nandroid so I could boot into honeycomb to do the factory reset from there (again, as suggested).

I flashed the ROM again...

And bugger, bootloop again!!

I was pretty sure that what I did was 'meant to work', so before freaking out and trying other stuff, I restored nandroid and completed the process again... And yes, I was stuck in another bootloop!!

Then I realised that after I did factory reset, I let the Xoom reboot up until the Welcome Screen. So I thought I'd try again (after restoring nandroid again...) to factory reset inside honeycomb.

But this time I watched it and after the wipe was complete and it was about to boot up (Moto Dual Core image), I pushed Vol- and booted to recovery.

Again, re-flashed ROM and rebooted.

And it booted!!!!! Woohoo!!! Fancy new ROM!!!

Thinking I was in the clear, I started repopulating my bare Xoom, and BOOM! I was getting a reboot whenever I installed apps from the market.

Bugger.

So I stuffed around with wiping and flashing for a bit more before I found a method that worked (for me).

This is what got it working (and still working/installing apps/generally pwning) for me...

1- Factory reset inside Honeycomb.

2- Don't let it boot up to welcome screen! Stop it at the Moto Dual Core image by pressing Vol-, then Vol+ to get into recovery. (this is the only way it would get past bootloop)

3- Flash ROM.

4- Boot into shiny new ROM, log into google account and try to install apps. If/when bootloop occurs,

5- Do factory reset again from inside honeycomb.

6- Enjoy!!!

Again, this is just my personal experience/insights.

I still recommend everyone follows Team Tiamat's instructions at first!!!

Then if you run into troubles similar to mine, try what I did...

Also, thanks to all involved in developing this ROM. I look forward to blindly following you into the future!!
[Xoom Android Development] jdale38:
Try a factory reset from fastboot (hold power button and volume down)...ull have to have the android sdk...was stuck on dual core logo and that worked for me
[Xoom Android Development] Alxoom33:
Thanks BRD and the Tiamat team. You are awsome and the directions you gave were flawless. I Flashed 1.0 on my wifi xoom and reebooted with no problems, It works great. Although I still have reeboots at 1.7 on the browser. However, I noticed that the battery is draining faster than the stock 3.1 with 1.4.4 and quadrent scores are a little lower, about 3700 vs 4900+ when running at 1.7 with a performance governor. Is the battery drain a bug in this ROM?

Also, is there an easy way to get the charging light back?
[Xoom Android Development] leglerreddin:
The problem with that is that I did change the us string using the before mentioned technique
[Xoom Android Development] Alxoom33:
Did you try going to an earlier version of CWM recovery. Version 4.0 has been reported to cause problems, which might account for what you have been experiencing. Try flasing version 3.0.025 in CWM. That's what I did before backing up my rom and flashing 1.0.

Also, DON'T WIPE!!! Good Luck!:D
[Xoom Android Development] nory82688:
Yes! Lol fellow crack flasher
[Xoom Android Development] sooner2k1:
I also lost root access coming from Tiamat 1.4. Has anybody else had this problem?
[Xoom Android Development] Almighty1:
You sure it was Superuser Elite that did it and not Superuser which had a update today. I updated Superuser and I'm still on the stock 3.1 rom on my WiFi XOOM and it replaced the su binary with version 2.3.1-efg which is incompatible with the Xoom. What happens when you type su as follows, it it getting you to the # prompt?

adb shell

$su

It should give back #, if it doesn't, and you get the following:

reloc_library[1315]: 2756 cannot locate '_mktemp'...

CANNOT LINK EXECUTABLE

then this is the fix atleast for me when I got the broken su. This su is something I extracted from the ROM file in the first post of this thread which is version 2.3.1-ef.

Download the attached su.zip and extract the su file from it to the same directory where you will run the adb command:

adb remount

adb push su /system/bin

adb shell rm /system/xbin/su

adb shell ln -s /system/bin/su /system/xbin/su

adb shell chmod 6755 /system/bin/su

and then try running su again.
[Xoom Android Development] sooner2k1:
I think I also made the mistake up updating SU, and then letting it install a new binary. I tried the steps mentioned in the process above, but for some reason my Xoom never accepts the adb shell, so I tried it leaving the "shell" off, but had no luck. Now i'm getting force closes. I think i've now boinked everything, and am now getting FC's for everything that requires root.
[Xoom Android Development] sooner2k1:
So I tried this again, and for some reason this line gives me trouble:

adb shell push su /system/bin

The message I get is "not found".

If I remove the "shell" from this line item and just use "adb push su /system/bin", then proceed with your directions exactly as they are stated, including the use of shell in the command, it works for me.

I wonder why it won't accept the shell in the push command.
[Xoom Android Development] Almighty1:
That was my fault, since I meant to type "adb push su /system/bin/", make sure you download the su.zip in my previous post and then extract the su file from the su.zip and place the su file in the same directory you are doing the adb command from.
[Xoom Android Development] Tesler32:
I am getting a 404 error on any game that uses openfient
[Xoom Android Development] romedundun:
i'm fairly certain the openfeint issues are due to the UAString changes..
[Xoom Android Development] BUMP THAT:
How can i put the stock battery back in the status bar?
[Xoom Android Development] ax0r:
This thread contains a framework-res.apk that is used for the contacts fix which reverts the battery icon back to stock
[Xoom Android Development] rschenck:
OK, my problem is this....flashed the ROM, rebooted into bootloops, so I realized I had to do a wipe, so tried to restore my Nandroid. Only problem is that it couldn't erase the boot.img so after much dancing around and strange problems I got booted up again and wiped data inside HC then went to recovery and flashed the ROM again then rebooted...still bootloops.

Any suggestions?
[Xoom Android Development] brandor:
Okay, I'm sorry I am pretty sure I am following your instructions correctly, I flashed the ROM, then the 3g fix, rebooted, tried installing a market apk and it rebooted, so I let it boot up went into settings>privacy>factory data reset> did the reset> rebooted into CWR> flashed the ROM followed by the 3g fix and tried again, but im still getting the same issue when i try to install the apps........ did i miss something or does anyone have any help they could offer please???
[Xoom Android Development] brandor:
I wiped using Settings>PRivacy>Factory Data Reset, and I STILL cannot install apps?!? any ideas?
[Xoom Android Development] teo91:
Hello, before I start I wanted to be certain not to make mistakes. I am with the last Kernel Tiamat and I followed this method: http://xdaforums.com/showthread.php?t=1074609. I just put the zip on the SD and start CWM? Is that correct?
[Xoom Android Development] rschenck:
Thanks to ax0r's excellent instructions, I have the ROM up and running...however I have one more strange problem.

My external SD does not appear in Root Explorer and no app can find it. It appears in Recovery when I choose Select Zip from SD, but nowhere else.

When I try to Mount USB Storage, it tells me "Leaving this menu unmount your SD care from your PC"...but I am not currently connected to the PC. Is there some command I need to run from adb?

Thanks

EDIT..Could this be a bootloader issue? I flashed the 3.1 Bootloader patch before I flashed the new ROM, but perhaps I should flash one of Tiamat's kernel bootloaders to fix this?
[Xoom Android Development] cam30era:
You should be OK. Follow instructions from OP exactly (below):

"Instructions:

1) Back up your device's apps and data and nandroid to be safe

2) Put rom in root of MicroSD

3) Flash rom

4) Flash the 3g Fix if you're activated on Verizon.

5) Reboot

6) DETERMINE IF A WIPE IS NECESSARY

IF YOU ARE COMING FROM A XOOM WITH ANYTHING BUT THE VERIZON 3G FIRMWARE, IT IS POSSIBLE YOU MAY HAVE TO DO A FULL WIPE

Example: If you have a US Wifi Only device, but you upgraded with my method to the Verizon 3g upgrade kit, YOU WOULD NOT HAVE TO WIPE. If you have a UK Wifi Only model with UK wifi only 3.1, it is possible you may have to wipe.

If your device bootloops, which is not likely, you will need to wipe

Once booted, attempt to install an app either from the Market or a side loaded apk. If the install fails and borks out, a wipe is necessary.

If it is determined you have to wipe, do a Factory Reset in Android Settings menu. At this time do not use Clockwork Recovery to wipe.

Once wiped, flash rom again and reboot."
[Xoom Android Development] 1st_Xypher:
hmm somehow not working for me.

got no CRT anim

Version still shows 3.0.1

and WiFi is not working

only changes i see is the File Explorer an Quickboot.

Any g
[Xoom Android Development] cam30era:
You need to upgrade to Honeycomb 3.1 first. I suggest that you follow this > http://xdaforums.com/showthread.php?t=1074609
[Xoom Android Development] okantomi:
I think you hit othe answer. If I remember correctly, you need one of the Tiamat bootloaders for the SDcard.
[Xoom Android Development] rschenck:
Nods..that sounds right to me...but wouldn't the ROM have installed one of his bootloaders?

And can I flash a new bootloader over the ROM without screwing things up?
[Xoom Android Development] BUMP THAT:
thank you. I ill give it a shot
[Xoom Android Development] armychris28210:
anyone else get this?

so last night i restored my backup of brd's 3.1/timat 1.4.4...

i was running "welcome to win",oc'd to 15400... but some odd things were happening, so i got scared. i was using terminal emu, and it said i didnt have permission to access what i was doing, then it asked if i was rooted. so i checked my SU and busybox. busy box said i wasnt rooted, and it wasnt showing in SU. My quick boot app didnt respond to anything inside when clicked. My Xoom also shut down on its own when trying to access my external usb powered western digital 500gb HD. so now im back on 1.4.4 oc'd. I have a 3gxoom that is being used wifi only<not activated>...no boootloops or anything like that...just wierd issues. anyone else having these probs?
[Xoom Android Development] monyozt:
anyone face batree drain bit faster on this rom?
[Xoom Android Development] okantomi:
Don't know the technical aspects but it seems that all pieces (ROM,kernel,bootloader, and recovery) are seperate but interactive. After flashingthe ROM I rerflashed the 1.4.4 Tiamat kernel to restore the oc gpu. So my understanding is that you need the bootloader that goes with your "suite" if that makes sense.
[Xoom Android Development] rschenck:
I tried it out...refound my SD card but lost WiFi....very very odd.
[Xoom Android Development] okantomi:
Did you try to reflash the kernel, and rom again? (or rom and kernel).
[Xoom Android Development] joeski27:
Yep battery life looks horrendous so far on this ROM, but other than that its great :D.

By the way has anyone figured out how to get the led-ON-while-charging behavior back? I tried flashing BDR's boot that used to enable this, but that essentially killed my wifi, so that was a no go (had to re flash the new ROM to fix this). Thoughts??!?!
[Xoom Android Development] rschenck:
Flashed just the bootloader...and got an error on Wifi.

So I then flashed the ROM again and regained WiFi...and kept the External folder as well.

Victory!

So anyone who loses the external directory when they use Ax0r's method, just flash one of Tiamat's bootloaders, then reflash the ROM to fix yourself up.
[Xoom Android Development] okantomi:
Yay! And I flashed the 3G fix for the contacts...someway kept the circle battery icon, and it fixed the laggy typing in the browser that I suddenly experienced.
[Xoom Android Development] cat2115:
hi, i installed Tiamat Rom v1.0 plus LaunchPad v1.2.2, when using NTFS mount v1.3, it causes FC. Now I can't open NTFS mount.
[Xoom Android Development] bigrushdog:
well, glad to see we're off to a smooth start lol! I've worked out some of the kinks but we got some work to do still. The problems are tied to two things. First problem was binary permission which was borking network provisions. That's fixed. The other issue has to do with effective wiping. Last night I built the rom with the 3g fix integrated. First I went Ito recovery 3.2.0.0 and wiped data and cache. I flashed the rom. Booted to setup wizard. Set everything up but cancelled activation cause I don't have 3g. I experienced the market download reboot issue. Went back into recovery and wiped data again. Rebooted and everything has been flawless since. Tbc
[Xoom Android Development] okantomi:
Even with an element of risk it's been fun to test these efforts! Thanks to you and the entire Team Tiamat for staying on top of all of these diverse effects. I don't know how you do it but I'm glad you do it.
[Xoom Android Development] lrs421:
Hey guys, I've been out of the loop for a couple of days, been trying to catch up. What have some of you done to get it to install on 3.1 wifi ota. Followed the instructions in the OP to the letter and end up in a bootloops every time.

I got it to install once by deviating from the instructions but couldn't download from the market.

I'm also running the latest recovery.

Thanks BRD, for the status update.
[Xoom Android Development] ax0r:
Glad my post was helpful. I looked on my Xoom and I am able to see the external on Astro in /mnt/sdcard/external/

After the BRD update and bootloader patch I flashed tiamat rom, and then the OC kernel without flashing the boot.img from the tiamat thread.

The bootloader patch and the Kernel boot.img are different. Open up the zip and you will see.

Regardless this rom comes with Tiamat 1.4.4 so when you flash it it should come with the appropriate boot.img. The OC GPU is based off tiamat 1.4.4 so you dont need tp flash the boot.img again
[Xoom Android Development] rschenck:
Search in this thread for Ax0r's guide....if works.
[Xoom Android Development] rschenck:
Not sure why my install went odd, but all worked out for the best. Thanks again for your help.
[Xoom Android Development] lrs421:
Would you mind linking to your post...searching on this damn thing is difficult....thanks.
[Xoom Android Development] lrs421:
Ahhhh.... This did the trick. Finally up and running. The second factory restore from within the os did the trick. Can now install from the market.
[Xoom Android Development] Almighty1:
I tried my attempt to flash the ROM to my XOOM US WiFi which was OTA upgraded to 3.1 and then rooted using public animal's method and basically what happened was it just kept showing the flashing honeycomb for the past 12 hours (okay, I went to sleep) so I tried reflashing in CW Recovery and it still kept showing the flashing honeycomb for over 30 minutes so restoring the nandroid backup worked. I'll attempt this again later but is there a way to use adb or fastboot to do the wipe? Also, does nandroid backup (solarnz's version) also backup the /sdcard - the internal storage of the Xoom?
[Xoom Android Development] rschenck:
First, a nandroid saves an exact image of the internal SD card.

Second, use Ax0r's method for flashing 3.0.1, then upgrading to 3.1 then flashing the Tiamat ROM...it really does work like a charm.

Just keep your head, don't panic and be prepared to tinker a bit until you are set up.
[Xoom Android Development] lrs421:
I had the same thing happened to me until I applied the method above from Loki.
[Xoom Android Development] ax0r:
It was on page 23 but here you go
[Xoom Android Development] lrs421:
You're a gent, thanks. I actually got it going by using another posted method, the more the merrier :-)
[Xoom Android Development] cam30era:
Thanks for this info. For future reference, if I need to do a full wipe what do you recommend? Note, I don't use (nor like) ROM Manager.
[Xoom Android Development] bigrushdog:
I updated OP to reflect updated installation instructions. BASICALLY, FLASH THE ROM FIRST WITHOUT WIPING ANYTHING. INSTALL AN APK FROM MARKET OR SIDELOAD. IF YOU DEVICE REBOOTS AFTERWARD, YOU WILL NEED TO WIPE USING FACTORY RESET IN ANDROID SETTINGS MENU.

That's called an Easter Egg. Also known as a "Hidden Feature". It will flash just fine :p
[Xoom Android Development] headcheese:
just tried installing without a wipe and bootlooped for 5 or 10 min. i maybe should have waited longer, but just gonna do the wipe anyway.

3.1 OTA wifi only. glad i made a backup!
[Xoom Android Development] ClydeB1:
As stated in the OP, use Android Settings > Privacy > Factory data reset
[Xoom Android Development] anon20:
SMS capable enabled? What is this?

Sorry for the noob question. Found answer. Please delete.
[Xoom Android Development] Kas206:
If anyone is having problems with there xoom rebooting after trying to install an APK do this

Go to settings > Privacy > Factory data reset

It fixed the problem for me and the data was intact. :)
[Xoom Android Development] Brenardo:
I am excited as hell... I am also just a bit worried to try this as I don't quite understand the data partition talk.

Anyway if I have to wipe will I be able to reinstall apps thru ?he advanced selection of CWR?
[Xoom Android Development] tagacapiz:
crap, lazy evening. this has gotten me all giddy.
[Xoom Android Development] lokko21:
My xoom it's not connecting to 3G network, other then that its working fine. Anybody with this problem..??

Evo Better Than The Best...
[Xoom Android Development] ClydeB1:
All they're saying is that if you currently do a wipe via CWM, there is a bug which wont allow you to install apps. So don't wipe via CWM. If you need to wipe do it via Settings > Privacy > Factory data reset
[Xoom Android Development] Brenardo:
thank you kindly for explaining that for me.
[Xoom Android Development] Marshall1975:
hello

Just wondering if you will be doing a version for UK 3g xooms.

Cheers
[Xoom Android Development] jfvidalc:
I just flashed rom, and i'm having the same problem.
[Xoom Android Development] le_pere_noel:
one small question what is "at the moment" the advantage of this rom, if we use tiamat 1.4.4 ?
[Xoom Android Development] bigrushdog:
What device and service do u have?
[Xoom Android Development] Lolento:
Guys,

I'm new to android but I already have tiamatkernel running and all of the rom features by push other things on the forum.

So what is the advantage of installing this rom?
[Xoom Android Development] headcheese:
tried with and without a wipe and cannot get this to boot on wifi xoom.
[Xoom Android Development] bwcorvus:
tweaks and deox.

Sent From My Evo
[Xoom Android Development] le_pere_noel:
ok so at the moment nothing really new for a novice user :p. I will wait for next release with more tweaks then.

Thx anyway for all the work
[Xoom Android Development] h4jj1:
Little hiccup.

I have a 3G Xoom (but only use as wifi - no active Verizon Account). Was running 3.1 per this thread:

http://xdaforums.com/showthread.php?t=1074609

Per the instructions in this thread - I did a factory reset, and through CWM, did a reset / cache wipe / dalvik wipe, and then installed this ROM and rebooted.

The wizard opens - 1st step is to Activate and you are given the options to Skip/Active.

I Skip - popup dialog I confirm Skip - The wizard restarts, and asks to Activate.​

Is there something I missed, or maybe a bug?
[Xoom Android Development] aronslusa:
Followed the whole method of restoring to 3.0.1 and then redoing it all... worked like a charm.

Now if only netflix would hurry up