Database Users

[Q] How do you check Knox counter?

Hi,
I rooted using towel root and then downloaded supersu from the Play Store. I opened supersu, which first asked if I wanted to disable Knox. I elected to disable Knox.
Afterwards, a prompt popped up asking if I wanted to update the binaries. I elected to update the binaries, but the update failed.
I decided to uninstall supersu and reinstall. After reinstall, the binaries updated, but the prompt re: whether to disable Knox did not come up again.
I wanted to check the Knox counter, so I entered download mode. However, there was no reference to Knox counter where I used to see as in my old s3.
My questions are:
1. Since I disabled Knox on the first install, did it remain disabled after uninstalling and reinstalling (there was no prompt to disable Knox after the reinstall)
2. How do I check the Knox counter?
Thanks in advance!

KNOX refers to a few things. There is the software component and the hardware component.
Most custom ROMs have KNOX software removed, along with Carrier IQ stuff if your carrier pre-installs that.
The hardware side, is a warranty indicator. See attached picture (it's similar for G900 phones). If you are 0x1 your KNOX warranty is supposedly void, and cannot be reset. There will also be a number in parentheses like (1) or (2), that is the counter. The hardware part of KNOX can NOT be reset at this time, and probably never will be.
If you want more information, look it up on Google or use the XDA search feature, as KNOX has been discussed endless amounts of times already.
edit: You also might want to read this for future reference: http://forum.xda-developers.com/showthread.php?t=2712710

So the KNOX flag can normally be checked while in download mode, yes? How to get into download mode?
Sorry if the question seems noob.

TheSamWolf said:
So the KNOX flag can normally be checked while in download mode, yes? How to get into download mode?
Sorry if the question seems noob.
Click to expand...
Click to collapse
Or install Phone Info from Play to see the KNOX warranty void status, download mode is volume down + menu + power button.

Thanks gee2012! I think you mean: Volume Down + Home + Power Button?
And press volume up at the prompt.
I hope that's right

TheSamWolf said:
Thanks gee2012! I think you mean: Volume Down + Home + Power Button?
And press volume up at the prompt.
I hope that's right
Click to expand...
Click to collapse
Yup, sorry i meant home and then volume up is correct

banditsw said:
2. How do I check the Knox counter?
Thanks in advance!
Click to expand...
Click to collapse
Use this app: Phone INFO ★Samsung★
Will get all info you need.

[Q] Please some help with KNOX.

Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?

VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Reflashing stock rom and without root your device again.

VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Wow

VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Deroot your device and flash stock rom..... try and post your feedback here

Joku1981 said:
Reflashing stock rom and without root your device again.
Click to expand...
Click to collapse
more instructions please,how to reflashing ?

VaRyOss said:
more instructions please,how to reflashing ?
Click to expand...
Click to collapse
You can easily search on the q&a section on how to reflash your phone. But if you don't know how to do that, I suggest you read a LOT before you attempt to reflash.
Your original post shows that you have absolutely NO idea about how to do anything to your phone and keep it in a working state, or what any modification implies.
If you lost knox, there is absolutely NO way to get it back. Reflashing to stock will have NO impact on the state of the knox. If the knox flag is triggered, then your knox apps have stoppped functioning and, like I said before, there is ABSOLUTELY NO WAY to reverse that.
I really don't know why the others told you to reflash to stock. I thought it was general knowledge that once you lose knox, it cannot be reversed and you also lose the knox apps.
I know i repeated myself a couple of times, but with your kind of people, repetition is the only way to make oneself understood.
Good luck dude!

VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
To my knowledge every Root related thread mentions, very explicitly, that rooting prevents you from using the KNOX app.
Which makes perfect sense, since KNOX is a security container meant for storing secure data. Once you root, no part of the device is truly safe from tampering.
Once the KNOX flag is 0x1, The KNOX app is disabled and can not be restored. If you want to use KNOX, I'm afraid you'll have to buy a new device. The 0x1 flag can't be reset.

ShadowLea said:
To my knowledge every Root related thread mentions, very explicitly, that rooting prevents you from using the KNOX app.
Which makes perfect sense, since KNOX is a security container meant for storing secure data. Once you root, no part of the device is truly safe from tampering.
Once the KNOX flag is 0x1, The KNOX app is disabled and can not be restored. If you want to use KNOX, I'm afraid you'll have to buy a new device. The 0x1 flag can't be reset.
Click to expand...
Click to collapse
uhmm....k..i understand that. there is another app. similar to KNOX?

i find a app. in magazin play called "Knoxx",work's close anought for me. For people who want to know is the one with a yellow K

Kingroot on top of My KNOX, Working Great! !

I was concerned about Security with Kingroot so decided to try this. I'm on a RETAIL Verizon Note 4 running 4.4.4.
I did a factory restore then after setup, I DISABLED SDM, THEN I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot on the "Personal" side.
It worked. Root is, On Demand, temporary, And I think it is safer than using Kingroot without Knox.
I went into recovery to check but no Knox trip. I win!. I have two environments. One rooted the other as secure as you can get.
This is like having a dual boot on the fly. With this root you can at least use Adaway. You can get a lot done with it. This is the best root solution for the Retail Verizon Note 4. I am hoping to get developers interested.
O.K.,This is where I'm at. If someone could look at the pictures and tell me what I should add to the OP description, I'll do it. Look at the last two pictures, Knox would not let me take the screen shots because of security.
Check Out MOST ASKED QUESTIONS and Fixes in the next post.

MOST ASKED QUESTIONS
1. What phone is this for? Retail Verizon Note 4. This may also work on other un-rooted phones
2. What ROM are you on? 4.4.4 found HERE http://forum.xda-developers.com/not...w-to-roll-to-kk-4-4-4-lollipop-5-0-1-t3097054
3. How did you set up your google account? I set my personal side up with a "burner" email and the Knox side with the email I use every day.
4. How do you disable SDM? I used this: http://forum.xda-developers.com/and...---------------------------------------------
5.Where do you get My Knox" The Play Store.
6. Where did you get Kingroot? http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
7. What order do you install the software? Restore 4.4.4/Set up Google account./disable SDM/setup My Knox/Kingroot on personal side/=enjoy..... .......Note: this is not for use with SuperSUME.
8. Is root permanent? Some of the modification made when rooted are permanent but this Root is On Demand, temporary And I think this root method is safer than using Kingroot without Knox.
9. What about reboots. If a App ask to reboot first try not rebooting some changes will take effect without a reboot. If you have to reboot use a soft-reboot like SimpleReboot. You will almost always lose root with a hard reboot.
10. For an added security measure I am going to use the "Personal" root side as a playground and reboot before I open the My Knox Security side. Just to throw off any would be hackers.
Fixes
1. I found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select allow and then on the first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
The same procedure may work for other apps. For some reason Adaway starts working without a reboot. You will need to clear and restart your browser.
Calm down, these things take time. First when you reboot allow your phone to settle down, a minute or two. Don't open anything. FIRST, Open and run kingroot. Once root is established run Adaway like I said. It probably will work the first time but if it fails just try again. It seem that once Kingroot gets to the point where it is not asked for permission, the reboots go away and it becomes more stable.
2. O.K., KNOX disables USB debugging, but I was able to uninstall Knox at the Playstore /Re-enable USB debugging/ then use gatesjunior's debolater app to remove SDM/ then install Knox /then root with Kingroot and it is working great again. I did try to put Super-Sume Pro on top but it would NOT work. I think Super-Sume Pro removes Knox. So I had to start over but I got it working great. If you need to use USB debugging for anything now we have to uninstall Knox. I'm still testing now.
-----------------------------------------------------------------------------------------
Check Back to post # 1 & 2 for updates.

Having some guys look into this.

doctor-cool said:
I was concerned about Kingroot and security so decided to try this.
I'm on a retail Verizon Note 4 running Gatesjunior's Safe 4.4.4.
I did a factory restore then after setup, I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot . It worked. Now sometime when I reboot I get the Unlock logo with the words Custom on the boot screen just like the DE Note 4 . I went into recovery to check but no Knox trip. I win the Root Price. I have two environments. One rooted the other as secure as you can get.
Click to expand...
Click to collapse
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app

warriorpluto said:
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
Click to expand...
Click to collapse
did you test it?
Extreme Syndicate L

This is like having a dual boot on the fly
gatesjunior said:
Having some guys look into this.
Click to expand...
Click to collapse
I have two separate Google play store account on two separate partitions .
Can you get it to work with SuperSuMe Pro.
All this time we have been disabling Knox and actually My Knox is your friend.

I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...

Wetzel402 said:
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Click to expand...
Click to collapse
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.

doctor-cool said:
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
Click to expand...
Click to collapse
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.

gatesjunior said:
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
Click to expand...
Click to collapse
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.

doctor-cool said:
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
Click to expand...
Click to collapse
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L

elliwigy said:
did you test it?
Extreme Syndicate L
Click to expand...
Click to collapse
No. I havemt backed up my phone yet to try. Ill do it when I get home and try
Sent from my SM-N915V using XDA Free mobile app

not random
elliwigy said:
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
Click to expand...
Click to collapse
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:

doctor-cool said:
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
Click to expand...
Click to collapse
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L

elliwigy said:
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
Click to expand...
Click to collapse
I meant when AdAway disables the commercials it is worth the trouble. But yes most of the time the root results are temporary . But once you get it set up your good to go and it is worth the trouble until your battery dies
-----------------------------------------------------
Edit: I may have found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select alow and on first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes

I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr

Hotdizzle said:
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Click to expand...
Click to collapse
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.

doctor-cool said:
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
Click to expand...
Click to collapse
I have the retail note 4

Hotdizzle said:
I have the retail note 4
Click to expand...
Click to collapse
Then...l don't know. I'm on safe 4.4.4, how about you?
-----------------------------------------------------
I just read your post 16 . Your on LP I'm on KK

LOL this works?!? how did nobody ever try this until now.. I'm speechless

Galaxy S8 Secure folder with Knox ?

Hello
How to use secure folder with Knox 0x1 ?
It there any way to do this ?

no

locarno said:
Hello
How to use secure folder with Knox 0x1 ?
It there any way to do this ?
Click to expand...
Click to collapse
Once your Knox is tripped you can not use secure folder. There is no fix for a tripped Knox.

Is it possible to mask the 0x1 to make Knox and Samsung Pay work?

WilliamBlake said:
Is it possible to mask the 0x1 to make Knox and Samsung Pay work?
Click to expand...
Click to collapse
Yes MagiskHide masks the 0x1 Value to 0x0 and it might work to use some of the features that check for the Knox counter value.
0. You need to be rooted with the latest version of Magisk.
1. You need to change the name of the Magisk Manager app to a different name using the "Hide Magisk Manager" function.
2. Turn on MagiskHide in settings and check Samsung pay and Secure folder (And all the apps that help them run like Samsung pay framework etc.) in the MagiskHide tab.
3. Delete any files in your internal storage that have Magisk in the name.
4. (Optional) If you dont want to be rooted you can also disable Superuser access within the Magisk Manager App.
Edit: You may also have to enable "Magisk Core Only Mode" so that no modules or anything extra is loaded that Samsung Pay could possibly detect.
This is not 100% guarenteed to work but it is worth a try as it is close as you are going to get to knox 0x0.

JJcoder said:
Yes MagiskHide masks the 0x1 Value to 0x0 and it might work to use some of the features that check for the Knox counter value.
0. You need to be rooted with the latest version of Magisk.
1. You need to change the name of the Magisk Manager app to a different name using the "Hide Magisk Manager" function.
2. Turn on MagiskHide in settings and check Samsung pay and Secure folder (And all the apps that help them run like Samsung pay framework etc.) in the MagiskHide tab.
3. Delete any files in your internal storage that have Magisk in the name.
4. (Optional) If you dont want to be rooted you can also disable Superuser access within the Magisk Manager App.
This is not 100% guarenteed to work but it is worth a try as it is close as you are going to get to knox 0x0.
Click to expand...
Click to collapse
Once Knox is tripped it triggers an Efuse, that can only be fixed by a motherboard replacement. Samsung Pay will never work once Knox has been tripped.

stonedpsycho said:
Once Knox is tripped it triggers an Efuse, that can only be fixed by a motherboard replacement. Samsung Pay will never work once Knox has been tripped.
Click to expand...
Click to collapse
I know, but MagiskHide masks the value to 0x0.

JJcoder said:
I know, but MagiskHide masks the value to 0x0
on boot.
Click to expand...
Click to collapse
That will not make Samsung Pay work.

stonedpsycho said:
That will not make Samsung Pay work.
Click to expand...
Click to collapse
Are you sure? Maybe if you just enable MagiskHide it wont work; but if you follow all of my steps how can Samsung pay detect Knox 0x1 and root? Maybe you have to reinstall Samsung Pay? I am still on the 7 day jail (RMM state lock) on my S8 so I can't experiment with it right now.

JJcoder said:
Are you sure? Maybe if you just enable MagiskHide it wont work; but if you follow all of my steps how can Samsung pay detect Knox 0x1 and root? Maybe you have to reinstall Samsung Pay? I am still on the 7 day jail (RMM state lock) on my S8 so I can't experiment with it right now.
Click to expand...
Click to collapse
It will not fix the Efuse though.

stonedpsycho said:
It will not fix the Efuse though.
Click to expand...
Click to collapse
You are right! I'm not trying to revert the eFUSE that
is not possible. I am trying to mask the value so that Samsung Pay and other apps will think that Knox is 0x0 and that the phone is not rooted. My question is
how can Samsung Pay detect Knox 0x1 even when following all of the steps I listed above while all of the Knox Status apps on the Play Store say 0x0 while simply enabling MagiskHide and checking the app in the MagiskHide tab?

JJcoder said:
You are right! I'm not trying to revert the eFUSE that
is not possible. I am trying to mask the value so that Samsung Pay and other apps will think that Knox is 0x0 and that the phone is not rooted. My question is
how can Samsung Pay detect Knox 0x1 even when following all of the steps I listed above while all of the Knox Status apps on the Play Store say 0x0 while simply enabling MagiskHide and checking the app in the MagiskHide tab?
Click to expand...
Click to collapse
I am no expert and don't understand how it all works but if there was a way or workaround for Samsung Pay to work I think the talented Devs here on XDA would have found a solution by now, like one did for Secure Folder.

stonedpsycho said:
I am no expert and don't understand how it all works but if there was a way or workaround for Samsung Pay to work I think the talented Devs here on XDA would have found a solution by now, like one did for Secure Folder.
Click to expand...
Click to collapse
Did anyone actually try following the steps I listed? Maybe you also have to enable Magisk Core only mode so no modules or anything extra is loaded that Samsung Pay could possibly detect? If that doesn't work then what about reinstalling Samsung Pay and it's framework after following these steps?
As I said I wish I could try myself but I am still in RMM state: Prenormal

JJcoder said:
Did anyone actually try following the steps I listed? Maybe you also have to enable Magisk Core only mode so no modules or anything extra is loaded that Samsung Pay could possibly detect? If that doesn't work then what about reinstalling Samsung Pay and it's framework after following these steps?
As I said I wish I could try myself but I am still in RMM state: Prenormal
Click to expand...
Click to collapse
I have never tried that but I highly doubt it will work still.
Jail time! You tried the trick of moving the clock forward 7+ days?

stonedpsycho said:
I have never tried that but I highly doubt it will work still.
Jail time! You tried the trick of moving the clock forward 7+ days?
Click to expand...
Click to collapse
Yes, but it didn't work for me (because I think it only works on Oreo and im on Pie)
So I just have to wait 7 days.

JJcoder said:
Yes, but it didn't work for me (because I think it only works on Oreo and im on Pie)
So I just have to wait 7 days.
Click to expand...
Click to collapse
I know it can be hit and miss and can take a few attempts, probably worth another try. I only faced jail time on Oreo, but I use a Note 8.
If you do get Spay to work though, please let us know as so many people will be very happy with you :fingers-crossed:

stonedpsycho said:
I know it can be hit and miss and can take a few attempts, probably worth another try. I only faced jail time on Oreo, but I use a Note 8.
If you do get Spay to work though, please let us know as so many people will be very happy with you :fingers-crossed:
Click to expand...
Click to collapse
Well im already on my third day and if the date trick doesn't work then i'll have to start all over again.
As yes I will let everyone know if I can get Samsung Pay to work

Where is the su of rooted S7 edge binary stored?

Hi!
I want to hide su binary from my phone temporarily to trick apps into thinking that my phone is not rooted. I thought I could just rename su binary from TWRP but I could not find that. It's not inside /system/xbin/ or /system/bin/.

It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.

Thanks!
V0latyle said:
It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.
Click to expand...
Click to collapse
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.

sysctl said:
Thanks!
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.
Click to expand...
Click to collapse
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.

V0latyle said:
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.
Click to expand...
Click to collapse
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?

sysctl said:
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?
Click to expand...
Click to collapse
Unrooting won't wipe data. It doesn't matter how you do it.

V0latyle said:
Unrooting won't wipe data. It doesn't matter how you do it.
Click to expand...
Click to collapse
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.

sysctl said:
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.
Click to expand...
Click to collapse
I honestly don't know that much about Knox but having it disabled doesn't make your device any more vulnerable than being rooted. Be mindful of what you install, and don't grant root access to apps you don't trust.