yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] alias_neo:
What is this Motorola Update Util everybody keeps mentioning?

Let me make something clear:

If you modify your XOOM by unlocking and flashing anything, there is currently NO WAY for a european xoom to be put back to stock and relocked.

We DO NOT have the images from Motorola.

The images that I or others have posted as "stock" in other threads are DUMPS and are NOT official images. We CANNOT relock with these.

No relock mean no OTA, until it is modified to flash on a rooted XOOM.

You have been warned.
[Xoom Android Development] Marshall1975:
Alias

Hello there I need your help. I rooted using your guide and all went well. I then went on to install 3.1 and a custom rom which all went well. Played around this morning and noticed i was no longer rooted, so i used your guide again and now im stuck on the red M and will not boot. Also now have a message saying failed image LNX 0x002. Any help would be greatly appreciated

cheers
[Xoom Android Development] alias_neo:
That sounds to me like you relocked it.

You can't run 3.1 on our xooms, its cdma and its boot image is incompatible.
[Xoom Android Development] Marshall1975:
hello

Thanks for the info alias. Got it all sorted but have to ashamedly admit I dived in and flashed 3.1 lol. All works great but just gnna have to wait to get my 3g back. Did give the German stock image a go which worked but installing the language pack sent it into a boot loop. I know my fault for not reading.

Cheers
[Xoom Android Development] davidebeatrice:
let me know please
[Xoom Android Development] ulnagar:
Alias, thanks heaps for your guide. I just bought an Australian Xoom and tried the US rooting steps but got stuck at the "Dual Core" screen. Your guide helped me get the device rooted.

Do you have a copy of cifs.ko that will work with the rooted, stock kernel? I am not really interested in replacing the kernel, only getting CIFS Manager working.

Thanks again.
[Xoom Android Development] alias_neo:
I do have some, havnt tried the cifs but he tun.ko works fine. Ill try upload it from browser now, tapatalk doesn't seem to support attachment....

EDIT: I'v attached them to the original post now, let me know how you get on with them.

Macbots drool as I XOOM through the Galaxy to my hearts Desire.
[Xoom Android Development] ulnagar:
Thanks for the quick response Alias, but unfortunately it doesn't seem to work.

I can insmod the file, but when I try to mount the share (either via CIFSManager, or manually using the mount command in a terminal emulator) the device simply reboots. It's possible that you have a different software version in the UK.

I'm a little hesitant to replace the Kernel with an older version of Tiamat seeing as 1.4.2 is for HC3.1 only. I guess I'll either have to give it a go or live with what I got.

Thanks for all your help.
[Xoom Android Development] sandro.bertini:
Ulnagar, if you would like I have Tiamat Kernel version 1.4.1, pm me with an email address and I can send it to you. It worked great.

Alternatively you can upgrade to 3.1 (I did it and it works great) following the guide linked in my signature (you will need CWM installed).

Regards,
[Xoom Android Development] kent27:
does this work for asian model too?
[Xoom Android Development] ulnagar:
Thanks Sandro. I was a little nervous about doing it on an Australian Xoom without someone else having tried it first, but I did follow those guides and everything is working perfectly now. I have HC3.1 flashed along with the 1.4OC version of Tiamat 1.4.2 and CIFSManager can now connect and map drives. This is exactly what I was hoping for. Thanks for your help!
[Xoom Android Development] alias_neo:
Its unlikely, if you have the same kernel there should be no problem. Ill try tthe cifs on my xoom when I get home and let you know if I get the same reboot. What we need is the nfornation from dmesg or the kernel panic to find why its dying.

Macbots drool as I XOOM through the Galaxy to my hearts Desire.
[Xoom Android Development] terminal 7:
** deleted post ** kinda found answer in q&a

- nice work tho :)
[Xoom Android Development] ydaraishy:
Verified an interesting/sobering fact today. UK uses build H.6.1-38-1, DE H.6.1-38-5, AU H.6.1-38-9.

38-1 and 38-5 use different kernels, presumably so would 38-9. So that could be the cause of module versioning issues.
[Xoom Android Development] rikiau123:
adb remount, tells me invalid command.build H6.1-38-1
[Xoom Android Development] MattCB72:
Did you flash the boot.img, that's provided in the first post?
[Xoom Android Development] davidebeatrice:
hi guys!

ive a problem...i cant mount my xoom in debug mode...adb cant find my device...

can someone post the drivers please? (Im using win7, its better to try with xp?)

thx

Never mind...I found drivers on motorola web site...

Now...which is the best kernel? (where can I download it? on tiamat download center I find only the 3.1 version)

