Database Users

[Q] Stock 4.3, KNOX and rooting

Alright, where to begin.
I've owned quite a few Samsung phones by now and I've rooted every single one of them and installed custom recovery and ROMs. But with KNOX on the S4 this has made me unsure...
What will happen to my device when I root it now? I figure it'll trigger the Knox flag to 0x1. What are the drawbacks of that? Will it affect the function of my device?
And is the rooting procedure done as usual with Odin like on the S3?
And maybe most of all, is it worth rooting the S4 and installing custom ROMs?
Many questions, but I haven't found any real answers to any of them...

Nothing will happen to your device when counter z 0×1
Drawback z you'll void ur warranty & youll not get official updates if u r on I9500.If ur on I9505 then triangle away can solve both problems.No function gets hampers until you really mess with ur phone but that's after root
Yes the procedure z same
Well if ur on I9500 then there r only customised stock version nothing much only debloated or deodexed.If ur on I9505 then definitely worth it
Sent from my GT-I9500 using XDA Premium 4 mobile app

Triangle away dont do much with the knox . Once trigger there is no way at the moment to reset this.

hjertis said:
Alright, where to begin.
I've owned quite a few Samsung phones by now and I've rooted every single one of them and installed custom recovery and ROMs. But with KNOX on the S4 this has made me unsure...
What will happen to my device when I root it now? I figure it'll trigger the Knox flag to 0x1. What are the drawbacks of that? Will it affect the function of my device?
And is the rooting procedure done as usual with Odin like on the S3?
And maybe most of all, is it worth rooting the S4 and installing custom ROMs?
Many questions, but I haven't found any real answers to any of them...
Click to expand...
Click to collapse
What happens when you actually get Knox flagged to 0x1?
You basically lose the ability to install Knox softwares, and your device will be flagged as 'insecure', which means if your company allows employees to bring their own device to work for accessing corporate emails etc and they use knox to keep security, your device will not allow this. However, you will still have the ability to use future samsung firmware releases even though you have the knox flagged.
How do you trigger Knox?
You still can root your phone with CFautoroot, but that will trigger knox to flagged to 0x1. If you try to downgrade your firmware, knox will also trigger to 0x1, therefore, once you upgrade to new bootloader, there is no way to go back to old bootloader without knox. (I would suggest if you do not want knox, but you want the new firmware, you've got to manually flash the modem.bin files using Odin)
Lastly, there is still a big question mark as to whether Samsung will actually service devices with knox 0x1

kenshi08 said:
What happens when you actually get Knox flagged to 0x1?
You basically lose the ability to install Knox softwares, and your device will be flagged as 'insecure', which means if your company allows employees to bring their own device to work for accessing corporate emails etc and they use knox to keep security, your device will not allow this. However, you will still have the ability to use future samsung firmware releases even though you have the knox flagged.
How do you trigger Knox?
You still can root your phone with CFautoroot, but that will trigger knox to flagged to 0x1. If you try to downgrade your firmware, knox will also trigger to 0x1, therefore, once you upgrade to new bootloader, there is no way to go back to old bootloader without knox. (I would suggest if you do not want knox, but you want the new firmware, you've got to manually flash the modem.bin files using Odin)
Lastly, there is still a big question mark as to whether Samsung will actually service devices with knox 0x1
Click to expand...
Click to collapse
I agree with you except last words. Modem has nothing to do with knox... flashing a different modem version from rest of FW version (ROM and CSC) will probably give some data or voice problems, and he will still have the same android 4.2.2 version....
What I suggest if he wants last FW, is just flash it, root it, delete all knox files, assume he will have knox bit activated, and enjoy it.

[Q] i9505 "clean" stock Android

Hello guys,
I’m aware this has been discussed many times before, but this information is "old" most of the times. My Galaxy S4 (i9505) is now running stock Touchwiz Android 4.3 (i9505XXUEMJ7).
What I want to do is the following: flash my phone to a i9505G, but with some research I've found that that isn't possible. Are there any other ways to get the clean i9505G 4.4.2 ROM without any changes (like root) on my i9505? (I know there are much custom ROM's, but if possible I'd like to keep it "stock".)
Since I'm running 4.3 with Knox I'm a little scared about the Knox 0x1 status, is this already "resolved" or will this still be a problem?
Thanks.

Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.

tsphere said:
Broodplank's AOSP rom is the way to go:
http://forum.xda-developers.com/showthread.php?t=2397511
You still need to flash a custom recovery to flash it, though. I recommend CWM. Simply works.
Click to expand...
Click to collapse
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?

As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...

tsphere said:
As far as i seen, once you flash something with odin, your knox flag gets changed. However it's not clear to me whether it changes the warranty actually...
Click to expand...
Click to collapse
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?

JoeyLe said:
Thanks for your reply. Rooting and flashing a custom recovery shouldn't be a problem, however I'm still a little worried about Knox, there simply isn't a way to reset it after it goes to 0x1?
The HTC One can be "changed" into a HTC One Google Edition: http://forum.xda-developers.com/showthread.php?t=2358781
But as far as I can tell this isn't possible for the Galaxy S4?
Click to expand...
Click to collapse
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832

JoeyLe said:
It's not just the warrenty I'm worried about. If I want to sell the phone later I want it to be fully working, I assume with Knox 0x1 Knox isn't working anymore?
Click to expand...
Click to collapse
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE

dclarkg said:
In theory every non G device can be converted into a G device if the hardware model is the same but in practice is not always accomplished 100%. The problem here is Knox, for waht I understand it has 2 layers: The knox bloatware that comes stock on sammys ROM and the off rom portion included in the bootloader. The bootloader is basically what the system loads up first
. so it can't bypassed. So to kkep it simple, if you flash ANYTHING (not sure however if re flashing the stock original ROM activates the flag) on the knox bootloader (AKA: new bootloader) the ''flag'' will change to 0x1, this flag is called eFuse so basically 0x1 means is burned and it can't be changed ANYWAY. If you don't plan to use your phone for work you shouldn't care about the flag.
For more information you can check this thread
http://forum.xda-developers.com/showthread.php?t=2447832
Click to expand...
Click to collapse
Thank you very much! That was very interesting to read. I personally don't care about Knox, all the Samsung bloatware is the main reason I want to have stock Android on my S4.

dandroid13 said:
1. It isn't clear if Knox 0x1 voids warranty or not.
2. If you have Knox 0x1 your phone will work fine, but you won't be able to use Knox security enhancements.
3. You can't convert the 9505 to the 9505G, the Google Play edition has different bootloader, modem and pit partition.
Enviado do meu Xposed Galaxy S4 4G LTE
Click to expand...
Click to collapse
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.

JoeyLe said:
Thanks for the information. I see there are many custom roms which are very close to stock Android, that should be fine as well.
Click to expand...
Click to collapse
Sure, but the 4.4 roms (Google Play) have one main issue, random reboots.

Question about knox/OTA

Hello,
Is it possible to flash a stock firmware with Odin (with stock kernel, unrooted) if the knox flag is 0x1 and still receive OTA-updates? Or is it the knox flag that determines if the phone should receive OTA-updates? The question is because if I want to sell the phone in the future the buyer might want stock with OTA-updates...

ozzalbatrozz said:
Hello,
Is it possible to flash a stock firmware with Odin (with stock kernel, unrooted) if the knox flag is 0x1 and still receive OTA-updates? Or is it the knox flag that determines if the phone should receive OTA-updates? The question is because if I want to sell the phone in the future the buyer might want stock with OTA-updates...
Click to expand...
Click to collapse
yes in short you can

For clearification and my own understanding: if the Knox flag is tripped you can still flash and use stock firmware (with the side effect that it disables Knox functionality and removes Samsung warranty coverage) but it can still receive pushed ota updates and those updates will work properly (assuming with the exception of Knox functionality). Is this the entirety of the effects of tripping the Knox efuse?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

cpgeek said:
For clearification and my own understanding: if the Knox flag is tripped you can still flash and use stock firmware (with the side effect that it disables Knox functionality and removes Samsung warranty coverage) but it can still receive pushed ota updates and those updates will work properly (assuming with the exception of Knox functionality). Is this the entirety of the effects of tripping the Knox efuse?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
yes just voids Samsung warranty thats about it:silly:

jaythenut said:
yes just voids Samsung warranty thats about it:silly:
Click to expand...
Click to collapse
Then may I ask why everyone is making a huge deal about it? Most (all?) manufactures state that you void your warranty when you flash non stock firmware. I'd bet if I submitted my original galaxy note to Samsung for warranty repair that they'd see the bootloader flag set as custom rom and not touch it... So what is it really that you lose by blowing Knox that you didn't lose when you flash custom firmware on any other device that is making people super angry?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

cpgeek said:
Then may I ask why everyone is making a huge deal about it? Most (all?) manufactures state that you void your warranty when you flash non stock firmware. I'd bet if I submitted my original galaxy note to Samsung for warranty repair that they'd see the bootloader flag set as custom rom and not touch it... So what is it really that you lose by blowing Knox that you didn't lose when you flash custom firmware on any other device that is making people super angry?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
The argument is, We own the device therefore swapping out software shouldn't affect any hardware issues. Samsung don't have the best quality control and things are faulty sometimes.. why should you be penalized if your volume button breaks or screen breaks due to fault, and they won't fix it because you rooted to add a nice clean theme to your device?
Then there is the underlying security issue surrounding KNOX.. is it a spy tool? is it not? who knows?
- Best answer I could give you there lol -

Hi guys,
first of all im sorry about my english... It's not very well :angel:
You say that its possible to do OTA-Updates although the KNOX flag is 0x1... But a few days ago i had a message like "This device is not original/Is touched - no updates available"...
Was it a temporary problem or what is it?
Greetings

shinchillahh said:
Hi guys,
first of all im sorry about my english... It's not very well :angel:
You say that its possible to do OTA-Updates although the KNOX flag is 0x1... But a few days ago i had a message like "This device is not original/Is touched - no updates available"...
Was it a temporary problem or what is it?
Greetings
Click to expand...
Click to collapse
it means your system partition has been modified.
did you root the phone?

vndnguyen said:
it means your system partition has been modified.
did you root the phone?
Click to expand...
Click to collapse
Aaaah okay, yes i did a root! SO when i flash a STOCK ROM without a root it should be fine? And when Android 4.4 is released i am just able to update it OTA???

shinchillahh said:
Aaaah okay, yes i did a root! SO when i flash a STOCK ROM without a root it should be fine? And when Android 4.4 is released i am just able to update it OTA???
Click to expand...
Click to collapse
you can anyway update OTA while keeping root.
Read this: http://forum.xda-developers.com/showthread.php?t=2519103

Thank u sooo much!

Un-Root S5 GM-900F with Odin

Hi,
Its been a few years since ive Rooted or been ontop of the forums ect.
Just wanted to let other people know my experience with Un-Rooting my S5 GM-900F
- Rooted with Odin + tar file
- Un-Rooted with Super SU
- Typically their is now an update available but cannot update as Samsung recognise that the phone was previously rooted.
- On a PC or Mac download Kies and update.
- Nothing has flagged up with any counters, did not experience any problems with KNOX
Hope this helps everyone.

MaxiBizzle said:
Hi,
Its been a few years since ive Rooted or been ontop of the forums ect.
Just wanted to let other people know my experience with Un-Rooting my S5 GM-900F
- Rooted with Odin + tar file
- Un-Rooted with Super SU
- Typically their is now an update available but cannot update as Samsung recognise that the phone was previously rooted.
- On a PC or Mac download Kies and update.
- Nothing has flagged up with any counters, did not experience any problems with KNOX
Hope this helps everyone.
Click to expand...
Click to collapse
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm

castillofr said:
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
Click to expand...
Click to collapse
Not true, KNOX will still say 0x1 after unrooting, he probably means the system status and binaries are reset to Official again.

castillofr said:
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
Click to expand...
Click to collapse
Hi,
Well the uninstall of SuperSU went ahead with no problems, a box did flag up saying something about would you like to disable KNOX before continuing and just confirmed it.
Since the Un-Root, i have just opened KNOX again and havent had any problems at all. I did complete a factory reset just for my OCD needs with it and nothing has been triggered and no flags or counters. Still have the KNOX app with the set up wizard client available to get it going if i ever need it again so..
Didnt realise that people where having a problem with KNOX if im honest, when i finish work i shall have a play around with it and update this if i encounter any problems.

gee2012 said:
Not true, KNOX will still say 0x1 after unrooting, he probably means the system status and binaries are reset to Official again.
Click to expand...
Click to collapse
This might well be the case, i dont fully understand all of the tech terms regarding the binaries but only have a little knowledge when it comes to checking the counters and any flags or problems.
- Say for example that KNOX was tripped, a) What would happen and when/where would i encounter a problem and b) Is their any detrimental effect on the overall phone or just for KNOX?
Regards.

