This is work in progress, have got some ideas to disable Knox(only if you are rooted). Will be updating this thread tomorrow after testing the steps on the loserskater 4.3 release.
This may work but only time will tell.
Don't forget to set SELinux to permissive
Remove the following files:
Code:
(along with any associated .odex files)
/system/app/ContainerAgent.apk
/system/app/ContainerEventsRelayManager.apk
/system/app/KLMSAgent.apk
/system/app/KNOXAgent.apk
/system/app/KnoxAttestationAgent.apk
/system/app/KNOXStore.apk
(entire folders)
/system/containers
/system/etc/secure_storage/com.sec.knox.store
(doubt this one is necessary)
/system/lib/libknoxdrawglfunction.so
And I'm not sure SELinux set to permissive is actually necessary. Been running enforced with root and haven't had any issues yet.
Root persisted through reboot?
mrhaley30705 said:
Root persisted through reboot?
Click to expand...
Click to collapse
Just removed knox, rebooted, restored TiBU, rebooted, and root is still intact.
That is very good to hear :thumbsup:
loserskater said:
Remove the following files:
Code:
(along with any associated .odex files)
/system/app/ContainerAgent.apk
/system/app/ContainerEventsRelayManager.apk
/system/app/KLMSAgent.apk
/system/app/KNOXAgent.apk
/system/app/KnoxAttestationAgent.apk
/system/app/KNOXStore.apk
(entire folders)
/system/containers
/system/etc/secure_storage/com.sec.knox.store
(doubt this one is necessary)
/system/lib/libknoxdrawglfunction.so
And I'm not sure SELinux set to permissive is actually necessary. Been running enforced with root and haven't had any issues yet.
Click to expand...
Click to collapse
Can i just rename this files ?
EDIT: I renamed and restarted. Root are present after restart..
loserskater said:
Just removed knox, rebooted, restored TiBU, rebooted, and root is still intact.
Click to expand...
Click to collapse
Have you or anyone else tried Root->freeze Knox in TiBu as an alternative?
stoobie-doo said:
Have you or anyone else tried Root->freeze Knox in TiBu as an alternative?
Click to expand...
Click to collapse
I tried this, but SuperSU is still crashing. So no root for apps that didn't get root access before you installed 4.3.
norbarb said:
Can i just rename this files ?
EDIT: I renamed and restarted. Root are present after restart..
Click to expand...
Click to collapse
Did you root with CF AutoRoot or Kingo?
Evilweasel47 said:
I tried this, but SuperSU is still crashing. So no root for apps that didn't get root access before you installed 4.3.
Click to expand...
Click to collapse
Update samsung security and SU will work. Just after SU FC go to notification and there is policy info, click on it and agree to update. After this SU should work just fine.
Sent from my GT-N8013 using XDA Premium HD app
---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------
stoobie-doo said:
Did you root with CF AutoRoot or Kingo?
Click to expand...
Click to collapse
With CF-Auto
Sent from my GT-N8013 using XDA Premium HD app
norbarb said:
Update samsung security and SU will work. Just after SU FC go to notification and there is policy info, click on it and agree to update. After this SU should work just fine.
Sent from my GT-N8013 using XDA Premium HD app
---------- Post added at 01:39 PM ---------- Previous post was at 01:38 PM ----------
With CF-Auto
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
stoobie-doo said:
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
Click to expand...
Click to collapse
I am able to authorize new apps. However after removing Knox supersu fcs. I do not receive a prompt as mentioned above.
stoobie-doo said:
One more q... are you having the same root behavior that others have had, i.e., previously authorized apps continue to work, but no new ones can acquire root?
Click to expand...
Click to collapse
No i did not notice this.. I just tryed app with root requairment and no problem. Everything working like before update.
Just wanted to add more information to the table
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
tyrantsbane said:
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
Click to expand...
Click to collapse
I think you have to agree to securituy polices before you remove/dissable/rename knox files.
Edit: i post pictures to see that my SU is working fine and no problem. I did what i post allover this forums.
ali3n8 said:
I am able to authorize new apps. However after removing Knox supersu fcs. I do not receive a prompt as mentioned above.
Click to expand...
Click to collapse
I think you can somehow agree to new polices before you remove knox files and in security in settings... (sorry but i don't realy know how). All i know you need to agree in order to SU work until someone will find some other way. I did same with my S4 and last update to 4.3 and twice to leak to on S3 MJ6.
BTW: I got sim card out on my S3 this maybe case and is wort to try.
tyrantsbane said:
Yesterday after I found out that 4.3 finally released officially, I Odin'd back to stock and worked my way to 4.1.2, and then 4.3. So my phone is completely virgin, the way it would be if I just bought it and upgraded.
I Used CF-Auto Root to give me root and Superuser. The Odin flash did the job, it rebooted into recovery, did its dark magic, and started the phone normally.
As soon as the phone booted up, it FC. I ignored it, and proceeded to use root explorer to go rename the files given by Loserskater to remove Knox off the system.
As soon as I go to rename the first file, SU again crashes and I get a note about security policy needs to be update. Reading what other users were saying, I let it update.
It then blocked Super User. It won't open, and anything that tries to access it will crash (like using root explorer to do tasks that require root)
I said "Okay, maybe we'll try this again" Second flash of CF-Auto Root worked like it should. SuperUser is still blocked.
I factory reset the phone. SuperUser was there as soon as I boot up, and it FC immediately. Knox still had it blocked.
I was forced to turn off SU for now as to stop getting pop ups.
So, there has been my first few hours with Knox. Not very pleasant.
Any ideas?
Click to expand...
Click to collapse
To revert back to a fresh state on 4.3 I had to CF autoroot to get the stock recovery installed. Then while in stock recovery I selected apply update from external sdcard. I have found that when using a custom recovery I was not able to go back to a stock 4.3 state. First boot after doing this will take a bit and may even require a reflash.
so...
Does anyone know how to reset the security policies so I can test some more methods?
Or do I need to Odin down again and trudge my way back up
tyrantsbane said:
does anyone know how to reset the security policies so i can test some more methods?
Or do i need to odin down again and trudge my way back up
Click to expand...
Click to collapse
do not use odin to downgrade after installing the ota!!! You will brick your phone
Related
I installed the rooted ROM at [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPALEN] (http://forum.xda-developers.com/showthread.php?t=1774722), although I stopped before installing CWM.
It appears I don't have root. I even try to let Superuser update itself from a 3.0.x version to 3.1.1. I am never prompted to grant root access, and it eventually says "Superuser has been denied Superuser permissions".
If Superuser itself cannot get root, then how can this be called a rooted ROM?
P.S., I would have posted in the thread, but I am apparently too much of a n00b per the forum settings.
I know this doesn't help you, but Superuser worked fine for me after using the same method. All I can suggest is to try flashing it again.
Edit: make sure you don't have both Superuser and SuperSU installed. They can conflict with each other.
novasource said:
I installed the rooted ROM at [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPALEN] (http://forum.xda-developers.com/showthread.php?t=1774722), although I stopped before installing CWM.
It appears I don't have root. I even try to let Superuser update itself from a 3.0.x version to 3.1.1. I am never prompted to grant root access, and it eventually says "Superuser has been denied Superuser permissions".
If Superuser itself cannot get root, then how can this be called a rooted ROM?
P.S., I would have posted in the thread, but I am apparently too much of a n00b per the forum settings.
Click to expand...
Click to collapse
You need cwm.. Flash It and you will profit....
Sent from my SPH-L710 using xda premium
EndlessDissent said:
I know this doesn't help you, but Superuser worked fine for me after using the same method. All I can suggest is to try flashing it again.
Edit: make sure you don't have both Superuser and SuperSU installed. They can conflict with each other.
Click to expand...
Click to collapse
Thank you!
I only have Superuser installed. It's what came with the ROM. I haven't installed anything else since doing the ROM.
I already flashed twice, got the same results each time.
However, after the flash but before it started installing updates, I ran Superuser, clicked Info, and the entire line above tap to check for updates was green. However, after allowing the first update to install, the line had the left side red:
-rwxr-xr-x root shell /system/xbin/su
It was the same after the third update. I wonder if something about those two updates is disabling root?
Naddict said:
You need cwm.. Flash It and you will profit....
Click to expand...
Click to collapse
Are you sure CWM is needed to get root? My understanding is you must have root before installing CWM?
novasource said:
Are you sure CWM is needed to get root? My understanding is you must have root before installing CWM?
Click to expand...
Click to collapse
Track down the team epic site that walks you through... You should be able to do those steps successfully... Here found link
http://forum.xda-developers.com/showthread.php?t=1743780
Sent from my SPH-L710 using xda premium
Naddict said:
Track down the team epic site that walks you through... You should be able to do those steps successfully... Here found link
http://forum.xda-developers.com/showthread.php?t=1743780
Click to expand...
Click to collapse
Thanks. Just to make sure, are you saying that the original instructions (in the thread linked at top) are wrong to suggest you have a rooted ROM if you haven't installed CWM?
Also, that would mean http://www.androidauthority.com/gal...ot-l710vpalen-stock-rom-flash-counter-103351/ is incorrect.
novasource said:
Thanks. Just to make sure, are you saying that the original instructions (in the thread linked at top) are wrong to suggest you have a rooted ROM if you haven't installed CWM?
Click to expand...
Click to collapse
CWM is used to install root and rooted roms. I have root for my wifes phone but I do not have CWM and all works fine. She actually would never use recovery but I do know how to flash one on there if necessary.
I am quite sure the tutorial is not incorrect and just a misunderstanding somewhere
playya said:
CWM is used to install root and rooted roms. I have root for my wifes phone but I do not have CWM and all works fine. She actually would never use recovery but I do know how to flash one on there if necessary.
I am quite sure the tutorial is not incorrect and just a misunderstanding somewhere
Click to expand...
Click to collapse
I'm scratching my head because there's not much to misunderstand here. The instructions are simple; either you've installed the ROM or you haven't. Since Superuser appeared for the first time after installing the ROM, and the phone prompted me to install two updates after installing, that tells me that the ROM installed correctly.
Wonderful. Just followed the instructions for installing CWM that were linked from http://www.androidauthority.com/gal...ot-l710vpalen-stock-rom-flash-counter-103351/. Not only did that not give me a working copy of CWM, that also made CUSTOM BINARY DOWNLOAD report Yes (1 counts).
novasource said:
Thank you!
I only have Superuser installed. It's what came with the ROM. I haven't installed anything else since doing the ROM.
I already flashed twice, got the same results each time.
However, after the flash but before it started installing updates, I ran Superuser, clicked Info, and the entire line above tap to check for updates was green. However, after allowing the first update to install, the line had the left side red:
-rwxr-xr-x root shell /system/xbin/su
It was the same after the third update. I wonder if something about those two updates is disabling root?
Click to expand...
Click to collapse
I see what your problem is. You're taking the OTA updates. Those erase /system/bin/su and unroot you. Before you take either OTA, install Voodoo OTA Rootkeeper from the Play Store, and back up your root. Then take both updates, reopen, Rootkeeper, and restore root.
No CWM needed.
EndlessDissent said:
I see what your problem is. You're taking the OTA updates. Those erase /system/bin/su and unroot you. Before you take either OTA, install Voodoo OTA Rootkeeper from the Play Store, and back up your root. Then take both updates, reopen, Rootkeeper, and restore root.
No CWM needed.
Click to expand...
Click to collapse
Good catch... Hard as hell to get knee deep into troubleshooting while driving
OP... If that. Doesn't work... http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
Sent from my SPH-L710 using xda premium
EndlessDissent said:
I see what your problem is. You're taking the OTA updates. Those erase /system/bin/su and unroot you. Before you take either OTA, install Voodoo OTA Rootkeeper from the Play Store, and back up your root. Then take both updates, reopen, Rootkeeper, and restore root.
No CWM needed.
Click to expand...
Click to collapse
YOU ARE CORRECT! I'll add that to the comments of http://www.androidauthority.com/gal...ot-l710vpalen-stock-rom-flash-counter-103351/. Thank you for the help.
EDIT: Voodoo OTA Rootkeeper doesn't work. More details later.
Bad news: While it is correct that the OTA updates are killing my root, Voodoo OTA Rootkeeper won't work. Even with it installed,
When you start the app, it says it is "useless" for "Samsung phones updated via KIES or Odin...".
Will check on alternatives.
novasource said:
Bad news: While it is correct that the OTA updates are killing my root, Voodoo OTA Rootkeeper won't work. Even with it installed,
When you start the app, it says it is "useless" for "Samsung phones updated via KIES or Odin...".
Will check on alternatives.
Click to expand...
Click to collapse
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
Have you tried this?
Naddict said:
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
Have you tried this?
Click to expand...
Click to collapse
I tried once using the instructions at .http://www.androidauthority.com/galaxy-s3-sph-l710-sprint-clockworkmod-recovery-99305/. Not only did it not install, it incremented my binary counter. Fortunately I was able to use Triangle Away to reset that.
I'm still not clear how CWM will help me. This is supposed to be a rooted ROM already. Not sure why I would need CWM.
novasource said:
I tried once using the instructions at .http://www.androidauthority.com/galaxy-s3-sph-l710-sprint-clockworkmod-recovery-99305/. Not only did it not install, it incremented my binary counter. Fortunately I was able to use Triangle Away to reset that.
I'm still not clear how CWM will help me. This is supposed to be a rooted ROM already. Not sure why I would need CWM.
Click to expand...
Click to collapse
It is a combo deal...It is not a ROM though...Try it...you may like it
this? http://www.youtube.com/playlist?list=PL7011CD883D5201B8&feature=view_all
Naddict said:
It is a combo deal...It is not a ROM though...Try it...you may like it
this? http://www.youtube.com/playlist?list=PL7011CD883D5201B8&feature=view_all
Click to expand...
Click to collapse
OK, I tried it, and it appears to work. I had to use Triangle Away to get rid of the binary counter increment.
It's important to note that I only got this to work by not using the "No Tripping Flash Counter" ROM.
novasource said:
OK, I tried it, and it appears to work. I had to use Triangle Away to get rid of the binary counter increment.
It's important to note that I only got this to work by not using the "No Tripping Flash Counter" ROM.
Click to expand...
Click to collapse
Good?!?
Sent from my SPH-L710 using xda premium
Naddict said:
Good?!?
Click to expand...
Click to collapse
Yes!
Im trying to root my n2 and odin gives this error, <ID:0/003> Can't open the serial(COM) port. What do I do? Also, my phone does not boot, it stays on the samsung screen.
You are in soft brick my friend, which I unfortunately i cant help you out of. I woukd edit your post and change the name to [Q] Soft Bricked Please Help....youll get more responses from smarter people than me. But dont worry, soft bricks are easily fixed....it just may take until the smart people wake up is all.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Probably going to need some more info. 1st, did you install the drivers prior to trying to root with Odin. 2nd, are you in download mode when Odin can't see the phone. 3rd, before attempting root did you do anything else to the phone. Let's start with that. Also try and pull the battery and boot the phone again to see if you continue to bootloop.
Also try a different cable
Sent from my SAMSUNG-SGH-I317 using xda premium
I followed this thread to the T. I ended up do a factory reset from the factory recovery. My phone boots now, and has su icon. Im not sure if it is really rooted though because the wifi tether app does not work and it asks me if Im rooted, not sure what state the phone is please reboot.
So you were successful with Odin or did you use another root method? Grab root checker from the market to see if you have root. If not, just grab CF's exploit apk to root or start over with auto root through Odin.
It says I do not have proper root access.
Here's the exploit apk thread. Use it to root then I would grab goo manager from the market to install twrp. After that, boot to recovery and make a backup.
http://forum.xda-developers.com/showthread.php?t=2050297
Will cwm touch work?
Sure. I just prefer twrp thats why I mentioned it. You can flash cwm with Odin or ROM manager, but I wouldn't use ROM manager for anything else. Do your backups and flashing manually in recovery.
So there is a chance my camera might not work? Also do I need to remove su from my current appst? I don't understand how this method linked above can be turned rooted access on and off? I please explain thx
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
The app takes advantage of an exploit to root. Rooting will not break your camera. If you use the patch after, it might. As far as Supersu...if you have the Superuser app, I would delete it as they are two different apps. If you have the Supersu then you can probably keep it. Most likely will overwrite it.
How do I delete su app? It will not uninstall through playstore. I guess I do not understand what the patch is. Ive never used a method like this.
The su app most likely installed as a system app so you can't remove it without root. Read through that thread I linked for more about the patch and the exploit. It would be too much to try to explain here. If you initially tried to use cf-auto root, then don't worry about removing su. It's the same developer and the same su app. Just use the app to root and apply the patch. Check your camera. If the screen is green then remove the patch to use the camera. It won't harm anything.
OK thanks for all the help. Hey, how do I unroot?
The supersu app can full unroot in settings.
Thats awesome! every root should be this simple. wifi tether still does not work. What do you recommend?
Wifi tether works for me natively, but I heard foxfi is good. No root needed for that one of course. Other than that I'm not too familiar with those apps.
playstore says foxfi is not available for my carrier. Are you paying for hotspot on your phone/?
Family bundle. It's included. I think you can grab foxfi from their website.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
At&t is probably blocking it in the playstore
Ok,
I know this is a hot question but I am hoping someone can point me in the right direction. Stupidly, in hindsight, I let KIES update my SGH-I747M to 4.3. After it rebooted, SuperSU/Triangle Away, etc would not load or work. So, I tried using ODIN to put 4.1.2 back on but all attempts have failed so far as my counters are now at 3 and state is custom. Normally , I would run TriangleAway and all would be good. But SuperSU will no longer load and stick around so that I can run TriangleAway. I have not tried any other custom ROMs yet.
I have also used the latest SuperSU v1.80 but it does not stay installed and I cannot use Triangle Away to reset the counters. Anyone have any ideas on how to get SuperSU to work? That would allow me to reset the warnings and all would be great.
Marsch52 said:
Ok,
I know this is a hot question but I am hoping someone can point me in the right direction. Stupidly, in hindsight, I let KIES update my SGH-I747M to 4.3. After it rebooted, SuperUS/Triangle Away, etc would not load or work. So, I tried using ODIN to put 4.1.2 back on but all attempts have failed so far. I have not tried any other custom ROMs yet.
I have also used the latest SuperUS v1.80 but it does not stay installed and I cannot use traingle Away to reset the counters.
Anyone have any ideas on how to get SuperUS to work? That would allow me to reset the warnings and all would be great.
Click to expand...
Click to collapse
You have to re root your phone. Use cf auto root and when that's done find superSU in the play store and install/update it. Then open SUPERSU and when it asks you to disable knox say yes. Also update its binaries. Now you have root and you can use any root application you want.
Sent from my SGH-I747M using Tapatalk
Florad77 said:
You have to re root your phone. Use cf auto root and when that's done find superSU in the play store and install/update it. Then open SUPERSU and when it asks you to disable knox say yes. Also update its binaries. Now you have root and you can use any root application you want.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
Ok... I see the path. just want to know where I can find the proper "cf auto root" files for the SGH-I747M. I will search the web again, but if you happen to have a pointer that would be great.
:fingers-crossed:
Success . . . . .
Marsch52 said:
Ok... I see the path. just want to know where I can find the proper "cf auto root" files for the SGH-I747M. I will search the web again, but if you happen to have a pointer that would be great.
:fingers-crossed:
Click to expand...
Click to collapse
I just did as you said and it updated SuperSU by itself, turned of KNOX and Voila!!!!!! :good: :good: :good:
THANK YOU!!!!!!! and Chainfire....need to donate to him for his excellent work
Florad77 said:
You have to re root your phone. Use cf auto root and when that's done find superSU in the play store and install/update it. Then open SUPERSU and when it asks you to disable knox say yes. Also update its binaries. Now you have root and you can use any root application you want.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
I just did this and it keeps telling me "Unfortunately, SuperSU has stopped. And I'm pretty sure knox is preventing it..
NEVERMIND! Apparently it didn't update SuperSU automatically. Now it updated, normally updated binaries, rebooted, and checked root with Titanium Backup. All's good!
I know there are a ton of other threads regarding Knox out there, I have read more than a few, but I am still having trouble. I have a SPH-L900 (Galaxy Note 2 from Sprint). I recently made the move to 4.3. Prior to this I had 4.1.2 and was Rooted but did not have any custom ROM. I did have a custom recovery, TWRP. I took my device back to stock using a toolkit which I had used to root it in the first place. I then used Kies to upgrade to 4.3. I then proceeded to attempt to root my phone again using CF-Autoroot. It worked but of course Knox reared its ugly head. This sent me searching for how to disable it. Almost everything I tried didn't work. In fact, at one point I thought I totally screwed up my device but was able to find a stock ROM that worked with ODIN. So, I am back to stock 4.3. Here comes my question.
I saw many different methods and options for the N7100/N7150 but things seem to be a little light when it comes to the SPH-L900. How can I root my phone and disable or remove Knox? Most of the methods I saw seem to need root access which Knox is blocking, thus you end up in a loop. The app needs access to remove Knox but Knox won't let it have access. There must be a way to do it, I am just tired of reading forum posts, I just don't have that much time. If anyone has some thoughts or can assist me I would greatly appreciate it.
Thanks.
P.S. Knox is ob-knox-iuos. Like Windows User Account Control.
I used the program kingo root, to root the phone and it also installs supersu. Once thats done simply install root explorer and delete knox related files. Use Odin to flash custom recovery done.
Sent from my SPH-L900 using xda app-developers app
skye206 said:
I used the program kingo root, to root the phone and it also installs supersu. Once thats done simply install root explorer and delete knox related files. Use Odin to flash custom recovery done.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Ok, I will give Kingo Root a try. The problem I find though is that even once my phone is rooted, I try to use Root Explorer or anything else like that and Knox blocks the request for super user authority. Does Kingo Root do something different to allow Root Explorer a chance to do its thing before Knox can block it? I mean I WAS successful in rooting my phone or it seemed I was but Knox kept blocking that super user request. I think it also hides superSU so I couldn't even open SuperSU like the one method said to be able to remove Knox. Knox blocked SuperSU from even opening. I will try your method though and see if I have any luck. Thanks.
Draeconix said:
Ok, I will give Kingo Root a try. The problem I find though is that even once my phone is rooted, I try to use Root Explorer or anything else like that and Knox blocks the request for super user authority. Does Kingo Root do something different to allow Root Explorer a chance to do its thing before Knox can block it? I mean I WAS successful in rooting my phone or it seemed I was but Knox kept blocking that super user request. I think it also hides superSU so I couldn't even open SuperSU like the one method said to be able to remove Knox. Knox blocked SuperSU from even opening. I will try your method though and see if I have any luck. Thanks.
Click to expand...
Click to collapse
Indeed, your method worked. I was able to get rooted and delete all the Knox files. The only weird thing is Kingo Root still says Waiting for Device but it appears everything is done. I pulled the USB cable and it did nothing. It has been like that for several minutes so not sure what to make of that. Maybe just a glitch.
For reference here is a list of where the Knox Files are.
http://forum.xda-developers.com/showthread.php?t=2514703
Draeconix said:
Indeed, your method worked. I was able to get rooted and delete all the Knox files. The only weird thing is Kingo Root still says Waiting for Device but it appears everything is done. I pulled the USB cable and it did nothing. It has been like that for several minutes so not sure what to make of that. Maybe just a glitch.
For reference here is a list of where the Knox Files are.
http://forum.xda-developers.com/showthread.php?t=2514703
Click to expand...
Click to collapse
What version of root explorer did you use to delete the knox files? My buddy has this phone ( I'm on S4) and just rooted his phone and has the knox issue. We tried to delete it with root toolbox pro, and it just says deleting and goes on forever without deleting. He tried the free version of root explorer and it says it is a read only file and won't let him delete it. I have been able to avoid the knox issue on my phone, and am loaded on kitkat. We can use TB either because it requires root privilages, and of course knox is blocking supersu.
btvolta said:
What version of root explorer did you use to delete the knox files? My buddy has this phone ( I'm on S4) and just rooted his phone and has the knox issue. We tried to delete it with root toolbox pro, and it just says deleting and goes on forever without deleting. He tried the free version of root explorer and it says it is a read only file and won't let him delete it. I have been able to avoid the knox issue on my phone, and am loaded on kitkat. We can use TB either because it requires root privilages, and of course knox is blocking supersu.
Click to expand...
Click to collapse
Actually I used ES Explorer. If you use this app you need to turn on Root Explorer. Hit your Menu button which will pop out a side bar on the left. Scroll down to Root Explorer and flip the switch.
I suggest starting from a fresh flash of stock ROM. Then use Kingo Android Root. Let your phone reboot and then go right to ES Explorer and delete files. Reboot if you want and you should be Knox free. If not then I am not sure where to go. As you see from my OP, I did try a lot of different methods. One thing to also make sure of is the exact model of the phone. Some methods don't work for some models. Hope this helps.
Draeconix said:
Actually I used ES Explorer. If you use this app you need to turn on Root Explorer. Hit your Menu button which will pop out a side bar on the left. Scroll down to Root Explorer and flip the switch.
I suggest starting from a fresh flash of stock ROM. Then use Kingo Android Root. Let your phone reboot and then go right to ES Explorer and delete files. Reboot if you want and you should be Knox free. If not then I am not sure where to go. As you see from my OP, I did try a lot of different methods. One thing to also make sure of is the exact model of the phone. Some methods don't work for some models. Hope this helps.
Click to expand...
Click to collapse
Thanks for the info, but I just went a head and odin'd twrp and then flashed a custom Rom for him, so all is well now. I am on the S4 and didn't ever accept the 4.3 ota, so never had to deal with knox.
such confuse
skye206 said:
I used the program kingo root, to root the phone and it also installs supersu. Once thats done simply install root explorer and delete knox related files. Use Odin to flash custom recovery done.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Draeconix said:
Actually I used ES Explorer. If you use this app you need to turn on Root Explorer. Hit your Menu button which will pop out a side bar on the left. Scroll down to Root Explorer and flip the switch.
I suggest starting from a fresh flash of stock ROM. Then use Kingo Android Root. Let your phone reboot and then go right to ES Explorer and delete files. Reboot if you want and you should be Knox free. If not then I am not sure where to go. As you see from my OP, I did try a lot of different methods. One thing to also make sure of is the exact model of the phone. Some methods don't work for some models. Hope this helps.
Click to expand...
Click to collapse
Will this trip the KNOX "voided warranty" counter? I am on fresh 4.3 OTA MK4, and I want to be sure not to trip the setting since it is not already tripped. I have been reading many threads for hours now. Am I mistaken, and I need to go back to MC2 before I can do this? Or can I really just use Kingo Android Root, then ES and delete the KNOX files? Or does it only trip the KNOX counter when you flash a custom recovery, which we are not doing in this particular method?
Thanks for any info/clarification
I've got a friend with an AT&T Note 2 with the latest 4.4.2 OTA. He wants to root so he can backup and transfer everything to a new device. I'm assuming towelroot won't do the trick since it's an Exynos CPU, but will Chainfire's auto root still work? I'm assuming Knox is on the newest OTA and wasn't on it originally when CFAR was released. I searched, but I don't see anything recent about rooting, and I just want to be relatively assured of not bricking him. Any help is appreciated.
tedkord said:
I've got a friend with an AT&T Note 2 with the latest 4.4.2 OTA. He wants to root so he can backup and transfer everything to a new device. I'm assuming towelroot won't do the trick since it's an Exynos CPU, but will Chainfire's auto root still work? I'm assuming Knox is on the newest OTA and wasn't on it originally when CFAR was released. I searched, but I don't see anything recent about rooting, and I just want to be relatively assured of not bricking him. Any help is appreciated.
Click to expand...
Click to collapse
Towel root will NOT work. Cf auto root will. It's the method I used. You may need to manually install the latest super user and after.
As stated above. . Use CF....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Ok I used cf auto root and it seems to have worked except as soon as my phone reboots I get "Unfortunately SuperSU has stopped"......now what I'm a Lil confused....it's there...just doesn't work.
I'm on official 4.4.2
Shortbus-Driver said:
Ok I used cf auto root and it seems to have worked except as soon as my phone reboots I get "Unfortunately SuperSU has stopped"......now what I'm a Lil confused....it's there...just doesn't work.
I'm on official 4.4.2
Click to expand...
Click to collapse
Now just install supersu from the play store and then go to the app after you download it and if it says to update it do it and you'll be fine
Shortbus-Driver said:
Ok I used cf auto root and it seems to have worked except as soon as my phone reboots I get "Unfortunately SuperSU has stopped"......now what I'm a Lil confused....it's there...just doesn't work.
I'm on official 4.4.2
Click to expand...
Click to collapse
Many people have encountered that problem.
here's the solution
marckusdavis said:
Sorry, I need to make sure I fully understand this too. So you have an SGH-i317 and were rooted. You installed the OTA update to 4.4.2 which unrooted you. Then you ran CF-AutoRoot and were able to successfully re-root on 4.4.2?
UPDATE:
Well, after reading another post where this worked, I decided to give it a try. It seemed to work, but then I get the message "Unfortunately SuperSU has stopped". I tried the solution using ES File Explorer to reinstall SuperSU.apk to no avail and there is no "UPDATE" button in Google Play, only OPEN, ENABLE or DISABLE so I can't update the binary. Any help would be greatly appreciated!
UPDATE 2:
Got it working, sort of! Since rooting seemed to work, but the old binary for SuperSU kept stopping, I downloaded the updated SuperSU zip file from here and then used ES File Explorer to look into the zip and find and run/install the Superuser.apk file. That works, but it does not appear to survive a reboot, so for each reboot I have to redo this process. Good enough work-around for now though as I'm sure there will be a complete solution down the road.
UPDATE 3 (probably final):
Was able to use the "Clean up for reinstallation from Google Play" option in the SuperSU settings. After reboot, Google Play then gave me the option to Install SuperSU which I did. It now survives reboot and it also, FINALLY, disabled the stupid Knox (which from what I read, was the cause of all of these problems in the first place. You have to be quick with the fingers though because as soon as SuperSU gave the option to disable Knox, a second later Knox closed it. I had to fire up SuperSU again and then click the disable Knox OK button IMMEDIATELY to kill it). I'm a happy, rooted Note 2 user on KitKat now! Hope all of this info. is helpful to someone else.
Click to expand...
Click to collapse
terpin32 said:
Now just install supersu from the play store and then go to the app after you download it and if it says to update it do it and you'll be fine
Click to expand...
Click to collapse
Cf auto root already installed supersu as a system app and market only gives the option to "open" it....I do not have root access and therefore can't unistall nor remove it ....lol this is frustrating. ...
I've never had this much problems and I currantly have an s4 and have had pretty much the entire "S" line starting from the Vibrant :-/
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
SockmanTGR said:
Many people have encountered that problem.
here's the solution
Click to expand...
Click to collapse
All that isn't making any sense either I'm afraid.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Shortbus-Driver said:
Cf auto root already installed supersu as a system app and market only gives the option to "open" it....I do not have root access and therefore can't unistall nor remove it ....lol this is frustrating. ...
I've never had this much problems and I currantly have an s4 and have had pretty much the entire "S" line starting from the Vibrant :-/
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
All that isn't making any sense either I'm afraid.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The solution I stated above works. try it. I had the same problem and that solved it.
Solved just had to get cwmr installed and flash a rom with root on it.