yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] jayhammy:
I'm really stuck here:

When I go into ROM Manager and try to install zip files from my sdcard, it doesn't go to the correct folder. And if I select a file from within RM to install, it reboots and says it doesn't find it.

Also, how can I find the sdcard from within recovery? Seems like it's reading only internal memory. Yes, I'm running the correct version of CWM--I didn't update within Rom Manager.

Thanks!
[Xoom Android Development] floomat:
is it possible to push this fixes into CWM 4.x? and is it possible to remove those horrible "No's" - Selection Screens when you try to do something? on nexus s there exists a customized cwm which looks a bit like amon-ra's and those "No's" are gone forever. I have no idea how to modify the recovery but if someone is able to do i hope it'll be done...
[Xoom Android Development] burnmatoaka:
I would prefer "NEIN" repeated 9 or 10 times myself. lol.

But seriously, I finally discovered this clockworkmodmod, and am pretty stoked to finally access my SD in recovery. Thanks, devs. Anyone care to elaborate on the fixes incorporated into the 4.x series? Anything stability related? Thanks in advance for any info.
[Xoom Android Development] okantomi:
We don't advise using the 4,0 series. You don't have access to external sdcard from recovery for flashing updates or doing backups. Use the recovery in the OP of this thread!
[Xoom Android Development] burnmatoaka:
Using it, thanks. Didn't hat too much a problem w/ the 4.x series in the three days since I rooted my four day old xoom, but I do prefer not having to rely on the internal "sdcard." My question was regarding what non-sdcard related changes were merged into the 4.x series that are not currently present on this bad-boy. I didn't have any stability problems with either this or the 4.x CWM. Koush doesn't really keep a running changelog, at least not where I've been able to dig it up. Just trying to be as informed as possible. Thanks for the info.
[Xoom Android Development] gitit20:
Will this work OK for the new 3.2 update? I am rooted thx.
[Xoom Android Development] solarnz:
This recovery should work across all Xoom devices and android versions.
[Xoom Android Development] pariksheetsharma:
It worked ... Thanks a lot.
[Xoom Android Development] parabola949:
I'm having a slight issue -

I do the reboot bootloader, flash the recovery image, reboot.. then reboot recovery - all I get is the Android with Exclamation. I can get to stock recovery.

I saw a reply earlier (page 2) that explained recovery was being replaced on every reboot, and to rm some files.... but I don't have root, so of course rm is denied.

Just picked this thing up, running stock 3.2 HTJ85B, not modified at all. It's actually my jobs Xoom, they asked me to write something for it, but I can't seem to get CWM on to it, root it, anything. And yes, it is unlocked. That had no issues.

Thoughts?
[Xoom Android Development] parabola949:
Nevermind on my previous post - I did not see this reply....

I got it to work now, apologies

Thank you much dan.expo for this information, and thank you solarnz for the great guide!
[Xoom Android Development] mjforte:
I am trying to erase EVERYTHING from my Xoom. I put the "eraseData" without the quotes in the clockworkmod folder but it still doesn't delete everything. My issue is I updated to 3.2 on my 3G Xoom and then tried to flash the Tiamat kernel for 3.2. That really messed up everything because now I get force closes again and again on everything. Tried going back to 3.1 and still get force closes. I just want to delete everything and start over. How can I do this?

Edit: Well I went back and restored stock images through fastboot and was able to get everything working again. I was a little scared I wouldn't be able to get my Xoom back to normal, but all is good now.
[Xoom Android Development] radi0chik:
I had the same problem yesterday mjforte - but after 12 hours (!!!) of messing with it, I finally got hammerhead on it thanks to help from solarnz

Keep up the good work guys!
[Xoom Android Development] ComfySofa:
Gents - does this work on a uk 3g xoom ? and if so i noticed one guy was having a problem with v4 (i think) which is different to the one at the front of the thread 3.2 or am i reading that wrong?
[Xoom Android Development] okantomi:
Please use the version on this thread. Version 4 is not compatible with the external sd card--won't save a back-up to it, won't flash from it. The Tiamat v3.2.0.0 R4c is customised for the Xoom and works with all models.
[Xoom Android Development] Barsky:
Trying to do a restore. First, it wouldn't see the sdcard, so I copied it to the internal 32gb storage. (also there was no mount option for the sdcard).

I was then able to run restore, but it errored out wheil restoring /system.

