verifying internal MMC block
not need checksum confirmation already executed
E: failed to mount /data (invalid argument)
E: can't mount /data/fota/ipth-muc.prop
E: failed to mount /efs (invalid argument)
E: failed to mount /system (invalid argument)
# MANUAL MODE #
E: failed to mount /data (invalid argument)
E: failed to mount /system (invalid argument)
john-ammu said:
verifying internal MMC block
not need checksum confirmation already executed
E: failed to mount /data (invalid argument)
E: can't mount /data/fota/ipth-muc.prop
E: failed to mount /efs (invalid argument)
E: failed to mount /system (invalid argument)
# MANUAL MODE #
E: failed to mount /data (invalid argument)
E: failed to mount /system (invalid argument)
Click to expand...
Click to collapse
Hello,
What device do you have?
___
v7
XDA Assist
v7 said:
Hello,
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HI,
i have 2 devices they have little bit similar issues
SHV-E120L
and SCH-i535
So...I'm a little bit of a newbie when it comes to fixing technology, so I hope to be as clear as possible. All of a sudden my Samsung Galaxy s4 died few hours ago. It would just boot and get stuck at the "Samsung Galaxy s4 GT-I9505" screen (If I plug it to charge it remains stuck at the screen where the battery is grey and it has a white circle in it). Before that it normally booted up for like 20-30 seconds. Then it rebooted that way. Now, I can get to recovery mode, and what I get is the following text when entering:
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (invalid argument)
can't mount '/system' (invalid argument)
E:failed to mount /cache (invalid argument)
can't mount '/cache' (invalid argument)
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_recovery
E:failed to mount /data (invalid argument)
E:can't mount /data/log/recovery_log.txt
E:failed to mount /system (invalid argument)
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:failed to mount cache (invalid argument)
E:Can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (invalid argument)
I didn't perform any root or flashing since I barely know what they are, I tried an emergency recovery and initialization with Kies by booting the phone into download mode but it says that my phone doesn't support it, which is weird. How big of a problem is this? I brought the phone to a local technician which said I should contact Samsung assistance because "the internal memory is gone" (as for damaged, I assume) but I don't think it can be right since again, I booted it up in the morning and for 30 seconds it was perfectly fine, I am thinking more of a corruption, somehow, of the files. Is there any way I can get out of this state? Can I recover any data from it? I underestimated the situation and I've never done a backup of the phone sadly... If it can help, when this happened I was on firmware 4.4.2. Thanks in advantage for any reply.
dariomrk said:
Do you have your warranty? I suppose that the hardware is damaged. In that case you will probably need a motherboard replacement.
Click to expand...
Click to collapse
Phone was bought in November 2013 so I suppose it's not eligible for warranty replacement
CrashRatchet008 said:
So...I'm a little bit of a newbie when it comes to fixing technology, so I hope to be as clear as possible. All of a sudden my Samsung Galaxy s4 died few hours ago. It would just boot and get stuck at the "Samsung Galaxy s4 GT-I9505" screen (If I plug it to charge it remains stuck at the screen where the battery is grey and it has a white circle in it). Before that it normally booted up for like 20-30 seconds. Then it rebooted that way. Now, I can get to recovery mode, and what I get is the following text when entering:
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (invalid argument)
can't mount '/system' (invalid argument)
E:failed to mount /cache (invalid argument)
can't mount '/cache' (invalid argument)
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_recovery
E:failed to mount /data (invalid argument)
E:can't mount /data/log/recovery_log.txt
E:failed to mount /system (invalid argument)
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:failed to mount cache (invalid argument)
E:Can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (invalid argument)
I didn't perform any root or flashing since I barely know what they are, I tried an emergency recovery and initialization with Kies by booting the phone into download mode but it says that my phone doesn't support it, which is weird. How big of a problem is this? I brought the phone to a local technician which said I should contact Samsung assistance because "the internal memory is gone" (as for damaged, I assume) but I don't think it can be right since again, I booted it up in the morning and for 30 seconds it was perfectly fine, I am thinking more of a corruption, somehow, of the files. Is there any way I can get out of this state? Can I recover any data from it? I underestimated the situation and I've never done a backup of the phone sadly... If it can help, when this happened I was on firmware 4.4.2. Thanks in advantage for any reply.
Click to expand...
Click to collapse
Greetings and welcome to assist. It sounds like your partition table is corrupt, can you get into download mode ? If you can try kies/smartswitch emergency firmware recovery
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. It sounds like your partition table is corrupt, can you get into download mode ? If you can try kies/smartswitch emergency firmware recovery
Good Luck
Sawdoctor
Click to expand...
Click to collapse
As I mentioned in the OP, I already tried the emergency firmware recovery, but both Kies, Kies 3 and SmartSwitch claim that the phone is not eligible for the emergency recovery. Of course, I tried performing these operations by entering in download mode and then connecting the phone to the pc to perform the operation but no luck so far. Other options? Do I need to flash a new firmware?
CrashRatchet008 said:
As I mentioned in the OP, I already tried the emergency firmware recovery, but both Kies, Kies 3 and SmartSwitch claim that the phone is not eligible for the emergency recovery. Of course, I tried performing these operations by entering in download mode and then connecting the phone to the pc to perform the operation but no luck so far. Other options? Do I need to flash a new firmware?
Click to expand...
Click to collapse
Try this thread, if the firmware doesn't work you could try mskips toolkit, that has an emergency firmware recovery. As a last resort you could flash a pitfile
https://forum.xda-developers.com/showthread.php?t=2751515
Good luck
Sawdoctor
I have rooted my phone, and I have installed custom ROMs, but afterwards, it took AGES to boot, so I decided to boot into recovery mode, and it said the following in the log:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid Argument)
E:failed to mount /system (Invalid Argument)
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any help? It's a Samsung Galaxy Ace GT-s5839i
Help would be much appreciated.
Just this morning as i put on my phone ,it went on upgrading but couldn't finished and cant resurrect any longer it seems like a joke as i did every thing but no avail i quite for that day...Have to use my SD card to wake it and now this what i "ve got.... Although is not a rooted device, flashed firmware KIES also with CWM/TWRP but this report still exist please someone give me a hand.
E: Failed to mount /cache (Invalid argument)
Can't mount '/cache '(Invalid argument)
E: Can't mount /cache/recovery/Last_recovery
E: Failed to mount /data (Invalid argument)
E: Can't /data/log/recovery_log . txt
E: Can't mount /cache/recovery/last_locale
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed to mount /cache (Invalid argument)
I can use every rom just fine. However, I need to flash stock rom but when I boot to stock rom it says "No Command". After a minute or so, the screen changes to installing system update, which flashes to black every second.
Stock firmware that I flashed is "J710MNUBS4CSF1_J710MNICE4CSD4_J710MNUBS4CSG2_HOME.tar.md5"
When I press Power + Vol up in the "No command" screen, this is what the text reads:
apping: device or resource busy
E:[libfs_mgr]Couldnt create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE: [libfs_mgr] Error creating device mapping: device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E: [libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rwE:failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: can't open /cache/recovery/log: (invalid argument)
E: failed to mount /cache/ (invalid argument)
E: can't mount /cache/recovery/last_log
E: can't mount /cache/recovery/last_log: invalid argument
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/last_install
E: can't open /cache/recovery/last_install:invalid argument