yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] thajacka:
i got the same thing, while the procedure is going it says applications were blocked by some secuirty thing. then after when i open supersu is says unable to disable knox. in adb shell su not found.
[Verizon Samsung Galaxy S 4] gkersting:
I may have a similar issue. My install on MK2 went as follows:

Sending files to your device...

434 KB/s (17800 bytes in 0.040s)

2452 KB/s (100452 bytes in 0.040s)

2785 KB/s (2139595 bytes in 0.750s)

3008 KB/s (1109128 bytes in 0.360s)

61 KB/s (629 bytes in 0.010s)

Starting rooting program.

ro.build.product=jfltevzw

ro.build.id=JSS15J

Succeeded in getroot!

Remount success!

Copying files..

Done.. now reboot to enable root!

Removing temporary files...

Rebooting... Please wait.

Waiting for device to re-appear... [I never waited long enough and had unplugged cable]

I have root, as I am running SuperSu 1.86 and have got permission prompts for any root capable apps I run.

I can also su via terminal and traverse folders in /system.

To be sure I went into a terminal and ran following:

su -c mount -o remount,rw /system

su -c chmod 6755 /system/xbin/su

su -c chmod 6755 /system/xbin/daemonsu

su -c /system/xbin/busybox --install -s /system/xbin

sleep 15

su -c mount -o remount,ro /system

I now see /system/xbin/daemonsu & su as: -rwsr-sr-x from the chmod 6755

Aso, /system/xbin/busybox is present with 12/19 date.

Main problem is that after a reboot and the lockscreen appears, I get a notification:

"Currently unable to download. Please try again later." flashes 2X

Also see: SE For Android Status Enforcing SEPF_SCH-I545_4.3_0012
[Verizon Samsung Galaxy S 4] Drayk:
Don't know if this will help.....I'm a total noob here. I was having problems loading this. I disabled/force stopped knox before I rooted and that seemed to let root load. I only know about 1/2 of what I'm talking about, but that seem to work for me...

Merry Christmas!
[Verizon Samsung Galaxy S 4] NyekonX:
I attached a SS of my phone. I don't think I mentioned on an 1337 w/ AT&T as I should have. Hope you didn't reflash your phone yet.

Knox gives a very general message, I attached a SS for your reference of that too. It doesn't say what it's blocking. I tried looking for an audit.log file but can't seem to find it. Google was saying logs should be at "/data/misc/audit/audit.log" but I'm getting denied a read.

Install-recovery and daemonsu are in place as you said.

shell@jflteatt:/system/etc $ find | grep install

./install-recovery.sh

./install-recovery.sh.old

./install-recovery-2.sh

shell@jflteatt:/system/xbin $ find | grep daemon

./start-stop-daemon

./daemonsu

./daemonsu.old

Running SU from adb is a bit strange. It say's it can't find it..

shell@jflteatt:/system/xbin $ echo $PATH

/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

shell@jflteatt:/system/xbin $ find | grep su

./cksum

./lsusb

./md5sum

./sha1sum

./sha256sum

./sha512sum

./su

./sulogin

./sum

./daemonsu

./daemonsu.old

shell@jflteatt:/system/xbin $ su

/system/bin/sh: su: not found

127|shell@jflteatt:/system/xbin $ /system/xbin/su

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

127|shell@jflteatt:/system/xbin $

Hope that sheds a bit more light on things and thanks for you help!
[Verizon Samsung Galaxy S 4] k1mu:
I've already tried it on a clean VZ MK2 phone, and have the same problems. I'm trying now to figure out how to kill Knox as that's what's blocking access to su.
[Verizon Samsung Galaxy S 4] NyekonX:
You just went into App Manager and forced them to stop? I'll try that now.

*edit* Just tried that, it didn't work :( Thanks though!
[Verizon Samsung Galaxy S 4] Drayk:
Yep. Root loaded in about 5 min after I force stopped..... & I'm definitely rooted
[Verizon Samsung Galaxy S 4] rithvik14:
Will it work for at&t galaxy s4?
[Verizon Samsung Galaxy S 4] roote223:
Will it also work on the tmobile gs4 with mk2?
[Verizon Samsung Galaxy S 4] gkersting:
I see why my SE For Android status is Enforcing.