Did I do this to myself by allowing Rom Manager to update CWM recovery?

Would reflashing with your CWM file perhaps fix this?

Thanks
[Xoom Android Development] shmigao:
Most likely yes
[Xoom Android Development] Barsky:
Yep. Looks like it is restoring sytstem now. Hmm. They said go ahead and install rom manager, but of course you can't use it until you let it install. Xoom was the only item in the list, so I thought it would be ok. shrug. I think all will be good now regardless.

thanks.

Update: oh yeah, that's the good stuff. success
[Xoom Android Development] okantomi:
Absolutely yes. There should be a huge flashing warning sign: DON'T LET IT UPDATE!
[Xoom Android Development] Barsky:
Hehe yep. No plans to install that again on this thing. No big loss. Not especially needed.

Thanks
[Xoom Android Development] scriptx:
speed up backups

heres a tip for those of you using clockworkmod recovery to perform nandroid backups: create a file named " .hidenandroidprogress" in the /microsd/clockworkmod directory, NOT in /sdcard. recovery will read this file and will omit the content listing and progress bar during backups, which will drastically improve the backup speed.

Cheers!!
[Xoom Android Development] debosmebo:
I did a backup with 3.2.0.0 but when I went to restore after I was testing the Android 3.2.2 and trying to go back to my backup. It restored but no data restored. I had to re-install all my apps and everything. Has anyone else experienced this problem?
[Xoom Android Development] okantomi:
You were probably "updated" to v4.0.0.4 in Rom Manager.
[Xoom Android Development] jrock60:
I am only able to boot into recovery if I select it from the CWM app. I know that I am supposed to push vol down after I see the Moto logo but it never works for me. Is there something Im missing? I really need this feature because just in case something happens and I end up unable to boot into the OS I want to be able to restore my backup using recovery and without the need for the PC.
[Xoom Android Development] okantomi:
If you are rooted, the simplest way is to download the Quick Boot app (free is fine) from the Market and that will allow you to boot right into recovery. Very easy. I just don't use Rom Manager because it constantly tries to update you to that v4.0.0.4 recovery.
[Xoom Android Development] Alxoom33:
The string posted appears to have a wrong "10/6" update date

The update date of this post "10/6" is wrong, should be 8/6?
[Xoom Android Development] solarnz:
Nope. This hasn't been updated since the 10th of june.

I'm from New Zealand, which doesn't use the American date format.
[Xoom Android Development] Legato Bluesummers:
two quick questions for this.

One, is it " .hidenandroidprogress" with hidden with one "D"?

Or is it ".hiddenandroidprogress" with two "D's"?

and two, will this affect when you flash OS updates or other files through CWM? Like whenever the next Solarnz ROM comes out, would i still see each stage of the update (flashing kernel, flashing system, ETC...) or would that be hidden as well? I wouldn't mind speeding up backups, but i also like to know the progress of the updating process so if it fails i can see where.

Thanks
[Xoom Android Development] solarnz:
.hidenandroidprogress

It will only effect nandroids.
[Xoom Android Development] Legato Bluesummers:
LOL i am stupid. Sorry. Didn't even think of it being worded like that. :( sorry
[Xoom Android Development] Alxoom33:
Oh, OK. I thought it was a typo. Sorry.:p
[Xoom Android Development] debosmebo:
I double checked and am still on CWM 3.2.0.0 when I go into recovery. the Rom Manager just doesn't recognize it. Oh well, I guess 3.2.0.0 is not meant to backup data.
[Xoom Android Development] okantomi:
No it totally is, if you have a microsd card in your Xoom when you boot into recovery.

Download Quick Boot from the market and use that instead of Rom Manager to boot into recovery if you don't want to do it manually. I actually don't even use Rom Manager for anything now.
[Xoom Android Development] kcrudup:
Yeah, it's happened to me, too- after 3.2.2 didn't work, I'd tried to restore everything thru Solarnz' recovery (3.2.0.0) and while it appears to be restoring the data, when the device comes up it's like it's completely fresh. Do you get prompted with either "Select language", or with the default circular lockscreen when you boot after a restore?

That's what's funny- I've actually had to wipe completely and restore an earlier CWM backup before using 3.2.0.0, and that worked just fine.

