I have a GSIII for 2 years now. Everything was working great but 3 months ago it started rebooting and boot looping. Long story short I tried everything I could do to solve the issue (custom ROMs, Dalvic cache clean, system cache clean, new battery, new charger). I even sent it to Samsun g official service but after a few weeks the problem reappeared and after some time the phone was practically unusable. So, in my despiration, I tried some things with Odin that messed up things even more.
Anyways, now, everytime I turn on the phone boot loops and when I enter the Recovery Mode the following message appears:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : CYO
Successfully applied multi-CSC
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
E: Can't mount /data/log/recovery_log.txt
Recovery Mode and Download Mode both work.
SO is there any way that I can save my phone and bring it back to life?!
PLEASE HELP IF YOU CAN
The best shot you have is to flash a stock firmware from sammobile.com be sure to use the latest version of Odin.
Sent from my GT-I9300 using Tapatalk
Your emmc chip is corrupt, probably nand is damaged.
Related
Two days ago I changed my ROM and after it loaded it got stuck at the Samsung logo. I've tried flashing other ROMs and reverting to stock. I have a Sprint Samnsung S6 Edge + (SM-G928P). My phone is either in download mode, or I can flash it into recovery, or on the Samsung logo, of course it tells me nothing at all except when I go back to stock and into the recovery mode there, that's when I see the E: failed to mount / efs (invalid argument) . what can I do? I'm sure the answer is out there so can someone please help me out... In the mean time I will keep looking for the right answer.
Thanks in advance!!
frankmcquade said:
Two days ago I changed my ROM and after it loaded it got stuck at the Samsung logo. I've tried flashing other ROMs and reverting to stock. I have a Sprint Samnsung S6 Edge + (SM-G928P). My phone is either in download mode, or I can flash it into recovery, or on the Samsung logo, of course it tells me nothing at all except when I go back to stock and into the recovery mode there, that's when I see the E: failed to mount / efs (invalid argument) . what can I do? I'm sure the answer is out there so can someone please help me out... In the mean time I will keep looking for the right answer.
Thanks in advance!!
Click to expand...
Click to collapse
what was the answer??!
Samsung Galaxy S2 SGH-i777 in infinite boot loop.
When I turn on the phone it proceeds past the Samsung logo screen and after a while ends up at the AT&T Rethink Possible screen where it proceeds to reload that screen over and over again in what appears to be an infinite loop.
When I hold down Vol Up & Vol Down and Power, the phone displays the Samsung logo, appears to power cycle and display the Samsung logo again and appears to enter recovery mode. When the phone enters recovery mode, it displays a number of error/status messages as follows:
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/command
-- Copying media files...
E:failed to mount /cache (Unknown error: 0)
E:copy_cache_media:Can't mount /cache
your storage not prepared yet, please use UI menu for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Updating application...
E:failed to mount /data (Unknown error: 0)
E:install_application_for_customer:Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Unknow error: 0)
E:Can't mount /cache/reocvery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Unknown error: 0)
The above messages don't display at once but seem to display after a few presses of the Vol Up button.
After the error messages have all displayed, I see the following at the top of the screen:
Android system recovery <3e>
Enter: Power Key. Select : Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache parition
BUT even though I can use the Vol buttons to navigate the choices, pressing the power button has no affect to select them.
At the moment, I would just like to get back to a working phone. I have attempted to use Odin to flash the UCKH7 stock rom that I found in this post: http://forum.xda-developers.com/showthread.php?t=1286432. It indicates that it does so successfully but it doesn't change my phone situation.
Because I saw the errors about the various partitions I also though maybe I should try re-partitioning with a PIT file. This was probably not a good idea but I was not aware at the time that it may have been a bad decision.
What should I try to fix this situation and get my phone working again?
Thanks!
I'm assuming you are able to boot the phone into download mode, since you flashed Entropy's UCKH7. I suspect that you have memory corruption, and not memory damage. That old UCKH7 from that thread contains only the system and kernel, and not the other files you need to do a full install, so I'm not surprised it didn't boot.
If you flashed the UCKH7 pit file, it probably didn't do any damage, but it would not clear the corruption by itself.
The first thing I would try is to flash a full stock distribution in Odin, without pit, and see if that clears the problem. You can find the files you need in the Download Repository. See the link in my signature. I would suggest flashing the latest stock firmware full distribution, which is I777UCMD8 (Android 4.1.2 Jelly Bean). It's the next to last item at the bottom of the page. The original UCKH7 Full stock distribution is there also under the heading I777UCKH7-CL503881 Stock Binaries.
If the above does not resolve the issue, all is not lost. Post your results back here and I wil post how to clear the corruption. Good luck.
FIXED!
Yes. You assumed correctly. I suspected (or maybe it was hoped) that it was just memory corruption and not damaged but couldn't find what to do.
After following your advice of downloading the latest stock firmware full distribution and using Odin to flash it.
After flashing and booting, I kept getting stuck at the AT&T logo screen. I booted back into recovery mode and saw that it was still unable to mount the /data partition and it didn't seem to let me wipe the /data partition. I then went through a series of reboots and even re-flashed again. Finally, I entered recovery and got distracted. When I came back to the phone, I discovered I was able to get the power button to select the Wipe Data Partition. I wiped data and cache and then I re-flashed one more time.
After this my phone finally booted all the way.
Thank you so much for your help. It is really appreciated.
hi .
I have a Samsung galaxy note 4 . I hold volume up and power button to enter recovery mode and when I click on reboot system now , after few seconds the red error message "e:failed to mount /data (invalid argument) " appears below but the phone reboots successfully and it works fine again . I did a full factory reset and i get this message again . I want to know why i get this message ? does it have any effect on system performance ? because it was slower than other note 4s from the beginning but not noticeable but after a couple of months of using the phone it sometimes gets so slow and lagging sometimes .
here is attached the screenshot of the error i get second before the phone reboots :
Hi, I wonder if you can help.
I have a Samsung Galaxy S3 GT-i9300 White 16GB, purchased in the UK for T-Mobile.
Some time ago I unlocked it to accommodate a Virgin Sim.
It has never been rooted, always running Stock Rom.
Just recently, on powering up, it reached the "Samsung Galaxy S III GT-I9300" splash screen and got no further.
Initially, I couldn't get to Recovery Mode, but could access Download Mode, so I flashed Stock Recovery. From here I attempted to "wipe data/factory reset", and received a barrage of errors, some of which are below:
Error mounting /data
E: format _volume: make_extf4fs failed on /dev/block/mmcblk0p8
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
I have read and executed a string of methods from other threads on this forum, and some Youtube videos, in an attempt to get it working again. This included using ADB, on some of the mmcblk0p directories, but have failed to get the phone back in working order, stock would be ideal.
Currently I have ClockworkMod Recovery v6.0.4.7 installed, but can change that again if need be.
I'm not precious about any of the data on the phone. I have a Mac and Jodin, and do have access to a PC and Odin, but only at work. Any help and guidance would be greatly appreciated. Should you require further info from me please do ask.
Thanks... Calhoon
Flash a stock rom via odin before you knacker it completely.
The problem is the recovery partition as that loads everything to start the os and it is complaining that it can't find cache. That means one of 2 things. Either the recovery partition is borked and needs fixing or the nand itself has died. You will only find out by flashing a stock rom, preferably the same as what was already on it but if you don't know then go for the latest. Make sure you get a single package and not the 4 individual parts.
shivadow said:
Flash a stock rom via odin before you knacker it completely.
The problem is the recovery partition as that loads everything to start the os and it is complaining that it can't find cache. That means one of 2 things. Either the recovery partition is borked and needs fixing or the nand itself has died. You will only find out by flashing a stock rom, preferably the same as what was already on it but if you don't know then go for the latest. Make sure you get a single package and not the 4 individual parts.
Click to expand...
Click to collapse
Thanks shivadow,
Really appreciate your guidance here.
Gonna try and give you as much info as I can here. I followed your suggestion above.
Using on Windows 10, ODIN V1.85, which had Auto Reboot and F.Reset Time ticked.
I set the phone in Download Mode, (Power Button+Home+Volume Down), and connected to the PC via USB.
The screen before you press Volume Up to enter Download mode shows a yellow triangle with an exclamation mark.
Download Mode shows Custom Binary Download: Yes (7 counts)
Odin shows status: yellow 0:[COM3] <ID:0/003>Added!!
To the PDA section I added this md5 file : I9300XXUGML2_I9300TMUGML2_I9300BVUGML1_HOME.tar.md5
which I'd extracted from TMU-I9300XXUGML2-20140325171933.zip, which I believe is 4.3 Jellybean for the UK T-Mobile handset.
I chose this as although now unlocked, this handset was originally a T-Mobile phone.
On Odin, I then pressed Start. A blue progress bar is shown on the phone.
This reaches its end and Odin reports Success.
The phone rebooted, I held the Recovery button config, Power Button, Home and Volume Up.
Initially I see the Android image with the blue icon, then it switches to the Android on its back with the red icon.
Once in Recovery the phone reports:
E: failed to mount / efs (No such file or directory)
E: failed to mount /cache
E: failed to mount/data
E: failed to mount/data/log/recovery_log.txt
E: failed to mount/system
E: failed to mount/cache recovery/log
can't open /cache recovery/log
Can't mount cache/recovery/last_log
Can't open cache/recovery/last_log
Can't mount /cache/recovery/last install
Can't open cache/recovery/last install
I then selected Wipe Data/Factory Reset, and the phone responds with:
Wiping data
Formatting /data
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
can't mount /cache recovery/log
can't open /cache recovery/log
etc
This is the cycle I've basically been stuck in whilst attempting to recover this phone.
Any more advice would be greatly appreciated, and should you require further details from me, be it more in depth or not, please don't hesitate to ask.
Many thanks already.... Calhoon. :good:
Looks like the internal memory chip may be damaged.
You could take it to a cell shop to see if it can be force flashed using something like at Octopus Box.
audit13 said:
Looks like the internal memory chip may be damaged.
You could take it to a cell shop to see if it can be force flashed using something like at Octopus Box.
Click to expand...
Click to collapse
Hi, thanks for the reply and advice.
Would you mind letting me know what is it that told you the internal memory chip may be damaged?
And if anyone else out there has an opinion I'd be please to hear it out.
Thanks.. Calhoon
Partitions that cannot be mounted by stock recovery is an indication of a memory problem. It could be that all partitions need to be re-created or the memory chip is damaged.
A failed memory chip on cellphones is not uncommon.
audit13 said:
Partitions that cannot be mounted by stock recovery is an indication of a memory problem. It could be that all partitions need to be re-created or the memory chip is damaged.
A failed memory chip on cellphones is not uncommon.
Click to expand...
Click to collapse
Apart from visiting a cell shop and asking them to force flash it, is there any way that you know where I could recreate the partitions myself?
Thanks again... Calhoon:good:
Dead phone. You can try flashing the original recovery on its own but if it fails to flash or fails to boot afterwards you can safely assume it us a dead phone with no way to recover it. Not even Samsung can do it. The only option is replace the motherboard.
I've tried to flash TWRP today and got stuck in a bootloop. First unlocked oem - success. Downloaded corresponding TWRP version (3.0.2, my WIKO is running Marshmallow 6.0) according to instructions from "https://rootmygalaxy.net/root-wiko-fever-4g-and-install-twrp-recovery/" Then went to flashing Wiko with TWRP through "SP Flash Tool", got green tick (hooray)... and during reboot my phone showed WIKO logo for 2 times, then went into TWRP... and looped, looped, looped.
Screen showes such text:
"Could not mount /data and unable to find crypto footer
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
... done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Running Recovery Commands
Formatting Cache using make_ext4fs
Failed to mount '/data' (Invalid argument)
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)" then loops
Since then i waited a few minutes/few reboots to look if it ceases to show up, but it persisted. Since usual holding POWER button for a few seconds didn't worked, as phone was not powering down and still booting into TWRP, I decided to unplug battery for 10 minutes. My WIKO has non-removable batt, but these few screws weren't a big problem, and I managed to unplug it. Sadly, after plugging it back, looping came back too.
Tried to power it back (after another 10 mins unplug) with VOL+ and VOL- to put it into download mode, but it just showed " ==> meta mode" info on left bottom part of the WIKO screen, then screen appeared once again without that info, and looping TWRP came back. Tried it few times, with same result.
Seems that nothing works - any help would be really appreciated
EDIT:
Managed to work around it on my own One thing that still worked good was PWR + VOL+, meaning enter boot menu (Recovery, Fastboot, Normal). When in recovery I was able to use TWRP, and since after unlocking oem my data simply vanished, it was only to decide whether to restore Marshmallow or move to madOS 8.1 https://forum.xda-developers.com/android/development/rom-official-mados-wiko-fever-clones-t3762804 Rest is a history....
Since original thread is closed, I will express my deepest thanks to @DerTeufel1980 for a great, great job doing Oreo8.1 compilaton for Wiko Fever. Working like a charm