[HELP REQUEST] Device Bricked, Odin Hangs at NAND Write Start - Galaxy S III Q&A, Help & Troubleshooting

Hey Guys,
So, My first post has to a help request...
I've had my SGS3 for maybe 3 years now, and had it flashed with CyanoGenMod v10.x and a version of CWM. And about 4 months ago, my phone decieded it would reboot itself one last time, and then just sit on the CyanoGenMod boot sceen, for hours and hours and hours on end. I thought, maybe, it would sort itself out if I left it running like that. Queue leaving my phone on that screen for a month, Nothing new, no change. Alright, Ill jump into CWM and try a quick and dirty reflash, just use CWM to flash the ROM that ive got on my SD card. And then... It went up the creek. From there, the flash failed, gave me an error code (cant for the life of me remember) and then would only sit on "Samsung Galaxy SIII GT-I9300".
At this point, I decieded to leave it alone, I had used this phone every day for 3 years, and put that thing through it's paces, It is it's time to die.
But ALAS, Today I'm doing a Dr.Frankenstein. I did some research, and came up with this thread.
Now, I know that I should have had a backup sitting around, and I did, until I sold off my old computer and completely forgot about the "BACKUPS" folder that was on it...
So, I started following the above guide, Boot into Download mode, Connect to ODIN, attempt to flash the VRALEC bootchain file, but here is where I reach an issue. Although ODIN recognises that ive got a device attached, Here is the log it throws me.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
And onscreen, I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And there it stays.
Ive done a little more research and tried to use this to no avail, mainly because ive no idea how to use it xD.
Anyway, Any and all help is going to be really useful right about now, Ive already ordered a new phone ( A oneplus two in case youre curious) so reviving this phone isnt too important, but it would be nice none the less. Im pretty sure ive deleted all user data anyway, so its not to get any data back, not that you can once it's bricked AFAIK.
Thanks a bunch.
-Starns
EDIT::
Also, here is a screenie of ODIN after it's been trying to write to NAND for like, 3 hours

---

If you have the unlocked btu version then flash this rom: https://drive.google.com/file/d/0B4vTiHTBB629OVlvY0pkcXN4ak0/view?usp=docslist_api
If no joy then the nand is borked.
I wish I stole my HTC M9.

---

shivadow said:
If you have the unlocked btu version then flash this rom: [SNIP BECAUSE NEW USER]
If no joy then the nand is borked.
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Thanks for the help man, After spending some time trying to get that ROM to flash, Ive decieded that the NAND is up the small river lacking any form of propulsion. :/
anyway, here's the ODIN output
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

---

Yep. Borked nand. That rom is my ol' faithful. No flash means dead phone.
I wish I stole my HTC M9.

---

Flash twrp as recovery and than flas @archidroid's v1.8 rom for s3. I havd cwm first and it goes with flashing rom but still hangs at the reboot. So fix was twrp
Sent from my SM-G900F using Tapatalk

---

Starns said:
Hey Guys,
So, My first post has to a help request...
I've had my SGS3 for maybe 3 years now, and had it flashed with CyanoGenMod v10.x and a version of CWM. And about 4 months ago, my phone decieded it would reboot itself one last time, and then just sit on the CyanoGenMod boot sceen, for hours and hours and hours on end. I thought, maybe, it would sort itself out if I left it running like that. Queue leaving my phone on that screen for a month, Nothing new, no change. Alright, Ill jump into CWM and try a quick and dirty reflash, just use CWM to flash the ROM that ive got on my SD card. And then... It went up the creek. From there, the flash failed, gave me an error code (cant for the life of me remember) and then would only sit on "Samsung Galaxy SIII GT-I9300".
At this point, I decieded to leave it alone, I had used this phone every day for 3 years, and put that thing through it's paces, It is it's time to die.
But ALAS, Today I'm doing a Dr.Frankenstein. I did some research, and came up with this thread.
Now, I know that I should have had a backup sitting around, and I did, until I sold off my old computer and completely forgot about the "BACKUPS" folder that was on it...
So, I started following the above guide, Boot into Download mode, Connect to ODIN, attempt to flash the VRALEC bootchain file, but here is where I reach an issue. Although ODIN recognises that ive got a device attached, Here is the log it throws me.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
And onscreen, I get this:
And there it stays.
Ive done a little more research and tried to use this to no avail, mainly because ive no idea how to use it xD.
Anyway, Any and all help is going to be really useful right about now, Ive already ordered a new phone ( A oneplus two in case youre curious) so reviving this phone isnt too important, but it would be nice none the less. Im pretty sure ive deleted all user data anyway, so its not to get any data back, not that you can once it's bricked AFAIK.
Thanks a bunch.
-Starns
EDIT::
Also, here is a screenie of ODIN after it's been trying to write to NAND for like, 3 hours
Click to expand...
Click to collapse
Why not just try to flash the full stock firmware to restore the device? You might need to get a PIT file and possibly turn on the repartition option in Odin if isn't already when you open Odin.
If Odin doesn't work then try downloading a Linux distro and make a Linux live USB or Live CD then give Heimdall a try? Its a bit more complicated than Odin but it has been known to successfully restore devices that Odin never could, there is also Heimdall for MAC and JOdin for MAC.
Dripped from the Tapa of a Liquidsmooth far far away Galaxy SIII