MaxiBizzle said:
This might well be the case, i dont fully understand all of the tech terms regarding the binaries but only have a little knowledge when it comes to checking the counters and any flags or problems.
- Say for example that KNOX was tripped, a) What would happen and when/where would i encounter a problem and b) Is their any detrimental effect on the overall phone or just for KNOX?
Regards.
Click to expand...
Click to collapse
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1 and you are rooted. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again after you flashed a stock rom.

gaudent 206854
gee2012 said:
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again if you flashed a stock rom.
Click to expand...
Click to collapse
Hi,
Well KNOX is working as it did the first day i got the S5 and havent encountered any problems nor seen any flags. IF their were to be a void flag 0x1 where would i see this?
I was just nosing around on the forums and saw that alot of people were Un-Rooting via SuperSU and then using Kies to then boot the stock rom.
Thanks for your help and advice. Sorry this seemed like a dud thread!

MaxiBizzle said:
Hi,
Well KNOX is working as it did the first day i got the S5 and havent encountered any problems nor seen any flags. IF their were to be a void flag 0x1 where would i see this?
I was just nosing around on the forums and saw that alot of people were Un-Rooting via SuperSU and then using Kies to then boot the stock rom.
Thanks for your help and advice. Sorry this seemed like a dud thread!
Click to expand...
Click to collapse
KNOX is only tripped intentionaly (not by accident), that is if you root with CF Auto Root or flash a custom recovery or kernel with (Mobile) Odin.

