yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Almighty1:
The problem is the su installed by SuperUser app is not compatible with the Xoom. All you have to do is do a terminal session or use adb with the "adb shell" command which will get you to:

$

type "su" and hit the enter key and it should give you back:

#

If it doesn't, and you get the following:

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

CANNOT LINK EXECUTABLE

The 1315 and 2756 might not be the exact numbers since I didn't note down the exact numbers before I looked up how to root a Android device when one has lost root.

See post #340 in the following thread for the fix:

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

This is the previous version of the su binary that was modified to work on the XOOM which is version 2.3.1-ef, hopefully there will be a modified version of 2.3.1-efg available soon.
[Xoom Android Development] texasez:
Your links gives a page not found error.
[Xoom Android Development] Almighty1:
Sorry, that's what I get for a copy & paste job. In any case, try it now and I gave you a Thanks for that!
[Xoom Android Development] odyseus:
I have set setcpu to performance and 1.5ghz.

I don't get any re-boots but performance is extremely laggy!

You can type something in the browser and it can take several seconds for the letters to show.

In the end I disabled setcpu, re-booted and everything works OK

But that sort of defeats the point of having a clocked kernel installed?

Any ideas to the very laggy performance? Or should I try a different kernel?

All the best

Ody
[Xoom Android Development] Steady Hawkin:
Using the performance governor really is not necessary, I would give the interactive a shot and see if you still have similar issues. Browser lag seems to be more of an issue on the HC side, and not the kernel. I run the stock browser, but have heard lag issues are reduced when using a different browser (ex. dolphin).
[Xoom Android Development] dixon_coxon:
I just did this and it took less than 15mins .....Thanks bigrushdog!!! This is awesome!
[Xoom Android Development] drivebynerf:
true

You said it better than me lol(id rather just listen to commentary and coments looking to improve), pointless but i think theres a rule online, have a smooth forum you always have ONE DB

Though i wish he was right, wife just scored 1158 on THD fruit ninja while on a trip to the island to buy property killing my score badly on 95o, i wish id have a crash to erase it ha, thats at same time as using it as main source to collect pics and vids and upload via drop box (approx 4 gigs over that time), not a hiccup in 4 days of seriously heavy usage and numerous hotspots etc, all while doing her normal stuff online / remote

only issues i had while running was full 1.7 it didnt remain stable at that under load (yeah im an idiot i tried it lol), caused boot crashes, i reflashed and all is well at 1 gig-1-1.6 gig interactive. I switched from setcpu to no frills, it seems to lower any crashes to zero but every once in awhile i get an annoying hesitation (maybe twice a day under serious load, kids playing with it etc, it doesnt crash just locks for half a second then resumes with no missing data. though i miss set cpu granularity of setting parameters, might try again with it later. Battery actually seems even better normally over a full day before recharge. screen to screen clicks are VERY smooth which was orginally with stock kernel my biggest PIA. Even using transformer water as background and weather..nada issues

been a while since a new update / kernel..anything new coming out?
[Xoom Android Development] survivalsounds:
HELP: ALL Wifi Xoom root attempts (various kits) always result in hang boot screen.

I had tried using the one-click. Had to revert to stock using ADB.

I am now trying all of the other root methods but each one always puts me at the motorola dual core boot screen with a hang.

I am always able to go back into either clockwork or ADB and get myself out of trouble but I can't get the job done.

I really want to use my 32GB MicroSD card and OTG USB Cable, y'know?

Please help!

Xoom 32GB WiFi-Only Version
[Xoom Android Development] okantomi:
I don't recommend the one-click methods...too many issues. This is the way I rooted:

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

This should work for you as long as you have a good version of Clockwork Recovery (anything lower than Version 4 should probably work...try solarnz' version 3.2.0.0 from this thread:

http://xdaforums.com/showthread.php?t=1074979 ).

Then you can update to any newer kernels, roms, etc. You will need a microsd card for this method. I used a 2GB sdcard that had been used in an android phone...somehow that seems to help it be recognized. Load up all the files you will be flashing, and you'll be good to go.

Good luck!
[Xoom Android Development] Turkawa:
i had the same issues.

The solution for me was,

i stopped looking for an easy way out and had to do it ADB style.

Worked like charm for me.

I have no knowledge of any kind of linux or anything.

You just had to bite the stick and take the pain :)

I bet there are similar thread in here on xda somewhere but i used this (for 3.0 only) one

All you have to do is read very carefully (assuming you are a noob like me)

take your time and GET THE CORRECT FILES.

And for the love of god, dont brick it :)