thx!
[Xoom Android Development] rikiau123:
yes flash the boot.img
[Xoom Android Development] davidebeatrice:
double post sorry...

see below
[Xoom Android Development] davidebeatrice:
Hi guys...

after rooting ive flashed the cwm recovery and now im trying to flash the 1.3.1 tiamat kernel but if I try to mount usb mass storage, desktop pc ask for formatting: ive to do that?

thx...
[Xoom Android Development] alias_neo:
I recommend you don't format anything via CWM, you don't really know what it's trying to format and could make an unholy mess.

Why exactly are you trying to mount your SD card in CWM anyway? It's already available to the computer when you are booted. Or take it out and copy stuff across.
[Xoom Android Development] slob13:
Thanks a lot, I've rooted my MZ601 without any problems. But I want to ask if I upgrade to ver. 3.1 I will lose root or not?
[Xoom Android Development] alias_neo:
There is no update yet, and you can't update without going back to stock. Don't worry though, soon as we get 3.1 ill update the guide and files.
[Xoom Android Development] davidebeatrice:
..but when...:-( c'mon moto...
[Xoom Android Development] Ish61:
sd card

Hi Neo,

Thanks for the brill guide......managed to root my xoom without any issues.

Can you help with enabling the sdcard or point me in the right direction???

cant seem to get it working.

much approciated. thanks.
[Xoom Android Development] MattCB72:
You need the Tiamat-Kernel to get the sdcard working.
[Xoom Android Development] davidebeatrice:
Hi Alias_neo.

I see the new tiamat rom (and ive posted also there). the new tiamat rom is ok for us?

Im still on 3.01 stock rom with stock kernel and recovery. I think to flash i need sd card working...so what ive to do? the tiamat kernel to enable sd card is only for 3.1 USA devices.

there is a way to finally do the upgrade to 3.1 with better kernel for us or not?

thx

cheers!
[Xoom Android Development] Ish61:
Hi MattCb,

Can u tell me which kernal to use? Any instructions pls?? Really appriciate it.
[Xoom Android Development] MattCB72:
Look in this thread, there you get the Tiamat-Kernel 1.4.1. Newer kernels don't work with Android 3.0.1.
[Xoom Android Development] Ish61:
hi,

it says 'In order to upgrade please be on 1.3.1 then 1.4.0 prior to using these instructions.'

my kernal on the xoom is : 2.6.36.3 - am i missing something?

thanks again
[Xoom Android Development] davidebeatrice:
Any news on 3.1 for our euro xoom?
[Xoom Android Development] m0rph3us:
Thanks, procedure worked perfectly...
[Xoom Android Development] gpf_drizit:
Would these be the stock images you need to unroot?

http://developer.motorola.com/products/software/
[Xoom Android Development] misc77:
Any update on this? I have MZ601 and completely missed your post and now running US 3.1 HC. NO 3G is available now! :(

Please help.

Can I just download the stock ROM from Motorola and flash it?

I'm in Singapore but the original ROM says MZ601.
[Xoom Android Development] misc77:
Thank God I managed to flash back the stock ROM and got it rooted via this thread correctly. Currently back to running 3.0.1. Will be patiently waiting for a ROM with 3G capability.

Cheers.
[Xoom Android Development] mickgeorge:
If you have a Euro 3G xoom and follow the instructions in this post http://xdaforums.com/showthread.php?t=1089695 you will end up with a fully functional Xoom - 3.1, working 3G and SD card support.

Took me about 20 minutes from start to finish
[Xoom Android Development] misc77:
I actually got stuck at the build.prop. I received phone error which I believe was not available in xoom. It tried to run the phon service background and kept popping up. Neither do I get a 3-G running.

Is there anyone can write out a brief version and cut out all the update information? I was a bit confused . Still is.

If you can help would be appreciated.

Thank you.
[Xoom Android Development] mickgeorge:
The problem with cutting and pasting is that people are likely to be following out of date info in a short pace of time, which is not a good thing in the case of the Xoom :-)

The relevant threads I followed were as below, and most definitely in that order (obviously skip step 1 if already rooted):

1)http://xdaforums.com/showthread.php?t=1049901 - this will give you a rooted 3G euro xoom. you don't need to go any further than the first post and stop after you've pushed SU to the device

2) http://xdaforums.com/showthread.php?t=1074979 - this will give you a fully working CWM recovery. Use this one, don't put v4 on as there have been incompatibility issues with the Xoom.

