hello, ima a newbie and i have a problem with my friends galaxy fit
we tried to instal some new android and we messed up the phone, now it wont start, how can i bring it back to normal..
when i enter the recovery mode it says:
--Appling Muti - CSC --
E:failed to mount / system (invalid argument)
when i go to wipe dada/factory reset this shows
E: format_volume: rfs for at failed on /dev/stl13
formatting /cache...
E: format_volume: rfs for at failed on /dev/stl14
data wipe complete
the phone data is:
GT-S5670 Galaxy Fit
PDA: S5670XWKS4
CSC: S5670OXFKQ4
MODEM: S5670XWKS3
Added: 2011-10-11
I too had the same problem
REFER http://forum.xda-developers.com/showthread.php?p=47343291
Already answered:good:
Thank me and also him who answered
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).
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
Hello xda teams
My name is Dereje even i don't know how and where i started about my phone problems, first I trying to open but it will start again off frequently then I trying to reboot again it will not then I decided to make flash by using ODIN again not even ODIN successfully completed all the threads but when I tried to reboot it says....
E: Error in /cache/recovery/log (I/O error0
# Manual mode v1.0.0#
----Applying multi-csc....
Applying the csc-code :EGY
successfully applied multi-csc.
successfully verify for dmverity hash tree
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/last kernel manual
E: Can't open /cache /recovery/ last kernel manual
E: faild to find /misc partition.
this is it so please help me how to fix this problems.
my phone model is J7 (2016) SM-J710F
Thanks a lot
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