Edit: Okantomi was faster than me :)
[Xoom Android Development] okantomi:
Turkawa, when I read your post, I realized that we've both assumed that Survivalsounds is coming from stock 3.0. Is there any down side to root using files that also upate to 3.1 if you're already on 3.1? I don't want to give bad advice.

Survivalsounds, can you let us know if you are on 3.0 or have updated to 3.1?
[Xoom Android Development] survivalsounds:
Thanks for replying. I am going to try this step-by-step... slowly. I will let you know but let me just say that I did an SD Card method also. Literally, every rooting method is doing the same thing. The only process getting me past boot screen is:

fastboot flash boot boot.img fastboot flash system system.img fastboot flash recovery recovery.img fastboot flash userdata userdata.img fastboot erase cache

...with the stock boot, system, recovery, userdata files going back to the Xoom via ADB from C:\xoom on my computer.

Yes, I have unlocked the Xoom

Yes, I feel like I am following steps carefully.

Yes, I was able to get clockworkmod just like on my Evo.

Yes, my MicroSD card was recognized by clockworkmod and wrote the information to the Xoom, but everything hangs on boot screen.

Anybody know if there is a common error I am making, or a problem with my Wifi Xoom if I am always getting the boot screen, regardless of method?
[Xoom Android Development] survivalsounds:
Thank you both for hand-holding over here! I just noticed:

I had 3.1 that was pushed to the device. However, in restoring a stock rom, I am now on 3.0.1.

Kernel 2.6.36.3-g2a4197e

android-build@apa28#1

Build Number: HW169

I will actually wait to hear from you guys before going through another set of action steps.
[Xoom Android Development] okantomi:
You seem to be using adb properly but are you using the right files? You should check your downloaded files in your platform tools folder--make sure they are whole and not corrupted-- and try using the method I posted, as it provides the right environment for future Tiamat series kernels/roms etc. Turkawa's will work too, but you will have some additional steps to flash the kernels, if you want to, and I assume you do, or why root?

Anyway, have you already updated (through Moto update?) to Honeycomb 3.1? Are the stock files you have flashed through adb for 3.0 or 3.1?

Update: I just read your post. That is probably why it's been hanging, lol!

Anyway if you are now on stock 3.0X, you should be able to use brd's method that I posted, or the one Turkawa posted...it's your choice.
[Xoom Android Development] Turkawa:
@okantomi Well I assumed he is 3.1 ..When i first fired up my xoom i get the update in a minute or so and i thought he did received it too. But you are right we need to be more careful :)

@survivalsounds Mine was factory clean 3.1 when i rooted. I read a lot about oneclick and ppl having all kinds of problems so i choose ADB. Had no issues.

Thats all i can say actually. I dont want to go deeper on advising you cose i am a noob too. Okantomi have a good point there.

Good luck and keep us posted..
[Xoom Android Development] survivalsounds:
I just took the OTA update to 3.1 after reading your replies.

Now that I am back in stock 3.1 what is the proper (step-by-step w/ file links) forum thread (or threads) to follow to root from 3.1 properly and get MicroSD and OTG USB support active... overclocking via stable kernel of course would be fine too!

I am waiting before moving forward... just not waste your time and mine and get it right this time. Let me know if, for any reason, I need to go back to 3.0x

HUGE THANKS!
[Xoom Android Development] Turkawa:
As far as i know both me and Okantomi are rooted and have sd card support and OTA working fine. So both methods work. I was on 3.1 when i rooted so i dont believe you need to get back to 3.0..Now all you need to do is choose a method and give the happy news :)
[Xoom Android Development] okantomi:
Survivalsounds, since you are now updated to 3.1, you cannot use either of the methods Turkawa or I had posted. This link below is the only method I can find to root the Xoom from stock 3.1:

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

I think he knows what he is talking about and has been updating the thread as required.

You really do need to use the correct files and the correct methods. As long as you fit the criteria, PublicAnimal's method looks good. Use the newer recovery he listed.

Good luck!
[Xoom Android Development] survivalsounds:
TRAIL OF BREADCRUMBS (THAT WORKED FOR ME) TO GET PAST BOOT SCREEN HANGING ON ATTEMPTED ROOT INSTALL.

My mistake: I was using the wrong files from various threads. Once I figured that out, it all made sense.