kararye and
gee2012 said:
KNOX is only tripped intentionaly (not by accident), that is if you root with CF Auto Root or flash a custom recovery or kernel with (Mobile) Odin.
Click to expand...
Click to collapse
Ok no worries. Completed the Root with Odin v3.09 i believe, did not flash any custom roms or anything was just playing around with xposed installer, Mobile Odin was never used.
Not sure if that makes any difference?

MaxiBizzle said:
Ok no worries. Completed the Root with Odin v3.09 i believe, did not flash any custom roms or anything was just playing around with xposed installer, Mobile Odin was never used.
Not sure if that makes any difference?
Click to expand...
Click to collapse
What what software did you root with Odin? If you used CF Root your flag is 0x1.

gee2012 said:
What what software did you root with Odin? If you used CF Root your flag is 0x1.
Click to expand...
Click to collapse
Hi,
Oh right i see what you mean now, sorry for the delay. It was CF-Root

MaxiBizzle said:
Hi,
Oh right i see what you mean now, sorry for the delay. It was CF-Root
Click to expand...
Click to collapse
As you live in the EU warranty for the device is still valid when rooted/tripped KNOX unless the manufacturer can prove the issue is caused by rooting.

gee2012 said:
As you live in the EU warranty for the device is still valid when rooted/tripped KNOX unless the manufacturer can prove the issue is caused by rooting.
Click to expand...
Click to collapse
Hi,
Oh right i didnt know that. Is it just within the EU that the warranty is still valid? Are their any other countries that are the same?
Just a general question then, with regarding the voidance of KNOX or anything, would that only effect me if i wanted to send the phone back for whatever reason? The counters for example wouldnt made a difference for my phone and daily useage anyway so if i just keep the phone and continue to not having any problems i could have as many counters on it as possible?
Just getting my head around the whole void/counters thing.

