yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] jiwengang:
A little feedback on the update through this method.

At the same time I would like to ask my fellow xoomers' if you have similar observations.

I have US wifi Xoom.

method 1

I used the method described here flashed it once to upgrade to 3.1 from wifi stock (I returned to stock completely first)

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

method 2

Then I saw this great great effort by BRD, so I flashed it following exact steps and every step was ok.

then I noticed that

1. screen resolution from method 1 is SO MUCH better than screen resolution from method 2. (I am the one , guess not the only one who flashed twice using two methods, actually maybe only a few minutes apart from each flash. I definitely feel the difference)

2. home screen browsing in method 1 was SO much smoother than the home screen browsing experience in method 2. In fact in method 2, sometimes I swipe the screen and it even did not response.

3. similar to 2, apps opening and running etc are noticeably slower than the experience from method 1.

Basically to me, it feels like the 3.1 from method 2 was generally like UI of 3.0.1 and core of 3.1 (necessary functions were there)

To confirm if the above 3 observations are true, I re-flashed using

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

again, and it re-confirmed my suspicion.

The method 1 only used custom boot.img in intermediate step and it flashes back stock boot and system before upgrade, so I would say it is generally a pure google experience upgrade except with the help from cwm. Could guru devs please check further and see if the method 2 changed something that is unnecessary to change at this stage?

Quite frankly, to me , a very smoother UI and swift apps opening and running experience overrule sdcard support, well it may not be same priority for others and I do respect that.

Again, just a little feedback and please have a look into it if possible

Appreciate the dev's great work to our community!!!
[Xoom Android Development] jlaw904:
Back to 35 linpack... eeek.
[Xoom Android Development] jiwengang:
If you have working cwm then it looks to me likely your zip file is not correctly downloaded.
[Xoom Android Development] bwcorvus:
Then you did something wrong...the recovery in the first post does not have access to /data/media (ie sdcard) to clear it.
[Xoom Android Development] joeski27:
No, I can assure you, one of the first things I did was install the "new recovery", and that installed perfectly. I'm not the only one who has had this happen, so please don't assume that I did something wrong.

And it isn't "/data/media" that is supposed to be protected - as the post clearly states it is supposed to protect "/sdcard"
[Xoom Android Development] LNKNPRKFN:
This worked FLAWLESSLY!!! THANK YOU for your time and effort, didnt really want to unroot/Relock, Glad i waited...
[Xoom Android Development] SS2006:
followed ecverything perfectly

now stuck at Moto logo

I was initailly on android 3.0.1, rooted with the one click root (so it didi install some tiamat kernel)
[Xoom Android Development] bwcorvus:
"NOTE: Your internal storage (aka /sdcard) will be safe from this wipe. However, all other userdata will be wiped. Seems to be a necessary evil."

Read much? internal storage is /sdcard aka /data/media/. As one of the testers of the recovery, i think i may know a thing or two about it. This has nothing to do with your external sdcard aka /data/sdcard/external.
[Xoom Android Development] ajayendra:
SD Card wiped!...all my music...uhhh...will have to reload again...glad I made a tbu on my external SD. External SD shows.

Also, Tibu pro doesn't work on 3.1

Can someone confirm if the USB host is working?
[Xoom Android Development] Didact74:
Wow, that's a bit concerning. I hope that's not the case but look forward to any responses. I am rooted, unlocked, and on tiamat 1.4.1 and am patiently waiting for all the foam to settle before trying to upgrade to 3.1. I am pretty happy with my xoom as it sits right now and am patiently waiting for visual and performance feed back. Thanks to the devs for all the time invested in this upgrade!
[Xoom Android Development] LNKNPRKFN:
Ya i found the "oneclick root" a bit risky, try holding power and +vol to reboot then tap -vol until fstboot then press +vol to confirm, then you can try adb reboot recovery, i was at the same issue, you may have to go back to stock and relock then use http://xdaforums.com/showthread.php?t=1058272 to reroot/unlock and get to 1.4.1 kernel then do the above TUT for the update, just a suggestion
[Xoom Android Development] b0ricua:
I seemed to bork my browser by restoring data (trying to restore bookmarks). Can someone hook me up with the browser file so I can push it?
[Xoom Android Development] SS2006:
You mean you need to be on 1.4.1 tiamat to upgrade? i think it works frm the SD card regardless, i was able to flash from it
[Xoom Android Development] ebaca:
I get a file not found on rapid share for the update file and the bootloader patch file.
[Xoom Android Development] dscribe:
Wow. I,m sorry, all I can say is "wow"
[Xoom Android Development] publicanimal:
Try 3.0.2.8 it always works for me:

