Database Users

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!

[Q] Bootloader

I am curious what the difference between a dev vzw n3 and a retail with Knox tripped 0x1?
Sent from my SM-N900V using Tapatalk

Imarik81 said:
I am curious what the difference between a dev vzw n3 and a retail with Knox tripped 0x1?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
A retail with Knox tripped means the owner either did some unsupported mod or used an old root method and the warranty is now void. It does not mean the bootloader is unlocked.
A Dev Note 3 has Knox tripped but can be bootloader unlocked.
Don't get a Knox tripped retail.

changt34x said:
A retail with Knox tripped means the owner either did some unsupported mod or used an old root method and the warranty is now void. It does not mean the bootloader is unlocked.
A Dev Note 3 has Knox tripped but can be bootloader unlocked.
Don't get a Knox tripped retail.
Click to expand...
Click to collapse
Not exactly but close...the Dev Note 3 does not have knox tripped out of the box. Once you flash anything custom in odin, then knox is tripped. However that is all irrelevant because there is no warranty anyway aside from a 1 yr on mechanical defects.

droidstyle said:
Not exactly but close...the Dev Note 3 does not have knox tripped out of the box. Once you flash anything custom in odin, then knox is tripped. However that is all irrelevant because there is no warranty anyway aside from a 1 yr on mechanical defects.
Click to expand...
Click to collapse
Well I tripped my Knox. It's not the end of the world. It does stink though. I'm running Eclipse right now but I'd love to check out Cm11. Is that possible?
Sent from my SM-N900V using Tapatalk

@lmarik81 - I think the pointed question you need to ask is:
"Suppose I want to intentionally blow my Knox warranty flag on my retail device - will the retail device become equivalent to a dev device at that time?"
I *think* the answer is "NO - you will still not be able to boot unsigned kernels."
But it would be better if someone with a blown Knox retail device can validate the above with a "yeah, I tried that on my (blown Knox) retail device and it didn't work" ... either that or refute that assertion from contrary experience.
Direct first-person experience is very desirable here.
[Edit] @lmarik81 - mind saying how you blew yours? Flashing the recovery partition, or something else?
.

Is it possible to hard brick my device by doing this? I'm tempted to try if I can just restore back with worst case 0x2.
Sent from my SM-N900V using Tapatalk

I had the case off the back of my phone and some how the battery came out as I was flashing either a rom or recovery and when I turned the phone back on I went into recovery and it tripped.
Sent from my SM-N900V using Tapatalk

If you are rooted you can use the Triangle Away app and reset your counter.. works for me

[Q] What Shall I Do About KNOX?

Hi
My s5 currently is rooted and KNOX is 0x0. I want to flash something more exciting to it but what can I do about KNOX? Can I Remove It Before it is tripped or does it happen no matter what?

Hi - Sorry I don't know the answer to your question but could you share how you managed to root your phone without tripping Knox? All guides / info I have read says Knox will be 0x1 after root and as such I cannot / have not rooted.
Thanks

you cannot remove KNOX.
If you flash anything - KNOX goes to 0x1 making you void your warranty

dieselboy said:
Hi - Sorry I don't know the answer to your question but could you share how you managed to root your phone without tripping Knox? All guides / info I have read says Knox will be 0x1 after root and as such I cannot / have not rooted.
Thanks
Click to expand...
Click to collapse
Visit this thread https://towelroot.com/ on your phone and click the lambda and follow instructions. KNOX will stay on 0x0.

Thanks !
It seems within the last 2 weeks after almost everyone saying "rooting will trip Knox and don't count on anything different any time soon" that rooting now does not trip Knox
Very pleased, I am.
And thanks for the link. Seems not everyone knows about this yet.

KNOX
Understood. But is the warranty that important?

Sure using towelroot to root your device won't trip knox but once you flash a custom recovery so you can use custom roms, kernels etc it will

What happens after you disable KNOX from SuperSU?
I thought that you could do anything you want and KNOX will be 0x0 since it's "disabled".

forsberg78 said:
What happens after you disable KNOX from SuperSU?
I thought that you could do anything you want and KNOX will be 0x0 since it's "disabled".
Click to expand...
Click to collapse
Iirc Knox is implemented in the boot loader which can't be hacked, so Knox will always be there
If you live in Europe, Knox isn't a factor

