I guys, I have a Galaxy tab 2 GT-5110, it is stuck in the Samsung Icon, it also won't start in Odin (download mode), when a press power + down volume it shows the message "no command" then E: failed to mount /efs (invalid arguments), I don't have the efs back up, and the Samsung Kies doesn't recognise the tablet, pleasessss any tips?, thank you so much
Related
My Samsung Galaxy S Relay 4G took a dump tonight. It crashed and rebooted [normal shut off to black screen and turn back on kinda crash]. Not totally unheard of, it's electronic so things happen. Anyway, I sit there holding it while watching tv waiting for it to come back on and it doesn't! It sits at the screen that says "Samsung GALAXY S RELAY 4G exclusively from T-Mobile". I work with computers everyday so I know this a bad sign. I try a full power cycle by removing the battery and that didn't help. I tried just letting it do it's thing while I ate dinner and that didn't help. So I start Googling and just about the only stuff I can find is how to root the phone. I find things about booting to Safe Mode [didn't work, same result], things about rooting [hangs up at the Downloading... screen] and things about factory reset [not my 1st choice but it's already broke]. So I try to boot into the restore mode and it says:
failed to mount /system (invalid argument)
So I'm kinda lost. Basically the phone won't boot up, it won't boot safe mode and I can't get it to boot to recovery. Any help from the wise android community?
This is an official...not a rooted one.
Either emmc is borked or you have a bad battery....Samsung put this special battery feature in them that when the battery goes bad it acts like a brick...I had this happen once and with me battery it booted right back up....also have you tried Odin back to stock yet?
I just tried swapping to a known good battery [GF has the same phone] and that didn't fix it. I tried the Odin reset and that's how I saw the failed to mount /system error
Full error when loading Odin with Vol Up, Home and Power:
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# Manual Mode #
--Applying Multi-CSC...
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
invader138 said:
Full error when loading Odin with Vol Up, Home and Power:
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# Manual Mode #
--Applying Multi-CSC...
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
Click to expand...
Click to collapse
I fixed it by reflashing to the latest stock ROM with Samsung Kies. I had everything backed up so it was an easy restore of apps after the flash. I hope this helps someone in the future.
Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
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
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/last_install
E: Can't open/cache/recovery/last_install
Data wipe complete.
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_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
djillusion954 said:
Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
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
E: failed to mount /cache (invalid argument)
E: Can't mount/cache/recovery/last_install
E: Can't open/cache/recovery/last_install
Data wipe complete.
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_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
Click to expand...
Click to collapse
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
beekay201 said:
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
Click to expand...
Click to collapse
MRA56K factory image???????????? what is that and where can I find it???
Maybe the op meant to say mra58k?
Hey. So, same problem here (same errors), but a faulty power button caused the reboot in the middle of the update.
Replaced the power button but now can't flash anything since my USB debugging was off (unrooted- from day one just auto-updated).
Can I do something or I'm screwed? we don't have here google services and I bought the device from US (google store website).
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
By a mistake I formatted EFS folder. Now I am unable to flash any firmware.
This error is getting on android recovery.
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verify error...
Please help me....
Are you able to go into download mode or a custom recovery. If you hold down volume down + home + power key - hold it for 5 secs, all at once, you will go to download mode automatically.
Sent from my SM-T377V using Tapatalk
my friend gave his phone G955f,it was only possible to enter download mode,no recovery,nothing..not even boot samsung logo..after 2 days i finally flashed firmware...now i have new problem,flash was done with odin,3 different german firmwares and i always get the same result
buttons are responsive,i can restart phone,get into download mode but it is stuck on boot logo..i have deleted cache and factory in recovery menu and still nothing..
But in down left corner in recovery i get message:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
Does anyone know why is that and how to fix it?
empty