yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] k1mu:
Not likely. Again, read the OP: you need the drivers for the phone installed for this to work.

Of course, you're welcome to try it as it can't hurt anything.

I'd look for Ubuntu drivers for the phone and install adb. Is there a version of Kies for Ubuntu? There's one for MacOS.
[Verizon Samsung Galaxy S 4] k1mu:
Guessing here: You stored this somewhere where there's a space in the path name. I.e. C:\Documents and Settings\User\My Documents\root\install.bat". I use Windows 7 so didn't see that issue.

If that's the case, then I know how to fix that and will push an update.
[Verizon Samsung Galaxy S 4] k1mu:
Actually, it's a defect in the install.bat script. I'll fix, test, and reupload shortly.
[Verizon Samsung Galaxy S 4] TemporalShadows:
In the past, when using ADB on linux no drivers were required. You do have to make a few changes for it to work with a specific phone model, though.

Here's a tutorial that should work:

http://community.linuxmint.com/tutorial/view/888

After you can see your phone when running "adb devices" just run each command in the .bat file manually and it should work.
[Verizon Samsung Galaxy S 4] Surge1223:
Linux should work the bat file would need to be modded slightly though, adb for linux should work fine it depends on the knowledge level of the linux user and whether or not they know how to add adb to their path (PATH=${PATH}:/path to adb) then the bat file would need to be edited with this added to the first line #!/bin/sh and then some other small edits. It would probably be faster to use windows though
[Verizon Samsung Galaxy S 4] k1mu:
That's answered in post #1 - no warranty void from Saferoot.

Since you ask that FAQ, I feel that I should point out that if you consequently try to flash a custom kernel or recovery, you WILL set the flag and permanently void your warranty.

