yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] cam30era:
It says on the OP, "fixed mounting SD card for some users ".
[Xoom Android Development] ankorez:
i have always probleme with last version
[Xoom Android Development] opsahl:
I was blind, but now I see.
[Xoom Android Development] andypotts:
Just a quick question.... as I am onto my 2nd xoom now....

Do I need to root before running through the steps "without cwm"?

I presume once I have ran through these steps I could then flash the 3.1 update.

I tried to root my last device with rootboot.img and totally bricked it.

Not sure if it being a UK 3g model makes any difference.

Thanks in advance, maybe im just being over cautious
[Xoom Android Development] opsahl:
solarnz

solarnz....

what happened to the tiamat android robot? He made me smile, now he's been replaced by the old hat. :/
[Xoom Android Development] starcms:
++10char++
[Xoom Android Development] cam30era:
Yes, you need to root. I would suggest following Land Master's tutorial in the Q&A section, "for noobs....."
[Xoom Android Development] andypotts:
managed it using "alias_neo"'s guide.
[Xoom Android Development] kgeissler:
I am having a problem that maybe someone can help with. I had stock wifi xoom. I received the 3.1 update yesterday and decided I want to change to CWM recovery. I installed the 3.0.2.8, but everytime I try to boot into recovery I get the android guy with the exclaimation point. I saw the above post saying you needed to run 2 commands since the stock recovery reflashes every time you reboot. Thing is, I don't have root permissions to change the file permissions on those files to run the command.

I then grabbed the stock recovery image for the wifi xoom and flashed that, but still get the same result.

How can I either 1) get CWM recovery to work or 2) get the stock recovery to work?
[Xoom Android Development] solarnz:
You need to flash this recovery in fastboot, do

fastboot reboot

Then about 3 seconds after you see the motorola boot logo, press volume down.

The select "Android recovery" with volume down, then volume up to boot.
[Xoom Android Development] kgeissler:
When I select "Android Recovery" with the volume down button, it starts recovery, but then gives me the Android logo with the exclaimation point.
[Xoom Android Development] archosfan:
Do i need a SD card for backups?

I tried to make a backup, but I always get the error:

"Can't mout /sdcard

E:Can't mout /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mout /cache/recovery/last_log

E:Can't open /cache/recovery/last_log"

I have EUR Xoom 3G.
[Xoom Android Development] solarnz:
Yes, an external sdcard is required for clockworkmod to function.
[Xoom Android Development] neaux:
+1

I have the same problem.

I updated my Xoom in 3.1. it is root

but no longer works CLOCKWORK RECOVERY

I tried these 2 commands:

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

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

I get the following message:

rm failed for / system / recovery-from-boot.p, read-only file system

should it work on 3.1? What can I do? :confused:

thank you and sorry for my bad English
[Xoom Android Development] matt4321:
You can use your internal SD card.

---------- Post added at 01:38 PM ---------- Previous post was at 01:37 PM ----------

Official CWM doesn't support the internal SD card, use this recovery or another that is modded to do so
[Xoom Android Development] beston94:
Will this work if I just updated my xoom to 4.0.4? And it doesn't have a unlocked bootloader or rooted?
[Xoom Android Development] airesch:
It will work on 4.0.4 (tho there are easier to use/better recoveries for the Xoom,) however you do have to have the bootloader unlocked (fastboot oem unlock) which if you haven't already unlocked it, it's going to wipe the device, so back everything up.
[Xoom Android Development] robbo10:
I need some help, I managed to unlock the xoom and fastbooted the .img from the op and all seemed to go well but when I run adb reboot recovery it never goes to CWM recovery. I get - -> android recovery, press volume up and I get

- -> Android Recovery

Entering Android Recovery Mode

Reading ODM fuse: 1

then I get the android with the triangle with a red exclamation. Stays there for a while then boots. Also tried manually and same thing.