3) http://xdaforums.com/showthread.php?t=1089695 - this is the trickiest step, but still relatively simple if you can type accurately ;-) Start at pre-reqs on post 1. I'd suggest using method 1a (you can download unyaffs here - http://boomtopper.blogspot.com/2009/...ws-binary.html). I had to use admin CMD prompt to get this to work.

Do _exactly_ as stated in step 2, then download the build.prop as stated in step 3a and push it to your Xoom (if you do 3a, skip step 3b).

Pushing everything back in step 4 is fairly simple as long as you search out the files first from the nandroid backup and make sure they're sitting in the same folder as Unyaffs and ADB. However, DON'T carry out the final command "adb push build.prop /system/build.prop" as you've already done this in step 3a (as written, I think this will simply put your old build.prop back and you'll lose 3G - could be wrong though)

Reboot and you're sorted.

All I'd say is make sure you lock yourself away while you do it and concentrate, the instructions these guys have written are all fairly simple, the whole process is just a bit laborious.

Hope that helps, but don't blame me if you end up with a bricked device!
[Xoom Android Development] voxhel:
hi mickgeorge

i have done all on the 1st and 2nd links

on the 3rd link i have done until the step 2, with all the steps that the guide required

but after the last reboot during the booting fase i states and error but continues with the boot, something about "signature verification failed".

and the boot finished i'm still with the 3.0.1 :(

any idea how to solve this?

i have installed the ROM MANAGER v4.3.2.3 ClockworkMod Recovery free app from the market, and flash with Recovery Zip (solarnz-R4c-100611-1150) FLASHED THROUGH CWM

any idea?
[Xoom Android Development] emrahhh:
wifi not working please help me..

ı don't this method

fastboot reboot okay but

abd remount?????
[Xoom Android Development] mickgeorge:
I'm fairly sure installing the recovery zip with CWMv4 won't work (if it did, we wouldn't be having to use the Solarnz version?). You need to push the recovery with ADB. I'd suggest you give that a try and hopefully all will be well
[Xoom Android Development] mickgeorge:
I'm not sure there's enough in that post to understand the issue. Can you try and supply a bit more info?
[Xoom Android Development] terminal 7:
works for me

hi.

the "...in five steps..." method worked out just fine for me.

you do have to keep an eye on what your doing rather than just blindly following the instructions.

so just as long as you have ADB and Fastboot working in the same directory and the databases you pull ( or unyaffs ) along with your custom build,prop in the same folder too, you should be okay..

the only odd thing i found was that upon first reboot the "verizon activation fix" didnt work, from there i just did a factory reset in CWM and all worked just fine on the reboot :)

(if the verizon fix doesnt flash for you your xoom will ask for activation upon reboot)

its been a week ( or a bit more ) since i did the 3.1 conversion, the signal meter doesnt work properly as its trying to make sense of uk networks while being calibrated for usa networks, you can download a decent signal meter widget that shows you the truth though ( 3g - H - works fine )

just thought you might like my feedback :)

.

.

OH yEAH- and i always always use fastboot to flash the recovery, i never flash a zip as it seems to fail - if you fastboot a recovery.IMG it always gives good results, oh and never use ClockworkMod app to flash recovery from within the application as this seems to fail on UK Xooms also !!
[Xoom Android Development] redsat:
Worked for me too . I have 3G international Retail version.

Now on 3.1 / Tiamat 1.4.5 / SD / 3G / ....
[Xoom Android Development] jayz_style:
Brilliant took me 5 mins no hiccups and rooted my Xoom 3G UK with Wi-fi and 3G working and also tested few root apps and they working fine. Thanks alot, you rock.
[Xoom Android Development] Aeren:
I have recently acquired the MZ601 Xoom and decided to follow this guide. I am using Ubuntu 11 and have everything set up perfectly. I get the the following step

(using the files attached to the first post)

and it boots to the red motorola Dual core screen after typing the next step

and it just hangs there.....

muchos sad face.... any advice my fellow wizards of XDA.

It came stock with 3.1 out of the box if that helps....
[Xoom Android Development] mickgeorge:
and you successfully carried out the oem unlock step?
[Xoom Android Development] Aeren:
I did indeed. I believe that my system may have just had a hissy fit, it was a bad download of file....one of the MANY gremlins that plagues us modders.

I managed to get the stock files from ;

developer.motorola.com/xoomsoftware

flash that back to stock and lock it again. Back to step one and TRY again.....ahhhhh the things we do

