yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] k1mu:
"Don't be custom" means that you made your phone non-standard by rooting it. The OP states that this will set the "Custom" flag.

To remove that, flash a factory stock ROM. you won't be rooted, but won't be custom any longer.

If ALL you did was to root it, you can unroot as I said just a few posts above and it won't show custom any longer.

Sorry, I'm tired of answering this same question over and over again. Please go back and read this thread.
[Verizon Samsung Galaxy S 4] ojusrane:
Can someone tell me if this is a reliable source for stock rom, because I don't want a bricked phone or tripped knox. I'm only considering this one because sammobile download links have really slow download speed.

http://www.androkick.com/joomla/ind...-i9505-lte-samsung-galaxy-s-4-iv-gt-i9505-lte

I want to download i9505xxuemj7
[Verizon Samsung Galaxy S 4] greatdaneduke:
Awesome. Worked on my SCH-I535
[Verizon Samsung Galaxy S 4] sjmiller:
Not quite true. Your script - thank you for making it available - also installs busybox. Using SuperSU to unroot will not remove it. I know you mentioned to also remove any other changes, but a casual rooter might not be aware of this. In the past, I have actually removed busybox, but kept root, and custom goes away. I haven't done this yet with my S4, because at the moment it doesn't bother me.

Scott
[Verizon Samsung Galaxy S 4] my59:
Excellent work, thanks.
[Verizon Samsung Galaxy S 4] BladeKnight:
hello sir k1mu, does this work on MKE? good morning...
[Verizon Samsung Galaxy S 4] k1mu:
MKE? You must be on a non-Verizon phone, yes?

You're better off asking in a forum for your phone. MKE may be updated to fix the kernel flaw that this rooting tool uses.

In any case, being able to install recoveries depends on if your bootloader is locked or not. On the Verizon I545, the bootloader is locked and won't allow custom recoveries. That's why we use Safestrap.
[Verizon Samsung Galaxy S 4] k1mu:
I've updated the OP to include OSX and Linux adb binaries, and to add a bit more guidance to the installer script.

I've also removed the 'selinuxoff' program - it turns off the "SELinux Enforcing" flag, but the kernel for the I545 was built to ignore that flag, so being in "Permissive" mode is meaningless; the SELinux enforcement is still in place.

Remove /system/etc/install-recovery-2.sh and /system/xbin/selinuxoff to remove this if you've already rooted and have it installed.
[Verizon Samsung Galaxy S 4] BladeKnight:
yes, i'm on a international version sir k1mu. thank you so much for the fast response...:good:
[Verizon Samsung Galaxy S 4] tshelby73:
I have a selinux.old do I need to do anything with it also.
[Verizon Samsung Galaxy S 4] k1mu:
Yes, also remove that. (That's left around from a re-root.)

Leaving it won't trip the custom flag, however.
[Verizon Samsung Galaxy S 4] tshelby73:
I also seen a install-recovery.sh.old in etc folder is this also left overs. Is .old the same as .Bak meaning the OS doesn't see it?

---------- Post added at 03:47 AM ---------- Previous post was at 03:41 AM ----------

So even though in about phone se status said permissive it really wasn't?
[Verizon Samsung Galaxy S 4] k1mu:
Yup. I spent a couple of days fighting this, trying to create a symbolic link in /sdcard pointing to my external SDcard.

The phone wouldn't allow it, Reading the kernel source and checking the running code in the official kernel, I verified that it was built with CONFIG_ALWAYS_ENFORCING set, which means that most of the SELinux checks ignore the "enforcing" flag and assume that it was enabled.

Since I can't overwrite the kernel code (it's read-only in memory), I can't override that, so setting the flag to "Permissive" is meaningless.

That's frustrating, but there's nothing I can do.
[Verizon Samsung Galaxy S 4] lath19:
Great tool. By far the easiest root method I've ever gone though. Thanks!

S4 MK2.
[Verizon Samsung Galaxy S 4] tshelby73:
I will say this is the easiest way to root a locked bootloader phone but the easiest way ever for me was cwm flash supersu.zip. lol
[Verizon Samsung Galaxy S 4] Fe4r_[KiNg]*:
Hi, please can someone tell me, how can I unroot my phone withour tripping KNOX after I root it with this metod.?

EDIT: will this root metod work on I9505XXUEMKF

Thanks!
[Verizon Samsung Galaxy S 4] Mistertac:
You can use SuperSu to unroot. And I believe he addressed removing busybox as well manually in another post.

Verizon Galaxy S4

SafeStrap 3.71