DSA said:
Iirc Knox is implemented in the boot loader which can't be hacked, so Knox will always be there
If you live in Europe, Knox isn't a factor
Click to expand...
Click to collapse
Quote: `If you live in Europe, Knox isn't a factor`.
Can you explain this a bit more please, or do you mean warranty wise

gee2012 said:
Quote: `If you live in Europe, Knox isn't a factor`.
Can you explain this a bit more please, or do you mean warranty wise
Click to expand...
Click to collapse
Yeah. I Would like this explained. If KNOX isnt a factor in Europe Then Thats A Plus For Me.

Wildey1771 said:
Yeah. I Would like this explained. If KNOX isnt a factor in Europe Then Thats A Plus For Me.
Click to expand...
Click to collapse
They are referring to some regula by EU Laws, which indirectly tells that manufacture cannot deny warranty because of rooting.
At same time, organization in my country responsible about these kind of claims says, they agree on Samsungs warranty paper, which says we are not allowed to root. So If I would want justice in my country, it can be done only by court!
So dont count on EU law helping... may work and may not.

gee2012 said:
Quote: `If you live in Europe, Knox isn't a factor`.
Can you explain this a bit more please, or do you mean warranty wise
Click to expand...
Click to collapse
Warranty...there are laws here that supercede it, but the above post is basically true (although two people I know who had rooted and used the warranty didn't have to go to court)

txr33 said:
Sure using towelroot to root your device won't trip knox but once you flash a custom recovery so you can use custom roms, kernels etc it will
Click to expand...
Click to collapse
Understood.
However in my case all I want to do right now is disable the silly camera shutter sound.

Alright, So Im From The UK. I Want To Get Rid Of Silly Touchwiz which Samsung loves to use. To do so I know I need to flash a different ROM. Doing this will flag KNOX. KNOX being flagged will void warranty. Should I Care About Warranty? Or Should I Flash Away?

Wildey1771 said:
Alright, So Im From The UK. I Want To Get Rid Of Silly Touchwiz which Samsung loves to use. To do so I know I need to flash a different ROM. Doing this will flag KNOX. KNOX being flagged will void warranty. Should I Care About Warranty? Or Should I Flash Away?
Click to expand...
Click to collapse
Not necessarily.. Have you heard of "Themer"? I was running themer on my completely stock Note3. You have a wide selection of touchwiz replacements. Take a looksie.

Knox will be tripped if you load a custom recovery or kernel.
Apart from resale reasons, why is everyone so worried about going 0x1?
Sent from my SM-G900I using XDA Free mobile app

Inm8 said:
Knox will be tripped if you load a custom recovery or kernel.
Apart from resale reasons, why is everyone so worried about going 0x1?
Sent from my SM-G900I using XDA Free mobile app
Click to expand...
Click to collapse
Perhaps because it may void people's phone warranty.

born4trance said:
Perhaps because it may void people's phone warranty.
Click to expand...
Click to collapse
True, didn't think about how many people actually used that.
Sent from my SM-G900I using XDA Free mobile app

Inm8 said:
True, didn't think about how many people actually used that.
Sent from my SM-G900I using XDA Free mobile app
Click to expand...
Click to collapse
Hopefully not many. You'd expect Samsungs warranty return % to be very low. I wonder if there are published figures, but I would hope <0.1% of customers. However, after a few months of using your device you would know if you need to warranty the phone or not. Then I guess you wouldn't mind going 0x1.

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...

Rooting detection for warranty, etc

Hey all, it's been a while since my rooting days but I wanted to check in and ask this: Is there a simple way that the manufacturer can tell if you have rooted the phone? I ask because I'm a verizon employee now and they're more strict than my previous employer was, At&t. I know samsung used to have a counter on some of their devices but wanted to check in with today's current root methods. And if there is a way they can tell, can you reset it to zero after flashing through odin or another method?
TIA!

There is Knox warranty void which is tripped when root and when tripped it's permanent. There is no way to undo it other than changing mainboard.
Knox is an efuse, hardware based thing.
Sent from my SM-A9000 using Tapatalk

But what about the exynos version. is the knox flag still there if you go back to stock?

unrated87 said:
But what about the exynos version. is the knox flag still there if you go back to stock?
Click to expand...
Click to collapse
It is. But it does not have an efuse so could potentially be reversed. However nobody has found a way to do it as of yet.
Sent from my SM-G935F using Tapatalk

everytime you'll flash something, the knox counter will be from 0x0 to 0x1, which means your warranty is void.
Up to now there is no known way to turn it back to 0x0