Develop Bugs

[Q] Set Warranty Bit: Kernel

First thread = noob question
Hi, what exactly does mean: "Set warranty Bit: Kernel" after root?
(Using the search function I couldn't find it)
Thanks

reply
PansenJim said:
First thread = noob question
Hi, what exactly does mean: "Set warranty Bit: Kernel" after root?
(Using the search function I couldn't find it)
Thanks
Click to expand...
Click to collapse
Same question here. It isn't a tragic issue, but still annoying on boot.

Same here
Same here, it's OK but if there's any way to get rid of this, I'd be glad :good:

Is there any way too get rid of that annoying message? After I root, and install custom recovery it appears on every boot and even when I enter in recovery is annoying -.-

rolo143 said:
Is there any way too get rid of that annoying message? After I root, and install custom recovery it appears on every boot and even when I enter in recovery is annoying -.-
Click to expand...
Click to collapse
Only way is to flash back stock firmware = loose root.

ladislav.heller said:
Only way is to flash back stock firmware = loose root.
Click to expand...
Click to collapse
Baseband will loose too.-_-!

So there's no way to have custom recovery + root without having that message.. right? Or at least for now. ..
Sent from my GT-I9195L using Tapatalk

ladislav.heller said:
Only way is to flash back stock firmware = loose root.
Click to expand...
Click to collapse
Yea ok. But Knox wont let you flash back to stock.
I tried.
The messages are from Knox.
Its to tell Tmobile we modified the phone...
Dont you just love Samsung now?

rolo143 said:
Is there any way too get rid of that annoying message? After I root, and install custom recovery it appears on every boot and even when I enter in recovery is annoying -.-
Click to expand...
Click to collapse
No one mentions which JB but if you upgrade or re-install Chainfire's Super SU, I believe current is 1.80, upon installation it will mention Knox asking annoying questions and do you wish to disable Knox. Answer OK, and it will do so upon re-establishing root. You can go into System/apps and rename, move or delete the Knox apps, I suggest 'rename' if you are new to this. (just add .bak to .apk's) Use Root Explorer or ES File Explorer as R/W root and you should be OK.
EDIT: Knox files to rename or whichever, KNOXAgent.apk KNOXStore.apk ContainerAgent.apk
ie: rename Knox...xx.apk.bak
I create a directory on the Ext SD, /App_Bak and just move what I de-bloat or don't need while testing, that way I have them if needed later.

I rooted using the old method, by flashing custom recovery first, then flashing the zip file "rootkit" and then having Superuser.apk on my phone. It worked even with the latest firmware, but now I have that yellow message thing. .
Sent from my GT-I9195L using Tapatalk

rolo143 said:
I rooted using the old method, by flashing custom recovery first, then flashing the zip file "rootkit" and then having Superuser.apk on my phone. It worked even with the latest firmware, but now I have that yellow message thing. .
Sent from my GT-I9195L using Tapatalk
Click to expand...
Click to collapse
Which ROM do you have now? And have you gone to the Play Store and updated to the latest Super SU?
When you update SU it re installs and will, with permission disable Knox. I'm guessing you have. Try a reflash w/Odin 4.2.2 and just repeat the S4_Mini_Rootkit and update SU. Kinda' do it over...Sometimes that helps.
Sorry I'm not too clear right now, been up 25 hrs and gotta' sleep. I'm older than dirt and can't go the distance any more.
EDIT:Apologies, missed the part about you having the latest firmware. If you are on 4.3, others have had success so IDK, unless you have an earlier SU than 1.80.
My Bad...Another EDIT: Did you by chance go into system/apps and delete KNOXAgent.apk, KNOXStore.apk, ContainerAgent.apk ? Just maybe......... I gotta' sleep, bye.

Lol... I don't have Knox security warnings, I deleted all Knox files. The message in yellow says "Set Warranty Bit: kernel" on Samsung boot logo, but that's it. I think is nothing to worry about, but if I can get rid of it, that would be great. It appeared after I installed TWRP Recovery. .
Sent from my GT-I9195L using Tapatalk

rolo143 said:
Lol... I don't have Knox security warnings, I deleted all Knox files. The message in yellow says "Set Warranty Bit: kernel" on Samsung boot logo, but that's it. I think is nothing to worry about, but if I can get rid of it, that would be great. It appeared after I installed TWRP Recovery. .
Sent from my GT-I9195L using Tapatalk
Click to expand...
Click to collapse
Yeah, that's still that blasted Knox, doing it's "Set Warranty Bit: kernel", you are tripped at 0x1 with an eFuse.
I was going to play with TWRP, I think I'll retain CWN for a bit. It still might be worth a shot to go back to square one with the baseline Arco68-CWN setup with 1.8 SU and at least see if the warning goes away. Or have you already?
(I'm kind of tempted to duplicate your setup, I'm curious about this.) Can you clarify? Are you on 4.3, or did I misunderstand and you're on 4.2.2 ?

I'm on 4.2.2.. I stupidly updated my phone via OTA, because I thought it would have 4.3 but surprise! I got a Knox firmware and I can't go back. And I think TWRP or CWM it doesn't matter, I think when you flash any recovery that isn't stock, the warning activates..
Sent from my GT-I9195L using Tapatalk

rolo143 said:
I'm on 4.2.2.. I stupidly updated my phone via OTA, because I thought it would have 4.3 but surprise! I got a Knox firmware and I can't go back. And I think TWRP or CWM it doesn't matter, I think when you flash any recovery that isn't stock, the warning activates..
Sent from my GT-I9195L using Tapatalk
Click to expand...
Click to collapse
The OTA explains your problem. 4.2.2 is fine, the below root process deals with Knox.
Re-do with the Arco68 root from square one. Stick with CWM for now, TWRP may not be fully stable with the S4 Mini at this time, CWM is. Using it removes any question.
http://forum.xda-developers.com/showthread.php?t=2364980
(make sure to click the Arco68 thanks)

Got the same message in my galaxy 4 mini
Hi guys! First of all consider I'm a graphic designer and have no idea about rooting and getting in phones softwares hahaha, but I have so bad luck that after purchising my Samsung S4 mini (GT i9195) on a trip in France about a month ago and trying to use it here in Buenos Aires with a local SIM, I got Samsung's Region Lock message pop up. I gave it to a friend from work and not only he couldn't fix it, but also returned it to me with this tiny annoying message in the initial animation that says "Warranty bit: kernel" (really bad caption attached).
So here I am, trying to fix the region lock and also the Warranty Bit message. The most important thing is the region lock, of course, but now I think my friend rooting the phone caused this message to appear.
The thing is, can I fix both things? In order to fix the region lock I need to have the device rooted, and, in the other hand, the root left this message.
Can anyone help me? I swear I've tried to understand it on my own but there are so many thecnical vocabulary I just don't get.
Couldn't thank you enough!
Hope you are all doing great,
best
Laurie.

Laurie, if you don't want to see that yellow message you have to install stock ROM with Odin, your warranty still voided.
have you tried region lock away I'm not sure if it works but it won't hurt trying.
sent from my i9192 with CM11 by sekil

set warranty bit kernel
I have galaxy s5 sm900f but i think every phone is the same text proplem . I try many difference roms and only one work without that text is alliance rom. Every others roms always come text kernel is not seandroid enforcing and set warranty bit. I dont know what is difference that rom i use philz recovery.

Also where is the best place to get the stock ROM files so we can use Odin and load them? Thanks for all your help!

Sammobile dot com

[GUIDE] Root T999 (variants) on android 4.3 AND remove knox

WARNING: Following any of these instructions WILL void your warranty,
and could possibly cause irreparable harm to your device (i.e. bricked)
If you do Not understand these risks, stop here and do Not proceed.
If you do Not know how to use Odin, stop here and do Not proceed.
This guide is ONLY for SGH-T999 variants that are ALREADY RUNNING android 4.3
If you do Not have a SGH-T999 variant, stop here and do Not proceed.
If you are Not currently running android 4.3, stop here and do Not proceed.
I am not responsible for anything that happens to your device. YOU chose to follow this guide.
I have the SGH-T999V (samsung galaxy S3, canada, Videotron)
I flashed the full 4.3 firmware from samsung-updates.com as soon as it became available ... and then I tried to root it the usual ways
However knox prevented the superSu app from running, and it closed immediately, and obviously root was Not available to any app
This method will obtain ROOT and REMOVE the knox garbage
note ... altho it is optional to remove knox, I have Not tested without removing knox and do Not know if root will work using this method (guide) with knox still installed !
I did NOT create this method ... I simply found it, read thru user comments, and used it
FULL CREDIT goes to
@upndwn4par for the method ... the thread is here
@Kaito95 for the Knox Removal script ... the thread is here
@Dees_Troy for the TWRP recovery
@Chainfire for SuperSu
as you can see, this method was for the AT&T, Rogers, Bell, Telus Samsung Galaxy S3 ... I747 variants, I believe
So here is how I achieved a successful root on 4.3 using the above method, with adjustments for our T999 variant
Using Method #2
1. Download required files
a) download Odin 3.07 to your PC​
b) download the latest TWRP recovery for your device, in TAR format, to your PC
click on your device here
scroll down on your device page to the section called Download - Odin Flashable Tar
below that, click on the Select the latest .tar file from here link
scroll to the bottom of the files and click on the latest TAR version
note to d2tmo users ... thanks to @Perseus71 it has been noted that 2.6 versions may have issues on your device, and it is recommended that you choose the 2.5.0.0 TAR version
example: Mine looks like this: openrecovery-twrp-2.6.3.0-d2can.tar
note to T999V users ... both d2can and d2tmo work for our device ... I personally use d2can​
c) download SuperSu 1.65 zip to your DEVICE​
c) download Knox Removal zip to your DEVICE​
2. Reboot into Download mode ... VolumeDOWN + Power + Home
Run Odin
make sure that re-partition is NOT checked!
click the PDA button and point to the TWRP recovery TAR file that you downloaded above
connect your device to the computer ... wait briefly
the COMM port in top left box should turn blue
click Start
when it is done, PASSED, and phone has rebooted, disconnect device
3. Reboot into Recovery mode ... VolumeUP + Power + Home
Flash (install) the Knox Remover zip
Flash (install) the SuperSu zip ... it is version 1.65, current is 1.80, so it will prompt us to update later :good:
Reboot System
4. Update SuperSu from the Play Store
5. Open SuperSu
it should prompt that it needs to update the binary
accept and let it update the binary the Normal way
6. Reboot
7. Enjoy rooted 4.3, knox-free :laugh: :good:
​
thanks again to @Perseus71 for noting that it is possible that the default Enforcing mode of SElinux may cause issues with the ability and/or performance of some root apps despite being granted root permission
if you are experiencing similar issues, he recommends that you check out the SELINUX Status Changer app.
[I have Not personally tested this app]