Yet another FAQ. :(

You can flash a stock ROM and that will clear the Custom flag but it will not clear the Knox Warranty Void flag. There's currently no known way to clear the warranty void indication.
[Verizon Samsung Galaxy S 4] brian6685:
Has anyone been able to fix or get past the unable to disable knox problem with mk2?
[Verizon Samsung Galaxy S 4] ichibantokkan:
Gt-i9505 buil MK9 from Vodafone Portugal rooted successfully with this metod :victory:

thanks
[Verizon Samsung Galaxy S 4] bgmg:
My MK5 rooted successfully. In post one it sounds to me like busybox was supposed to be installed during the process, yet busybox did not install. Though I'm a certified network engineer and a certified nerd with many other certs, i still have much to learn regarding this newer cell phone stuff. Four weeks ago I was using a palm pre lol

So please forgive if this is a dumb question but... was busybox supposed to be auto installed during this safe root?

And I'm still reading around just to find out what busybox is and does. I hate being a nerd and yet a noob..ugh
[Verizon Samsung Galaxy S 4] k1mu:
Yes, busybox is installed post-reboot.

What busybox gives you is a large set of standard Linux command line tools. There's no application icon that shows up, but you'll see a bunch of programs in /system/xbin that point to the busybox binary. find, dd, diff, ftpd, hexdump, .... lots of different programs, that some programs assume are in place for a rooted ROM.
[Verizon Samsung Galaxy S 4] bgmg:
Thanks k1mu. That makes sense. I also installed the busybox app on the playstore. I don't know yet what it does or if it's even related to all this. This is new world to me, but I'm learning fast. As you can see I purchased xda premium as well as su pro and several other apps to help the cause and show my appreciation for all the help.

I have more questions but I need to read more first and am too tired to type any more tonight.
[Verizon Samsung Galaxy S 4] k1mu:
Nope. I've considered lots of ways to try to work around this, and built test code that so far hasn't worked. Unfortunately, since the VZ MK2 builds don't have this problem, it's kind of hard to figure out a fix. Some people running AT&T phones with MK2 are able to root, so it's some update post-MK2 that's blocking things. If there's a no-wipe MK2 ROM image for your phone, you could try flashing that to see if that allows rooting.
[Verizon Samsung Galaxy S 4] JerryGNYC:
Hi. For when you're not so tired, and had some coffee (or such :silly:) -

http://en.wikipedia.org/wiki/Busybox

Cheers,

-Jerry (Certifiably Insane IT Professional) :cool:
[Verizon Samsung Galaxy S 4] Segamalaga:
Noob question. Please don't be cruel :fingers-crossed: :

Could I use this method on my I9505 4.4.2 Kitkat?

Thanks in advance
[Verizon Samsung Galaxy S 4] k1mu:
If it's not in the first post, I don't know. The i9505 is rootable for some builds, so it may be worth trying, but Samsung has 4.3 builds with the patches that keep saferoot from working. That seems to make it unlikely that a 4.4 build will be vulnerable.
[Verizon Samsung Galaxy S 4] bgmg:
Thanks Jerryjync. That was interesting reading. Now I need to read and learn what this busybox pro app on the play store can do for me If anything. The description on the play store wasn't helpful. Perhaps I should not have bought it lol

I just kept reading every one talking about busybox, I thought maybe i better buy it, so I bought it a few days ago

On initial launch It seem to want to make a backup of my rom or phone or something. In any case, I'll figure it out.
[Verizon Samsung Galaxy S 4] JerryGNYC:
I've been using this one for a few years now, on my EVO 4G and EVO 4G LTE. Works great, I just would do a straight install, none of the fancy options...

https://play.google.com/store/apps/details?id=stericson.busybox

Will probably root my GS4 next week. :D
[Verizon Samsung Galaxy S 4] muj123:
Confirmed working with Note 2 N7105 4.3

KNOX 0 :D

Thanks
[Verizon Samsung Galaxy S 4] bgmg:
Jerry,

That's the same app I have except I bought the pro version. What do you use it for?
[Verizon Samsung Galaxy S 4] mohseen khan:
After rooting mk9 ur knox trripped to 0x1 .????
[Verizon Samsung Galaxy S 4] gothicasshole:
You can install busy box from the play store but it is hidden it's in a system/bin file if I'm not mistaken.. you can use a busy box detector from the play store!! ;) welcome to android and welcome to the forums and thank you for not going ios you think a locked boot loader is bad?? Try getting anything apple might as well come with a master lock hooked to an electric fence
[Verizon Samsung Galaxy S 4] domnic79:
Not working on GT-n7100 ML4. :(
[Verizon Samsung Galaxy S 4] thecensor:
Having the exact same problem with my Verizon Note 2 on 4.3. rebooting didn't help.

can you help?

Thanks
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
What problem? The post you quoted says they were successful
[Verizon Samsung Galaxy S 4] thecensor:
Sorry, the original problem (which is still mine):

"Im trying to root and the script it stuck at "Sending files to your device" for like 20+ minutes.... what should I do? "

I also tried and failed with Kingo Android root and Odin "\I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5"

Maybe I should also add that I bought this phone used and it has not SIM or SD card.

Thanks
[Verizon Samsung Galaxy S 4] k1mu:
No, it won't trigger the Knox Warranty Void flag. Why do people keep asking this?
[Verizon Samsung Galaxy S 4] k1mu:
Then ADB isn't working right. You need to verify that USB debugging is on. Of course, saying what kind of device you're trying this on, what model it is, etc. would be kind of helpful as well. What you tried flashing is apparently for an i605 - a Galaxy Note 2. Some people have reported success rooting those.

If it's consistently getting stuck transferring those files, I'd suggest trying a different USB port, perhaps a different cable.

If your PC can't communicate reliably with your phone, Kingo won't work either (it uses the same exploit, after all..)

Neither is needed.
[Verizon Samsung Galaxy S 4] thecensor:
Tried different cables and USB ports. My device is I605VRUEMJ9 . which is OTA updated by previous owner.
[Verizon Samsung Galaxy S 4] k1mu:
Lots of questions to at least narrow this down:

Are you doing this on Windows, OSX, Linux? What version?

The first thing after the "Sending files to your device" is a sideload of Superuser.

Do you end up with a copy of SuperSU installed on your phone?

Then, try a few things to figure out where it's hanging.

Open a command prompt and use the "cd" command to change your directory to wherever you unpacked Saferoot.

Start with "adb devices" - do you see a device show up?

Then "adb install Superuser.apk"

Does that work or not?

Then "adb push getroot /data/local/tmp"

Any errors from that?
[Verizon Samsung Galaxy S 4] thecensor:
You were right. I connected the phone to USB port this time without the long extension cable, but I didn't try this method yet, but rather the Odin one:

http://xdaforums.com/showthread.php?p=34891181&highlight=vruemj9#post34891181

I flashed it successfully, but I'm still on 4.3
[Verizon Samsung Galaxy S 4] alley23:
will this rooting method will work on below link for S4 i9505xxufna5???

http://www.sammobile.com/2014/01/16/exclusive-i9505xxufna5-leaked-android-4-4-2-kitkat-test-firmware-for-galaxy-s4-gt-i9505/
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Already answered only a few posts ago
[Verizon Samsung Galaxy S 4] dd00:
the last message has not reappeared... Unimportant!(?)

OK for me : I9505, Android 4.3, MK9.

Only a difference with k1mu tutorial in [ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3.

On dos box launched by install.bat, the last message was : "[*] Waiting for last message to re-appear..."

But nothing re-appear... and my phone is rooted.

Perhaps I might have had to disconnect and reconnect the phone?

dd, Bordeaux
[Verizon Samsung Galaxy S 4] k1mu:
Assuming you mean "Waiting for phone to re-appear..."

At that point, the phone is rooted. The script reboots it and waits for it to re-appear over ADB.

Perhaps disconnecting and re-connecting will work, or you may need to toggle the camera mode.

What you have, since you haven't finished the script, is a rooted phone with busybox not installed and an extra file (/system/xbin/super) that you can remove at your convenience.
[Verizon Samsung Galaxy S 4] dd00:
Thanx for your answer. You assumed well :)

Can I install busybox manually? Or is it safer and more efficient to run the script again?

dd, Bordeaux
[Verizon Samsung Galaxy S 4] k1mu:
It's easier to install busybox from the Play Store.
[Verizon Samsung Galaxy S 4] TMMhere:
It works !!!

Samsung S4 GT-I9505

Android 4.3

Build: JSS15J.I9505XXUEMKE

Root works fine, Knox Warranty Counter 0x0 :victory: :D :good:

Many Thx for this solution !!! :good::highfive::cool:
[Verizon Samsung Galaxy S 4] ashkan78:
appreciate your job, work grate.
[Verizon Samsung Galaxy S 4] gothicasshole:
How do you tell your knox status?
[Verizon Samsung Galaxy S 4] mohseen khan:
Samsung S4 GT-I9505

Android 4.3

Build: XXEUMK9

Root works fine, Knox Warranty Counter 0x0 good

Many Thx for this Developer !!!
[Verizon Samsung Galaxy S 4] JerryGNYC:
Basically, all the app is used for, is to update the busybox binary. Your purchase of the Pro version provides a donation to the author.
[Verizon Samsung Galaxy S 4] dimkit:
i am doing the procedure , and after the phone reboots i receive the message , something has delete SU -looking for the backup copy

The backup is gone too - can't recover,

Superuser is installed on the phone but without root access , i am trying it to the latest I9505XXUENA4

Sorry i find now that i can not root , but if i install previous version of the rom will be able to root?
[Verizon Samsung Galaxy S 4] byzking:
You're my hero! No homo. lol
[Verizon Samsung Galaxy S 4] k1mu:
Did it show the "this device is not supported" message prior to reboot?

That's the indication that it's not rootable using Saferoot, which you appear to have figured out.

You can't root using this without downgrading your kernel, but the Samsung bootloader won't allow that (and will set the "Knox Warranty Void" flag if you try it.)

When I get a chance, I'll look at making the script a bit smarter about this as it really should notice that things didn't work and un-do what it did before the failure.
[Verizon Samsung Galaxy S 4] dimkit:
Finally i downgrade to MK9 (they use the same bootloader with ENA4), i use safe root succesfully and then i update with mobile odin and ever root option .

Now i am with the latest XXUENA4 fully rooted and with KNOX 0x0.

Thanks a lot. you are the best

P.S. I do not know why you say that the system status will be custom , but mine is still official and OTA still works
[Verizon Samsung Galaxy S 4] JerryGNYC:
Worked very nicely for me. Just could't get it to work (see the phone) on 64-bit Windows 7 Enterprise until I rebooted into 32-bit and there I had to install the Samsung USB drivers linked in the OP (KIES worked fine either way, go figure). Thanks very much [MENTION=3940199]k1mu[/MENTION] :good: :good:
[Verizon Samsung Galaxy S 4] k1mu:
OK, that's good information. For us, the MJ7 and MK2 builds use the same bootloader so we can downgrade.

As far as the status goes, apparently you've got a phone with less aggressive checking for unauthorized software. Be happy about that. :)

Oh, and OTAs: those usually go OK as long as you haven't done anything else (de-bloat, freeze apps, install xposed.)
[Verizon Samsung Galaxy S 4] k1mu:
I'm on 64-bit Windows 7. No idea why it's not working for you, but that's not important as you have it working.
[Verizon Samsung Galaxy S 4] k1mu:
Boot into the bootloader (power/home/volume down) and read the very tiny type on the screen.

Hold down the power button when you're done to shut off.
[Verizon Samsung Galaxy S 4] mstammyt:
Sprint GS4 MK4 on Saferoot..

Saferoot worked great on my Sprint GS4 MK2. Now I would like to program it to us the Hotspot. Does the Saferoot have built in recovery? I have been very confused by different posts.. Maybe someone can just give me simple instructions on using the hotspot with Sprints GS4 MK2 phone with Saferoot already applied??

Thanks for any help..

Tammy
[Verizon Samsung Galaxy S 4] JLow0214:
Just used this to root Sprint SPH-L520 Galaxy S4 Mini worked like a champ :good:
[Verizon Samsung Galaxy S 4] k1mu:
No, all you get from this is root. The only recovery available for MK2 is Safestrap, which has a limited set of ROMs available.

Given that you ask about recovery, please take a step back, and read the information here in the Q&A and general forums. You WILL brick your phone if you try to install custom recovery, but that's been stated over at least hundreds of times here in these forums.

As far as the hotspot goes, you should search the Sprint forums for your phone for help.
[Verizon Samsung Galaxy S 4] JerryGNYC:
And if I may be so bold as to say, please do not quote a (relatively) long OP (first post). Especially if you've read it... you DID read it, right? :)

Copy and paste what snippets may be pertinent, but not the whole thing...

Thanks! :good:
[Verizon Samsung Galaxy S 4] spinninbsod:
thank you

it works great really easy to do didnt set knox set custom boot flag but you said that it would just downloaded wanam xposed and it works great

yay i can customize my s4 finally
[Verizon Samsung Galaxy S 4] axtn95:
For anyone wondering, works great on Sprint GS3 4.3 MK5
[Verizon Samsung Galaxy S 4] JerryGNYC:
SPH-L710, yes?
[Verizon Samsung Galaxy S 4] axtn95:
Exactly! :)
[Verizon Samsung Galaxy S 4] JerryGNYC:
Great, thanks! Can use this on my wife's phone... :)
[Verizon Samsung Galaxy S 4] celiocalves:
Can you guys confirm if this safe root is working good with i9505 internacional model?