I am on JB 4.1.2, I would appreciate some help tia
[Xoom Android Development] robbo10:
This was my problem :) all good
[Xoom Android Development] N-Gage4ever:
re-up plz
[Xoom Android Development] Dr_Wolodya:
Re-upload please.
[Xoom Android Development] soulburnerms:
please, someone reupload this file again =(
[Xoom Android Development] GaiusCoffey:
Yes, please reupload please!

Alternatively, I found the GitHub link in the start, is there a way to compile what we need from that?

Thanks,

G
[Xoom Android Development] jerryspring:
Will your recovery be able to flash 4.4 roms and up? I know a little about the big part recovery. Can you enlighten me? Thanks
[Xoom Android Development] MMT_2020:
Thank you
[Xoom Android Development] Diagon:
Just click through on the link in the OP, and you will see from the URL that solarnz-R4c-100611-1150 is the same as recovery-Tiamat-R4c-100611-1150-cwm.img

This person found it. I don't think you want this CWM recovery, though. I think you want TWRP-2.8.x.0. Read that thread. They are supposedly compatible with all the Xoom's (despite being labeled "Wingray"), and have both BigPart and non-BigPart versions.

BigPart Repartition Upgrade and Resource Center. Note the discussion in my link for TWRP, above. First you have to adjust the partitions, then install a recovery that is appropriate for the new, larger, /system partition. After that you flash a ROM that is BigPart compatible. If you ever want to return from a BigPart ROM & recovery to a non-BigPart ROM & recovery, you will have to wipe and repartition. There is some discussion here, though I haven't read it all yet.
[Xoom Android Development] kgeissler:
I followed these instructions and now mine is working great!

http://xdaforums.com/showthread.php?t=1078019
[Xoom Android Development] solarnz:
If you are indeed rooted, do

adb remount

before removing the files.
[Xoom Android Development] JiminSD:
where do you have your recovery.img file, should be in the tools file not on the sd card? I would check that.
[Xoom Android Development] neaux:
hello,

thank you for your reply, I solved the problem

I flashed boot.img with the stock and the recovery has worked

I then made ​​the 3.1 with Maj External Storage Enabled and everything works

thank you
[Xoom Android Development] lrs421:
Is it safe to make a nandroid on 3.1 with this latest recovery?

Also, can someone remind me how to manual reboot into recovery. Thanks in advance.
[Xoom Android Development] cam30era:
Yes. But backup is limited to a max file size of 4gb. If you have a lot of apks, games, and/or data you may not be able to.

To boot into recovery: Volume up + Power; then when you see the Motorola logo immediatly Volume down. Select Android recovery from the four options. "volume down" moves the curser and volume up selects. Once in recovery, volume down and up both move the curser, and power button selects. Good luck.
[Xoom Android Development] cam30era:
Nandroid backup does work

Wifi only Xoom.

Just an FYI for anyone that hasn't tried it yet: Installing a nandroid backup via CWM does work. It just saved my bacon. I tried to flash publicanimal's 3.1 wifi only files (following the procedure in his OP) over BRDs 3.1. After completing the first set of adb commands and reboot, my Xoom immediately went into a boot animation loop. So I rebooted into recovery and flashed my recent nandroid backup. Worked like a charm. For anyone who has CWM installed; if you haven't made a nandroid backup yet, do it now. It could save you a lot of headaches later.
[Xoom Android Development] lrs421:
You're a gent! Thanks for sharing, didn't realize the max size limit, only have a few apps though. Thanks again for the recovery reminder, I thought it was volume down and power then press volume up, thanks again :). I'm good to go now!
[Xoom Android Development] raviosopr:
I do the process of the 3 seconds afte de motorola logo and I still getting the android exclamation sign
[Xoom Android Development] zyexx:
I am trying this but I keep getting an error "cannot load recovery-solarnz-XXXXXX-XXXX.img"

how do I get past this?

Edit:When I reboot into recovery I get what raviosopr got, android exclamation
[Xoom Android Development] raviosopr:
you need to replace the Xxxxxxs with the numbers that the recovery file has
[Xoom Android Development] zyexx:
thanks but I got past that. When I try to reboot to recovery I see the Android with the exclamation sign
[Xoom Android Development] zyexx:
retried this a few times, same results....what am I doing wrong????
[Xoom Android Development] JiminSD:
What you describe will happen if you didn't, put the right recovery image in the right place. Name the recovery image recovery.img and put in your tools folder not your SD card. That's what happened to me, anyway.
[Xoom Android Development] zyexx:
I downloaded the file from the first post, is there another file I should use instead?
[Xoom Android Development] kgeissler:
Go to this link and follow the directions here to fix your recovery problem :

http://xdaforums.com/showthread.php?t=1078019
[Xoom Android Development] raviosopr:
i'm still getting the error, I think that the error is due to android 3.1
[Xoom Android Development] zyexx:
I too am getting the error. The sad thing is that there isn't much else that can be done until CWM is running ok. No root, no SD card fix. I dont even want to fully set up the Xoom and them lose all the data after I get all that done. sucks
[Xoom Android Development] gerald410:
If your flashing CWM and its not sticking its because 2 files need to be deleted (recovery-from-boot.p) and (install-recovery.sh). The commands to do so are

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

