yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] shingers5:
I am on the verge of taking the thing back right now. I actually think the xoom is better than the transformer or iconia a500. I have owned all 3 devices and chose this one. However the lack of dev activity for uk xoom owners is a downer and moto stance on releasing 3.1 update to us also puts me off. Its a shame really as this is a solid piece of kit. 3.0.1 is so buggy on this its not funny. Anyway maybe hold on a bit to see if moto can drag the 3.1 from japan and spread it over here. Moto fail again
[Xoom Android Development] Trig0r:
Yeah I know what you mean, Motorola really dont seem to give a rats which is a shame as I picked the Xoom over the ipad2 because its Android and 3g where as the iPad is just 64gb wifi..
[Xoom Android Development] ed.dark:
Mate, bite the bullet and flash the rom from this post. Then flash tiamat kernel. Its an awesome piece of hardware let down by 3.01. 3.1 is cool and tiamat has let on that regional zooms will be supported. The future is very bright!
[Xoom Android Development] shmigao:
I think so too. MZ601 here running 3.1, tiamat kernel and EU mods and happy
[Xoom Android Development] Trig0r:
New ROM from the Tiamat guys, downloading now..
[Xoom Android Development] hiamster:
Sigh, just tried the new Tiamat......however still unable to get my 3G working on this 3.1 ROM.

tried pushing the databases and build.prop all over again still couldn't get my 3G to work.... =(
[Xoom Android Development] Trig0r:
havent flashed the new one yet, been busy at work, just trying it now..
[Xoom Android Development] mcfisch:
I've installed it this evening on my german xoom - it works out of the box :D

Had running the 3.1 running (followed this guide) before. After installing the Tiamat 1.1 I flashed the language-pack 0.5 at 1st - resulted in bootloop. Wiped again and reinstalled the ROM, now having the system in English, it isn't a serious issue.

The strange thing is: I haven't pushed the telephony-databases back as I did with this mod before, but 3G was working from the beginning. Speedtest says 4.9/1.5 MBit/s down/up, so HSPA is workin, I assume.

The only issue I've found atm is with the keyboard (EN & DE) - some strange behavior with the number-keys and backspace: number-keys sometimes give the special chars located on this keys at a physical EN-keyboard, backspace behaves like delete-key. I've also Hacker's Keyboard installed, so will use this until the other one gets fixed.
[Xoom Android Development] Trig0r:
Got it working here on my UK Xoom on vodafone at the mo..

We need to get some way of flashing language packs seperatly..

Maybe if we could compare the files pushed back in step 4 we could build ones that cover the euro devices and then push them back in a zip via CWM instead of adb maybe do the same with the apn settings etc.

I did start a seperate thread but no reply as yet, perhaps not that many euro device's?
[Xoom Android Development] shmigao:
The problem as always: not as many Euro devs as US devs...

The primary culprit is the framework_res file. If one dev can update the multilanguage framework file to the one in tiamat 1.1 then it should be pretty much ok
[Xoom Android Development] Ready1:
Xoom on Telstra Next G

So what did I do to my xoom

I opened the box and realised i have plenty of charge to just go ahead and root + upgrade to 3.1..

Followed lowtraxx instructions word for word and for all the noobz please to do not skip a step (its 100% noob proof, take it from me)... I now have a fully working rooted xoom running on latest Tiamat kernel + overclock patch + SD card (love the external)

Thanks lowtraxx all i have to now is take the protective cover on the back and screen :)
[Xoom Android Development] redsat:
Dears,

I went through post one , and now I'm ROOTED , and on HC3.1 but NO Radio (3G) available .

My XOOM original Built Number was : H.6.1-38-9 (Other_International_Retail)

Now is : HMJ37

I've CW 3.2.0.0 .

Kernel Version is : 2.6.36.4 Tiamat_Xoom-v1.4.5-Alpha

What should I do now to fix this? .

EDIT : I used Build.prob.frankenrom (Cause I don't have mine).

EDIT : NOW I'm OK . I fixed it . Tnx to the Forum with it's good posts.

Tnx
[Xoom Android Development] lowtraxx:
Updated the thread with updates pertaining to the 3.1 AU images.
[Xoom Android Development] Marshall1975:
Lowtraxx

What do I do with the md5 file. Do i need to save it as some sort of file then put it in the created folder on my sd card
[Xoom Android Development] lowtraxx:
CWM Checks the md5 sums of the images before flashing the. You have to copy the md5 file into the folder where the images lie like described in the AU thread. Then you can flash them seperatly.Just click right on it and use "file save as..."
[Xoom Android Development] Tim24:
Lowtraxx, which system languages are included in the 3.1 AU image?
[Xoom Android Development] Marshall1975:
Lowtraxx

Copied them from your link. Saved as nandroid.md5 and placed on sd card. Every img I try to rrestor just always gives me an md5 mismatch error.
[Xoom Android Development] lowtraxx:
You have to do exactly as described in the other thread. And create a new nandroid directory and copy the img and the md5 files there.
[Xoom Android Development] lowtraxx:
As far as I can tell all there are for honeycomb.

All types of english, german, french, italian, chinese, dutch,...
[Xoom Android Development] Marshall1975:
Lowtraxx

I did exactly that. Created new folder under /clockworkmod/backup/20011-07-09.22.22.22. Copied the files you posted into the above folder. Then copied and pasted the md5 figures into notepad and saved as nandroid.md5 and put that in the folder with the images.

Im guessing im doing something wrong. Can you see anything from my above procedure thats not correct.

Thanks
[Xoom Android Development] Marshall1975:
Lowtraxx

Can you just confirm Im doing the correct procedure regarding the md5 figures.

1. Copy them from your link

2. Paste them into notepad

3. Save the file as nandroid.md5

Thanks
[Xoom Android Development] :
@Marshall

Hey bro, are you sure it's supposed to be "/20011..." and not just "/2011"?

Gonna try this later - I'm fed up waiting for official 3.1 :-)
[Xoom Android Development] lowtraxx:
Have you tried right click save as, should not matter, but with windows I m not sure :-)

I also had a typo in the post, which I corrected, the date is wrongly formatted instead of 20011 is should read 2011. Could you try if this fixes your problem. If not I don't have any more options ATM. Look at your latest backup, and analyze the file structure, your new folder should have the same sstructure with the same file names.

HTH
[Xoom Android Development] Tim24:
You have to modify the nandroid.md5 to

287cf689a3dafe9985ee8d11cb14ffa0 boot.img
9216fac5cdda042466127d4739711008 data.img
cd6f989e202c37a3fe3874331cef0cfc system.img

to flash the images within CWM without MD5 mismatch error.
[Xoom Android Development] Marshall1975:
Lowtraxx

Have corrected the typo and checked the structure of my own nandroid backup and everything is identical. Still MD5 mismatch

Tim

Tried your suggestion and still MD5 mismatch

Am completely stumped now. US 3.1 I guess it is for the moment.
[Xoom Android Development] :
Hmm, I decided to try this and I now have the same problem as Marshall! MD5 mismatch, no matter what I do... Any solution?