yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] yake:
Failed with a S4 running 4.3 MKE

Failed with a Galaxy S4 I9505 running 4.3 MKE...

Here is the sequence of messages:

[*] 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=jflte

ro.build.id=JSS15J

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed.

[*] Removing temporary files...

[*] Rebooting... Please wait.

[*] Waiting for device to re-appear...

[*] Checking if su is still there

Something has deleted su - looking for the backup copy

The backup is gone too - can't recover!

Press any key to continue. . .

After that the .bat closes and the phone is still missing root. Any tip/idea/suggestion?

Thanks!

Note: I noticed other users with the same phone/ROM version/build being successfull in getting root access on ther phones, so I am surprised with the message informing that "this device is not supported"...
[Verizon Samsung Galaxy S 4] LVGN:
Just want to say thanks. I was able to root without too much an issue. My issues were drivers but I was able to get them downloaded and got Root. Thanks again.
[Verizon Samsung Galaxy S 4] k1mu:
That "this device is not supported" message means that your device is patched. You'll have to find an alternative means of rooting, unfortunately.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Is it me or did the build numbers suddenly splinter after MK2 (and/or between MJ7 and MK2) . Anyone got a list of all the different build mentioned in this thread? There are at least three I think.
[Verizon Samsung Galaxy S 4] jackrabbit72380:
Hmm wish things where not so complicated. the link says it's for VRUEMJ7

I have VRUCML1

?
[Verizon Samsung Galaxy S 4] yake:
Ohh... Those are really bad news... I've just updated from 4.2.2 to 4.3 after reading this topic. I know this isn't your fault, but I am quite regretful for moving from a non Knox rom to a Knox enabled rom. Too bad for me.

Well, moving forward with life: this may be offtopic but I've seen some guys over the net talking about other root methods but I think all of them should have Knox counter flagged, is this correct? Or there are other root methods keeping Knox untouched?

Thanks again!
[Verizon Samsung Galaxy S 4] k1mu:
Which link? Remember that this is a Verizon forum. If you're looking for info on flashing something other than the i545, you should be looking elsewhere.
[Verizon Samsung Galaxy S 4] k1mu:
I agree. I've just added a list of devices that I know about from this thread to post #1.

If anyone sees anything missing or has corrections, please let me know.
[Verizon Samsung Galaxy S 4] shayind4:
Thanks.
[Verizon Samsung Galaxy S 4] bgmg:
MK5

k1mu,

That is really frustrating. You are absolutely right, and I don't know how I missed it. I see it now right in post 1 (http://xdaforums.com/showthread.php?t=2565758) a successful report on Sprint MK5...ugh

I read for days multiple threads including this thread. I did a thread search for mk5, a forum search, a browser search on page....you name name it, I did it...and somehow I still missed it.

Well...what can I say..I'm sorry for the dumb question.

Thanks for the kick in the rump...I added another Thanks.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Seriously, is it that hard for you to read the first post, which actually lists that build as working?!? Come on now.
[Verizon Samsung Galaxy S 4] bgmg:
k1mu,

Hopefully this is a more intelligent question.

Do you know if there is a way to reset the custom flag on MK5 after doing this saferoot? I always like to know that I can get my device back to official if needed.

PLEASE KEEP READING

