Database Users

tripped knox flag to 0x1 what now?

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

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

[Q] CWM recovery removal with out tripping Knox Counter??

I recently purchased a SM-N900W8. Love this device, just retired my S2 which i messed around with for a few years and never had issues...
I neglected to do research on XDA (Big mistake) before rooting it and had no idea about the repercussions of this KNOX issue.
I used this method to root it (http://galaxynote3root.com/galaxy-note-3-root/how-to-root-galaxy-note-3/)
I successfully installed CWM recovery and SuperSu and the phone is rooted. I had no intentions of installing Custom Roms just yet just wanted to be able to use some of my favorite apps that require rooting. The phones Current Binary and Phone status have both been tagged custom but my KNOX Warranty Void is still tagged at 0X0. Needless to say maybe I got lucky?
I was hoping to Revert to Stock and Unroot so I could follow this method instead (http://forum.xda-developers.com/showthread.php?t=2498850)
Is there anyways to Accomplish this without tripping the KNOX counter? I've been scouring the forums for several hours trying to find a concrete answer but cannot.
I have downloaded my stock firmware (http://www.sammobile.com/firmwares/3/?download=26653)
Any help or suggestions would be greatly appreciated. I have included a screenshot of my device info. I apologize in advance if this issue has already been addressed.
Thanks,
-Rob

For device info and Knox warranty status, you can use my app Phone INFO ★Samsung★ to get more detailed info.
Download link in my signature.

Why did you even install CWM if you didn't need it ?
Why do you want to remove it ? Don't fix it if it ain't broken. De la vega will trip Knox in 4.4, so leave it as it is.
Sent from my N9005

Dejan Sathanas said:
Why did you even install CWM if you didn't need it ?
Why do you want to remove it ? Don't fix it if it ain't broken. De la vega will trip Knox in 4.4, so leave it as it is.
Sent from my N9005
Click to expand...
Click to collapse
Will do. Was just worried about official updates and warranty if phone still says custom but knox is not tripped. But bell outsources another company for repairs and doesn't send back to Samsung directly so I probably don't need to worry to much..
I used CWM because I've used it for a couple years with my S2 and enjoyed the features so when I saw cwm was avaliable for note 3 I jumped on it.
But there is no way to revert to stock without tripping count?
Thanks.

SSJ3Rob said:
Will do. Was just worried about official updates and warranty if phone still says custom but knox is not tripped. But bell outsources another company for repairs and doesn't send back to Samsung directly so I probably don't need to worry to much..
I used CWM because I've used it for a couple years with my S2 and enjoyed the features so when I saw cwm was avaliable for note 3 I jumped on it.
But there is no way to revert to stock without tripping count?
Thanks.
Click to expand...
Click to collapse
Flashing stock using odin should rever everything back to stock and possibly not trip knox counte, I am saying possibly cuz nobody has tried to flash stock recovery and try to keep knox cool as custom recoveries have tripped everyone's knox AFAIK. But your phone FW or maybe something else might make your device an exception.
Sent From My SM-N9005 To All You Wonder Nobodies!!

Khizar said:
Flashing stock using odin should rever everything back to stock and possibly not trip knox counte, I am saying possibly cuz nobody has tried to flash stock recovery and try to keep knox cool as custom recoveries have tripped everyone's knox AFAIK. But your phone FW or maybe something else might make your device an exception.
Click to expand...
Click to collapse
I will leave as is for now until more info on the subject surfaces. As much as I want to try to flash back to stock recovery and test your theory I will hold out and not mess around with CWM or mess with apps requiring root to much incase it decides to trip the counter.
Thanks.

Root S5 Without Tripping Knox ??

Hi guys
As some of you know I've just bought a S5 and want to root it.
I touched on this in my last thread but thought it was way off topic and that i should start a new thread.
There's plenty of threads about this but they are either old or speak of particular models of s5 or include installing a custom firmware.
What i would like to know (i got there in the end....lol) is there a way to do a root only (without installing custom firmware or recovery) with out tripping knox?
I think I've looked everywhere but cant find any guides.
I'm in the uk and my s5 is the SM-G900F on android 4.4.2.
Also is it worth even trying to root it when 5.0 is just around the corner?

Anyone

http://forum.xda-developers.com/showthread.php?t=2783157
Just install this app, and hit the button! Worked very well for me.

GcDm2010 said:
http://forum.xda-developers.com/showthread.php?t=2783157
Just install this app, and hit the button! Worked very well for me.
Click to expand...
Click to collapse
I didn't think towelroot worked with the latest build of 4.4.2 ?
And doesn't odin now trip knox?

Inked_ said:
I didn't think towelroot worked with the latest build of 4.4.2 ? And doesn't odin now trip knox?
Click to expand...
Click to collapse
Odin has always tripped knox.
Towelroot should work with 4.4.2. is worth a try, the worst thing that could happen is it kills the app and tells you that you've been compromised.

GcDm2010 said:
Odin has always tripped knox.
Towelroot should work with 4.4.2. is worth a try, the worst thing that could happen is it kills the app and tells you that you've been compromised.
Click to expand...
Click to collapse
Thanks for the replies (I thought more people would be replying to this topic....lol)
I read that it was ok to use odin without tripping knox if you flashed an official Samsung firmware.
Ill look into towelroot again
So if it kills the app and says I've been compromised, what do I do then?

It will just try to kill the app. But if that happens, I don't know of any way to get around knox.
And this forum is where experienced people like me just come to raise my post count so I can post where the real action happens.

GcDm2010 said:
It will just try to kill the app. But if that happens, I don't know of any way to get around knox.
Click to expand...
Click to collapse
Ok thanks.
So it wont actually trip knox and I can just reboot the phone to get rid of the message?
GcDm2010 said:
And this forum is where experienced people like me just come to raise my post count so I can post where the real action happens.
Click to expand...
Click to collapse
So where does the real action happen on here ?
Because I've made a few threads on here now but I don't seem to get many replies in any of them

Yeah, just hold the power button to reboot.
The real action here happens in the Unified Development section. Lots of activity going on right now.

My phone has just took the 5.0 update so I guess I've got no chance of rooting it without tripping knox now

Root without tripping knox idea (will not work)

Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As you can see my idea was a bust but here is the original op
Okay, Lets try this here because nobody seems interested in helping in the T-Mobile section.
ThePagel said:
Correct me if I am wrong here, the reason knox is being tripped by cf auto root is because of the way it acquirers root not because it is rooted. With that in mind I would Like to make a tar ball with a pre rooted system.img. To make sure it will have the best possibility to not trip knox and not cause a soft brick I want to use a system dump from a running phone that has only been rooted. I am pretty sure this has worked on every galaxy phone before the s6 and the only reason you don't hear more about it recently is because of the success of towelroot. I am getting this phone on the 1st (so excited) and would like root but want to try samsung pay more.
If you are willing to help I need the following:
Be on a 100% stock samsung bloated system with root (absolutely no tweaked systems I need pure stock with root)
Install supersu into /system (supersu settings)
Make a system.img dump with adb or terminal emulator and upload it for me (as long as you do not dump the data partition no personal data will be dumped)
At this point I will make the tarball and upload it and have the person who made the system dump flash the tarball. If he/she boots up fine I will the need a volunteer who has not rooted and verified that knox has not been tripped on his/her phone to flash it and see if knox still has its warranty. Obviously the volunteer should go into this not caring if knox gets tripped.
To make things completely clear I need the following:
Somebody who knows how to dump with adb/terminal emulator and already rooted
Somebody without a tripped knox warranty who doesn't care if it gets tripped
Click to expand...
Click to collapse

As soon as you flash an unsigned image Knox is going to be tripped.

Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app

Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
^^^ This, unfortunately, ends the discussion altogether.

Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CafeKampuchia said:
^^^ This, unfortunately, ends the discussion altogether.
Click to expand...
Click to collapse
Indeed now I get closure, thank you.

So how does safestrap work?

lowspeed said:
So how does safestrap work?
Click to expand...
Click to collapse
Doesn't matter in this instance because you need root to use safestrap. He is pretty open on how safestrap works if you look at his threads and website.

Sorry guys, which signature needs to be applied? I found a guide to sign Windows modded drivers, I don't know if this can be applied here, too...

The real trick is getting it signed. There might be no easy way to do that unless the key method can be replicated to make signed binaries. This could be a samsung proprietery tool. That said I did find an interesting nugget of info hxxp://galaxys4root.com/what-is-binary-counter/ in the comments section.
HI,
I flashed pre rooted firmware 4.2.2 using ODIN on my Samsung I-9500 4.2.2. Then the status is remain same
Binary : Samsung Official
System : Official.
Then I installed Wanam apk to modify the UI, It asked me to download Xposed framework I grant Super user permission. Once It completed I checked the status
Binary : Samsung Official
System : Custom.
I flashed stock firmware 4.2.2 and did the reset factory reset. Then it changed to
Binary : Samsung Official
System : Official.
My question, Is the hidden binary count or knox counter triggered or not ?
If I updated to stock 4.3 Is the Knox Warranty bit 0×0 or 0×1 ?
Please help me.
The rooted aspect only seems to be possible provided nothing in the UI itself is changed? There is a trigger file in the rom. Something that obviously a Wanam install triggers. All that seems to indicate that it might actually be possible to have a pre-rooted rom and install via recovery. But considering the phone model referenced, its possible this particular workaround has been plugged. On the off chance that it has not. It might be the only viable way to do root without tripping knox. I imagine the existing stock roms with root preloaded however trip knox (I saw no indication of that in posts but I did not dig that deep).
If anyone can answer that in the affirmative or negative it might be worth noting. Will knox get tripped on a stock (but pre-rooted) rom?

The point of this thread is to point out something we already know and have known for some time? WTF

shollywood said:
The point of this thread is to point out something we already know and have known for some time? WTF
Click to expand...
Click to collapse
I don't think the OP was aware of all the information when he started the thread. I think the thread title has since been changed.
But yeah, i guess the thread could be closed.