yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] k1mu:
That's been stated several times here, specifically in post #2.

I'm not sure how to make this more obvious other than using big blinking letters that would annoy the people who actually read the information already posted.

When you root, you modify your phone. The phone looks for modifications all the time and sets the custom status.

If having "Custom" show up at boot, fix it with the means described in post 2, or don't root.

Saferoot won't trip the Knox Warranty Void flag. which is permanent. You can't ever re-set that.

Fixing the custom flag for real means that you must have a stock, unmodified, unrooted device. Sorry, you can't have root and un-root at the same time.

Triangle Away is NOT how you clear that "Custom" flag. You've now voided your warranty. :(
[Verizon Samsung Galaxy S 4] Nirak:
I don't know what you're trying to explain here, but for me it is and was already clear that saferoot doesn't trip the Knox counter.

Basically i made a mistake returning the rooted device to stock (selling it). I removed custom recovery, ran TA and Odined the newest stock firmware on it including the new Knox bootloader (stupid..i know....). After that i noticed my binary count was still on 1 (cuz of the custom rom i had). So i re rooted with saferoot to avoid knox 0x1 and used TA in the hope it wouldn't trip Knox, but it did. My binary count was reset to 0 btw.

My only point was explaining to anu.cool that triangle away worked on my GT-N7100 but using it does trip the Knox counter.

Since i already had a custom binary count my warranty was voided anyway.
[Verizon Samsung Galaxy S 4] ichibantokkan:
hi i'm from Portugal, i have a gt-i9505 from vadafone pt, and it's version is mk9, can i use this root method without trip my knox? :D
[Verizon Samsung Galaxy S 4] shayind4:
Any suggestion on which version of 'Safestrap' app to use or just the latest version?

Thanks
[Verizon Samsung Galaxy S 4] rlichtefeld:
Just to verify I did this to my T-Mobile SGS4 with 4.3 and MK2, and it worked without a hitch. I have full root and busybox, and the Knox counter isn't tripped.

Here's what my Download screen now says:

ODIN MODE

PRODUCT NAME: SGH-M919

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

KNOX KERNEL LOCK: 0x0

KNOX WARRANTY VOID: 0x0

CSB-CONFIG-LSB: 0x30

WRITE PROTECTION: Enable

eMMC BURST MODE: enabled

We are following this thread over in the T-Mobile SGS4 forum: http://xdaforums.com/showthread.php?t=2611175

Rob
[Verizon Samsung Galaxy S 4] Anubhav Agrawal:
my question was basically if I flash a no wipe rom after unrooting later,will it trip Knox or not..

now that I was not able to root my gs4,so the question is basically to update my knowledge...

and well yes,I did misread triangle away's functionality,sorry for that..
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
The no wipe is official samsung it just doesn't wipe out your apps, setting and media drive;it doesn't trip knox, but not sure how that matters as you have already tripped it...no turning it back, tripped is tripped.
[Verizon Samsung Galaxy S 4] gadget069:
If you're on mk2 use 3.71 or mf3 use 3.65
[Verizon Samsung Galaxy S 4] shayind4:
Thanks. I am on MJ5 and used safestrap version 3.71 and installed working Hyperdrive rom.

Regards
[Verizon Samsung Galaxy S 4] marlar:
What does this mk2 and mf3 refer to? I have a Samsung S4, how do I know whether it is mk2 or mf3 or whatever?
[Verizon Samsung Galaxy S 4] nlatifolia:
Last 3 chars of build number.
[Verizon Samsung Galaxy S 4] Gachmuret:
Hi all,

Don't want to spam but because I'm using Knox as secure environment for privat and sensitive data I really wanted to know, if anyone tried to use it while rooted and if it still works flawlessly, even when rooted :confused: (I know that it won't pull the trigger ;) )

Thx for sharing your experience!
[Verizon Samsung Galaxy S 4] nlatifolia:
I don't use Knox and yet rooted (waiting for 4.4 OTA) but I can say something to share that it is dangerous to utilize side by side Knox + root because if u heavily use Knox your data will encrypted in exclusive container and by rooting (even it didn't trigger Knox at first place) it might tempted us to do more than just rooting it and there the danger will come. Once Knox triggered all data within the container will be once and for all destroyed irreversably. Read more on Knox advantages and disadvantages.
[Verizon Samsung Galaxy S 4] Gachmuret:
Yeah, that's a point but as long I only use some apps like Adaway, Greenify, TiB that simply are essential for my Android experience it should be no problem if it's working with root.

Also I think of Xposed+Wanam but no custom rom or recovery... just have to test any change extensivly before I seriously use Knox with it.

