Related
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
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!
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
So I recently updated to the I747MVLUFNF2 update in Kies from the I747MVLUFNE6 Update and I can't seem to root it using towelroot (I keep getting a phone unsupported message). Is there another method to root the phone without tripping KNOX?
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I understand once I root it with CF Auto Root then the warranty bit is tripped, but does this prevent me from using my phone with kies to update or backup? Or what exactly happens?
It just means you cannot use Knox for secured storage. The vast majority of us hate knox anyway so you might actually call this a win!
Of course it also means they can refuse warranty services, but most never need this, and many have reported their warranty being honored regardless.
Otherwise, it has no other effect on how you use your device, flash roms, root, etc.
I have the same issue.
I don't care about knox... but rooting it with the other ways that I know installs the super user app properly but then the SU app keeps crashing... I was assuming it was because of knox but now I'm not sure anymore, tried to reset it and to reflash the rom twice and every time it did the same thing...
Do you have any ideas why that might be happening?
I really would need a solution as I hate unrooted 4.4.2... :S
Thank you!
After rooting, you should be able to open SuperSU and it'll update its binary if needed and will disable knox.
Did you do that part?
I did try to update SU... The result was the same... the SU app would crash when I tried to launch it, before it even gives you the screen to disable knox... Trying to download the slightly older I747MVLUFNE6 which hopefully will root better...
You cant downgrade firmware. You could flash a rom, but i dont think that's what you were getting at.
How did you try to root? Have you tried using the oldest method we've got? Seems to never fail when others do!
Flash custom recovery with Odin.
From recovery flash the SuperSU update zip. You can find it by going to chainfires thread. (Its also in my sig bit I haven't added the very latest version yet)
Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.
Bob Terwilliger said:
Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.
Click to expand...
Click to collapse
Hi Bob
please witch version of auto-root have you use ?
The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.
Bob Terwilliger said:
The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.
Click to expand...
Click to collapse
Using the zip you provided, which version of SU did you use?
The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.
Bob Terwilliger said:
The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.
Click to expand...
Click to collapse
i have tried this one but it doesn't solve my problem, SuperSU crashed when it start, i don't understand what is the cause :crying:
It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.
Bob Terwilliger said:
It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.
Click to expand...
Click to collapse
thanks bob, i discover that the problem was about the I747MVLUFNF2 rom, so I changed it by I747MVLUFNE6 and all ok now
thank you again :good:
I did the opposite. I flashed the latest version of CF-Auto-Root from http://autoroot.chainfire.eu/. SuperSU was crashing, so I re-flashed the latest version of SuperSU (v2.01) from http://download.chainfire.eu/supersu and it worked fine after that. This was on the I747MVLUFNF2 ROM.
DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!
If Towelroot doesn't work, there is no other way to root without using Odin and a PC.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
hey
aryan.yazdani said:
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!
Click to expand...
Click to collapse
Actually... PM me, I'll tell you how I did it.
After seeing many people ask questions about Knox on a regular basis about what they can or can't do, I have decided to create this thread that will hopefully make things clear for those searching information about Knox on our devices.
So first things first.
What exactly is Knox?
Information about Knox
Knox allows people to use their device on a secure business (work) network. It allows the data which belongs to the business to be encrypted per DoD standards. Once the Knox/warranty bit is tripped, you can no longer use this service because it proves the device has been tampered with. You can imagine how much simpler it would be to manipulate this service without the restrictions Samsung had to enforce in order to protect sensitive data. This is the main reason I believe the Knox bootloader was added and why root access, once gained, is still limited in some cases. There is also claims that a tripped warranty bit means your warranty will be void, but I have not seen any cases where people have been denied warranty. However it is better to play it safe than sorry if you really do care about warranty.
Wikipedia sums it up pretty nicely.
Knox on Wikipedia
Click to expand...
Click to collapse
F.A.Q
Q. I have Knox firmware on my device, can I still root, flash custom roms, and kernels?
A. Yes, yes you can. Procedure is the same as it has always been. If you have questions search the forum or ask in this thread. Your Knox counter may trip doing any of this so continue to next FAQ for info.
Click to expand...
Click to collapse
Q. What will trip my Knox counter?
Flashing custom recovery or kernels will trip Knox counter, so avoid them at all costs if you want or need to keep that counter at 0x0. Some root methods will also trip this counter, keep reading if you want to avoid this.
Click to expand...
Click to collapse
My Knox counter is tripped, how can I reset it?
Once tripped, the counter CANNOT be reset.
Click to expand...
Click to collapse
Q. How can I root and not trip Knox?
We can currently use the TowelRoot method by geohot for 4.3 and 4.4.2. Follow link below to thread. It does NOT work on 4.4.4
TowelRoot
Click to expand...
Click to collapse
Q. How can I downgrade my firmware?
You cannot and Odin will fail at any attempt to do so. Do not try to bypass this and try to downgrade another way, you run a high risk of bricking you device! This applies to any device that has been officially updated from 4.3 and up from OTA, Odin, or Kies. If you must downgrade for any reason, flash an older rom in custom recovery only. That is the only way to downgrade. Knox Bootloader will not and cannot be removed, so learn how to get along with it.
Click to expand...
Click to collapse
Q. How can I avoid bricking my device? I have seen people say flashing will brick anything with Knox bootloader.
Do not flash firmware for other devices. Do that and you will be okay. On some devices you can flash other firmwares, if you have questions about this you can ask in this thread.
Click to expand...
Click to collapse
Q. Will tripping the Knox counter void my warranty?
As I stated earlier, there have been cases of people successfully filing insurance claims on their devices. However if you really care about warranty, you may want to avoid tripping this counter to be on the safe side.
Click to expand...
Click to collapse
Q. I see an odd message when I start up my device and it says something about SEAndroid kernel not enforcing, what is this and how do I fix it?
It is normal, you either flashed a custom kernel or custom rom with modified kernel. Do not let it bother you but if you flash back the stock unmodified kernel it will disappear. There is also the possibility you performed an unsupported root method and your device is bootlooping, if this is the case, then flash back to stock firmware with Odin to fix and use an updated root method like TowelRoot
Click to expand...
Click to collapse
And if you have any questions feel free to ask
Nice work bro. Should answer a lot of questions for folks.
Haters Made Me Famous
Deviant Team Member
Forgot to reserve, but mine! I'll use this in case Sammy changes something in the next version of android
Never know
And if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for this post!
After rooting using TowelRoot, should you install SuperSU or some other su?
Sizzlechest said:
After rooting using TowelRoot, should you install SuperSU or some other su?
Click to expand...
Click to collapse
SuperSu from the Play Store
The Sickness said:
SuperSu from the Play Store
Click to expand...
Click to collapse
Thanks! It won't trip Knox, right?
Sizzlechest said:
Thanks! It won't trip Knox, right?
Click to expand...
Click to collapse
Nope, perfectly safe
Sizzlechest said:
Thanks! It won't trip Knox, right?
Click to expand...
Click to collapse
A custom recovery or kernel trips Knox
Good. It prompts you to disable Knox, so I thought that might trip it.
I need help with update
Sorry people, it has been many years that I have been on here. I just got the s4, rooted using the SU method (not towel) and it shows 0x1 for knox.
When I try to go to my software update it says, your devise had been modied and cannot be updated.
please help
It's having root that is keeping you from updating. Not tripping Knox.
I'd download the latest firmware. From sammobile or shinyside's links. And use Odin to flash.
Anyway to flash or odin a custom os with a stock kernel and recovery without tripping knox? Mabey a modified official tar? Just replace system, etc?
lordodin912 said:
Anyway to flash or odin a custom os with a stock kernel and recovery without tripping knox? Mabey a modified official tar? Just replace system, etc?
Click to expand...
Click to collapse
It might be possible but I don't know the procedure. I imagine it must be very unconventional, otherwise we would see it very often
Thanks, SEAndroid kernel not enforcing worried me.
Hmmmmmm wish I were a bit more fluent in this area.....itd be nice if you could just replace/repackage the tar file....then mabey id get off MDL....just read something about repacking tar files for odin and apparently you cant pull and repackage the system without breaking the signature (of the system) therefore odin wont flash....but imma noob in this area. If anyones got any info, please share
noobieneedshelp said:
Sorry people, it has no been many years that I have been on here. I just got the s4, rooted using the SU method (not towel) and it shows 0x1 for knox.
When I try to go to my software update it says, your devise had been modied and cannot be updated.
please help
Click to expand...
Click to collapse
Use this to go back to stock and fix Knox then root again with towelroot method.
http://forum.xda-developers.com/showthread.php?t=2336392
http://forum.xda-developers.com/galaxy-s4-tmobile/general/root-nb4-knox-0x0-t2802185
Thanks for the info!
Just for clarity: What does having a tripped Knox bit mean? Just that the phone has been tampered with and possibly voiding the warranty?
Legioss199 said:
Thanks for the info!
Just for clarity: What does having a tripped Knox bit mean? Just that the phone has been tampered with and possibly voiding the warranty?
Click to expand...
Click to collapse
Yes, and it also means you can no longer use the Knox service.