Samsung Galaxy S3 GT-i9300 stuck at boot logo - Galaxy S III Q&A, Help & Troubleshooting

The phone can boot into Download Mode and Recovery mode. I've been googling about this problem for like a week now. the first attempt that I did was using Odin and downloading the *.md5.tar for my phone. It gave me several errors:
<Download mode details on the top left corner:>
ODIN MODE
PRODUCT NAME: GT-i9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM OFFICIAL: Official
<Odin GUI Errors:>
[FAIL]
ID/COM: [COM9]
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Next I tried recovery mode. While entering recovery. I got errors also:
Starting Recovery mode errors:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
# MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
E:failed to mount /cache (No such file or directory)
Can't mount /cache/recovery/last_recovery
E:failed to mount /data (No such file or directory)
E:Can't mount /data/log/recovery_log.txt
E:failed to mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (No such file or directory)
<After those errors stop appearing. The top part gets replaced with:>
Android system recovery <3e>
Volume up/down to move highlights;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
----------------------------------------
<When selecting "Apply update from ADB sideload / cache / external storage (also known as sdcard)". Errors are:>
E:failed to mount /system (Block device required)
E:failed to mount /cache (Block device required)
<If ADB is selected. the last lines say:>
Now send the package you want to apply
to the device with "adb sideload <filena
me>"...
<If external storage is selected. the last lines say:>
E:failed to mount /sd card (No such file or directory)
<When selecting "wipe data and fatory reset and/or wipe cache partition". Errors are:>
E:format_volume: make_extf4fs failed on /dev/block/MMCBLK0P12
E:format_volume: make_extf4fs failed on /dev/block/MMCBLK0P8
Please help
UPDATE: While I'm attempting to restore the *.zip update with ADB. The process goes to:
loading update.zip
sending update.zip ?? % (with underscores spazing from left to right)
and then looking from the phone.
it says:
<<<some things that I forgot after the sideload. the errors goes too fast for me>>>
Installation aborted
E: Can't mount /cache (Block device required)
E: Can't mount /system (Block device required)
E: Can't mount /efs (Block device required)

---

Try using different USB cables and USB ports to flash with Odin. I also recommend using Odin 3.07 as that has always worked for me.

---

Borked recovery. Flash back to stock is the best option but if that is failing then you don't really have much choice.
Beamed in by telepathy

---

audit13 said:
Try using different USB cables and USB ports to flash with Odin. I also recommend using Odin 3.07 as that has always worked for me.
Click to expand...
Click to collapse
I did borrow an original cable from my friend. The error is still there. I also tried plugging the cable from the rear usb port.
But thanks for the reply. I hope that others can find this helpful too

---

shivadow said:
Borked recovery. Flash back to stock is the best option but if that is failing then you don't really have much choice.
Beamed in by telepathy
Click to expand...
Click to collapse
Hmm.. "Borked recovery"? You mean that every command / operation that the recovery mode is performing are being blocked by the system itself? or you mean by errors in files inside the eMMC? There is no proof that the eMMC is damaged because it can boot to Download mode and recovery mode. I am still wondering if the recovery, download mode have their own eMMC.
BTW is it "ok" to use an SDHC for recovery image (selecting "Apply Update from external storage")? bcoz its the only one I have ATM (and no cash)
I am willing to go for SD card as an internal memory for the phone. I've read many articles about running your phone from SD card if the internal memory. But with one disadvantage. Read and Write are slower than eMMC. As much as I want to perform this operation but I don't have JTAG or other tools to start with. I also don't know what resistor to short.