• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root "E:Can't mount /dev/block/mmcblk0p1..."

Sak01

Sak01

Android Expert
I was stuck in a boot loop for some reason so I did a few nandroid restores, wipes, reflashing the rom etc. and now I get this message in Amon-ra if I try to do anything:

Code: 
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard

I'm about to try to reformat the sd card in GParted assuming the card is corrupted. Is this the correct thing to do?

I don't have a card reader so hopefully it will let me mount the phone to PC.

edit: actually I do have a card reader but I'll try mounting the phone first.
 
either the sdcard has become corrupted or its a usb brick

try the fastboot command to enable sdcard access first (on the usb brick thread in tricks and tips)
if that doesnt work then its likely to be an sdcard corruption
 
if you are s-off then do fastboot flash misc mtd0.img (if you have one)
no idea what caused your usb brick
 
Everything is working now. Do I still need to do that?

edit: I don't have a custom mtd if that's what you mean.
 
Mtd is what each partition is called. Mtd0 is the misc partition. That image replaces that partitions contents with working contents
 
well you may note have too. if you find connecting the device to mass storage while booting still doesnt work then you will have to flash the mtd0.img
 
I can mount mass storage from recovery but in hboot Windows makes that error noise when I plug in the usb cable. Also the adb shell command gives 'error: device not found'. Nothing is listed under adb devices either.

I've flashed the mtd0 image but still get the error noise and nothing under adb devices. Everything else seems to be working fine but I'm thinking it's best to fix this now?
 
Sak01 said:
I can mount mass storage from recovery but in hboot Windows makes that error noise when I plug in the usb cable. Also the adb shell command gives 'error: device not found'. Nothing is listed under adb devices either.

I've flashed the mtd0 image but still get the error noise and nothing under adb devices. Everything else seems to be working fine but I'm thinking it's best to fix this now?
Click to expand...

hboot has nothing to do with adb thats just the bootloader drivers
if you can mount mass storage in android then all is fine
 
I just had this problem and panicked! I rebooted back into recovery and it worked fine.

Just wanted to share my experience.
 
hi all, im a newb and my galaxy tab is stuck on the boot....it gets to SAMSUNG and sticks....i tried the master reset and i get this message...
[E:can't mount/dev/block/mmcblkop1
(no such file or directory)
[E:can't mount cache:log/recovery.
can anybody help me with this?
 
You will need to speak to guys who have your own device, I.e in the galaxy tab device forum. You will need to give them more detail, like if you're rooted or not.
 
You must log in or register to reply here.
Back
Top Bottom