yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] k1mu:
Is it the "This device is unsupported" message from saferoot? Then, as above, that's caused by having a kernel that's patched to fix the flaw that saferoot uses to root the device.
[Verizon Samsung Galaxy S 4] k1mu:
Sorry - I just updated the unroot script the fix that. Either unroot by hand as described in post #2, or re-download the saferoot.zip and root again. That should push a fixed copy of unroot onto the phone.
[Verizon Samsung Galaxy S 4] joNz.:
My phone is already rooted, do i have to redo that before unroot?

EDIT: re-downloaded the saferoot.zip and tried running the unroot.bat, now i get this:

"tmp-mkish: /system/xbin/unroot: not found"

EDIT2: I tried the manual way through Terminal Emulator, how do i know if it worked?
[Verizon Samsung Galaxy S 4] k1mu:
That "tmp-mkish" is a different problem from what I was seeing. I'll try a couple more devices to see if I can find and fix it.

To tell if unrooting worked, reboot your phone and wait an hour. It should then show up as "Device status: Official".

Or, use a file manager and look in /system/xbin - there should only be three or four files there, and no "su" or "daemonsu".
[Verizon Samsung Galaxy S 4] joNz.:
I didn't do the unroot from supersu yet, just did the first part with those commands in terminal emulator.

that was what i was wondering should i get any message after typing those commands?

or am i good to go for making a full unroot from supersu?

Took a shot and ran the full unroot from supersu and restarted my phone, seems to work. checked with the root checker and it said my phone was not rooted, and now im downloading a update OTA, so it works :)

was only using the root to get rid of ads and boost the cpu a little, but felt later on that root was not needed for me and i wanted to update to the latest android version :) but thanks for all the time you put into this and answering my questions.
[Verizon Samsung Galaxy S 4] Benduchi:
awesome this worked on my 1 month old SGH-i537 4.3 thanks
[Verizon Samsung Galaxy S 4] masondoctorjt:
Apparently mk4 and uc1 must use the same bootloader? Because I did odin mk4 over uc1, and now im on mk4 and my warranty bit is 0.
[Verizon Samsung Galaxy S 4] phochiom:
Worked on GT-N7100 (international Note 2), on Stock 4.3, Knox 0, used Wanam xposed to revert custom to official.

Now I'm rooted without tripping Knox. Thanks :)
[Verizon Samsung Galaxy S 4] slbenz:
I have the same problem using my T-Mobile S3 phone. Hope there is a solution to this. Mine is updated to Android 4.3.
[Verizon Samsung Galaxy S 4] k1mu:
As above, the "this device is not supported" means that whatever update you've installed includes a kernel that's patched such that Saferoot won't work. I can't promise that any such flaw will ever be discovered.