although I must add that in doing that it took my 3.1 out of the box, back to 3.0.1...... -____-
[Xoom Android Development] iccy:
Just want to say TNX, the instructions aew awesome, rooted my device a few times.
[Xoom Android Development] ComfySofa:
im having the same problem - did the oem unlock, did the fastboot flash boot boot.img (copied and pasted it) now im stuck at the boot screen....is it knackered? only had it a day....
[Xoom Android Development] alias_neo:
Don't try and use this to root 3.1 its for 3.0. i need to make files for that.
[Xoom Android Development] ComfySofa:
ok - well - thats why then (mine was on 3.1) earlier a guy said that he downloaded a file from moto dev. (MZ601_H.6.1-38-1_Retail_Europe) which i got last night. Can i reflash that? and if so what are the steps or, if you make new files can the boot.img be reflashed? and (all these questions!!) how do i get the xoom back into a flashable state as its stuck at the M logo?

It looks like he did the same thing as me but he didnt post how he did it...i supose if i do the same thing then i can drop back to 3.0 root it and then do what i want anyway (which was my main goal) - the main thing was to root it to send sms's and use the phone part (aka as my last galaxy 7 tab) - im kinda missing that now...heh!
[Xoom Android Development] ComfySofa:
found the thread here (this is to the other guy that locked his up like me)

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

mines up and running again.
[Xoom Android Development] ComfySofa:
Im at the next step "adb remount" but its giving me a "error: device not found" do i have to change the device type in the manager or something....it is however working again now so im happy about that....
[Xoom Android Development] alias_neo:
It's an easy fix, just get the stock 3.0.1 from Motodev or on the forum here and flash back (and then either root it with this guide or update via OTA and wait).

I have been busy so I havn't even OTAd by own Xoom yet but i'll get on making an updated guide asap.
[Xoom Android Development] ComfySofa:
Thanks very much for your help. I am running again. did you see my earlier post - im kinda stuck at the adb remount bit....it just says error: device not found.

Some other questions.

Providing i dont do anything too drastic i can perform the reinstall of the stock image and oem lock it again.

Also - if i actually manage to get through this (at the start of the post) does it mean that once its rooted i can either stay where i am on 3.0.1 or go for a custom ROM (which one do you recommend)?
[Xoom Android Development] ComfySofa:
changed a little - for whatever reason the usb debugging wasnt on ( i thought it was ) - im getting remount failed: Operation not permitted.
[Xoom Android Development] ComfySofa:
sorry - answered my own question - flashed the wrong boot.img....it was still in there from the stock reimage...
[Xoom Android Development] ComfySofa:
ok - im there! - thanks very much for the help.

More questions.

Ok - so im here....rooted 3.0.1. is there a link for cwm install? and i take it after that im away installing whatever i want.
[Xoom Android Development] alias_neo:
Get solarnz clockworkmod and flash that with fastboot and you're good to go.

As for ROMs, try Tiamat Hammerhead, it's 3.2 and runs brilliantly on my UK 3G. I'd recommend anything these guys release.
[Xoom Android Development] Lupus77:
I got fed up with the T-Mobile ROM and no update stuff, so I flashed the 3.0.1 EU version yesterday. Worked like a charm and got the two OTA updates and I am running 3.1 now.

Next step for me was to root the devices, in order to accomplish that, I used the files Paul O'Brien (MoDaCo) has used in his australian 3.1 update ( http://android.modaco.com/topic/344...ra-h63-25-5-based-including-baseband-updater/ )

Here is a repack with only the needed files for root: http://ul.to/nxc83ldo

I am asuming you already are unlocked, you can get root with:

adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
adb remount
adb push su /system/bin
adb shell
ln -s /system/bin/su /system/xbin/su
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app
adb push bcm4329.ko /system/lib/modules
adb reboot
[Xoom Android Development] mercinellim:
Download link not working :-(
[Xoom Android Development] Lupus77:
Just tried, it's still working
[Xoom Android Development] ComfySofa:
Just got it on.....absolutely the best android device I've used yet....brilliant! Many thanks for your help.
[Xoom Android Development] mousi:
Wow that helped A LOT... I have a German Xoom (I bought it on ebay) and I hated Morelocale's Greek. So I did exactly the same thing as you and then I rooted it. Thanks!
[Xoom Android Development] trakcnik:
German to EU

Hi, inspirating posts. I have German Xoom 3G and going to make flash to panEU RAM and 3.01 > 3.1 > root.

@mousi: Is your 3G working well after this process?
[Xoom Android Development] Lupus77:
3G is working for me. Did you use the new files for 3.1 or have you used the 3.0.1 files?
[Xoom Android Development] boywiz:
Loving it

Very nice and very simple :D

I now have a Mz601 routed, Sweet!

Any news or idea on the 3.1 or 3.2 update for the rooted devices?

Cheers
[Xoom Android Development] alias_neo:
3.1 is out, ill get the euro root files in this thread asap.
[Xoom Android Development] mousi:
Sorry I just saw this... Yes everything is working fine, including 3g
[Xoom Android Development] alias_neo:
Sorry about the delay guys, new insecure boot image for 3.1 is in the OP, let me know if there are any problems.
[Xoom Android Development] cheetah2k:
Does anyone know if this will work on the 3G/Wifi Australian Optus MZ601 model??

I assume this is good for all MZ601 3G tabs?

*** edit, yes this works on Optus Xooms :) )
[Xoom Android Development] slob13:
Hello, sorry for stupid question but can someone tell me how to update to 3.1 if I have already rooted MZ601. Because when if offer to update it fails.
[Xoom Android Development] deb10042:
Great! Thank you for that!

