Originally Posted by DDBgermany
Am I right that as of now rooting my device will set the Knox count to 0x1 and there is no way around yet?
According to the linked post it is so
Well I'm just asking because he actually updated his thread the last time back in January and I'm afraid I just missed something here perhaps. Unfortunately I bought the phone second hand and it has been updated to 4.4.2 before.
It might seem stupid to ask but I already searched the web for quite some time and all l can find is pretty old.
May someone just answering my question please?
I'll tell you what not to do: use Kingo Android Root. I had read somewhere, possibly on another forum, that it would work. So I looked at their site, and strangely, Samsung wasn't shown among virtually every other manufacturer. But I downloaded it, and ran the program.
Needless to say, it tripped that flag, and it also left the phone soft-bricked -- only running the bootloader every time it rebooted -- until I ran CF Autoroot, which did root it but would trip the flag anyway.
And incidentally, I also soft-bricked after flashing Clockworkmod Recovery. After restoring it once before, I almost shat myself. But the fix was entering download mode (Vol+Home+Power) and pressing the Up button.
Scared the hell out of me, because I've had the phone like a couple days. Before that, I managed to screw up two LG G2's, plus had a third one stolen. Guess I can't leave well enough alone. :P Anyway, hope you have luck finding 0x0... if you find it, please tell everyone in this thread. I searched and read for half an hour, and found nothing.
·T···Mobile· Galaxy Note III (SM-N900T [hltetmo])
Rooted stock 4.4.2 ROM & recovery, tripped 0x1 but froze KNOX
AT&T LG G2 (D800, unlocked to use with T-Mobile)
LG warranty replaced two defective phones, had a third stolen
·T···Mobile· Galaxy S II (SGH-T989 [Hercules])
Broke, don't work -- never attempt to repair your USB port!
Plus original G1, myTouch, Slide, EVO.... you name it, I've had it.