It would boot into TWRP recovery or download mode but never boot. I eventually noticed in TWRP that it said my internal storage was 0MB large and found that the userdata partition was corrupt (e2fsck wouldn't work)
I've tried every combination of flashing a stock .tar and/or .pit file but nothing seems to change.
Here is the output I get when trying to repartition with odin:
<ID:0/003> Added!! <ID:0/003> Removed!! <ID:0/003> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/003> Odin v.3 engine (ID:3).. <ID:0/003> File analysis.. <ID:0/003> SetupConnection.. <ID:0/003> Initialzation.. <ID:0/003> Set PIT file.. <ID:0/003> DO NOT TURN OFF TARGET!! <ID:0/003> Get PIT for mapping.. <ID:0/003> Firmware update start.. <ID:0/003> aboot.mbn <ID:0/003> NAND Write Start!! <ID:0/003> FAIL! <OSM> All threads completed. (succeed 0 / failed 1)
heimdall flash --repartition --verbose --RECOVERY openrecovery-twrp-188.8.131.52-d2att.img --pit ../sgh-i747-16gb.pit --no-reboot
Heimdall v1.4.0 Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au/ This software is provided free of charge. Copying and redistribution is encouraged. If you appreciate this software and you would like to support future development please consider donating: http://www.glassechidna.com.au/donate/ Initialising connection... Detecting device... Manufacturer: "Sasmsung" Product: "MSM8960" length: 18 device class: 2 S/N: 0 VID:PID: 04E8:685D bcdDevice: 0100 iMan:iProd:iSer: 1:2:0 nb confs: 1 interface.altsetting: num endpoints = 1 Class.SubClass.Protocol: 02.02.01 endpoint.address: 82 max packet size: 0010 polling interval: 09 interface.altsetting: num endpoints = 2 Class.SubClass.Protocol: 0A.00.00 endpoint.address: 81 max packet size: 0200 polling interval: 00 endpoint.address: 01 max packet size: 0200 polling interval: 00 Claiming interface... Attempt failed. Detaching driver... Claiming interface again... Setting up interface... Initialising protocol... WARNING: Control transfer #1 failed. Result: -9 WARNING: Control transfer #2 failed. Result: -9 WARNING: Control transfer #3 failed. Result: -9 WARNING: Control transfer #4 failed. Result: -9 WARNING: Control transfer #5 failed. Result: -9 WARNING: Control transfer #6 failed. Result: -9 Protocol initialisation successful. Beginning session... Some devices may take up to 2 minutes to respond. Please be patient! Session begun. Uploading PIT ERROR: Failed to unpack received packet. ERROR: Failed to confirm end of PIT file transfer! ERROR: PIT upload failed! Ending session... Releasing device interface... Re-attaching kernel driver...