yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] k1mu:
You can get an updated modem from this thread.

However, it's not clear what you're asking. If you're on a MDK bootloader with a loki'd recovery, then you should be able to flash a 4.4 ROM.

If you're having problems doing that, you should ask in one of the 4.4 ROM threads.
[Verizon Samsung Galaxy S 4] azuziel:
my device status is official and i have busy box. wanam xposed worked to restore my ota updates.

the play store version, not the xposed module zone (I imagine same thing, but I've always used separate wanam xposed, not module).

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] pmkool:
i9500 on mk9 supported, ?? will it trip knox??
[Verizon Samsung Galaxy S 4] k1mu:
1. Read post #1 - it has the list of devices that have been reported to me.

2. READ POST #1. Please tell me what it says about Knox. :mad:
[Verizon Samsung Galaxy S 4] social-design-concepts:
My device is a Dell Venue 7 Intel Clovertral-Plus SOC it looks as if this exploit will work for my device but i haven't figured out how to build it for android yet.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0038

https://github.com/saelo/cve-2014-0038

or apply it safe root.
[Verizon Samsung Galaxy S 4] k1mu:
This is a flaw with handling of 32-bit system calls on a 64-bit operating system. There's no way to exploit it on a 32-bit only OS, such as Android.
[Verizon Samsung Galaxy S 4] social-design-concepts:
well that sux it's why i posted here i thought i that on one of the other explanations of this exploit that it could be used on 32bit, i read that this affected all kernels back to 3.4 as long as CONFIG_X86_X32=y flag was set at build so i thought since the clovertrail-plus atom was considered an X86_32 and not an i386 that it might be possible to port this exploit since it looks as if this flag is set in the default config for the clovertrail.

see this

http://www.exploit-db.com/exploits/31347/

from above

same principle will work on 32bit but I didn't really find any major

distros shipping with CONFIG_X86_X32=y
[Verizon Samsung Galaxy S 4] k1mu:
You're right - this isn't the 32-bit compatibility layer for 64-bit systems. It's a different ABI that allows a 32-bit program running on a 64-bit CPU to use more of the CPU resources while still using 32-bit pointers and a 32-bit address space. See Wikipedia for a full explanation.

So, if your kernel is built with CONFIG_X86_X32 enabled, it's quite possible that this ABI is enabled and exploitable. However, there's no good reason for it to be included in an Android device.

If you can get the kernel source for your tablet, you'll be able to tell if it was compiled with CONFIG_X86_X32 enabled. However, I consider that to be pretty unlikely. However, it it's enabled, then it's possible to modify this exploit to work on a 32-bit only system.
[Verizon Samsung Galaxy S 4] social-design-concepts:
its in the default ctp_deconfig from the Dell source code well at least on the kernel source provided for the 4.2.2 no source released for the 4.3 kernel as of yet. it still remains after i apply the android deconfig scripts intel-ia has in their source.

im not sure how to port it for 32bit. it be nice if once i figure out how to exploit it on my device to swap the exploit out in saferoot to use it to make it easier for other users with these intel based 4.3 tablets to root.

i like to apologize to the people in this form i know this device is not your family of devices but there dosn't seem to be to many devs working on the Intel based tablets as of yet so when i find something interesting i have to ask where i can.
[Verizon Samsung Galaxy S 4] JerryGNYC:
If k1mu doesn't mind, I don't... :cool: Good luck with your exploit-hunt! :good:
[Verizon Samsung Galaxy S 4] k1mu:
No problem. Unfortunately, I don't have the device so can't easily test anything. There's a native development kit for the x86 that's published by Intel, so it should be possible to write an exploit there.

However, there's a good chance that an x86-compiled version of Saferoot will work for you. Let's give this a try.

If you're willing to try an x86 version of Saferoot out, here's your chance.

Unzip the attachment. There will be a single file called "getroot".

Using adb, try the following:

