[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AquaYan:
Hi. Before you read all that mess below, just answer this simple question first: Is it possible to restore to stock (as in with all bloatware and pre-loaded apps intact) on an AT&T Samsung Galaxy S4 SGH-I337 Baseband Version I337UCUAMF3 on Android Version 4.2.2? If not, just say so and disregard reading the rest lol. (If it's any help, the Kernel Version is 3.4.0-812098 and Build # is JDQ39.I337UCUAMF3).

So I have been messing around with my S4, specifically with NoBloat and rooting, trying to delete bloatware and such. And with that line, you should already know by now what has happened. Though I did backup most of the things I deleted, I think I've deleted some important things and now want my phone returned to stock. It has been rooted so I also want to get rid of the binary counter as well. Before you send me to another thread however, I want to tell you guys what I have already tried and researched, yet always encounter an obstacle in:

I have tried using Odin (3.07 AND Odin3 v1.85) and flashing (correct term?) to my phone with I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 as the PDA, but when I pressed start, Odin would get to the first box then say FAIL!. My phone then has START [224, 1440] then under it SW REV. CHECK FAIL : fused :2, Binary : 1. I think it may be because in the ID: COM space, my phone recognizes as a 0:[COM:3], 4, or 5, but not a 6, which in a video tutorial I've watched, says it must be a COM:6 for it to work. I have tried many of the troubleshooting tips such as removing and putting the battery back in, changing usb ports, and reinstalling drivers, all of them leading to the same FAIL! screen. I know the file and the version of my phone doesn't match (wishful thinking I guess xP ), but is there any other way pr a tar.md5 file for my version to restore using Odin?

Another thing I've tried is using ADB to reupdate (?) my phone. I downloaded the adt files and put the tar.md5 file in the platform-tools folder. Then I opened a command prompt but when I type in adb sideload <filename.tar.md5>, it says it could not be read or could not start. Backtracking, I tried downloading sdk properly but got lost in that and jumped off this method completely.

Finally, giving up all hope of reverting back to complete stock, I simply wanted to reset the binary counter, and even here I had issues. I found out that AT&T is one of the carriers that locks their bootloader, so I searched and found djrbliss' LOKI method to get around it. I tried downloading at the github link, but didn't know how to download it (maybe I somehow just didn't see the download button), so sadly, I couldn't do this either.

I have reset and restored using past backups but the applications, lock screen, and a few other things did not restore properly (while the rest of it did fine, strangely).

Sooo...yeah. I think I may have exhausted almost every method possible, so this thread is really my last resort. Please help me find a way or just tell me it can't be done, so I can put this to rest.

Sorry for the long-winded message, haha, but thanks to all who'll help me find a solution to this dilemma :)