yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] gunzaa:
I haven't been able to root with this method successfully. After I connected my phone into the computer and checked Developer setting options, I opened install.bat and nothing happens.

Now I see the message:

daemon not running. starting it now on port 5037

Then nothing happens again...not sure what the problem is. . do I need to install SDK?
[Verizon Samsung Galaxy S 4] uribees:
So I was able to root successfully on MJ7 (thank you for that). If I take the new OTA will I be able to re-root using the same method? Also is there a way to just keep root even if taking the new Verizon OTA? I used to use Voodoo Root Keeper but it doesn't support 4.3.
[Verizon Samsung Galaxy S 4] jco897j:
I'm personally going to ditch OTAs for a while. With Safestrap headed our way I'd hate to update and lose that possibility. Plus I'm still holding out for a bootloader exploit. I constantly monitor several threads I'm subscribed to. I'll never give up hope.
[Verizon Samsung Galaxy S 4] dgutierrez04:
People are saying this method also works on mk2 ota update. Do not used voodoo used SuperSU and enable the "Survival Mode" and update it. Like I said people r saying this method works for mk2. Or u should wait until more people are reporting they can enable root access on mk2.
[Verizon Samsung Galaxy S 4] tyson10:
If you take the OTA -- you can use this same method to root. I was able to complete last night via SDK
[Verizon Samsung Galaxy S 4] jco897j:
The root method works. But Hash is working on safestrap with MJ7. So if you have plans on using it it's better to be safe than sorry.
[Verizon Samsung Galaxy S 4] Mauri65:
[*] Trying to disable Knox... Programs hangs here. Knox notification.I remove and reinsert usb cable into pc

[*] Rebooting... Please wait.

error: device not found

[*] Waiting for device to re-appear...

[*] Checking if su is still there

-rwsr-sr-x root root 104500 2014-01-12 17:01 daemonsu

-rwsr-sr-x root root 104800 2014-01-14 23:01 super

Wait until your phone reboots,then unlock it and Press any key to continue . .Phone does not reboot here. I restart it manually

On your phone, open SuperSU and let it update if it asks.

When SuperSU is done updating, Press any key to continue . . .KNOX intervenes again

On your phone, watch for the SuperSU permission popup and give

permission for ADB Shell to gain root permissions.

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

[*] Disabling Knox

/system/bin/sh: /system/xbin/su: not found

[*] Setting Permissions

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

/system/bin/sh: /system/xbin/su: not found

[*] Installing busybox

/system/bin/sh: su: not found

Nothing has basically changed.
[Verizon Samsung Galaxy S 4] grmncrsnbr:
Just Ran this on my Verizon S4 and received this:

[*] Waiting for device to re-appear...