MaxiBizzle said:
Hi,
Oh right i didnt know that. Is it just within the EU that the warranty is still valid? Are their any other countries that are the same?
Just a general question then, with regarding the voidance of KNOX or anything, would that only effect me if i wanted to send the phone back for whatever reason? The counters for example wouldnt made a difference for my phone and daily useage anyway so if i just keep the phone and continue to not having any problems i could have as many counters on it as possible?
Just getting my head around the whole void/counters thing.
Click to expand...
Click to collapse
Afaik only in the EU by EU law wich superceeds OEM terms/conditions.

gee2012 said:
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1 and you are rooted. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again after you flashed a stock rom.
Click to expand...
Click to collapse
I have currently official status but Knox 0x1.
The one & only thing concerned then is warranty. Knox based apps and all others should work as before Knox 0x1.
Hawke84 said: "If the Knox warranty void line says 0x1 then you cannot use knox softwareas your device has been flagged as insecure. By this i mean that if your workplace / company supports bring your own device to work for corporate emails etc and they use knox to keep security your device will not allow this. You are still able to use future samsung firmware releases with the knox flag 0x1. hope this makes sense. sorry for any confusion this has caused!"

Consequences of tripping knox?

Hey,
I've heard that tripping knox might disable the ability to use Samsung Pay in the future.
Do you know any other consequences of tripping knox - like being unable to use the fingerprint scanner or updating OTA on stock rom?

