yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Festivale26:
Saferoot works on Samsung Note 8 N5110

I had to restart it once, and also change from MTP connection and Camera, and later back again to MTP to get it to finish, but IT WORKED! It said it was installing Busybox, but it did not. I can download that from the Play store anyway. Kudos to the dev!! Donation sent - with thanks!!

Question: Previous to rooting my device with Saferoot, I used Odin to flash 4.2.2 as I did not have that option for OTA or via Kies. I was stuck on 4.1.2. After using saferoot, in Download mode I see the following:

ODIN MODE (in red)

Product Name: GT-N5110

Custom Binary Download: No

Current Binary: Samsung Official

System Status: Official

So it appears from this I am not rooted (even though I am)...however....

When I go to Settings....About Device....Device Status....It shows "Custom". Is that a flag to Samsung or others if I needed to take my device in for warranty work of any kind?
[Verizon Samsung Galaxy S 4] Baenwort:
I get to this step on my Samsung Note II T-Mobile 4.3 and I do not get a pop up in SuperSU asking me to grant permission.

I see two access attempts in the log but no pop up.

What should I try next?
[Verizon Samsung Galaxy S 4] mezo91:
How come we can root note 3 and not i9506 s4? It is so annoying
[Verizon Samsung Galaxy S 4] gothicasshole:
LEARN TO READ THERE IS NOTHING WE CAN DO ACCEPT IT MOVE ON ACCESS DENIED YOUR KERNEL IS PATCHED MEANING THE EXPLOIT WILL NOT WORK UNLESS YOU CAN GET ODIN.TAR FILES AND DOWNGRADE TO THE PREVIOUS UN PATCHED SOFTWARE YOUR STUCK HAVE A NICE DAY!!!! AND STOP TROLLING

---------- Post added at 11:43 PM ---------- Previous post was at 11:34 PM ----------

Bc the note 2 mk2 4.3 isnt patched you accepted the security update which patched it you did this to yourself now live with it *rolls up the news paper* dont make me smack you with it
[Verizon Samsung Galaxy S 4] k1mu:
There's a program that runs after your phone has finished booting that scans for altered system files. It'll find those, then set the "System Status: Custom" on the boot screen. It won't appear that way the first time you boot until you give the scanner time to find things. It sounds like the scanner has run now and set the Custom flag.

You can remove that temporarily by using one of the techniques mentioned in the first post. Or, permanently remove it by flashing a factory stock ROM, which is what you should do prior to returning it anyway.
[Verizon Samsung Galaxy S 4] k1mu:
Sorry, but since all of the responses that I've received in this thread about the status on the i950x phones have ignored my questions and simply re-stated that it "doesn't work", well, then, I guess it doesn't work. This isn't a case of a patched kernel, if I'm understanding correctly, since the rooting program runs but can't install su. If that's really the case, there may be something that can be done, but it's not going to be easy, and can't be done without cooperation by the user base.
[Verizon Samsung Galaxy S 4] k1mu:
When you opened SuperSU did it offer to update the "su" program, or did it give any other error?

If you can use "adb shell" or terminal emulator to open a shell on your phone and type

Then try "su" at the shell prompt. Does SuperSU ask for permission?
[Verizon Samsung Galaxy S 4] mezo91:
Wow. I didn't know you had caps lock in your keyboard. Thanks for sharing that information.

---------- Post added at 05:40 AM ---------- Previous post was at 05:39 AM ----------

Thanks for the answer. I guess I'm stuck then. Great app too.
[Verizon Samsung Galaxy S 4] Breezer23:
Will removing apps from the system folder trip knox? I'm on the 4.3 JB Rom (Verizon). Unfortunately, I dropped my previous Note 2 and now I'm stuck using this method with my now locked bootloader. Sad face indeed.
[Verizon Samsung Galaxy S 4] equlizer:
freeze everything to do with knox then you can uninstall/disable what you want. (just to be safe)

Method worked on note 2 Bell 4.1.2. Tempted to update to 4.3 :P
[Verizon Samsung Galaxy S 4] k1mu:
No. The only thing that will trip the Knox Warranty Void flag is attempts to flash a non factory kernel or recovery. You will get Custom status, but not Knox.
[Verizon Samsung Galaxy S 4] k1mu:
I guess that's the case. Since I can't get any real details on what happens when you try rooting, I can't help with why it's failing. All I know at this point is that it fails.
[Verizon Samsung Galaxy S 4] gothicasshole:
Random question... is there a way someone can catvch an ota and reverse engineer it to get the boot loader key?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Based on the fact that it's not being done, i'm going to wager a hard no
[Verizon Samsung Galaxy S 4] gothicasshole:
Guy can dream lol it would be awsome
[Verizon Samsung Galaxy S 4] mp5navy187:
Just saferooted my i337 but now my wifi wont work doesnt turn on?
[Verizon Samsung Galaxy S 4] THE-COPS:
.. The alternate USB drivers did the trick. Once they were installed, adb request came on screen as soon as it went into MTP mode. Not sure why same drivers don't work on all other VZW S4's... shrugs .. anyways. Root success :D :good:

Thanks all for your help. Now to get rid of that damn VZW bloat.
[Verizon Samsung Galaxy S 4] k1mu:
No. The key is held by Samsung and used to sign the bootloaders. The signing key (the private key) never leaves Samsung's premises.

The piece that's used to verify that signature (the public key) is openly available, but that can't be used to create the signature in the first place.
[Verizon Samsung Galaxy S 4] k1mu:
Did you also install Safestrap? You'll need to flash the proper kernel modules.

If not, what else have you done after rooting? Saferoot will not cause your wifi to stop working.
[Verizon Samsung Galaxy S 4] mp5navy187:
I got it all last nite figured it out just gotta read all the thread's provided
[Verizon Samsung Galaxy S 4] k1mu:
Thanks! Working this out was fun. Now I'm just polishing the edges to get it working as well as I can.
[Verizon Samsung Galaxy S 4] dhc1214:
Ok, stupid question time. Now on restart(and other random tines) I get a notification from Verizon support and protection saying "Software on this device has been modified" I immediately checked knox and found 0x0. I did not freeze anything. Even when superSU asked me to disable knox, I chose no.

If I click the notification I am taken to the verizon support and protection app where is wants me to perform a scan(yeah not happening).

If I disable the knox stuff will that take care of this notification? If I do let SuperSu disable knox, how would i re-enable it if necessary?
[Verizon Samsung Galaxy S 4] k1mu:
I disabled Knox using SuperSU and don't see those notifications.

To re-enable it, open terminal and type "su pm enable com.sec.knox.seandroid"
[Verizon Samsung Galaxy S 4] DRELUXOID:
That's weird then, because I ended up with SuperSU after running the script. I definitely did not have it before.

It's SuperSU v1.80.

Could this be a result of getroot or install-recovery? Or perhaps busybox?
[Verizon Samsung Galaxy S 4] k1mu:
I think this was a naming problem - the APK was called SuperUser.apk, but it was actually SuperSU.

It's now called what it should be, and installed into /data/app versus /system/app so you can update it if necessary.
[Verizon Samsung Galaxy S 4] DRELUXOID:
Ok, that was my other hunch. Either way, it worked out well as SuperSU is what I wouldve preferred anyway. I like how it grants permissions better than how superuser would do it.
[Verizon Samsung Galaxy S 4] RockRatt:
[MENTION=3940199]k1mu[/MENTION];48392009 I "HOPE" I never have to use this as I got my S4 before it was locked down like fort KNOX... But wanted to give Thanks for where thanks is due. Great job on this and thanks for giving hope for all the ATT S4's stuck on 4.3 My sincere gratitude.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[Verizon Samsung Galaxy S 4] nickknaack:
This was oddly easy. THANKS! :)
[Verizon Samsung Galaxy S 4] k1mu:
Don't forget to click "thanks" on the OP :)

(Yeah, I'm a thanks counter junkie.)

For those of you worried about the "Custom" showing up at boot:

Install the Xposed framework and Wanam Xposed.

In Wanam, Security Hacks, tap on "Fake system status". Problem solved.

I also have "Disable Knox notifications" selected.
[Verizon Samsung Galaxy S 4] azuziel:
New kingo doesnt harvest emei, that wad vroot running thru kingo interface. Kingo guy has a twitter and a website and responded in spades to that issue, and has released a new version that has that malicious vroot code removed. Remember, kingo is only an interface that uses existing ecploits to gain root, one of which was vroot

We also have gobs of antivirus for Android now. Ive been running avg for a few weeks and it has caught a plethora of malware and Trojans attemping to piggy back in on other apps. Have seen no such activity when using kingo.

Also ran tcpview and tcpdump while running Kingo on a fellow IT staff handset, neither of us could see any traffic to china, also checked logs and real time on asa 5505, didnt see anything suspicious in new version. Just fyi.

To the author, thanks for the new/old method :)

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] shindiggity:
If I'm rooted with vroot what's the easiest way to go back to stock so I can re-root?
[Verizon Samsung Galaxy S 4] k1mu:
Correction: the new Kingo SAYS that they don't harvest EMEIs. There's no proof that they're not. Nobody has source.