And if Knox with root should be a no go, then still there are some alternatives like EDS with similar function in Playstore.
[Verizon Samsung Galaxy S 4] k1mu:
Yes, of course. Didn't you read the OP? This will NOT trip the Knox Warranty Void flag.
[Verizon Samsung Galaxy S 4] swrght13:
Used this method to root my sch-i545(running mk2 build). Worked like a charm. No issues. Sure can't wait until the bootloader is unlocked so I can install cyanogenmod on this bad boy.
[Verizon Samsung Galaxy S 4] Anubhav Agrawal:
just a tip, doing that will trip knox ...
[Verizon Samsung Galaxy S 4] juapao:
Hi dev! I would like to thank you fir this wonderful workaround with the bypass of tripping the knox counter/flag. I have rooted my i9505 device on 4.3 hopefully you could also work on the future the custom recovery without tripping the knox as well.:)
[Verizon Samsung Galaxy S 4] Killberty:
Hi guys 2 things:

1) you can install custom roms 0x0 with mobile odin pro, as far as it is an update zip and samsung based. NO CUSTOM KERNELS OR RECOVERIES

2) will this work on note3? (Theoretically? Or anyone tested and can confirm?) EDIT: okay i read the thread :p

Any chance u find another kernel exploit?

3) To the DEVS: do you think this will root the kitkat update on s4 or any other device?

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app
[Verizon Samsung Galaxy S 4] k1mu:
Basically, this is equivalent to using Safestrap and flashing into the stock slot. Only ROMs compatible with the stock TouchWiz kernel will work.

I don't have a note3 so it's unlikely anything will come from me for that device.

That's not likely. Samsung has already patched the kernel for the Note 3 so anything later will also be patched.
[Verizon Samsung Galaxy S 4] marlar:
Thanks.

My buildnumber ends with mkf. Is that a problem with this rooting method?
[Verizon Samsung Galaxy S 4] k1mu:
Possibly, but perhaps not. Some devices past MJ7 have a patched kernel.

It can't hurt anything to try - if you get "device is not supported" then it fails but doesn't have any ill effects.
[Verizon Samsung Galaxy S 4] bgmg:
SPRINT Galaxy S4 Baseband = L720TVPUAMK5

Can anyone confirm this Saferoot method works on SPRINT Galaxy S4 Baseband = L720TVPUAMK5 Model = SPH-L720T ?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
This guy succeeded

(Searching the thread works :sly: )
[Verizon Samsung Galaxy S 4] bgmg:
MK5? SPRINT Galaxy S4 Baseband = L720TVPUAMK5