I ran Saferoot version from 12/18 that did not have extra binary installs and commands.

12/18/13: Correct the "text file busy" fix. Force su binary to be setuid root so root checkers will work.

12/18/13: Add more help in the "install.bat" for people having troubles getting adb working

12/18/13: Ensure the folder setup is right when starting install.bat

12/18/13: Give users time to allow su permissions

12/21/13: Disable SEAndroid before rooting

12/22/13: Install selinuxoff to set SELinux to Permissive mode at boot

12/23/13: Fix permission on selinuxoff binary

Should I try re-running script or try to manually add selinuxoff binary ?

Thanks,
[Verizon Samsung Galaxy S 4] WordsworthESP:
That's what I'd thought, until I saw your post informing a member to reroot for passive mode that made me question myself. Thanks. :)

Edit: This could probably be applied to you as well, gkersting. Unless you just really want permissive SELinux. I can't claim to know what the benefits are, if any, one already rooted.

Sent from my Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] swc2001:
Well the first root app that I have had fail is my ad blocker.... it says failed mounting the system read and write fail. K1mu do you know why this might have happened?
[Verizon Samsung Galaxy S 4] gkersting:
Yeah, at least I have root and no major issues, so it's best to leave things as they are. Thanks,
[Verizon Samsung Galaxy S 4] RDomke:
AT&T sgh-i337

I could not help but try "SafeRoot", darn it worked. I had root in about 4min. This has to be one of the easiest roots I have done. Was on 'mk2' still am and everything seems to be working.

The reason I'm writing this, I am 71 years old and if I could do it anyone can.

But just incase something goes wrong, is there a UNROOT method. Just want to cover my bases.

RJDomke@Gmail.com :D
[Verizon Samsung Galaxy S 4] k1mu:
I've had a very busy evening re-flashing MJ7 and updating to MK2 and trying various ways to make this more robust.

Things went well if you had installed SuperSU earlier and left it around, or had disabled Knox when running MJ7, leaving it disabled for MK2.

So, I had to try various fixes over and over, re-ODIN'ing my poor suffering phone until I figured out what needed to be done.

Hopefully the OP is now updated with a version that should work independent of what you've done before.

Merry Christmas. :laugh:
[Verizon Samsung Galaxy S 4] k1mu:
To unroot, run SuperSU and go to "Settings", then scroll down and tap "Full unroot".
[Verizon Samsung Galaxy S 4] k1mu:
That's odd - I mount and remount /system all the time with no problems.

Which ad blocker are you using? I can give it a try to see what's wrong.
[Verizon Samsung Galaxy S 4] k1mu:
Re-download and re-root if you want Permissive mode.

The installer passes an address to selinuxoff that it uses to disable SELinux without needing root; without that, it'll need root to run.
[Verizon Samsung Galaxy S 4] k1mu:
The current installer scripts disables the Knox notification. Note that this does NOT disable the "Knox Warranty Void" detection. If you flash a custom kernel, it'll still set the warranty void flag.
[Verizon Samsung Galaxy S 4] Drayk:
Dang. And I was all revved, up thinking I made a contribution. :D
[Verizon Samsung Galaxy S 4] swc2001:
Here is the ad blocker it was created by Jrummy

https://www.mediafire.com/?xmowaw973onmnue
[Verizon Samsung Galaxy S 4] Drayk:
1st off....many thanks to K1mu for the time spent on this. Mucho Gracias Amigo

2nd-Has anyone been able to get the stock GS4 boot screen back? I've tried everything suggested.

I downloaded and installed this file: de.robv.android.xposed.installer_v25_36cbbc.apk Installed Wanam Eposed>Security hacks>Fake system status....checked the box=status set to official.

It's really not a big deal. I've accomplished what I wanted to....deleting junk & bloat ware. I'm actually more interested in getting free wifi hot spot!! :cool:
[Verizon Samsung Galaxy S 4] mpsrent:
I can confirm that it works on Bell Mobility i337MVLVEMK6.
[Verizon Samsung Galaxy S 4] cduced:
Just wanted to let you know that it worked great on my wife's at&t s4 w/ 4.3 based MK2. It was a little difficult to get the USB drivers sorted out but finally got them to work. I needed to install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 and then adb recognized the phone. Thanks! -- Bud
[Verizon Samsung Galaxy S 4] NyekonX:
Thanks for all the work you put into this! Where's the tip jar? It'd be nice to buy you a few rounds.

