Related
Hey,
I wanted to de-brand my phone from carrier's rom, and i put MGA from this forum (pre-rooted version). I didn't know that in two very small OTA's i would update to MH8 since there were no description to any of them, so i'm now on MH8 unfortunatly.
In Download Mode i have official mode, KNOX Warranty Void 0x0 (so i have my warranty still, right?) and now i want to know two things:
1. How can i root it withouth having 0x1 flag or any other problem? Is it even possible?
2. What triggers that KNOX flag? What to avoid etc.? I want to be as cautious as i can so i wont lose my warranty. (at least till somebody figures how to disable/downgrade knox/bootloader).
If you try to root your phone then the knox flag will turn to 0x1. I do not know what triggers this flag. But I saw a post in google+ fron chainfire there is nothing you can do if you want to return your phone in full stock with warranty because of knox flag. I rooted my sgs4 and I flashed an aosp custom rom and recovery but now I am in full stock and the knox flag remains 0x1. Triangle away is not a solution for that. Just give developers some time to figure this out.
Sent from my GT-I9505 using xda app-developers app
Yea, i saw same post on his account, just couldn't find any list of things that sets that flag to 0x1. And i do value my warranty more then root a little bit. Good thing is that KNOX is being deployed to more and more roms and phones (not that great for them actually) but this should mean that there will be more devs to look at this problem and there should be fix sooner. Hope some1 will do his magic and be able to reset this, as its just software, i don't belive it can't be cracked.
Thanks for answer!
Guys, I'm on stock 4.2.2 MGG firmware. That's how my devices came out of the box.
I rooted it just out of the box even before I put the screen protector, so now the knox flag is 0x1.
What will happen now? Will I be ever able to update to 4.3? or install ANY custom roms from the devs?
I rad the QA thread about knox, but its really unclear and there's some cross information.
The device is I9505
Thanks in advance.
bidav1 said:
Guys, I'm on stock 4.2.2 MGG firmware. That's how my devices came out of the box.
I rooted it just out of the box even before I put the screen protector, so now the knox flag is 0x1.
What will happen now? Will I be ever able to update to 4.3? or install ANY custom roms from the devs?
I rad the QA thread about knox, but its really unclear and there's some cross information.
The device is I9505
Thanks in advance.
Click to expand...
Click to collapse
The flag won't stop you doing anything with your phone at all, the only difference is that Samsung may now not honour any warranty claims for your handset.
There's also the few issues with root access not working properly with KNOX installed, but that happens with or without the flag being tripped, it's just a feature of KNOW.
Dan1909 said:
The flag won't stop you doing anything with your phone at all, the only difference is that Samsung may now not honour any warranty claims for your handset.
There's also the few issues with root access not working properly with KNOX installed, but that happens with or without the flag being tripped, it's just a feature of KNOW.
Click to expand...
Click to collapse
Dan,
From what I understand I won't be able to downgrade or upgrade to knox enabled firmwares at all since my device is now compromised.. 4.3 HAS knox in it. Am I wrong?
bidav1 said:
Dan,
From what I understand I won't be able to downgrade or upgrade to knox enabled firmwares at all since my device is now compromised.. 4.3 HAS knox in it. Am I wrong?
Click to expand...
Click to collapse
Ah, yes I forgot about that. You won't be able to downgrade (at least not easily) to non-KNOW firmwares. However there's not really any reason to now that you've already tripped the flag, so you're not missing out on anything there.
I think that's all there is, although I could be wrong.
Dan1909 said:
Ah, yes I forgot about that. You won't be able to downgrade (at least not easily) to non-KNOW firmwares. However there's not really any reason to now that you've already tripped the flag, so you're not missing out on anything there.
I think that's all there is, although I could be wrong.
Click to expand...
Click to collapse
Thing is that I'm on 4.2.2 now, and want to UPGRADE to 4.3. but 4.3 is a knox enabled firmware so it seems from what I understand is impossible?
I was also on 4.2.2 with knox status 0x1. I have flashed the leaked 4.3 firmware with knox without any problems so dont worry
Sent from my GT-I9505 using xda app-developers app
Upgrading to a higher fw will always work, even if knox is triggered. Only downgrade won't work or maybe will hardbrick your device.
Sent from my flying Galaxy S4 GT-I9505
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!"
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...
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