Is there also a way to get USB-OTG working on the rooted 3.1 EUR version? :confused:
[Xoom Android Development] georg.madler:
Hi!

* Search the market for "USB Mass Storage Watcher OTG" and install the app.

* You need a special OTG-cable.

If you have those 2 things then it works...
[Xoom Android Development] alias_neo:
I will look at modifying the kernel to enable it, and we'll need a new vold.fstab

This works too.

I'm a little disappointed that it doesn't support OTG right off the bat, even my Galaxy S II does USB host just by plugging a device in, I'm sure the Americans got USB Host in their 3.1, or was that just bigrushdog/Tiamat that enabled it?
[Xoom Android Development] deb10042:
No, it doesn't, at least not for me :(

The USB Mass Storage Watcher OTG doesn't load/mount the connected devices (USB sticks or else). It doesn't seem to be a problem with the cable or the USB stick, as they both work with a Tiamat kernel.
[Xoom Android Development] deb10042:
That would be really GREAT! Thanks in advance for that! :)
[Xoom Android Development] deb10042:
Any news on that, alias_neo? Did you already have a chance to look into it?

Thanks! ;)
[Xoom Android Development] mfad:
3.1 Stock bootloader?

I'm just curious that if the attached boot.zip file has untouched, 3.1 stock boot.img? If not, could someone provide the file please?

Thanks.
[Xoom Android Development] alias_neo:
The boot image I attached is a stock, unsecured boot.img that I tock from the stock 3.1 build and modified only to enable remounting.
[Xoom Android Development] mfad:
Thanks for the quick reply. I actually thought that one of the boot files is untouched boot.img but it looks like both are unsecured images, one is for the old 3.0.1 and other's for 3.1.

I was just wondering if I want to unroot my 3.1 xoom, then I only have to flash the original 3.1 boot.img. So that I don't have to flash it to 3.0.1 first, then OTA 3.1 again.

Thanks.
[Xoom Android Development] alias_neo:
Unfortunately it 's not that simple, we don't have any 3.1 official boot images, since the update comes as a patch to 3.0.1. if we were to dump the 3.1 boot you couldn't use it to flash and relock because it wouldn't have the correct signature.

The best, and safest way to get back to stock is to go via the 3.0.1 stock image route and OTA to 3.1.
[Xoom Android Development] mfad:
Totally understood. Thanks again!
[Xoom Android Development] joja_2:
hi

first, sorry for my english...

well, i want to root my xoom eu 3g...

i type: adb shell chmod 4755 /system/bin/su

i view the result: unable to chmod /system/bin/su: No such file or directory

can you help me???

thanks
[Desire Q&A, Help & Troubleshooting] rajverma3135:
Hi Everyone

I googled alot to find any way to create/make a RUU file from Branded HTC Desire. but bad luck

Is anyone know how to create a RUU.exe or zip file from Branded HTC Desire, so that I can upload to shipped roms website/xda forum as well as save that file for myself for future use, if I need to return my phone to company.

I know on xda forum and shipped rom website there are many RUU available but i wants to create my RUU with respect to my carrier service provider.

I will be grateful n really appreciate this if someone could help me to do this

Many Thanks

Raj Verma
[HTC Incredible S] androf:
You rock man!
[HTC Incredible S] qvert:
thank you! nice guide!
[HTC Incredible S] chchia:
i flashed my IS two days ago with the similar setup process, i change the whole ROM.zip to PG32IMG.zip and never delete any files in the zip, the process is simple and fast.

now my hboot is 1.13(if i not mistaken...)
[HTC Incredible S] venezia64:
Yes 1.13 instead of 1.09 before. It's quite surprising that the flash process is allowed even if the CID in the .txt file doesn't correspond to yours... does it?

If you follow this guide next time, you won't have to reinstall clockwork recovery after each flash ;)