Can anyone confirm this Saferoot method works on SPRINT Galaxy S4 Baseband = L720TVPUAMK5 Model = SPH-L720T ?
[Verizon Samsung Galaxy S 4] nbock01:
Worked great on my 2 i605s! Thanks!
[Verizon Samsung Galaxy S 4] k1mu:
Thanks. Especially from a VMS fan. (I'm perhaps the only person to ever be both an OpenVMS and a UNIX Partner while at that company.)
[Verizon Samsung Galaxy S 4] Chris-M.:
Works with Verizon galaxy note 2 4.3
[Verizon Samsung Galaxy S 4] yapkui:
confirmed work on my i9505

android 4.3

XXUEMKE

Knox warranty : 0x0

:good::good:
[Verizon Samsung Galaxy S 4] sniper9911:
the method did not work correctly

I did enable developer and usb debugging and grant the computer access to device via adb

super su injection was a success

super su can update via play store

the problem is after the injection phone reboots and nothing done afterwards ... no busybox no denox

when I open super su it gives a message that I havent been rooted correctly

device : galaxy note 2

rom : stock 4.3 ueml4 flashed via odin

contains knox bootloader

knoxs warranty void 0

system status official

custom binary count 1 , from previous 4.1.2 rom root

help please I want root
[Verizon Samsung Galaxy S 4] marlar:
I would love searching the thread, but how? I haven't been able to find any "Search this thread" tool or similar.

AND WHILE WRITING THIS I SUDDENLY SEE IT! Below the thread at the bottom of the page. Strange! Believe me, I have been looking for this for a long time, not only for this thread! But mostly those search tools are somewhere at the top of the page, don't know why I didn't think of looking down there :silly:

But thanks!

---------- Post added at 11:26 AM ---------- Previous post was at 10:59 AM ----------

Okay, I did it and it seems to work, albeit with some strange complaints from the script.

Here is the last lines of the output using install.sh on Linux:

Succeeded in getroot!
Remount success!
Copying files..
Done.. reboot to enable root!

[*] Removing temporary files...

[*] Rebooting...Please wait.
[*] Waiting for device to re-appear...
./install.sh: 75: [: X: unexpected operator
Something has deleted su - looking for a backup copy
./install.sh: 80: [: X: unexpected operator
No su program can be found. Exiting.

So it says that it is rooted, but then after reboot it cannot find su. And then there is an unexpected operator "[" (I checked my command history if I accidentially added that character after ./install.sh but I didn't).

But it IS rooted! If I write adb shell and then su I get the su prompt #. And apps like Titanium Backup and Greenify works - they ask for SuperSU access and works as the should after granting the permission.

Should I just ignore the message about missing su since it seems to work, or is there something wrong I should try to fix?

And knox? It didn't trip!

One more question: SuperSU asked me to update the binary. I could choose between Normal and some other mode whose name I can't remember. I didn't know what to do so I just pressed back to cancel. It doesn't seem to ask me again, but what should I choose if it does?
[Verizon Samsung Galaxy S 4] kuijkens:
Search bar is also at the top of the page, on the far right side of the screen (next to the first post of the page, maybe you will have to wait for the page to be fully loaded).

If it is rooted, just let it be or uninstall SU and try again.

If I where you I would give it another go, no harm in doing that.

What you did wrong was the following:

After the reboot when the scripts says "Open SuperSU and let it update if it asks", open SuperSU and it will indeed ask to update the binary.

You will have 2 options, normal or via CWM/TWRP (recovery). Just choose Normal.

Wait for it the be updated.

---------- Post added at 12:56 PM ---------- Previous post was at 12:53 PM ----------

I would say, give it a go.

If it fails you are able to undo everything the script has done without triggering knox.
[Verizon Samsung Galaxy S 4] bgmg:
-------------------------------------------------

For the MK5

, how do you undo everything including the custom flag without triggering knox? Please send me the URL to the thread. I want to be sure there is a method for getting back to stock before I try.
[Verizon Samsung Galaxy S 4] kuijkens:
I do not think unrooting is firmware dependent.

Just take a look at he second post of this thread, unroot tutorial for this method of rooting.
[Verizon Samsung Galaxy S 4] BlueAngel1953:
So I rooted my phone the other day, all went well. Now am I good to asume KNOX is disabled so I can install CWM without tripping KNOX?
[Verizon Samsung Galaxy S 4] umberto.sulla:
No, if you install a custom recovery you will trip knox flag... Knox flag isnt tripped by knox runtime, but by bootloader and kernel that check for stock recoveries and signed images. If you instal a new not samsung signed recovery you will trip the flag.

Just use Mobile Odin Pro to flash roms and Titanium to backup.
[Verizon Samsung Galaxy S 4] BlueAngel1953:
Wasn't looking to flash a new rom, but I am trying to edit some files so I can install a custom PRL. And apparently I need CWM or a custom recovery to do so.
[Verizon Samsung Galaxy S 4] pball52998:
Had to change the script for mac to ./adb so replacing all the adb with ./adb in the script before running it in terminal, but besides that worked great. O yeah I accidentally pressed enter to quick after it and I think I missed something :$ it said it installed but is there anything important I missed? Please if so how would I fix that :$ but worked great!! I have SU! Thanks!! :)
[Verizon Samsung Galaxy S 4] :
Root:

I used the Saferoot method and after running Root Checker Pro to verify I receive some funky info. I included screenies of my inquiry. Also, I am on the Sprint GS3 OTA 4.3 MK3 build, already had tripped the Knox warranty flag (no big deal to me) but I would like to possibly try a custom ROM or two. I currently have TWRP installed as my Recovery. Will I be able to do such without hard bricking? I have read so many mixed results. Thank you all in advance here at XDA.

View attachment 2530434 View attachment 2530435
[Verizon Samsung Galaxy S 4] k1mu:
The discrepancy is caused by Knox removing the setuid bit on the su binary.

That's cosmetic as it still works, which is what Root Checker says.

You can fix that from a terminal emulator:

su
mount -o remount,rw /system
chmod 6755 /system/xbin/su
mount -o remount,ro /system

Or you can use a root-aware file explorer to change the permissions.

Now, as far as what you can do, you'll need to ask in the Sprint forums. I honestly don't know if the bootloader on the Sprint GS3 permits you to flash custom roms, recovery, etc.
[Verizon Samsung Galaxy S 4] k1mu:
About the only way I'll be able to tell what's happened is for you to capture the output from the root attempt.
[Verizon Samsung Galaxy S 4] k1mu:
Oops - that "unexpected operator" is an error in the script which I thought I had fixed. I'll re-test on my Mac and re-upload once it's fixed.

For updating SuperSU, use Normal mode.
[Verizon Samsung Galaxy S 4] :
Thank you for your reply, I ran the following in Terminal Emulator and it says Unable to chmod /system/xbin/su: Read -only file system. :/ If you say this is just a cosmetic error then I do not feel so bad. Although I would like to resolve it.
[Verizon Samsung Galaxy S 4] k1mu:
That second line: mount -o remount,rw /system

is what remounts /system as read/write. Either you didn't do that, or it didn't work. The command above has the spaces doubled so you can see it more clearly.
[Verizon Samsung Galaxy S 4] :
Thanks, I did get it to pass thru. Although on the System File Properties for Root Access it still says in Result/Analysis that No such file or directory exists: /system/bin/su Sigh, I seriously regret taking this OTA update. You guys rock here regardless :)
[Verizon Samsung Galaxy S 4] sniper9911:
hope this helps

thanks
[Verizon Samsung Galaxy S 4] k1mu:
"This device is not supported" - your phone doesn't have the kernel defect that saferoot uses to root, so it won't work.
[Verizon Samsung Galaxy S 4] k1mu:
su is installed in /system/xbin/su, not /system/bin/su (at least that's how SuperSU does it.)

This is why I've commented in the past to not trust root checkers. If Titanium Backup works, you're rooted.
[Verizon Samsung Galaxy S 4] :
Yes, sorry for the typo there. Well I am indeed Rooted. Thank you for the help, I am going to head over to the Sprint forums and dig around on trying to install a custom ROM. Just would hate to end up with a pretty purple paper weight, lol. Thank again buddy, greatly appreciated!
[Verizon Samsung Galaxy S 4] sniper9911:
so no hope for me to root without voiding warranty ?

what a shame

thanks for your help
[Verizon Samsung Galaxy S 4] bgmg:
How to return MK5 from custom back to official

-----------------------

Thanks, but unrooting is not the same as changing back to stock/offical. Using the full unroot in the SuperU does not change the custom flag back to official.

If anyone knows how, Please advise.
[Verizon Samsung Galaxy S 4] yapkui:
Hi,i rooted my i9505 with saferoot.Can i flash custom rom from Mobile Odin Pro and Knox warranty still 0x0 ?

Thanks.
[Verizon Samsung Galaxy S 4] Killberty:
Yes if its a stock based rom

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app
[Verizon Samsung Galaxy S 4] ScallywagginIT:
I was able to use the saferoot.zip tool to root my Droid RAZR M successfully. Everything is working great in regards to the phone being rooted, but I am now having problems with Google Play Services crashing on me. I wanted to do a factory reset on my phone to reinstall everything fresh, but I am wondering what steps I need to take to make sure I am rooted properly after the factory reset. I know that doing a factory reset only wipes /data and /cache so I was wondering if all I would need to do is install SuperSU from the Play Store after I am done doing the reset and the su binary should still stay on /system, keeping my device rooted.

Is it ok or better to re-run the saferoot tool after I do a factory reset, or is it better to just install SuperSU from the Play Store and everything would still be intact?

Also I noticed that a number of other files are copied to /system besides su. Can you explain what the root tool actually does because I believe it installs busybox and su on the /system partition and then pushes SuperSU to the /data partition. However, I am unclear how busybox installs or works because it seems that su and the other binaries copied are linked to busybox when they run. Just curious so I understand how to maintain my root better. Thank you in advance!
[Verizon Samsung Galaxy S 4] k1mu:
Read post 2. This is already answered.

Either undo whatever you changed or flash a no-wipe stock after unrooting.
[Verizon Samsung Galaxy S 4] k1mu:
See post #2 - that explains what you need to do to undo what saferoot changes.
[Verizon Samsung Galaxy S 4] ScallywagginIT:
Ok thank you. I appreciate the quick response. So are you saying that I need to unroot completely by following post #2 before I do a factory reset on the phone? Just wanted to make sure. Thanks!
[Verizon Samsung Galaxy S 4] k1mu:
That's the safe thing to do, but it's not strictly necessary.
[Verizon Samsung Galaxy S 4] ScallywagginIT:
Ok great. My last question is that for unrooting, you mention these commands:

# rm /system/etc/install-recovery-2.sh*

# rm -f /system/xbin/selinuxoff*

On my Droid RAZR M (not Samsung) I am not able to see an "install-recovery-2.sh" or "selinuxoff" in my /system/etc and /system/xbin, respectively. However, I do have an "install-recovery.sh" which appears to have been modified at the same time all of the other root files were copied to my phone. Is there a reason why this file was modified at the same time I rooted or do I need to delete that at all? In regards to selinuxoff, I saw in the changenotes that you removed it from the root script. Is that correct? Thank you.
[Verizon Samsung Galaxy S 4] marlar:
Btw, I forgot to mention that I don't have the boot padlock either :)
[Verizon Samsung Galaxy S 4] k1mu:
Those two files were part of the failed attempt to turn SELinux off.

install-recovery.sh is part of SuperSU and as far as I know, it's removed when you do a full unroot. using SuperSU.
[Verizon Samsung Galaxy S 4] noobapotomus:
SG note 2

Had to fight like hell with knox. found i needed to stop the 4 knox related apps under app manager, to get the batch file to run. even then, i did not get prompted for SU permissions. i went into /system/app and reran the superuser apk.and then reran the bat file. that allowed it to complete, and reboot. now time to start looking at custom roms. Thanks again for such a great forum
[Verizon Samsung Galaxy S 4] osokthedevil:
Works on Telus Note 2

this method works on my Telus note 2 **** ya !!! SGH-I317M
[Verizon Samsung Galaxy S 4] sehooo:
Any safe support for kitkat 4.4 soon ?:confused:
[Verizon Samsung Galaxy S 4] leon22heart:
Jss15j.i9505xxuemke

working on said firmware .Many thanks .
[Verizon Samsung Galaxy S 4] tuffluck:
Just curious about the OP instructions stating he has swapped Superuser with SuperSU that installs busybox also. I have already completed this root method with no issues whatsoever, but I only see SuperSU and not busybox app, and I also don't see the busybox app in SuperSU either. Am I missing something? Regardless, if it really isn't there, I've not been limited by root capabilities so far...
[Verizon Samsung Galaxy S 4] tshelby73:
Busy box doesn't show as app. It's system level I think. I used stericson busy box app from play store. Wait for it to do its thing and will show what version is installed. You can then just uninstall the app
[Verizon Samsung Galaxy S 4] blu422:
Still no custom roms on mk2?
[Verizon Samsung Galaxy S 4] decaturbob:
Hyperdrive and a handful of others...just gotta read some rom threads here.

safestrap enabled, Hyperdrive driven
[Verizon Samsung Galaxy S 4] gadget069:
Just used the newly released tar files for MK2 to upgrade from mf3, worked like a charm, also used saferoot without any issues.

Thanks!!!!!
[Verizon Samsung Galaxy S 4] OfficeLinebacker:
Just got it to work on MK2 with Windows. A few notes:

I downloaded Kies 3 from the Samsung site. It found the phone fine. However, the script did not work unless I had Kies open while I was running it. I discovered this because I closed Kies after starting install.bat and even though it started OK, I got errors. Tried again with Kies closed, nada. Tried again with Kies open and it worked.

Another thing is I never saw the "enable debugging with this device thing" but I tried reinstalling the USB drivers from Kies and when I did that, the popup happened on the phone. But I didn't catch it quick enough. I did it again and I caught it and checked "always allow." Not sure if this helped because this was before the previous discovery.

Right before the phone rebooted, I got a message in the notification are that said something like "unauthorized access to a secure area" Didn't catch much else cos the phone rebooted.

Finally, when updating SuperSU, it asked if I wanted to update the Normal way or with TWRP or something similar. That wasn't in the guide so I chose Normal and it worked fine.

Now to ask, what's the best Wifi Tether app to use with this phone? (Feel free to point me to another thread.)

Thanks, XDA Rocks!
[Verizon Samsung Galaxy S 4] tshelby73:
This is what I use http://xdaforums.com/showthread.php?t=2512981

I haven't used the newest version with toggles but the old version works great.
[Verizon Samsung Galaxy S 4] blu422:
No I mean like is it possible to install custom roms coming from mk2 sorry for the confusion
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
No confusion, those are your options, the likelihood of an unlocked bootloader is slim to none
[Verizon Samsung Galaxy S 4] pegasus123:
thanks it works without triggering knox 0x1. on GT-I9505 MKE firmware
[Verizon Samsung Galaxy S 4] ryebread761:
Worked and successfully rooted S4 i337m. Awesome. Thanks so much!
[Verizon Samsung Galaxy S 4] shayind4:
I think it would be a good idea to have a list of devices and build numbers that we have succeeded in rooting with Saferoot....all in first post for ease of reference.

I did succeed in rooting S4 i9505 4.3 MJ5.
[Verizon Samsung Galaxy S 4] ryebread761:
I would agree. You have to go post-hunting ATM.