Hyperdrive 12
[Verizon Samsung Galaxy S 4] topcat888:
Worked with MK8, perfect..!
[Verizon Samsung Galaxy S 4] ma678:
May I assume this method also works for I337m variants?

Thanks.
[Verizon Samsung Galaxy S 4] WordsworthESP:
Welcome. I'd recommend reading the XDA rules, then read and search the thread. 95% of your questions have already been asked and answered. If yours hasn't, then ask.

Sent from my Hyperdriven Samsung S4
[Verizon Samsung Galaxy S 4] k1mu:
As I've said several times, it's worth trying. If it doesn't gain root, the only lasting side effect is that SuperSU is installed, but you can always uninstall it. Nothing is done that will harm your phone.
[Verizon Samsung Galaxy S 4] echodeluxe:
i was told this works with the verizon s3. is that not true?

i have been getting the error of not seeing the device and the error of not finding the su file. halp.
[Verizon Samsung Galaxy S 4] nickknaack:
Been rooted for a couple weeks now, but Samsung wants to push through an OTA update. Fine. I attempted to do and go an error. I'm guessing because of the root? Do I need to un-root to install the OTA and then re-root or is there another way?
[Verizon Samsung Galaxy S 4] echodeluxe:
finally worked! it took like, ten tries haha

anyway, now that im rooted (verizon galaxy s3, 4.3) if i try to flash CM 10.2 or whatever, is it gonna brick my phone since its technically downgrading?
[Verizon Samsung Galaxy S 4] Swimboy46163:
You need an unlocked bootloader... Which isn't possible right now.
[Verizon Samsung Galaxy S 4] echodeluxe:
god dammit verizon/samsung.
[Verizon Samsung Galaxy S 4] Swimboy46163:
You can use safestrap for flashing touchwiz ROMs like hyperdrive
[Verizon Samsung Galaxy S 4] rod_ol_fo:
works for my vzw note II. only had to run script twice and it worked! rooted on 4.3 OTA. cant wait for unlocked bootloader!!!

Thanks Dev
[Verizon Samsung Galaxy S 4] zeroth:
I just rooted my girlfriend's galaxy s4 and it worked perfectly, thank you so much, I have only one question,.

Is there anyway to disable future ota updates?

Thanks.
[Verizon Samsung Galaxy S 4] sharkie405:
Remove or disable SDM.apk from /system/app.
[Verizon Samsung Galaxy S 4] ma678:
I rooted my i337m after the first attempt.

