yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] koreo:
verizon s4. build number? vruemk2. ive already rooted
[Verizon Samsung Galaxy S 4] decaturbob:
what do you mean "any roms work with this?"....what is the "this" you are talking about for starters?
[Verizon Samsung Galaxy S 4] koreo:
this root method. im a total newb but i had rooted my gnex back in the day and then went straight to cyanogenmod as my main rom. I'm trying having a hard time finding how/what/where i need to get customs roms on my s4
[Verizon Samsung Galaxy S 4] JerryGNYC:
I'm on Sprint, so can't tell you what'll work. But you may want to look around here -

http://xdaforums.com/galaxy-s4-verizon/development

Which is just one level up from this thread... (and possibly look around one more level up and then down?)

HTH,

-Jerry
[Verizon Samsung Galaxy S 4] sergiu_07_07:
Any way to root 4.4.2 without tripping the knox flag?
[Verizon Samsung Galaxy S 4] WordsworthESP:
If there was, we'd know about it.

Sent from my Hyperdriven S4
[Verizon Samsung Galaxy S 4] decaturbob:
Several threads in general section and q&a sections
[Verizon Samsung Galaxy S 4] duhst:
Have the exact same phone and build number. Having the same problem.... Help?

EDIT: The phone is Verizon but I am use on T-Mobile with T-Mobile APN settings. Not sure if that makes a differences.
[Verizon Samsung Galaxy S 4] dafonehacker:
The firmware is probably just not supported. Samsung may have patched the exploit this method uses.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Verizon Samsung Galaxy S 4] NRadonich:
Sorry, but reading through 135 pages of this thread just to see if SafeRoot works with 4.4.2 was not for me. :mad:
[Verizon Samsung Galaxy S 4] negativzeroe:
Could have used the search....
[Verizon Samsung Galaxy S 4] decaturbob:
I suspect less than 40 or 50 posts back 4.4 was discussed...but way easier for some one else to dish out an answer than to read.
[Verizon Samsung Galaxy S 4] RobertdeHoop:
confirmed: JSS15J.I9505XXUEMKF

Thanks for this solution.

Confirmed to work on JSS15J.I9505XXUEMKF
[Verizon Samsung Galaxy S 4] k1mu:
That's interesting.

The root worked, but your phone disconnected before it could complete.

I would try it again, but first plug in your phone and let it sit for a few minutes before starting the install.bat
[Verizon Samsung Galaxy S 4] Zulfi:
Can I try it on N7100XXUENA1 ?

Thank you
[Verizon Samsung Galaxy S 4] JCBiznatch:
Last night I flashed rls15 and I lost root and recovery. I have tried to reboot into recovery with home button, power, and volume up only to reboot the device instead. When I try to run titanium backup it says not root found, I have been reading this morning about safe root , but was really wondering if I could root form terminal emulator??? Thanks for the feedback guys!
[Verizon Samsung Galaxy S 4] Surge1223:
Its possible, if you look at my pic in post #21 & #47 you can see I did it through terminal emulator but that was some time ago and im pretty sure the files were already pushed to /data/local/tmp and permissions set through adb shell so maybe its not actually possible but why not use adb?
[Verizon Samsung Galaxy S 4] goldsmitht:
Safe VZW apps to freez

ok, i did use search, but nothing came up. Honest...

what apps, most notably VZW Bloat, on S3, Stock, are safe to freeze? Would like to at least freeze cloud stuff i don't use and don't want to keep turning off to save battery.

any help would be appreciated

FYI: easiest root method ever!

:good:
[Verizon Samsung Galaxy S 4] JCBiznatch:
Cpu is at my buddies getting Chrome os put on my I7. That's the only reason. Just trying to fix it before I get it back tomorrow. I'm still on MDK so should be rather easy.
[Verizon Samsung Galaxy S 4] koreo:
installed safestrap. went to create a rom slot. not enough space. factory reset and cleared. still not enough space. tried to restore my stock backup and fails everytime.. im getting worried.. =\
[Verizon Samsung Galaxy S 4] jadajada:
So the steps were:

1. Flash MK9 with Odin

2. Root with Saferoot

3. Flash ENA4 with MobileOdin with Everroot

?

Do anyone know if I can use MKF instead of MK9? For my model (csc NEE) there is no MK9, but there is an MK8 with the same changelog as MK9, are they the same? MKF is newer, so if I can flash MK9 without errors or tripping knox, I should be able to flash MKF as well?
[Verizon Samsung Galaxy S 4] JerryGNYC:
As far as space goes, is your stock backup located on internal memory? And is there more than one version? If so, you should try moving it/them to the external SD card.

EDIT: you may want to ask around in the thread for Safestrap...
[Verizon Samsung Galaxy S 4] koreo:
i moved it to the sdcard.

My phone rebooted and now i cant even get back into safestrap and no rom is install so it just sits at splash!! :((
[Verizon Samsung Galaxy S 4] JerryGNYC:
I'm still a Sam-noob, but I think you will need to reflash your phone via Odin.

http://xdaforums.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539

Believe you can get the right firmware file(s) at sammobile.com

HTH...
[Verizon Samsung Galaxy S 4] mrwormburn:
This is odd, but does anyone else have root (I do and rootchecker verifies it) access but no custom logo on the startup screen? Or has heard of this? Any possible issues with this?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Custom logo only show on certain boots (I believe only a full reboot, or maybe randomly...I'm an Android noob so I have a (only slight) chance of misstatement)
[Verizon Samsung Galaxy S 4] XxSHaDoWxSLaYeRxX:
Just a note, if you have bluestacks running on your computer, close it as it is detected as a device "emulator 555-4" and the program will fail because more than one device will be connected.

---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------

I believe the custom logo only appears if you modify system files, or it appears if you flash a rom, dont remember which.
[Verizon Samsung Galaxy S 4] bgmg:
I bought a brand new latest model ATT GS4 in early January, it had the big custom logo after saferoot. I bought a brand new latest model sprint GS4 triband in late January and used saferoot again. It has never shown the custom screen during any kind of boot. Both phones had a Custom flag of 0x1 after root. Therefore, the big custom screen must be dependant on the model GS4 or Carrier's image/setup for the phone.
[Verizon Samsung Galaxy S 4] WordsworthESP:
Both. I don't know how much SafeRoot has changed since I used it, so I don't know if it still installs Busybox. If it does, it should show the custom screen upon a full reboot.

Also, just because Root Checker says you have root access, doesn't mean you actually do.. I've had that issue myself. The easiest way to know is to actually try adding or removing something to or from system/app. If it doesn't work, you don't really have root.

Sent from my Hyperdriven S4
[Verizon Samsung Galaxy S 4] bgmg:
Hopefully this gives you theinfo you want. Read this: http://www.note2forum.com/forum/galaxy-note-3-development/4216-bloatware.html
[Verizon Samsung Galaxy S 4] k1mu:
The custom status is set by an application that runs after boot that scans your phone for non standard files. What indication you get of the status does depend on the carrier.

You can always look at the status in settings/about to see if it is normal or custom.
[Verizon Samsung Galaxy S 4] k1mu:
Folks,

I'm starting to see a trend toward off-topic questions here. Please remember that this is a Development thread.

This thread should not be used for questions not related to rooting your phone, for example what to do next, what bloat to remove, etc.

Saferoot works on a lot of different devices and we can't answer every post-root question related to all of those devices.

If it feels like a device specific Q&A, then it probably belongs in a Q&A thread.

I'm not calling anyone out here, but I do want to focus back on topic before the mods have to step in.
[Verizon Samsung Galaxy S 4] RobertdeHoop:
SELinux Permissive vs Enforcing

I have rooted my phone using Saferoot, the process was easy and well documented. BIG THANKS FOR THAT :good:.

After root I found some apps that require root are not working due to the SELinux Enforcing mode. After searching through this forum, I could not find if the root script should have updated the SELinux mode to Permissive.

In my case, It did not and I would like to know if I can change the state to Permissive and if it would help or not.

I tried some apps, but they were not able to change the state to Permissive.

please advise.
[Verizon Samsung Galaxy S 4] dafonehacker:
When I used saferoot it was also still enforcing. You could try an xposed module like Wanam to set it to permissive

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Verizon Samsung Galaxy S 4] senfinger:
Huge thanks for throwing all of this together- :good: WORKS PERFECT!!!
[Verizon Samsung Galaxy S 4] giorgiosandros:
Not working on S4 ENA4

I tried this method but got the error: device not listed or supported

Im on i9505XXUENA4.

Just had device for ONE day and already freaking out because of Samsung's apps.

It's like half the battery is being used for apps I don't even want on MY(not samsung's!!) phone.

Got it with a contract for 2 years, so I don't want to trip the KNOX warranty void.

So if anyone has other ideas for the i9505XXUENA4, you're my savior.

Thanks!
[Verizon Samsung Galaxy S 4] helboy618:
Works on ATT Galaxy Note 8.0 SGH-I467

Ran this routine on my S3 running 4.3 and worked perfectly and easily, so I grabbed my galaxy note 8.0 running 4.1.2 to see if that would work because I did not see it listed anywhere and sure enough, ROOT! Thanks!
[Verizon Samsung Galaxy S 4] Numero17:
works on samsung note 3 9005?
[Verizon Samsung Galaxy S 4] dafonehacker:
Try it. If it doesn't work nothing will happen. It is tottaly harmless. Knox won't be triggered. But it won't work if you are on kitkat.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Verizon Samsung Galaxy S 4] Numero17:
No i hate kitkat if possible i want downgrade but it s impossible for me. So knox doesnt grow if i try to install it?

---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------

No i have Android 4.3
[Verizon Samsung Galaxy S 4] dafonehacker:
If you have 4.3 there is a chance that it will work. But if it doesn't then it won't trip knox either. Hence the name Saferoot.
[Verizon Samsung Galaxy S 4] Numero17:
Ok so if i try and it works its ok if he doesnt work know not grows right?
[Verizon Samsung Galaxy S 4] k1mu:
That's answered multiple times in the original post. Please read that.

No, it won't set the Knox Warranty Void flag.
[Verizon Samsung Galaxy S 4] k1mu:
At one point, Saferoot came with a program that set the SELinux enabled flag to "Permissive" (You have to do that each time you boot as it can't be done permanently.) Once that was run, the status would display as "Permissive" even though the stock was set to default to Enforcing.

You can still do that with a Xposed Framework module. However, what I discovered was that setting SELinux to Permissive doesn't help very much. At least for the Verizon MJ7/MK2 builds, the kernel is compiled with CONFIG_ALWAYS_ENFORCING defined. What that does is to bypass many of the checks of the selinux enforcing flag in the kernel - it always acts like SELinux is set to enforcing, ignoring the selinux enforcing flag.

Given that, there's little point in setting the flag to permissive since that won't change the behavior. The only way to make "permissive" actually permissive is to replace the kernel, which we can't do. This is, of course, intentional - that's what the Knox program is all about, which is to create an execution environment that strictly limits what the userland programs can do.

I don't know if any other vendor ships a kernel built with CONFIG_ALWAYS_ENFORCING defined. If yours doesn't, then setting SELinux to permissive mode may actually allow you to do things that enforcing mode won't. In those cases, setting it to permissive is worthwhile.
[Verizon Samsung Galaxy S 4] youphone:
can anyone confirm that this rooting method works on

Verizon Samsung Galaxy Note II with OTA 4.3

already installed?

Thanks!!!
[Verizon Samsung Galaxy S 4] dafonehacker:
It depends on what build you have. You could try it. Maybe it works, and if it doesn't, its harmless (read OP)

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Verizon Samsung Galaxy S 4] Telperion:
Worked for me on 2 T-Mobile Optimus F3 phones.
[Verizon Samsung Galaxy S 4] GS4privileged:
how do i unpack

how do I unpack the zip file
[Verizon Samsung Galaxy S 4] Taboltini:
Works for me on MK2 (at&t). Thank you!!!
[Verizon Samsung Galaxy S 4] webmastir:
Arg. This almost makes me want to finally update to 4.3. Unfortunately, there's really no big pro to go from 4.2.2 to 4.3 at this time. I get a few minor enhancements that don't apply to how I use my phone, and I lose the ability to use a hacky safestrap to possibly ROM in the future. I guess I'll just keep my options open. If and or when 4.4 comes in the next year or so, I may just upgrade and get used to the fact we can never ROM on newer versions on our phone.

(why or why did i not get this phone before the bootloader was patched)
[Verizon Samsung Galaxy S 4] enfurnic:
worked great fast and easy
[Verizon Samsung Galaxy S 4] maniaryan:
Anyone had success with busybox?
[Verizon Samsung Galaxy S 4] sweh:
FWIW, the install.sh script is a little confused about whether it's "Superuser.apk" or "SuperUser.apk" but setting the case correctly in the script and setting it correctly in the files/ directory solved the problem. My MK2 rooted; very simple, very easy.

Thanks
[Verizon Samsung Galaxy S 4] -Lawless:
Now might be a good time to update your sig? :good:
[Verizon Samsung Galaxy S 4] lalec:
It wasn't just a concern about malware. The story was that the code was collecting your IMEI number and possibly storing it on a server in China. That was the reason the links to those tools were removed entirely from XDA. If you already rooted there may not be any malware on your phone but your IMEI number has already been given away.
[Verizon Samsung Galaxy S 4] tyson10:
for busybox - i rooted. then inside SuperSU went to settings / cleanup / re-install. Rebooted - re-installed super su from playstore

Super SU then disabled Knox & installed busybox
[Verizon Samsung Galaxy S 4] Swimboy46163:
To unroot, can I go into supersu and say full Unroot?
[Verizon Samsung Galaxy S 4] maniaryan:
Trickster mod saying busybox is borked hmmm
[Verizon Samsung Galaxy S 4] Nick3193:
Thank Goodness!

After just two days of not having a rooted phone I was beginning to despair. I guess I'm just a control freak, but I want my phone to work the way I want it to work, which is not always how Verizon or Samsung think I want it to work. (No, I don't need a reminder to unplug my phone when the battery is 100% charged, thank you very much. Nor do I need a constant reminder that I'm connected to a WiFi network.) I want the added security of controlling what apps can access the network. Most importantly, I want to be able to backup and restore my data! I'll be trying this method ASAP. Thanks to everyone involved for making it happen!
[Verizon Samsung Galaxy S 4] DRELUXOID:
Hmm, I just noticed that I only have SuperSU. Do we need SuperUser too? As far as I knew, they were essentially the same thing (or rather they serve the same purpose)?
[Verizon Samsung Galaxy S 4] tshelby73:
Can someone tell me if security policy updates will affect root. Should I disable it. If it doesn't affect root should I leave it on does it actually help with security?
[Verizon Samsung Galaxy S 4] tyson10:
SuperSU is what allows super user rights

---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------

trickster shows same for me as well. i tried trickster's busybox on rails -- but same thing. wonder if its something to do w/ knox
[Verizon Samsung Galaxy S 4] DRELUXOID:
So what's the point of having that AND superuser.apk as well? Aren't they redundant?
[Verizon Samsung Galaxy S 4] tshelby73:
Trixter working fine after installing busy box on rails for me. I have like 7 or 8 Knox files froze
[Verizon Samsung Galaxy S 4] -Lawless:
You shouldn't need anything more than SuperSU
[Verizon Samsung Galaxy S 4] maniaryan:
Which ones did you freeze man?
[Verizon Samsung Galaxy S 4] k1mu:
You probably had SuperSU installed earlier. This pushes Superuser.apk, but I think I'm going to update it to push SuperSU.apk.

Re: the thread earlier about busybox: that's a remnant of the xperia root. You can, after you gain root, use terminal emulator and use

"su", then "busybox --install" to install it.

I'll update the OP with SuperSU and the command to install busybox in a few minutes.
[Verizon Samsung Galaxy S 4] -Lawless:
Oh by the way, thank you very much for this. It is easily the easiest root process I've ever used.

Sent using Tapatalk Advanced Pro+
[Verizon Samsung Galaxy S 4] WordsworthESP:
FTR, 4.3 is Jelly Bean, not Kit Kat. And GS4privileged, Google will tell you everything you need to know.
[Verizon Samsung Galaxy S 4] GS4privileged:
help

when I plug my phone In to install the "install bat" file the black screen come up and I do what it say then it says unfortunately root has fail cleaning up. why is this doing this?

---------- Post added at 12:43 AM ---------- Previous post was at 12:39 AM ----------

I figured it out but it wont root when I run the bat file it just says unfurtanitly root failed, cleaning up
[Verizon Samsung Galaxy S 4] JerryGNYC:
:eek: Please do NOT quote entire OPs like that. Thanks much.
[Verizon Samsung Galaxy S 4] k1mu:
Well, apparently you figured out how to unzip it. :fingers-crossed:

Then, unfortunately, the root script said that the device was not supported, then "Unfortunately, rooting failed. Cleaning up." that usually means that your device is patched. What model, what build are you trying this on?
[Verizon Samsung Galaxy S 4] GS4privileged:
I am on nb1 I down graded using ted77 method and now am trying to root im on 4.3 now though cuz of downgrade

---------- Post added at 06:36 AM ---------- Previous post was at 06:32 AM ----------

My model is i337 I'm downgraded to mk2 now with I believe nb1 boot loader still
[Verizon Samsung Galaxy S 4] Numero17:
it doesn't work on galaxy note 3 n9005
[Verizon Samsung Galaxy S 4] Umeaboy:
When will this work on the International version of i9305?
[Verizon Samsung Galaxy S 4] dkephart:
[MENTION=2690386]Umeaboy[/MENTION] when you learn to develop, or at least hold your tongue while developers work. ETAs are the sign of a very low intelligence on XDA.
[Verizon Samsung Galaxy S 4] gothicasshole:
Hey have you looked into this ?? http://www.droidreport.com/how-root-samsung-galaxy-s4-lte-running-android-442-kitkat-xxufnba-7436
[Verizon Samsung Galaxy S 4] RobertdeHoop:
Be careful, this is not SAFEROOT: "This rooting will void the Samsung KNOX warranty.
[Verizon Samsung Galaxy S 4] k1mu:
What I know about the i9305 is that it's been reported that the phone doesn't have the /data/local/tmp folder that Saferoot uses.

Attempts to create that and push the files failed since it appears that Knox on that phone also blocks saferoot from executing.

There may be some way of working around that and making Saferoot work, but without the phone in hand there's not much that I can do.

CF-AutoRoot is reported to work on the i9305, but that requires an unlocked bootloader and will set the Knox Warranty Void flag.
[Verizon Samsung Galaxy S 4] k1mu:
That's CF-AutoRoot, which is what I used to root my Galaxy Tab 2. Unfortunately, that won't work on a device with a locked bootloader.

And, it will set the Knox Warranty Void flag on Knox-enabled devices.
[Verizon Samsung Galaxy S 4] bloodhunter112:
So this is the root we all have waited for or is it limited?
[Verizon Samsung Galaxy S 4] bgmg:
What do you mean limited? Root is Root is Root. If you have root permission then you have root permission. This is an awesome root tool because it's as safe add it gets. Read post 1 and just make sure your model is listed.
[Verizon Samsung Galaxy S 4] k1mu:
I'm not sure what you're asking for.

Saferoot works across a wide range of Android devices - phones, tablets, Google Glass, all sorts of devices.

However, there's nothing that's not subject to some limits. If you've got a really old kernel, Saferoot won't work. Same is true if your kernel is up-to-date. Nothing lasts forever, so anything running native KitKat probably can't be rooted using Saferoot. They've adapted.

Given that, look at the OP for the list of what's rootable using Saferoot. It's not the fix for everything, but it's pretty useful at the moment.
[Verizon Samsung Galaxy S 4] bgmg:
Any limitations are listed in post one. The only limit that comes to mind is that it's not yet work on 4.4 kit kat.
[Verizon Samsung Galaxy S 4] k1mu:
You'll get more help from a forum specific to the i337, however it seems that your kernel is still patched even though you downgraded. I've just got a Verizon S4, so without a link to whatever "the ted77 method" means, I can't really help. Google doesn't find anything obvious.
[Verizon Samsung Galaxy S 4] GS4privileged:
I think this is the link http://xdaforums.com/showthread.php?t=2663545&nocache=1

and this supposedly has been do before for nb1 sgs4 everyone told me I just have to down grade then gain root through saferoot then id be able to do acouple other things to get around it
[Verizon Samsung Galaxy S 4] k1mu:
Having read a bit of that thread, it does NOT restore your phone to MK2, it installs a few files that allow you to trick the NB1 update into completing.

You have NB1, aka Kit Kat. Not rootable using Safestrap. Specifically, you have a patched kernel and can't downgrade it.

For example, post #43 from that thread:
[Verizon Samsung Galaxy S 4] GS4privileged:
Ok so how then would I root it, cuz everyone has told me to downgrade than I can root it
[Verizon Samsung Galaxy S 4] raf1hh:
Confirmed root on Galaxy NX (JDQ39)

this is mostly for google and anybody else trying to root the galaxy nx camera. Saferoot worked fine on build JDQ39 (Android 4.2.2) for me. Don't have to do anything special just follow the instructions in post #1.

Btw, thanks for the hard work.

Raf
[Verizon Samsung Galaxy S 4] k1mu:
I don't know - you'll have to ask the people telling you to downgrade how to do that, as Surge said in that thread that it's impossible to downgrade. That thread tells you how to fake a downgrade to allow a failed update to Kit Kat to complete.

I know I'm going to get tired of saying this: There is no root technique currently available for Kit Kat phones with locked bootloaders.

Since you've allowed the 4.4 OTA to update your kernel, you'll have to wait for a new rooting technique to be discovered.

Edit: OK, now I'm completely confused. As I read on in that thread, it's apparent that people ARE able to downgrade successfully and re-root with Saferoot. There may be something you're missing, but I think you'll get better help if you ask over there. However, I'm still reading.
[Verizon Samsung Galaxy S 4] ALD3:
Check below for information on downgrading from NB1 and also rooting NB1. Had my I337 rooted in Deadly Verom NB1 for about a week.

http://xdaforums.com/showthread.php?t=2447482
[Verizon Samsung Galaxy S 4] MisiuKP:
[MENTION=3940199]k1mu[/MENTION]

Thank you for saferoot.

Work flawlessly on ATT Galaxy Note 2 model SGH-I317 Android 4.3
[Verizon Samsung Galaxy S 4] -=puma=-:
Works on SCH-R530U.

:o

Add Reported Successes model SCH-R530u U.S. Cellular
[Verizon Samsung Galaxy S 4] Tickie:
OTA KitKat Android 4.4

I have been checking and some say this saferoot will work on the new OTA push of KitKat on the I9505... Has anyone in here tried it?

:cowboy:
[Verizon Samsung Galaxy S 4] ggravier:
What about next firmware update?

Hi!

Question... if I want to update to the next version of the firmware that comes out (either next 4.3 update, or 4.4 if ever)... will I need to unroot first?

Gilles.