[Q] Samsung Galaxy S3 GT-i9300 Can't mount /data /efs bricked ? - Galaxy S III Q&A, Help & Troubleshooting

Hi everyone,
I've been trying quite a lot of things until now to fix my phone, but it seems that I can't get it right.
My phone (Galaxy S3 Gt-9300) was running on Cyanogen 13 until now.
Somehow the battery started to have problems and my phone rebooted quite often, and would sometime get stuck at boot.
Then the battery inflated, and the phone couldn't turn on anymore.
So i bought a new battery, but now I'm stuck on booting screen.
I have tried to wipe data/ factory reset via the clokworkMod recovery .
But the /data and /efs cannot be mounted. So impossible to wipe them out.
I have tried to install the firmware using ODIN, but it somehow always gets stuck when trying to retrieve the PIT (i have tried 3-4 different ODIN version, multiple cable and computer)
If I install a zip from sideload, i get errors too :
"could not detect filesystem for /dev/block/mmcblk0p9"
"could not detect filesystem for /dev/block/mmcblk0p12: assuming ext4
mount: failed to mount /dev/block/mmcblk0p12 at /data: invalid argument
unmount of /data failed : no such volume
detected filesystem ext4 for /dev/block/mmcblk0p9"
Script succeeded result was [0.200000]
Basically the only thing that this achieved was changing the logo of the boot (but still stuck)
I fear that the internal memory was damaged during a bad shutdown.
What can I do ? Remapping the internal memory might be an option but since I don't have a readable /efs I don't know if this would work.
Thanks for the help

Your only option is the rescue firmware in general forum with pit. If this won't flash then your emmc chip is damaged.

So if the emmc chip is dead, it's game over ?

Have you tried an official cwm recovery from the official website?
Sent from a stolen phone!

Whatever rom I use, it cannot finish.
Either it's the official one or not.
Odin cannot complete the job. It usually get stuck at PIT.

Related

[Q] [Help] [GT-I9000M] I can enter download mode... but

tl;dr What files do I use in Odin to return to stock from a phone that boot loops? (i have no idea what software was on there before it started)
The phone came from Canada (Bell). Previous owner tried to unlock it for use in the US. Phone worked for a few days then turned off & wouldn't get past boot (it would show animation & sound then go into a black screen with menu/back key lit up). It was also missing volume up/down keys. Phone was given to me as I was moving back to Canada. Now here I am in Canada...
I've ordered & replaced the volume keys, got into download mode, and using Odin I've flashed "I9000XXJVU_I9000OXAJVU_OXA". I've no idea what software version was on the phone at the time. I used pit 512. The phone reboots and...
Code:
-- Copying media files...
[COLOR="Red"]E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.[/COLOR]
Meida files copy failed.
-- Wiping data...
Formatting /data...
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
[COLOR="Red"]Data wipe failed.[/COLOR]
-- Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'KOR'
Successfully applied multi-CSC
The failed actions are due to me not having an SD card correct? And at the bottom there it says it applied the CSC-code 'KOR' for Korea? I'm in Canada.
Now the phone goes into a loop, flashing the "Galaxy S GT-I9000 Samsung" logo on and off for ever (no animation or sound this time). I also tried flashing the latest from sammobile (under GT-I9000M). It's a single file and that put me in a boot loop as well.
Any advice greatly appreciated!!!
You will have far better luck going to the I-9000 forums to get answers. While similar, they are different from the T959 Vibrant.

S4 legend bricked. Just enter in recovey

Hello everybody!
Well...Like the title says, my phone (HDC S4 galaxy legend) isnt responding at all. I was using my phone when a message told me that sd card was with errors and asked me if i want to fomat. I´ve selected yes and the nighmare starts... Now when i power on the phone shows the logo and get stucks there... well, i thought that maybe recovey will fix this.. i have entered recovery and the first warnings appeared "e: cant mount sd card". I have tried format all the options, make wipes and stills appears message e: cant mount emmc or e: cant mount cache... i have tried to install the stock rom from the sd card and apparently shows that is installing, but then reboots and it get stuck in logo screen again. Another thing is that when i connect the phone to my pc, it doesnt recognize it, not even my PC make a sound when i connect the phone. I have tried to reflash with flash tools but it doesnt work cause the phone is not detected, is like a brick.. well.. then i have tried to make partition from cwm and nothing works and it doesnt installs the rom.
Now i can only access to recovey but nothing else, please someone help me :crying: :crying:
No one can help?
No one can help?
I have detected the problem. My internal card is bad formated, because it says can't mount emmc / data .... i have tried whith aroma wiper but i still cant recover the original partition (ext4). Someone have a tool to get back to my old partition????

[Q] Error mounting /data

Hey! yesterday I found a new rom for my phone, Alcatel One Touch 991 so I went downloading it, after flashing it. Everything worked just fine, but the after i restarted the phone, it didn't boot, it was stuck at the boot logo. So, I formatted my whole phone and then reinstalled the preloader, dsp_bl and that stuff. The only problem is that when I got into recovery to install android, i tried to wipe data/factory reset, but the screen just got black, then it gone back to the CWM's start screen. When I try to format /data it does the same thing, and when i try to mount /data it says "Error mounting /data". Installing a ROM won't help anyway, it would get stuck at the logo.
Can anyone help me? This phone does not use ODIN, because everything i found was for Samsung phones.
Thanks.
Anyone? :crying:

[HELP] Unable to mount storage: Bootloop

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?

Stuck on Splash Screen Logo - Samsung Galaxy S3 GT-i9300

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.

Categories

Resources