adb shell rm / system / etc / install-recovery.sh or you can use root explorer to remove them.
[Xoom Android Development] zyexx:
So I do this before or after I flash the recovery file?
[Xoom Android Development] starcms:
This is entirely not correct. The entire point of this latest version of recovery was so that the data/media folder (otherwise known as /sdcard or your internal memory) would be EXCLUDED from the backup. Therefore, one would never have a backup exceeding 4gb (or probably 1gb for that matter).

edit: PLEASE read the OP.
[Xoom Android Development] solarnz:
Before - this way the recovery isn't overwritten.
[Xoom Android Development] ankorez:
i have a same problem with recovery

for reboot in cwm you must use adb commands "adb reboot recovery"
[Xoom Android Development] cam30era:
OK. Thank you. BRDs had the 4gig limitation. Glad to know that this was changed.
[Xoom Android Development] solarnz:
Well this recovery still has a 4GB limit as this is a limitation on fat32.

However as this recovery isn't backing up /data/media, our nandroids shouldn't exceed 2GB.
[Xoom Android Development] cam30era:
OK. Thank you. Got it, now.
[Xoom Android Development] johnpwu:
Backup Error- Can't mount /data

After flashing 3.0.2.8, rebooting, then booting back into recovery, when I attempt to perform a backup, everything appears to work, until it gets to "backing up data..." at which point it returns "Can't mount /data!"

Is this what was being referred to with "If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard. This will revert to the old way of formatting /data. NOTE: by doing this you will lose everything that you have in /data/media."?

Edit: not sure if this is relevant, but when I open ROM Manager, it shows the current recovery as 3.0.2.5, but if I reboot into recovery, it shows 3.0.2.8. When I pull my sd card and plug it directly into my computer, the backup that ended in the data error does show up, and appears to be the right size, but I'm not sure what to make of that given the error during the backup.

Edit 2: I tried flashing back to 3.0.2.5 (which seems to have worked), then trying to perform a backup again. Now I get the same error with 3.0.2.5 as well.
[Xoom Android Development] solarnz:
No, putting eraseData in the clockworkmod folder will not have any effect on doing the backups. It only effects the formats of /data, I.E format /data, wipe data/cache (factory restore) and nandroid restore.

Are you able to boot your xoom?

What model xoom do you have?
[Xoom Android Development] z06mike:
These codes will not work because the file system is read-only. Is there a workaround for this?
[Xoom Android Development] ClydeB1:
Have you tried adb remount and then the rm commands?
[Xoom Android Development] z06mike:
This is on the stock kernel. Under remount, I get an "operation not permitted" error.
[Xoom Android Development] ClydeB1:
I think you will need to be rooted to remove those files.
[Xoom Android Development] z06mike:
Yeah, I think you're right :(.
[Xoom Android Development] johnpwu:
My Xoom boots fine. In fact, it seems to be doing everything fine, aside from letting me do a nandroid backup (the only error I'm seeing is that it can't mount /data).

I have the wifi only Xoom, unlocked, rooted, running 3.1.

Sorry about the lack of info. Thanks for the reply.
[Xoom Android Development] Squeak22:
Any chance that this could be modded to allow installing zip's from the internal storage? I know I should just buy another SD card, but I would rather give it to developers.
[Xoom Android Development] mnaim:
And of course backup to internal storage, now when is internal storage excluded from backup. That will be awesome.
[Xoom Android Development] solarnz:
It is entirely possible, I know birdman was working on this to get cwm working on the galaxy 10.1 tablet
[Xoom Android Development] solarnz:
I'll have a debug build for you to test later today that will enable us to collect more information about why you are unable to mount /data
[Xoom Android Development] johnpwu:
Wow, that would be great, thanks! I'm happy to do anything I can to contribute to stuff like this working. I certainly appreciate your hard work. Thanks again!
[Xoom Android Development] mrnicotra:
I have learned that 3.0.2.5 had a bug by which you could completely brick the device while trying to repartition from CWM. Is it really a bug? If it is was it solved with the newer releases?
[Xoom Android Development] solarnz:
I don't know, I haven't tried this.
[Xoom Android Development] jim_panse:
is there a way to make a backup to the INTERNAL sd? I don't have an external but I like to have a complete backup to play with.
[Xoom Android Development] bwcorvus:
Nope...external or nothing.
[Xoom Android Development] MiRaCL:
Maybe in just retarded, but how do i boot in to the recovery?