Thanks a lot.
[Verizon Samsung Galaxy S 4] anomolli:
What if toggling between "media device" and "camera" doesn't work and your device is still not detected by install.bat? Is there anything else I can try? I've verified that drivers are installed (I have Kies 3 installed and it recognizes my device), I've run it as administrator, and I have extracted it to c:\saferoot on Win7. Not sure what else to try.
[Verizon Samsung Galaxy S 4] Swimboy46163:
I rebooted and toggled the developers settings off and on. And it worked.
[Verizon Samsung Galaxy S 4] anomolli:
I was really hoping it would be something simple like this. Unfortunately, rebooting and turning on/off develop options and toggling from "media device" to "camera" and vice versa still leaves me stuck on the "[*] Waiting for your phone to appear" message. :(
[Verizon Samsung Galaxy S 4] Swimboy46163:
Are you using the cord that came with the device or some other cord? I also used the cord that came with the device.
[Verizon Samsung Galaxy S 4] anomolli:
Yep, I'm using the Samsung cable that came with the phone. I've read people saying that I should use the usb ports in the back of the computer, however I have three laptops, none of which have usb ports in the back (all ultrabooks). I can't really see why this would be a problem, but I don't know enough to dispute it. I have tried to more than one laptop with the same results. I've also tried on both usb 2 and usb 3 ports. I got nothing...
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Usb in the back? Not all PCs are build the same. There is no such beast as a difference in back or front usb. What they mean is make sure you're using usb2.0 or higher ports. Does the phone, aside from rooting, show up in "my computer" as a media device or camera (depending on what setting you currently are at)?

If yes, the next step is to make sure usb debugging is turned on.

If yes, restart the script and look very carefully at your phone's screen it should be asking for permission to debug

Edit

Also make sure you ran command prompt as admin

(On vista or newer type cmd into start menu, right click choose run as admin)
[Verizon Samsung Galaxy S 4] anomolli:
Hey thanks a ton. While trying to toggle Developer options, I failed to notice that the USB debugging check mark is unset when I toggle Developer options. Finally have it working now. The cmd prompt is at "[*] Waiting for device to reappear" after the reboot. I'm going to do some more reading to see why it's stuck there, but thanks so much for reminding me to check the details! :good:
[Verizon Samsung Galaxy S 4] CheriePie:
Hi k1mu,

So I had rooted with your safeboot method before you had put in the SELinux permissive stuff. Instead of rerooting to add that stuff, I enabled the "Disable SEAndroid (Beta)" option in Wanam, which according to the description sets SELinux to Permissive mode on Boot since I assumed this was the same as the extra stuff you had added. It did ask me to grant root access to the Android OS process on reboot, which I did, but I'm guessing that like your own script, this setting isn't really doing anything on this MK2 build either since the SE for Android Status under my About Phone Settings still shows Enforcing.

Basically I'm just wondering if this option in Wanam was the same as what you were doing, so all your comments above apply to this setting as well. Correct?
[Verizon Samsung Galaxy S 4] electricpete1:
I'm trying to root my AT&T S4 stock 4.3 using this saferoot install.bat. (AT&T forum provides a link to this Verizon thread).

I have the same experience as anomolli., Specifically:

Verified phone is seen by Kies. Shut down Kies

Enable USB debugging

Unzip saferoot.bat which creates a saferoot folder in a data directory of my pc.

Go into that directory and run install.bat

Stuck at “Waiting for your phone to appear”

Toggled back and forth between camera mode and data mode.

After I toggle each time in about 5 seconds a popup appears (similar to when I plug in usb drive) giving me options to import pictures or browse in windows explorer etc. I dismiss the window. Still “waiting….” I wait for at least 15 seconds and toggle again. Over and over same result.

Ran as administrator… same result.

Unplugged and replugged phone multiple times… same result.

Tried all 3 USB ports on my Windows 7 laptop... same result.

Verified USB debugging remains enabled throughout.

Any suggestions?

One question I have,.. does it matter what directory on my pc the saferoot.zip is installed into? (I see reference in the bat file to system32…I’m not installed in that directory).
[Verizon Samsung Galaxy S 4] anomolli:
Can't tell you if it matters, but I extracted saferoot.zip into c:\, so the extracted directory structure is c:\saferoot\, which worked for me. There's nothing to install, just run the .bat file. The system32 directory you're referring to is where the cmd utility is located, not where saferoot is.
[Verizon Samsung Galaxy S 4] electricpete1:
Thanks. I tried unzipping into C: (which created c:\saferoot) and still didn't work.

Also I'm using the original cable.

Next step, I'm going to try the other drivers. I'll report results, thx.
[Verizon Samsung Galaxy S 4] k1mu:
What I *think* Wanam is doing is the standard approach of writing a "0" to /sys/fs/selinux/enforce which will normally set permissive mode.

That's blocked by the CONFIG_ALWAYS_ENFORCING kernel build configuration, so what I did was to write a program that ignored that and wrote directly to the selinux_enforcing variable in kernel memory. This gets you a display that says that SELinux is in "Permissive" mode, but too much of the SELinux code ignores that flag due to the CONFIG_ALWAYS_ENFORCING.

Unless there's a way to patch the kernel code, there's no way to make this actually permissive.
[Verizon Samsung Galaxy S 4] k1mu:
It doesn't matter what directory you install Saferoot into.

One thing: You've got to give debugging permission ON THE PHONE when you first connect. If you don't give that, it's ALWAYS going to show as offline. This is mentioned in the script comments, but just to be clear:

Unlock your phone. Ensure that USB debugging is on. Don't plug in the cable.

Go to Settings, More, Developer Options. There should be a "Revoke USB debugging authorization" entry. Tap that, and "OK" when it warns you about USB debugging access being revoked.

Plug in the phone. You should see an "Allow USB debugging?" prompt.

Make sure that "Always allow from this computer" is checked, then tap OK.

Unplug and re-plug the phone. You shouldn't see anything else pop up.

If you don't get a "Allow USB debugging?" prompt, there's something funny going on.

If you do, and it's now given permission, try starting the install.bat again.

If all this doesn't work, then you'll need to start playing with the supplied adb.exe from a command prompt.

adb get-state

should reply with "device".

adb devices

should reply with "List of devices attached" including an address and a status entry, like:
[Verizon Samsung Galaxy S 4] gothicasshole:
What that refers to is desktops.. you see the usb ports on the front are connected via a cord to the motherboard.. it's basically the same as a usb hub. On the back are the usb ports directly on the motherboard therefore they don't go through lag or other limitations. With a laptop/ultrabook all usb ports are connected to the mother board therefore that doesn't apply to you
[Verizon Samsung Galaxy S 4] gothicasshole:
Woot worked flawlessly!!!!!! At&t gs4 mk2 :) its not all that hard at all folks :) i installed kies updated the drivers extracted the files ran the install boom i do need to mention that i did do the revolk usb debugging autherozation once i did that it was waiting on device but then i ran it a second time the dialog box popped up on my phone i clicked accept and bingo!! Ran it for a third time pressed the space bar clicked accept on my phone again it ran the process adb pushed the su.apk i updated it then pressed the space bar again and i now have root access :) so woot!!!!!!!! Now only if we can get a cwm build and a cyanogen this baby will be smokin :) so please please please download kies update your drivers revolk your usb debugging extract the .zip fallow the instructions which are super easy!!! Update the su and bam you got root
[Verizon Samsung Galaxy S 4] k1mu:
I'd like to understand what's going on that's causing the su binary install to fail.