Three weeks ago (early January 2014), I bought a brand new latest edition ATT S4 with 4.3, I rooted it with your saferoot method (http://xdaforums.com/show....php?t=2565758) and it only tripped the custom flag. It worked perfectly just as stated.

Further more, I then realized that I should not have gone with ATT coverage in my area and needed to get the custom flag reset in order to be able to return it. ted77usa then advised me to do a full unroot in SU and perform his unbrick method in post #3 of the same saferoot thread (even though I was not bricked). I followed his instructions and sure enough, he was right. It worked PERFECTLY. It reset my custom flag back to official and my phone was as good as new. I then returned the phone to the onine store I bought it from and bought a new Sprint S4.

The following is the detailed device information for that ATT S4 with Knox that I rooted and then reset the custom flag:

After using k1mu saferoot method

ODIN Mode

PRODUCT NAME: SGH-I337

CURRENT BINARY: Samsung Official

SYSTEM STATUS = Custom

KNOX KERNEL LOCK: 0x0

KNOX WARRANTY VOID: 0x0

CSB-CONFIG-LSB:0x30

WRITE PROTECTION: Enable

eMMC BURST MODE enabled

After using ted77USA unbrick method

ODIN Mode

PRODUCT NAME: SGH-I337

CURRENT BINARY: Samsung Official

SYSTEM STATUS = Official

KNOX KERNEL LOCK: 0x0

KNOX WARRANTY VOID: 0x0

CSB-CONFIG-LSB:0x30

WRITE PROTECTION: Enable

eMMC BURST MODE enabled

Here is my Current Stock Sprint phone details

ODIN Mode

PRODUCT NAME: SPH-L720T

CURRENT BINARY: Samsung Official

SYSTEM STATUS = Official

KNOX KERNEL LOCK: 0x0

KNOX WARRANTY VOID: 0x0

CSB-CONFIG-LSB:0x30

WRITE PROTECTION: Enable

eMMC BURST MODE enabled

The big question is....Will the same CUSTOM FLAG RESET (unbrick) method work on Sprint S4 phones such as MK5, or can one of you make a similar method (based on ted77usa methods) for the latest S4 Sprint Phones such as MK5 which has all the same flags. currently ted77usa is uncertain whether it would work on Sprint MK5 but thinks it's unlikely.

SPRINT DEVELOPERS AND SENIOR MEMBERS:

Can you please take a close look at this and try to come up with a similar CUSTOM FLAG reset solution for Sprint MK5?

I sincerely hope that spreading this post around will help all of us Sprint S4 users from developers to junior members

Let me end by saying thank you to all you senior members and developers for all your hard work. We can not appreciate you enough.

Any feed back and Thanks(Likes) are always appreciated.

If this is helpful, please add a Thanks.​
[Verizon Samsung Galaxy S 4] wlc108:
First of all, huge thanks to k1mu. This worked great on my SPH-L720T. As for my reply to bgmg:

I'm by no means an expert when it comes to Samsung and the flags.

What I can say is this is what my download screen says after rooting:

PRODUCT NAME: SPH-L720T

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

KNOX KERNEL LOCK: 0x0

KNOX WARRANTY VOID: 0x0

CSD-CONFIG-LSB: 0x30

Note: My device errored out at this stage:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
(kallsyms_addresses=c0aaaca0)
(kallsyms_num_syms=0001742a)
kernel dump...

[*] Removing temporary files...
error: device not found
error: device not found
error: device not found
error: device not found

I then manually followed the batch file from that point and ran all the commands via ADB. Worked nicely.
[Verizon Samsung Galaxy S 4] k1mu:
No problem - that was just added to the first post today. There's no reason to apologize for not reading something I just added. :D
[Verizon Samsung Galaxy S 4] k1mu:
The "Custom" flag is set by a scanner that looks at the content of your phone, searching for anything that's modified or unexpected.

As I've said several times, you have two choices: Rooted and Custom, or not rooted. To clear the custom flag, un-do any changes you've made to the phone (like "de-bloat"), remove busybox, unroot, then reboot. Wait an hour and reboot again. You should no longer have any changes from stock, so you'll no longer be custom. It's easier, if you're planing to return your phone, to just flash a full-wipe factory stock ROM. (Not a "Stock" ROM, but factory stock from Samsung unmodified.)​
[Verizon Samsung Galaxy S 4] bgmg:
Thanks k1mu. Hmmm...That is interesting. When I rooted my ATT GS4 a few weeks ago with your saferoot, I never added anything else to it that requires root (such as nobloat, appquarantine, busybox or anything else). I did a full unroot and never saw the custom flag change back to official. I did several reboot attempts over the next few days and it never returned to official. It always said custom. It was not until I did ted77usa's unbrick method that it switched back to official.

I hope it really is that easy with my Sprint MK5 if I ever want to return it to Official.
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
For goodness sake, he answered you on this a few posts back, if custom doesn't go away do a full wipe either via odin, or my preferred method using the carrier-utility or kies (directly to you he said this about 20 or so posts ago in post 891).
[Verizon Samsung Galaxy S 4] Tada10:
Or use Triangle Away. Gets rid of custom when you reboot.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
It's been mentioned a number of times in this thread that TA has been tripping knox counter (void warranty) so even if getting rid of the cosmetic custom was his only concern (it wasn't) this would be against the spirit of his question (easy returnablity to carrier)

::grumbles about entire thread reading ought to be required::
[Verizon Samsung Galaxy S 4] daniel4653:
Hey I see that you haven't added the Regular Spritn GS4 SPH-L720 on MK2 to the list of confirmed devices after I stated that it in fact works.
[Verizon Samsung Galaxy S 4] nabeelally:
AWESOME!!!!!

