[Sprint Samsung Galaxy S III] easyrider77:
Not sure....but to my understanding it has to be at least MG2, the rest below that are ICS, MG2 is a JB bootloader......that would explain why I can't install KK at all from MD7 if that's the case and I'm still somehow on the MD7 bootloader.....at any rate I'm in the process of downloading a MD7 stock un-rooted rom w/stock recovery, so I can accept the OTA.

As for the knox it doesn't affect the phone physically, it just triggers a counter of sorts.....and it's a perm thing. Can't revert back once it's tripped, can't even revert it back via triangle away.

It was implemented by Samsung for a secuirty purpose and angle of it....so companies that use the knox protocol can securely use knox when they are at work. It is also a trigger for repair shops and Samsung to tell if you have rooted or modified the bootloader in ANY way, because once you do, it trips it and cannot be undone.

Companies have what they call BYOD (bring your own device) where say I can bring my phone, use it at work but here's the catch.....if my phone has knox bootloader baked in, and I trip it, the phone cannot ever be used with any knox protocol again.

Outside that yes it's fine and the phone does work fine other than that also....it just 1: voids your warranty or any hopes of repair if anything goes wrong if they so choose to refuse it and 2: you cannot use it with a company using knox protocol. For the average joe that will never see knox protocol, and doesn't care about voiding the warranty at all, it's plenty fine...root away, but if your concerned about warranty at all, well you have to make a choice.

Here is an example, you buy a sprint s3, and say root it a week later and trip knox......as long as nothing goes physically wrong with the phone, your just fine, but if something goes wrong within the 2 year contract, and you decide you want to take it in for repair, you better hope the tech ins't wise to knox trigger or that sprint will be lenient about the void warranty part, because by all rights, they can and have been know to refuse service. It's not hard to check if it's been triggered either, it's as simple as booting to download mode, and seeing the 0x1 (in normal state is it 0x0) line, that immediately tells the tech or whoever the phones been compromised IE: rooting, and they have the options to "just say no"

To date there is NO fix or workaround of resetting the knox counter once it has been triggered, well at least that can be readily available to everyone. I did read that one person went into a store and the tech was nice enough and said nah don't worry about it...took the phone in the back, reset it back to 0x0 and gave him back the phone.

This tells people and devs that it's somehow software related it seems.....so I'm sure they'll find a fix some time soon, I think they are really close to that. As for now though there isn't a fix...aside from the so called magic reset box the tech used :).

This being said, I think boost is a bit less lenient in this nature,so tripping the knox flag and boost will more than likely say NOPE sorry sucker, or at best send it to Samsung, in which case I'm almost positive they would refuse to fix it.

This is why I say I am going to be holding off for at least a month to see how the hardware holds up, make sure nothing is defective at all before I trip the knox.

If I recall too, once you trigger knox, you can't revert back to 4.1.2 android, your stuck on that bootloader or higher.

And there you have fairly simple explanation of knox :)....I've done some reading and done my homework heh