Hi All,
I have a ZE551ML (4 GB RAM, 16 GB ROM) that belongs to a friend. Yesterday, he was using it when suddenly all apps force closed and the device rebooted after which, there's a bootloop. We tried factory reset and it is able to format /data but throws the error E:failed to mount /cache (Invalid argument). Because of this we cannot flash anything as well (remote cmds error). We tried flashing with SD Card, fastboot, ASUS Flash Tool and from what it seems, the flashing fails because it is unable to mount the cache partition.
Can anyone guide on how to fix this issue?
Is it an eMMC failure?
Related
Hi there !
After flashing the MIUI rom, I noticed that i could'nt format or mount my sdcard in recovery anymore (Clockworkmod 2.5.0.7) it says exactly when I try to format, or do a full wipe :
Code:
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(Invalid Argument)
Error mounting /sdcard/.android_secure
Skipping format...
Even after formatting with gparted on a linux live cd.
I don't know what to do, what doest this error mean ?
Thanks !
Dear All,
I have important photos at the mobile internal SD. However one day the mobile suddenly reboot. After that it is booting to a interface, it said the memory is corruptted required reset default.
1. I tried boot to recovery mode, it said
e: failed to mount /data (Invalid argument)
can't mount /data, cannot write file to /
e: failed to mount /data (Invalid argument)
can't mount /data/log/recovery_log.txt
Any method to repair/copy back the photo??
Please Help
My galaxy S3 Crash and TWRP says it can't mount anything internal. So I thought I would install CWM Rcovery and see what happens. I used Odin and it says it went find, but I noticed that the progress bar on the phone never displayed. When I reboot, TWRP is still there. What's wrong?
Reflash with Odin but don't check auto reboot. After flashing cwm, remove cable, remove battery, replace battery, he button combo to get into recovery.
Same thing. Odin sees the phone, then acts like it is flashing, but I never see anything happen on the phone itself. I thought normally there is a progress bar to show something is uploading, but nothing happens. When I go into recovery mode, I am back in the teamwin screen which takes about 3 minutes to boot. When I go to the TWRP log, I see:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder/
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/data'
E: Unable to mount '/cache'
E: Unable to mount internal storage
E: Unable to mount /data/meda during GUI startup
E: Unable to mount '/cache'
E: Full SELinux support is present.
Running boot script...
Finished runing boot script
E: Unable to mount '/cache'
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount '/data'
Is the phone an i747 or i747m?
Have you tried mounting the data partition in twrp and formatting it using a Windows machine?
Hi,
I tried to flash viperOS using squid twrp for moto G5S, but something in the process i think i did wrong.
My phone model is montana xt1790.
I unlocked the bootloader.
I tried to install the recovery, but had same problem than @dau999
dau999 said:
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
Click to expand...
Click to collapse
I tried to flash "no-verity-opt-encrypt-5.1.zip" file posted as solution here https://forum.xda-developers.com/showpost.php?p=74813124&postcount=23.
After this i have working the recovery, but i believe this is what did wrong:
With debug mode enabled, after a wipe clean (Cache, Data, Dalvik/ART and system) and format data (wipe all your apps, backups, pictures, videos, media and removes encryption on internal storage) got this errors:
Code:
Could not mount /data and unable to find crypto folder.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage.
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (Invalid argument)
After this errors i flashed ViperOS, but after first boot it, first thing viper OS ask me was the phone password, after i enter it, the phone show up a message saying that password is ok but data is corrupt, restarting and trying to fix my phone without success (same errors like failed to mount /data)
Also i tried to use the "repair or change file system" selecting Data partition, twrp show me this: http://oi65.tinypic.com/2prin8y.jpg, also i got this errors:
Code:
/sbin/fsck.f2fs /dev/block/mmcblk0p54 process ended with ERROR: 255
Unable to repair Data
What should i do?, i don't know is related with an encryption on data partition, or if this can be solve.
EDIT:
Found the solution in reddit: www.reddit.com/r/AndroidQuestions/comments/7w5c75/used_the_format_data_option_in_twrp_recovery_on/
Just fixed the issue after making a second format in TWRP ( WIPE > FORMAT DATA)
Hi,
my german N7100 one sad day rebooted just to the Samsung logo and froze.
After some research i found Heimdall and jOdin and managed to flash TWRP 3.3.1-0 as recovery.
Booted into that, looked around and found on tapping the menu icon:
Code:
Failed to mount '/cache' (Invalid argument)
E:primary block device '/dev/block/mmcblk0p16' for mount point /data is not present!
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/efs' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present
E:
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
ADB was and is enabled.
Flashing a stock ROM with jOdin first complained about a missing PIT file, then proceeded getting one from the phone, then did the flashing and reported PASS.
Didn't change a thing, though, the phone still didn't boot further, and TWRP reported the same as before.
adb shell
works and i looked around in the phone; i found
/dev/block/mmcblk0
and
/dev/block/mmcblk0p1,
both readable by less, but no other mmcblk* were there.
The phone has a MicroSD card inserted, which isn't listed in /dev or /dev/block, although TWRP can write the system logs "successfully" to it.
Right now, i can't check the contents without a MicroSD adapter.
I looked around here and found nothing quite similar, therefore this new thread.
Help, please?
--
best regards,
-- recook
maybe emmc dead or what?