adb push getroot /data/local/tmp/

adb shell chmod 0755 /data/local/tmp/getroot

adb shell /data/local/tmp/getroot

You can push the getroot binary to your tablet over a USB media connection as well.

Then, using Terminal Emulator

cp getroot /data/local/tmp/

chmod 0755 /data/local/tmp/getroot

/data/local/tmp/getroot

Please give it a try. I'll bet that it gives you temporary root. Permanent root from that point is a piece of cake.

[Edit: removed the attachment as it didn't work.]
[Verizon Samsung Galaxy S 4] social-design-concepts:
C:\Users\Administrator\Downloads>adb shell /data/local/tmp/getroot

ro.build.product=thunderbird

ro.build.id=JSS15Q

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed.

i had to switch back to windows i had to restore my old windows image because of an issue with fastboot and these devices on linux, im in the middle of redoing my linux android setup on my linux dual boot guess ill compile the kernel from Dell's source to see if i can use the generic address in syatem.map.
[Verizon Samsung Galaxy S 4] k1mu:
Damn. Worth a try, I suppose, but frustrating. Well, I guess some small bit of good news: it's possible to build for your platform and get it to execute. :)

Now I'll have to think about how to port the existing exploit to 32-bit and test.
[Verizon Samsung Galaxy S 4] social-design-concepts:
thank you for your assistance ill be compiling the kernel per Dell instructions what address does getroot need to run. i should be able to get these from the system.map file after the kernel is built i was told well at least generic addresses?
[Verizon Samsung Galaxy S 4] k1mu:
Apparently your kernel is patched to fix the flaw that getroot uses.

To use the CVE-2014-0038 exploit will require several kernel addresses - ptmx_fops, tty_release, commit_creds, and prepare_kernel_cred.

You may be able to get those from your own kernel build, but my experience is that isn't very reliable.
[Verizon Samsung Galaxy S 4] social-design-concepts:
Thank you again for taking some time out and looking at that.

JCase rooted a couple of the Venue8s but his been focused on family stuff and other stuff. May be I can plea to one of the lucky who got root for the need address.

Guess its time to research reworking the exploit for x86 my coding is limited to the allwinner a10 fixing merge cinflits and porting from 4.1.2 to 4.2.1 but I'm sure I'll figure it out.

Thank you all again I'll let you know how it goes.
[Verizon Samsung Galaxy S 4] k1mu:
If there's a flashable recovery image you should be able to extract the kernel and use that to find the addresses.

Converting the exploit to 32-bit is going to be rather difficult. It takes advantage of the fact that pointers are 64 bit wide and start with 0xffffff.

I'm going to write a simple test program to see if the X32 ABI is available on your Venue8, since if not, there's no point in re-tooling the exploit.
[Verizon Samsung Galaxy S 4] k1mu:
Bad news. A simple test program on my GS4 fails since you don't have permission to bind() a socket unless you're root.

That's the SEAndroid security policy getting in the way.

Now, it's possible that your device doesn't have a highly restrictive policy like mine. The attached zip has a simple test program that won't get you root, but does try using the X32 system call. As before, push it to /data/local/tmp, chmod 0755 /data/local/tmp/x32test, then /data/local/tmp/x32test

If it's working properly, it should hang waiting for traffic. PM me with what happens and we'll go from there.

Edit: This doesn't work, giving a "Function not implemented" when calling the X32 ABI system call. That means that the support isn't available.
[Verizon Samsung Galaxy S 4] :
Please update first post as International S4 MH8 does work :D
[Verizon Samsung Galaxy S 4] gui.zanotelli:
Ok, so I have a GS4 i9505, MKE and I ran the bat file as said in the instructions and I got that a similar message to the one above:

ro.build.product=jflte

ro.build.id=JSS15Q

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed.

Tried doing what was said here

And got the same message at this command: "adb shell /data/local/tmp/getroot"

I already tried updating adb from SDK, putting the zip files on the C:\ directory and running the bat file as administrator. Did a lot of reading but it was no use...

Can anyone help??
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
The exploit is incompatible with your device, it says so directly in your quoted code
[Verizon Samsung Galaxy S 4] gui.zanotelli:
Than why is my phone (International Galaxy S4 i9505 MKE) listed as reported success?
[Verizon Samsung Galaxy S 4] JerryGNYC:
Did you use the zip from the first post, or a page or two ago?
[Verizon Samsung Galaxy S 4] gui.zanotelli:
The zip of the first page. I didn't see any other one.
[Verizon Samsung Galaxy S 4] k1mu:
Read post #1035. It works on the base build, but security updates can cause it to fail.

The list in post #1 is based on reports from users here. If there's an error, I'll be happy to fix it.
[Verizon Samsung Galaxy S 4] gui.zanotelli:
Ohh, thank's man, really! So if I flash an older Official Samsung ROM, 4.3 there's a chance I can get it rooted?

Btw, how do I buy you a beer? you're defitnely one of the most helpful guys on xda!
[Verizon Samsung Galaxy S 4] pmkool:
it says that knox will not be tripped
[Verizon Samsung Galaxy S 4] k1mu:
Very possible, but be careful. If it's the same build as what you currently run, you should be able to flash it and get yourself back to a rootable state. Just don't try to flash an earlier build as that may soft-brick your phone.

As far as beer is concerned, click the donate button. :)
[Verizon Samsung Galaxy S 4] k1mu:
Yes, it (the OP) does say that. What Saferoot does will not set the Knox Warranty Void flag.

