Hello everyone! I've been trying to fix this phone for hours now and I'm not sure what to do. It was rooted at one point and is now stuck in this boot loop. Every time It is turned on, it goes to the blue recovery screen. I did the wipes that are available and tried installing the update.zip but every time I do, I get this error:
E:Can't mount /dev/block/vold/179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
installation aborted.
I can get it into download mode so I'm hoping there is a way to just reset the phone with odin so I can start from scratch. The problem is, every guide I find leads to broken download links and 404 errors. If any of you could help me get this thing going again, I would be so incredibly grateful. Thanks in advance for all your help!
Nevermind, got it figured out. Couldn't find how to delete the post.
Welcome
Maybe it's strange but I accidentally removed the efs by clicking "format efs" ktool program and then the phone has shut down I might add that before I did the backup format but not gotten it to PC and is probably on the phone.
I tried 3 times to write it rom XEO-I9100XXMS7-20140522135710 but the phone is not picked up, stops samsung logo.
What do you keep trying? Download mode and recovery mode works, I might add that in the recovery writes in red E: failed to mount / efs (invalid argument)
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.
Woke up to my phone unresponsive so I removed the battery and tried to power up, but was stuck in a bootloop for more than 5 minutes. Rinse repeat. Nothing. So I boot into TWRP and try to factory reset but "
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
etc
---
Comes up. I am unable to wipe, flash, anything. I have tried both LG flash tools but they both fail. KDZ method says its complete but still stuck in bootloop. TOT simply fails to wipe.
I am unable to take my phone to Verizon as well because the boot-up image is Blisspop so they would know that I have rooted my device. In order for me to use Edge to get a new phone I have to trade this one in in working order, which now I can't.
Any help would be greatly appreciated as I've been working at this for the last 6 hours. I am thinking that it is an internal storage issue but like I said I am unable to take it into Verizon to attempt a warranty exchange.
INFO:
LG G3 VS985
BlissPop ROM - 06/22
Sirrometan said:
Woke up to my phone unresponsive so I removed the battery and tried to power up, but was stuck in a bootloop for more than 5 minutes. Rinse repeat. Nothing. So I boot into TWRP and try to factory reset but "
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
etc
---
Comes up. I am unable to wipe, flash, anything. I have tried both LG flash tools but they both fail. KDZ method says its complete but still stuck in bootloop. TOT simply fails to wipe.
I am unable to take my phone to Verizon as well because the boot-up image is Blisspop so they would know that I have rooted my device. In order for me to use Edge to get a new phone I have to trade this one in in working order, which now I can't.
Any help would be greatly appreciated as I've been working at this for the last 6 hours. I am thinking that it is an internal storage issue but like I said I am unable to take it into Verizon to attempt a warranty exchange.
INFO:
LG G3 VS985
BlissPop ROM - 06/22
Click to expand...
Click to collapse
I'm at the same spot with this in regards to the crypto footer issue...did you ever get this fixed?
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.