Confirm it works on International Galaxy S4 I9500 with MJ8
[Verizon Samsung Galaxy S 4] LinxuSx:
This worked perfectly on my Verizon Samsung Galaxy S3 (SCH-I535) with the 4.3 update. Thank you!
[Verizon Samsung Galaxy S 4] Killberty:
Just use wanam exposed to fake the system status

I am on official, samsung official, 0x0 with root

hit 'thanks' if i helped you

SM-N9005 0x0 X-Note7 ML2

XDA Developers 4 premium app​
[Verizon Samsung Galaxy S 4] bgmg:
k1mu,

Thanks. Sorry I missed it. I'm still human at best. I added some more thanks for you.
[Verizon Samsung Galaxy S 4] k1mu:
That's added now. Thanks.
[Verizon Samsung Galaxy S 4] Ylilataus:
Does this work with build XXUENA4? :confused:
[Verizon Samsung Galaxy S 4] k1mu:
I don't know. You'll have to try it and tell us. :laugh:

Seriously, I've documented most of what's known in post #1.

Give it a try and let us know.
[Verizon Samsung Galaxy S 4] pegasus123:
i have rooted now using saferoot. is flashing cmw recovery via Mobile Odin trip knox to 0x1?
[Verizon Samsung Galaxy S 4] max621:
Yes
[Verizon Samsung Galaxy S 4] pegasus123:
thanks for answer bro :)
[Verizon Samsung Galaxy S 4] k1mu:
Yes, it will trip the warranty void flag. AND it won't work.
[Verizon Samsung Galaxy S 4] decaturbob:
Cwm won't work unless you have mdk base build

safestrap enabled, Hyperdrive driven
[Verizon Samsung Galaxy S 4] ertoalb:
Cant update SuperSU

I run the batch file, all the steps are successful on the command window but in the phone, when I'm on the SuperSu update step it fails, cant update the binary, please restart and try again.. blah blah.. (The screen asking for Normal or CWM/TRWP update), the phone is on stock MK2 (Unlocked AT&T I337), I've tried multiple factory resets and it fails on the same step. :crying:
[Verizon Samsung Galaxy S 4] Ylilataus:
I tried to root my Galaxy S4 I9505 and this is the result:

[*] 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=jflte

ro.build.id=JSS15J

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed.

[*] Removing temporary files...

[*] Trying to disable Knox...

/system/bin/sh: /system/xbin/super: not found

[*] Rebooting... Please wait.

[*] Waiting for device to re-appear...

Something has deleted su - looking for the backup copy

The backup is gone too - can't recover!

I have build XXUENA4. Is it possible to get it working on that build?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
As has been said multiple times, this error means your kernel has been patched against the vulnerability exploited by this method; you will, unfortunately, not be able to root this way.
[Verizon Samsung Galaxy S 4] Ylilataus:
Thanks for quick reply. I hope someone will find a new way to safely root Galaxy S4.
[Verizon Samsung Galaxy S 4] gothicasshole:
This is the root path it should put in ;) so it might help in this long winded debate

Congratulations! You have root access!

Super User Application Status:

SuperSU application - version 1.91 - is installed!

System File Properties for Root Access:

Standard Location

Check Command: ls -l /system/bin/su:

Result: /system/bin/su: No such file or directory

Analysis: File /system/bin/su does not exist.

Standard Location

Check Command: ls -l /system/xbin/su:

Result: -rwxr-xr-x root root 113032 2014-01-27 07:21 su

Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!

Alternative Location

Check Command: ls -l /sbin/su:

Result: /sbin/su: Permission denied

Analysis: File system permissions restricted and denied access.

Alternative Location

Check Command: ls -l /system/xbin/sudo:

Result: /system/xbin/sudo: No such file or directory

Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:

Root user id:

uid=0(root)

Root group id:

gid=0(root)

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:

ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1

Results provided on your SAMSUNG-SGH-I337 device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market - http://goo.gl/NcnHn
[Verizon Samsung Galaxy S 4] pegasus123:
hello not sure what the problem is now im on MKE firmware I9505 model. my root just broke all of a sudden. some root apps do work like droidwall, wanamlite, xposed framework, game guardian. all these works no problem. but now i cant use other root apps such as triangle away, titanium backup, mobile odin. these apps says i have no root? so not sure what is the problem?

the first time i rooted my phone, i was able to run the titanium backup and was able to backup all my files, now it doesnt work. what do i need to check?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Make sure all knox and security policy updating are disabled. Also the first question to ask of any bug is "what changed between working and not working" (new app, updated app, allowing a security policy update to occur).