I am NOT going to change the OP to say

This will not trip Knox​

Mostly because some people won't read it regardless of the blinking, underlined, huge font, whatever, and will ask yet again, "will this trip knox"?
[Verizon Samsung Galaxy S 4] pmkool:
sorry friend... :(
[Verizon Samsung Galaxy S 4] goast:
OK guys I'm rooting the Verizon s4 for a friend its on the mk2 so I'll have to use this method to root..could some one point me to a aosp Google edition based ROM I could flash and offer any more insight to what else I might need like what recovery? Can it be gotten from goomanager? Etc...thanks in advance
[Verizon Samsung Galaxy S 4] k1mu:
Please put down the phone and step away.

MK2: using Goo manager will brick it.

Flashing AOSP? will brick it.

Flashing Google edition? Will brick it.

You are suggesting a whole lot of really bad things. Slow down, and read this.
[Verizon Samsung Galaxy S 4] goast:
Thank you so it seems my best course of action would be just to simply root, remove bloat and leave it be correct?

Edit: will xposed modules be OK to use?
[Verizon Samsung Galaxy S 4] Nergal di Cuthah:
Yes
[Verizon Samsung Galaxy S 4] jyazzie110:
Any one try this on the att note 8.0 sgh-i467?
[Verizon Samsung Galaxy S 4] gunniboy:
S4 I9500 MK9 : Didn't get Rooted

I followed your instructions fully. Everything went well. And then this is what displayed. I have tried repeating it several times. Same cycle. What could be the problem? Please help. Thank you.
[Verizon Samsung Galaxy S 4] mielletseed:
Everything went well?

The screen shows your problem: this device is not supported ....
[Verizon Samsung Galaxy S 4] k1mu:
The I9500 with MK1 is reported to work. Apparently MK9 was patched to remove the flaw that saferoot exploits, so there's nothing you can do to make it work.
[Verizon Samsung Galaxy S 4] gunniboy:
Thanks for explaining clearly. I shall patiently wait for some expert to find a solution.
[Verizon Samsung Galaxy S 4] studiorat:
I CAN CONFIRM IT WORKS ON mk2
[Verizon Samsung Galaxy S 4] Gonzalo1987:
It works in a i9506 with Android 4.3 ML1?
[Verizon Samsung Galaxy S 4] Raillery:
Verizon GS3 with 4.3 update

I get error "the program can't start because adbwinapi.dll is missing from your computer"

I have Kies installed...
[Verizon Samsung Galaxy S 4] k1mu:
You've missed something when unpacking the zip file - adbwinapi.dll is included along with adb.exe in the files folder.
[Verizon Samsung Galaxy S 4] gothicasshole:
Heard the new kit Kat update was hitting today (don't pay too much mind to here say) but if they do push it i will loose root correct? And has anyone found an exploit for kit kitkat thatworks with the leaked I

It's?

---------- Post added at 09:54 PM ---------- Previous post was at 09:50 PM ----------

Find it and double click it it should install if not move it to your windows folder so windows will recognise it it's what I had to do but got them from the ask
[Verizon Samsung Galaxy S 4] k1mu:
Yes, you will lose root. No, as far as I know (and I am tracking this) there's no new exploit. If you update to KitKat be prepared to be unrooted for a while.

Moving it anywhere special won't make a difference. As long as the adbwinapi.dll and adbwinusbapi.dll are in the same folder as adb.exe it should work.
[Verizon Samsung Galaxy S 4] Abaddon:
worked on I9505XXUEMKE with CSC of GLB. kept my knox to 0x0 :D
[Verizon Samsung Galaxy S 4] goast:
OK I got a question..I'm going to be rooting a Verizon s4 mk2. When the kit kat update comes up will it need to be unrooted before excepting the ota? I'm not expecting to keep root thru the ota just that root won't stop it
[Verizon Samsung Galaxy S 4] k1mu:
Being rooted will not stop an OTA.

Being rooted and having frozen apps, removed apps, etc. will possibly cause you OTA problems.

OTAs patch the existing files to bring them up to date; if you've changed anything, the patching won't work, so the OTA checks the hash of every file it's going to update before it changes anything. Any altered files causes the OTA to quit.
[Verizon Samsung Galaxy S 4] sportytony:
Thanks so much for this. I am a believer, supporter and follower of xda for years. Just bought 2 s4s at cost to keep data and mk2 worked like a charm on mine (wife won't let me touch hers) and then used hashcodes hack to fix hotspot.
[Verizon Samsung Galaxy S 4] Boombastical:
S4 Mini I9195 XXUBMJ7 Confirmed root

Hi to all Samsung owners,

I just wanted to confirm succesfull root for S4 Mini I9195 with buildnumber XXUBMJ7 - JB 4.2.2 with Knox preinstalled.

Knox still 0x0 and disabled with system status "Custom" .

Out of topic: But also this same S4 Mini was bricked and sended to Samsung repaird service with root and custom recovery on it and with Knox 0x1 and all other notifications was "Custom" and is repaired without any problem from Samsung .

Thanks to k1mu for this method.

Cheers !
[Verizon Samsung Galaxy S 4] shayind4:
It seems that Samsung service centres can reset tripped Knox flag 0x1 to 0x0. How do they do it?
[Verizon Samsung Galaxy S 4] hakisac78:
stupid question?

do i need to unroot, uninstall ss, then take the 4.3 update before i try this root process?
[Verizon Samsung Galaxy S 4] tyson10:
you wont be able to take the OTA if you have ss or root.
[Verizon Samsung Galaxy S 4] k1mu:
Before the OTA will take, you'll need to clean up all of the changes you've made to your phone. This will be a frustrating process as it's really hard to tell what the OTA is complaining about (tiny font, doesn't stay around long).

The best thing to do is to use the "Update to MJ7 and keep root" process. That flashes a clean load of MI1 so the OTA will work.
[Verizon Samsung Galaxy S 4] k1mu:
I've updated the zip in the OP to fix the problem where there were spaces in the path name to the folder where you unzipped it. It should now work regardless of where you unzipped.

I also changed the "install.sh" script into a Unix script that can work for Linux or MacOS, assuming that you have adb installed on your Linux or Mac system.
[Verizon Samsung Galaxy S 4] maniaryan:
Awesome man, so just manually enter the commands for Mac that you mentioned previously? thanks a bunch dude!
[Verizon Samsung Galaxy S 4] DRELUXOID:
There's an install.sh script for use on the mac. I just rooted MK2 successfully on the first try on my mac.

[~/android]$ chmod +x install.sh
[~/android]$ ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---

1559 KB/s (17800 bytes in 0.011s)
2357 KB/s (100452 bytes in 0.041s)
4398 KB/s (1966976 bytes in 0.436s)
3754 KB/s (1109128 bytes in 0.288s)
204 KB/s (629 bytes in 0.002s)

getroot start.
ro.build.product=jfltevzw
ro.build.id=JSS15J
Succeeded in getroot!
Remount success!
Copying files..
Done.. now reboot to enable root!

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

rebooting...
waiting for device...

--- all finished ---
[~/android]$

Notes:

1. You'll need adb. Get it using this tutorial: http://xdaforums.com/showthread.php?t=1917237

2. It's a good idea to set your path for adb in your bash profile (instructions are in that tutorial) (you need to restart terminal for that to take effect)

3. I chmodded the install script +x just in case.

4. When I first ran 'adb devices' it showed my device as unauthorized. To solve this, put your device into camera (ptp) usb mode instead of media mode and that'll prompt you on your phone to authorize your computer. Leave it in camera mode for the root.

Thanks to OP and anyone involved for contributing this root method!!! :) Now it's time to freeze the hell out of the bloat! ;)
[Verizon Samsung Galaxy S 4] maniaryan:
oh so the install.sh is all you need to run? you don't need to follow the instructions on the install.bat?

edit: SO dumb hahah read the .sh and it's got it all done for me! giving it a whirl now!
[Verizon Samsung Galaxy S 4] DRELUXOID:
.bat is for windows.

.sh is for macos/linux/unix.
[Verizon Samsung Galaxy S 4] RGardner:
FYI - Worked fine with ubunbu 13.10 via Wine.
[Verizon Samsung Galaxy S 4] k1mu:
On a Mac, install adb, then just use the "install.sh" in the package in the original post. You'll need to find a *current* adb for OSX.

For example, adb-fastboot-install isn't up to date. Nor is the EasyADB package here on XDA.

When you plug in your phone with whatever adb you choose to use and use "adb devices" and it says that the phone is there but offline, that's because the adb you've installed hasn't been updated to authenticate to the phone.

I've tried four or five different "easy" installers and none of them work.

The best thing to do is to go to https://developer.android.com/sdk/index.html and download the SDK bundle for Mac. Read the "Setting Up the ADT Bundle" directions, and you should be ready to go.

Similar for Linux - install the same package for your OS and you should be able to use the "install.sh" as long as there's a working adb on your OS.
[Verizon Samsung Galaxy S 4] maniaryan:
did you place the files folder in place you set your path for adb?
[Verizon Samsung Galaxy S 4] DRELUXOID:
Yup. Looks like this:

These files are in /Users/username/android/

the line in ~/.bash_profile looks like this:

export PATH=${PATH}:/Users/username/android
[Verizon Samsung Galaxy S 4] maniaryan:
Thank you so much for your help DRELUXOID, i have everything pointed in the right direction i thought but this is coming up...hmm...

--- Samsung i545 VRUEMJ7 Root ---

--- Based on the CVE-2013-6282 exploit by cubeundcube ---

./install.sh: line 8: adb: command not found

./install.sh: line 9: adb: command not found

./install.sh: line 10: adb: command not found

./install.sh: line 11: adb: command not found

./install.sh: line 12: adb: command not found

./install.sh: line 13: adb: command not found

./install.sh: line 14: adb: command not found

./install.sh: line 15: adb: command not found

getroot start.

./install.sh: line 19: adb: command not found

removing temporary files...

./install.sh: line 22: adb: command not found

./install.sh: line 23: adb: command not found

./install.sh: line 24: adb: command not found

./install.sh: line 25: adb: command not found

./install.sh: line 26: adb: command not found

rebooting...

./install.sh: line 29: adb: command not found

waiting for device...

./install.sh: line 31: adb: command not found
[Verizon Samsung Galaxy S 4] DRELUXOID:
Quit terminal completely and open it again to load the adb path.

Test that it's working by typing 'adb devices' into terminal and hitting enter.
[Verizon Samsung Galaxy S 4] maniaryan:
success! thanks again man! time to get crazy!
[Verizon Samsung Galaxy S 4] Mechastomper:
i had to move it as well. script issue i think worked fome from root of the C drive
[Verizon Samsung Galaxy S 4] tech_head:
There is always an unroot method.

Make the system partition read/write and remove the su binary and SuperSu.apk.

Reboot.
[Verizon Samsung Galaxy S 4] dhc1214:
I've rooted a Droid X, a Bionic and this guy once already. This has been by far the easiest root method I have ever came across. Awesome work sir!
[Verizon Samsung Galaxy S 4] fclifton:
Worked great for me with MK2. Thanks!
[Verizon Samsung Galaxy S 4] sirooga:
MK2

Ran perfect for MK2 on AT&T. Thank you :)
[Verizon Samsung Galaxy S 4] Boombastical:
Not at all...