No app crashing or failed root?
[Verizon Samsung Galaxy S 4] yake:
It works for 'some' International I9505 MKE. It depends on the security updates applied to it.

Mine was a fail...

It's just a matter of trying, since as the name says it is a 'Safe' root method, as it should not flag your Knox counter.

I would like to know if there is some method to revert the security patches and go back to the 0day, just after the update to MKE (maybe a no-wipe rom?).
[Verizon Samsung Galaxy S 4] k1mu:
No-wipe should remove any security updates post-MKE, so it should then allow you to root.
[Verizon Samsung Galaxy S 4] celiocalves:
Mine is i9505 MKF with kernel 3.4.0

If I try to root (with this saferoot) and it fails, the phone will continue working like never happened?

If I flash the stock MKF ROM again from sammobile website with odin it will not trigger the knox flag?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Correct on both points as long as the mkf is the official (either wipe or no-wipe should install fine)
[Verizon Samsung Galaxy S 4] celiocalves:
Thank you !

Only one more question:

Some people are saying after this root some apps that worked fine, now are stopping/crashing. Its cause of this root?

---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------

"No wipe" you mean stock rom or another ROM modded to not wipe?
[Verizon Samsung Galaxy S 4] k1mu:
If you could please provide a pointer to the "some people" it would be appreciated. That's extremely unlikely.

