[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] bzwick:
Please lend a hand to help me rectify a problem.

Started earlier today by CF-Auto-Root my New Rogers SGH-i1337m, installed without incident via Odin 3.07, followed up with TWRP 2.7 install, again via Odin, without incident, then created NANDROID backup to ext sdcard.

First issues started cropping up, but culminating in what appears to be soft bricking:

1st) Could not mount internal memory (was attempting to browse in Windows) via TWRP. Every time I would select internal memory it would mount the sd card contents only. Weird, but pales compared to further issues.

2nd) Was preparing to install Custom ROM, boot into TWRP, attempted factory reset but this just constantly restarted TWRP. Thought this was strange so I figured Id use Goomanager to update TWRP, occurred without incident and I went back to attempt to factory reset, but then trouble started.

3rd) Boot looping, could not boot back into the OS. Decided I would attempt to restore my Nandroid backup, TWRP loads fine but restore didn't work. Figured Id try flashing back to stock rom (obtained RWC-I337MVLUEMK6-20131125124040 via links in other comments. This is where things got out of control:

A) Restore via Odin 3.07 failed, device restart failedbut loaded the "Firmware Upgrade encountered an issue..." screen.

B) Attempted redownloading the stock rom, new usb port, new oem cable, reinstalled drivers, and with each Odin would fail as follows:

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_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> boot.img

<ID:0/004> NAND Write Start!!

<ID:0/004> recovery.img

<ID:0/004> system.img.ext4

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

C) Briefly TWRP would not load, so I reflashed 2.7.0.1 for openrecovery-twrp-2.7.0.1-jfltecan without incident, TWRP reloaded fine, could now do factory reset, but often end up getting could not mount /system. Now using TWRP to restore theNANDRPID from earlier seemed to rebuild the partitions and said it was successful, and the device will boot to a static Samsung screen, but after 20 mins of waiting, would not boot farther.

D) At this point tried to reflash w Odin 3.07 the stock, but still get that error.

So here is where I'm at, with what appears to get me the closest to booting/flashing with stock:

1) Reflashed openrecovery-twrp-2.7.0.1-jfltecan.tar with Odin 3.07, immediately following this:

<ID:0/004> Removed!!

<ID:0/006> Added!!

<ID:0/006> Removed!!

<ID:0/004> Added!!

<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> recovery.img

<ID:0/004> NAND Write Start!!

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Removed!!

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

..and the device hangs @ "Samsung Galaxy S4" black screen, letting that sit for 15mins without any change (didn't expect it to, but may as well be complete).

2) TWRP is bootable (load screen says Recovery is not SEANDROID ENFORCED and Set Warranty Bit: recovery) and functional, rebooting recovery states "No OS installed, are you sure you want to restart? ". Interestingly with 2.7.0.1 now installed, i can factory reset but with errors "E: unable to mount '/system". In TWRP, i have tried restore of my NANDROID backup, it completes successfully and appears to rebuild the partitions, but even after completing the restore and rebooting, still end up hanging at the static Samsung screen for >20mins without a change. I could transpose the entire log from the restore if needed.

3) At this point I would try Odin 3.07 with the above stock image, and the failure when attempting to write system occurs again.

Ive been searching for hours and hours and attempting to reflash but not making any headway.

Could anyone help point me in some better directions? I just finished attempting KIES emergency restore, but it too failed when it tried to upload to the device.

Any help would be greatly appreciated.