yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jkeuclid:
Saferoot technically doesn't work directly with KK, however by downgrading from 4.4.2 to 4.3, or from a rooted 4.3 to KK you can end up with a fully rooted KK phone such as the S4 Active with root here, really not that difficult thanks to [MENTION=4287865]Sunderwear[/MENTION] and his rooting prowess.
[Verizon Samsung Galaxy S 4] gothicasshole:
This is for mk2 on 4.3 you need a 4.2.2 root program

---------- Post added at 12:50 AM ---------- Previous post was at 12:45 AM ----------

Just out of curiosity did the verizon dev community fund a solution to the kit kat root??
[Verizon Samsung Galaxy S 4] htcp85:
This is from the OP

(If you have used the current version of Saferoot to root your phone, then there's an unroot script installed to make this easy.

If you still have Saferoot unzipped, plug in your phone and use "unroot.bat" (Windows) or "unroot.sh" (Unix) to remove the changes that Saferoot made. Then, open SuperSU and instruct it to perform a "full unroot". After that, all changes that Saferoot have made to your device have been removed.)

I used the unroot script that comes in the unzipped, This means busybox is removed too?
[Verizon Samsung Galaxy S 4] BROKEN1981:
I dont want to look stupid but I'm on the s3, Verizon. When I go to about phone it list android version 4.3. So why would I be told I'm on 4.4? At the end of build number it is nc1. Is that the reason?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
You aren't on 4.4. The hazard of posting in a non-your-device specific thread (this is the vzw s4 board) is they don't know your build numbers from squat. You have this build correct?