I'm tempted to reflash to stock as well and trying Saferoot again to negate all the anomalies. The version you posted first looked promising up until the reboot again hahaha.

--- Samsung i545 VRUEMJ7 Root ---

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

Waiting for device...

Watch your phone. Unlock it and give permission for the install to run.

Sending files to your device...

3484 KB/s (2139595 bytes in 0.599s)

pkg: /data/local/tmp/Superuser.apk

Failure [INSTALL_FAILED_ALREADY_EXISTS]

385 KB/s (17804 bytes in 0.045s)

5864 KB/s (104800 bytes in 0.017s)

303 KB/s (13592 bytes in 0.043s)

4537 KB/s (1109128 bytes in 0.238s)

13 KB/s (629 bytes in 0.045s)

Starting rooting program.

ro.build.product=jflteatt

ro.build.id=JSS15J

search kallsyms...

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

(kallsyms_addresses=c0aac160)

(kallsyms_num_syms=00017428)

kernel dump...

1 2 3 4 5 6 7 8 9

prepare_kernel_cred=c0096e9c

commit_creds=c0096964

ptmx_fops=c11693c8

selinux_enforcing=c1153024

Succeeded in getroot!

Remount success!

Copying files..

Setting SELinux to Permissive

remount: Device or resource busy

Done.. reboot to enable root!

Removing temporary files...

Rebooting...Please wait.

Waiting for device to re-appear...

Unlock your phone, and when prompted, give SuperSU permission for

'ADB shell' to run.

/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

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

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

Installing busybox

/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

--- All Finished ---

I'll reflash and see if there's a difference. Thanks k1mu, happy Christmas to you and your family as well.
[Verizon Samsung Galaxy S 4] k1mu:
It's weird. It seems to be doing the right thing, and getting a success value back:

D/Shell (24035): Running 1 command(s)...

D/Shell (24035): mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system

D/Shell (24035): exit_value: 0

But then complains that it didn't work..

I can't really tell what's happening here without more info. I suspect it's time to contact the author.
[Verizon Samsung Galaxy S 4] k1mu:
OK, this is too strange. It's almost like something is deleting the su binary after the rooting tool creates it.

One off-the-wall idea: could you edit the install.sh and remove the quotes from the su commands:

i.e. edit

adb shell "/system/xbin/su -c sleep 1"

to just

adb shell /system/xbin/su -c sleep 1

Remove those from each of the commands and give it another try. Easier, try the following (no need to re-root):

If nothing is found from the first command, there's no sense in trying the rest. :)
[Verizon Samsung Galaxy S 4] mattamous:
Thanks in advance for this super easy rooting tool!! Worked flawlessly!

Anyone else getting this notification after using the root tool?
[Verizon Samsung Galaxy S 4] swc2001:
Thanks for tryin boss! I will contact him (jrummy)
[Verizon Samsung Galaxy S 4] Surge1223:
Wow I haven't checked this thread for a couple days but I had this problem happen to me twice. I solved it each time using two different methods.

1st method: Flashed back to mj7 with the mj7 Odin tar because I figured the newer kernel & system security on mk2 had something to do with the error. Result ---> Success!

2nd method: modified the script, let it run once and it failed, then after reboot ran it again and let the phone reboot again then I quickly opened up terminal and typed su and got the toast message and prompt to disable knox. I'm trying to find/remember what I changed..but anyways Result ---> Success!
[Verizon Samsung Galaxy S 4] AndroidLonghorn:
Hi K1mu,

Sorry it took me so long to try this. I tried the latest script on a 2nd computer, and I still have no luck. The script does seem to work after the phone reboots and finishes whatever it thinks it is doing. Here is what resulted after running the items you suggested:

ls -l /system/xbin/su

-rwsr-sr-x root root 104800 2013-12-24 16:14 su

ls -l /system/xbin/daemonsu

-rwsr-sr-x root root 104800 2013-12-24 16:14 daemonsu

ls -l /system/etc/install-recovery.sh