The only cases I'm aware of are people who root then use the fact that they're rooted to remove critical system files.

If you root your phone then drop it in the toilet, then you can't blame the fact that it's now dead on it being rooted. :)

A "no wipe" ROM is a factory ROM that's been modified to not remove user data. It cleans and re-flashes /system.
[Verizon Samsung Galaxy S 4] celiocalves:
Sorry, i don't want say nothing bad about your work with that previous post.

I've just read some posts in the thread and some people said that.

Your work with this root is funtastic, i don't have doubt of that, almost everyone could root the device.

I will try to root now, to see if it works for me.

Keep the good work! You are good ;)

---------- Post added at 03:03 PM ---------- Previous post was at 02:35 PM ----------

During root process the superSU app asks to "try to disable knox". Click OK or CANCEL?
[Verizon Samsung Galaxy S 4] Mistertac:
Hit ok
[Verizon Samsung Galaxy S 4] celiocalves:
Thank you all guys! :D

I successfully rooted my device with no problems! :victory:
[Verizon Samsung Galaxy S 4] imafriend123:
What do you mean restarted script? How do you do that?
[Verizon Samsung Galaxy S 4] imafriend123:
i'm stuck on sending files to your device.

I've done everything. flashed two odin files and still nothing. i tried replacing usb cables and ports every way possible still doesn't work. help please~!
[Verizon Samsung Galaxy S 4] k1mu:
What kind of device, what OS are you using?