http://xdaforums.com/showthread.php?t=1038870
[Xoom Android Development] wwwhershcom:
Can any one reup the files, download links on't seem to be working.
[Xoom Android Development] dscribe:
Interesting. I too have installed via both update methods but I got pretty much exact opposite results per method so I surely don't know what the deal is.
[Xoom Android Development] publicanimal:
My internal storage/SD card folder was wiped during the factory reset. Fortunately I had a nandroid which I am restoring now.
[Xoom Android Development] rcmojo66:
USA wifi Xoom user. I download the 3 files - completed steps 1 & 2 without problem. Got aborted install on step 3. I rebooted the Xoom and now I'm stuck at the splash screen. I'm able to reboot into ==> Fastboot - Starting Fastboot protocol support - tried running adb reboot bootloader but device is not recognized. Is there anything I can do or did I ruin this Xoom?
[Xoom Android Development] konman795:
Is it supposed to take forever when it's flashing system.img? Never done this before so I'm starting to wonder if it froze or if it just takes that long.
[Xoom Android Development] SS2006:
takes 2 minutes here
[Xoom Android Development] SS2006:
Well I went back to stock image (thread is in forums)

then rooted again (not using One click tho) but using this method

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

Then formatted by SD Card in an android phone (fat 32) and did the process again

this time it WORKED!

so i donno if the initial problem was due to the one click root (the kernel it installed)

or the SD Card, but hurray
[Xoom Android Development] b0ricua:
can someone e-mail me a copy of their browser.apk from HC 3.1? I killed my browser trying to restore a backup and get nothing but FC's.

Any help would be appreciated.
[Xoom Android Development] dscribe:
Grats! It has been quite the adventure eh. :cool:
[Xoom Android Development] godkillax:
I'm running Clockwork 3.0.2.8 with a 4GB SDcard installed which I can read on SDCARD2 directory and I can't get Clockwork to flash anything from the SDCARD.

I'm running Tiamat 1.4.1 kernel. Any ideas why I can't flash anything in clockwork and I keep getting "Can't mount SDCARD"?
[Xoom Android Development] SS2006:
can soemone see if thier automatic brightness is working after installing this

on mine even if i check auto brightness, it retains the same brightness that was manually set
[Xoom Android Development] publicanimal:
I noticed some interesting differences between this and the WiFi version of 3.1. Using this version there are Verizon specific Hotspot/tethering options in the Settings menu that should not be there on my WiFi Xoom.

I don't know why but this really bothers me. I don't want any trace of Verizon on my Xoom. I restored a Nanroid of the WiFi version of 3.1 and those options disappeared from the settings menu.

BRD - First of all THANKS for this and the new recovery. Second, will you be releasing a kernel that could activate external storage on the WiFi Xoom version of 3.1?
[Xoom Android Development] kmckis1029:
thanks this worked like a charm :)
[Xoom Android Development] starcms:
If people followed directions, this would not have happened. The new recovery that BRD posted does NOT in ANY WAY affect/touch/modify the data/media (/sdcard) directory at all. The only way that directory can be wiped is if you do a hard reset inside of Android OS instead of inside of CWM.
[Xoom Android Development] lokko21:
hope it helps.
[Xoom Android Development] konman795:
Okay so my xoom is stuck on flashing system.img for the past 30 minutes now and it's starting to heat up like crazy. How do I shut it down manually and what could be the problem?

Man...I'm starting to panic now, adb reboot returns: "device not found"