It may just be that the build isn't compatible; not all 4.3 (or any Android) are the same, even for similar or even same-device-different-carrier builds can differ. If your build is listed on the front page of this thread, then you accepted a security update (spit-balling here I don't have your phone type) which means you need to factory wipe, turn off automatic updates of security definitions (on the S4 that's settings>more>security but idk if that is the same on yourn) then run root
[Verizon Samsung Galaxy S 4] msasm09:
Could it work on SGN3 SM-N9005 runing 4.3 MK3 TMS
[Verizon Samsung Galaxy S 4] BROKEN1981:
Yes that my build. Thank you for clearing that up. I had used safe root since it worked for the s3. As my girlfriends s4 got the new update so did my s3. I knew I would lose root but figured I would just use the zip file again. Thats why I had posted what's the deal when I seen my phone was still on the same version that safe root worked with.
[Verizon Samsung Galaxy S 4] febrilabs:
Is this work on i9500 black edition?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
If it isn't listed on post 1 or 2 we don't know. It doesn't hurt to try. The script will almost IMMEDIATELY tell you if it'll work or not
[Verizon Samsung Galaxy S 4] AlexRuhl:
i9300 black edition do not root

I have 4.3 i9500xxuenaa build and I don t upgrade to 4.4.2 for rooting the device and don t flag knox. But I try with vroot and nothing change, with kingo the program tell me that install custom recovery and I lost warranty and with saferoot I obtain this message.

Do you want to install Busybox on your device [Y/N]? y[*] 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...

[*] Starting rooting program.

ro.build.product=d2vzw

ro.build.id=JSS15J

Your kernel is patched!

This device is not supported.

[*] Checking if rooting succeeded

[*] Unfortunately, rooting failed. Cleaning up.

Press any key to continue . . .

What can I do? Is it possible root naa without flag knox?
[Verizon Samsung Galaxy S 4] dkephart:
Saferoot told you all we know. You are on a build on which the exploit it uses is patched. You may have to downgrade or something, look in the forum for your device.
[Verizon Samsung Galaxy S 4] alemosman:
sprint s3 with kitkat

Thanks for this wonderful root method, I would like to know if this method of rooting is going to work on the Sprint Galaxy S3 which just updated to kitkat 4.4.2, Build L710VPUDND8??
[Verizon Samsung Galaxy S 4] AlexRuhl:
If I downgrade I flag knox..I want to preserve warranty
[Verizon Samsung Galaxy S 4] k1mu:
Whatever you did updated the kernel on your phone, so it's not rootable.

Edit: You apparently were able to downgrade to an older ODIN flash that was rootable, so no problem.

It's very likely that your phone took an OTA, which is what un-rooted it in the first place.
[Verizon Samsung Galaxy S 4] k1mu:
It only works on phones that have an unpatched Linux kernel. 4.4 is definitely shipping with patched Linux, so it won't work there, but taking any OTA that's later than MK2 or so WILL come with a kernel that won't be rootable.

We have said over and over to NOT take OTAs. Don't take OTAs as you'll lose root. Wait until the developers figure out how to regain root or retain it across the update. Unfortunately, you now know why. If you can downgrade to an earlier release using ODIN (which will probably work if the update is still Android 4.3) then you can regain root.

There are paths that allow you to get to 4.4 while still retaining root. You do need to be careful what you do if you're going to take that path. (And describing how to do it is off topic here.)
[Verizon Samsung Galaxy S 4] k1mu:
Yes.
[Verizon Samsung Galaxy S 4] k1mu:
Nope. This has already been answered dozens of times - Saferoot won't work on 4.4.x.
[Verizon Samsung Galaxy S 4] k1mu:
Well, then you're stuck. The Knox Warranty Void flag will get set if you try to use CF-Root as well.

I don't know of any way to root once the kernel is patched (If I did, I'd be collecting the non-trivial bounty.)
[Verizon Samsung Galaxy S 4] jkeuclid:
Indeed, precisely the point I was trying to make in my post #1690, though I should've been more clear, my apologies. Nonetheless, I'd like to thank you [MENTION=3940199]k1mu[/MENTION] for the latest update and for your efforts in making these roots possible.
[Verizon Samsung Galaxy S 4] AlexRuhl:
If can help I do an OTA two weeks ago but I don t remember what build I had before.
[Verizon Samsung Galaxy S 4] 012512:
unfortunately, It failed to root my phone. :(

Saferoot fails with the messages

"Your kernel is patched!

This device is not supported."
[Verizon Samsung Galaxy S 4] doncaruana:
I was rooted with 4.1.2 and haven't rerooted since taking 4.3 which I had to do for work. I know the bootloader is locked forever. I'm okay with touchwiz. But, after taking NC1 (this is a verizon GS3), I tried saferoot for the first time on 4.3 and I got hung up at "sending files to device". I looked under the covers a bit and tried to just execute the commands manually. I can shell to the phone and do stuff, but if I try the install, it just hangs. And when I looked in /data (the bat file pushes stuff to /data/local/tmp) I see nothing. I tried simply pushing the files somewhere else and that was fine, but when I tried to change the permissions, I got "Operation not permitted".

Needless to say, I'm not rooted. But it seems others get farther than this before failing, even on NC1. So my big question is whether there is something funky with my setup or with adb which is preventing these commands from working properly. My phone initially connects as an installer but then flips to a media device shortly thereafter, even though I have usb debugging enabled, etc, since I can obviously run adb and all.

Any help/insight would be greatly appreciated.
[Verizon Samsung Galaxy S 4] twiz0r:
I just wanted to say THANK YOU. I received my replacement device today (old one had black screen of death - I was unable to repair) - took me 2 tries (1st time froze on waiting for device...), restarted the install and worked flawlessly.
[Verizon Samsung Galaxy S 4] gothicasshole:
You have to go back to mk2 otherwise there is no hope
[Verizon Samsung Galaxy S 4] htcp85:
Just rooted my Tmobile S4 today, last week when I rooted didn't disable knox with SuperSU and decided to unroot , and this time SuperSU didn't asked me to disable and last week did, but the program at the end says knox disabled. So I think is good. Also I don't have the custom padlock I don't know why.
[Verizon Samsung Galaxy S 4] picklefish:
My phone is asking every day to do the OTA update (i keep telling it to wait) will it force update ever?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Freeze the update program using titanium backup or other such software. If you have an S4 it's called SDM and/or Updater
[Verizon Samsung Galaxy S 4] picklefish:
brilliant thanks
[Verizon Samsung Galaxy S 4] tumbleweed65:
Any way to revert back to before the update so I can reroot?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Usually not, but you have to give more info.

What device

What was old build

What is the build you upgraded to
[Verizon Samsung Galaxy S 4] tumbleweed65:
My bad too many threads open but I found my answer, thanks

---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------

I'm on the Verizon s3 with the 4.3 update I have to Odin back to m1

http://xdaforums.com/showthread.php?t=2586319
[Verizon Samsung Galaxy S 4] bozob:
Can't root AT&T Galaxy S3

I've tried your program with a new S3 I received as an insurance replacement. This said that it failed the rooting, but others here have had success. I've even tried CF-auto-root to no success (and lost my new 12-month warranty--I wish I'd come across this solution earlier). I'm hoping you can help me out.

I'm running:

SAMSUNG-SGH-I747

V.4.3

Baseband version I747UCUEMJB

Kernel: 3.0.31-2024954

Oct 31 2013

Build JSS15J

SE Enforcing SEPF_SAMSUNG-SGH-I747_4.3_0010

I've tried loading TWRP 2.7.0.0 recovery, but it only shows that it is unable to mount anything. CF-auto-root will reboot without rooting or loading a stock recovery back in. (CF-auto-root remains as the recovery reboot unless something else is loaded in.)

I can adb shell in, but I really don't know what to do after that.

Any ideas on what's happening?
[Verizon Samsung Galaxy S 4] k1mu:
What did the install tell you when you tried to root? Without that, it's kind of hard to tell you what may have gone wrong.
[Verizon Samsung Galaxy S 4] k1mu:
If it's hanging with "sending files to device" do you see anything on the phone to indicate that Knox has gotten in the way?

Some users have had problems because adb is seeing emulators or other devices on their PC. Start with phone unplugged and use "adb devices". Does anything appear in the "List of devices attached"?
[Verizon Samsung Galaxy S 4] bozob:
I manually stepped through the steps in the batch file. None of them gave any errors, but the files su and superuser did not exist in the directories after the getroot command.

There is one thing very weird that keeps happening. When I am in adb shell it keeps exiting me out after a few seconds. I don't think it's able to finish the getroot command. Here is what I'm getting when I run it:

shell@d2att:/data/local/tmp $ ./getroot -b

./getroot -b

ro.build.product=d2att

ro.build.id=JSS15J

search kallsyms...

1

(kallsyms_addresses=c08265e0)

(kallsyms_num_syms=00011d11)

kernel dump...

1 2

C:\Downloads\saferoot\files>

After the "2" is when it dropped out. If I run it with the complete command line "adb shell /data/local/tmp/getroot -b" it will count to about 4 or 5 before exiting the shell. Many times when it exits I have to execute "adb devices" again before I can run "adb shell" otherwise it will state "error: device offline".

It's as if there's something running on the phone designed to kill an adb process every so often.
[Verizon Samsung Galaxy S 4] bozob:
I've attached dumps from 'ps' and 'top' commands so you can see what the phone may be running.
[Verizon Samsung Galaxy S 4] acraigl:
Me too... but this is new after the OTA update I just took today. I had hoped it was kitkat, but is just another variant of 4.3. This saferoot that worked yesterday, does not appear to be doing so with this latest update. I'll continue to follow this thread in hopes of a solution becoming available.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
A solution using Saferoot method will NOT become available, the update you took was the Mobile manufacturer closing the flaw that allows rooting with this method. You can try to downgrade to the 4.3 that works (using your carrier/device full wipe odin) but there's no guarantee that you will be able to do that
[Verizon Samsung Galaxy S 4] acraigl:
Well then. Bad news for me. Thanks.
[Verizon Samsung Galaxy S 4] doncaruana:
ADB was working, but spotty for some reason (like from command to command!). Anyway, after walking through all the steps manually, this is what I ended up with:

shell@d2vzw:/data/local/tmp $ ./getroot -b
./getroot -b
ro.build.product=d2vzw
ro.build.id=JSS15J
Your kernel is patched!
This device is not supported.
1|shell@d2vzw:/data/local/tmp $

So, the moral of the story is, yes, there was something wrong with my setup.

Moreover, this shows for anyone still wondering that NC1 patched the kernel so this won't work any more.
[Verizon Samsung Galaxy S 4] k1mu:
The Verizon S4 has some dumb feature that when you plug it in, ADB connects, then about 30 seconds or so it disconnects, then reconnects. If your phone is doing something like that, plugging it in then waiting a few minutes before trying to root may work.

If there's something dropping ADB connections periodically, complain to the vendor, LOUDLY. That means that adb backup can't work.

A phone that does that is simply nonfunctional and needs to be returned for a warranty replacement until they fix it. :)
[Verizon Samsung Galaxy S 4] htcp85:
Got a quick question why I don't have the custom padlock unlocked boot screen after I'm rooted there is something wrong.
[Verizon Samsung Galaxy S 4] sergoreg:
Does it work on MS659 (MetroPCS) , the script stuck at

"Plug in your phone and Press any key to continue..."
[Verizon Samsung Galaxy S 4] namitutonka:
My phone: Unrooted SGH-I537, Stock Official Android 4.3, Baseband I537UCUBML2, Kernel 3.4.0-2244695, Build JSS15J.I537UCUBML2, SE for Android status Enforcing SEPF_SAMSUNG-SGH-I537_4.3_0016, Secure boot status Type: Samsung

Sunderwear's has same values except that his android 4.3 is no longer official, because his baseband version is I537UCUAMF1, which is

why he can have root access, even while running android 4.3 :good:

Sunderwear's OP at http://xdaforums.com/showthread.php?t=2690133
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
As has been stated you won't always see the custom lock on every boot. I'm pretty sure it's only on hard reboots and even then not always. Quick question back: as long as you have root, why does it matter on a cosmetic badge that most people don't even want, if you gave it?

---------- Post added at 09:59 PM ---------- Previous post was at 09:56 PM ----------

MS659 Tells us nothing. what is the phone? what is the build? is there a message on your phone about allowing ADB? Did you tell the phone to forget all previous ADB connections? What OS computer, and version? Do you have any android emulators running on the pc such as bluestacks?
[Verizon Samsung Galaxy S 4] ryks:
hello .

it works but it erase the twrp from device .-so i reinstall with odin the twrp again to make a full backup..
[Verizon Samsung Galaxy S 4] htcp85:
It doesn't matter to me I just want to know why , I thought maybe I did something wrong but tanks for the answer.
[Verizon Samsung Galaxy S 4] bozob:
I doubt that would work since the warranty bit is now set. But I did find the source of the problem and how to resolve it.

I reloaded the stock ROM and recovery using ODIN 3.07 and the TAR file from here: http://xdaforums.com/showthread.php?p=52056692 (This TAR requires 3.07)

When I rebooted I had to set-up the phone as new and shortly thereafter saw a pop-up from Samsung asking if I wanted them to periodically check and protect my device from malicious software. I remember agreeing to this last time so I did again this time and had the same problem. I did a factory and data reset and then didn't agree to the option. After that it let saferoot through and I was able to root the phone.

This may be something you want to add as a note to people who experience this problem.
[Verizon Samsung Galaxy S 4] k1mu:
The "Custom" flag is set by an application that runs on your phone and periodically looks for modified files. If it finds any, it sets the Custom flag. If it doesn't, it clears the flag.

If you haven't installed busybox along with rooting, and haven't changed anything on the phone, you may avoid the Custom flag. If you HAVE changed anything, then once you revert the files to stock you should be OK - reboot then let the scanner run (which may take an hour or more).

You then won't be "Custom" any longer.

Busybox does seem to set Custom.
[Verizon Samsung Galaxy S 4] htcp85:
I installed busybox with saferoot , I click "Yes" at the beginning of the program so should be OK, one more thing how do you check if you have busybox installed. Thanks
[Verizon Samsung Galaxy S 4] jkeuclid:
Search for "Root Checker" on Google Play and run it, has root and bb verification
[Verizon Samsung Galaxy S 4] acraigl:
So I made the mistake of updating to NC1, and lost root. Fortunately, I found the ML1 image and was able to ODIN without losing any of my settings or apps. Then I used Saferoot and now back where I was, no fuss or muss.
[Verizon Samsung Galaxy S 4] RCOO:
I wonder if this method would work on KK?
[Verizon Samsung Galaxy S 4] decaturbob:
Don't think so.. no direct root method for 4.4

sent by safestrap enabled bajarom
[Verizon Samsung Galaxy S 4] HernanYH:
samsung galaxy s4 mini i9190 4.2.2

Hello, I have the same problem. Is there any solution? i have a samsung galaxy s4 mini i9190 4.2.2
[Verizon Samsung Galaxy S 4] finite:
Thanks for this I thought I was out of luck looking for a clean method to root a Samsung Galaxy Young GT-S6310N, XXAMK1, but I thought I would give it a shot as the kernel is 3.4.0

It's worked a treat. What would be the safest way to skip the Knox section? I just sat it out.
[Verizon Samsung Galaxy S 4] k1mu:
You're not running the current Saferoot since apparently "this device is not supported" isn't clear. I've changed the message Saferoot displays to help with this case. It now says that "Your kernel is patched!". Along with "This device is not supported".

So, your kernel is patched. You must either downgrade to a kernel version that's not patched to stop saferoot from working, or find another way to root.
[Verizon Samsung Galaxy S 4] k1mu:
What do you mean by "sat it out"?

If you don't disable Knox, then there will be things that you won't be able to do even though you're rooted as the Knox utility will kill processes that it considers to be dangerous. Disabling Knox has no obvious side effects so it's quite safe to disable it.

"pm enable com.sec.knox.seandroid" will allow you to re-enable it if you care to. (You'll need to execute that command from a shell where you've used "su" to gain root permissions.)
[Verizon Samsung Galaxy S 4] finite:
I haven't found any trace of Knox on this entry level 4.1.2 phone. I just waited for the script to finish and there were a few not found messages as it ran through the disable Knox section.
[Verizon Samsung Galaxy S 4] CamCroz99:
Can anyone confirm whether this works on the Virgin Mobile version of the L710 (S3)?
[Verizon Samsung Galaxy S 4] pckarma112:
It works here too.

Just wanted to let anyone who is looking for root on this device. I have a Samung AT&T galaxy tab 3 model sm t217a running 4.2.2...build jdq39t217. Could find no way to root unless I tried kingo. No way on that. Heard to many bad reports. Long story short. I remembered I had the apk of saferoot. Installed to tablet. Ran it. Updated supersu after reboot. Done. Took a whole minute. I do not remember where I got the apk? But, I presume the pc way will work too. Sorry to post in vzw thread. But, this is good news for owners of this tablet. One more device to add to list. Thank you very much dev! Ps..I could not find a post for the att version? If I missed it. I apologize.
[Verizon Samsung Galaxy S 4] agapedisciple:
I've got a Sprint SGS3 that the usb port is unrecognized on my pc. (issue with this phone, my other SGS3 works fine.) Can I execute saferoot directly from the phone using the extSDcard? I looked at the batch file and it looks possible without using ADB, but I'm having issues with the Android Terminal Emulator app on the play store...

what do u think?
[Verizon Samsung Galaxy S 4] jmjoyas:
There is a saferoot apk. Check post 1633 of this thread.
[Verizon Samsung Galaxy S 4] pckarma112:
Thank you.

Thanks..why don't they put that in the op?
[Verizon Samsung Galaxy S 4] mva1985:
Where you about to download it... I tried several times and couldn't.

Sent from my SCH-I535
[Verizon Samsung Galaxy S 4] acraigl:
Link is dead :(
[Verizon Samsung Galaxy S 4] k1mu:
Because the author of the OP hasn't ever used that app. I'm sure it works fine, but can't vouch for it either way.
[Verizon Samsung Galaxy S 4] k1mu:
The link worked fine for me: http://playfuldroidz.com/wiki/Saferoot
[Verizon Samsung Galaxy S 4] mva1985:
Yes that link works fine. It's the actual goo.im link that is not working

Sent from my SCH-I535
[Verizon Samsung Galaxy S 4] jmjoyas:
https://www.dropbox.com/s/0f7m612p818nobw/saferoot.apk

Here's a link to the original saferoot apk.

I take no credit. All credits to the original authors.

It worked for me on my ATT S4 (SGH-i337).

1. Install APK

2. Reboot phone

3. Open the application and root.

Note: If there is any objection, I shall edit the post to remove the link.
[Verizon Samsung Galaxy S 4] mva1985:
Thank you very much.

Sent from my SCH-I535
[Verizon Samsung Galaxy S 4] decaturbob:
Samsung galaxy 10.1 P5113 successfully rooted with saferoot
[Verizon Samsung Galaxy S 4] gothicasshole:
No this requires an open adb shell your not going to get that from an sd card plus it requires reboots so it would potentially brick your phone
[Verizon Samsung Galaxy S 4] shankarana:
Rooting Script Failed

Hi I am trying Root my Note 2 GT-N7100 (running Andriod 4.3 Build xxxxxDDUENA1) on my Mac OCX . The script is throwing following error please help

*] Your phone is detected and ready for rooting.

[*] Sending files to your device...

./install.sh: line 92: [: missing `]'

./install.sh: line 96: [: missing `]'

[*] Starting rooting program.

ro.build.product=t03g

ro.build.id=JSS15J

Your kernel is patched!

This device is not supported.

[*] Checking if rooting succeeded

[*] Unfortunately, rooting failed. Cleaning up.

./install.sh: line 107: [: missing `]'

--- All Finished ---
[Verizon Samsung Galaxy S 4] mielletseed:
Please do not full quote the OP (or any other post)!

And read the script output, you will find

, this means that you cannot use saveroot for your device, since the kernel is patched. Maybe you can downgrade to an older version.
[Verizon Samsung Galaxy S 4] mva1985:
Had NC1 on my SGS3. Rolled it back to ML1 with Odin 3.07 and rooted with Saferoot... ahhh I'm feeling much better
[Verizon Samsung Galaxy S 4] k1mu:
OK, that's not right.' I'll update the script and re-post. (It's missing a space after "Y" in those lines.)

However, this:

What that means is that your kernel is patched to fix the flaw that Saferoot uses and is therefore not supported.

You can't use Saferoot unless you downgrade the kernel.
[Verizon Samsung Galaxy S 4] decaturbob:
if you had read some previous post in this thread you would had seen this issue been answered many times...your device is not supported becasue the kernel has had the exploit patched
[Verizon Samsung Galaxy S 4] shankarana:
Thanks ...

My Kernel ver is

3,0.31.-2401794

tue jan 7, 2014

Is there any other alternative way to Root & Install Custom Recovery?

I tried this as well http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-on-mac-osx/ , but didn't work.