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
Related
This has been replaced by Universal Root de la Vega!
Question & Answer
"Root de la Vega" What kind of name is that?
It's named after Ralph de la Vega, CEO of AT&T Mobility.
Can I flash custom recovery/kernel/rom without tripping KNOX flags?
No, Flashing a custom ROM will trip the flag
No, Flashing a custom Kernel will trip the flag
No, Flashing a custom Recovery will trip the flag
Will this set a tripped KNOX flag 0x1 back to 0x0?
No.
Can you help me with the drivers?
No, but you can head over here for help with drivers.
How do I get into download mode?
Method 1: adb reboot download
Method 2: Pull the battery out, unplug the usb cable, reinsert the battery. Hold Volume Down + Home + Power. Follow the instructions on the screen.
Will rooting or downgrading or flashing stock trip the Knox flags?
No, KNOX flags will not be tripped!
Will root survive a factory reset?
Yes, it does.
Will root survive an OTA update?
The Sprint Note 3 has survived an OTA update, you only need to perform the sdcard steps again to get root. However, you should NOT take OTA updates, it is possible for them to patch the root method with an OTA update.
Do I need have to fully wipe my phone when rooting?
Yes. If you don't you will get lots of nasty force closes. I have yet to find a way around it.
Does Xposed Framework work?
Yes, it has been updated to work fully with the Note 3.
Will rooting report system as custom and display an unlocked lock on the initial boot screen?
Yes. It can be removed by installing Xposed Framework with Wanam Xposed and enabling Security hacks > Fake system status.
Titanium Backup is giving me problems, how can I fix it?
Check out this thread. If you are still having issues, please take your concerns to the dev, they are not related to rooting.
How do I open a 7z file?
With 7zip or IZArc!
Can I do this on OS X/Linux?
No, not until heimdall is updated to support the Note 3.
Can I unroot?
Yes, use SuperSU full unroot option or flash stock.
I am getting a "Prevention Information" popup after running a root app, how do I disable it?
From terminal emulator or adb shell as root, run; pm disable com.sec.knox.seandroid
Or freeze the Knox apps with Titanium Backup.
I am getting Force Closes after flashing, how can I fix it?
Make sure you are flashing the CSC file! If you are, try flashing AP and CSC separately.
Good stuff. did this yesterday and it worked like a charm.
Thank you so much!
just to confirm, i can remove/freeze system apps, run ad blocker, xposed, etc, with just root, right? I have never not fully "unlocked" a device and just stayed with the stock ROM. So just want to confirm before using this. And thanks btw for your hard work on this.
And one last one...Im pretty sure I wont be able to get OTA's so how would one go about updating once an OTA has been released without tripping knox?
EDIT: I just saw the 2nd post with all the FAQ...some reason it didnt show before until after I posted. But still wondering about the OTAs
droidkevlar said:
just to confirm, i can remove/freeze system apps, run ad blocker, xposed, etc, with just root, right? I have never not fully "unlocked" a device and just stayed with the stock ROM. So just want to confirm before using this. And thanks btw for your hard work on this.
And one last one...Im pretty sure I wont be able to get OTA's so how would one go about updating once an OTA has been released without tripping knox?
Click to expand...
Click to collapse
You can do all of that fun stuff with root
I am unsure on the OTAs, haven't had any roll out yet.
I can also confirm, worked like a charm. Did it today, and didn't lose any data. Phone was how it was pre root, but with added SU goodness.
Sent from my Psion 5mx
Hey designgears,
Nice to see you're still at it. Your old Cognition ROM (eclair iirc) was one of the first ROMs I ran on my SGS1 Captivate, years ago, before I settled on CyanogenMod. Didn't see you in SGS3-land, but here you are again with the Note3. Hey-ohhhh.
Thanks.
Rooted through this method today. It worked like a charm. Now my Note 3 feels invincible. Thank you!
Sent from my SM-N900T using xda app-developers app
Ok. Here we go. I've been on android for a long time and never heard of KNOX. What the hell is this and do we need it?
Sent from my XT1056 using Tapatalk now Free
EDIT: I forgot--Google is my friend. Nvm
I'm sorry if this is too off topic but, while it IS wonderful to have a root method like this and I'm VERY grateful for it, most of what I read online states that a custom recovery will mess with knox and cause issues. I dint know if I could keep an android phone and not flash custom roms! I'm still within my return window with t mobile (I'm coming from Sprint) and I'm actually thinking about trading for a nexus 4. Hope we get a functioning recovery soon!
Sent from my XT1056 using Tapatalk now Free
Any difference between this and the root method from here:
http://forum.xda-developers.com/showthread.php?t=2481330
Any reason for someone who has rooted using the other method to redo it with this one?
Thanks
hdad2 said:
Any difference between this and the root method from here:
http://forum.xda-developers.com/showthread.php?t=2481330
Any reason for someone who has rooted using the other method to redo it with this one?
Thanks
Click to expand...
Click to collapse
Same thing
Sent from my SM-N900T using xda app-developers app
hdad2 said:
Any difference between this and the root method from here:
http://forum.xda-developers.com/showthread.php?t=2481330
Any reason for someone who has rooted using the other method to redo it with this one?
Thanks
Click to expand...
Click to collapse
This process is a little different from the way I did it too. What is the purpose of the additional CSC file? Should I reroot using this new method?
jimmydigital00 said:
This process is a little different from the way I did it too. What is the purpose of the additional CSC file? Should I reroot using this new method?
Click to expand...
Click to collapse
+1
Sent from my SM-N900T using XDA Premium 4 mobile app
jimmydigital00 said:
This process is a little different from the way I did it too. What is the purpose of the additional CSC file? Should I reroot using this new method?
Click to expand...
Click to collapse
No need to root again, I just separated the two files.
This worked like a charm. Thanks DG!
Sent from my SM-N900T using XDA Premium 4 mobile app
Finall got all files downloaded gonna flash tomorrow after work Thank you so very much designgears, chainfire and all testers for the hard work that brought us root to the G-Note 3 you guys snd XDA are unstoppable!!!
:thumbup:
Sent from my SGH-T889 using XDA Premium 4 mobile app
Works perfectly. Donated!
I can also confirm that if you bork stuff while rooted, you can Odin the stock rom over everything and start over without throwing the Knox flag.
I know that flashing a custom recovery or custom ROM will trip the KNOX counter...BUT...
1. is it possible to adb sideload (after Root de la Vega)?
and...
2. if you CAN adb push and pull, can we pull the framework-res.apk, modify it to our liking and push it back...or will this be the same as flashing a custom ROM which will trip KNOX?
I am curious because I'd like to enable unlimited wifi tethering like I did on my old Galaxy S III by creating a flashable zip (however with Note 3 I wouldn't make it flashable, just push)
Thanks for your work putting this together.
It was real easy to do, and root certainly is appealing. One thing I need is device-level encryption, and that is so far unavailable on a rooted N3.
I've even tried Xposed Framework with Wanam Xposed, and checked System status via TriangleAway:
Counter = 0
Binary = Official
System = Official
But somehow device still won't encryp. Back to stock I go (a 3rd time)...
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
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!
Keep in mind that if you follow this method, you are tripping the knox flag to a 0x1. This completed voids your warranty and until this moment there's no possible way to research back to a 0x0.
I used Oden to apply the Chainfire root. After rebooting, Knox told me it prevented an unauthorized app from accessing secure area of the phone. Then SuperSU FC'ed. I went to play, updated it SuperSU, and opened it. After a brief pause, it asked "Do you want to disable Knox?". I pondered that question intently, and in about 10ms, answered OF COURSE! It the successfully disabled knox.
After, go into the play store, and download "Rom Manager". Open it up, and click on the first tab. "Recovery Setup" (Even if it says that you already have CWM recovery installed, still do these steps) After clicking on that tab, on the list "Install or Update recovery" Click on ClockwordMod Recovery. Then click on our device name. A box will pop up suggesting you have Wi-Fi (If you're not already on it), just click OK. And then it'll automatically download it and flash it. There you go.
Sorry if this has already been posted. People might think that there is a different way to root 4.3, just here to help.
Took part of this from erkme73
Thanks .. worked like a charm
Thanks a lot. This method worked for me and very quickly! Thanks!
Thnaks for testing this out. This method worked for me. I had the old CFautoroot before and it didn't work for me, so after downloading the CFautoroot that's specifically for t-mo version, this worked for me.
I didn't even have to go and download a custom recovery. I managed to have the stock recovery on.
Previous to 4.3 I flashed Robinson's stock root-injected 4.1.2 rom. Would this method work for me? And can I skip the CWM recovery part?
ungraph said:
Previous to 4.3 I flashed Robinson's stock root-injected 4.1.2 rom. Would this method work for me? And can I skip the CWM recovery part?
Click to expand...
Click to collapse
If you use ODIN to flash the 4.3 stock, then you'll lose root, and then you'll have to do this method to get root back. You already have root. Wait until Mr. R puts out the root injected 4.3 so you won't lose your root.
nmw407 said:
If you use ODIN to flash the 4.3 stock, then you'll lose root, and then you'll have to do this method to get root back. You already have root. Wait until Mr. R puts out the root injected 4.3 so you won't lose your root.
Click to expand...
Click to collapse
I flashed Robinson's stock root-injected 4.1.2 via Odin and I installed the 4.3 update via Kies yesterday so I lost root. I was wondering if this method would work for me.
It worked for me through ODIN. My mistake was using the old CFautoroot that was for the note 2 international. Once I used the one for t-mo, it all worked exactly as the OP stated - I stopped before the recovery installation since I didn't need TWRP or CWM
is it possible to be rooted and still use knox?
nmw407 said:
It worked for me through ODIN. My mistake was using the old CFautoroot that was for the note 2 international. Once I used the one for t-mo, it all worked exactly as the OP stated - I stopped before the recovery installation since I didn't need TWRP or CWM
Click to expand...
Click to collapse
Just did exactly what you said and it works! I gained root on stock 4.3.
bones718 said:
is it possible to be rooted and still use knox?
Click to expand...
Click to collapse
From what I have seen with my phone NO... But hey still very early. The root method here is great. I found that I had to also uninstall Knox completly with TiBu and seems to hold. I found booting back into recovery even with Knox on Freeze it still would interfere ... Just my limited experience speaking here also.
Thanks again for the root method. Seems 4.3 is pretty smooth, I installed exposed and Wanam and all is good, Also flashed Devil Kernel and good good so far.:victory:
youStolemylaptop said:
There you go.
Sorry if this has already been posted. People might think that there is a different way to root 4.3, just here to help.
Took part of this from erkme73
Click to expand...
Click to collapse
Worked like a charm. Thanks for posting the steps!
This method works but i did a master reset to start "fresh" after rooting and i got on the Tmobile 4g lte screen loop.
Any ideas?
lmarranzino said:
From what I have seen with my phone NO... But hey still very early. The root method here is great. I found that I had to also uninstall Knox completly with TiBu and seems to hold. I found booting back into recovery even with Knox on Freeze it still would interfere ... Just my limited experience speaking here also.
Thanks again for the root method. Seems 4.3 is pretty smooth, I installed exposed and Wanam and all is good, Also flashed Devil Kernel and good good so far.:victory:
Click to expand...
Click to collapse
What do you meant by interfere?
DKM119 said:
This method works but i did a master reset to start "fresh" after rooting and i got on the Tmobile 4g lte screen loop.
Any ideas?
What do you meant by interfere?
Click to expand...
Click to collapse
Mine hung on that screen for longer than I wanted (started getting nervous) but eventually the phone finished loading up
Sent from my SGH-T889 using xda app-developers app
Keep in mind that if you follow this method, you are tripping the knox flag to a 0x1. This completed voids your warranty and until this moment there's no possible way to revert back to a 0x0. This means you can't downgrade your firmware and if you try, even via Odin, it wouldn't let you and lock your phone. Just a heads up. OP shouldve posted this in the post but if you don't mind flashing custom rooms etc, then by all means go ahead.
ungraph said:
Keep in mind that if you follow this method, you are tripping the knox flag to a 0x1. This completed voids your warranty and until this moment there's no possible way to research back to a 0x0. This means you can't downgrade your firmware and if you try, even via Odin, it wouldn't let you and lock your phone. Just a heads up. OP shouldve posted this in the post but if you don't mind flashing custom rooms etc, then by all means go ahead.
Click to expand...
Click to collapse
I'll edit it in right now to let everyone know.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
it's work on my NOTE2
Thanks
I thank the OP for updating the post to reflect the Knox issue... but I think anyone with a Note 2 should have already been aware of such issues when rooting. Even if they weren't around for the "modified/binary count/triangle away" disscussions... those that did root, still had to deal with those issue and heard all about them... and now that we've headed towards that next phase of OTA's... it's hard to think anyone has not seen/heard/read something on Knox itself... I can hardly go 5 topics without seeing something related to Knox posted within the first 2 pages... I commend the OP for updating... but how can people be so careless with a phone that cost $400-700. Especially when the first rule of xda is "read first" followed by rule two "at your own risk"
Ultimately, I tripped out about the whole "modified status won't allow OTA's / void warranty" at first and in the end it was patched... I hope for everyone's sake, this gets the same solution... like Coug, I'm holding out for the moment, but I do have faith
Sent from my SGH-T889 using xda app-developers app
PhxDroid86 said:
I thank the OP for updating the post to reflect the Knox issue... but I think anyone with a Note 2 should have already been aware of such issues when rooting. Even if they weren't around for the "modified/binary count/triangle away" disscussions... those that did root, still had to deal with those issue and heard all about them... and now that we've headed towards that next phase of OTA's... it's hard to think anyone has not seen/heard/read something on Knox itself... I can hardly go 5 topics without seeing something related to Knox posted within the first 2 pages... I commend the OP for updating... but how can people be so careless with a phone that cost $400-700. Especially when the first rule of xda is "read first" followed by rule two "at your own risk"
Ultimately, I tripped out about the whole "modified status won't allow OTA's / void warranty" at first and in the end it was patched... I hope for everyone's sake, this gets the same solution... like Coug, I'm holding out for the moment, but I do have faith
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
In a perfect world this is completely true, but this isn't a prefect world. Most the post I see about Knox is "what is Knox" instead of people searching. That's why we have so many people already bootlooping trying to go back to 4.1. I'm glad the op updated the Knox warranty but because I'm pretty sure there will be some people shocked by theirs being tripped.
On a side not Vroot and kingo will root without messing up the Knox. Just Google them. They were removed from xda because some suspicion of virus, but I didn't have s problem
Sent from my SGH-T889 using xda app-developers app
So if you flash Mr. Robinson's stock root injected update you lose root. He has ripped out knox so if you use this method, you shouldn't have any issues and regain root?
Hi I am new to this forum and a casual user. I wanted to root my note 2 tmobile android version 4.3 and actually rooted it once but knox created a lot of problem. I could not even launch titanium backup to freeze knox. Or was completely unable to disable knox. Now as android 4.3 has been released for quite a few months. Does anyone know of a method which will root my galaxy note 2 tmobile (SGH-T889) for sure and let me completely disable knox? If so please give me step by step instruction of rooting my device or alteratively you can provide me a link of the instruction so I can root my note 2 phone. I appreciate your help.
cooljd1 said:
Hi I am new to this forum and a casual user. I wanted to root my note 2 tmobile android version 4.3 and actually rooted it once but knox created a lot of problem. I could not even launch titanium backup to freeze knox. Or was completely unable to disable knox. Now as android 4.3 has been released for quite a few months. Does anyone know of a method which will root my galaxy note 2 tmobile (SGH-T889) for sure and let me completely disable knox? If so please give me step by step instruction of rooting my device or alteratively you can provide me a link of the instruction so I can root my note 2 phone. I appreciate your help.
Click to expand...
Click to collapse
cf auto root should work for root. what did you use to root? if you are rooted install a custom recovery and flash a knoxfree rom from the dev section
Flash CF auto root via Odin then download latest superuser from play store and you are ready to go.
All credits to ChainFire
Did you try this method, if so did it work for you? Im having similar issues with my tmobile note 2 running 4.3 too. I'd appreciate it, thanks in advance...
Sent from my SGH-T889 using XDA Premium 4 mobile app
J3D1mineTR1X said:
Did you try this method, if so did it work for you? Im having similar issues with my tmobile note 2 running 4.3 too. I'd appreciate it, thanks in advance...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just as a suggestion, something that happened to me while playing around with the phone: if you're running Stock rom and then flash a custom recovery via Odin (I used Philz Touch) upon booting on recovery just to wipe cache/dalvik I found something interesting: my phone wasn't rooted, so when chosing the option "reboot system now" a message that said something like "root is broken, would you like to root your phone before rebooting" appeared. I was curious, as I normally use a website called Kingo root that does it in a one-click kinda way. When I chose Yes in the recovery, upon booting my phone it was rooted. After, I just intalled Chainfire's SuperSU from the play store and it was all good.
It's worth trying I believe.
Cheers
Sobaro said:
Flash CF auto root via Odin then download latest superuser from play store and you are ready to go.
All credits to ChainFire
Click to expand...
Click to collapse
wavv.drama said:
Just as a suggestion, something that happened to me while playing around with the phone: if you're running Stock rom and then flash a custom recovery via Odin (I used Philz Touch) upon booting on recovery just to wipe cache/dalvik I found something interesting: my phone wasn't rooted, so when chosing the option "reboot system now" a message that said something like "root is broken, would you like to root your phone before rebooting" appeared. I was curious, as I normally use a website called Kingo root that does it in a one-click kinda way. When I chose Yes in the recovery, upon booting my phone it was rooted. After, I just intalled Chainfire's SuperSU from the play store and it was all good.
It's worth trying I believe.
Cheers
Click to expand...
Click to collapse
+wavv.drama
I have a question. If you don't run odin as a administrator do you get this error message: Windows cannot access the specific device path or file. You may not have the appropriate permissions to access. The last time I tried to root my phone i didn't run odin in administrator mode. I'm just finding out about this recently. I have all of the files installed on the computer and ready. Odin, recovery, keis, and supersu zip on sd card. Im just trying to figure out why I got that error message. Any ideas or suggestions would be appreciated. Thanks in advance... Awaiting your response...
"What good is knowledge if it's not to be shared"...
Sent from my SGH-T889 using XDA Premium 4 mobile app
J3D1mineTR1X said:
+wavv.drama
I have a question. If you don't run odin as a administrator do you get this error message: Windows cannot access the specific device path or file. You may not have the appropriate permissions to access. The last time I tried to root my phone i didn't run odin in administrator mode. I'm just finding out about this recently. I have all of the files installed on the computer and ready. Odin, recovery, keis, and supersu zip on sd card. Im just trying to figure out why I got that error message. Any ideas or suggestions would be appreciated. Thanks in advance... Awaiting your response...
"What good is knowledge if it's not to be shared"...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The only answer that pops up in my mind would be that you weren't running Odin as an administrator, like you mentioned. Maybe try running Odin as an admin, or alternatively (and I haven't tried this myself but Chainfire's thread gives a good step-by-step and people in the forum do help) use mobile Odin ------> http://forum.xda-developers.com/showthread.php?t=1347899. The first time I wanted to root my phone I was having issues too, not being able to do it because of lack of experience. I stumbled upon this website: http://www.kingoapp.com/. Check it out, if you would like. This kingo app is a downloadle app (kind of like Odin) that Roots yourm phone alone, without needing to flash anything. The step-by-step's are there, just turn on your developer options and then turn on USB debugging. I personally rooted A Galaxy Tab, SIII, a Note I i717 and an Asus MemoPad with that website and it worked perfectly for me. Rooting via custom recovery is something that I learned recently, and by chance. I do not know whether it trips the Knox counter or not to be honest with you, to me it doesn't make a difference since I will not be returning any of the devices I rooted, After rooting the phone like so you could potentially download mobile Odin from Chainfire's thread and then use Odin without needing to use your computer.
Hope this helps
+wavv. Drama
Yeah that was it, i rooted it earlier today. I do have another question for you. I ran root checker pro and it says I'm rooted. I tried to install busybox but it said remove supersu permissions reinstall supersu and to delete and reinstall busybox. Also the adb shell doesn't have root access either. So is that a common occurrence, or is it the norm after rooting and installing custom recovery? Awaiting your reply. Thanks in advance...
What good is knowledge if it's not to be shared...
Sent from my SGH-T889 using XDA Premium 4 mobile app
Sorry for the late reply, hadn't been to the forum in a minute. To be honest with u, I don't know for sure. I haven't personally yet served myself from adb so I can't tell u. However, the reason why you received that response from busybox may be because when u were partially rooted it gained root access (if it ever did, I only assume).
Try what was asked of u and I'm sure busybox will work no problems. Also, if u have the terminal emulator apk try entering the command "root" (without the ") and if u gain roots access it will definitely mean you are rooted for sure.
What do you want to use adb for, if I may ask?
Sent from my SGH-T889V using XDA Premium 4 mobile app