Now I will walk you through what I did that caused this dilemma, aka doing the absolute most
It started out as me wanting to test out 2 different ROMS (eZKAT Beta found here http://forum.xda-developers.com/show....php?t=2747733 and Ditto Note 3 found here http://forum.xda-developers.com/show....php?t=2541860). My smart @$$ (sarcasm of course) didn't do a full wipe internally when flashing between the two. Reason being, I honestly just started doing that and never ran into an issue until now because of not doing it. I recently got an S5 and my 32gb sd card is in that phone and I found an 8gb sd card in an old G1 I had. So because I had ROM files and TitaniumBackup files on the sd card, I was using internal storage to house the two test ROM's. Bad idea I now know. I'm so thankful my Note II is now just a backup along with my iPhone 4S but still, it's nice to be able to experiment with a test android phone and know your primary is fully functional. Plus, all the apps I bought and things I got used to using that are strictly for rooted devices...anyway back on topic.
I flashed eZKAT and got that fully booted, even installed xposed framework and wanam both worked. That ROM is not on hold but development is currently. I'm fine with that, what was put out for us to use does work. eZdubzitmk4 does great work, and has responded to PM's from me seeking assistance in the past. So since I'm somewhat familiar with his work, I didn't think twice about trying it out. My curiosity kicked in and I thought ok, let's try a different Note 3 ROM because I've successfully flashed and used Sky Note Air (both editions) in the past and seanzscreams is another developer who does great work. I'm not saying nor implying no one else does, I'm just shouting out two developers.
Something went wrong between me switching from eZKAT to Ditto Note 3 and the only thing I can recall not doing that likely enhanced my issue was not wiping internally. I tried to flash CWM and Philz Recovery as suggested here http://forum.xda-developers.com/show...41860&page=429 and I thought that would fix the issue. What actually happened was after flashing in Odin, the phone would attempt to boot into recovery and all I'd see was a navigation bar at the bottom with 4 arrows but no text and the screen would immediately fade to black and reboot. I could not get into recovery at all. I saw the Samsung Galaxy Note II splash screen repeatedly. I left it off the charger all day, and it repeated that same process the entire time. I tried using KIES and KIES3 but neither worked. I almost got something to work in KIES3 but right before the end, it failed and my phone said unsupported version in red text. I did a few Google searches at work which did help point me in the right direction.
I tried flashing stuff in the PDA slot as well as the Bootloader slot, but it didn't matter everything was the same result. My thought process was try it and see, all that can go wrong is it not boot into download mode . I prayed on it last night then did another Google search tonight when I got home from work, after attempting all that stuff again. This time I did a search for note 2 will not boot into recovery and I found this http://forum.xda-developers.com/show....php?t=2573576. TWRP was successfully flashed and I was able to flash CleanROM Ace 5.0 again now I'm happy ...but also EXTREMELY hesitant to flash anything else at this point. I'm just glad I no longer have a $371 paper weight ($321 for the phone and $50 for the AT&T flap cover case with attached back). I did state that if and when I fixed my phone I would create a thread about what I did and what worked for me. Hopefully this can be of use to someone else, because I know I'm not the only who has faced this issue. I also was all over Google with generic searches because all I knew was what was happening, not the technical/official name for what it was if that makes sense .
Here's a video showing what I'm describing.