If you've had this problem, could you please try the attached batch file for installing? Put it in the same directory as the normal install.bat, rename it to 'install-test.bat' and double click to run it. It'll display the installed su program prior to rebooting and afterwards.

If, as I suspect, something is deleting the /system/xbin/su program, it'll be obvious.

The script also lists all of the installed packages so we may be able to spot the source of the problem and remove it. This will be written to "packages.log" in the directory where the batch file is stored.

If you're one of the people seeing this "not found" error, please give this a try so I can try to find out what's happening.
[Verizon Samsung Galaxy S 4] gothicasshole:
Here's my proof ;)
[Verizon Samsung Galaxy S 4] gothicasshole:
I hate to say it I think most people are forgetting the fact that 4.2.3 and up (including 4 3)has an adb encryption key you must go to your settings> more> developer options> revolt usb debugging keys

Install Kies go to tools reinstall drivers once done go to the install.zip find it extract it and let it run
[Verizon Samsung Galaxy S 4] electricpete1:
After reinstalling drivers and trying several times focusing on instructions above, it worked!!!

Yeeeee haa!!!

Thanks very much k1mu for bringing this root method to S4's with 4.3 and for helping me figure out how to get it done.

I am truly grateful.

THANKS!!!
[Verizon Samsung Galaxy S 4] born4trance:
This is amazing :good::cool::good:If only i found this before tripping KNOX :p

edit: Will this work for Android 4.4 (KitKat) as well or did they patch it?
[Verizon Samsung Galaxy S 4] gothicasshole:
Hmm you can use exposed to reset it rite?
[Verizon Samsung Galaxy S 4] diablofreak:
if i am already on me7 safestrap - can I go back to stock rom and update via OTA to MK2 and run this to re-root?
[Verizon Samsung Galaxy S 4] whatsisnametake2:
nandroid

hi folks,

i see it states that you can't use a custom recovery with this root method. does that mean there is no way to do a nandroid backup?

thanks!
[Verizon Samsung Galaxy S 4] thornev:
I believe you can simply Odin to mk2. That's what I did.

Galaxy S4 - Safestrap 3.7 - Hyperdrive 12

---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------

No. You can use safestrap 's recovery to do a nandroid.

Galaxy S4 - Safestrap 3.7 - Hyperdrive 12
[Verizon Samsung Galaxy S 4] k1mu:
This has already been patched for some 4.3 phones, so I think it's unlikely to work on 4.4.

You MAY be able to retain root across an OTA using SuperSU Pro "Survival Mode", but only time will tell.
[Verizon Samsung Galaxy S 4] machobug:
Quick Question

I did this and it worked, super easy! So thanks.

Now I'm wondering if it's okay to flash CWM via Odin Flash? Or is that not possible?

Thanks again.

Edit: I don't know if it matters, I'm on the T-Mobile version
[Verizon Samsung Galaxy S 4] gothicasshole:
Most likely no because you won't have a custom recovery
[Verizon Samsung Galaxy S 4] omnifarious:
You can use safe strap recovery or you can use onandroid to make a backup from within Android.

Btw, this method to root works on T-mobile MK2. However, even after unrooting and re-flashing MK2 via odin, it still said Device Status Custom under about device. What files are added, if any, to the /system folder or otherwise? I could not find install-recovery-2.sh nor the aformentioned file in xbin.
[Verizon Samsung Galaxy S 4] datstudandre:
Has anyone confirmed this works on the vzw gn2 running 4.3?
[Verizon Samsung Galaxy S 4] k1mu:
The other change is the busybox install. I've posted a script to uninstall that earlier in this thread:

su

mount -o remount,rw /system

find /system/xbin -type l | xargs rm

rm /system/xbin/busybox