Yes.....OTA will more than likely be broken.
If your employer asks you to bring your device to work, you won't be able to connect to their secure server network.
Samsung *are* using tripped knox to deny warranty repairs....even if the fault is hardware based and couldn't possibly have been caused by modified software. (Some users will say that they have had a repair with tripped knox, but that's down to nothing more than pure luck.....Samsung's official line is that tripping knox WILL void warranty)
There may be other effects from tripping knox that I don't know about....best to see if anybody else answers.
http://i.imgur.com/rVnFwJM.jpg

The S5 won't have Samsung Pay. Not the way the S6 does it. It's missing the MST chip.
Might as well root.

OTA still works after tripping KNOX (Stops working once you root or flash anything custom but starts working again once you're back on stock), I haven't found anything that doesn't work, fingerprint and private mode etc all still work
Haven't used Samsung Pay, possible things like that might stop working, but I have my doubts it breaks anything other than warranty

keithross39 said:
Yes.....OTA will more than likely be broken.
If your employer asks you to bring your device to work, you won't be able to connect to their secure server network.
Samsung *are* using tripped knox to deny warranty repairs....even if the fault is hardware based and couldn't possibly have been caused by modified software. (Some users will say that they have had a repair with tripped knox, but that's down to nothing more than pure luck.....Samsung's official line is that tripping knox WILL void warranty)
There may be other effects from tripping knox that I don't know about....best to see if anybody else answers.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
What do you mean about not being able connecting to a secure server network? I've never heard about that before :/
s3nr1 said:
The S5 won't have Samsung Pay. Not the way the S6 does it. It's missing the MST chip.
Might as well root.
Click to expand...
Click to collapse
Yeah, considering the age of the phone, I'm also thinking about doing it without worrying about those thing - not sure yet though.
*Detection* said:
OTA still works after tripping KNOX (Stops working once you root or flash anything custom but starts working again once you're back on stock), I haven't found anything that doesn't work, fingerprint and private mode etc all still work
Haven't used Samsung Pay, possible things like that might stop working, but I have my doubts it breaks anything other than warranty
Click to expand...
Click to collapse
And you're positve that OTA and all the other stuff still works like if it was 0x0?
Thanks for the answers

Daabeck said:
And you're positve that OTA and all the other stuff still works like if it was 0x0?
Click to expand...
Click to collapse
Of course, that's how I update, I just flash back to stock, and OTA update, then root again
OTA only stops working if it sees you have modified the OS, such as root or adblocking etc, that's why I flash back to stock for the OTA

If you've never heard of a secure server network (also called a 'business enterprise' network) and your employer has never asked you to/will never ask you to bring your device to work, tripping knox is not an issue.....The main thing you have to consider is what if you need a warranty repair?.......
http://i.imgur.com/rVnFwJM.jpg

I will attest to the fact that it does. However if you reflash the factory image no Knox
Sent from my SM-G920P using Tapatalk

p0krf2ce said:
I will attest to the fact that it does. However if you reflash the factory image no Knox
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Do you even understand what KNOX is?
Attest to the fact that it does what?
Flashing stock does NOT reset KNOX

*Detection* said:
Do you even understand what KNOX is?
Attest to the fact that it does what?
Flashing stock does NOT reset KNOX
Click to expand...
Click to collapse
Totally agreed.......
One of the most experienced, highly respected developers on XDA (Chainfire) is of the informed opinion that knox is an eFuse.
As such it CANNOT be reset, and that once tripped, it REMAINS tripped........forever......
http://i.imgur.com/rVnFwJM.jpg

I have tripped KNOX and the finger scanner does not work. Samsung Pay does not work (B.A. at least).
When I fash back to stock counter reads 0x0. Forgive my ignorance of the efuse.
Sent from my SM-G920P using Tapatalk
---------- Post added at 11:47 AM ---------- Previous post was at 11:43 AM ----------
*Detection* said:
Do you even understand what KNOX is?
Attest to the fact that it does what?
Flashing stock does NOT reset KNOX
Click to expand...
Click to collapse
Sent from my SM-G920P using Tapatalk

p0krf2ce said:
I have tripped KNOX and the finger scanner does not work. Samsung Pay does not work (B.A. at least).
When I fash back to stock counter reads 0x0. Forgive my ignorance of the efuse.
Sent from my SM-G920P using Tapatalk
---------- Post added at 11:47 AM ---------- Previous post was at 11:43 AM ----------
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
If it says 0x0, then you never tripped KNOX in the first place
And the fingerprint scanner works fine with tripped KNOX, something else is wrong
Or you don't have an S5

*Detection* said:
If it says 0x0, then you never tripped KNOX in the first place
And the fingerprint scanner works fine with tripped KNOX, something else is wrong
Or you don't have an S5
Click to expand...
Click to collapse
I am using the S6 but have had the S 5 and S 4. I have tripped KNOX using TWRP method purposely. Flashed stock and I read 0x0. Ping-pong works fine. I have soft bricked, bootlooped, ended up with just battery symbol. And stock has always brought me back to life. I am not arguing but as far as the software is concerned it looks like I haven't tripped KNOX. So I must not understand somethong else. I thought the efuse was hardware?
Sent from my SM-G920P using Tapatalk

p0krf2ce said:
I am using the S6 but have had the S 5 and S 4. I have tripped KNOX using TWRP method purposely. Flashed stock and I read 0x0. Ping-pong works fine. I have soft bricked, bootlooped, ended up with just battery symbol. And stock has always brought me back to life. I am not arguing but as far as the software is concerned it looks like I haven't tripped KNOX. So I must not understand somethong else. I thought the efuse was hardware?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
To put it very simply, if you had EVER tripped KNOX on the S5 (Can't speak for other devices) then 1000% you have never ever reset it from 0x1 back to 0x0, guaranteed
KNOX is a hardware eFuse yes, once it burns out, that's it, gone, forever on 0x1
Flashing stock does absolutely nothing to repair KNOX 0x1, nothing, so get that out of your head
Bricking your phone, and recovering it by flashing stock again, has no connection to KNOX 0x1 > 0x0
It's easy as pie to unbrick an S5, it's impossible to reset KNOX 0x1
In fact, last I heard, there was a substantial reward for anyone who managed to reset KNOX back to 0x0

*Detection* said:
To put it very simply, if you had EVER tripped KNOX on the S5 (Can't speak for other devices) then 1000% you have never ever reset it from 0x1 back to 0x0, guaranteed
KNOX is a hardware eFuse yes, once it burns out, that's it, gone, forever on 0x1
Flashing stock does absolutely nothing to repair KNOX 0x1, nothing, so get that out of your head
Bricking your phone, and recovering it by flashing stock again, has no connection to KNOX 0x1 > 0x0
It's easy as pie to unbrick an S5, it's impossible to reset KNOX 0x1
In fact, last I heard, there was a substantial reward for anyone who managed to reset KNOX back to 0x0
Click to expand...
Click to collapse
I have tripped on the s4 variant repeatedly and reset the counter. And if there is a reward I deserve it. Because i have tripped the KNOX counter and reset as many other developers have. Here's a link to a great discussion on XDA about Locke and how to reset the counter if you're worried about your warranty. http://forum.xda-developers.com/showthread.php?t=2738175
I am not arguing the validity of some efuse but I can make the software say 0x0 after 0x1.
Sent from my SM-G920P using Tapatalk

No you can't, not on the S5, which is the forum you are in right now, while talking about S6 and S4s....
If you do not own the S5, leave
You deserve nothing other than being put on iggy tbh
Read the thread you just linked to, all of it, show me the part that has the tutorial on resetting the S5 KNOX eFuse...
Go away troll
In fact, make an uncut video, showing the S5 with 0x1, and show how you reset it back to 0x0 - go ahead

Here's Chainfire's Google+ blog for additional info.......
https://plus.google.com/+Chainfire/posts/LCfF5A9fsTG
http://i.imgur.com/rVnFwJM.jpg

Wow, people nowadays, somehow lollipop managed to bring on such ignorance, he just doesn't understand.

Frost009 said:
Wow, people nowadays, somehow lollipop managed to bring on such ignorance, he just doesn't understand.
Click to expand...
Click to collapse
Um excuse me? Who EXACTLY are you calling ignorant? Chainfire by any chance?
If it is.....YOU stand to be corrected, as he KNOWS and UNDERSTANDS a damn sight more about android than 95% of members on here EVER WILL......including you or me.
http://i.imgur.com/rVnFwJM.jpg

I read it as him talking about "p0krf2ce" - at least I hope he was
EDIT -After reading some other of his posts, I'm beginning to wonder...