reserved
in case

You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0

Perseus71 said:
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Click to expand...
Click to collapse
hi and thanks for your input
I just looked at that SELINUX Status Changer thread and will keep an eye on it ... but for now I won't add it cuz:
the dev says it is pre-alpha version
Mine is Enforcing and root seems stable and hasn't had any problems, yet ... 4 days so far
SElinux is here to stay, and there's a big difference between proper (Google) implementation and samching implementation ... root blocked by samching, but not by standard android enforcing #BAM
congrats on being first, lol
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?

cLogic said:
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
Click to expand...
Click to collapse
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?

Perseus71 said:
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Click to expand...
Click to collapse
fair enough ... thanks again for your input ... OP updated

Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)

trepoman said:
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
Click to expand...
Click to collapse
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?

cLogic said:
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
Click to expand...
Click to collapse
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...

trepoman said:
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
Click to expand...
Click to collapse
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)

cLogic said:
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
Click to expand...
Click to collapse
Confounded facts. Always kicking my ass.
This is what happens when I stay up too late and try to do too many things. Linked from another thread and had too many tabs open.
Delete.

Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.

So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.

ksec said:
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
Click to expand...
Click to collapse
are you sure you're running stock 4.3 ? baseband MK5 ?
re-do the Odin steps, except uncheck the auto reboot option .. so that it stops after successfully pushing the recovery tar
unplug the phone from the pc .. it should still be in download mode
pull the battery
then put it back in
boot into recovery immediately
if you see the TWRP recovery, great!, complete the guide and you'll be knox free and rooted
if that worked then there are two files that you seem to still have that are putting stock recovery back on normal boot .. post results here and I'll find them for you