It may be that the install is failing for some reason. The first thing the script does is to install SuperSU.

Is anything showing up on your phone or the notification area?

Another thing to try - Settings/More/Security. Check the "Unknown sources" box.

If all else fails, edit the install.bat file.

In this area:

echo [*] Sending files to your device...
files\adb install files\Superuser.apk >NUL 2>&1
files\adb push files\getroot /data/local/tmp/ >NUL 2>&1
files\adb push files\su /data/local/tmp/ >NUL 2>&1
files\adb push files\busybox /data/local/tmp/ >NUL 2>&1
files\adb push files\install-recovery.sh /data/local/tmp/ >NUL 2>&1

Remove the ">NUL 2>&1" at the end of each line. Try it again - any errors with the adb install or adb push operations will show up on your PC.

Finally, you could comment out the first (adb install) line by adding "::" at the beginning of the line.

Install SuperSU from the play store. Then try rooting.
[Verizon Samsung Galaxy S 4] justpastfinish:
I tried searching bit I couldn't find anything. If I just use this method to root my mk2 Verizon s4 will this wipe my phone?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
No but you should back it up as well as you can anyway beforehand. This is a root exploit not a ROM
[Verizon Samsung Galaxy S 4] justpastfinish:
Thx
[Verizon Samsung Galaxy S 4] ghanson:
Tip For DOS Command Line Junkies