Xoom still stuck at the flashing new system.img screen :(
[Xoom Android Development] dscribe:
When I checked mine it seemed the same to me at first but when I turned my brightness all the way down and then checked auto it did brighten a little. It is looking to me like the brightness you set does have a big effect on the autobrightness feature.

Update: After looking at this again I think you are just plain right.
[Xoom Android Development] pablo1010:
hold power and the volume up
[Xoom Android Development] konman795:
Okay cool, I think it may have been a corrupt file because mine was only 134mb and redownloading it shows its 135mb. Hope it works *crosses fingers*

Woot, everything worked out fine, thanks for all the help!
[Xoom Android Development] drawde:
Worked perfectly! Thanks!
[Xoom Android Development] publicanimal:
Funny, because I did a hard reset inside of CWM! So that is NOT "the only way" the directory can be wiped.

I think the error in BRD's directions was that he does not say to reboot after flashing the new recovery. So I was still inside the old recovery when I did the factory reset, even though I had flashed the new recovery.

For anyone using the WiFi XOOM, this is not the same version of 3.1 that we have on our devices, this is the Verizon 3G version modified to work on our devices. If you flash just the boot.img and not the system.img that is in BRD's zip, you can get external SD storage working on the WiFi-only version of 3.1 (I just did it and it works perfectly).
[Xoom Android Development] jland22:
Followed OPs instructions and everything was easy and worked. Not complaining but some observations:

- Titanium backup does not recognize any of my system aps or user aps.

-google restored most apps

-lost everything in my internal SD

-kept everything in my external SD (CWM backup, recoveries, etc)

-alhtough not noticable, quadrant benchmarks are low, averaging 1700.

-rom manager will revert your new recovery to 3.0.2.5 and doesnt need to be used any longer.

I am happy with all the hard work the people are doing here in these forums. I am not sure at this point which of the observations are results from the OTA and expected and which ones are from the process of putting them on while keeping root, cwm, etc. Just wanted to point my experience.
[Xoom Android Development] ericizzy1:
did it, works great, thank you
[Xoom Android Development] sleeplessninja:
Thank You! Patience paid off.

I made a video, surprising yes I know, following your steps. Hopefully it can help clarify some questions or just for those who want to see how this process works.

[YOUTUBE]YRpKh3Koqr8[/YOUTUBE]

http://youtu.be/YRpKh3Koqr8

Also for those who don't have ClockworkMod Recovery Installed you can follow this video. Really easy to do.

[YOUTUBE]Or-qVYj2avQ[/YOUTUBE]

http://youtu.be/Or-qVYj2avQ
[Xoom Android Development] gorgio1:
just ran it on my wifi xoom worked flawlesss

Thanksss
[Xoom Android Development] Zerxer:
It does say, and has said for awhile now, that you should reboot your device after flashing the new recovery.
[Xoom Android Development] Hyperion82:
Thank you !!! :D
[Xoom Android Development] jonnypedantic:
Looks like encrypting was a horrible, horrible mistake. Since the external sdcard was rendered completely nonfunctional after encrypting, CWR is completely useless. And the only way to remove encryption is a complete factory reset. So I have to start from the absolute beginning just to flash this. This is going to be fun.
[Xoom Android Development] burden010:
OK I've searched the thread but can't find any info on this question:

Will this work on a UK wifi Xoom? As all the wifi Xooms are the same model the hardware is the same. Software builds are different though.

Additional Q: If I do a nandroid backup in CWM then flash the US images and update can I then go back to my nandroid backup or do I need to flash original images again?
[Xoom Android Development] starcms:
Beat me to it. It's been saying that ever since BRD posted the thread.
[Xoom Android Development] tribalb:
need help. forgot to wipe and now it just loops the startup screen. cant fastboot into recovery nor adb. any help please

*edit* nm. forgot theres a option in fastboot to wipe userdata and cache. finally started up.
[Xoom Android Development] starcms:
If you followed the instructions, specifically step #3, then you will now have the option to boot directly into recovery from the bootloader, even though previously you could not with a wifi xoom.

Turn on the Xoom, about 1/2 second after the Motorola screen appears, start tapping volume down. You'll get a menu with 3 options that can be scrolled through with volume down. Select recovery and press volume up for enter. You are now in recovery. If you already followed steps 1,2, and 3, simply choose wipe data/factory reset inside recovery and reboot. Welcome to Android 3.1 :D
[Xoom Android Development] tomcrown1:
First I want to say everything worked fine and data was kept on the internal and external card. Still have all of the like the typing lag etc . #3. 1 stinks. I Have also noticed no support for overclocking.
[Xoom Android Development] starcms:
Uh...fragmented sentences/thoughts much...:confused::confused::confused:

Did you also notice any mention of support for overclocking? :rolleyes:

BRD will need to release a new kernel for 3.1 before you get overclocking back. One day at a time.
[Xoom Android Development] publicanimal:
If anyone is interested in a flashable version of the WiFi only version of the 3.1 update, I have one available in this thread. It does not require a data wipe and enables external SD storage.

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

I know that this one works for WiFi only but it has 3G only artifacts in the Settings menu like Hotspot tethering.
[Xoom Android Development] starcms:
In your thread you state BRD's has "Verizon software." In actuality, it has one little option enabled in the OS which allows tethering to show. If you notice, it has no mention of Verizon anywhere. It's very similar to enabling the SIP dialer, which by default is disabled/hidden on both the 3G and WiFi Models.

edit: And I can only speak for myself, but I would much rather have an extra option in the menu present than have Videos and potentially other programs not working.
[Xoom Android Development] p2flol:
Worked great on my wifi xoom, thanks alot. Glad I didn't lose root.
[Xoom Android Development] stevenege:
Flawless Victory

Went off without a hitch.
[Xoom Android Development] publicanimal:
True enough, I guess the Hotspot feature isn't Verizon specific. I changed the wording a bit in the post. There are no programs that don't work other than Videos. And that plagues the official WiFi update in general, not just my version of it. Anyhow suit yourself, I thought there might be some people out there who don't want to wipe data and want the software that was specifically made for their device.
[Xoom Android Development] starcms:
Videos app is working just fine on my WiFi Xoom using BRD's update.
[Xoom Android Development] flombs:
Thank you, thank you, thank you!!! :D

I've asked this question a bit with no reply, so here's hoping, is there a way to update without losing my external sdcard2 access?

Cheers!
[Xoom Android Development] starcms:
Yes, just follow the directions by BRD in the OP.
[Xoom Android Development] bpelletier:
Hi there,

I have tired CWM 3.0.2.5 and the new one, but It cant see the SD Card, (error mounting), I have formated it in Windows (windows sees the card fine if I put it in the , I have 1.4.1 but I cant see it either in the Xoom (sdcard2 or External) any ideas?

Thank you.
[Xoom Android Development] flombs:
Could I just follow the video instead? Its the same thing, right?

My brain processes pretty videos better than typed instructions. :p

I know I'm being pedantic, just want to make sure I don't stuff the work I've done s far to my Xoom.

Thanks again, starcms. Your a legend and a squire for the help.
[Xoom Android Development] starcms:
Haven't seen the video personally, but I'm sure it would be of help. You will have to do a wipe data/factory reset inside of recovery, so be sure to make a backup using Titanium Backup so you can easily restore all of your apps+data+settings.
[Xoom Android Development] siscim23:
If you have an Android phone, format it with that. If not, find an sd formatting program and format with that.
[Xoom Android Development] starcms:
Make sure you are using windows to format it as FAT32 and not FAT(FAT16) or NTFS.
[Xoom Android Development] gigafast:
I messed up and didn't complete step 5 :

Step 5: Return to main menu. Do a "wipe data/factory reset"

NOTE: Your internal storage (aka /sdcard) will be safe from this wipe. However, all other userdata will be wiped. Seems to be a necessary evil.

I restarted instead and now stuck the honeycomb start image. What should DO? HELP!
[Xoom Android Development] futuregerald:
Just wanna say thank you thank you; it was hard to wait but waiting paid off. On top of it all people in IRC were helpful as well when i had a question. I love XDA, thanks so much :D
[Xoom Android Development] starcms:
Hold power and volume up to restart the xoom. About 1/2 second after the Motorola screen appears, start tapping volume down. You'll get a menu with 3 options that can be scrolled through with volume down. Select recovery and press volume up for enter. You are now in recovery. If you already followed steps 1,2, 3, (and 4 if you have 3g model) simply choose wipe data/factory reset inside recovery and reboot. Welcome to Android 3.1 :D
[Xoom Android Development] gigafast:
Thanks for the advice but, I only get Fastboot > NvFlash > RSD oprtions. Which one is recovery?
[Xoom Android Development] starcms:
None are recovery. Judging from those 3 available options, you have a WiFi model and did NOT complete step #3 which would have replaced the NvFlash option with the recovery option.

Sorry, I'm not sure how you should proceed from here. Not to sound like a smartass, but next time just read the directions: they are extremely simple and straight-forward.
[Xoom Android Development] gigafast:
You are right. I didn't properly read the instructions. Got distracted at work and didn't follow through. Still can anyone give me a hand please?

Thank you,
[Xoom Android Development] gerbick:
Using CWR 3.0.2.5, worked fine for me - and I didn't even reboot after flashing new recovery.

Regardless... flashed up to 3.1, no FC's, seems speedy enough - the Quadrant scores are much lower now than I had with Tiamat 1.4.1 - yet for some reason, Titanium Backup does not work.

Is that part normal?
[Xoom Android Development] xmellyx:
You need adb. First, dl the recovery.img from step one. Place the recovery.img into your tools folder that the you adb from.

Next you need to reboot and press volume down until you get the option for fastboot. Press volume up to get into fastboot and type:

"fastboot flash recovery recovery.img" without the quotations.

This should flash the new cwm. Now type:

"fastboot reboot" to reboot the xoom.

Tab volume down at boot and you should now have the option to get into recovery and start from step 2 again.
[Xoom Android Development] starcms:
Benchmark scores will be lower until BRD releases his Tiamat kernel which supports 3.1.

Regarding Titanium Backup, download BusyBox installer from the market, and using it install BusyBox 1.18.4 to /system/xbin/. Then restart Titanium Backup and you should be all good. Also, make sure you have USB Debugging enabled in settings->applications->development.
[Xoom Android Development] starcms:
That won't work. He has the Wifi Xoom. The old bootloader on the Wifi version (which is updated in step #3 of the OP) has no option in the volume down menu at boot for recovery. It doesn't matter which version of recovery is installed.
[Xoom Android Development] akodoreign:
Yup, you need to do the persistence fix. I had to use root explorer to do it but here are the instructions.

Originally Posted by Berzerker7 View Post

In order for the CWM flash to stick you must run the following commands:

Code:

adb shell rm /system/recovery-from-boot.p

adb shell rm /system/etc/install-recovery.sh

Flash CWM again and it should stick.
[Xoom Android Development] cam30era:
For those undecided and still on the fence....

Coming from Tiamat 1.4.1 and CWM 3.0.2.8. Wifi only Xoom.

Everything works exactly as described. No problems at all. Maintained all data on internal sdcard. External sdcard still mounts and is accessible (as stated in OP by BRD).

But you must read, understand, and do exactly as BRD says in the OP.
[Xoom Android Development] gigafast:
I am still only getting the 3 options without recovery as one of them. When I entered fastboot flash recovery recovery.img i get the following:

Flashing allowed for partition recovery

Onewire: Charger is not connected or battery is not being charged...

Device 0x8000 (hp0). Battery charge level : 73%

Flashing StorMgr partition recovery STATUS: - done!

on computer :

fastboot flash recovery recovery.img

sending 'recovery' (3936 KB)... OKAY [ 0.490s]

writing 'recovery'... OKAY [ 1.020s]

finished. total time: 1.511s

No luck.. :(
[Xoom Android Development] starcms:
You're still missing my point. It doesn't matter whether the stock recovery, CWM 3.0.2.5, CWM 3.0.2.8, or CWM 9.9.9.9 is already successfully installed on the device. There is NO WAY to boot directly into recovery from power off using volume down on a WIFI Xoom unless step#3 was performed which updated the bootloader adding the option to boot into recovery.

WIFI Xooms, until this post with the updated bootloader, have never had the option to cold-boot into recovery because the only 3 options in the bootloader were NvFlash, Fastboot, and RSD. The 3g model had the fourth option: Recovery. The new bootloader (step#3) removes NvFlash, and replaces it with recovery on the WiFi Model. On the 3G model, it simply removes NvFlash and keeps recovery.
[Xoom Android Development] starcms:
Excellent advice. 5 minutes of reading and comprehending will save 5 hours of headaches.
[Xoom Android Development] gigafast:
So I'm out of luck???
[Xoom Android Development] starcms:
No, I'm sure there is a way -- you definitely aren't bricked for good -- I just don't know what it is. I'm sure someone will be along that should be able to help more.
[Xoom Android Development] gigafast:
Thanks for the optimism. I'm really sorry to be tying up this thread. My fault for rebooting early, but any help would definitely be appreciated!

Thanks everyone! :confused:
[Xoom Android Development] jondwillis:
BRD, hook us up with an OC kernel ;)
[Xoom Android Development] gigafast:
I'm Back!!! At least for now.

Here is what I did:

I went into fastboot OEM Unlock and it cleared everything.

Then fastboot flash boot boot.img

Started up!

I'm going to flash that recovery image now... !!!
[Xoom Android Development] jrezin:
mz604 br

with BRD's instructions, worked pretty well on my MZ604 BR... just lost some original wallpapers that wasn't included in the US version (anyone got them? that tron cycle like blue and orange? =] )

...just not sure what MZ604 version I have now... ;]
[Xoom Android Development] cypher0815:
Also coming from Tiamat 1.4.1 and CWM 3.0.2.8. on a german 3G Xoom.

Everything seems to work except 3G :( Is there a chance to get it running?