[AT&T Samsung Galaxy S 5] mtpmd:
Need some help on an unexpected glitch updating to OF3

I have a problem I need a hand from some helpful expert on, a bit similar to the above. I have an S5 Active G870A that was running the rooted stock supplied courtesy of muniz_ri (thanks very much for that and all else you've done in this regard).

When I got notice of OF3 in an update check after reading about Stagefright, I took the OTA download, just to be able to capture it in case needed (as I've seen sometimes, requests for such by devs for their use), but did NOT install it, continuing to refuse when it nagged me, then also looked and saw that a rooted OF3 had been posted. BUT, I wanted to backup all my stuff before doing that, and I started this late and it took a while, so I went to bed. I woke up however, to find my phone in Odin mode, saying it was unable to boot normally. All I can think is that the OTA nagged me again, and when I didn't tell it "down boy", after waiting a while, it went ahead and executed on its own - which I'd've never thought it would do, but, in retrospect, wouldn't be surprised - and updated me with the stock OTA, which now won't load correctly due to my having been rooted etc. Turning the phone off and on, battery out and in, etc. a couple times, all gave same result, can't boot normally message and Odin mode on the screen.

Since I at least had Odin, and wasn't bricked, I decided to flash back to G870AUCU1ANE4_Full_Odin, as all the posts seem to advise is needed in such cases, but, this didn't quite take - I can now get past the first part of boot, but the initial splash screen still shows the "custom ROM" note from the rooted OF2 ROM, and, though it proceeds past where I had been, and like it's going to boot normally, then I end up stuck (in boot loop?) at the ATT logo, and nothing more happens.

I can however by keypresses during boot still call Odin mode back up, and I can also call recovery mode up.

But, since flashing G870AUCU1ANE4_Full_Odin didn't work, and all of the later rooted updates are for a running phone using flashfire, I dunno what I can do with either of Odin more or recovery mode, or any of the available update files, to get myself operational. I have some IT and phone savvy, but for the most part just follow the instructions of you experts, don't have that level of knowledge of the internals to be able to tinker much.

I also BTW have both CWM and TWCP nandroid backups of my rooted OF2 system made right before this happened, but, have never been able to (or gotten around to) flashing CWM or TWCP recovery, and likewise don't know how I might use the CWM or TWCP backups I have with Odin or with stock recovery (or whatever recovery muniz_ri puts in the stock rooted OF2, if it's not stock).

Anyone know how I can use the OF3 zips via recovery or via Odin, or some other answer (or am I now f***d because I was rooted OF2, and tried to flash back in Odin to NE4 and am now some weird hybrid [since it didn't quite take and seems to have left some of the OF2 stuff intact])? Any help? Any suggestions? I'm almost certain there's something I can do to fix this, I just don't know enough to know what it is.... lol (and also don't want to mess with it more before I get some information/advice, out of fear of making it less fixable instead of more fixed) Thanks very much!

Edit/Update: Fixed, resetting to factory from recovery after flash back to NE4 gave me a working boot to NE4 instead of the hang at the ATT logo.. From there all else re upgrading to the rooted OF3 has been fine. Ty all who helped/commented.