I was running the Saferoot exploit on my I337 MK2 and it would simply stop at the pause during "Testing adb usability." I double-checked and triple-checked my settings and all was correct. I logged into adb and confirmed that devices were active and I could run the adb shell successfully. Of course, I couldn't mount the phone /system because I wasn't root and the Knox Shield would pop up over on my GS4. So I knew the software platform was okay.

I was running from an elevated command prompt (CMD.EXE) on my Win 7 x64 machine because I just assumed that would be the best way to execute install.bat. Then it dawned on me that maybe this was a PATH issue...

I executed install.bat from within Windows Explorer and Saferoot immediately started running and completed successfully within a few minutes!

The moral of the story: Don't overthink it; simply run install.bat from within Windows Explorer!

Fantastic work k1mu!

---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------

Follow up:

Successfully created a nandroid backup using TiB, w00t!

Thanks again, k1mu for the great work and for sharing it with all of us.

Greg
[Verizon Samsung Galaxy S 4] imafriend123:
I'm using Verizon Galaxy S4 on MK2. So, I followed your tip and it starts but stops again at

"/system/bin/sh: /data/local/tmp/getroot: not executable: magic 7F45
[Verizon Samsung Galaxy S 4] k1mu:
The first thing I can think of offhand is that you're trying these commands inside a terminal emulator window, not via adb. However, the error I get when I try that is different.

The next thing is that your phone has a SEAndroid/Knox security policy update that blocks adb shell from running untrusted programs.

(While you can disable Knox notifications using SuperSU, you can't turn off Knox enforcement.)

Here's how you can help find out what's going on. There's a line in the install.bat that reads

files\adb shell chmod 0755 /data/local/tmp/busybox

Just below that, add

files\adb shell /data/local/tmp/busybox ls -l /data/local/tmp

(That's "LS -L" in lower case, since capital i and lower case L look the same.)

If you run that and get the same "not executable:" error, then it's a security policy issue.
[Verizon Samsung Galaxy S 4] squir002:
Works perfectly on Samsung Galaxy S4 Mini LTE (GT-I9195) [PDA:MJ7 / PHONE:MJ7 / CSC:MJ2 (XEF)] :)

Huge beer for you!

(KNOX flag 0x0 <3)
[Verizon Samsung Galaxy S 4] imafriend123:
So there's nothing I can do if it's a security issue?
[Verizon Samsung Galaxy S 4] k1mu:
Not necessarily. AT&T MK2 has been successfully rooted in the past, so the key is to understand what's going on.

It may be possible to inhibit the security policy long enough to gain root if I can understand what's happening.

Worst case, flashing a no-wipe factory ROM may get you an older policy file and allow rooting.
[Verizon Samsung Galaxy S 4] dean2900:
I need help!

I have a VZW I535 and hated that I took the 4.3 OTA update. I used the saferoot with success but then my phone started giving errors about the Unfortunately, the program has stopped working for anything. I opened up a shell and unrooted the phone and have hard reset it several times, removed battery, removed the sim, sdcard, etc. No matter what I do, after I do a clean wipe of the data and the cache, the phone keeps saying "Unfortunately, the Internet has stopped working" or whatever app. I cant even setup my corporate email because I get the "Unfortunately, the email has stopped working" even after wiping the device clean and going through the setup wizard unrooted. I have double checked with programs to make sure busybox is uninstalled and so is any root permissions.

Does anyone have any idea what I can do at this point? I don't even care if it is rotted anymore, I just want it where I can get my email.

I am 2 months away from my Verizon contract expiring and will be going away from them. They just put on too much crap!

Thanks in advance,

Dean