Vroot and kingo are risky. Nobody knows how risky, and nobody will know for quite a while. They built their product on somebody else's work, which is what I did. However, they won't tell you what they're doing. There is no reason for that that I can see.

Yes, my rooting program is built on the same exploit that vroot/kingo uses. I figured out how to extend that exploit to allow it to work around the SELinux restrictions - the original exploit would not work on our devices.

I promise that there's no data sent ANYWHERE when rooting. And if you don't trust me, read the source. Kingo? Source eventually, maybe, for something - who knows if that source will correspond to what they're doing today. Vroot? No comment from them. And I'm not convinced that they're not both the same group of individuals just trying to obscure what they're doing.

As I've said repeatedly, I have no evidence that vroot or kingo is malicious. Keep in mind that absence of proof is not proof of absence.

However, what my rooting program does is open and transparent. Vroot and kingo are not. The obvious reason for them to not be transparent is because it would harm them. Why is that?
[Verizon Samsung Galaxy S 4] k1mu:
I don't think it's worth doing that, actually. There's no evidence that vroot is doing anything bad.

If you're worried, flash the MJ7 emergency recovery ROM (which will wipe everything), then re-root. That's a lot of pain for a marginal concern.
[Verizon Samsung Galaxy S 4] azuziel:
Edited post so it's done with. My mistake.

Anyway thanks again to the authors of this new/old method. Im sure it will help a lot of folks.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] Craleb:
So I have used xposed in on the past. But never on a stock ROM like this. Are all the settings in wanam xposed module safe safe to change? Have you (or anyone) experimented with this more?
[Verizon Samsung Galaxy S 4] azuziel:
I read somewhere here i a thread that wanam *does* trip knox. Can anyone confirm? I know xposed works in memory, so cant really effect it, tho not all that familiar with wanam. Just wanted to share what i read from someone else's experience. Believe was in knox thread.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] TemporalShadows:
That kind of personal attack is uncalled for, first of all. k1mu wasn't attacking you or your skills, he was simply explaining his viewpoint.

Secondly, I'm an IT guy, and I agree that it was irresponsible. Sure, you can see AFTER you've run it on your corporate network that there were no packets sent, but you didn't know that when you made the decision to do so. Aside from that, we all miss things from time to time, and it could have done something you missed. I'm not saying it did, but it certainly could have.

Bottom line: both kingo and vroot have done shady things in the past and should be viewed with at least mild suspicion, and any IT guy worth their salt wouldn't lash out at someone for harboring such suspicions.
[Verizon Samsung Galaxy S 4] azuziel:
K

Nope. Not the case at all. Thats what dmzs are for my man. Segregated, yet allows me to analyze.

Glad you came running to your budz defence, guess chivalry isnt dead.

And i didnt lash out at all. All he (and you) had to do was ask how i setup my lab. Thats all. Attempting to publicly shame someone (if you work in IT then you know full well calling someone Irresponsible is as bad as calling someone stupid) is what was uncalled for. A simple I disagree wasn't enough? I stand by my opinion, and my lab was *very* secure and segregated, virtual equivelant of another continent.