Make sure my files are 3.1 compatible and that I was in 3.1. Keep in mind I started in 3.1 but the first time I had to flash back to stock rom, I switched to 3.0x and erroneously kept using 3.1-compatible rooting methods.

I updated OTA to 3.1

I got a proper version of ClockworkMod and installed it via ADB. Thanks to the two above posters!

I followed Tiamat's instructions for rooting/upgrading kernel of 3.1 ONLY by installing the the files on my MicroSD Card. These were Wi-Fi specific files for me... make sure you get WiFi or 3G/4G depending on your Xoom! Make sure you are using a 3.1 compatible set of files.

I installed a compatible Kernel from Tiamat.

I rebooted in ClockworkMod. This all took a few minutes.

NO MORE HANGING ON BOOT SCREEN DURING ATTEMPTED ROOT!

WOO HOO!
[Xoom Android Development] okantomi:
Great news, I feel like a midwife, lol!
[Xoom Android Development] Turkawa:
Glad it worked :)
[Xoom Android Development] Turkawa:
Holly cow!

I was in the kitchen making coffee and thinking why okantomi said " dont use both methods!"..Then i checked the link i give you and BAM. It was the wrong one. It was for 3.0 not 3.1!

Thank god Okantomi was there to warn you..

I must have "Brainfreeze!" today..

And again.. glad it worked :)
[Xoom Android Development] survivalsounds:
It's worth it if we hash it out and keep someone from making the same mistake and wasting a whole lot of time like I did, hehe. By no means your fault... I was using the wrong combination of files from the start. I actually would have been able to root using your method because I was mistakenly in 3.0x, hehe.

Of course, now I'm right where I want to be with Tiamat's stuff. I'm moving files using USB as we speak!
[Xoom Android Development] ivcarlos:
Tiamat for 3.0.1

Hi all..

I need a version of tiamat that work in my 3.0.1 mz605 stock rom. I googled a lot and all links point to this thread but no versions at all.

I will update to 3.1 when official gsm version released, but i need enable my microsd port.

Anybody have version 1.4.1 - i believe the last version for 3.0.1?

At this moment i using stock rooted one.
[Xoom Android Development] cam30era:
Go back to the OP. Second post has the repository link for all old kernels.
[Xoom Android Development] theMaDHakkeR:
Sorry if this has been asked but is there any UV support? Pimp My CPU said unsupported kernel so i can only use SetCPU. Does Voltage Control work eith this kernel?

Also, how do i use the EXT4 filesystem mount mod? I didnt see anything in my clockwork mod.

Thanks.
[Xoom Android Development] rschenck:
No UV in Tiamat right now. BRD has promised it in future versions.

There is also no need to change the file system, so don't worry about any ext4 modding.
[Xoom Android Development] theMaDHakkeR:
Thanks.
[Xoom Android Development] ivcarlos:
Tiamat for 3.0.1

Hi...

If you say about "http://bigrushmods.com/tiamat.html" i accessed its and find only versions for 3.1 - 1.4.2, 1.4.3 and 1.4.4. None for 3.0.1.

In old threads i found ver 1.3.1 and all references to 1.4.1 point to this thread.
[Xoom Android Development] cam30era:
You are correct. 1.4.1 is not there, on the archive page. Probably because BRD is only supporting archived kernels for HC 3.1
[Xoom Android Development] rschenck:
I would imagine he doesn't want to try and support the older 3.0.1 builds, preferring to focus on his ROM right now...however as he is a prince of a fellow I am sure you could PM him and ask for one of the older kernels directly.
[Xoom Android Development] Ifiuse:
I have just flash the kernel, but i forgot the image.

If i flash it now, will it work?
[Xoom Android Development] thdj:
im trying to make my 3g stick working but it seems that i have a problem with modules option.ko and usb_wwan.ko not being compiled for kernel 2.6.36.4 but 2.6.36.3

Could it be possible to update them? Thanks!

Here's my dmesg result when trying to start the ril-daemon :

<5>[ 202.493683] scsi 4:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2

<5>[ 202.504154] sd 4:0:0:0: [sda] Attached SCSI removable disk

<3>[ 247.530592] usb_wwan: version magic '2.6.36.3 SMP preempt mod_unload ARMv7 ' should be '2.6.36.4Tiamat_Xoom-v1.4.4-Full_Throttle-g0baec41 SMP preempt mod_unload ARMv7 '

