If you are reading this, you probably have a bricked/dead Galaxy S 3 which you want to fix yourself.
Please note that a phone can be Soft-bricked and Hard-bricked. Google them up if you don't understand them.
Also, the brick could be software or hardware related.
Through this guide, I'll help you do anything software related to fix your S3 phone. I hope you succeed, otherwise you need to fix the hardware which you probably can't do by yourself at home.
CAUTION: If you don't know about flashing, Odin, ADB, or haven't installed USB Drivers, or if you are a noob, please read other topics first. I'm not responsible for any damage you might do to your phone.
If your phone is soft-bricked, you can flash it with a full firmware.
Please check out "What I had tried" if you are not interested in what ROM, Kernel and Recovery my phone was using.
Thanks for everyone's help.
My phone was:
I had a Galaxy S3 19300 International. I hadn't done any flashing/rooting/upgrading in a while.
And I was running a DeltaROM III with android 4.3 (and heavily modified by myself in many parts), Googy Max Kernel, plus PhilZ Touch Recovery, when the accident happened. A very nice pack of ROM, Kernel and Recovery indeed.
I really loved that phone, and have tested any ROMs (from latest Stock to CyanogenMod) and any recovery (CWM, TWRP, ...) on it.
What had happened:
One day my battery went down and my phone turned off.
When I turned it on, it stuck on the kernel boot-screen so I turned off my phone and went to the Android Recovery using Vol Up+Home+Power.
My phone couldn't mount any partitions at all.
boomboomer said that letting battery die has a high chance of destroying the emmc chip (which is an "insane" chip Samsung uses for internal memory).
This is the exact log that I was getting after flashing on TWRP (TeamWin Recovery):
E:Unable to find partition size for '/boot' E:Unable to find partition size for '/recovery' E:Primary block device '/dev/block/mmcblk0p12' for mount point '/data' is not present! E:Unable to mount '/data' E:Unable to recreate /data/media folder. E:Unable to mount '/efs' E:Unable to mount '/cache' E:Unable to mount '/system' E:Unable to mount '/data' E:Unable to mount '/preload' E:Unable to mount internal storage. E:Unable to mount /data/media during GUI startup. E:Unable to mount '/cache' Full SELinux support is present. E:Unable to mount /data/media/TWRP/.twrp when trying to read settings file.
(The following happens for /cache, /data, /system and all other partitions)
E:failed to mount /data (no such file or directory) E:Can't mount /data E:Can't open /data
Or maybe the mounting script has been corrupted I guess.
- Phone turns on.
- Recovery mode.
- Download Mode.
- Flashing with Odin or other software.
- Custom Recovery (via Odin)
- ADB in Recovery
- Installing ZIP files if I push it to /tmp/ directory via Odin and installing from TWRP.
What didn't work:
- Mounting any partitions at all.
- Mounting USB in the recovery mode.
- Booting to Android.
What I had tried / You should try too:
I usually Google these problems, and try to fix them myself. This usually works if the internal memory is not damaged, otherwise I can't do anything.
- Flashing PDA with Odin 3.09.
- Re-partitioning my S3.
- I tried re-partitioning using a PIT file + an older version of android via Odin 3.07.
- I tried flashing TWRP. (to upload Aroma File Manager and see what can I do.)
And not slightest bit of luck. It seems nothing could mount any partitions at all.
I've sent my phone 2 times to the Warranty service and 3 times to a phone-repair shops, and they could fix my phone,
I wanted to try doing a JTag, but I couldn't do it at home.
UPDATE #1: I tried [RESCUE FIRMWARE SGSIII I9300], with GT-I9300XXUGMJ9_KOR_MULTI_FACTORY + a PIT file. It didn't helped me either, because as I said my problem was with my emmc chip - not software. (Please try it.)
My device couldn't mount or find any partitions at all.
UPDATE #2: I gave up fixing my phone myself and brought it to some phone-repair shops. They tried restoring the efs partition, flashing a bootloader, wiping partitions, and using something called a 'box'. These didn't work either - the emmc chip really needed to be changed.
(By the way, oddly they call the emmc chip a "hard" here, although it has nothing to do with a H.D.D.) :|
However, when they changed the emmc chip, my signal went off, and my phone showed "Not registered on network". Oddly though, My IMEI wasn't null and I had a baseband version.
I took my phone to another place, they used a 'box' - which turned out to be a z3x box - and it really worked, and restored my signal (they only used ADB to restore it in less than 5 mins or so.)
Many said that using this method, my signal would likely die again if I flash my phone again, but he guaranteed that it would not, using his own method.
So, I decided to flash a Googy Max Kernel (mostly for fading LED), and my signal died again. This time, my IMEI was showing null, and my baseband was unknown. WTF.
And I really hate those bastards who want to charge me whenever a single small problem happens.
I'm going to buy a Galaxy S 5 and get rid of this phone for good. :| (or maybe keep it as a iPod/Game Device.)
I want to boot my phone normally, and I my /data partition is important for me, I prefer to save it! (I'm not a back-up kind guy unfortunately.) :|
I am a programmer, so I'm not a noob (as you can see!)
I want to learn how to fix my phone - so I don't have to bother you guys or spend my money on those phone-repairing shops whenever something like this happens.
Thank you all, and have a great day.
P.S: I will remove unnecessary details from this post once this problem is solved.