I think the 3.2.2 .zipfile modified some file somewhere (outside of /system, /cache or /data) that makes the system ignore the restored data and start off clean every time Not happy! :(
[Xoom Android Development] bigrushdog:
Hey kc. After this rom release, which will not support lte 3.2.2 yet, we will put fresh focus on a new recovery. Give the team rogue recovery a shot. I've ran it for a few days and its pretty smooth. Ill email ya later.
[Xoom Android Development] kcrudup:
Well, it used to work OK! :)

I think I figured out the failure mode- the restore isn't complete. Backup size on the data.img file seems OK, but there's several directories missing when the restore completes.

I'll try that.
[Xoom Android Development] rockhumper:
I agree it would be nice to have new recovery, with more awesome robots! Dragons are ok and all but I am not into tribal art. Robots for the win!
[Xoom Android Development] debosmebo:
Exactly, it appears it restored the data but didn't. Its funny because I got the lock screen I backed up. No language selection though from my memory. It sounds like we had about the same experience with it.
[Xoom Android Development] kcrudup:
Question- did you have an active Exchange Mail account set up before you did the backup?
[Xoom Android Development] debosmebo:
No................................
[Xoom Android Development] kcrudup:
Damn, that rules out my other theory, that because I was connected at the time of my backup to an Exchange Server that had the "Wipe device on lockout" property set, that perhaps if there wasn't a token set somewhere that wasn't part of the backup (? wild-assed guess on my part) that the software was set to wipe the device on boot.

I stopped being mad about this a couple of days ago, esp. since it's been reported that Moto will wipe your X when they do the LTE update anyway.

But what's been especially troubling is that I've borrowed a Galaxy Tab 10.1 from the office- it's completely stock- and although it's got the same processor and essentially the same OS, it feels much smoother than even my 1.5GHz OCed Xoom, and the IPS screen is niiiiice. It hasn't lagged on me yet, something my X does sometimes at random.

If it weren't for the fact that it's got the proprietary dock connector and no SD-Card, I'd've probably gone out and bought the GTab 10.1 LTE version this weekend. I just wonder what the Xoom 2 will be like.
[Xoom Android Development] padanfain:
I am rooting/installing my friend's xoom and running into a problem. I did the following:

adb reboot bootloader

fastboot oem unlock

fastboot reboot

used volup+power to get into fastboot again

fastboot flash recovery recovery-filename.img

fastboot reboot

wait for reboot, adb reboot recovery

Instead of seeing cwr like I expected, I got an android with an exclaimation point on it. If it hit volup+power i get a menu where it says "android system recovery (3e)" and gives me the option to reboot or flash an update from a usb drive, or wipe cache / data.

What is going on here? why can't I get the recovery to work?
[Xoom Android Development] rockhumper:
Adb reboot bootloader

Right before flash of recovery?

Are you typing the actual recovery file name into flash recovery recovery-filename.img? Or contest your exact wording? Did you put the recovery image into sdk tools folder or the platform tool folder? HonestlyI used the three steps on page one and had no problem, but you seem to have a few different steps than instructed..
[Xoom Android Development] Fieser-Kardinal:
I've flashed the latest R4C Version on my Xoom EU 3G + WiFi with HC3.1

All went well but as i enter Recovery i get a few Error Messages:

What went wrong and how do i fix this?

<edit>

Sorry, my SD-Card was broken. Replaced it and all is working well!
[Xoom Android Development] onorevolelux:
I have the same problem...
[Xoom Android Development] KaitenII:
I had the same issue just now..... Might be worthwhile checking the rest of the thread. I found a solution for mine.
[Xoom Android Development] aussiechris:
G'day Guys

I'm having a very similar issue. I can flash recovery successfully through fastboot, but can't boot into it.

I can't seem to boot into recovery using the Vol Down key on my Aussie 3.1 Xoom. Instead of CWM I get NvFlash, RSD and Fastboot options.

The system seems to replace recovery with stock if I reboot and use adb to reboot into recovery.

It's a catch 22. I need recovery to flash root, but I need root to stop the recovery being replaced so that I can boot it and flash root etc...

Has anybody had this experience? or any suggestions?
[Xoom Android Development] twinkyz1979:
What kind of file are you supposed to place in the directory on your ext sdcard to revert back to erasing all data? i mean is it a txt file or what
[Xoom Android Development] enmriley:
Flashing custom recovery help

Hello, really need some help here. I have tried to install the universal recovery from both my Mac as well as Windows (albeit the Win attempt was XP on Virtual Box from my Mac). I am running the following commands on XP and Mac respectively:

