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)
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,
I just got my S5 and i want to root.
i had S4 before and i used CF-Auto root.
but i was looking at some threads and they were saying that there is Knox Free root?
please can someone guide me to root.
i dont really care about knox but i prefer if its still 0x0
Check this guide
http://forum.xda-developers.com/showthread.php?t=2843044
aniqpirzada said:
Hi,
I just got my S5 and i want to root.
i had S4 before and i used CF-Auto root.
but i was looking at some threads and they were saying that there is Knox Free root?
please can someone guide me to root.
i dont really care about knox but i prefer if its still 0x0
Click to expand...
Click to collapse
If you want to flash custom recovery`s or custom roms KNOX will be tripped unfortunately
So, to sum up, if you want to root without tripping KNOX, you need to stay stock and not even install custom recovery. if you plan to install custom recovery, no need to go though the effort of not tripping KNOX and just use CF-Auto root.
Towel root should root pre June 6th builds of S5 4.4.2 firmware, without incrementing Knox.
Installing any custom kernel or recovery or using CF autoroot will increment the Knox counter. Less commonly, some failed firmware writes, corrupted partitions, soft bricks or kernel crashes may also increment the counter.
.
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.
I saw a post on android central and a guy said he was able to root his note 3 with out tripping knox, he said that it didn't trip because he didn't flash a custom rom, and since SuperSU promps you if you want to disable knox when you download it. So my question is do you need a custom rom to root the galaxy s8 and does SuperSU actually stop knox from tripping?
Here is the link to that forum post that I saw:
HTML:
https://forums.androidcentral.com/ask-question/401468-just-rooted-supersu-wants-disable-knox-will-void-warranty.html
Thank you in advance if I don't respond. :good:
KingZeroKiryu said:
I saw a post on android central and a guy said he was able to root his note 3 with out tripping knox, he said that it didn't trip because he didn't flash a custom rom, and since SuperSU promps you if you want to disable knox when you download it. So my question is do you need a custom rom to root the galaxy s8 and does SuperSU actually stop knox from tripping?
Here is the link to that forum post that I saw:
HTML:
https://forums.androidcentral.com/ask-question/401468-just-rooted-supersu-wants-disable-knox-will-void-warranty.html
Thank you in advance if I don't respond. :good:
Click to expand...
Click to collapse
Bro it was the first knox now it's smarter. You flash something that is not Samsung and your warranty is gone.
Sent from my SM-G950F using Tapatalk