I followed some instructions while rooting the Xoom where i had to "catch" the recovery. Is this the only way to do it or can i boot from Rom manager?
[Xoom Android Development] RinTinTigger:
either connect the xoom to pc, and on command shell type adb reboot recovery (if you have the sdk installed and working)

or just grab "QuickBoot" of the market and choose "Recovery" in menue :)

Also RomManager should let you boot to recovery
[Xoom Android Development] rubixmaster:
I have read the entire thread, and I cant figure this out.

I am rooted on version 3.0.1, Running tiamat 2.6.36.3

I can see my SD card with a file explorer but I cant browse to it from my computer thus, I cant place the file on the SD card. What am I missing?
[Xoom Android Development] ClydeB1:
You should be able to see it, but I guess you could always just remove it from the Xoom and using a card reader copy the file on via your pc.
[Xoom Android Development] tonyb15re:
I downloaded ClockworkMod Rom Manager from the Marketplace, you can select reboot into recovery from that. Bizarre thing is though even though I have 3.0.2.8 installed this app still reports that its running 3.0.2.5, I assume its the same app and the same Dev who wrote it?
[Xoom Android Development] solarnz:
Once again... this isn't the official ClockworkMod recovery. This is why Koush's RomManager only shows 3.0.2.5.
[Xoom Android Development] tonyb15re:
Ok so is 3.0.2.5 in RomManager the same as the predecessor to 3.0.2.8 and will I have a conflict having these running on the device?
[Xoom Android Development] gerald410:
You should be only using 3.0.2.8 or later on the Xoom.
[Xoom Android Development] solarnz:
*bump for new version*
[Xoom Android Development] kev0153:
just installed new recovery image keeps booting back into recovery after selecting reboot option
[Xoom Android Development] cruzin_cruzing:
Currently have the same problem as above.
[Xoom Android Development] kev0153:
he's looking into, better hold off installing.
[Xoom Android Development] cruzin_cruzing:
Damn, so does anyone have the last version's download link/file.
[Xoom Android Development] kev0153:
here is a fix. reboot with volume button held down. This puts you in fastboot. Power down with volume up power button. Turn back on and it should reboot as normal. They figure on the problem and I suspect it will be posted again soon.
[Xoom Android Development] cruzin_cruzing:
Didn't work.
[Xoom Android Development] kev0153:
yeah doesn;t seem to work everytime. He is uploading the new files now
[Xoom Android Development] bwcorvus:
urz sftwarz brikd my ****z
[Xoom Android Development] solarnz:
Try flashing the image (not the zip) through fastboot.

(The download links are back, thanks kev0153 for alerting us in the #xoom channel)
[Xoom Android Development] vn_soft:
I have used clockworkMod 3.0.2.8 but i cant mount sd card or usb in recovery mode (i can access usb flash in ordinary use by astro). Cwm show me the text: it cant mount dev/block/mmcblk1p3):confused:

Anyone can help me or extract this file (mmcblk1p3) for me? . Tks in advance
[Xoom Android Development] cruzin_cruzing:
Still experiencing problems.
[Xoom Android Development] solarnz:
Flash http://dl.dropbox.com/u/13093938/recovery-solarnz-120511-2030.img through fastboot to the recovery partition. See if that helps.

If not, please come find us in #xoom on freenode.net.
[Xoom Android Development] solarnz:
Also try vol up + power.

Then as soon as the screen goes black, hold vol down + vol up at the same time for a cold boot.
[Xoom Android Development] kev0153:
This worked for me. Flash new recovery. Reboot and while the screen is black hold the power up and power down. Took me a couple of tries to get my fat fingers on the keys just right.

thanks to solarnz and BWcorvus for the help
[Xoom Android Development] bwcorvus:
Np glad you brought it to solarnz before it got to far out :)
[Xoom Android Development] Archangel:
installed fine for me dont know if it made a difference but once i flashed the zip in cwm i rebooted my xoom like normal and not back in cwm doing a nandroid now.
[Xoom Android Development] solarnz:
Yeah, the zip file was updated.
[Xoom Android Development] Archangel:
cool,,, took me a while to get cwm on my google io galaxy tab due to a bad usb cable,,,was hoping this would go smooth and it did, thanks
[Xoom Android Development] Archangel:
works like a champ!
[Xoom Android Development] Archangel:
may have spoke too soon got some wierd "cant mount cache" message when booting back into cwm

edit-may have been a fluke checking again
[Xoom Android Development] RinTinTigger:
THANKS SOLARNZ!

;)