Ergonyx said:
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
Click to expand...
Click to collapse
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1

cLogic said:
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
Click to expand...
Click to collapse
I updated the the SuperSU binary.
The apps will open but when it attempts to do anything requiring root access it is denied or fails.
SuperSU and Knox were installed through the TWRP recovery boot thing as the guide specified. Other things were either installed from the app store or downloaded APK files. I didn't have Titanium at the time I attempted rooting my phone. Wasn't mentioned in the guide so I never got it. I have the basic version now from the play store now. As I'm sure you can tell, I've never rooted my device before. Always had a friend do it for me.
Should I just restore to a stock install (not sure how to do this) and then try again? Especially now that I know the 2.5 warning was specifically for T-Mobile users? Or can I just put the 2.6X version on my phone and try again? lol

it's working
@ cLogic
Thanks a lot man, thanks to you I successfully root my sgh-t999v (stock android 4.3)

I've managed to use GooManager from the Google Play store to install latest TWRP and to flash the 4.3 mod.

Having issues when trying this. I followed all the steps and received no errors. But when the SuperSu ap tries to open on my phone it crashes, the ap only phone is stable.
I have Tomo G3 4.3 Stock rom
Flashed the TW 2.5.0.0 version
Rebooted into the touch recovery
Ran Knox removal
Ran SuperSu
Booted
Knox is not in my list off apps
SuperSu does show
Cant not open supersu, updating binarys does not work since the app crashes.
(Edit)--> Redid the whole process but did not let the phone reboot during the TW flash and the Zip installs. Seemed to of fixed the issue. (Edit)
Thanks added