If you can downgrade your kernel, you'll be able to root it. If not, you'll need to find another way to root (for example, CF-Root, since you have a phone with an unlocked bootloader).
[Verizon Samsung Galaxy S 4] THE-COPS:
Has Verizon patched their S4 4.3 as of late? Because I can not get the ADB screen to come up on the phone regardless of what I do. Developer options are enabled, USB Debugging is checked, computer with Windows 7 has KIES 3.2 latest (had 3.0 and it wasn't working with that, then it asked to update), and yes KIES sees the phone and connects without any trouble. On the phone, when I plug the USB cable in, it immediately shows "Installer Mode" at the top... I run the install.bat file, first time I run it, it hangs after it says "Press any key to continue" and tapping a key. I have to X out of it otherwise it just sits there. Second time I run it, it doesn't get stuck, but it stays on "waiting for phone to appear". On the phone, I go to USB mode and change it to MTP....occasionally switching it to camera mode and back to MTP every 30 seconds or so. The computer sees the phone and opens a prompt to View files etc, but NO ADB pop up ever appears on the phone screen. I tried the "Revoke" thing in the Developer options, turned off and back on Debugging mode and even rebooted the phone, still I'm going thru the same thing over and over.

What is the reason for this? Would Windows Defender do anything to it? I don't have any AV software turned on at that time. And one other thing, on the computer, you say to open Properties for Install.bat and check the box "Run this program as an Administrator". Well, I can't do that, that box is grayed out and can't click it. My computer and User account are already set as Administrator so Idk if that is the reason. Any help you can provide would be appreciated.
[Verizon Samsung Galaxy S 4] dafonehacker:
Did you run the script as administrator in windows 7 by right clicking and then choosing run as admin? You could try to make a new user account with standard privileges, maybe it will work then?

Verzonden vanaf mijn iPad met behulp van Tapatalk
[Verizon Samsung Galaxy S 4] odicamillo:
Can you please elaborate a bit on what you mean with "locked" and "unlocked" bootloader?

After many forum pages here and there I understood that the Knox bootloaders are all locked in the sense that:

1. You cannot downgrade the bootloader.

2. You cannot downgrade the firmware (even if someone claim to have succeeded to downgrade excluding the bootloader from the downgrade).

3. When you try to downgrade with a Knox bootloader installed you may get a bricked device.

4. Whatever you flash that is not an official stock upgrade will trigger the knox flag.

By contrast when you don't have a Knox bootloader you can do whatever you want. Only in this case I would say that the bootloader is unlocked.

Thank you in advance.
[Verizon Samsung Galaxy S 4] JerryGNYC:
I believe that what is meant here is... that if you have an unlocked bootloader, you can flash a custom recovery like Philz Touch. This will let you do all sorts of neat things like nandroid backups, flashing custom ROMs (without Odin and tar files and all that detritus). If your bootloader is locked you can't do any of that.
[Verizon Samsung Galaxy S 4] k1mu:
I've never had a phone that couldn't get into ADB mode, so I'm not sure what to suggest.

You can narrow down what to try a bit, though. Open a command prompt (start/run cmd) and use the "CD" command to change your directory to the folder where you unpacked saferoot. Then use "cd files" to change into the files folder.. now you should be able to use adb commands to probe your phone.

First, plug it in. You should see "Connected as an installer" on your phone.

Now, wait a minute or so, then open the device manager. (To do that, hold down the Windows key and press "Break", then click on "Device Manager").

What devices show up? You should have an "Android Phone" with "SAMSUNG Android ADB Interface" underneath, and a "Portable Devices" with the "SCH-I545".

In the command prompt window, typing "adb devices" should show your phone listed.

If not, unplug your phone. Use the task manager to kill anything running adb.exe, then try again.

If that doesn't help, try a different USB port.

If you get this far, what's probably going wrong is that the ADB device driver isn't being installed for some reason. Uninstall Kies and any Samsung drivers, then install the driver package from the first post here. Cross your fingers at that point as that's about everything I can think of offhand.
[Verizon Samsung Galaxy S 4] Marshmellow92:
btw just so you can add to list. I succesfully rooted a ATT galaxy s3 on 4.1.2.
[Verizon Samsung Galaxy S 4] dbpaddler:
Anyone successfully do this on a Sprint S4 Mini on NA7, 4.2.2?
[Verizon Samsung Galaxy S 4] k1mu:
[MENTION=2696307]JerryGNYC[/MENTION] is right.

"Knox" is an umbrella term that Samsung uses to describe a range of security features that allow tight control of their devices. One of the Knox features detects when someone tries to flash unauthorized software and either rejects it or records the fact that the device has been tampered with. Tampering (trying to flash an unauthorized kernel or recovery) sets the warranty void flag.

A device with a locked bootloader will reject most attempts to modify those critical files. You can sneak by those restrictions, but that'll usually end up with a bricked device which will show Knox Warranty Void once you recover it.

A device with an unlocked bootloader will allow you to flash a custom kernel or recovery. If that bootloader is Knox enabled, it'll detect the unauthorized modification and set the Knox Warranty Void flag but allow the update. So, for those devices, you can do what you want as long as you accept the consequences of the Warranty Void flag. (Which seems to be limited to the fact that you can't build a Knox container, which only matters to corporate users.)

Bottom line - pre-Knox you could do what you want without impunity on unlocked devices.

Post-Knox you may be able to flash, but it'll be irreversibly recorded.

Having a Knox-enabled bootloader on a locked phone severely restricts what I'll be able to do.
[Verizon Samsung Galaxy S 4] Beanerman:
Thank you!
[Verizon Samsung Galaxy S 4] odicamillo:
Thank you for your detailed answer.

But now the question is: how do you recognize a locked bootloader?