(I only updated for the robot)
[Xoom Android Development] kevdog:
What's this new recovery do since I don't see anything added to the changelog in the first post?
[Xoom Android Development] solarnz:
I had this once a while ago.

Try downloading the image again and check the md5sum to be sure that the image wasn't corrupted when you downloaded it.
[Xoom Android Development] davidebeatrice:
same here...and now download wont starts...

other question: I tried to hard reset on cwm 3.0.2.8 by wiping data-cache and nothing happens. after restart all data was there...any suggestion?

thx!
[Xoom Android Development] cam30era:
Installed new .zip from CWM. Everything working fine for me.
[Xoom Android Development] movieifx:
I had same problem and md5 all ok. Tried flashing through CWM originally and then fastboot. Have reverted to 3.0.2.8 (solarnz-12051102030) which works fine.

Wondering if this is a none-US issue, I'm in the UK (on 3.1 with 3G wor around and latest Tiamat etc.
[Xoom Android Development] stevefxp:
Is anyone having an issue with the combination of CWM 3.2 and the latest Tiamat 1.4.4 kernel?

I updated CWM first, and rebooted to make sure it was active. I then flashed the Tiamat 1.4.4 kernel, and on the next reboot it hangs on the Moto boot screen.

Thanks,

Steve
[Xoom Android Development] cam30era:
Wifi only Xoom.

I have been running 1.4.4 for a few days. I flashed the 3.2 .zip from CWM this morning. Now I can't cold boot into bootloader or recovery anymore. Volume up + power just boots normally.
[Xoom Android Development] metaverse:
a Warning

Never do a "SD CARD PARTITION" with ClockWorkMOD recovery. You will brick your device beyond of any reparation. I knew that by the hard way :(
[Xoom Android Development] b0ricua:
The Robot is back! Flashed successfully!

Thanks solarnz!
[Xoom Android Development] cwizardtx:
Why does this option even exist if this is the case?
[Xoom Android Development] RinTinTigger:
why would u partitin sd anyways ?!?
[Xoom Android Development] b0ricua:
I posted a warning in the "Xoom General" forum warning people from trying to partition in either Clockwork or ROM Manager hoping it would get stickied.

Sucks, sorry to hear.
[Xoom Android Development] solarnz:
I will take this out of the next release.
[Xoom Android Development] solarnz:
Done. No more sdcard partitioning in R4b.
[Xoom Android Development] keunhuvac:
Hi!

How to extract *.img (like sytem.img, ...) after backing up?

I use unyaffs to extract but always get error!
[Xoom Android Development] Stealyourface:
Did you just disable it? Because I still see it under advanced.
[Xoom Android Development] solarnz:
If you go into it, it will tell you that it is disabled.
[Xoom Android Development] mcfisch:
Mine stucks in "Reading ODM fuse: 1" too. I'm on Tiamat 1.4.3, so can't be caused by 1.4.4.

I tried to update through CWMR from 3.0.2.8 to 3.2.0.0. It was working before, but now I can't get into recovery anymore. Will try to flash 3.2.0.0 via Fastboot.

Btw, cold boot didn't help...
[Xoom Android Development] 911junkie:
Flashed OK and booted up fine.

Re-boot into Recovery and I get the following errors:

e:Can't mount /cache/recovery/command

e:Can't mount /cache/recovery/log

e:Can't open /cache/recovery/log
[Xoom Android Development] mcfisch:
At first I've flashed 3.2.0.0 (R4b) via Fastboot - with the same result: device stucks at "Reading ODM fuse: 1". Then I've flashed 3.0.2.8 via Fastboot and this is working fine, can get into Recovery now.
[Xoom Android Development] cam30era:
Ditto here. US Wifi only Xoom. Flashed back to 3.0.2.8 and now I can boot into recovery.
[Xoom Android Development] Brenardo:
e:Can't mount /cache/recovery/command

e:Can't mount /cache/recovery/log

e:Can't open /cache/recovery/log

Same issue here as well....
[Xoom Android Development] BlackDino:
Everything seems to be working here Canadian WIFI (3.1)

I can boot into recovery on startup
[Xoom Android Development] BM1515:
my error message

i can get into the recovery fine but on the bottom it says

e:Can't mount /cache/recovery/command

Is this normal?
[Xoom Android Development] dominosus:
Unable to flash recovery

Hello all!

I flashing stock 3.01 for US WiFi, after that receiving 3.1 OTA. But now i can't flash CWM. Command "fastboot flash recovery ..." return "Done" (w/o errors), but after "adb boot recovery" i see original...