./install.sh: line 128: unexpected EOF while looking for matching `"'

./install.sh: line 129: syntax error: unexpected end of file

I can't update the superuser binaries
[Verizon Samsung Galaxy S 4] k1mu:
And, if you "adb shell" into the phone and type "super" what happens?

I suspect that our buddy Knox will block it, but it's another data point.

The script is *supposed* to see that the 'su' isn't there and fall back to trying the second copy (super), but doesn't. I'll see if I can find out why.

I do have some other ideas that are worth trying - I'll build another installer tonight.
[Verizon Samsung Galaxy S 4] Mauri65:
C:\>adb shell

shell@jflteatt:/ $ super

super

and it hangs there, while Knox trips on the phone.
[Verizon Samsung Galaxy S 4] Nirak:
Rooting worked like a charm on my international GT N7100 (KNOX bootloader MK9), but when i installed Triangle Away 3.25 it didn't work, so i installed an older version of it, 3.10.

This one worked en fully resetted my binary counter, unfortunately this tripped knox :crying:

Maybe i made the mistake of using an older version of TA, i didn't read enough before i decided to do that, or maybe it's just how TA works, regardless of which version.

Anyhow....i've now joined the official Knox 0x1 club, while everything else is flagged 'official'.
[Verizon Samsung Galaxy S 4] studiorat:
just click ok

normal...
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
TA even contains warnings that you can trip knox...why wouldn't you just use Xposed as was suggested (or better leave the custom screen which is harmless and only appears occasionally) you had a perfect phone and then made it void :sigh:
[Verizon Samsung Galaxy S 4] decaturbob:
no need to do any of that....
[Verizon Samsung Galaxy S 4] k1mu:
Edit the install.sh, line 74 - remove the quote after No.such.file.or.directory"

The same change is needed on line 79.
[Verizon Samsung Galaxy S 4] Nirak:
[MENTION=5447130]Nergal di Cuthah[/MENTION] and [MENTION=3882268]decaturbob[/MENTION]

Your both right, but i needed to bring my device back to stock as close as possible, wanted to give it a go and since both flags void warranty it's not sucha big deal.

Tx anyway
[Verizon Samsung Galaxy S 4] simonsalo:
can we root i9506

Can we root 9506 & is the lock symbol on boot removed?
[Verizon Samsung Galaxy S 4] landous:
Just rooted my Sprint S4 running MK2 successfully. Thanks for the tutorial.
[Verizon Samsung Galaxy S 4] k1mu:
Hmm. The search function appears to be missing.

Several have asked about the 9506, but as far as I recall nobody has reported.

Re: the "Custom" symbol on boot: please see post #2. I won't taunt you this time. :)
[Verizon Samsung Galaxy S 4] gadget069:
I've been watching for awhile now. I know some att users are having issues rooting. But it seems only if they're not restoring completely back to stock? Currently on mf3 planning on odining back to stock mf3 then applying the mk2 update zip.
[Verizon Samsung Galaxy S 4] k1mu:
Damn. So what that means is that Knox is blocking SuperSU entirely.

OK, sorry to keep tossing out new root programs, but the "saferoot-test.zip" in post #2 is another attempt. This tries to disable the Knox agent by editing the package configuration file. If this works, you'll need to apply it twice - run it until it reboots the phone, then use Control-C to stop the batch file. Re-start it from the beginning and cross your fingers.

Sorry for these repeated tries, but it's a tough nut to crack, apparently.
[Verizon Samsung Galaxy S 4] Mauri65:
No need to say sorry, I should be the one to apologize for wasting your time (and actually am apologizing :o).

Anyway, nothing positive out of this attempt:

--- Samsung Galaxy S4 Android 4.3 Root ---

--- Based on the CVE-2013-6282 exploit by cubeundcube ---

[*] Testing adb usability

Plug in your phone and Press any key to continue . . .

[*] Waiting for your phone to appear

[*] Your phone is detected and ready for rooting.

[*] Sending files to your device...

[*] Displaying initial status

-rwsr-sr-x root root 104500 2014-01-12 17:01 daemonsu

[*] Starting rooting program.

ro.build.product=jflteatt

ro.build.id=JSS15J

Succeeded in getroot!

Remount success!

Copying files..

Error opening /system/xbin/daemonsu for write: Permission denied

Setting property to disable Knox

Done.. reboot to enable root!

[*] Removing temporary files...

[*] Trying to disable Knox...

and again it hangs here..
[Verizon Samsung Galaxy S 4] k1mu:
OK, that's expected for the first pass since Knox is still active.

Just to verify, is this still happening to you after you kill it and try the root a second time? If so, that's not good news.

You may need to re-flash stock to get rid of the su stuff that's left behind as I'm running out of ideas.
[Verizon Samsung Galaxy S 4] Mauri65:
yes, still happening.

What exactly do I need to reflash/ get reflashed, the ROM or the recovery image, or..?

Thank you a lot for your time.
[Verizon Samsung Galaxy S 4] gothicasshole:
Do me a favor go to your start bar type cmd. Open the command line. Hook up your phone make sure usd debugging is checked. Settings>more>developer options>usb debugging. Type in adb devices. If the command line says adb is not a command or executable file. You need these two files: adb.exe and winapi.dll. you can get these by downloading the android sdk. But i will be a sport and upload them in my next post along with instructions!!:D if it comes to a samobile37e73r7urur (example only!!!!) Then adb is working properly
[Verizon Samsung Galaxy S 4] SmOoThEm:
Can someone explain to me what makes a rom safestrap compatible? What can I do to a rom to make it boot with safe strap?
[Verizon Samsung Galaxy S 4] k1mu:
You'll need to poke around in the ATT forums to find a ROM image you can flash.
[Verizon Samsung Galaxy S 4] k1mu:
adb for Windows, Linux, and Mac OSX is included in the saferoot kit. No need to re-post.
[Verizon Samsung Galaxy S 4] k1mu:
The ROM needs to be built to use the stock TouchWiz kernel that's on the phone, as Safestrap can't replace the kernel. (Flashing a non-Samsung kernel will set the "Knox Warranty Void" flag.)
[Verizon Samsung Galaxy S 4] gothicasshole:
Its going to be a seperate thing it should be in the op below the original rom and say ss edition its splits it into moduals that you flash seperately as where people with unlocked boot loaders and cm recovery its a regular.zip file with the kernel attached after a dalvic, cache and system wipe you simply flash it.

But with safe strap you flash the rom wipe then flash the mk2 (or what ever baseband moduals then the kernel moduals you get it? Its basically broken into differant sections you have to flash in succession i hope i didnt confuse you oh and for now we can only flash 4.3 roms no kit kat!!!! They're working on it but as of rite now all the extra securiry at&t/samsung put on it anybother way is doomed to brick SO ****ING READ ON SAFE STRAP AND HOW TO USE IT COMPATABILITY IT SUCKS FOR ME TO I WANT A GOOGLE EDITION ROM TO BIT IM LIKE YOU I MUST BE PATIENT
[Verizon Samsung Galaxy S 4] gothicasshole:
ok im a man of my word :) :D THIS IS FOR WINDOWS ONLY!!!!!!!! NO MAL WARE OR ANYTHING FUNNY THIS IS STRAIGHT FROM THE SDK:) all you need to do is to decompress those backups.rar extract the adb.exe adbwinapi.dll adbwinusbapi.dll and the fast boot.exe....

OK GO TO YOUR START BAR LOOK FOR COMPUTER IT SHOULD BE ON THE RITE OPEN IT GO TO YOUR C DRIVE FIND WINDOWS. SIMPLY DRAG AND DROP ALL OF THE FILES INTO YOUR WINDOWS FOLDER PAY NO MIND TO THE SECURITY DIALOG ITS JUST STANDARD TO ASK FOR PERMISSION:) NO FUNNY BUISNESS I SWEAR:angel: OK ONCE YOU GOT THEM IN ALL YOU NEED TO DO IS SIMPLY DOUBLE CLICK THE ADB.EXE AND FASTBOOT .EXE PRESS RUN FOR BOTH YOU WILL SEE A QUICK COMMAND PROMPT FLASHING THE FILES TO YOUR WINDOWS FOLDER... GO BACK TO YOUR START BAR TYPE IN CMD AND MAKE SURE YOUR PHONE IS HOOKED IN. MAKE SURE USB DEBUGGING IS CHECKED. SETTING>MORE>DEVELOPER OPTIONS> USB DEBUGGING CHECK IT AND MAKE SURE DEVELOPER OPTIONS IS TURNED ON :) IF YOU DO NOT HAVE DEVELOPER OPTIONS GO TO SETTINGS>MORE>ABOUT PHONE>TAP MODEL NUMBER UNTIL IT SAYS DEVELOPER OPTIONS ARE ENABLED CLICK BACK AND GO TO YOUR DEVELOPER OPTIONS AND REFER BACK TO ^^^

NOW OPEN THE COMMAND PROMPT AND TYPE ADB DEVICES IF IT SAYS SAMOBILE 4836456543567 (EXAMPLE) IT MEANS ADB DAEMON IS SUCCESSFULLY RUNNING :) OK IF IT SAYS WAITING ON DEVICE GO TO DEVELOPER OPTIONS PRESS REVOLK USB DEBUGGING AUTHORIZATION UNPLUG THE PHONE PLUG IT BACK IN WAIT FOR THE DIALOG BOX TO ASK FOR PERMISSION CHECK ALWAYS REMEMBER THIS COMPUTER. NOW LETS ROOT THAT SHINY GS4!!!!:d:d:d

NOW OPEN YOUR ROOT SCRIPT AND DOUBLE CLICK THE ROOT.BAT AND YOU SHOULD BE GOOD TO GO :) ROOTED MY MK2 BASEBAND :) FOLLOW THE ON SCREEN INSTRUCTIONS AND IT SHOULD INSTALL ALL OF THE FILES ALSO CHECK STAY AWAKE IN DEVELOPER OPTIONS AND PAY CLOSE ATTENTION TO THE SCREEN SO YOU DONT MISS THE SUPER.SU PERMISSIONS CLICK GRANT AND UPDATE THE BINARIES WHEN YOU REBOOT AND IT SHOULD DISABLE KNOX :)
[Verizon Samsung Galaxy S 4] marlar:
Do you mean that there is a problem with this root method and that we should wait a bit? Or is it only a problem with certain phones/models?

I have a S4 (GT-I9505), I9505XXUEMKF

PS. If the Knox flag isn't an issue, are methods like CF-Auto safer than this?

Btw, thanks for your awesome work!
[Verizon Samsung Galaxy S 4] k1mu:
No, the problem is with an ATT phone that apparently took an update to MK2 with SuperSU installed. It's now locked down so SuperSU can't run.

No, CF-Auto isn't safer, as it will set the Knox Warranty Void flag. And, incidentally, won't root your phone (at least for the i545 MJ7/MK2).
[Verizon Samsung Galaxy S 4] joedajoester:
I am thinking of rooting my dads phone with this method. He is sick of all the bloat that cant be removed, so he is really considering it. The only thing is that if his phone bricks in the process or something, he has nothing; and he needs his phone for work too. I have a gs3 running cm11 on it, so i have some experience with samsung devices, but i just want to know if i should go for it, and what can i do if something goes wrong?

To simplify this all:

*What are some known issues that can occur during the process, and how would i resolve it?

*Will supersu ask to disable knox, or will the install.bat do it?

*Do i have to remove all the knox apps in system/app?

*What happens when there is a new update, will i have to odin to be able to take it? Will i run into problems if i even want to root again?

Thanks a lot guys :)
[Verizon Samsung Galaxy S 4] k1mu:
Um, as I said, what you've just posted is not needed. A working copy of adb is included with the script in the original post.

The adb here is identical to the copy included with the saferoot.zip in the OP.
[Verizon Samsung Galaxy S 4] joetrizeo:
YES YES YES!

I too used this on a Verizon Samsung galaxy s4 mini SCH-i435!

k1mu - Thank you so much for your hard work and for completeness in your solution (comments, notes, full explanation and including ADB). Easiest root ever.

postal302 - Thanks for researching this, risking your device, and letting the s4 mini forum know! I too was anxious for a safe root.

When mine asked 'try to disable Knox' I chose YES and it successfully disabled it. I noticed k1mu's script tries to disable it as well and my line said 'disabled'. I don't know if it matters if supersu disables it or the script. Maybe k1mu will chime in.

Thanks!
[Verizon Samsung Galaxy S 4] nlatifolia:
MK2 Note 3 ?

I wonder if anyone was able to root MK2 on Note3 with this rooting method ? Please kindly share your experiences.
[Verizon Samsung Galaxy S 4] kuijkens:
I can confirm this methods works for the GT-I9505 running on MKF!

Rooted, no knox triggered.

Thanks!
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
Help

Hi, few days ago I rooted my phone "Samsung Galaxy S4 GT-I9505" with this metod.

Now my phone starts rebooting all the time when battery is lower then 50% and now I must send it to service.

I need to unroot my phone before sending it to service.

If I unroot my phone with SU app, will phone status get back to "official" or not?

By the way Im from Croatia "EU".

Thanks!
[Verizon Samsung Galaxy S 4] ricardo1976:
Works on MK8 / MK9 ?

Does saferoor work on Mk8 build ? Thanks in advance.
[Verizon Samsung Galaxy S 4] Nirak:
I wonder if i could use this on my SM-N9005 (Int. Note3) on build MK2 (baseband MJ7)?

I'm scared to give it a try myself...device is brand new....just one week old.

---------- Post added at 06:23 PM ---------- Previous post was at 06:18 PM ----------

I unrooted a GT N7100 as described in OP and did a factory reset afterwards.

Device status returned to 'official'.
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
Have you done just this:

1. How do I unroot?

OK, so why are you so anxious to unroot just after rooting?

There's two things you need to do to undo what this installer does. First, remove busybox. This will require adb shell or the use of Terminal Emulator to get a shell prompt. Do the following at the shell prompt:

$ su

# mount -o remount,rw /system

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

# rm -f /system/xbin/selinuxoff*

# find /system/xbin -type l | xargs rm

# rm /system/xbin/busybox

# mount -o remount,ro /system

# exit

$ exit

Now, open SuperSU and use "Settings", "Full unroot". When that's done, everything that this installer has done has been reverted.

If you've installed xposed framework or wanam, you should remove those and reboot BEFORE doing the SuperSU unroot. Also, if you've installed Safestrap you'll need to boot into SS recovery, delete the custom ROM slots, then uninstall Safestrap recovery. Or, uninstall the Safestrap application. If you forget to do these before doing the SuperSU unroot, you'll need to re-root to do those.

If you need adb to access your phone, there's a copy in the "files" directory included with the installer. You'll need to open a command prompt and use cd to change to the files directory before trying to use that adb.
[Verizon Samsung Galaxy S 4] Nirak:
Yes. . That's what i did and a factory reset afterwards.
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
It dont recognize this: # rm /system/etc/install-recovery-2.sh* (there is no such file)
[Verizon Samsung Galaxy S 4] Nirak:
I also had some errors in those commands, probably because busybox wasn't installed during root, but, chicken as i am...i followed everything to the letter...and it worked out.
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
What if I skip this step?

Can I get this error because I have stock rom on my phone and not custom rom and custom recovery?
[Verizon Samsung Galaxy S 4] Nirak:
To be honest. .i don't know why you get this errors, but i suggest you just perform all the steps...regardless of the errors, just go ahead.
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
I will try it.
[Verizon Samsung Galaxy S 4] The Jinxer:
Worked for me! noticed slight performance drop in launcher (stock) so i unrooted though, but great work!
[Verizon Samsung Galaxy S 4] k1mu:
That's only there for some of the versions of saferoot - if it's not there, that's not suprising.
[Verizon Samsung Galaxy S 4] gothicasshole:
Yes but if you want to run she'll commands and had total bs like I did with no connection this is all you need to run a db and fast boot as she'll commands :) for some odd reason windows didn't incorporate it as command lines until I put them in my windows folder
[Verizon Samsung Galaxy S 4] Gachmuret:
Knox disabled?!

Hi there,

Two questions :confused: :

1. I understood that it won't trigger knox, but will it disable knox or is it possible to have knox working with root? (Because I really like the idea of having a safe pw protected area for private or sensitive data and use Knox for that, but also need to have root access)

2. Does it work without triggering Knox Warranty Void for my Rom:

Baseband version, AP and CP: I9505XXUEMKF and CSC: I9505AUTEML1 ( the CSC is that I worry about, as I read MKF should work)?

Thx for your help!
[Verizon Samsung Galaxy S 4] Anubhav Agrawal:
i have a question,

if i unroot, i will still see custom flag, and if i flash a no-wipe ROM, wont it trigger kox flag?!

Can i use triangle away to undo custom flag?

Will root survive OTA when i update to 4.4.update(when it comes out?)

Cant we fake unroot?(had a method working for my old phone, where you fake unroot/non-root phone)

Help will be greatly appreciated ...

Thank You.

EDIT-Didnt root my I9500, screenshot attached, any chance of my device getting support?
[Verizon Samsung Galaxy S 4] shayind4:
...

Does this method work for international 9505?

Thanks
[Verizon Samsung Galaxy S 4] joedajoester:
I am also wondering what will happen if you are rooted and take the ota to 4.4. Will we have to odin, or something else, or will we be fine?
[Verizon Samsung Galaxy S 4] WordsworthESP:
No, it won't trip the Knox Counter, which is important, but it can disable Knox security. Similar name, different problem.

Wanam can (safely) get rid of the Custom screen, just search the forum for more info. I've heard mixed reviews about Triangle Away (tripped Knox counters, etc.)

I'd recommend you backup your Stock ROM after rooting, as there's no way to know if it'll mess up the OTA. If you're on a Stock ROM without crazy mods, etc. You might be okay and just lose root. You might even be able to use Survival Mode to keep it.

The best thing to do would be to wait and see what other users encounter, as there will be plenty who just simply cannot wait. Then make an informed decision from there.

Sent from my Hyperdriven Samsung S4
[Verizon Samsung Galaxy S 4] Nirak:
[MENTION=4974773]anu.cool[/MENTION]

This method worked flawless for my GT N7100 (Galaxy Note2 Int.), but when i used TA 3.10 to reset my binary counter it did trip Knox.

Don't confuse the binary counter in download mode with the 'custom' system information in settings > device status.

With the Note2 the 'custom' system state returns to 'official' when unrooted on stock firmware and recovery.
[Verizon Samsung Galaxy S 4] Nirak:
Got the same result as anu.cool on my SM N9005(int. Galaxy Note3).

Device not supported.

Any change of adding this device?
[Verizon Samsung Galaxy S 4] dermousis:
Unfortunately, it seems that Samsung has patched the kernel in Note 3, and fixed the vulnerability that this rooting tool uses.

http://xdaforums.com/showpost.php?p=48749875&postcount=475

http://xdaforums.com/showthread.php?t=2602344
[Verizon Samsung Galaxy S 4] niklas1407:
Hi there!

I tried to use this rooting method with my s4 mini (gt-i9195). While some users with another model reported that it works, the script produces an error while trying to root.

Maybe one of you knows some help?

--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---

[*] Testing adb usability

Plug in your phone and
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.

[*] Sending files to your device...

[*] Starting rooting program.
ro.build.product=serranolte

ro.build.id=JDQ39

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed.

[*] Removing temporary files...

[*] Trying to disable Knox...
/system/bin/sh: /system/xbin/super: not found

[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...

Something has deleted su - looking for the backup copy
The backup is gone too - can't recover!

My adb is working fine, also tried to do the steps manually via terminal, also gave the same error. :p
[Verizon Samsung Galaxy S 4] k1mu:
When you see that, it means that your device has been patched by the vendor to fix the defect that saferoot uses.

You'll need to look for another rooting technique, unfortunately.
[Verizon Samsung Galaxy S 4] shayind4:
[MENTION=3940199]k1mu[/MENTION]

Thanks for the exploit. I have just rooted my S4 9505 MJ5 using saferoot after updating adb to latest version. Need to remember 'Safestrap'.

However, the exploit did not work for my S3 9305 MK2, and it gave the errors as in 2 posts above. I used root explorer to check the filesystem. The data folder is apparently empty. Tried to create new 'local' folder in data but nothing showed even though it said new folder successfully created. Tried to adb push getroot but permission was denied and I kept noticing android security warning in notification bar. Newer roms have been patched against this exploit. It should work if it's possible to create 'local/tmp' folder in data folder (disable the android security which doesn't appear knox-related).

Thanks