-rwxr-xr-x root root 629 2013-12-24 16:14 install-recovery.sh

cat /system/etc/install-recovery.sh

#!/system/bin/sh

# If you're implementing this in a custom kernel/firmware,

# I suggest you use a different script name, and add a service

# to launch it from init.rc

# Launches SuperSU in daemon mode only on Android 4.3+.

# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.

# If you want to force loading the daemon, use "--daemon" instead

/system/xbin/daemonsu --auto-daemon &

# Some apps like to run stuff from this script as well, that will

# obviously break root - in your code, just search this file

# for "install-recovery-2.sh", and if present, write there instead.

/system/etc/install-recovery-2.sh

shell@jflteatt:/ $ exit

exit
[Verizon Samsung Galaxy S 4] k1mu:
OK, it's successfully installed the su binary with root permission and the background daemonsu.

You should be able to open SuperSU now and use it to turn off Knox. If SuperSU didn't get installed, install it from the Play Store.

(The latest change to the install script changed how it installs SuperSU since that wasn't getting recognized on my clean ME2 phone.)
[Verizon Samsung Galaxy S 4] AndroidLonghorn:
Hmmm... It still says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"

Then it just says ok and closes SuperSu. Is there another way to turn off Knox or can I use another SuperUser app? Whenever I try to use titanium or anything else at this point, it still tells me I'm not rooted. Thanks again for all of your help!!
[Verizon Samsung Galaxy S 4] k1mu:
I unrooted my phone and flashed it back to MJ7, then upgraded to MK2, then tried rooting. The problem that I kept running in to is that even though the script pushed Superuser to /system/app, it didn't show up. If you already had SuperSU installed from earlier, it'd be able to give the "su" binary permission. I changed it to sideload Superuser.apk, which has it working more consistently. I think Something in the MK2 security system was blocking SuperSU.

The script now disables Knox reporting and the Verizon security tool early on after the reboot to try to stop them from interfering.
[Verizon Samsung Galaxy S 4] RuggedHunter:
I also have successfully rooted with this method...chose sooner rather than later due to the Samsung update patches I'm hearing about. Everything seemed to go well after getting the drivers right. Root confirmed with Root Checker.

SuperSU never asked me about disabling Knox though?? I'm concerned...

I froze "Knox 3.0" and "Knox Store 1.0" in TiBu Pro, and purchased SuperSU Pro and enabled Survival Mode. I have Samsung Auto update unchecked in settings.

Trying to research how to ensure I don't get a surprise OTA patch now....
[Verizon Samsung Galaxy S 4] k1mu:
Tonight's exercise was to unroot and return to stock MK2. Then I rooted using my Mac.

The interesting thing was that it did pop up the security violation warning, which seemed to suppress the SuperSU permission prompt.

SuperSU timed out waiting for authorization to permit "adb shell" root access, and it remembered that it hadn't gotten permission and denied further attempts. You've got to pay attention and

You can fix that by opening SuperSU and permitting the shell to run, but it's too late for the install to finish up.

I'm going to have to think about a way to work around this problem to make this more reliable. Probably involving the having the user type "su" at the shell prompt until they get permission.
[Verizon Samsung Galaxy S 4] k1mu:
There's no way to turn off Knox without root, but something is blocking you.

What happens if you "adb shell" into the phone and type "su" at the shell prompt?
[Verizon Samsung Galaxy S 4] Surge1223:
I dont ever use ota zips or no wipe tars. Theres no way SuperSu was already in /system I really think it had to do with runing the script twice and manually calling su from terminal (quickly) . Also when knox forces the reboot to "undo modifications" I always intervene by booting to recovery and wiping cache..maybe a combination of all that happening had something to do with it working for me lol
[Verizon Samsung Galaxy S 4] k1mu:
It's probably opening the shell and using "su" that triggers SuperSU to give permission.

If you're watchful, it'll work, but SuperSU times out too quickly.
[Verizon Samsung Galaxy S 4] civicman76:
S3 on 4.3 works.

It also works on the d2vzw s3 with the 4.3 update. Thank:good:s
[Verizon Samsung Galaxy S 4] roote223:
Do you know if it works on the T-Mobile MK2 GS4???? No one has ever responded to my question on this thread.
[Verizon Samsung Galaxy S 4] Swimboy46163:
Yes, I'm pretty sure someone said it has worked.
[Verizon Samsung Galaxy S 4] ojusrane:
How to unroot and get everything back to official status

Can somebody tell me how you unroot the s4 and keep everything in official status in the download mode?? I know that one way to unroot is to "full unroot" via supersu, but I am worried whether I would still have the custom status, can somebody help me please please I really need help
[Verizon Samsung Galaxy S 4] ojusrane:
Will I go back to official status if I "full unroot" via supersu?? Because I don't like these types of methods unless someone makes a video and proves the their device is official and not tripped
[Verizon Samsung Galaxy S 4] Swimboy46163:
Are you looking to unroot to full stock? This is the only way to do that. There's other ways to keep the root and make it not say custom.
[Verizon Samsung Galaxy S 4] k1mu:
That depends on what you want to do.

If you just want to get rid of the "Custom" status but keep root, then install Wanam Exposed and have it reset the status.

My rooted phone is using that and doesn't show the "Custom" padlock on boot Settings/More/About Phone/Status says "Device Status: Official".

If you want to unroot and make sure it doesn't stay "Custom" then you can't just use SuperSU to remove root. You first have to revert any other changes you've made to the phone. For example:

Anything frozen with Titanium needs to be thawed

Safestrap must be removed

If installed, xposed framework needs to be disabled then uninstalled

If you've used a "debloat" package, you've got to restore anything it deleted

Anything else you've deleted or modified needs to be put back

There's probably other things I've forgotten. After that's all been repaired, you can use SuperSU to remove root.

If you miss something, then you'll still show custom, which means that you'll need to figure out what you misssed, re-root, then try again.

That's why [MENTION=5519692]Swimboy46163[/MENTION] pointed you to the guaranteed fix, which is a full-wipe restore.

You could try un-rooting then use the no-wipe image. If that still shows "Custom", then use the full wipe emergency recovery.
[Verizon Samsung Galaxy S 4] greatdaneduke:
Do not sweat the custom... or flash counter. I turned my phone in with PA and no one said a thing. Once it is repaired it is going to be returned to stock anyways. Rooting has no bearing on any hardware.
[Verizon Samsung Galaxy S 4] ojusrane:
Thanks for your help, I was worried only worried about [MENTION=5519692]Swimboy46163[/MENTION] method because I don't want to flash any firmwares via a computer and then find out that my phone is knox tripped, otherwise im doomed and I'll have lost my warranty forever
[Verizon Samsung Galaxy S 4] RDomke:
UNROOT

Thank you for the super su info. I had read about it before but was not sure it was the correct way to go.

Thanks again.have a safe and happy holiday season.

RDomke@Comcast.net
[Verizon Samsung Galaxy S 4] k1mu:
I don't know, but it's worth trying as it's harmless if the attempt fails.
[Verizon Samsung Galaxy S 4] Swimboy46163:
My method I mentioned won't trip Knox at all.
[Verizon Samsung Galaxy S 4] dovedescent7:
Thanks

Worked well for my i337 at&t model

one very important part i should have read is about when your phone asks you to allow debugging...

a window actually appears

so don't think just because you have debugging turned on your done,because your not...

when you plug in after enable debug, a message asks 'allow debugging?"

select yes and it will root.

thanks to who built this....
[Verizon Samsung Galaxy S 4] WordsworthESP:
That should (hopefully) be the least of anyone's worries. If they can't figure that out, they probably shouldn't be rooting their device. ;)

Sent from my Hyperdriven Samsung S4
[Verizon Samsung Galaxy S 4] Mistertac:
[MENTION=3940199]k1mu[/MENTION]

Thanks for saferoot, used it a couple times now after running into problems installing hd12 on my stock slot.

You're work really helped me out!

Verizon Galaxy S4

Safestrap 3.7

HYPERDRIVE 11
[Verizon Samsung Galaxy S 4] Drayk:
Ok....I've done this as well, and still have the custom/padlock on boot screen......BUT the secure boot status says Type: Samsung.....weird

This isn't huge, tho. It's more an of OCD thing. I'm more concerned with getting a backup method.....Nandroid / TWRP, something.

Does anyone know of anything?