I love using Wanam Xposed along with the extra power the Xposed framework gives to Greenify but I found an issue with it on the S5. When you install the framework S Health no longer works. Anyone else find this or is it just my S5?
carbonize said:
I love using Wanam Xposed along with the extra power the Xposed framework gives to Greenify but I found an issue with it on the S5. When you install the framework S Health no longer works. Anyone else find this or is it just my S5?
Click to expand...
Click to collapse
im also having the same problem , try posting on there thread and see if you can get anyhelp
this is my log file for the error when s health crashes
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
I have posted in the Xposed forum so will see if I get anywhere.
Hmm I did have a reply but tapatalk wasn't showing there being one. http://forum.xda-developers.com/showthread.php?t=2725405
The problem has something to do with disabling knox after rooting. If you do not disable knox, s-health seems to be ok, but after disabling it, it has issues. Some people have restored, rerooted, keeping knox and resolved the issue.
risestar2 said:
The problem has something to do with disabling knox after rooting. If you do not disable knox, s-health seems to be ok, but after disabling it, it has issues. Some people have restored, rerooted, keeping knox and resolved the issue.
Click to expand...
Click to collapse
happen to have a link to thread where users have done the above looking for a bit more info on this.
far I knew knew there was no way to root and recovery without tripping knox
Tripping the Knox flag us not the issue, the issue us when you disable know in #su afterwards. You can root and keep Knox running and it eliminates these issues
ex-28 said:
happen to have a link to thread where users have done the above looking for a bit more info on this.
far I knew knew there was no way to root and recovery without tripping knox
Click to expand...
Click to collapse
risestar2 said:
Tripping the Knox flag us not the issue, the issue us when you disable know in #su afterwards. You can root and keep Knox running and it eliminates these issues
Click to expand...
Click to collapse
So how do you root and keep knox in intact with recovery?
Sent from my SM-G900W8 using Tapatalk 2
Yes, when it asks you if you want to disable Knox, you choose no
ex-28 said:
So how do you root and keep knox in intact with recovery?
Sent from my SM-G900W8 using Tapatalk 2
Click to expand...
Click to collapse
risestar2 said:
Yes, when it asks you if you want to disable Knox, you choose no
Click to expand...
Click to collapse
Ok thanks do
You have the thread handy should how to revert back when Knox is disabled?
Sent from my SM-G900W8 using Tapatalk 2
I used Chainfire's root and don't remember disabling Knox.
risestar2 said:
Tripping the Knox flag is not the issue, the issue us when you disable knox in #su afterwards. You can root and keep Knox running and it eliminates these issues
Click to expand...
Click to collapse
carbonize said:
I used Chainfire's root and don't remember disabling Knox.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2696537
Using this root increases your flash counter and trips the KNOX warranty flag!
maybe i'm reading what other post said key word "disable"
I never disabled knox but did trip the flag
Pretty much any rooting method to date or any unsecured bootloader will trip the Knox flag. If you don't want to trip the flag, you're going to have to stay bone stock. There's a difference in tripping the flag and disabling the Knox software. When you root and choose to disable Knox, that's when people have issues with some Sammy apps
Sent from my SM-G900T using xda app-developers app
I'm trying to understand... are people disabling Knox themselves before/after they install Xposed, or is Xposed disabling Knox automatically?
Anyway to test if Knox is enabled or not?
risestar2 said:
Pretty much any rooting method to date or any unsecured bootloader will trip the Knox flag. If you don't want to trip the flag, you're going to have to stay bone stock. There's a difference in tripping the flag and disabling the Knox software. When you root and choose to disable Knox, that's when people have issues with some Sammy apps
Sent from my SM-G900T using xda app-developers app
Click to expand...
Click to collapse
risestar2 said:
The problem has something to do with disabling knox after rooting. If you do not disable knox, s-health seems to be ok, but after disabling it, it has issues. Some people have restored, rerooted, keeping knox and resolved the issue.
Click to expand...
Click to collapse
can you explain this more please you stated that some people are restoring and rerooting and keeping knox enabled then s health works fine. but searching the forums I am unable to find any reference to this or how to do this.;
would also like to know a way to tell if knox is enabled or disabled , I know my knox flag is tripped but far as I know I never disabled it , if that's the case then if knox is the issue then my s health should be working fine.
---------- Post added at 10:37 AM ---------- Previous post was at 10:35 AM ----------
maybe a better question is this
risestar2 are you rooted with recovery and have xposed installed with s health working fine ? on the galaxy s5
Surely the big question is what is Xposed doing that stops it working as it works fine until I install Xposed.
carbonize said:
Surely the big question is what is Xposed doing that stops it working as it works fine until I install Xposed.
Click to expand...
Click to collapse
would like to know as well
mine works fine even after installing xposed ,its when you install the framework in xposed that makes s health crash as if I uninstall the framework from within xposed and reboot , s health is fine again , I took my logcat files and have posted them but no luck form anyone yet
I'll try to find the thread, but essentially it's this.
You root your phone using one of the 2 preferred methods, both of which trigger your one time Knox flag.
Installing root installs the #su app. Upon starting this for the first time, you should be prompted that Knox is running, do you want to disable? Yes/No.
People that choose yes are having difficulty using some Sammy apps, including so health and private mode. People that don't disable Knox are not having these issues.
You may be able to re-enable Knox in #su, or your best bet is factory restore and then reroot and choose not to disable Knox (root and everything still works fine)
You can troubleshoot it by Uninstalling all xposed framework and modules and testing all Sammy apps. If they work fine then the issue is a compatibility issue with xposed or xposed and another app or modification. If they don't work with xposed Uninstaller then the issue is likely Knox related and you likely need to re-enable Knox.
The Knox flag is a one time flag, not a counter so once it's tripped, it's tripped (e-fuse) and it doesn't really matter what you do afterwards. You can load a hundred different rooms and it will still be 0x1 Knox warranty void.
Risestar2 I've already said the issue only occurs after installing Xposed and goes away one I uninstall it. So the problem definitely lies with Xposed and not knox.
Related
Has anyone run across this who have upgraded to 4.4.x?
Apparently, in the version of KitKat released by Samsung, without a 3rd party chip installed in the accessory, the accessory won't be recognized by the ROM.
http://forum.xda-developers.com/showthread.php?p=49696039 (yes, it's my original post, just asking the question here as well).
sanjsrik said:
Has anyone run across this who have upgraded to 4.4.x?
Apparently, in the version of KitKat released by Samsung, without a 3rd party chip installed in the accessory, the accessory won't be recognized by the ROM.
http://forum.xda-developers.com/showthread.php?p=49696039 (yes, it's my original post, just asking the question here as well).
Click to expand...
Click to collapse
Yup, but it has been fixed if you have root >>> here
Will updating/flashing Framework require you to trip knox though? Meaning, does it require a different recovery? Not clear in the link you provided. Sorry, I'm not an expert at all on framework and how to get it on the devices.
sanjsrik said:
Will updating/flashing Framework require you to trip knox though? Meaning, does it require a different recovery? Not clear in the link you provided. Sorry, I'm not an expert at all on framework and how to get it on the devices.
Click to expand...
Click to collapse
Well rooting (unless you are on MJ2 firmware) will trip your KNOX I'm afraid but no custom recovery is required only root access, - but if you were rooted, then it's just a case of installing Xposed framework (pretty much just an .apk install) - then open the app, go to downloads and find that mod, hit install and reboot and that's it pretty much
rooting <> tripping Knox
radicalisto said:
Well rooting (unless you are on MJ2 firmware) will trip your KNOX I'm afraid but no custom recovery is required only root access, - but if you were rooted, then it's just a case of installing Xposed framework (pretty much just an .apk install) - then open the app, go to downloads and find that mod, hit install and reboot and that's it pretty much
Click to expand...
Click to collapse
Not a true statement at all that rooting will trip Knox. I used Kingo and haven't tripped Knox at all. I'm just asking if flashing Xposed framewwork requires a different recovery and bootloader which WILL trip Knox as it requires a new recovery. However, I have 0x0 root so, no, rooting does NOT imply you've tripped Knox at all.
I just looked up Xposed and was able to install and run the APK and able to install a few of the add-ons.
Nice. And all that without tripping Knox, hmm.
sanjsrik said:
Not a true statement at all that rooting will trip Knox. I used Kingo and haven't tripped Knox at all. I'm just asking if flashing Xposed framewwork requires a different recovery and bootloader which WILL trip Knox as it requires a new recovery. However, I have 0x0 root so, no, rooting does NOT imply you've tripped Knox at all.
I just looked up Xposed and was able to install and run the APK and able to install a few of the add-ons.
Nice. And all that without tripping Knox, hmm.
Click to expand...
Click to collapse
Well usually rooting any firmware past MJ2 trips KNOX especially if using CF Root, I cannot comment on Kingo as it was banned and still is banned on XDA afaik, so never had any dealings with it. Plus I tripped my KNOX straight away. Also, from what I have read around, after you reboot when installing certain root methods, it'll trip KNOX automatically (whether yours has/.will is a different story)
Hi, I downgraded my S4 from NA4 to MK8, and I rooted it. After that, I installed KNOX, and now I can't use it because it simply doesn't run... I'm able to type password, but then "KNOX stopped working"... How can I run this, or how can I uninstall KNOX? Maybe I should first install KNOX and then root phone? Or don't accept KNOX blocking while rooting?
E: Also, I have installed floating window mod, so I modified some system files, maybe this is why KNOX don't work?
Your knox must of tripped to 0x1. I have noticed that you cannot use any knox software anymore once it's tripped.
Sent from my GT-I9505 using xda app-developers app
adry1988 said:
Your knox must of tripped to 0x1. I have noticed that you cannot use any knox software anymore once it's tripped.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Wow, you scared me, but everything is OK. Knox flag is 0x0.
E: Ok, it looks fine for now. I just unrooted, and rooted again.
E2: No... It looks like KNOX don't work when xposed is installed. Why?
bartas225 said:
Wow, you scared me, but everything is OK. Knox flag is 0x0.
E: Ok, it looks fine for now. I just unrooted, and rooted again.
E2: No... It looks like KNOX don't work when xposed is installed. Why?
Click to expand...
Click to collapse
After rooting knox cant be run nd on rooting i think is should be ox1
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
After rooting knox cant be run nd on rooting i think is should be ox1
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I rooted it by Saferoot, it's not touching Knox flag. Anyway, last time I was on MK8, I had rooted device, and using Knox without troubles.
Why do you want to use Knox? I don't even know what it does
KingOfDope said:
Why do you want to use Knox? I don't even know what it does
Click to expand...
Click to collapse
Why use it
Because it is not liked by root users Knox has some good things depends on what angle he looked
KingOfDope said:
Why do you want to use Knox? I don't even know what it does
Click to expand...
Click to collapse
To store some files that shouldn't be opened by anyone else than me
bartas225 said:
To store some files that shouldn't be opened by anyone else than me
Click to expand...
Click to collapse
oowhh, thank you
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
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.