Develop Bugs

[Q] To root or not Android 4.3 Knox

I have downloaded everything necessary to root my Note 2 but what is this Knox issue that most seems to be facing from what i have read? Can someone tell me if it really is safe to go ahead and root? I am mighty confused.

nascarlam said:
I have downloaded everything necessary to root my Note 2 but what is this Knox issue that most seems to be facing from what i have read? Can someone tell me if it really is safe to go ahead and root? I am mighty confused.
Click to expand...
Click to collapse
No reason to be confused, if you flash 4.3 and then flash custom recovery or root, you will get Knox warranty void, end of
You want 4.3 without Knox, flash this

(InsertNameHere) said:
No reason to be confused, if you flash 4.3 and then flash custom recovery or root, you will get Knox warranty void, end of
You want 4.3 without Knox, flash this
Click to expand...
Click to collapse
Thanks man. Already flashed the official FW via odin. Anyways i guess am just going to go ahead and flash it. Already out of warranty and haven't extended the warranty. Fingers crossed.

nascarlam said:
Thanks man. Already flashed the official FW via odin. Anyways i guess am just going to go ahead and flash it. Already out of warranty and haven't extended the warranty. Fingers crossed.
Click to expand...
Click to collapse
Sorry to hear that, hit the thanks button if it was helpful in anyway.

[Q] How does Rooting affect Galaxy S3's Knox Counter?

I've read a little bit about Knox in the last few months, but wanted to make sure I've got everything right, especially since things have probably changed since the early days of Knox.
Here's my situation: I'm running a TMO Galaxy S3 w/ stock recovery. I was using mrRobinson's T999UVDMD5 and foolishly did the TMO update to T999UVUEMJC.
(I thought I'd be able to retain root, but ended up losing root, getting Knox, and a bootloader that won't let me roll back. )
Now my phone locks up during boot. If I'm lucky, it'll boot but locks up nearly immediately after boot.
And this is with stock everything. I've had the phone a year and a half, so it's out of warranty.
So what's Sammy's stance on their update breaking phones out of warranty?
Do they cover that? Can I get a TMO store to put DMD5 back on?
I'm thinking of using the root66 EMJC img. I'm pretty confident that it won't brick the phone, since it'll be the same bootloader I'm currently running.
And I'm not too worried if it trips the Flash Counter (flag, really) since I should be able to clear it.
But what about the Knox counter? Will that get tripped? mrRobinson's post leads me to think that it will.
Any other root options I should consider? (Above all else, I'd like to be able to restore back to stock if I need to.)
I kinda like the stock ROM (save for some bloatware) and TouchWiz doesn't bother me.

If it's out of warranty, it shouldn't matter if you trip the Knox counter, Should it? Some say as long as you don't install a custom recovery that if you do the root 66 method just for root that Knox doesn't trip. But I can never get anyone to confirm that.
Sent from my SGH-T999L using xda app-developers app

masondoctorjt said:
If it's out of warranty, it shouldn't matter if you trip the Knox counter, Should it? Some say as long as you don't install a custom recovery that if you do the root 66 method just for root that Knox doesn't trip. But I can never get anyone to confirm that.
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
Thanks masondoctorjt! That's one of my questions. (albeit, a lesser one)
If TMO/Sammy's update f'd up my phone will they cover it if it's out of warranty? especially when it was fine before?
(It's also a work phone, so I'd like to be able to return it like I got it, if need be.)
It's that confirmation I'm looking for here.
This Knox thread seems to state that as long as a Knox-enabled bootloader is used, the counter won't trip. But it also says flashing Knox-enabled fw via Odin trips the Knox counter too. (which I don't fully believe) Hence my confusion. A lot of contradictory info.
Add to that the loose usage of 'flash counter' to refer to both the triangle/flash counter/flag and the Knox counter/flag and you can see why my head is spinning!
It was tricky for me to see the Knox Counter info for my phone. Recovery and Bootloader mode didn't pop up the screen.
But when I used adb to enter bootloader, I saw the counter info.

So did you root it, and if so, did the trip the knox counter?
Sent from my GT-N8013 using xda app-developers app

No, not yet. I was hoping to hear back from someone who's tried this.
I didn't want to be the first guinea pig.
I'll probably take my phone down to the T-Mobile store this weekend and give them an earful to see if they can roll me back w/o tripping Knox flag and report back.

PhilipJFry said:
No, not yet. I was hoping to hear back from someone who's tried this.
I didn't want to be the first guinea pig.
I'll probably take my phone down to the T-Mobile store this weekend and give them an earful to see if they can roll me back w/o tripping Knox flag and report back.
Click to expand...
Click to collapse
I would be like to hear how you did after going to T-mobile. Thanks.

