[RECOVERY] ClockworkMod Recovery v3.0.2.8 [UPDATE 5/1]
- Thread starter bigrushdog
- Start date
- Status
mine says
mount
mount
unmount
if that helps and i only get the error when loading from power not rom manager or quickboot
mount
mount
unmount
if that helps and i only get the error when loading from power not rom manager or quickboot
So you can't restore either? It says error on boot image?
Sent from my PC36100 using XDA App
Sent from my PC36100 using XDA App
It must have to do then with the message Koush sent to BRD saying he needs to change the way the sd cards are mounted with his latest kernel. IIRC, it was said the internal sd card needs to be mounted as mmc something or other and sdcard2 needs to be sd card. I think BRD is working on this for the next kernel release.
exactly right, it will evolve into a more user friendly app in the future. I would not worry about it right now just do not rely on the nandoid back ups for right now and wait for a more solid fix to come out.
I installed both. first, I updated Koush's CWM that I already had installed from a while back, and then about an hour ago I installed BRD's recovery.img file.
So it is an interface issue with clockwork and the sd card mounting i am sure it will be fixed soon
I have
- mount /sdcard
- mount /system
- mount /cache
- mount /data
Ok, I only installed the BRD version. I installed Rom Manager but didn't update Recovery.
Ok sorry guys do what I'm getting from all this is everyone can back up. But can't restore? Thanks
sent from my evo
sent from my evo
Does it really matter which one I got?
I may be wrong on this, but if you want to enter recovery from initial power up (ie, from the red M logo then push the vol down button) then you need BRD's recovery.img. And then of course, if you want to boot into recovery from the operating system, use CWM and/or Quickboot. My guess is that it would be smart to have both
and your still getting the same cache error mounting when you power on and boot into recovery?
LOL i do not think you can have two recovery.img files loaded one will overwrite the other. Just an interface issue with clockwork and your sd card right now it will be fixed i am sure. The BDR and rom manager should be essentially the same recovery.img?
Does it really matter which one I got?
I may be wrong on this, but if you want to enter recovery from initial power up (ie, from the red M logo then push the vol down button) then you need BRD's recovery.img. And then of course, if you want to boot into recovery from the operating system, use CWM and/or Quickboot. My guess is that it would be smart to have both
I would say yes for now so dont rely on your nandroid backups to restore until it is fixed
Ok sorry guys do what I'm getting from all this is everyone can back up. But can't restore? Thanks
sent from my evo
I only have the one and I can still boot to CWM via Rom ManagerDoes it really matter which one I got?
I may be wrong on this, but if you want to enter recovery from initial power up (ie, from the red M logo then push the vol down button) then you need BRD's recovery.img. And then of course, if you want to boot into recovery from the operating system, use CWM and/or Quickboot. My guess is that it would be smart to have both
I get this error: (from Rom Manager and from boot up)
E:Can't open /dev/block/mmcblk1p3
(No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
been experimenting since last night, w/ music and movies on my sdcard, nandroids are only ~350mb. after factory reset, rebooted to make sure everything was gone except sdcard content, and restored nandroid back to original state w/ widgets, homescreen, etc. in tact.
happy customer as always, brd
happy customer as always, brd
Need an SD card?
Check out eBay - they have some wonderful prices on name brand 32 GB microSD cards. Already ordered a SanDisk for myself - should be in tomorrow. YEHEY!!
Check out eBay - they have some wonderful prices on name brand 32 GB microSD cards. Already ordered a SanDisk for myself - should be in tomorrow. YEHEY!!
How did you restore? It keeps telling me. Error deleting boot image
Sent from my Xoom using XDA App
been experimenting since last night, w/ music and movies on my sdcard, nandroids are only ~350mb. after factory reset, rebooted to make sure everything was gone except sdcard content, and restored nandroid back to original state w/ widgets, homescreen, etc. in tact.
happy customer as always, brd
Sent from my Xoom using XDA App
- Status
Similar threads
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
35ClockworkMod Recovery
Installation Instructions
Pull up your command prompt, then
Code:adb reboot bootloader fastboot flash recovery recovery.img fastboot reboot
Let your Xoom boot up. Then to check out your shiny new recovery,
Code:adb reboot recovery
Also, you can grab Rom Manager or QuickBoot from the market for easy access to recovery.
Download
ClockworkMod Recovery v3.0.2.8
MD5SUM: 9c851890ca04232cf95d0f224f7529752well, it looks like we are having issues with the boot partition. I am looking into this. In the meantime, used advanced restore and restore system and data manually. Use quickboot to easily access recovery from the Xoom. I am close to having a solid updater script so we can start flashing kernels, mods, and other stuff from recovery. Soon, no more of this fastboot crap!1About a day or so ago, I stated the following in another thread...
bigrushdog said:
I think this statement was probably premature. Flashing recovery has ABSOLUTELY NO EFFECT ON YOUR ANDROID SYSTEM. Recovery is completely separate. In the not-to-distant future, we should have a mod that will allow your Xoom to treat sd card as the system sd card. In other words, when you take a picture, it will go on the sd card. Also, apps will automatically store data to the sdcard. However, this future mod will have nothing to do with recovery.1
No, you don't. Recovery is completely separate from the rest of the system. But a new kernel is in the pipeline. And its wicked.