This is what I mean security policy. Settings>more>security
[Verizon Samsung Galaxy S 4] pegasus123:
i didnt change any that could break my root. i notice in the security settings however is the automatic install of new policy is enabled. might be the culprit, how do i clear its data?
[Verizon Samsung Galaxy S 4] djvita:
ATT S4

rooted now

thanks!!
[Verizon Samsung Galaxy S 4] k1mu:
What you're using to verify root doesn't work on an Android 4.3 system - it never bothers to actually obtain root access then says you're not rooted. Yup, that's a good plan. :)
[Verizon Samsung Galaxy S 4] k1mu:
As already stated, you've probably allowed the vendor to push a SEAndroid security update to your phone.

SEAndroid (SELinux) can deny root access even though you're rooted.

What happens if you open SuperSU? Does it tell you that you're not rooted? if that opens with no complaints but Titanium Backup doesn't get root, I think you've been had by a policy push.

The only way to revert is to flash a factory ROM image. No-wipe ROMs will probably work. Then, don't take any "Security Policy" updates.
[Verizon Samsung Galaxy S 4] pegasus123:
Tnx k1mu. Knox sucks now I need to flash again. Thanks for the help :)
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Before doing that, have you tried revoking a non-working app's root permission in SU and reauthenticated it?
[Verizon Samsung Galaxy S 4] pegasus123:
Actually no, because the non working root apps are not appearing anymore in the supersu permission because I have Uninstall ed them like the titanium backup. On the working root apps and new apps I installed such as terminal emulator root permission access/blocked that easy using supersu. There's just some apps that do not prompt for root access because it's not able to detect my root
[Verizon Samsung Galaxy S 4] brian6685:
I'm on a SGS4, MK2, 4.3.. And when running this, it gets stuck at trying to disable knox.. One time it went through, but when it rebooted, it wouldn't let me install the SU binary because it said it could not disable knox.. Any idea's please?
[Verizon Samsung Galaxy S 4] hiltun:
This worked for my Samsung Galaxy S4 from AT&T.

Model: SAMSUNG-SGH-I337

Android: 4.3

Baseband I337UCUEMK2

Build: JSS15J.I337UCUEMK2

I installed

Kies3Setup.exe then updated it.

Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
[Verizon Samsung Galaxy S 4] k1mu:
Apparently there's some Security Policy update that Samsung/AT&T are pushing onto the MK2 devices that's stopping the su binary from working.

I've tried several remote debugging mechanisms but haven't been able to figure a way around Knox blocking SuperSU.

I keep getting pinged for a security update on my Verizon phone. Accepting that might put me into the same state, but then I'd be un-rooted :crying:

Theoretically using a no-wipe MK2 flash will fix it and allow rooting. You might give that a try.
[Verizon Samsung Galaxy S 4] brian6685:
What do you mean by a no-wipe mk2 flash?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
http://xdaforums.com/showthread.php?t=2578209
[Verizon Samsung Galaxy S 4] brian6685:
Will those Verizon no-wipe's work for my ATT phone?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
http://xdaforums.com/showthread.php?t=2621279

Halfway down the page it has a link for the AT&T S4 index

http://xdaforums.com/showthread.php?t=2616221

Time taken for me to find it at the top of the att s4 forum 20 seconds, time to type this reply 2 minutes. (why'd we have to find it for you)
[Verizon Samsung Galaxy S 4] youngSWi:
metro pcs galaxy s4 4.3

Im trying to root and the script it stuck at "Sending files to your device" for like 20+ minutes.... what should I do?
[Verizon Samsung Galaxy S 4] mades32388:
This worked like a charm - thanks!

Any suggestions for migrating from one Galaxy S4 to another S4 (cracked screen)?

I know there's Titanium Backup and also My Backup - any thoughts. Would love the process to be as simple as possible and try to retain my settings and apps they way they were. I would even love them in the same spots (not sure if that's possible).

Thanks
[Verizon Samsung Galaxy S 4] k1mu:
Something's wrong with the "adb" connection to your phone if that happens. Or, something on the phone is disallowing adb from copying files to /data/local/tmp

What kind of phone, what build, etc. ?
[Verizon Samsung Galaxy S 4] youngSWi:
I restarted the script and my phone is successfully rooted, no flags from 2.3! :)
[Verizon Samsung Galaxy S 4] k1mu:
I've only ever used Titanium for that. The reality is that the Google backup actually works pretty well, with most of my applications and data being automatically moved to the new phone.
[Verizon Samsung Galaxy S 4] dmoney94:
How do i unroot my verizon GS4 MK2?

Ad removing CUSTOM on boot up..
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Post #2

:sly:
[Verizon Samsung Galaxy S 4] dmoney94:
Thanks!