mount -o remount,ro /system
[Verizon Samsung Galaxy S 4] omnifarious:
Thank you, and sorry, I had over-looked the 2nd and 3rd posts. I also went as far as formatting system and deleting folders in safestrap recovery before reflashing stock tmo mk2. Now I'm back to offical status and can send my phone in no worries.

OT, have you encountered the "instant shutdown" bug? When I press the power button, the phone shuts down with animation. There are no options to power off or to toggle airplane mode.
[Verizon Samsung Galaxy S 4] decaturbob:
That question been answered in hd thread.. not a Saferoot issue

safestrap enabled, Hyperdrive driven
[Verizon Samsung Galaxy S 4] k1mu:
The issue here is that apparently something, probably Knox, is deleting the su program as soon as it's installed.

If you issue the following adb command from your phone, it should disable Knox and allow you to root. (You'll need to run the rooting process again).

adb shell /system/xbin/daemonsu -c pm disable com.sec.knox.seandroid

If you try this and it works, please let me know.
[Verizon Samsung Galaxy S 4] rod_ol_fo:
You can do nandroid back ups but no way to restore it... Unfortunately you'll need a custom recovery to restore the nandroid. Haha although if I'm wrong I'd definitely would like to know how to restore a nandroid.

Theres a thread in XDA and app in playstore (same app) onandroid

http://xdaforums.com/showthread.php?t=1620255
[Verizon Samsung Galaxy S 4] rdeluis:
Yes it does. Run it twice. First time will give you an error.
[Verizon Samsung Galaxy S 4] optimummind:
Does anyone know if this will work on a US Note 10.1 2014 WiFi edition tablet?
[Verizon Samsung Galaxy S 4] omnifarious:
I'm not using HyperDrive so I don't have tweaks, I'm using stock tmo mk2. And I know it's not saferoot, that's why I said OT (off topic)
[Verizon Samsung Galaxy S 4] jcwilliams:
Just used this on mk2 update. Worked great.
[Verizon Samsung Galaxy S 4] 3V0_MR:
S3 and custom ROMs

I used this method for my S3 and it worked great! Next question..... I want to install a custom ROM and the post mentioned Safestrap, but when searching for Safestrap for S3, I couldn't find anything. Are there other methods, or am I just not finding the results I should? Any help is greatly appreciated. :)
[Verizon Samsung Galaxy S 4] hondabomdc5:
Mtp failure

Hello everyone. I have been pointed to this thread to try and find a issue to my MTP Failure.

Let me explain.

I am currently on ME7 and on the Hyperdrive 10.2 version of that ROM. I want to update to MJ7 so that I can update to the latest HD12. However, there are alot of steps needed like flashing the MJ7 image and doing saferoot and several other things that im sure all of you are aware of. Well, i cant even begin to do any of that because my computer will not see my phone.

I have tried multiple things to try and resolve this issue. Here is my long list of things I have tried.

-I have tried it on 2 personal laptops

-Tried it on my work laptop

- Using the stock cable that came with the phone

-Downloaded drivers straight from Samsung's website

-I have downloaded USBdeview program and uninstalled all samsung drivers and restarted each computer and plugged phone in to install all drivers and everything installs fine except for the MTP

-I have tried with USB Debugging on and off

-I have followed a Youtube video that has you go into the registry files and change a few settings

-I have researched and researched and asked questions in multiple threads on XDA and Google

- I did a FDR on my phone and reinstalled the HD10.2 ROM that I am currently on and wiped data and cache also

-Went into the application manager in settings and found the MTP app and media storage app and cleared the data and cache in those

-Put phone into "safe Mode" and tried installing drivers---still the MTP failed

-Called the Samsung tech support and had them try and help me and i pretty much already did everything that they told me to do and they could not figure it out so they told me to send my phone in and they would do a reflash on my phone...basically make it stock again but im afraid if I do that itll brick my phone since i have a custom ROM on it.

I have been at this for a week and a half. Im tired, defeated, frustrated and just dont now what else to do. It is driving me crazy and i am trying to be as patient as possible. I posted in another thread and someone told me to ask in here so that is why I am asking. I am hoping that somebody in here has some advice/help or a answer for me. Thank you so much for your support. I am looking forward to hearing what yall have to say.
[Verizon Samsung Galaxy S 4] thornev:
Your answers are in the S3 forums. The S3 bootloader was unlocked so you don't need safestrap.

Galaxy S4 - Safestrap 3.7 - Hyperdrive 12
[Verizon Samsung Galaxy S 4] LordAlexx:
I would reflash through Odin with a stock rom and see if that will clear up your port issues

. It shouldn't brick the phone unless you try to downgrade from 4.3