ok this is anoying know
keep getting this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
i flashed coolexe sense 3.0 before that i made a back up of rcmix 2.0
had a play with coolexe sense 3.0 went into ra recovery and went to wipe everythink before restoring my backup
and got this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
ive tryed looking for a answer but not getting any where
any one with some knowlegde i not sure but i think its a fastboot command but i cant find it any where
daddyspud said:
ok this is anoying know
keep getting this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
i flashed coolexe sense 3.0 before that i made a back up of rcmix 2.0
had a play with coolexe sense 3.0 went into ra recovery and went to wipe everythink before restoring my backup
and got this error
E: cant mount /dev/block/mmcblk0p1 ( or /dev/block/mmcblk0) (no such file or directory) E:cant mount /sdcard
ive tryed looking for a answer but not getting any where
any one with some knowlegde i not sure but i think its a fastboot command but i cant find it any where
Click to expand...
Click to collapse
maybe this thread could help you, click here, as i think that is what's happened.
nope i seen that but that not wat im looking for ziggy a buddy mentioned somethink about a command threw fastboot but he not online and was hoping some one else of might known it
Is there a video that says "I'm a noob @ XDA"?!
hope you fix it soon.
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
jordan.harris01 said:
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
Click to expand...
Click to collapse
thanks sorted ur a star all done thank **** lol
jordan.harris01 said:
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
Click to expand...
Click to collapse
I would like to thank you so much my friend for these commands. I just fixed my desire also.
jordan.harris01 said:
The commands you're looking for are:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should fix the USB brick. If it doesn't, PM me.
Click to expand...
Click to collapse
gonna tattoo this commands in my fore-arm
lifesaver!
seriously thought i bricked my desire
I've got the same problem on motorola dext..what commands to use there ?
Try to enable bluetooth
Sent from my HTC Desire using XDA App
already tryed all this small tricks i need something serious to solve my problem.
Related
http://psfreedom.com/wiki/index.php?title=OpenDesire4.0.4
http://www.ps3hax.net/showthread.php?p=123003
Im trying to install this recovery so i can jailbreak my PS3, but when i try to use unrEVOked, it hangs while pushing the recovery
When i try to use adb on both my phone and my computer it says i have no space!
what should i do?
EDIT:
fastboot erase recovery
fastboot flash recovery recovery.img
sounds like it would work, bu t i dont want to risk that lol
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
SwordOfWar said:
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
Click to expand...
Click to collapse
Alright, thats good to know. Ill look around
http://forum.xda-developers.com/showthread.php?t=770663
"You can only write to system on the desire via adb from recovery."
So i do what? boot into recovery, plug in my phone and adb it again?
flash_image recovery image.img?
Hmm, guess not.
I booted into recovery. Plugged my phone in and did an adb devices. It said one device called recovery
i did mount /sdcard (apparently i dont have to mount it to a location)
i cd'd into thte sdcard and did a flash_image recovery psfMod.img and it said i had no space
I was also looking at this
http://forum.xda-developers.com/showthread.php?t=770663
but i still cant get it to work.
do i have to have s-off?
Well.. I tried flashing the NEW CWM Recovery.. v3.0 and obviously... to flash the new one, i had to remove the old one. I removed the old one, flashed the new one via Terminal Emulator but here is the problem, i CANT DO ANYTHING WITH THE NEW RECOVERY! It wont let me wipe, install roms, or anything... i can navigate through the menu, but it will just give me a bunch of errors!
E:unknown volume for path [/cache/recovery/log]
E:cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
E:no misc partition
E:unknown volume for path [/cache/recovery/command]
Thats what i get if i try to do anything.... :,( whenever i select an option from the recovery menu... i get that same log of errorss.. can anyone tell me how to fix it..??
mymomma8 said:
Well.. I tried flashing the NEW CWM Recovery.. v3.0 and obviously... to flash the new one, i had to remove the old one. I removed the old one, flashed the new one via Terminal Emulator but here is the problem, i CANT DO ANYTHING WITH THE NEW RECOVERY! It wont let me wipe, install roms, or anything... i can navigate through the menu, but it will just give me a bunch of errors!
E:unknown volume for path [/cache/recovery/log]
E:cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
E:no misc partition
E:unknown volume for path [/cache/recovery/command]
Thats what i get if i try to do anything.... :,( whenever i select an option from the recovery menu... i get that same log of errorss.. can anyone tell me how to fix it..??
Click to expand...
Click to collapse
I believe that recovery was made only for gingerbread ROM's.. I'm so sure ha, I use a G2 now ha.. have you tried installing ROM manager and flashing the old recovery via it's menu? just stick with that recovery.
edit: by the way.. I have no idea how you can fix ur problem besides maybe trying to reflash it via terminal emu again and type the following with the recovery image file on the root of ur sd card
"su
flash_image recovery /sdcard/"name of recovery".img"
cheers, hope one of the things i suggested works.
mymomma8 said:
Well.. I tried flashing the NEW CWM Recovery.. v3.0 and obviously... to flash the new one, i had to remove the old one. I removed the old one, flashed the new one via Terminal Emulator but here is the problem, i CANT DO ANYTHING WITH THE NEW RECOVERY! It wont let me wipe, install roms, or anything... i can navigate through the menu, but it will just give me a bunch of errors!
E:unknown volume for path [/cache/recovery/log]
E:cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
E:no misc partition
E:unknown volume for path [/cache/recovery/command]
Thats what i get if i try to do anything.... :,( whenever i select an option from the recovery menu... i get that same log of errorss.. can anyone tell me how to fix it..??
Click to expand...
Click to collapse
well, im guessing u have fastboot working so either reflash recovery or run this command
fastboot wipe cache
it should fix that problem, also i would recommend going back to clockwork 2, if u dont have the file to flash it back (not the update.zip, the actual image) and need the link to the .img file pm me
Omg! Thank you! I rebooted into fastboot and ran the following commands
Fastboot erase recovery
Fastboot flash recovery /path/recoveryCWM2.img
And flashed it... =D everything works now =D
I think its a bug because CWM 3.0 is only a test .img I flash 3 times.. and got the same errorss.. I'm just going to stick with 2.5 until a stable 3.0 comes out.. thank both of you very muxh =D
mymomma8 said:
Omg! Thank you! I rebooted into fastboot and ran the following commands
Fastboot erase recovery
Fastboot flash recovery /path/recoveryCWM2.img
And flashed it... =D everything works now =D
I think its a bug because CWM 3.0 is only a test .img I flash 3 times.. and got the same errorss.. I'm just going to stick with 2.5 until a stable 3.0 comes out.. thank both of you very muxh =D
Click to expand...
Click to collapse
I'm glad I could help
Im sorry for shouting guys but i really need help with this.
I just got my G2 a Few Days ago and i Rooted it and i was running Cyanogen 7 (nightly). I was using it normally and then it just started to freeze.. so i yanked out the battery and it would just stay frozen in the HTC screen. i can still access the recovery through Fastboot but when i go into recovery it tells me
E:Can't Open /cache/recovery/log
E:Can't Open /cache/recovery/log
E:Can't Open /cache/recovery/last_log
E:Can't Open /cache/recovery/last_log
I'm Pretty sure this has something to do with it.
If anyone can help me PLEASE do! I'm Willing to pay
Did you make a nandroid backup before flashing cyanogenmod 7?
My G2 running GingerVillin 1.5
Mine has said that too, dont mind it unless it actually throws an error while your doing something. And try reflashing cm7, make sure you have cwm 3.x
murdah204 said:
Im sorry for shouting guys but i really need help with this.
I just got my G2 a Few Days ago and i Rooted it and i was running Cyanogen 7 (nightly). I was using it normally and then it just started to freeze.. so i yanked out the battery and it would just stay frozen in the HTC screen. i can still access the recovery through Fastboot but when i go into recovery it tells me
E:Can't Open /cache/recovery/log
E:Can't Open /cache/recovery/log
E:Can't Open /cache/recovery/last_log
E:Can't Open /cache/recovery/last_log
I'm Pretty sure this has something to do with it.
If anyone can help me PLEASE do! I'm Willing to pay
Click to expand...
Click to collapse
I think that you have a problem with your sd card. See if it is seated correctly.
Utorrent76 said:
Did you make a nandroid backup before flashing cyanogenmod 7?
My G2 running GingerVillin 1.5
Click to expand...
Click to collapse
Yes i did but its a CM 6.1.1 Backup
EdKeys said:
I think that you have a problem with your sd card. See if it is seated correctly.
Click to expand...
Click to collapse
I've already checked it multiple times and nothing
Powers88 said:
Mine has said that too, dont mind it unless it actually throws an error while your doing something. And try reflashing cm7, make sure you have cwm 3.x
Click to expand...
Click to collapse
It has thrown errors at me
its wont mount the System,boot,or cache
did you try reflashing recovery???
fastboot flash recovery recovery.img
flash a 2.x clockwork recovery and flash a froyo rom....
I just stared this thread http://forum.xda-developers.com/showthread.php?t=1023657 before finding this one. My problem sounds identical. Same symptoms - the freeze, the lack of booting, the errors - all the same.
Did you make any progress?
One last desperate bump
can't you access the phone's shell by using ADB?
SnowOokami said:
can't you access the phone's shell by using ADB?
Click to expand...
Click to collapse
I'm having the same issue as bonstio and murdah.
I don't think you can access adb shell because you can't accept superuser requests without access to the ROM.
I'm having the same symptons here. And when I try to flash another rom it aborts it. I recently redownload ROM manager, I don't know if that's the cause or not
Same problem mt4g here. Recovery doesn't work, it gives a fail error. I've tried fastboot commands they work, but don't fix the problem. adb commands do not work.
Well... whenever I got stuck in a bootloop (stuck at HTC screen) when I messed something up in the system, I could still use adb to enter the phone's shell. Pull out the battery, put it back in, hook the phone to the computer and power it on, adb should (not sure it will..) recognize it. If you can't modify the system, remount it.
Maybe another solution is to flash PC10IMG.zip again using fastboot?
SnowOokami said:
Well... whenever I got stuck in a bootloop (stuck at HTC screen) when I messed something up in the system, I could still use adb to enter the phone's shell. Pull out the battery, put it back in, hook the phone to the computer and power it on, adb should (not sure it will..) recognize it. If you can't modify the system, remount it.
Maybe another solution is to flash PC10IMG.zip again using fastboot?
Click to expand...
Click to collapse
I think he should be able to use the PC10IMG way if he used the gfree method I believe.( could be wrong) and if you used unforgivens method you would have to hex edit something to be able to return to stock or you will get a simi brick.
Sent from my Vision using XDA Premium App
Hi Last weekend i had the same issues used a tool i used a lot with my desire and it worked to get recovery installed on the desire z you need to be S-Off to use it so check this first it saved my new desire Z !!!!!
http://forum.xda-developers.com/showthread.php?t=794638
ClockworkMod still works (3.0.0.5) and I can still adb to the phone. Confirmed S-OFF. HBOOT -0.85.0005
Even though CMW is still OK I tried to reflash since it is moaning about recovery From adb shell:
/sdcard # flash_image recovery recovery-clockwork-3.0.0.5-passion.img
flash_image recovery recovery-clockwork-3.0.0.5-passion.img
Can't read device: "/dev/block/mmcblk0"
Error in reading mbr!
failed with error: -1
I'd be happy to try the PC10IMG.zip approach if you can be more specific.
Contents of /proc/mounts in case it helps:
/sdcard # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p27 /cache ext3 rw,nodev,noatime,nodiratime,errors=continue,da
ta=writeback 0 0
/dev/block/mmcblk1p1 /sdcard vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=
0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
It gets more sinister.
Following this thread http://forum.cyanogenmod.com/topic/15623-how-to-fix-a-semi-bricked-g2/ I tried to reflash PC10IMG.zip.
Blah blah continue with update? YES.
Then I see:
Parsing... [SD ZIP]
[1] BOOTLADER - Fail-PU
...
Partition update fail!
Update fail!
//cries
That's.... ouch at least you can still access the phone from the outside, not sure how to fix that issue though, you can't simply enter rm -r *
Check the development forums? maybe there's a solution there or someone who could help you.
Yay I fixed it. I returned to stock firmware using PC10IMG and reflashed recovery
Hello, this is my first post but been seeing lot of threads here with lot of help, so I thank you all before you start helping me.
I have my HTC One X, tried to update to Jelly Bean using Dragon's ROM, all went fine but the phone got stuck on HTC logo.
Since that I can only start on recovery (ClockWork Mod 5.8.4.0), HBOOT (0.94) or fastboot.
There is no way I can access the SDCard from recovery to flash the rom.
I tried factory reset with no luck, wipe cache, wipe data.../factory reset. all with no luck! Every time I try to format my sdcard it says:
"Formatting /sdcard/.android_secure..."
"Error mounting /sdcard/.android_secure!"
"Skipping format..."
If I try with "mounts and storage" then "format sdcard":
"Formatting sdcard..."
"Error mounting /sdcard!"
I must say that I can use "Mount USB storage", did format with FAT32 on Windows & Mac, no luck. Also tried using parted with adb shell, formatting on ext2, but no luck.
Here is my "recovery.fstab":
~ # cat /etc/recovery.fstab
# mount point fstype device [device2]
# /recovery emmc recovery
# /boot emmc boot
# /system ext4 system
# /cache ext4 cache
# /misc emmc misc
# /sdcard vfat /dev/block/sda1 /dev/block/sda
# /internal_sdcard vfat /dev/block/mmcblk0p14
# /data ext4 userdata
# /devlog ext4 devlog
/recovery emmc /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p4
/cache ext4 /dev/block/mmcblk0p13
/data ext4 /dev/block/mmcblk0p15
/sdcard vfat /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/misc emmc /dev/block/mmcblk0p17
------------
And here my fstab:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p15 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p14 /sdcard vfat rw
---------------
There is no way that ClockWork Mod can read my internal card for installing any zip. Any help would be really appreciated, even I would pay if necessary.
Thanks in advance for all the great work you guys do, and hope to get my phone back working!
If you mean the skydragon rom, ypu have to update hboot to use it.
And for the mounting problems... Try reflashing recovery.
I saw "fastboot oem format" somewhere and I aint sure what it does, but it might be worth a try.
Sent from my HTC One X using xda app-developers app
TToivanen said:
If you mean the skydragon rom, ypu have to update hboot to use it.
And for the mounting problems... Try reflashing recovery.
I saw "fastboot oem format" somewhere and I aint sure what it does, but it might be worth a try.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hello, thanks for the fast answer.
I tried the oem format and this is the result:
prosacalatform-tools prosaca$ ./fastboot oem format
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.017s]
finished. total time: 0.017s
I just want to get my phone working, does not matter what ROM or whatever, just want it working hehe.
I tried also reflashing recovery with no luck.
I don't know what left to do...
poloivan said:
Hello, thanks for the fast answer.
I tried the oem format and this is the result:
prosacalatform-tools prosaca$ ./fastboot oem format
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.017s]
finished. total time: 0.017s
I just want to get my phone working, does not matter what ROM or whatever, just want it working hehe.
I tried also reflashing recovery with no luck.
I don't know what left to do...
Click to expand...
Click to collapse
Someone could please tell me how do I restore my phone as it came?
I have downloaded a RUU, my version main is: version-main: 1.28.161.9
When I click the RUU it does nothing, someone please help?
Thanks.
You have to relock bootloader first: fastboot oem lock.
Then run RUU with admin rights.
Sent from my HTC One X using xda app-developers app
TToivanen said:
You have to relock bootloader first: fastboot oem lock.
Then run RUU with admin rights.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thank you all.
I have fixed my phone running the correct RUU.
Right now I am using Android Revolution HD 9.8. How can I update my HBOOT to run Android Revolution HD 18.0?
Best regards.
Two choices: Use a JB RUU or flash the correct firmware for your cid.
I have a family member's phone (N7100) that was stuck on a bootloop. This phone was never rooted or had any custom recoveries or roms installed on it. When I go into recovery I see that I'm getting the common "e:failed to mount /efs(invalid argument)". When trying to google the problem I found that common fix for it:
Code:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
So I go ahead and do this but I notice that even though the phone is out of a bootloop and goes into factory mode (I already know how to get out of it), it doesn't connect to the phone network. Going back to recovery I see that EFI is still not able to be mounted but the error is different "failed to mount /efs Operation not supported on transport endpoint".
I can tell that if I ADB into the phone and do "mount -w -t ext4 /dev/block/mmcblk0p3 /efs" it will mount just fine. Anybody knows what is happening? To make everything worse he doesn't have a EFI backup so at this point I'm thinking the phone is dead no matter what. Suggestions?
Thanks
Try flashing stock ROM.
Skull97 said:
Try flashing stock ROM.
Click to expand...
Click to collapse
I already did and it didn't help. Googling the problem doesn't seem to give me any results for that particular error line.
Bump! I hate to do this but I think this is my last chance to fix it. Google is not giving me any good leads for me to latch on.