Im a virtualization (vmware) and cisco guy myself. What are your specialities? Aside from android i mean.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] Craleb:
Omg you scared me! I have wanam installed and have gotten the custom boot screen back to official. ( I don't know why I care so much)

But I just checked and Knox is still 0x0 *whew*
[Verizon Samsung Galaxy S 4] R1150GSA:
Thanks, Thanks, Thanks!!!

Lots of thanks to k1mu et al for this rooting method. :good:

With news of Heartbleed still running around I wasn't too keen on going the Kingo route to get root. This method bypasses the dangers of IMEI harvesting. Even if it's a small step it's better than nothing when it comes to securing identity.

My installation was a bit wonky. I made sure I followed all steps to the letter but the dialog wouldn't progress. I knew my drivers were installed because my device was being detected.

My problem seemed to stem from the MTP/PTP settings. I shut down ADB and tried both. I believe it worked when I selected PTP and re-ran the install batch file. Suffice it to say, you'll know you've got it right when the script starts rolling.

The one item I'd like to see in the OP is in regards to OTA updates. My concern was that the root status would somehow block the long awaited Kit Kat update for the S4 Mini SCH-I435. So, I'm assuming OTA updating will still work, but I will lose root if I choose to update. Is that correct?

Anyway, thanks again k1mu. Outstanding work, and I await further greatness as new updates appear for this device.
[Verizon Samsung Galaxy S 4] k1mu:
If

all

you do is to root, it will not cause the OTA to fail. As soon as you start modifying anything else, it may break any OTA.

For example, installing Xposed Framework. Or removing "bloat", installing Safestrap, etc, all will probably break the OTA (but it won't break your phone - just fail to install.)

Right now my phone is stock MK2 rooted. It *should* take the Kit Kat update just fine since I haven't done anything else

You are, of course, correct that Kit Kat will remove root. It may be hard to get it back once updated. Samsung and Verizon are tightening the noose!
[Verizon Samsung Galaxy S 4] Keekers:
I'll accept the jabs...how do I tell if I have Saferoot or not? I always have to try a bunch of different threads to root my devices because I'm using a Mac. I don't remember how I rooted my phone and want to have Saferoot so I can WiFi tether and flash other ROMs.

<-----blonde moment
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
First what device are you on

Then what build (settings>more>about phone)

Next all "saferoot" refers to is running the file in the first post. The safe is in reference to the sketchy method for rooting the S4 previous to finding this exploit toward root. So it's not realllly something you have or don't have.
[Verizon Samsung Galaxy S 4] Keekers:
I'm on MK2. Oh okay that makes sense...I was confused. Thanks
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Ok if you're on mk2 and just updated to it, quickly go to

Settings>More>security

Roll down to the bottom and in the second to last section you'll see "security policy updates" tap that and remove the checkmark from automatic updates. DO NOT PRESS MANUAL UPDATE

Now read through the first and second posts in this thread

:)
[Verizon Samsung Galaxy S 4] Keekers:
Okay I followed your instructions and unchecked the check mark from automatic updates. I have read through pages 1 and 2 but went back again. I'm still just as retarded as I was before and can't figure it out. Sorry :(
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Since I don't have a mac I can't help from there, but someone will be by soon to pick this up
[Verizon Samsung Galaxy S 4] gothicasshole:
did you open the shell command??
[Verizon Samsung Galaxy S 4] mp5navy187:
Does deadly venom update there S4 rom monthly or no?
[Verizon Samsung Galaxy S 4] jkeuclid:
Has anyone tried this yet on the OTA KK UCUCNC9?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
[sarcasm]I don't know[/sarcasm] perhaps if you read the thread, or even the last few pages, you would see that it is very unlikely (translated to "as impossible as you as an individual can imagine" ) that this method will work with 4.4
[Verizon Samsung Galaxy S 4] jkeuclid:
:laugh: oh I do realize that, just curious if anyone had balls big enuf to try it, not me ;)
[Verizon Samsung Galaxy S 4] bgmg:
It doesn't take guts to try it because it's harmless to try it, hence the name saferoot. This method does not flash a recovery like other methods and will no trip Knox. That being said, it's virtually impossible it will work on kit kat at this time as previously stated.
[Verizon Samsung Galaxy S 4] decaturbob:
Wrong thread to post...
[Verizon Samsung Galaxy S 4] Keekers:
With the terminal emulator?
[Verizon Samsung Galaxy S 4] VICIOUSVIC1:
Hello am currently trying to root my wife S4 we got it for cheap. I downloaded saferoot zip and have enabled USB debugging in dev mode all drivers installed. The problem is after opening saferoot file prompt opens and instructs me to plug in s4 and press any key as soon as I press prompt goes away and nothing happens. I am familiar with rooting as I myself have a rooted s4 only difference is I was able to use casual root. Is there something I am missing?
[Verizon Samsung Galaxy S 4] jkeuclid:
Try revoking USB aurhorization under developer options, then try again. Sometimes after doing this, you run saferoot, plug in your phone it prompts to reauthorize for this PC and of course you do but then it doesn't do anything. Just close saferoot, disconnect your phone and restart saferoot, it should then work.
[Verizon Samsung Galaxy S 4] k1mu:
If the command prompt window is closing too quickly for you to tell why, you'll need to do this a bit more manually.

Note where on your computer you have unzipped the Saferoot zip file.

Then, open a command prompt window. To do that, press the Windows key and type "cmd" and press enter. (Windows 7 or later), or press the Windows key, click on run, then type "cmd" and enter. In both cases, don't include the quotes around "cmd".

Now you have a command prompt window open. Type CD, a space, then the path to your unzipped saferoot:

Now, type "install" (without the quotes) and press Enter. Let me know if there are any errors.
[Verizon Samsung Galaxy S 4] VICIOUSVIC1:
Am using windows vista
[Verizon Samsung Galaxy S 4] k1mu:
It's probably start/run then type CMD to get to a command prompt.

Vista? ew. That's even worse than Window 8!
[Verizon Samsung Galaxy S 4] VICIOUSVIC1:
Yes am in the command prompt but am unable to enter script. C\Users\VIC> This can not be deleted or edited
[Verizon Samsung Galaxy S 4] k1mu:
type

to set your directory to the place where you unzipped saferoot. Note that there's a space after the "cd".

Typing

Should show you install.bat, install.sh, etc. Like this:

now you can just type

To run the rooting script.
[Verizon Samsung Galaxy S 4] gothicasshole:
Depends just pay attention to the thread for us we must use the safe strap I'm on deadly Venom and I like it ;)
[Verizon Samsung Galaxy S 4] mp5navy187:
It is a smooth Rom I love it... Gonna been on you tune checking other Roms nothing really comes close golden eye looks fun
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Oops missed a page of answers lol
[Verizon Samsung Galaxy S 4] VICIOUSVIC1:
Have tried and tried but can not get it to run keep getting error message system cannot find path.
[Verizon Samsung Galaxy S 4] VICIOUSVIC1:
Here are the results of my last try I have tried a number of commands with same result getting annoying Att is trying to force update phone currently on mk2
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
From where you are c:\users\vic type

cd desktop

If install.bat is on the desktop

Then Type

install.bat

If not on desktop

Then repeat the first part replacing "desktop" with the name of the next folder. If the folder has a space in the name ( e.g. c:\users\vic\desktop\android root\ ) you must put " marks at the front and back of the entire folder (e.g. cd "c:\users\vic\desktop\android root"
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Wow I'm bad at reading today, please ignore this post

(Number 1610 I mean)
[Verizon Samsung Galaxy S 4] k1mu:
You want to change the directory to the folder containing the saferoot files.

Based on your screenshot, that's

cd \users\vic\downloads\saferoot

now you should be able to see install.bat if you type "dir" and enter.

Type

install.bat

to run it.
[Verizon Samsung Galaxy S 4] VICIOUSVIC1:
Well thanks for the help but phone Ota updated. It freaken sucks how AT&T force updates devices without owners consent. We paid for our devices so I do believe its no longer theirs so I feel they should butt out and let owner do as they please with device they paid for with hard earned money..
[Verizon Samsung Galaxy S 4] gothicasshole:
OK your going to have to take those adb files and install them to your system install them in the windows folder on your c drive seems like your not getting adb

---------- Post added at 06:48 PM ---------- Previous post was at 06:43 PM ----------

All hope is not lost your on att?? Here's a tool to partially go back to mk2 ;) he he he flash a custom 4.4.2 rom :) now please please ease read re read and comprehend and ask questions if you must I recommend deadly venom

http://xdaforums.com/showthread.php?t=2680868
[Verizon Samsung Galaxy S 4] demoncamber:
Has anyone attempted this on an LG G2 D801 running OTA 4.4.2?
[Verizon Samsung Galaxy S 4] gothicasshole:
Idk we have to odin flash partial boot loader upgrades it's a bit technical I'm not familiar with LG it's worth a shot tho but please contact your devs if you need a boot loader downgrade and root I'm not too sure this is for 4.3 root not kit kat
[Verizon Samsung Galaxy S 4] k1mu:
Nobody has mentioned trying it on that LG model. However, 4.4.x releases are unlikely to be rootable using Saferoot.
[Verizon Samsung Galaxy S 4] pckarma112:
It worked

It worked again on sgh i747 \mjb...took all of five minutes. Thanks to Dev. Who cares if this is Verizon forum...lol
[Verizon Samsung Galaxy S 4] Joeseph Mother:
For those of us without a working USB port (thanks Samsung...), you can get this working without adb. Just edit the getroot.c and change the path from /data/local/tmp to a data location you have permission to write to (I used the /data/data/berserker.android.apps.sshdroid since I used sshdroid to run the commands anyway), recompile, move the files to the directory you used, chmod getroot and busybox, and run getroot. Thank you to the op for posting the source so I could root my broken phone and keep it going for a little while longer.
[Verizon Samsung Galaxy S 4] k1mu:
Wow. Impressive. :)

I'll update the getroot source to take the working directory as an argument so you can put the files wherever you want.

The cool thing is that if some distribution blocks installs from /data/local/tmp you've just pointed out a way around that.