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...
Related
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
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.
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!"
Been trying to look for an answer but all related thread seem to talk about KNOX tripped (counter 0x1)... But my case is different here.
I have rooted my S5 G900F with Towelroot without tripping KNOX. Right now the phone is running stock NG2 firmware with root and KNOX disabled (KNOX counter remain 0x0, device status Custom).
Due to work requirement, I need to encrypt my phone, but encryption won't works with KNOX disabled. My question is, is it possible to enable KNOX (while rooted), then go on with encryption and disable KNOX after the encryption. If so, how? What is the effect of having KNOX enabled while remain rooted?
Good question
This question has been asked in the CF-Root thread many times. CF recommends to keep it disabled. Otherwise, the phone will be unstable (autoreboot) and other strange things could happen. Read CF-Root thread for more details.
After some reading, it seems like you can restore KNOX by: unrooting with superSU, flashing a stock rom, and do a data factory reset.
Check this link for more info: http://forum.xda-developers.com/galaxy-s5/help/unroot-rooted-towelroot-sm-g900f-t2804788
Hope this helps.
TheSamWolf said:
After some reading, it seems like you can restore KNOX by: unrooting with superSU, flashing a stock rom, and do a data factory reset.
Hope this helps.
http://forum.xda-developers.com/galaxy-s5/help/unroot-rooted-towelroot-sm-g900f-t2804788
Click to expand...
Click to collapse
The system status and current binaries both have to be showed as official in downloadmode to use KNOX.
Dark_Avenger said:
This question has been asked in the CF-Root thread many times. CF recommends to keep it disabled. Otherwise, the phone will be unstable (autoreboot) and other strange things could happen. Read CF-Root thread for more details.
Click to expand...
Click to collapse
I read that, but I didn't use CF-Root to obtain root (as it well trip KNOX), i used TowelRoot (without tripping KNOX). Don't know if it would behave the same as the CF-Root method.
Thanks for pointing out.
TheSamWolf said:
After some reading, it seems like you can restore KNOX by: unrooting with superSU, flashing a stock rom, and do a data factory reset.
Check this link for more info: http://forum.xda-developers.com/galaxy-s5/help/unroot-rooted-towelroot-sm-g900f-t2804788
Hope this helps.
Click to expand...
Click to collapse
That means I have to unroot it, not exactly what i'm looking for...
AFAIK Knox (the software container) will never ever be enabled when you are rooted (even with Knox counter set to 0x0).
I believe it checks on root access.
As I understand it correctly, the company where you work for only requires that your phone is encrypted and not manageable ?
I work for one of the largest companies in the world and my phone (S3) is not allowed to be rooted.
The container software (Airwatch) checks on that.
When every check is confirmed, only then will it make a container and encrypts the data in that container.
And from administrators it can be managed, like remote wipe, anti-theft, etc
speedme said:
AFAIK Knox (the software container) will never ever be enabled when you are rooted (even with Knox counter set to 0x0).
I believe it checks on root access.
Click to expand...
Click to collapse
That was my understanding too!
To re-enable KNOX, reflash stock firmware as described. After that, you can try again (towel) rooting your device, and Do Not disable KNOX. Though, I read that root will not work quite correctly?
Please write back with your results if you try it!!!
You probably right that Knox won't work when phone is rooted...
Well, with My Knox available now, no full phone encryption is required (as encryption will only be within the Knox container). Maybe one fine day I'll reset my phone, root then unroot temporary in order to try My Knox...
Sent from my SM-G900F using Tapatalk
Hey Guys,
I have a doubt on using KNOX.
Actually I don't care about tripping my Knox Counter. (0x1) but I just require to know whether I can use KNOX just like before rooting without any problems?
If Warranty is the only concern to be worried about , due to rooting of the phone; I can live with it, but does rooting limits/restricts the users from using KNOX and any/all of its functionality totally?
xda rocks said:
Hey Guys,
I have a doubt on using KNOX.
Actually I don't care about tripping my Knox Counter. (0x1) but I just require to know whether I can use KNOX just like before rooting without any problems?
If Warranty is the only concern to be worried about , due to rooting of the phone; I can live with it, but does rooting limits/restricts the users from using KNOX and any/all of its functionality totally?
Click to expand...
Click to collapse
In my experience(for what it's worth, lol), I have seen no performance issues with Knox functionality by rooting. Flashing through Odin trips the warranty counter and voids warranty. There are apps that disable Knox but the ones I've seen warn you before doing so. Hope that helps. Good luck
Sent from my SM-G900P using XDA Free mobile app
xda rocks said:
Hey Guys,
I have a doubt on using KNOX.
Actually I don't care about tripping my Knox Counter. (0x1) but I just require to know whether I can use KNOX just like before rooting without any problems?
If Warranty is the only concern to be worried about , due to rooting of the phone; I can live with it, but does rooting limits/restricts the users from using KNOX and any/all of its functionality totally?
Click to expand...
Click to collapse
You will NEVER be able to use the Knox Container EVER again after ur counter says 0x1... Samsung made it for business enterprises for security concerns, if these *Android Hackers and Modders* will just bypass the Knox security then Samsung wouldn't have business enterprises using the Knox Container because it can just easily be bypassed..
Sent from my SM-G900F using XDA Free mobile app
trettet said:
You will NEVER be able to use the Knox Container EVER again after ur counter says 0x1... Samsung made it for business enterprises for security concerns, if these *Android Hackers and Modders* will just bypass the Knox security then Samsung wouldn't have business enterprises using the Knox Container because it can just easily be bypassed..
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Makes sense...!!! But I see almost everyone requesting to get a root access mentioning about Warranty void. I was wondering if that is the only reason can we use knox even after making our phone warranty void. Anyways I got the idea. :sly:
I need help
please some one .. i need help and it's so important . one of my friend encrypted his data though knox and regardless of what super su and root do with knox and it's disabling knox ... he rooted his phone ! (he is todler and didn't take notice )
anyway his knox now is disabled and he can't access to his data because in security knox is disabled .. how can we enable knox so he can decrypt knox with password and access to his data ... thanks in advance and keep in mind that please guys if you are not sure about how can solve problem without losing data , guide me . data encrypted with knox is so important to him .
target device is Galaxy note 3 n9005 .
You cant use knox on rooted device
When uroot your device, ur device status nd binaries change to custom. KNOX checks that. If the binaries are custom, you cant use KNOX ever.
Is there a way to completely unroot and go back to KNOX 0x0, all official? Even if we pay Samsung service centre?
true sir, my Samsung Galaxy S7 edge unable to even install myknox after flash back to stock rom
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