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
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 would like to know if there is any known way at the moment to get a rooted kitkat 4.4.2 firmware without tripping knox. I'm momentarily running MKE 4.3, German csc I think. I'm aware of saferoot for this firmware, but I would like to know if there's something like it for official kitkat, or if it is possible to root my 4.3 and then upgrade via mobile odin and inject root via everroot everroot without tripping knox. If not I'll just update via OTA and root via another method but if it's possible I'd like to keep knox for now
wootyv said:
Hi,
I would like to know if there is any known way at the moment to get a rooted kitkat 4.4.2 firmware without tripping knox. I'm momentarily running MKE 4.3, German csc I think. I'm aware of saferoot for this firmware, but I would like to know if there's something like it for official kitkat, or if it is possible to root my 4.3 and then upgrade via mobile odin and inject root via everroot everroot without tripping knox. If not I'll just update via OTA and root via another method but if it's possible I'd like to keep knox for now
Click to expand...
Click to collapse
No, uptil now there is no such method developed. Check on Kingo root website whether they ve updated to root 4.4.2 firmware.
Mandark52 said:
No, uptil now there is no such method developed. Check on Kingo root website whether they ve updated to root 4.4.2 firmware.
Click to expand...
Click to collapse
Oké, Thanks anyway
I don't really trust kingoroot as I thought that it had spyware installed, just as vroot, but then I heard about saferoot and I I was hoping I could keep root via mobile odin, but too bad. I'll just just root via cf-root then
wootyv said:
Oké, Thanks anyway
I don't really trust kingoroot as I thought that it had spyware installed, just as vroot, but then I heard about saferoot and I I was hoping I could keep root via mobile odin, but too bad. I'll just just root via cf-root then
Click to expand...
Click to collapse
Not any spywarez but many of them reported that they lost their IMEI number.If you are on kitkat ,wait for stability updates n then root. Hit thnx if helpd.
Towelroot. by geohot
Does not trip the knox counter..but don't expect to use custom recoveries. It is a simple root only.
!SINGH! said:
Towelroot. by geohot
Does not trip the knox counter..but don't expect to use custom recoveries. It is a simple root only.
Click to expand...
Click to collapse
Thanks! I read about it in the featured articles but I wasn't sure it would work or not. I was just planning to use the root to clean the ROM up a bit to free up some system memory and RAM and make some apps system apps, better backups and fiddle a bit with my storage, and maybe using some modules, do you know if using Xposed trips knox?
wootyv said:
Thanks! I read about it in the featured articles but I wasn't sure it would work or not. I was just planning to use the root to clean the ROM up a bit to free up some system memory and RAM and make some apps system apps, better backups and fiddle a bit with my storage, and maybe using some modules, do you know if using Xposed trips knox?
Click to expand...
Click to collapse
Xposed doesn't... but I would be weary of modules that perform bootloader or deep system changes
Titanium Backup.. and use backup app and then remove/disable etc
Just be careful... if the knox counter is v important to you.
!SINGH! said:
Xposed doesn't... but I would be weary of modules that perform bootloader or deep system changes
Titanium Backup.. and use backup app and then remove/disable etc
Just be careful... if the knox counter is v important to you.
Click to expand...
Click to collapse
It's not that important to me, I just don't want to trip it if I don't have to, if I need to trip it for something I really want to do I don't have a problem with it , it's not like use knox thanks you very much
wootyv said:
It's not that important to me, I just don't want to trip it if I don't have to, if I need to trip it for something I really want to do I don't have a problem with it , it's not like use knox thanks you very much
Click to expand...
Click to collapse
Actually KNOX is very important for warranty issues. If you dont have warranty then I wouldnt worry about it. If you DO have warranty then do not mess with KNOX-tripping root methods.
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 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
Hello xda,
i have a serious question about my S4 I9506. All i want is SU so i can remove all the bloatware i don't need and unroot afterwards.
It has the latest FW I9506XXSDPK1 with latest security patch (i don't know if the old methods like CF-Autoroot or towelroot will still work).
And this shall all happen without loosing/triggering KNOX if possible.
Thank you in advance.
OB-bob said:
And this shall all happen without loosing/triggering KNOX if possible.
Click to expand...
Click to collapse
Impossible.
CF-Auto-Root is the only way to go.