patcal said:
I would be like to hear how you did after going to T-mobile. Thanks.
Click to expand...
Click to collapse
I honestly don't expect a whole lot from them really. But it's an avenue I have to try.
I'm ultimately going to root this anyway. If TMO can successfully roll me back to T999UVDMD5 completely, I'll just root that and stick till the dust has settled somewhat on Knox.

For Rooting after getting that 4.3 update, the process is pretty simple really. Since you have 4.3, you flash Root66 Via Odin. Or you could flash a custom Recovery via Odin and then flash SuperSU zip via Recovery.
It is my understanding that either one will not trip the Knox Counter. If you wish you can follow this guide.
NOTE - Do not Try to flash Older Root66 versions. You can only flash UVUEMJC version. If you flash any other version even accidentally then you will get expensive paperweight.

patcal said:
I would be like to hear how you did after going to T-mobile. Thanks.
Click to expand...
Click to collapse
It was ultimately unproductive.
I went in and explained the situation (w/ less detail) and asked them to roll me back to UVDMD5.
They said Samsung doesn't let them roll back, so he then proceeded to recover my phone.
He booted into recovery and wiped cache. When that proved unsuccessful, he wiped data. (nothing I couldn't have done)
Wiping data ultimately made the phone usable again. He then proceeded to enter some short codes to bind me to the network quicker.
(all he mentioned was #NUM#)
So I'm back to stock (more or less ). Not sure when I'll root now.
Perseus71 said:
For Rooting after getting that 4.3 update, the process is pretty simple really. Since you have 4.3, you flash Root66 Via Odin. Or you could flash a custom Recovery via Odin and then flash SuperSU zip via Recovery.
It is my understanding that either one will not trip the Knox Counter. If you wish you can follow this guide.
NOTE - Do not Try to flash Older Root66 versions. You can only flash UVUEMJC version. If you flash any other version even accidentally then you will get expensive paperweight.
Click to expand...
Click to collapse
From what I've read, the custom recovery should trip Knox. Have you tried this yourself?
I'm fairly confident if I merely flash root66 that it won't trip Knox. But I'd like better than a 51% confidence interval, that's all.
(Again, it's a work phone and I'd like to return it as I got it.)

It will trip that previous counter bit. Don't think it will trip the Knox counter.
No I do not have the Knox Counter.

PhilipJFry said:
It was ultimately unproductive.
I went in and explained the situation (w/ less detail) and asked them to roll me back to UVDMD5.
They said Samsung doesn't let them roll back, so he then proceeded to recover my phone.
He booted into recovery and wiped cache. When that proved unsuccessful, he wiped data. (nothing I couldn't have done)
Wiping data ultimately made the phone usable again. He then proceeded to enter some short codes to bind me to the network quicker.
(all he mentioned was #NUM#)
So I'm back to stock (more or less ). Not sure when I'll root now.
From what I've read, the custom recovery should trip Knox. Have you tried this yourself?
I'm fairly confident if I merely flash root66 that it won't trip Knox. But I'd like better than a 51% confidence interval, that's all.
(Again, it's a work phone and I'd like to return it as I got it.)
Click to expand...
Click to collapse
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat

patcal said:
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat
Click to expand...
Click to collapse
Was that the Flash Counter or Knox Counter?

Perseus71 said:
Was that the Flash Counter or Knox Counter?
Click to expand...
Click to collapse
Well I reset the flash counter with Triangle away. The Knox counter was not tripped until I flashed the recovery.
Pat

patcal said:
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat
Click to expand...
Click to collapse
Pat,
So just to get this straight, you flashed the stock TMO update, so you were not rooted?
Or did you do a root-injected variant of the stock?
Either way, I'm surprised you tripped the (triangle) flash counter.
But I'm more worried about the Knox counter; not worried about the other since there is Triangle Away.

patcal said:
Well I reset the flash counter with Triangle away. The Knox counter was not tripped until I flashed the recovery.
Pat
Click to expand...
Click to collapse
Thanks for letting me know.

PhilipJFry said:
Pat,
So just to get this straight, you flashed the stock TMO update, so you were not rooted?
Or did you do a root-injected variant of the stock?
Either way, I'm surprised you tripped the (triangle) flash counter.
But I'm more worried about the Knox counter; not worried about the other since there is Triangle Away.
Click to expand...
Click to collapse
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.

patcal said:
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
Click to expand...
Click to collapse
The Flash Counter (Triangle away kind) will trip due to the running tracer (read Sysscope) in that Rom. I'd not worry about it as Triangle away will take care of it. Yes it trips due to custom Recovery and Root.

Perseus71 said:
The Flash Counter (Triangle away kind) will trip due to the running tracer (read Sysscope) in that Rom. I'd not worry about it as Triangle away will take care of it. Yes it trips due to custom Recovery and Root.
Click to expand...
Click to collapse
Thanks for that Perseus71. Didn't know about Sysscope before, but sounds interesting. I figured root66 removed it, since mrRobinson claims that it doesn't trip the normal flash counter. And this matches my experience w/ his previous root66.
patcal said:
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
Click to expand...
Click to collapse
So it sounds like you were able to flash a rooted ROM and not affect Knox, as long as you leave the stock recovery.
That was my plan anyway. I'll probably look into this later this week.

PhilipJFry said:
Thanks for that Perseus71. Didn't know about Sysscope before, but sounds interesting. I figured root66 removed it, since mrRobinson claims that it doesn't trip the normal flash counter. And this matches my experience w/ his previous root66.
So it sounds like you were able to flash a rooted ROM and not affect Knox, as long as you leave the stock recovery.
That was my plan anyway. I'll probably look into this later this week.
Click to expand...
Click to collapse
Yep. Let us know how it goes.

FYI, the Knox counter gets tripped.
I flashed the root66 T999UVUEMJC via Odin. That's it.
Oh, and the flash counter does not get set.

[Q] Successfully Rooted with Towelroot on Note 3(SM-N900T), have some questions...

Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!

Steameffekt said:
Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!
Click to expand...
Click to collapse
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk

effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
If I flashed back to stock, did a factory reset, would it still say custom?

Steameffekt said:
If I flashed back to stock, did a factory reset, would it still say custom?
Click to expand...
Click to collapse
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk

effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
effortless said:
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Makes sense and I probably will flash a custom recovery. I just don't understand the fuss with people wanting not to trip knox if they're not even gonna use it.

I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?

un-answered question............
I don't know why I have not asked this before, but here it goes..........
First, I just want to say that I could care less about Knox...
(my phone already has the knox pox)
But for future reference if I had a brand new Note 3 with official stock NB4 baseband
and I rooted it successfully using Towelroot (or root de la vaga) would it be possible
to simply rename a custom rom like Hyperdrive to "update.zip" and copy it to the
internal sdcard then boot into the stock NB4 recovery and flash/install "update.zip"?
If the only problem with this method would be the fact that a different kernel would
also flashed along with the rom it would be an easy fix by just removing the kernel
from the custom rom file before flashing the update.zip?
I know that more likely than not this method would not work.
But if it did work it should not trip the knox right?

Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
Sent from my SM-N900T using xda premium

re: modile odin - knox
Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible". Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!

Misterjunky said:
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!
Click to expand...
Click to collapse
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?

re: knox - mobile odin
Eudeferrer said:
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?
Click to expand...
Click to collapse
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!

Misterjunky said:
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!
Click to expand...
Click to collapse
My bad. I guess I misunderstood you the first time. Thank you for your response.

HELP! sisters phone wont booy into the stock recovery.

(Without voiding knox) She has a completly stock 4.4.2 tmobile s4. She wants to update to 4.4.4. While trying to reset with triangle away i noticed i couldnt boot her recovery. Download mode works fine though. So what can i do? Push a stock recovery to her phone? Factory reset within the phone? Odin the new offical firmware without voiding knox? Help!

Delete

Delete

Download stock 4.4.4 firmware and flash with Odin and recovery would probably be fixed.. Easy way to take care of both problems

We need more info. It would help if you could post a picture of your sister.

Wouldnt knox get flagged serio22? And hilarious ultra ha

So I renamed and pushed the stock recovery.img from NB4 and everyhing seems to be working and knox is still 0x0. Ha good stuff.

Ok so i just odin'd the NB4 firmware and everything worked and knox is fine. Ill just have her OTA NH7. Love how on google its a 50/50 on flashing official firmware. Well anyway thanks guys and hopefully this helps people with knox. Glad I dont have it haha p.s. NH7 modem seems alright on MDL....so far so good.

Yeah the only way Knox will trip is if you flash custom recovery or kernel

Thats what i figured but damn goohl got me mixed up. Thanks again

serio22 said:
Yeah the only way Knox will trip is if you flash custom recovery or kernel
Click to expand...
Click to collapse
Why is tripping Knox bad? what happens?

Enathe said:
Why is tripping Knox bad? what happens?
Click to expand...
Click to collapse
Its not that bad as everyone makes it seems, but read this for more info http://forum.xda-developers.com/showthread.php?t=2823816

serio22 said:
Its not that bad as everyone makes it seems, but read this for more info http://forum.xda-developers.com/showthread.php?t=2823816
Click to expand...
Click to collapse
Awesome, thanks!

[Q/A] Answers Added - OTA's/Updates, rooting & tripping Knox? - other questions

So I rooted using chainfires method for my Tab S 8.4 wifi (T700) and it tripped Knox (0x1). I know there is no way to currently reset it and there is a bounty out for it. No big deal on tripping it, I wanted to root anyways and want to try out CM12 eventually. After doing some research it appears Knox gets tripped when unofficial firmware or recoveries get flashed via Odin. Knox is not tripped when you flash official Samsung firmware. I had a few questions though I can't seem to get a clear answer on and was hoping to find some or get a discussion going at least about Knox for the Tab S.
Questions and Answers
- Are you still able to receive OTA updates on a stock rooted rom/recovery with Knox tripped?
A: No, not while rooted, "Operating System on your device has been modified in an unauthorized way. Try downloading software updates using Samsung Kies on your PC" Unsure if Knox prevents it but most likely does not.
- Will you lose root if you can get OTA updates?
A: No OTA Updates allowed on rooted devices. Reports have stated that flashing the official firmware update via odin will unroot the device but maintain data, most likely kies is the same when updating. However if a bootloop occurs after flashing, you may need to wipe data and cache via stock recovery.
- If knox is tripped (0x1), if I flash a custom recovery (TWRP/CWM) or use chainfires method to root again will it trip Knox again (0x2)?
A: YES & NO, Knox will not read (0x2) if unofficial img's are flashed via Odin but reports on other devices have stated it will read {0x1(2)}
- If yes can you trip Knox too many times, rendering device inoperable or bricked?
A: NO, tripping Knox only informs if warranty has been voided by flashing unofficial firmware/recovery/img files and root kernals via Odin. When the knox warranty void status is tripped, the knox software will no longer work.
- What is tripped specifically in Knox (for the Galaxy Tab S), an efuse, or is it software or binary code?
A: Most likely an eFuse. There is no way to reset the flag counter as it is believed to be an eFuse that once gets blown it stays damaged and cannot be reset.
***New Questions***
- Will flashing a custom recovery img (TWRP/CWM) via ADB trip Knox (0x1)?
A: Yes, it will trip Knox.
Thanks to all who answer and contribute.
If there are any new questions, updates to be added or wrong information to be corrected please let me know.

No OTAs when you are rooted on custom rom. Dont worry, someone will make a stock custom rom to flash with twrp Or you can odin flash stock lollipop and root with twrp
If you do the ota it will probably not install because of root.
If you flash a custom recovery, or root again.. Knox will stay 0x1. It wont change.
Knox is like a check when booting up your device. Its more like uhh protection. If you install custom stuff then you dont get protection. Knox was a security feature that samsung included. Its really not needed as it really doesnt work. Thats why people trip it. I highly doubt its used for security but I think its just used to detect if warranty has been void or not. Its not something that you should worry.
Hope this helps!

DUHAsianSKILLZ said:
No OTAs when you are rooted on custom rom. Dont worry, someone will make a stock custom rom to flash with twrp Or you can odin flash stock lollipop and root with twrp
If you do the ota it will probably not install because of root.
If you flash a custom recovery, or root again.. Knox will stay 0x1. It wont change.
Knox is like a check when booting up your device. Its more like uhh protection. If you install custom stuff then you dont get protection. Knox was a security feature that samsung included. Its really not needed as it really doesnt work. Thats why people trip it. I highly doubt its used for security but I think its just used to detect if warranty has been void or not. Its not something that you should worry.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I figured Knox is nothing more than just a feature to let Tech's know if the warranty had been voided. Also I figure that flashing the updates myself when they come out would be the best option. Thanks again.

how do you make the knoxx counter back to zero ??
methslushee said:
Thanks, I figured Knox is nothing more than just a feature to let Tech's know if the warranty had been voided. Also I figure that flashing the updates myself when they come out would be the best option. Thanks again.
Click to expand...
Click to collapse
is there a limit to knox number and how can it be made to zero again to retain warranty

[email protected] said:
is there a limit to knox number and how can it be made to zero again to retain warranty
Click to expand...
Click to collapse
Read post two above yours. It can not be reset to zero once it's tripped.

Even if you root and trip knox, although you cannot receive official ota's, you can still use samsung kies to still recieve the updates.

updated OP with answers to questions.

Stupid Knox. This is one "feature" of Samsung devices which makes me less likely to purchase them in the future.

For the new question, flashing any custom recovery with odin or adb will trip knox. Flashing stock should not trip