Win

\android-sdk\platform-tools

adb reboot bootloader

fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

Mac

/android-sdk-mac_x86/platform-tools

adb reboot bootloader

fastboot-mac flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

(I even tried renaming this to simply recovery.img)

I get the following error on the Mac terminal after about five minutes from sending the flash recovery command (on XP it just hangs indefinitely)

ERROR: usb_write failed with status e00002ed

FAILED (data transfer failure (No such file or directory))

The Xoom shows:

Starting Fastboot protocol recovery support,

(in red text) "Failed to process command error (0x120003)

I am running the US WiFi unit, 604 (although I am not sure where I can confirm this on the device) with Android 3.2.1, Build HTK75D. The recovery is physically located in the Platform Tools folder with Fastboot-mac. Any advice would be greatly appreciated. I am familiar with rooting my two phones, but am stuck on this one.

---------- Post added at 11:04 PM ---------- Previous post was at 10:47 PM ----------

At the risk of sounding like a true noob, is it possible that the universal recovery could be packaged as the "update.zip" and flashed from the stock recovery?

Thanks Kaitenll for the quote describing that once you get to the Starting fastboot... text you hit the vol down too soon. I spent hours (literally) hitting the button too soon when trying to setup the unlock (but at least got through that). Knowing this I can get into the options menu every time. Now if I can get the recovery to transfer!
[Xoom Android Development] okantomi:
I answered you in the other thread where you posted this. Make sure you are calling the recovery image file by the correct name when you try to flash it. Better yet, rename it recovery.img.
[Xoom Android Development] enmriley:
Thanks okantomi. I did indeed rename the file to recovery.img with the same error. I am wondering, I unlocked the device a day before trying to flash the recovery file (before I got the timing correct on the reboot I spent many hours on this and then went to bed). The Xoom was then rebooted and used for a day or so until I had time to continue with the root. Is it possible that the "unlock" is only valid until the device is rebooted (i.e. booting into Android relocks the device)? If so, that may be my issue and I can start from scratch again with the unlock command.

Just got home and tried this from scratch (i.e. successfully performed the unlock again). Still the same errors when flashing the recovery. Can someone repost the recovery they know to work?

imacs-imac:platform-tools imac$ adb reboot bootloader

imacs-imac:platform-tools imac$ fastboot-mac flash recovery recovery.img

< waiting for device >

sending 'recovery' (3998 KB)... ERROR: usb_write failed with status e00002ed

FAILED (data transfer failure (No such file or directory))

imacs-imac:platform-tools imac$

I am starting to think the issue is that I am running Android 3.2.1, Build HTK75D.
[Xoom Android Development] okantomi:
The recovery that's known to work is the one in this OP but the guide in this thread calls it the wrong name--should be solarnz not tiamat (that was an earlier version).

I'm not familiar with the way the mac does adb, so I can't comment on what you have posted...seems pretty strange to me, like syntax is wrong.
[Xoom Android Development] kcrudup:
Your issue is related to USB transfers, and has nothing to do with your loaded build/Android version or the version of the recovery.

"No such file or directory " is a pretty big clue.

Try a different cable, don't use a hub, etc. too.
[Xoom Android Development] enmriley:
Guys,

Please keep the thoughts coming, I do appreciate it. Here is some feedback.

1. When I select the recovery on the OP, I get the Taimat one. Is the link broken? Can you post the known working recovery here?

2. I tried the same approach on XP, the only difference being "fastboot-mac". Are you suggesting there is different syntax than this (other than the fastbook-mac, this is just the file name for the mac version of fastboot). If so, please post.

3. I have been able to unlock and run other commands through fastboot-mac with no issues. But I will try the alternate cable just so it is covered.

Now, where am I?