<3>[ 247.535790] option: version magic '2.6.36.3 SMP preempt mod_unload ARMv7 ' should be '2.6.36.4Tiamat_Xoom-v1.4.4-Full_Throttle-g0baec41 SMP preempt mod_unload ARMv7 '
[Xoom Android Development] thdj:
Sorry my bad i was using a wrong rild version. Now i don't have the error. Still searching though for making the 3g stick work...
[Xoom Android Development] jrock60:
Noob question

I just got my xoom wifi (canada) and have unlocked, rooted, applied clockwork, and updated to 3.1 with working sd card.

I would like to apply the Tiamat Xoom 1.4.4 MOD.

Here are my questions:

Will I lose any data, settings or installed apps?

Will I lose root?

Do I just apply it in recovery mode using CWM?

Any help is much appreciated.
[Xoom Android Development] cam30era:
No, you will not lose data. Only when you unlock, or if you wipe data for some reason.

No, you will not lose root.

Yes, if you have CWM 3.X.X.X you can flash the .zip. If you have CWM 4.X.X.X from ROM manager, you will have to "downgrade ".
[Xoom Android Development] Brolloks:
I flashed from Tiamat 1.4.2 to this one and I can say that the new kernel feels much snappier, zero typing lag and it just feels smoother overall, same OC at 1.4 Ghz interactive

Thanks again to BRD and tge dev team:D
[Xoom Android Development] xlGmanlx:
Been using this for a while with the gpu overclock and its great. I will say that it does feel like it gets warm
[Xoom Android Development] funkatiko:
Can anybody tell me why i can´t browse my sdcard ? Since i installed the last kernel it seemed to stop. I can browse it with usb mass storage conected from the computer, but not on android. External or SDCARD2 is not working anymore?

Thanks!
[Xoom Android Development] cam30era:
Which version of CWM are you currently running? Did you download 4.X.X.X from ROM manager?
[Xoom Android Development] funkatiko:
I believe i had a lower version. Now i installed 4.x.x but still don´t find the folder...
[Xoom Android Development] legion21:
is it safe to install this if I already have launchpad installed or do I need to wipe first?
[Xoom Android Development] cam30era:
No. Wrong thing to do. Now you need to go back. In ROM manager go to the bottom and choose older versions of recovery. Flash 3.0.2.5. After that, flash solarnz 3.2.2, which is pinned to the top of this development section.
[Xoom Android Development] funkatiko:
Ok done. What else?
[Xoom Android Development] cam30era:
Did you have access to your external SD card before flashing 1.4.4? Have you made any other changes?
[Xoom Android Development] funkatiko:
I can´t actually remember when did i lose the acces to it....lately i´ve changed t he rom and changed the kernels..launchpad and tiamat....i don´t where should it be the folder....external, sdcard2..? :S i can acces throguh windows tho..
[Xoom Android Development] JFMFT:
None of the download links work on my Xoom. I am without a PC for a while, and none of the links will download directly to my Xoom using any browser (stock, dolphin, opera, or Firefox). Does anyone have a suggestion about how to download the 1.4.4 NON OC'd GPU version directly to my Xoom? The OC'd GPU version is causing a little instability on my Xoom and I need to swap kernels.

Thanks.
[Xoom Android Development] cam30era:
Did you change SD cards? Only thing I can think of is to format your SD card in an android phone.
[Xoom Android Development] nique0201:
Why when I try to flash the kernel it starts then it just says installation aborted.
[Xoom Android Development] chadswill:
download links dosent seem to work..

oh and btw.. i guess its safe to use this kernel with my Xoom EUR 3g/wifi HC3.1 ?
[Xoom Android Development] JFMFT:
Download links for the 1.4.4 kernels (both of them) no longer work. Can we get working links? Pretty please?
[Xoom Android Development] rockhumper:
Yes thank you! I need this too and had to post ten times to be able to reply in dev section...

My xoom seems very laggy since the gpu overclock...stock was waybetter for me
[Xoom Android Development] JFMFT:
I'm so glad im not the only one with this issue, lol. I have two Xooms. My stock, unrooted Xoom performs so much more smoothly. I never had that happen before the GPU overclock kernel. But until new links are given, well, I'm stuck using the OC'd GPU version :-[
[Xoom Android Development] solarnz:
.. the download links work just fine.

