yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] scribbl:
WiFi Xoom (MZ604) Root - Tiamat 1.4.0 version

Hi folks,

Figure I should give a little back to this forum. I bought a UK WiFi Xoom today. Looking at a few threads I've managed to piece together rooting instructions that use the new 1.4.0 Tiamat kernel directly. This might be of use to someone as noobish as me :) I'm using a Mac so I'll talk about terminals etc., but the Windows version should be easy enough to work out, especially if you read this along with the existing root method. Remember to check commands are

Check these threads first of all and grab the files...

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

ClockworkMod Recovery v3.0.2.5

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

Tiamat 1.4.0 (second post in the thread)

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

Motorola WiFi Xoom Root Zip file

Moto Drivers (if you're on Windows)

Now go to these sites and grab the files for your platform...

http://developer.android.com/sdk/index.html

Android SDK

http://developer.htc.com/adp.html

Fastboot

Thanks to bigrushdog and Xaositek who I am just putting in the right order.

Unzip the Android SDK

Open the Tools folder

Run Android

Click Available Packages

Install the Android SDK Platform-Tools

Now you'll have a Platform-Tools folder inside your Android SDK folder.

Copy Fastboot over into the Platform-Tools folder

Copy the recovery.img for Clockwork Recovery into the Platform-Tools folder

Unzip the WiFi Xoom Root file and copy the files into the Platform-Tools folder too

Fire up your Xoom and make sure you have USB debugging enabled (Settings > Applications > Development)

Now you need to fire up a terminal on your computer

Change into the Platform-Tools folder in the Android SDK

Now type this

adb reboot bootloader

Wait for the Dual Core screen with the Fastboot text on it then type

fastboot oem unlock

Now on the Xoom

Back to the computer

fastboot flash recovery recovery.img
fastboot reboot

Once reset do this to get into Clockwork Recovery

adb reboot recovery

Now use Volume Up and Volume Down on the Xoom to move the prompt and Power to select it.

When the Xoom rebooted (took a while and stuck on looping the cool honeycomb animation for a while) I lost my USB debug mode and had to re-enable it.

Back to the terminal

adb remount
adb push su /system/bin
adb shell ln -s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb push vold.fstab /system/etc/vold.fstab
adb reboot
adb shell
su
exit
exit

Now just for good measure, and since it was a new Xoom I went into Clockwork Recovery and Wiped the User Data and the Cache. If you want to do this then in the terminal:

adb reboot recovery

And use the volume buttons and power to select the appropriate options.

Now you have Tiamat Kernel 1.4.0 installed, and Clockwork Recovery 3.0.2.5 and have Root access...

Hope this helps someone. I've got a lot from XDA over the years for my Nexus One and Nexus S and figure I should give back :)
[Xoom Android Development] johnpwu:
Thanks to both of you. Got it working.
[Xoom Android Development] robbiev80:
Do you have a WIFI XOOM? This issue has manifested itself on my xoom and my co-worker's xoom as well.

EDIT: I guess this feature was taken out for some reason in the latest update.
[Xoom Android Development] xjack:
For those of us newbs, this post contains some acronyms I don't get?

MTP? When the Xoom is plugged, Win7x64 shows it and I can see and access the external folder on the "device". Is this what you're referring to? edit: found the answer

OTG Cable? Can someone point me to a link? edit: found the cable info and USB/Harddisk info

As a newbie to Android and the Xoom, a big thanks to you BRD! Donating now!
[Xoom Android Development] mskks64:
got this error

Installing: /sdcard/Tiamat_Xoom-v1.4.0.zip

Finding update package...

Opening update package...

Installing update...

Tiamat Xoom Kernel Series 1.4.0

Welcome to Xoom Mass Storage

Developed by Bigrushdog, Kcrudup, and Cybertronicz

Wiping Cache and Dalvic Cache in case you forgot

E:Error in /sdcard/Tiamat_Xoom-v1.4.0.zip

(Status)

Installation aborted
[Xoom Android Development] bwcorvus:
Use kernel manager, this is a common error i explained it alot earlier in this tread...but just use kernel manager.
[Xoom Android Development] atoosa:
I get the same thing....Halllllppp
[Xoom Android Development] blkbeltkid17:
i got the same error then i ran my xoom in debugging mode connected to my computer and followed the steps in the first post again and i had no problem ... hope that might help
[Xoom Android Development] csseale:
Also make sure you have sdcard unmounted in recovery under mounts and storage.

www.facebook.com/redcardgreencardpage
[Xoom Android Development] mskks64:
thanks that worked
[Xoom Android Development] blooregard_q_kazoo:
Kernal Manager flash broke my wifi :(

Is there anyway to go back to stock everything? I rooted and flashed the new 1.4.0 Tiamat, but now my wifi is broke. Everything i read says to go to like 1.3.2 or something, but i just want to go back to stock everything. Is this possible or is the only thing i can do really to go to 1.3.2? ok thanks!
[Xoom Android Development] ryan562:
X2. Guess we are the few that actually have had no issues with 1.4
[Xoom Android Development] blooregard_q_kazoo:
well i tried using the root 1 click wifi, and same thing, keeps sayin wifi error :( hope i didnt brick it
[Xoom Android Development] twinkyz1979:
WiFi Stock Version

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

3G Stock Version

http://xdaforums.com/showthread.php?t=988942
[Xoom Android Development] hgoldston:
Exactly where in the file explorer is your new shiny sd card suppose to show up. I looked for my files in external, usbotg and sdcard 2 but my files are not in any of those folders.

I can mount the sdcard and I can see my files but I cant see them on the xoom.
[Xoom Android Development] wheeeler:
I'm having a hard time finding a working link to the stock image... any suggestions?

btw, thanks for the help so far. i can't tell you how appreciative i am.

**UPDATE**

I found two working links to the stock SBF, one is named MZ600_HRI39.zip (117 MB) and the other TheGiftOfLegion.zip (127 MB). I'm not sure which, if either, will work, and I will post details after I flash. Thanks to my super-slow Bavarian DSL, I won't be able to try them out until tomorrow. Say a prayer for my Xoom!
[Xoom Android Development] nswenson:
Use the link and instructions in this thread:

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

After you finish, the Xoom should be back to the same state as when you bought it.

Edit: There is another option for restoring to stock that avoids needing the extra flashing program. Check this thread:

http://xdaforums.com/showthread.php?t=988942
[Xoom Android Development] bogatyr:
Does the tun.ko module in the latest update work with VPNConnections.apk for Cisco IPSEC vpns?
[Xoom Android Development] dimitri407:
I have a question about the kernel and the overclocking. I have flashed everything and am rooted but can't figure out how to set this to run at full speed or to set the governor without using Droid overclock. Sorry if this is a stupid question. Just trying to learn.
[Xoom Android Development] bogatyr:
Well I was able to get it to connect, but once connected I have no network access to anything anymore. If I try to disconnect is says disconnecting forever and I have to reboot. Shame, I was really excited when it said connected... last piece of the puzzle for me.
[Xoom Android Development] bogatyr:
I'm not very experienced with this but there are a couple flags for VPNs, namely:

CONFIG_TUN

CONFIG_IP_ADVANCED_ROUTER

But in the tegra_defconfig file from the source, neither are configured:

# CONFIG_TUN is not set

# CONFIG_IP_ADVANCED_ROUTER is not set

However, not having a clue about this, and there being a lot of config files, I'm not sure if that is the one that matters. Is that the correct config file, or is a different one the correct one? Are these set in this kernel? They need to be turned on for VPNC.
[Xoom Android Development] bogatyr:
Ok, I found it. The flags need to be fixed for VPNC:
[Xoom Android Development] bigrushdog:
Ill check this out tonight and see if I can compile an update
[Xoom Android Development] wheeeler:
You, sir, saved my Xoom. MZ600_HRI39.zip had all the original images, and fixed my wifi. If I had flashed one or two of these before wiping, I probably could have saved my data, but I'm thankful to have my Xoom back in action. Thank you so much!
[Xoom Android Development] kjdocs:
It seems no matter which version of the kernel i use (other then stock), i get reboots.

I'm to the point where i don't even have to overclock. I load the new kernel and i will reboot about once an hour (of constant use).

Does this mean i just have a sub-par CPU? Can i expect this behavior with all future roms?

Just curious. I'm otherwise completly happy with my xoom, but this does cornor me if i can't do other future kernel related modifications.

I have NO reboot issues with the stock kernel and wifi drivers.

Thanks.
[Xoom Android Development] Droid-Xer:
Yes you probably need a more conservative OC like 1200 or so. ROMs will be fine its just the overclok kernels you might want to avoid for now
[Xoom Android Development] Droid-Xer:
Tellme if I understand correctly...

If I was on v1.1.0 all I need to do is:

adb remount

adb push tun.ko /system/lib/modules/tun.ko

adb push cifs.ko /system/lib/modules/cifs.ko

adb push vold.fstab /system/etc/vold.fstab

adb reboot

Since I'm just pushing these files on?? Yes or no??

Now just trying to push bcm4329.ko I get:

cannot stat 'bcm4329.ko': no such file or directory
[Xoom Android Development] wheeeler:
That's just ADB telling you that it can't find bcm4329.ko in the directory you're in. Double-check to see if it is there, and make sure when you pass the file name to 'push' that it isn't named something funny.

I'm not a fan of throwing all these different kernels and modules into the same folder, so I added all the sdk tools to my path. That makes it a lot easier to work out of different folders without having to remember which kernel I'm flashing or what version of which module I need to push to make everything work.

...This coming from the guy who killed his Wi-Fi 2 weeks after getting his Xoom
[Xoom Android Development] Droid-Xer:
Nope its not named anything else. There's no other kernel folder in my platform-tools. I'm doing:

C:\android-sdk-windows\platform-tools>adb push bcm4329.ko /system/lib/modules/bcm4329.ko

And I get the cannot stat 'bcm4329.ko'-no such file or directory

Was I suppose to flash the SBF first then update to the new version?
[Xoom Android Development] bwcorvus:
Try

C:\android-sdk-windows\platform-tools>adb push bcm4329.ko /system/lib/modules/

Sent from my Xoom
[Xoom Android Development] Droid-Xer:
Tried that too, same error. I just used root explorer to put the wifi file back in manually so I at least fixed that. I was really wanting usb hosting, but for some reason the command wont take. Ive tried moving it to tools and nothing either. Im open to any other suggestions...v1.1.0 took the first time with no issues.
[Xoom Android Development] wheeeler:
**EDIT**

It took me too long to post; you did what I would have done. Here's my post anyway lol

**EDIT**

Try changing the permissions, then attempt the push again.

I hate to offer a workaround, but this might get you moving in the right direction. Since you can't seem to push bcm4329.ko directly to your modules folder, drag and drop it to a user-accessible directory using Windows (or whatever transfer utility you would use) just like it was an mp3 or an eBook. Hell, you could even e-mail it to yourself... just get it onto your Xoom. Then use a file manager with root permissions to copy the wi-fi module to /system/lib/modules/bcm4329.ko

The only time I've seen that error message is when I tried to push a file that didn't exist (typos, usually). I've accidentally pushed a file to a directory that didn't exist, and ADB was kind enough to create the (erroneous) direcories for me and deposit my file without complaining.
[Xoom Android Development] Droid-Xer:
Could I just push the files needed for usb hosting the same way you think??
[Xoom Android Development] wheeeler:
As long as the files are in the right place with the right permissions, it shouldn't matter how they get there.

I am still interested as to why ADB isn't cooperating with you. I don't think Windows has a root user, but is it possible for you to open a command prompt as Administrator? Like right-click>run as or something... It's not a good habit, but sometimes running commands as root/administrator will get the desired results.
[Xoom Android Development] dimitri407:
So for the new version 1.1.6 we just push the modules, correct? Or is it just the tun.ko that we have to push?
[Xoom Android Development] mskks64:
in the "sdcard" folder not the actual sdcard
[Xoom Android Development] driftr:
I just used the One Click Root tool to push Tiamat's 1.3 ROM and then flashed 1.4.0. So far everything's working great. When plugged into a computer I can access the onboard memory and if I save to the 'external' folder it shows up on the microSD card I put in. Files show up instantly and don't require a reboot. I hadn't had any previous ROMs installed so maybe that helped in making sure all worked? Dunno but I'm loving it!
[Xoom Android Development] odyseus:
Anybody experiencing sluggish performance with Tiamat 1.4.0 and SetCPU set to performance?? (Max freq 1500MHz)

Is there any way to find out if some apps is causing a slowdown in my Xoom's performance/

Cheers Ody
[Xoom Android Development] cat2115:
just want to report on 1.4.0. working great on my wifi xoom. i put all my music in microSD, reboot my xoom. click on music icon (the headset icon), and all my music r in there. so basically xoom see all my files in sd card. loving it. now i have a 64gb xoom :) for only $628 compare to 64gb other tablet or ipad2 = $700 :) excluding tax

tether iphone ad=hoc to wifi xoom. i guess my xoom is complete for me..

i didn't install "setcpu" overclock then i don't know what to check or uncheck. too much other which i don't know. i try one time and all i did was rise the bar to 1.5ghz and that it. is that how u do it?
[Xoom Android Development] joeski27:
BRD - thanks for all the hard work so far on the kernels, great job indeed. The only minor request I have is could you please please please re-enable the charging LED light so that it comes on while docked/charging while the device is powered on? This worked (and still does) on 1.3.2, but not on 1.4.0. It was one of my favorite little improvements on that kernel, but sadly now it is gone. I really really loved being able to see the charge status while it sat on the dock (while the device was still powered on), and I've reverted back to 1.3.2 until this is fixed.

Thanks!!!!:D
[Xoom Android Development] hgoldston:
That cant be right. I do have a folder called sdcard, but its the actual xoom drive not the sdcard.

Ive used Astro and es file explorer neither of which cant find my sdcard thats installed in the xoom.
[Xoom Android Development] bwcorvus:
Depends on the version you are running. 1.3.2 its in /sdcard/sdcard2 on 1.4.0 is in /sdcard/external.
[Xoom Android Development] mskks64:
in the sdcard folder(xoom internal memory) add a folder called sdcard2 IK it doesnt make sense but its right
[Xoom Android Development] TsaiKimon:
Like mentioned above its /sdcard/sdcard2 for 1.3.2 and /sdcard/external for 1.4.0
[Xoom Android Development] hgoldston:
I have 1.4.0 installed.

I will try sdcard 1k, like one post stated.

I looked in sdcard/external that folder is empty and if that is the correct folder where is the files that suppose to be in it. There are files on the external sdcard one of which is the 1.4 kernel

I already had a folder named sdcard2 located in sdcard/sdcard2 from when i had to adb it in from earlier release.

edited::

It was sdcard/external for some reason there are files now in that folder, i checked that folder numerous times and they wasnt there before. Oh well they are there now. Thanks everyone
[Xoom Android Development] cj10488:
It was disabled due to people complaining it was too bright when in the dock. I will be modifying his kernel tonight to tenable the charge light for my own use. If all goes well I don't mind sharing a copy with others. As long as he has this disabled I will be making a duplicate copy with it enabled as it is my preference too.

James
[Xoom Android Development] dlevans:
why not make another script to enable/disable the light? Seems like a win win.
[Xoom Android Development] cj10488:
Ok here is the 1.4 kernel with the Charge light enabled. I ahve tested this myself to the point of flashing and rebooting. the only change made was to enable the charge led when device is powered. Thanks BRD for the info.

As with Everything this is a USE AT YOUR OWN RISK file that I did for myself. this is the first boot.img that I have modified for android however the only change was for the LED so this should be the exact same thing as the original file with the charge LED enabled
[Xoom Android Development] andr0id23:
I'm sure this has probably been brought up in the 100+ pages, but as far as some people having to reboot to see files transferred over mass storage, has anyone use 'Media Rescan Root' from the market? Has always worked great for me on my other devices. Just does a quick media scan to let you see new pics in the gallery without having to reboot to start the motorola media scan process.
[Xoom Android Development] mutiny:
Damn. I didn't know that existed. Hmmm... time to revisit the 1.4.0? But then I want the charge ujnducator LED. Hmmm... decisions, decisions.

Edit: Wasn't worth it for me. Rescan Media Root just stayed at "Working..." and never went anywhere.
[Xoom Android Development] bigrushdog:
Tiamat 1.4.1 will be out shortly. I have completely overhauled the update script. You will no longer receive any errors when flashing. I still need to communicate with Shinzul to update Kernel Manager with the new script. This "should" resolve any issues flashing with KM as well. The new kernel has some updates to the wifi/Bluetooth radio. Also, I have included modules for mounting all sorts of popular file systems. Also included are aufs.ko and utf_8.ko for foreign language network mounts. And you still get the killer benchmark scores. Happy Xooming!
[Xoom Android Development] mikebeatrice:
I'm having an odd problem and as far as I can tell I can trace it back to starting after flashing 1.4.0 to my wifi xoom

I'm not 100% sure of what's happening, but basically it's like the app that I'm using loses control... or maybe one of the soft keys at the bottom of the screen is getting randomly automatically pressed.

For instance... if I'm playing a movie (in moboplayer)... it'll just stop randomly and jump to the video selection screen... or in a game (so far anything I've tried) randomly it'll pause all on it's own as if someone else took focus... usually jumping to the menu like someone hit the soft menu key... but no one has.

Am I the only one having this strange problem? I've tried re-flashing/pushing the files. Everything else seems fine... on the surface there are no issues with my device.

Only thing I haven't tried is going back to a prior kernel.. I was coming from v1.1.6

I haven't seen anyone else mention this, so ... eh...

Any thoughts?
[Xoom Android Development] jawonder:
Thanks OP looking forward to it .
[Xoom Android Development] robbiev80:
I had those issues a couple of days ago. I flashed 1.3.2 which fixed the issue for me. Went back to 1.4.0 soon after and issue has not come back.
[Xoom Android Development] mikebeatrice:
Thank you.. was actually about to try that.
[Xoom Android Development] cadiken:
You left the mass storage mod in there yes?

I'm loving that mod. I installed auto mount from the market and when I plug in my Xoom to my computer I get a new drive and when I put files in the drive they show up on the Xoom immediately and can be seen by everything - NO reboot necessary. I'm a happy camper. Thanks BRD for all you do.

PS, will 1.4.1 have the new update due out today?
[Xoom Android Development] lokko21:
Which its this upcoming update you are talking about..??

Evo Better Than The Best...
[Xoom Android Development] kilroy1stcav:
I use SDrescan, and itnworks great!
[Xoom Android Development] mikebeatrice:
I flashed back to 1.3.2 and the problem is still there... did you do anything else in particular? Or did the issue not go away until you re-flashed 1.4.0?

update:

Crap... went back to 1.1.6 and it's still doing it... This is extremely frustrating and basically makes the tablet unusable. It all started with v1.4.0... if anyone has any ideas to try, I'm game... would prefer not having to wipe, but I guess if I have to, I have to...
[Xoom Android Development] pat4714:
anyone get a ntfs formatted usb hard drive to work

my hard drive turns on and spins light turn on but no ones home but cant recognize it on otg my flash drive formatted fat32 works no problem so cables are correct im just thinking usb port not recognizing ntfs file system running 1.4.1 and have scriptor widget working if some one got a hard drive to work please post make and model i have seagate 500gb FreeAgent go formated in ntfs or please explain how to set it up thanks any help would be apreciated
[Xoom Android Development] robbiev80:
do a dalvik wipe and a partition wipe using clockworkmod.
[Xoom Android Development] mikebeatrice:
What gets wiped on a partition wipe?

edit: or should I assume that was a cache partition wipe?

edit2: well. that was a bust. meh... about to wipe.... this is really frustrating.
[Xoom Android Development] stryker759a:
I am trying to push version 1.4 by way of first adding 1.3.2 so that I can add clockworkmodrecovery. I have unlocked and rooted with the one click method. I have the latest sdk installed as well as the moto drivers. I am able to list my device my doing a adb device. I then run the adb reboot bootloader and my xoom restarts. I am not able to go any further since when my xoom comes back up and stays on the starting fast boot protocal support. I am not sure if it is locked up but I am able to restart it by holding down the power button and the volume up. I need help with why once it comes back up after the adb reboot bootloader it is no longer recognized. I am opening a commond window from C:\Program Files\Android\android-sdk\platform-tools where the files are located. Any help would be appreciated.

Thanks

Jason
[Xoom Android Development] mikebeatrice:
When you do the "reboot bootloader" you're booting into fastboot...

once you're there, push the boot.img by typing (without quotes)

"fastboot flash boot boot.img"

after that's done, type

"fastboot reboot"

then after you boot into android, use

"adb remount"

and then push all of the files like it says in the original post... all of the .ko files, etc...
[Xoom Android Development] stryker759a:
As soon as I try and run the fastboot flash boot boot.img I get fast boot is not a recognized as an internal or external command. I then just do a adb devices and it no longer is listing my device. It reconizes it while the device is on since it reboots with the adb reboot bootloader. The device is also listed under device manager while the device is on the starting fastboot protocol support. Any ADB command returns device not found.
[Xoom Android Development] mikebeatrice:
Make sure fastboot.exe is in the directory you're trying to execute it from or in your system path. It sounds like you're trying to execute from the wrong location.

when you're in fastboot, adb won't see the xoom.. only fastboot will (you can run fastboot devices)
[Xoom Android Development] andr0id23:
Hmm I'm thinking it was due to the latest update. I've been using it for months and it has always worked great, but I am now getting that problem on my phones too. I bet the dev will update a fix soon. Also, I forgot, but the root version didnt seem to work on my Xoom when I first tried it, so I used the non root one, 'Rescan Media' and it works great on my Xoom.