They just replaced a whole motherboard without checking it what was defect. And it wasn't defect at all, just few partitons were messed up due using a Swapper2 and swap partition. Swapper2 formated a wrong partition and that's was all.

Greetz !
[Verizon Samsung Galaxy S 4] shayind4:
Thanks for the explanation.
[Verizon Samsung Galaxy S 4] Boombastical:
You're welcome !
[Verizon Samsung Galaxy S 4] esheesle:
Trying to read through as much of this thread as possible to avoid asking the same questions, so apologize ahead of time if they have been asked.

1) Does this method permanently disable selinux (permissive vs the default mode). Obviously OTA, etc might re-enable but does this weaken the system by default and is it required to leave selinux in that mode or can it be re-enabled after rooting without breaking su?

2) Once completed, can Koush's superuser be installed instead without issue?

Thanks in advance.
[Verizon Samsung Galaxy S 4] k1mu:
There's no way to disable SELinux on recent kernels - the code that checks the enforcing flag is stubbed out to ignore it. I have a program that will set the flag back to "Permissive" on boot, but it really doesn't do anything useful. SELinux hooks the kernel to add enforcement; when I tried to replace those hooks with standard no-SELinux calls, then things start to fail due to the lack of security context. It's not possible to disable with the current applications and libraries.

As far as Superuser versus SuperSU - I don't know. SuperSU has been updated to have a process that runs early during boot that can gain root permissions and pass it to other processes. I don't think Superuser has that capability, which means you'll end up with UID=0 (root user) but confined so that you can't actually do anything useful. To be fair, I don't know that Koush's version works or not on a 4.3 device.
[Verizon Samsung Galaxy S 4] fivedezs:
So if I root but don't freeze our debloat I can successfully accept the ota whenever it comes? Since custom recovery is out is there a way to flash mods?
[Verizon Samsung Galaxy S 4] gothicasshole:
Sadly yes my suggestion to you is to make a back up with titanium then do as you please just be sure to be on the stock rom and go down to the bottom of the list to not installed re install them then run your ota

WARNING NO ROOT XPLOIT WORKS WITHOUT KIT KAT OTA FLASH ONLY IF YOUR COME RAPE WITHOUT ROOT ACCESS
[Verizon Samsung Galaxy S 4] nips1900:
Hi i have a fido I257m android 4.2.2, and it worked well.

thank you