I flashed Stock 4.3 via Odin before coming across this guide and now my device seems to be stuck at the boot screen. My question is, if I haven't completely booted, can I reflash using the modified version of 4.3 (root, deodexed, knox removed)? Do I have any other options right now?

Odin passes but Root Checker says no

For some reason its passing in Odin and saying it worked. Go into the phone and phone isn't rooted. Tried about 9 times running Odin and its not working. It says in download mode that I'm running custom binary but its not installing Su Binary when i run Super SU. The CF-Auto-Root isn't also installing with this package.
I reverted back to stock 4.1 from 4.2 because it was not letting me use the OTA update fuction before this mess started so I thought I had to remove my root to begin with. Then after having many errors/crashes in 4.1 I had to factory reset then it let my update to 4.3. Well now I'm following the first post in the root with CF-Auto-Root thread and its not letting me "root" and install the SU Binary.
http://forum.xda-developers.com/showthread.php?t=1963812

Check out the last few pages of THIS thread. A few people claim to have gotten it done. Just be sure to read, and be sure of what going on before proceeding forward.

GOT IT!!!!
Thanks for the post it helped get my phone rooted, I had to follow the post you linked to get it rooted smoothly then this post |Guide|How-To| Root & Install Custom Recovery for 4.3 Update |22 Nov 2013| to get SuperSU and KNOX remover to get root working.
Seems the root was not taking with CF-Auto-Root like everyone else but TeamEpic-Root-from-Recovery-v5.zip worked from TWRP. I just had pop ups in Android saying security policy update had blocked a app from accessing anything. Flashed the SuperSU app with the Knox remover from recovery then rebooted and TA DA! SuperSu worked and wanted to update my Binary.
Hope this post finds it way to other users stuck in the same boat I was in cause the last couple days I've been staying up HOURS trying to root my phone!

Zspy1985 said:
Cool thanks I'm going to give the first post a whirl.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
If you did the OTA update, then you should be aware that you now have the Knox bootloader on your phone. Do not, under any circumstances, try to Odin back to 4.1.2, which has a different bootloader, which will brick your phone. And if you flash cwm through Odin, it won't brick, but will void your warranty by tripping the Knox counter(triangle away won't erase this one). But to get root, simply flash PhilZ latest recovery for this phone through Odin, reboot to recovery, and flash SuperSu update, reboot, profit. Both links are on the rim op below. Make sure you have SuperSu downloaded before you reboot to recovery, and uncheck auto reboot and f. Reset Time in Odin. Good luck!
http://forum.xda-developers.com/showthread.php?t=2546505
Sent from my SPH-L710 using Tapatalk

prboy1969 said:
Check out the last few pages of THIS thread. A few people claim to have gotten it done. Just be sure to read, and be sure of what going on before proceeding forward.
Click to expand...
Click to collapse
Which last few pages because you posted this about 4 days ago. Could you tell me which page number to look at please?

Just do the first page on how to root
Sent from my SPH-L710 using Tapatalk

tbudke said:
Which last few pages because you posted this about 4 days ago. Could you tell me which page number to look at please?
Click to expand...
Click to collapse
If you are on 4.3 Stock OTA, people are getting it done using THIS method. If you are on 4.1.2 then use the method on the thread HERE.

[Q] SGH-I317M with KNOX can not be rooted

Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.

Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203

Stewegg said:
Can't even start SuperSU
Click to expand...
Click to collapse
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3

VeeDaub said:
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
Click to expand...
Click to collapse
Where is the Reactivation Lock located?
I can not find it in the Security Settings.

mrevankyle said:
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Click to expand...
Click to collapse
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?

Stewegg said:
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Click to expand...
Click to collapse
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
Link to philz recovery tar for our phone i317M
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/philz_touch_6.19.3-t0lteatt.tar.md5

Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk

Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
Simple. First get the root. Like the su binary and stuff. once you are rooted get suersu. What I mean by first get root is literally get root through a program or something. After this you will have root but you wont have root access. So get supersu now and launch the app. It will ask to update your su binary. Say yes. then the thing will say something about knox then ask you if you want to try to disable knox. Tap yes and knox should be disabled and your su binary should be updated and working.

I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:

My phone is I317M Rogers, it run stock 4.3. I followed this guide, http://forum.xda-developers.com/showthread.php?t=2618261 rooted success.

Eun-Hjzjined said:
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Click to expand...
Click to collapse
ifentanez said:
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
Click to expand...
Click to collapse
koodiifin said:
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
......
Click to expand...
Click to collapse
koodiifin's way worked perfectly!
Thank you koodiifin!

[GUIDE] how to root Sph-L710/L710T S3 4.4.2 (updated as of 8/19/2015)

I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse

work on ND8 rom? sprint phone?

Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders

Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!

oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.

henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?

6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.

I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app

jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....

Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave

dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM

churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.

Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all

Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.

Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.

Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!

strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff

added two more t=root methods