Related
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.
Hi guys,
A Small and dumb question. I rooted my device with towelroot without tripping knox. I would like (after uninstalling bloatware) to use xposed. Is it possible without tripping?
II was thinking about changing status bar color etc.
Thx
latouffe said:
Hi guys,
A Small and dumb question. I rooted my device with towelroot without tripping knox. I would like (after uninstalling bloatware) to use xposed. Is it possible without tripping?
II was thinking about changing status bar color etc.
Thx
Click to expand...
Click to collapse
Framework works OK, I use Wanaam, boot manager and privacy. I did not tested other modules (yet) as I think that some, like gravity box, could trip it. However, others, especially tailored for kitKat... hmm... why not?
latouffe said:
Hi guys,
A Small and dumb question. I rooted my device with towelroot without tripping knox. I would like (after uninstalling bloatware) to use xposed. Is it possible without tripping?
II was thinking about changing status bar color etc.
Thx
Click to expand...
Click to collapse
Hi,
KNOX will only be tripped if you root with CF Auto Root, flash a custom recovery or a custom kernel.....at most knox may block the use of the app in worse case scenario
Should not trip the warranty bit if rooted with towelroot
Hi guys so I'm really sorry if this has been asked millions of times but what I want to know is, does tripping the KNOX flag open a huge risk to normal system functionality not working? Now I know KNOX tripping, prevents you from using KNOX related stuff but does it stop you from an average joe using their phone normally, installing apps, sideloading apps, using the camera. That sort of thing.
The other thing is, I want to have a go at flashing custom ROMs to my device. My warranty runs out next month so this would be perfect, providing the above question is true (that it doesn't disable full functionality) I will go and follow normal tutorials.
Now I've been reading about SafeStrap and how it creates the ability to flash ROMs without touching vital system parts that would trip KNOX. Is this true? Could I really root without tripping, install SafeStrap and finally install custom ROMs without tripping KNOX or am I in a dream world haha?
WhaleTrain said:
Hi guys so I'm really sorry if this has been asked millions of times but what I want to know is, does tripping the KNOX flag open a huge risk to normal system functionality not working? Now I know KNOX tripping, prevents you from using KNOX related stuff but does it stop you from an average joe using their phone normally, installing apps, sideloading apps, using the camera. That sort of thing.
The other thing is, I want to have a go at flashing custom ROMs to my device. My warranty runs out next month so this would be perfect, providing the above question is true (that it doesn't disable full functionality) I will go and follow normal tutorials.
Now I've been reading about SafeStrap and how it creates the ability to flash ROMs without touching vital system parts that would trip KNOX. Is this true? Could I really root without tripping, install SafeStrap and finally install custom ROMs without tripping KNOX or am I in a dream world haha?
Click to expand...
Click to collapse
Tripping knox does not affect phone performance, as for safestrap, as far as I know that has to be used on locked bootloader phones (like US carrier ones).
Once knox is tripped knox is tripped, I have heard the proggy that does not trip knox when rooting is Towelroot, but some people are having big problems with battery life.
WhaleTrain said:
Hi guys so I'm really sorry if this has been asked millions of times but what I want to know is, does tripping the KNOX flag open a huge risk to normal system functionality not working? Now I know KNOX tripping, prevents you from using KNOX related stuff but does it stop you from an average joe using their phone normally, installing apps, sideloading apps, using the camera. That sort of thing.
The other thing is, I want to have a go at flashing custom ROMs to my device. My warranty runs out next month so this would be perfect, providing the above question is true (that it doesn't disable full functionality) I will go and follow normal tutorials.
Now I've been reading about SafeStrap and how it creates the ability to flash ROMs without touching vital system parts that would trip KNOX. Is this true? Could I really root without tripping, install SafeStrap and finally install custom ROMs without tripping KNOX or am I in a dream world haha?
Click to expand...
Click to collapse
Yes, it seems to be possible that you can flash custom roms without tripping Knox.
http://forum.xda-developers.com/galaxy-s4/general/guide-how-to-install-custom-roms-t2852310
Sent from my Galaxy S4 using Tapatalk
Without tripping knox you can get root, and modify the actual rom filesystem, for example you can change all /system of the rom using mobile odin pro.
You cannot change kernel or recovery, or you get knox 0x1.
Flashing roms with mobile odin pro is possible only if rom is compatible with your current official kernel you have, or the results would be bad (wifi not working or so on..).
fear_factory84 said:
Without tripping knox you can get root, and modify the actual rom filesystem, for example you can change all /system of the rom using mobile odin pro.
You cannot change kernel or recovery, or you get knox 0x1.
Flashing roms with mobile odin pro is possible only if rom is compatible with your current official kernel you have, or the results would be bad (wifi not working or so on..).
Click to expand...
Click to collapse
Can you flash roms after knox has been tripped
bottom661 said:
Can you flash roms after knox has been tripped
Click to expand...
Click to collapse
Yes
Sent from my GT-I9505 using XDA Free mobile app
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
I remember reading somewhere that root can be achieved [with KNOX 0x0] on the Note4 but only until restart when you had to root it again? Is this possible?
And whats the progress, any news, anyone working on permanent root on the Note 4 with out tripping Knox?
I've read about kingsroot, have someone tested it?
It does not work for lollipop, while it seems to work for kitkat, so you should downgrade before testing this app.
I don't know if it can be considered a safe practice, since the app, to perform the exploit, requires your data to be sent to a Chinese server and you will not get superuser, but the corresponding Chinese app. Anyway, some say they have eventually been able to remove such app and replace it with superuser. It is not something I tried by myself, so please do not take it for granted but it should be possible to flash lollipop by using mobile odin, while still keeping knox 0x0 and root.