E:mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory)

[mike808]

Hi guys, just got a brand new s82b in the mail today. Could not update firmware by sdcard, keep getting this error: E:mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory). I finally used usb burning tool to update hoping it would also fix this problem, however, this problem is still there, as I tried to install the trwp recovery but still keeps giving me this error: E:mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory). Otherwise box works good, there is no other problems. Other than it doesn't forget the wifi point, it forgets but than after a reboot it connects again without need the password again. The sdcard works fine when the box is up and running, i installed my backups using titanium on the sdcard and it all worked good.

I've done some searches and see others have also experienced this problem, however, I haven't seen any fixes for this except suggestions to format your sdcard etc., which I've already done and no luck. Please help, thanks.

[ant]

Hi guys, just got a brand new s82b in the mail today. Could not update firmware by sdcard, keep getting this error: E:mount /dev/block/mmcblk0p1 on /sdcard failed

Hi mike, did you try mounting the sdcard in Android mode then using a reboot app boot to recovery and see if you still have the issue.

[no_spam_for_me]

You can also use a USB device...

Sometimes it helps to remove and replace the SD cart at recovery (sometimes more often then once)...

SD cart
1. FAT32 ?
2. removed secure at PC ?
maybe try to reformat the SD to see if it fixes the problem...

[mike808]

Yes, I've already tried all this, used 3 different sd cards with fresh format fat32, also, mounted fine in android but doesn't mount in recovery. Also, tried to boot into recovery first and then insert sdcard and vise versa. And yes, like my first post, i do remove them safely from the computer. I've done this many times before but for some reason getting this problem with this particular unit.

Sd card otherwise mounts and reads writes fine in android, no problem. I restored many of my apps that were stored on sdcard (different one) using titanium backup.

Only getting this issue in recovery.

[mike808]

Well, didn't do anything differently, just for the heck of it tried once more and lo and behold, the thing is working as it should.

[ant]

Well, didn't do anything differently, just for the heck of it tried once more and lo and behold, the thing is working as it should.

That's a result then! I've just spent the last half hour googling
"E:mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory)" from what I've read the problem could lie in the internal sdcard not external sdcard. The only fix for the problem I could find was to use g-parted to format partion (p1).

Anyhow if there is now no problem there is nothing to fix.

[mts]

That's a result then! I've just spent the last half hour googling
"E:mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory)" from what I've read the problem could lie in the internal sdcard not external sdcard. The only fix for the problem I could find was to use g-parted to format partion (p1).

Anyhow if there is now no problem there is nothing to fix.

I'm having the same issue and can't get it solved. Do you used g-parted on the android device?

[dlangejc]

E:mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory)

Ensure that your SD card is partitioned as primary 😉


Sent from my iPad using Tapatalk

[Boten]

Indeed, solved this by formating the partition as primary with partition mini tools.

It just works !