anything easier than that?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Honestly if that's not easy I don't know what is. You used adb to root and the adb is just to remove busy box. The only "easier way" is to unroot via SU and run a WIPE Odin; I've never done this, so don't quote me on that being a full warranty-proof unroot, unlike post #2 which, frankly speaking, is.
[Verizon Samsung Galaxy S 4] dmoney94:
Will Odin wipe it clean with stock Rom?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Please learn to read; I answered that before you even asked
[Verizon Samsung Galaxy S 4] gothicasshole:
If my memory is correct once it disables Knox your supposed to install the binary rite then and look for the si to give permission then it reboots

---------- Post added at 06:04 AM ---------- Previous post was at 06:01 AM ----------

Do you think a custom rom will be triggered? I have knox removed XD IM RUNNING DARK VENOM
[Verizon Samsung Galaxy S 4] mohseen khan:
My mobile have official stock version with knox protected 4.3 , MK9 ...

1) If i saferoot this version it will trrip the knox 0x1 ????

2) If its trrip the knox to 0X1 ..Can i again install the stock version then make it official for OTA update ...
[Verizon Samsung Galaxy S 4] michaelg117:
WIll i be able to run the .bat on ubuntu if i have Wine installed..?
[Verizon Samsung Galaxy S 4] Swimboy46163:
Are you running a virtual machine by chance?
[Verizon Samsung Galaxy S 4] RGardner:
I'm going to give it a try in about an hour...
[Verizon Samsung Galaxy S 4] gunzaa:
I don't know, but I fixed it. Rooted and waiting for custom recovery soon. There is hope!
[Verizon Samsung Galaxy S 4] Swimboy46163:
Not working

Help! It doesnt seem to be working.... Heres what the code turns up. I'm running MK2.
[Verizon Samsung Galaxy S 4] jwhistler:
I'm having the same results, running MK2

---------- Post added at 03:44 PM ---------- Previous post was at 03:19 PM ----------

I ran the commands one by one, copy and pasted from the script to the adb command line and all ran well. The problem is in the system path. There was a time when I could have corrected that, but now it's just easier for me to cut and past the individual command lines :D

My MK2 now has root. THANK YOU!!
[Verizon Samsung Galaxy S 4] Swimboy46163:
Why does that work and not it doing it automatically?
[Verizon Samsung Galaxy S 4] jwhistler:
The script sets the system command path to included the OP folder in the path. That means you can run the command from any location on your computer file structure and it "should" point to the folder with the files. For some reason, the system path didn't work on my computer, so I simply opened the command window from within the OP folder, and the executed each line one at a time. Since I was already within the necessary folder, the needed files where right there. I probably am not explaining this correctly....
[Verizon Samsung Galaxy S 4] Swimboy46163:
For some reason when I click on the ADB application in the files folder it goes ahead and runs a script and doesnt open. Any ideas why?
[Verizon Samsung Galaxy S 4] GoBears:
I was having path issues as well. I put the extracted folder on the root of the c: drive, put the phone on usb camera mode and it ran without a hitch.

Thank you SO MUCH for this. Now rooted on MK2.
[Verizon Samsung Galaxy S 4] jco897j:
Same here. Unzipping to the C:\ root did the trick.
[Verizon Samsung Galaxy S 4] jwhistler:
A humble suggestion that this line be added to the instruction: Then you need to unpack the attached ZIP file to the root directory on your PC
[Verizon Samsung Galaxy S 4] nsciucco:
having issues- any ideas

getroot start.

/system/bin/sh: /data/local/tmp/getroot: not found

removing temporary files...

rm failed for /data/local/tmp/getroot, No such file or directory

rm failed for /data/local/tmp/su, No such file or directory

rm failed for /data/local/tmp/Superuser.apk, No such file or directory

rm failed for /data/local/tmp/busybox, No such file or directory

rm failed for /data/local/tmp/install-recovery.sh, No such file or directory

rebooting...

waiting for device...

---------- Post added at 11:42 PM ---------- Previous post was at 11:11 PM ----------

Figured out . I'm a idiot. Lol
[Verizon Samsung Galaxy S 4] k1mu:
Actually, from a Mac, the best thing to do is to install ADB and use that. The commands in the install.bat are pretty obvious.

i.e. when it says
[MENTION=302893]adb[/MENTION] push %~dp0\files\getroot /data/local/bin

You use

$ adb push files/getroot /data/local/bin

Or, like this:
[Verizon Samsung Galaxy S 4] k1mu:
It's waiting for the device to appear. If you don't have the drivers installed, it'll never proceed.