I noticed (the first time I got into the stock recovery) that I had the Android guy and the exclamation mark. I started to think maybe the Firmware was corrupt with the latest OTA update to HTK75D. I downloaded the latest files from MotoDev and executed appropriately (see below for syntax). Unfortunately the stock recovery would still not load (although I could unlock, and run every other command). After a reboot, the Xoom is now stuck at the "M". I can still get into fastboot, but a second attempt didn't change anything. I also noticed this morning when trying different key combinations of the vol buttons, that just after hitting power (from the off state) if I hold both vol buttons, I get “Cold-booting Linux, Reading ODM fuse: 1″. Could this be a means to revert to 3.2.1 or did I already scrog that? The problem is that I can't execute this command (there may be a specific key combo? Not sure I even want to go here though). I was under the impression that flashing the US GED (for the WiFI only) was available to anyone with a WiFi unit, regardless of current version. I kinda wish I could flash a previous version just to get past what I think 3.2.1 is creating here. Anyway, not giving up so if you could spread the request for assistance, I am sure there are some geniuses here at XDA that can help. Worst case, since i am out of warranty, I pay Motorola to fix it.
[Xoom Android Development] enmriley:
Great news. I found a site that included a good (high-level) description of fastboot commands (link is pasted in below). I decided to erase the Recovery partition and rerun all commands. I am now at 3.0.1 and running fine (3.0.1 is apparently the latest files from MotoDev). I assume I can now use the Universal zip method, but need to ask a few questions.

1. Do I need to update to 3.2?

2. Can someone please repost the link with the latest recovery? When I select the recovery on the OP (even though the OP shows solarnz), I get the Taimat one. Is the link broken?

http://www.gotontheinter.net/content/fastboot-cheat-sheet
[Xoom Android Development] enmriley:
Xoom Family Edition and CWM

Does anyone know if the CWM will run on the Xoom Family Addition? It comes stock with 3.2.1 so I assume it will, but wanted to check if anyone had any experience doing so yet.
[Xoom Android Development] twinkyz1979:
is anyone ever going to update this of the newer CWM 5.0 recovery?
[Xoom Android Development] okantomi:
If you can't unlock it and root it you can't install this recovery--it requires root.

---------- Post added at 10:14 AM ---------- Previous post was at 10:08 AM ----------

This is a custom Xoom recovery. If the developer finds a feature of v5 that he wants to incorporate, he probably will. I think everyone is waiting to see what effect ICS will have before investing a lot more effort into current mods. Just my feeling.
[Xoom Android Development] rockhumper:
Why? Just to have the latest version number....this one works plenty fine and I have only had misery from version 5 on my other rooted devices...if it ain't broke no need to fix it
[Xoom Android Development] twinkyz1979:
Cause it doesn't work with the new option in titanium backup or the option that appextractor brings to the table. it might work fine but things always need to be updated for the new things out and those yet to come.
[Xoom Android Development] Mohfath:
Big problem

uhhhh

I give up I have a problem for 3 days and now I want to share it with you.

The problem is:

Recovery Mod Says: I'm doing something and it wont!

to be more declarative I must say:

* When I choose a zip file to install, it acts as it is really doing it and when the process completes successfully I see that nothing has changed.

* Recovery crashes on deleting System/Data

* I cant even change recovery itself, I couldnt do it even with fastboot (I tried fastboot remove recovery)

And that was my story, I've vome up with a corrupted ROM and cant update and replace it with any other ROMs.

so anyone got a clue? please tell me even if you are not sure. I'm so desperate...

Peace out
[Xoom Android Development] BatGnat:
Am I crazy?

I am trying to backup.

But every time I do, It continually backs up /data/media which I don't want.

Am I missing something? I am on latest version.
[Xoom Android Development] jdlaser:
Question

When I go to download the recovery file, the link says the name is solarnz etc, however the saved file is named tiamat etc. What is the file name that we should use? I don't understand why the name difference in the link and the actual file.
[Xoom Android Development] scotto811:
To get around this, I simply installed the recovery (I was stock EOM unlock HLK75F) then on the reboot I mashed the down VOL and went straight to recovery and flashed the rom of my choice. This may be easier for some?
[Xoom Android Development] jabster42:
OK. Gotta ask a dumb question....The instructions say to use fastboot to flash recovery.img, but the link is to a recovery.bin.

Can I just rename to img? Or is the bin some kind of compressed file? I'm running Linux, if it matters.

Thanks,

john
[Xoom Android Development] jabster42:
Apparently it's a Chrome thing. I tried downloading with firefox, and I get the correct IMG extension.
[Xoom Android Development] Waza_Be:
Mine is trying to install since 20 minutes:

Should I stop it?
[Xoom Android Development] Craxx:
... i think 20 min it is not normal..... Normaly it takes onle some seconds or max 2-3 min. I would try again.....but no warrenty...
[Xoom Android Development] rockhumper:
Uhhhhh dude u ****ed something up....mine never looked like that when flashing....