This is really odd, i just updated Clockwork Recovery to 2.0.0.5, i then tried to flash to behnam's cyanongen mod 5.0.8-test7. I used Clockwork to download the rom + googleapps..ok good so far, once the download was complete i was offered to backup the existing rom and or wipe data...i chose simply to wipe. The phone then asked me to confirm the reboot, which i did, and it rebooted the phone but now brings up the black phone with a red triangle. If i press vol up + power i access the recovery menu but haven't attempted a flash because i don't know why i now don't have a properly functioning recovery? I seem to still have root access from within my currently installed rom too :S
Help lol?
I had exactly the same thing with the cyanogen rom and rom manager. If you go ahead and press volume up and power while in the red triangle screen, the recovery will carry on and work as normal. I've done it a few times now.
N
socktug said:
I had exactly the same thing with the cyanogen rom and rom manager. If you go ahead and press volume up and power while in the red triangle screen, the recovery will carry on and work as normal. I've done it a few times now.
Click to expand...
Click to collapse
and if when you press those buttons the recovery doesn't automatically launch, click on apply update.zip, this is the recovery image
cgrec92 said:
N
and if when you press those buttons the recovery doesn't automatically launch, click on apply update.zip, this is the recovery image
Click to expand...
Click to collapse
Hmmmm interesting...so re-applying the recovery update.zip will just fix it? Wonder what changed in clockwork to make this happen?
MojUk said:
Hmmmm interesting...so re-applying the recovery update.zip will just fix it? Wonder what changed in clockwork to make this happen?
Click to expand...
Click to collapse
Correct, I'm not sure why it happens randomly, that is how you'd access the recovery image, the image is the update.zip on your SD card. So apply that and you're there
i'm using the latest recovery and i can't mount the sd card anymore with /moun sdcard it gives error /dev/block/mmcbl0 can't be mounted,
never the less when i start amonra recovery batch and then go back to connect with adb shell to the still running clockwork recovery it works to mount the sd card strange behaviour
excuse me for this noob question... but what is this Clockwork Recovery?
vuoshino said:
excuse me for this noob question... but what is this Clockwork Recovery?
Click to expand...
Click to collapse
Do a search for it on this forum, or try searching rom manager in here. There are at least 4-5 threads on it. One of which is very big! Try searching for 'fake flash'
endursa said:
i'm using the latest recovery and i can't mount the sd card anymore with /moun sdcard it gives error /dev/block/mmcbl0 can't be mounted,
never the less when i start amonra recovery batch and then go back to connect with adb shell to the still running clockwork recovery it works to mount the sd card strange behaviour
Click to expand...
Click to collapse
this is not an issue, it is a feature of the new clockwork
i have spoken to Koush and what this means is that you are not using Apps2sd so there is nothing to be backed up.
the error should therefore be ignored as it is not a problem
Erm, this sounds like a bug. Can you join IRC:
http://webchat.freenode.net/?channels=koush
Ask for me, I'll be available.
I'm using apps2sd so the ext partition is there and schould be backed up!
i reverted to 1.8.9.2 (i think) and i backs up my ext partition just fine !
i'll join irc later !
Thanks to Koush for the assistance, top man.
Seems that some how the 'command' directory and 'update.zip' were missing from my /cache/ :s
koush, really nice support, fixed the sd-ext not mounting and not backing up in nandriod bug, and the mount sdcard bug within an hour over irc perfect!
could you post the solution koush gave?
just update to the latest recovery image (2.0.1.0)
mine's only offering 2.0.0.9
i talked to koush as well, nice fellow!
scroll down in Rom manager to older images, there you ll find 2.0.1.0
endursa said:
scroll down in Rom manager to older images, there you ll find 2.0.1.0
Click to expand...
Click to collapse
cheers
Unfortunately still not working for me on the latest Recovery (2.0.1.0)
Tried to backup my sd-ext (since that's where my A2SD apps are) and got:
Code:
E:Can't mount /dev/block/mmcblk0p2
(Invalid argument)
Could not mount sd-ext, sd-ext backup may not be supported on this device. Skipping backup of sd-ext.
I think my partition is ext4 if that makes a difference.
BSAB said:
Unfortunately still not working for me on the latest Recovery (2.0.1.0)
Tried to backup my sd-ext (since that's where my A2SD apps are) and got:
Code:
E:Can't mount /dev/block/mmcblk0p2
(Invalid argument)
Could not mount sd-ext, sd-ext backup may not be supported on this device. Skipping backup of sd-ext.
I think my partition is ext4 if that makes a difference.
Click to expand...
Click to collapse
Can you send me an ext4.ko? Recovery currently only supports ext3.
Related
in clockworkmod, im trying todo a backup and i get:
can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk 1)
no such file or directory
cant mount /sdcard
i did the unrevoked3 flash method.
FYI: I can mount in usb mode as hard drive and load mp3s.
i installed cwm rom manager and it cant mount sdcard. is my sdcard bad?
binaryhat said:
in clockworkmod, im trying todo a backup and i get:
can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk 1)
no such file or directory
cant mount /sdcard
i did the unrevoked3 flash method.
FYI: I can mount in usb mode as hard drive and load mp3s.
i installed cwm rom manager and it cant mount sdcard. is my sdcard bad?
Click to expand...
Click to collapse
BUMP: I'm having the same problem, used gparted to repartition sdcard which allowed me to Mount USB storage. When i try to mount /sdcard card i receive
Code:
E:Can't mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1)
(Invalid argument)
Error mounting SDCARD:!
Are you using setcpu? I had same message the other day when in clockwork. I had an idea to try to set speed back to stock and unchecked set on boot, rebooted in to clockwork and all was well. Not sure if the clockspeed and and set on boot has anything to do with it, but I had a feeling that it messed with backup/restore when writing/reading a custom speed specified to boot with. Anyway it worked for me on virtuous with 7.28 radio and kings bfs 5
Had the same issue... Formatted the SD card (using the phone, under settings/sd card) and it never happened again.
vangorder said:
Had the same issue... Formatted the SD card (using the phone, under settings/sd card) and it never happened again.
Click to expand...
Click to collapse
to follow this up, i was experiancing similar problems
like an idiot i ejected the SD card with the power on (bad idea) and had to format it
the card worked fine under my rom (miui) but when i booted into clockwork mod v4.something
i unmounted the SD card in the phone options and formatted it, after re mounting it the phone gave me a notification that the SD card was an unsupported format
so what i did was click that notification and format the card again
i booted into recovery and it worked, i hope this helps someone in the future
edit: my phone is the samsung fascinate using the glitch kernel v11
koszor said:
edit: my phone is the samsung fascinate using the glitch kernel v11
Click to expand...
Click to collapse
So why are you posting in a Forum devoted to the HTC Droid Incredible?
Can't mount /dev/block/mmcblk error
I received a replacement Dinc from Verizon under the extended warranty. My problem is that the new phone won't backup or restore under CWM. I get a notice that "E: Can't mount /dev/block/mmcblkp1p (or mmcblk)
My old phone was rooted with the 2.3.4 version 4.06 GB stock rooted ROM. I made a nandroid backup with CWM recovery 5.0.0.6. So far all is good. The replacement phone with amoled screen came with GB 2.3.4. (unrooted and s-on.) Following the directions in Droid Forums I downgraded to 2.2, rooted using unrevoked3, turned s-off with unrevoked forever and reinstalled 2.3.4 version 4.06. All files found from links of XDA. (THANKS to all for the great instructions and files.)
But now on the new phone the nandroid backup and recovery from CWM won't work as I get the above error. II read that the sd card needs to be reformatted but when I put it back in the old phone, CWM works well without the error. Any suggestions?
fns001 said:
I received a replacement Dinc from Verizon under the extended warranty. My problem is that the new phone won't backup or restore under CWM. I get a notice that "E: Can't mount /dev/block/mmcblkp1p (or mmcblk)
My old phone was rooted with the 2.3.4 version 4.06 GB stock rooted ROM. I made a nandroid backup with CWM recovery 5.0.0.6. So far all is good. The replacement phone with amoled screen came with GB 2.3.4. (unrooted and s-on.) Following the directions in Droid Forums I downgraded to 2.2, rooted using unrevoked3, turned s-off with unrevoked forever and reinstalled 2.3.4 version 4.06. All files found from links of XDA. (THANKS to all for the great instructions and files.)
But now on the new phone the nandroid backup and recovery from CWM won't work as I get the above error. II read that the sd card needs to be reformatted but when I put it back in the old phone, CWM works well without the error. Any suggestions?
Click to expand...
Click to collapse
I would first try to format your sdcard fat32, but dont put any of the old files back on yet. Then with the blank sdcard inserted try to run a backup and see if it works. If not try reflashing cwm thru hboot. Also make sure you have superuser and busybox installed. mmcbkk0p1 is the data partition, see if you can manually mount it thru recovery in the mounts and storage menu.
cmlusco said:
I would first try to format your sdcard fat32, but dont put any of the old files back on yet. Then with the blank sdcard inserted try to run a backup and see if it works. If not try reflashing cwm thru hboot. Also make sure you have superuser and busybox installed. mmcbkk0p1 is the data partition, see if you can manually mount it thru recovery in the mounts and storage menu.
Click to expand...
Click to collapse
Its mmcblk1p1 he said. That isn't the data partition . I think it is sdcard. I think an sdcard format will do the trick.
Sent from my Galaxy Nexus using Tapatalk
very wierd
been getting this error "E:cant mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1" with my g2 I cant flash from my sdcard or boot into os and when i restore a backup that I have using fast boot it just hangs when I try to boot up the system I do have clockwork recovery on the phone and adb access but cant mount the sd card please help thanks
A little punctuation please pal!? That was hard work to just read it.
OK, what are you trying to achieve? Is it just not booting under any condition?
... and you also cant restore a backup through "fastboot" or recovery?
Have you already tried a fresh flash of a ROM or is that a last resort to preserve data/apps?
Boot up into recovery > mounts and storage > Mount sd card > Flash a ROM or restore a backup.
I mean I'm just speculating, I've never had this problem before.
...and yeah wileykat's right, you can't restore from fastboot
omarsalmin said:
...and yeah wileykat's right, you can't restore from fastboot
Click to expand...
Click to collapse
Why couldn't you just use flashboot to flash the boot, system, and userdata partitions with your backup images? I thought flashing these types of partitions was the main purpose of the fastboot protocol to begin with. I hadn't heard that this doesn't work on the G2 (not sure why it wouldn't---is it something specific to the eng. hboot?).
And yeah, more details are probably needed to better understand the issue here.
I got it fixed. I had to bend the prongs on the sd card holder up to provide more contact. Thanks guys.
I am having the same error when I try to do a backup or rom upgrade. The strange part is that I can see the SD card in recovery mode......
nothing freezes on me, but EVERY single time (besides nandroid backup) I get that exact same message.
Does anyone have an actual answer? Like a workaround or something?
Or does it really matter as long as everything flashes
cheers
So i went to flash a ROM and now it says while flashing that the flash was aborted because the system can't mount the SD card. I'm using the newest CWM and have flashed stuff before. Not sure what to do, it wont let me make backups, restore, or flash anything.
jct522 said:
So i went to flash a ROM and now it says while flashing that the flash was aborted because the system can't mount the SD card. I'm using the newest CWM and have flashed stuff before. Not sure what to do, it wont let me make backups, restore, or flash anything.
Click to expand...
Click to collapse
Did you use the Mounts menu to try to manually mount the sd?
Also, Which method did you use to get into CWM?
mattallica76 said:
Did you use the Mounts menu to try to manually mount the sd?
Also, Which method did you use to get into CWM?
Click to expand...
Click to collapse
Ya i went into the menus and manually unmounted and then remounted the SD card but that didn't do anything. I used the typical three finger method to boot into CWM like i always do.
i think
I believe this has something to do with the way in which the SD card is formatted I also cannot mount in to usb storage in CWM i get an E: error
Have you guys tried to "Reboot recovery" from the "Adavnced" menu in CWM, and then try to flash the ROM?
I've had this happen before, it was a formatting problem. The easiest fix I found was to back up SD-card data on your pc, reformat the card from the Android system, then copy your data back over. CWM should be able to mount your card now.
I had a problem with the mount dropping mid flash it was my sd for some reason was chipped I always keep backup files
Sent from my SPH-D700 using XDA App
jct522 said:
So i went to flash a ROM and now it says while flashing that the flash was aborted because the system can't mount the SD card. I'm using the newest CWM and have flashed stuff before. Not sure what to do, it wont let me make backups, restore, or flash anything.
Click to expand...
Click to collapse
Just flash another version of CWM and u'r done. I faced this problem after flashing Siyah Kernel v2.3 which includes CWM 5.0, and I tried all the methods online; formatting, error-checking, etc... nothing succeed!
Finally I flashed another kernel (Which includes CWM 4.0) and it worked fine.
Thanks!
Same thing happened to me just now... found this thread.. pushed new CWM in ODIN - Worked like a charm.. Fixed in 2 minutes..
Flashing another CWM (ACS recovery this time...) via Odin did not fix the issue. Going to try the format /sdcard fix and see... argh!
*Edit* aaaand that didn't work either. WTF... I literally just got this phone 2 hours ago... brand new.
delete the .androidsecure folder on your sd that worked for me formatting wont work if you put your files on the same with me because i always copied that folder along too
I'm using Revolutionary CWM Recovery 4.0.1.4 that came with the revolutionary.io root method...
I formatted and partitioned the sdcard using this recovery
I have 16gb card - 2048mb ext4 - 64mb linux-swap - and the rest fat32
everytime i goto wipe dalvik i get e:unknown volume for path [sd-ext]
everytime i go to nandroid backup it says no sd-ext found
.android_secure folder is present on the sdcard
i know i have sd-ext, why do i see this error?
I had the same problem and I was able to fix it by formatting the SDCARD and then creating new partition. If you do, make sure you backup your data first.
jake200 said:
I had the same problem and I was able to fix it by formatting the SDCARD and then creating new partition. If you do, make sure you backup your data first.
Click to expand...
Click to collapse
i thought that too... so i copied contents of the sdcard to the pc.... formatted and repartitioned the sdcard, and copied contents back...
still getting the error... i know 100% that i have a sd-ext partition...
i'm wondering if its a flaw or bug in the recovery.img im using, which is the revolutionary cwm 4.0.1.4 that came with the revolutionary.io root method
After talking with attn1 on irc #alpharev
he re-wrote the Revolutionary CWM Recovery 4.0.1.4 to support SD-EXT
so for anyone still having this issue, here is the recovery he fixed and gave me
http://www.sendspace.com/file/0zi3nr
Will it work for Sensation XL?
please help
hello,
i have a huawei honor u8860 running official ICS 4.0.3.
i was trying to root it with CMW recovery and by mistake i've installed a CMW recovery for another honor device so i think i bircked it.
when i power on the device it goes to the stock recovery mod with the same message above ( unknown volume path.. etc)
anyway it's stuck at the recovery mod and i can not access my device.
the debugging is off too so i can not connect to the PC too.
can anybody please help, i would really appreciate it
thank you
mohannad911 said:
hello,
i have a huawei honor u8860 running official ICS 4.0.3.
i was trying to root it with CMW recovery and by mistake i've installed a CMW recovery for another honor device so i think i bircked it.
when i power on the device it goes to the stock recovery mod with the same message above ( unknown volume path.. etc)
anyway it's stuck at the recovery mod and i can not access my device.
the debugging is off too so i can not connect to the PC too.
can anybody please help, i would really appreciate it
thank you
Click to expand...
Click to collapse
This is the EVO 4G forum.
e:unknown volume for path [sd-ext]
Error on my HTC ONE X, recently I have restored the nandroid backup O2_001 3.14 Stock JB, because his phone not have ruu stock rom. what should I do? PC SD Card not appear as a storage.
Please help!
Hi, I am a total newbie and I rooted my phone (HTC Desire) and have obviously misread some instruction as I seem to have created and Sd-ext partition on the internal drive instead of the external.
I installed JB4.1.1 which is nice and I like it but whenever I try to use the camera I get a "Gallery closed" error. I'm wondering if these can be linked and if the sd-ext partition shouldn't be there? Perhaps the gallery is trying to save in the wrong place or something? I am clutching at straws to thi problem.
How can I safely remove this partition and reclaim it back if it shouldn't be there?
Sorry for being a complete tube!
Malk
How did u manage to make an ext partition on the internal?
Tell us everything you have done.
Sent from my HTC Desire using xda app-developers app
I think it is on the internal????
I went into recovery and created it?
Options I have are:-
mount /data
mount /sdcard
mount /system
mount /sd-ext
Malk
malkthealk said:
I think it is on the internal????
I went into recovery and created it?
Options I have are:-
mount /data
mount /sdcard
mount /system
mount /sd-ext
Malk
Click to expand...
Click to collapse
I highly doubt you made the partition on your internal. That would be difficult if not impossible.
Im guessing you just incorrectly made the partition.
Are you s-off? If so download the 4ext recovery app from http://4ext.net/. Install the apk and choose Online Install | Upgrade
It will ask if your phone is the HTC Desire GSM. Say yes, unless your phone isnt. (then go to the right forum )
Then you will see a list of all the different versions. Click on the latest one, and then install. It will tell you if it flashed succesfully, and then you can exit the app. To confirm it installed: turn off the phone, then turn it back on using power button + volume down. Then in bootloader select recovery. 4ext should come up instead of cwm.
Once you successfully have 4ext recovery installed look at this guide to see how to properly make the ext partition. Use the 4ext method and start at step [4].
Finally after you have done that, i would recommend doing a full wipe (everything except sd card) and reflashing the rom.
Many thanks, I'll try this. Good to know I couldn't screw anything up
Malk