[Galaxy Note 3 General] Lt1streconbn:
Tried this on several devices, and several different ways

I have finally gotten one to trip... while in system I formatted mmcblk0p21 with term emu then used ROM manager to flash CWM recovery to the device. It worked like a charm, I rebooted to recovery and got the moronic AT&T warning of non-authorized software and a softbrick related to booting to recovery. System was of course fine, as Ive read tons of post of people trying this on the SGH-I337 S4 on NB1-NJ1. This does trip Knox, which means the filter for the partitions is in the same place as the Knox warranty bit. That was actually helpful to know. It comes down to the bootloader though, as we know that is where the bit is stored. It's the one thing myself and no one else has managed to get past thus far.... anyway, I did flash with ODIN back to full stock immediately and rooted real quick and use SafeStrap to restore. The bot did not reset to 0x0 though... it remains 0x1. I needed that though lol... it helps me try different things Ive been working on to reset that bit... and there by learning to unlock bootloader hopefully.... as that's actually what I was working on in the beginning months ago when I stumbled over this post. Im working on a possible vulnerability that'll allow flashing the older, unlocked bootloader to the device... so far it has not worked. It bricks the device pretty well and you'll be paying $75 to Samsung to get it fixed. The bootloader is nearly identical to previous ones, with the difference of a 1 being a 0 now. It's been built up in layers, which is typical of development. They added the current security literally on top of the older version. Its easier and less cost and faster to do this. It's... like an onion in a way... and you just have to keep pealing the layers back. I think Im on the last one :) only took months to do in my spare time. That doesn't mean even with bootloader reflashed to previous version that knox warranty will reset, but itll be a huge help to do that with custom recovery in place and accessible and an unlocked bootloader I believe. IF it is in fact stored in bootloader partition somewhere I have not seen yet, flashing a new one will fix it because it didn't exist in 4.2 version and will be formatted and flashed over. It helped getting localhost working properly on port 5037. It at least allows me suid access. Youll have to remove knox and disable tima to get that to work or it'll freeze your SU app up and kill your access as soon as you do or itll freeze a script as soon as suid is issued by SU app. Anyway... that's where I am with this atm. Im running thru things with the 0x1 device and trying different 'approaches' to get more access and get the bootloader to accept reflashing to older version. No luck yet :( non of the things Ive tried reset the bit to 0x0 either. I do believe every now and again... something just glitches during rooting and flashing that might stop the bit from being changed in both props... there are two places after all. Perhaps if only one trips it doesn't truly trip the bit and it appears to be reset because one time in download/ODIN mode, a person, like myself saw a device show 0x1, but after doing something else... random thing maybe... it changes back to default 0x0. It's very possible :) Sorry this is long, but I had a lot to say. I'll post if I have any progress.