[Verizon Samsung Galaxy S III] noidodroid:
It could have been one of the other firmwares but was labeled tracfone d2ftnvzw. I might still have the firmware somewhere and if I find it or research for it again (got it from an archived site no longer up) I will post here for you to look at or send you a link via PM.

Well here is the verdict guys. I tried the unbrick file wrote to a 16GB Sandisk Class 10 microSD card on FAT32 which only created one partition for me unlike the d2vzw unbrick files which created multiple partitions. Any idea where the others are or are they not needed for this variant to unbrick? So after creating the microSD card to unbrick I put it in the phone with two different batteries and tried pressing power.. Nothing at all, no lights, no vibrations .. completely dead. However it still shows 9008 in Com ports on my phone repair box. So im wondering if there is a way to possibly get the partitions flashed through EDL with the right programmer and xml files. However I am sure about Samsung as this would be the first time I have repaired one via EDL and I am not finding any such files needed on the web. After this I plugged this phone into the wall charger and got a red light as if it was charging. My charger felt a little loose so i pulled it out and took a look inside and... pins for data transfer are no longer present with the side of the pins being broken off. So it only recognizes the wall charger right now. At least its showing signs of life. I cannot do much though with a broke charging port and do not want to repair it unless i can successfully unbrick this device. I am talking with a buddy who runs a Riff Box in his shop for repairs. Supposedly there is a new solderless method so perhaps he can aid me in repairing this device..

I had NO idea how rare this Samsung Galaxy S3 SCH-S968C variant was until researching it and looking on eBay. They go for as much as $80-$100 and thats just on eBay. Much more elsewhere. ESP if with the unlocked bootloader. The firmware i mentioned earlier i found was an upgrade to 4.4.2? i believe. Now whether or not it was for the S968C I do not know anymore. It more than likely is the cause of the brick if it wasn't. Though i dont see why I got a hardbrick. I never get these with samsung and I deal with a lot of devices, flashing / cross flashing sometimes, frp, repair etc.

Back to finding another SCH-S968C on H1 bootloader unlocked or a d2vzw bootloader unlocked. Have some promising leads just do not want to spend what they are asking. I also want to make sure the bootloader is unlocked. I started this project and plan to finish it off! =]

---------- Post added at 10:15 AM ---------- Previous post was at 10:05 AM ----------

Thanks for the help [MENTION=4828250]Ibuprophen[/MENTION]. Should help others as well. I will grab SamMobile's copy of the firmware and compare with what I have. I too trust SamMobile the most but I just cant wait on the lengthy downloads due to slow throttled speeds. Majority of the time I am in a hurry so I go to alternate sites I use majority of the time that have a bit quicker transfer rates. Perhaps I will get a paid membership for SamMobile eventually as it will benefit me in my everyday work.

---------- Post added at 10:22 AM ---------- Previous post was at 10:15 AM ----------

The Recovery partitions could all be on different blocks I never checked on that. Just For the record I was able to flash a multitude of what were suppose to be incompatible custom recoveries (some Verizon / ATT / T-mobile / .) on this S968C with no problems, all functions working for the most part except for a couple recoveries. I did however have to edit the intaller scripts for the multiboot I had. Though i later found what i believe was designed for the S3 a dualboot and even multiboot but never took anything further after the brick occured.

---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------

The SCH-S968C can be unlocked and will work on other CDMA networks. I was looking into unlocking it next after I got everything working correctly and backup made. It however will not work on GSM networks as it is CDMA/LTE only and carries no GSM bands. At least this is what I found from researching so decided not to take the unlocking any further for GSM and decided it would be best to leave it working with TFN/Verizon. I was surprised I kept a signal, IMEI, serial, baseband and such intact flashing up to 6.0 MM. Not once did I lose anything. I expected this after going up to 7.1.2 OctOS but unfortunately never got to try it due to the brick.