In the bundle that the OP links to, use the one of the last 2 links, it appears the first two links are offline, but the mirror works just fine.
[Xoom Android Development] rockhumper:
Thanks solnarz was not sure that mirror was the same...still learning. The link worked and things are better now. Thanks
[Xoom Android Development] sharptv:
how do you guys set the smartass governor? It is not listed under setcpu's governors. I have flashed the one with overclocked GPU. Any help please?
[Xoom Android Development] solarnz:
You can't, the smartass governor was removed in version 1.1.0
[Xoom Android Development] rockhumper:
Yeah I don't know the issue but flashing themirror file back to stock definitely improved things for me.
[Xoom Android Development] Mr Bland:
My Xoom hasn't been able to handle oc higher than 1504. I was hoping to overvolt to try to make to more stable at 1.6 or 1.7. I've read in another kernal that this can be done with terminal. So my question is, will overvolting using terminal commands work with this kernal, and if so how much overvolt is too much. I want to try to avoid breaking my Xoom while I tinker with it :)

By the way I read about it in the op of this thread:

http://xdaforums.com/showthread.php?t=1122902
[Xoom Android Development] dalvarez7:
Had this issue to. So what I'm thinking is happining is the default profile is set to turn the mhz down to 216 when the screen goes off and then bump back up to whatever you set the max to when back on. The problem is it's not going back up once you turn on the device. It stays at 216, hence it running so poorly. I created a profile in SetCPU that tells it to not drop the mhz down to 216 when screen goes off and makes it stay at 1.6hhz (or whatever you want). That seem to fix the lag.
[Xoom Android Development] solarnz:
No. The Tiamat 1.4.4 kernel does not contain user controlled under / over volting yet. Hopefully this will be in the next release & compatible with the new setcpu voltage controls.

However, both 1.6GHz and 1.7GHz are already at 1.4 volts - Probably not a good idea to go above this. Every xoom is made slightly differently, so not everyone can run at high frequencies, for example mine only handles 1.504GHz as well.
[Xoom Android Development] rockhumper:
Yeah mine only makes it to 1.6 and then starts crashing...very strange.you would think all devices are made equal but in practice you see they really are not.
[Xoom Android Development] legion21:
well with this kernel I was able to go at 1.7 long enough to run quadrant, but crashed after that. 1.6 is stable for me. What exactly does gpu overclocking do for us? I spent only a brief amount of time on stock so I don't really have anything to compare it to haha
[Xoom Android Development] davidsos:
Originally Posted by JFMFT

I'm so glad im not the only one with this issue, lol. I have two Xooms. My stock, unro

oted Xoom performs so much more smoothly. I never had that happen before the GPU overclock kernel. But until new links are given, well, I'm stuck using the OC'd GPU version :-[

I don't have this issue, I'm set to interactive at 1.6 Ghz and use the OC'd GPU kernel.
[Xoom Android Development] JFMFT:
It's hard to say just what about the overclocked GPU kernel was messing with my Xoom. My guess is that it was putting off too much heat over time, or was simply stressing the GPU too much, leading to instability. You know how sometimes if you overclock CPU/GPSs that you actually lose performance rather than continue to gain (after a certain stress point)? I think that's what's happening with my Xoom.

I'm running the same profiles as I was on the GPU OC'd version as I am now with the NON-GPU OC'd version, but my Xoom is infinitely faster/smoother with the kernel that DOESN'T have the overclocked GPU. Since flashing the regular kernel (thanks to the people who posted saying to use the mirror link to download - worked great for me!), my Xoom has been smooth as butter. In fact, I think I even have less force closes. That part is probably unrelated to the kernel, though.

The only profile I'm running is a screen off profile, low end 200something mhz, high end 1000mhz. I used interactive governor on both kernels. If it really was an issue about the device getting stuck at 200something mhz, it would be evident on both the OC'd GPU kernel and the regular kernel.

I think I just have a sucky GPU in my Xoom that can't handle the GPU overclock very well. Sucks for me. Oh well, I'm over it. I've known for about a year that the Tegra2 chipset is kind of a slouch (sorry, it is). Can't wait for Kal El, honestly!

BRD - once again, your work is awesome. Thank you for these kernels!
[Xoom Android Development] hkfriends:
Anyone pls help me out on Xoom 3.01 with Timat kernel 1.41, which i cannot access my external sdcard?

i already created a folder 'external' under /sdcard

Thanks
[Xoom Android Development] cam30era:
Did you format your sd card to fat32 in another android device (phone)?
[Xoom Android Development] dhicks19:
Hi mate I am trying to do what your doing, i got a rooted 3g uk xoom running 3.0.1.

I am unsure of how to install timat kernel 1.41. Do i also need a tiamat boot file? as they are only for android 3.1 and uk dont have 3.1

thanks