Before I thought Knox bootloader=locked bootloader. But now you say that you can have a Knox unlocked bootloader.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
It's based on your carrier and Build Number (found in settings>more>about phone
[Verizon Samsung Galaxy S 4] k1mu:
You shouldn't have to run the Saferoot install.bat as Administrator. It's possible that your Antivirus could block the install.bat as it's "Downloaded from the Internet", but other than that, there's no reason to need to run it privileged.
[Verizon Samsung Galaxy S 4] equlizer:
so no love for the I317M variant? :(
[Verizon Samsung Galaxy S 4] LVMickey:
I've used this a few times now to root my 1337 AT&T model and been totally successful but for some reason it just doesn't want to work this time. i run the .bat and it gets stuck at the first file it tries to send which is the Superuser.apk Does anyone know why it stopped now? I did just use Odin to revert to factory.
[Verizon Samsung Galaxy S 4] AndroidCraig:
I'm going to revisit my rooting problem on my S4 that's on MK2. I recently did another factory reset and then downloaded the latest saferoot.zip from post 1. I ran the install.bat and ran into the same issue as before where permission is denied for /system/xbin/daemonsu. I tried adb shell and then SU to get the # prompt, but no go. Then I read in a later post about trying adb shell then super. Voila, I had the # prompt. But where do I go from there?

I am still not rooted, but I at least can get to super prompt.
[Verizon Samsung Galaxy S 4] Trak-X:
If super works, then do:

pm disable com.sec.knox.seandroid

then

chmod 6755 /system/xbin/su

then

reboot

and see if you have root with Root Checker
[Verizon Samsung Galaxy S 4] tshelby73:
Anyone know anything about my Verizon app asking for root. It did this after latest update. Some research days it may be Verizon trying to break contracts or warranties of you have root. I froze it for now but my other phone is data capped and like to see the data usage.
[Verizon Samsung Galaxy S 4] AndroidCraig:
Tried them and this was the result:

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

D:\saferoot\files>adb shell
shell@jfltevzw:/ $ super
super
root@jfltevzw:/ # pm disable com.sec.knox.seandroid
pm disable com.sec.knox.seandroid
Package com.sec.knox.seandroid new state: disabled
root@jfltevzw:/ # chmod 6755 /system/xbin/su
chmod 6755 /system/xbin/su
Unable to chmod /system/xbin/su: Read-only file system
10|root@jfltevzw:/ #

What's my next option?
[Verizon Samsung Galaxy S 4] jmjoyas:
Before the chmod command, run "mount -o rw,remount /system" without quotes
[Verizon Samsung Galaxy S 4] k1mu:
Is there anything on the phone popping up from Knox that's denying the push?

It may be that you have something like SEAndroid stopping the file from being sent. It's also possible that the ADB connection has flaked out, perhaps due to a bad cable.

There's a security policy update that makes it impossible to execute this from /data/local/tmp - if that's been applied to your phone, you can't get Saferoot to work.
[Verizon Samsung Galaxy S 4] k1mu:
That's the fix - after you add

mount -o remount,rw /system

before the chmod, as jmjoyas suggested.

However, I'll bet that you'll be able to remount OK, but the chmod will fail. That's a symptom of a SEAndroid policy denying you the ability to have a working /system/xbin/su

If it's a policy issue that's denying you from changing the "su" binary to enable root, the only way to fix it is to re-flash a "no-wipe" factory image to get back to the initial security policy files.
[Verizon Samsung Galaxy S 4] Trak-X:
Allow me to disagree.

Running it right now with seandroid disable as i told him and no issues with su on MK2.

once he does "chmod" he will be able to run su without any issues.
[Verizon Samsung Galaxy S 4] gothicasshole:
The only thing you need kies for is to download the drivers off of it then exit out of kies entirely revolk your settings then unplug the phone plug it back in open the root.bat and yes disable windows defender it sees these files as unsigned therefore a threat when I do stuff like this firewalls anti virus are off keep it in MTP mode do not access the camera mode and you should get a dialog pop up to use adb you might be like me and have to extract the adb and adb USB files Into your windows folder as it seems the root installer isn't accessing adb the simple way to test this is to have your phone plugged in type in cmd in your search bar and type in adb devices if you get errors your computer isn't registering adb just open up a new folder on your c drive from computer and copy and paste them give administrative permission and boom

---------- Post added at 07:50 PM ---------- Previous post was at 07:38 PM ----------

He might have that adb issue I had couldn't use it until I installed it into my windows folder making it a system executable command

---------- Post added at 07:57 PM ---------- Previous post was at 07:50 PM ----------

Dial *3282# (data) send you get a text of your data use
[Verizon Samsung Galaxy S 4] k1mu:
"MK2" - I assume you mean AT&T MK2.

On a VZ MK2 it is not possible to disable SEAndroid. It's in enforcing mode all the time because the kernel ignores the selinux enabled flag.

Oh, you can easily turn the enforcing flag off, but that does almost nothing as most of the time it's not read.

I'm assuming that the AT&T MK2 kernel is similar. (Built with SELINUX_ALWAYS_ENFORCING defined.) If I can find the i337 kernel source, I'll verify.

So, to explain what I said and why I said it: there are security updates for some devices that reject any attempt to setuid the su binary as root. If you can chmod it, why didn't saferoot do that? The installer chmod's /system/xbin/su TWICE - once before reboot, and once after. I don't think doing it a third time is going to be any different. However, I could be wrong and would in fact be happy to be wrong. Otherwise, the downgrade is the only way to get there.

Edit: I see that you're running an i545, so not AT&T. Your kernel won't allow you to actually disable SEAndroid.
[Verizon Samsung Galaxy S 4] k1mu:
That's your antivirus getting in the way - rejecting executing a file downloaded from the Internet. There's probably a way to override that, or, as you did, copy the files somewhere else to trick the AV.
[Verizon Samsung Galaxy S 4] AndroidCraig:
Okay,

I added the Mount and then did the chmod command. this is the result:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

D:\saferoot\files>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
shell@jfltevzw:/ $ super
super
root@jfltevzw:/ # pm disable com.sec.knox.seandroid
pm disable com.sec.knox.seandroid
Package com.sec.knox.seandroid new state: disabled
root@jfltevzw:/ # mount -o remount,rw /system
mount -o remount,rw /system
root@jfltevzw:/ # chmod 6755 /system/xbin/su
chmod 6755 /system/xbin/su
root@jfltevzw:/ # reboot
reboot

D:\saferoot\files>

Rebooted and failed root test in ESFile Explorer and Ti Backup.

So where do I find this "No Wipe" Factory image?
[Verizon Samsung Galaxy S 4] AndroidCraig:
Never mind found them. So I just Load the No wipe factory image via ODIN and Then try safe root all over again right?
[Verizon Samsung Galaxy S 4] pckarma112:
Security Update?

I just bought a used s3 off Craig's for my son. The bad news its on 4.3. Is there any way to check phone to see if it has this security update? Anything to look at and indicate it does? Thanks.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Honestly, this isn't the place for that, I don't mean to sound :selfcensored: but this is a question for the Q&A board for your carrier specific S3

This is the VZN S4 board, and while yes saferoot works for many devices, K1MU can't be held responsible for moderating questions on every supportable device.
[Verizon Samsung Galaxy S 4] pckarma112:
lol

It was related to the post above. It took longer to say all that than a simple no. Honestly. Its all good..
[Verizon Samsung Galaxy S 4] ibizapower2003:
I tried to root my note 3 with baseband version n9005xxudmj7 but isnàt working..

someone had tried?

can u help me please? thank you
[Verizon Samsung Galaxy S 4] JerryGNYC:
There will not be anyone ABLE to help you UNLESS you tell us what is wrong (the more detail the better). Screenshots and/or a copy and paste of the output from the process (in the command shell window) would be Really Nice to have...
[Verizon Samsung Galaxy S 4] Numero17:
Also for me he didnt work
[Verizon Samsung Galaxy S 4] JerryGNYC:
Please read my post, just before yours...
[Verizon Samsung Galaxy S 4] k1mu:
That's right - re-flash the no-wipe in ODIN and give it another try.
[Verizon Samsung Galaxy S 4] Numero17:
i read but on my note 3 lte it doesn't work
[Verizon Samsung Galaxy S 4] k1mu:
As has already been asked, do NOT post just a "it doesn't work".

Before anyone can help you, we need to know what device you have (model), build number, and what happened when you ran Saferoot that caused it to fail.

Almost guaranteed: Saferoot says "this device is not supported".

That means, unsurprisingly, that your device is not supported by Saferoot. Your device has been patched to fix the flaw that Saferoot uses, and until a new kernel root flaw is found, you can't use Saferoot.

You will have to find another rooting technique for your device.
[Verizon Samsung Galaxy S 4] Numero17:
i have note 3 sm-9005 with mj7. I try to install this saferoot but supersu tells me: install manually because i update 4.3 my bootloader is locked
[Verizon Samsung Galaxy S 4] k1mu:
I can't help you until you provide the COMPLETE error message, where it came from, what you did to cause it.

I think what you're saying is that when you open SuperSU, it tells you that it is unable to update or install the "su" binary.

If that's the case, then you've got a SELinux/SEAndroid policy on your tablet that is blocking programs from setting root permissions on su. You won't be able to root that unless you can downgrade to an older version with a less restrictive policy, or unless I can find a way around that.

What happens on your tablet if you use "adb shell" to open a shell prompt and type "super"? (no quotes, all lower case).

I've got a few ideas you may be able to try if you have some root access.
[Verizon Samsung Galaxy S 4] AndroidCraig:
That did the trick. Now I am rooted again. Thanks.

One last question, am I now able to try out different roms via safestrap?
[Verizon Samsung Galaxy S 4] Numero17:
i can't downgrade firmware. if i try to root knox go 0x1
[Verizon Samsung Galaxy S 4] storo1975:
what would cause a device to be stuck on your phone is detected and ready for unrooting when running the unroot.bat?

its been on that screen for about 5 mins now
[Verizon Samsung Galaxy S 4] k1mu:
Good. Be careful not to take any further security updates!

Yes, you're all set to install Safestrap and start installing ROMs. Enjoy!
[Verizon Samsung Galaxy S 4] k1mu:
Well, I don't see much choice. Either someone with your device works with me to find a way to make this work, someone sends me one to play with, or you'll need to use CF-Root.
[Verizon Samsung Galaxy S 4] Numero17:
i don't want grows up knox. i want root with knox 0x0
[Verizon Samsung Galaxy S 4] k1mu:
Do you see the "[*] Sending files to your device ..." line as well?

If not, kill it using Control-C and try again.

If yes, and it's hanging after it starts sending files, look at the phone. Do you have any Knox warnings showing up?

It may be that you've got a bad cable, as that's the point where it's pushing a few fairly large files.
[Verizon Samsung Galaxy S 4] storo1975:
d-oh ... it was the bad cable. didnt even think of that.

it worked

you guys are friggin awesome. thanks for the help
[Verizon Samsung Galaxy S 4] Numero17:
Yes program tells me :sending files but then it fails and on my notw 3 there is supersu. There is not warning of knox
[Verizon Samsung Galaxy S 4] mezo91:
i want to safe root my i9506 but it says unsupported :( any help please?
[Verizon Samsung Galaxy S 4] k1mu:
I've answered this several times over the last few days. Please read the last 20 messages or so.
[Verizon Samsung Galaxy S 4] mrctony:
thanks

Root sprint gs4 mk2.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Un=Not thus it mean you cannot root with this method (I think it's pretty self explanatory but...)
[Verizon Samsung Galaxy S 4] viktorak:
Hi,guys,should this work on SGS 9305 latest 4.3.I mind safely with no Knox tripping?!:laugh:
[Verizon Samsung Galaxy S 4] mezo91:
ok tell me how to root with safe root then.
[Verizon Samsung Galaxy S 4] dbpaddler:
I don't think you're getting it. You need to find another way since this one won't work. Try googling your phone model and root.
[Verizon Samsung Galaxy S 4] k1mu:
I've added an explanation to the original post.

If the output from Saferoot has

Then you can not use Saferoot to root your device unless you can install a different kernel that has the flaw which Saferoot exploits.

Until a new kernel defect is discovered, there's nothing that can be done to Saferoot to make it work on your phone unless you can downgrade the kernel.
[Verizon Samsung Galaxy S 4] k1mu:
Please read the original post. As it says, using this will never set the Knox Warranty Void flag.

It may not WORK on the 9305, but it won't trip Knox. Please give it a try and report the results.
[Verizon Samsung Galaxy S 4] joderme:
Next order of business is to see if this will work on the SGS5. I am guessing they have patched the exploit.
[Verizon Samsung Galaxy S 4] k1mu:
Given that there are patched releases already out there for the SGS4, I think there's very little chance the S5 will be vulnerable.
[Verizon Samsung Galaxy S 4] joderme:
Yup no question unless there was a gross mistake...

I hadn't realized there were patched releases.
[Verizon Samsung Galaxy S 4] mezo91:
There is only one method which trips knox and I dont want it. Kingo amd safe root dont work.

When I flash any stock rom from sammobile rather than the singapore one I always get fail invalid ext4 I dont know why. The fail is after hidden. I want to flash Australian rom bcuz this current rom doesn't have lte support