yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Glynix:
Ok thank you very much k1mu . Everyone im confirming that I was on a verizon samsung galaxy s4 stock mk2, used the most current file in 1st OP, and I am now rooted! Going to try the new beta safestrap with it, load hyper in stock slot, and see if this works. Thanks.
[Verizon Samsung Galaxy S 4] lennie paz:
Is this root the same as I have on my S3? My son has an S4, and wants his phone rooted, but I'm not sure if there are any limitations with this root. Can he do everything I can do on my S3?
[Verizon Samsung Galaxy S 4] Drayk:
Thanks OP for this root method!!!

Is it possible to remove this custom screen (w/an open lock icon) without unrooting? I'd love to get the stock GS4 logo back, but certainly not a deal breaker for me. I'm paying for insurance as well and insurance terms are lost, stolen or broken. I'd need to check and see if messing with the OS or rooting is exempt from coverage. :D
[Verizon Samsung Galaxy S 4] jball:
Exposed or Wanam.

Search the names and you will find what you want

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] k1mu:
That's discussed earlier. Short answer: you can use Wanam Xposed to hide that. Search this thread using "wanam" for more info.
[Verizon Samsung Galaxy S 4] Drayk:
Thanks. Much appreciated!
[Verizon Samsung Galaxy S 4] cameronsutor:
First of all, I may have come across as ungrateful - Thank you for putting this together for us all!

Secondly, I'm not sure it is my zipping/unzipping program. I use WinZip Pro and have never had an issue. That said, I did see all three files in the zipped file (as referenced in the OP), and they were extracted with all of the correct contents, but it just kept telling me that 'files' was an invalid command ... I think it may have said 'adb' at one point too.

Nevertheless, as you said, I was able to get it working. Not without your help and the community here at XDA, so again, thanks.

C

---------- Post added at 03:41 AM ---------- Previous post was at 03:34 AM ----------

I had the same problem. I posted the exact same issue on a post on page 36 or 37, with a workaround that got it working for me. On the post I referenced, on page 36 or 37, I uploaded the .bat file that the OP included in the zipped file, but I changed where the script looked for the file needed for root. Unzip the file from the OP, and put it in the root of your C:, download the file I posted (I would repost it, but it is on my Windows drive and i'm on my Hackintosh build ...) and run it. It worked the first time for me. Or, the OP did say he was uploading the file again, so try that first.

C
[Verizon Samsung Galaxy S 4] k1mu:
No worries. I misunderstood the cause of the problem and eventually realized it was a real problem that I needed to fix.

I've fixed the real cause and made the installer more resilient for what I thought was going wrong, so in the end it's a net win, even if it took a few two-by-fours to the head to convince me that it was something I caused. :)
[Verizon Samsung Galaxy S 4] luis2k10:
Confirmed working on my att Galaxy S4 running mk2. Now to figure out how to sim or region unlock it.

Thanks a million!
[Verizon Samsung Galaxy S 4] rithvik14:
Yes that is what i am talking about...and what recovery is installed with this saferoot method?
[Verizon Samsung Galaxy S 4] AndroidLonghorn:
Still no luck. I tried running the latest version of the files. It now runs though and says:

Succeeded in getroot!

Remount success!

Copying files...

remount: Device or resource busy

Done.. now reboot to enable root!

After it says All Finished, I go to SuperSu and it still says There is no SU binary installed, and SuperSu cannot install it. As always, thanks for the help!
[Verizon Samsung Galaxy S 4] roote223:
If I rooted my Tmo GS4 with this would I be able to return to the official status and without the knox counter being set off? And can someone post a video on how to do this? Thanks.
[Verizon Samsung Galaxy S 4] cammykool:
So bean's S3 is dead?
[Verizon Samsung Galaxy S 4] munkie013:
Just wanted to say I followed this method on my T-mobile GS4 with the latest OTA (MK2) and it worked like a charm. Have SU and no flags were tripped. I do have a question though. I opened the su app after and it said Knox may interfere with how it works and asked if I wanted to disable it. I hit yes and it said it was successfully disabled. Does this mean I'm free to flash a custom rom without tripping the Knox flag?
[Verizon Samsung Galaxy S 4] jball:
If you noticed as you bring up Odin mode you will still see the "knox " warranty 0x0, I believe if it's still there it can be tripped.

I "dd" disabled my knox and still shows in Odin mode.still be careful

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] WordsworthESP:
I'm not sure if you've gotten it working or not since this post, but I had a similar problem. Knox blocked some part of the rooting process before SuperSU was able to block it, so the result was partial-root. Specific apps could acknowledge it, I'd get SuperSU requests, but nothing could actually use it and even ES File Explorer couldn't engage it's Root Explorer.

I had to unroot, reboot and run it again, now everything's working perfectly. Even got V4A working (I missed a line edit on build.prop.)

This may or may not help, as the files have changed a bit since I rooted. I suggest trying the unroot process before possibly anything extreme. I thought I was going to pull all of my hair out that night until I got it working. :)

Sent from my AT&T Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] k1mu:
No recovery. You can't install custom recovery on the phone that this was developed on (Verizon GS4, Android 4.3).
[Verizon Samsung Galaxy S 4] Craleb:
Ok I don't know what I did (my debugging mode is being retarded) but adb went trough for the second time and I now have custom boot screen. But when I open SuperSU I get "no binary installed this is a problem"
[Verizon Samsung Galaxy S 4] Surge1223:
Now try the script in terminal. Then type su at the end
[Verizon Samsung Galaxy S 4] Craleb:
--- Samsung i545 VRUEMJ7 Root ---

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

waiting for device...

1738 KB/s (17800 bytes in 0.010s)

2452 KB/s (100452 bytes in 0.040s)

1790 KB/s (1966976 bytes in 1.073s)

2762 KB/s (1109128 bytes in 0.392s)

getroot start.

ro.build.product=jfltevzw

ro.build.id=JSS15J

Succeeded in getroot!

Remount success!

Copying files..

Error opening /data/local/tmp/install-recovery.sh for read: No such file or dire

ctory

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 ---

Press any key to continue . . .

^^^^that is what my command promt says. also i can now type su and it works ( i think( it desnt say su doesnt exsist)) but my supersu still cannot install
[Verizon Samsung Galaxy S 4] Craleb:
Before when I typed su it would say it didn't exist or something.. so getting closer!
[Verizon Samsung Galaxy S 4] Surge1223:
Look at my pic. Do you have a # instead of $ like the last two lines in my pic? If so you have root.
[Verizon Samsung Galaxy S 4] Cdubzz20:
In the file he linked, it doesn't have SuperSU like he states, it has just Superuser.apk
[Verizon Samsung Galaxy S 4] Craleb:
Still $ :(

But hey thank you very much for helping me I know you don't have to. But I really appreciate it. It's guys like you that keep this community going
[Verizon Samsung Galaxy S 4] k1mu:
Rats. That means that the terminal emulator user that you're getting doesn't have permission to write to /data/local/tmp

I used the "adb" method to root mine, and assumed that the alternate method would work, but perhaps not.

Let me think about this - I can include the adb program into the installer, I suppose, to allow everyone to use it.
[Verizon Samsung Galaxy S 4] Craleb:
Thanks [MENTION=3940199]k1mu[/MENTION] but I have also done the adb method. I posted what it says when I do it a few posts back, in text.

It did give me the custom boot screen and SuperSU app but still don't have root?
[Verizon Samsung Galaxy S 4] Cdubzz20:
That would make it a lot easier, My computer seems to be having an issue making the bridge from your script running through ADB
[Verizon Samsung Galaxy S 4] Surge1223:
I see the problem. Try this, connect to pc open command prompt. Make sure you have adb installed correctly (add it to your path) if you get no errors during the following commands thats good.

cd C:\path to mj7root folder

Then

adb devices

adb shell

adb push files\getroot /data/local/tmp/

adb push files\su /data/local/tmp/

adb push files\SuperUser.apk /data/local/tmp/

adb push files\busybox /data/local/tmp/

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

adb shell "chmod 0755 /data/local/tmp/busybox"
[Verizon Samsung Galaxy S 4] Tada10:
Can you help him redo the install.sh also please?

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] k1mu:
The program says:

Error opening /data/local/tmp/install-recovery.sh for read: No such file or directory

That's my mistake - too many edits to the scripts. I've fixed this and will update the original post in a minute or so.
[Verizon Samsung Galaxy S 4] Cdubzz20:
So all I should need to do is replace the old file with the new one and repeat the steps? Or would it be better to use my computer

Edit: I'm on MJ7
[Verizon Samsung Galaxy S 4] hakisac78:
should i update?

I'm on me7 and want to get rls 11. should i do this update then wait for ss 4.3? then flash rls11? any input would help!
[Verizon Samsung Galaxy S 4] Tada10:
Didn't work on mine :(

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] k1mu:
Hopefully. I just re-uploaded the .zip file in the original post. The install.bat and install.sh now push the install-recovery.sh file that's required to make this work.

Sorry - making something that's usable once into a more robust technique is a bit of a learning curve for me. :)

I'm hoping that this can be made to work without requiring ADB to be installed, but we'll see.

Maybe putting the files onto an exFAT sdcard will fix the permission problems - my external sdcard is formatted ext4 because I want the quick recovery that exFAT won't give me.
[Verizon Samsung Galaxy S 4] k1mu:
What format is your sdcard?
[Verizon Samsung Galaxy S 4] Tada10:
It's Exfat see screenshot

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] k1mu:
No. You disabled the active, running on the phone portion of Knox. The bootloader still looks for attempts to flash custom ROMs and will still set the Knox Warranty Void flag. As I said in another thread about this, "Knox" is an umbrella name for a series of different protection mechanisms. Some of those (Knox on the phone) you can stop. Others, like SEAndroid, and the warranty flag, and the real-time integrity checking, you can't stop or avoid.
[Verizon Samsung Galaxy S 4] k1mu:
I've seen the "remount... busy" thing, Seems to be something not synching properly, but I'm not sure why it occasionally happening. It could be Knox, for all I know.

Did the phone reboot after the "now reboot to enable root!" step? You won't get root access until that's done.

If you're willing to try a few things using "adb shell", please give these a try. You can get adb access to your phone from a command prompt (start/run cmd), cd to wherever you unpacked the zip, then "files\adb shell" to get a shell prompt.

Please try the following and let me know what output you get.

$ ls -l /system/xbin/su

$ ls -l /system/xbin/daemonsu

$ ls -l /system/etc/install-recovery.sh

$ cat /system/etc/install-recovery.sh

$ exit
[Verizon Samsung Galaxy S 4] decaturbob:
your only option will be safestrap once hashcade releases the final version. Its in beta testing phase right now and some people are reporting success in loading HD11 into the stock rom slot only. Give it another week or two.

This will be, most likely, the only avenue for GS4 owners who don't have a MDK base phone. Custom ROMS will have to be based off the TW stock kernel, no CM or ASOP. Right now Hyperdrive 11 is working with safestap beta
[Verizon Samsung Galaxy S 4] Drayk:
Thanks so much for the assistance. I've done a search, found the app, read all I could, but there is no real explanation on how you regain the stock startup screen. I've emailed the Dev, as well. I seriously don't want to be a BIG PITA but, do you possibly have a 15 second explanation on how this is done???? :confused:

Any assistance is greatly appreciated :good:
[Verizon Samsung Galaxy S 4] k1mu:
In Wanam: Security Hacks, Fake System Status.
[Verizon Samsung Galaxy S 4] Trak-X:
If you want to take the phone back to Verizon, ATT or Tmo or others, you have to reflash to stock, to remove the Padlock and also root.

If you just want to remove the Padlock but keep root, this is just for your well being, install Xposed Framework, Then Wanam, and then, in Wanam, Security Hacks, Fake System Status.
[Verizon Samsung Galaxy S 4] Drayk:
Thanks guys....

I'm not really concerned about returning the device. I suppose I could always download an unroot app. I'm just not too keen on the custom startup screen, but I'm not neurotic about it either. I wanted to crack the nut mainly to get free wifi hotspot and weed out some of the dead wood.

Thank you all again for your kind assistance.

Happy Holidays to you, and to the entire XDA Nation!!!!
[Verizon Samsung Galaxy S 4] Parafly:
Hey guys just warranty exchanged my MDK for the new MK2. Rooted with one-click. Can I just install goo manager now? I don't really need custom roms but I do want to do a few things to the phone (change notification bar, remove wifi notification, etc)
[Verizon Samsung Galaxy S 4] Sniper_5:
No custom recovery for MK2 yet
[Verizon Samsung Galaxy S 4] tailgunner9:
Root 4.3 OTA MK2

Seems the file on page 1 to root still has Problems from what I am reading. Think he may need more research to get it working OK. What do you think???? I am wanting to keep stock recovery and stock rom. AT&T Galaxy S4, has anyone had trouble getting root with file on this phone??
[Verizon Samsung Galaxy S 4] jcwulf:
Took OTA of MK2...Didn't lose root

Just an FYI.

I was rooted with MJ7 and I didn't have any apps frozen with Titanium. I have found lately that the option to disable apps in the Samsung menu has been enough for me in dealing with bloatware. Yes, they are physically still there but they are not taking up RAM or using airtime whether wifi or 4g.

The only real mod I have is a change in the "feature.xml" doc where I enable the shutter sound option in the camera so I can turn it off (it annoys me).

In any case I gave the OTA the "go ahead" and it installed just fine and to my surprise I didn't lose root!

BTW...Thanks XDA geniuses for all your help over the years with my HTC incredible, galaxy tab 7, SG S3, and now my SG S4!
[Verizon Samsung Galaxy S 4] k1mu:
I'm not aware of any problems at the moment. There's a few people who have had to flash this more than once to get it to work, but most people aren't seeing that. So, at the moment, it's working fine for most people.

Once I get some information on why some are having problems, I may be able to adjust the script to compensate. However, there's no reason not to try it. The worst that can happen is that you won't have root when you're done.
[Verizon Samsung Galaxy S 4] tailgunner9:
Root OTA 4.3 Update

Thanks for reply k1mu. Will give it a try then on my stock MK2 SGH-i337. Will let you know how it goes.
[Verizon Samsung Galaxy S 4] jimbob_sf:
On MK2. I rant the .bat and it appeared to work. I had root. I rebooted and it went away. Now, when I try to run the .bat again, it reports errors after the "installing busybox" section. i'm running a cmd window as Admin on Win 8.1. I have Kies 3 freshly installed.

It reports "device not found" 5 times once it reboots and runs these commands from the .bat file. I stopped the program in between the reboot and busybox install (lines below) and adb shell won't let me get su. That may explain why the commands fail. So, I had root, it went away, and I can't seem to get it back. What do I try next?

files\adb shell "su -c mount -o remount,rw /system"

files\adb shell "su -c chmod 6755 /system/xbin/su"

files\adb shell "su -c chmod 6755 /system/xbin/daemonsu"

files\adb shell "su -c /system/xbin/busybox --install -s /system/xbin"

files\adb shell sleep 15

files\adb shell "su -c mount -o remount,ro /system"

Suggestions?
[Verizon Samsung Galaxy S 4] swc2001:
Getting concerned!!! trying to Root MJ7

I did this:

"When adb first connects to your phone, it will display a dialog box reading "Allow USB debugging?"

You may need to turn on your phone to see that. Tap on the "Always allow from this computer" checkbox to enable it, and tap "OK".

There are cases where people can't get the connection working unless they toggle the USB connection type from Camera to Media and back. Perhaps that may help getting it to work."

afterwards nothing happened!! it is just sitting there. What do I do?

how long should the root take?

:edit Reinstalling drivers and going to try again.

any help would be appreciated.
[Verizon Samsung Galaxy S 4] tailgunner9:
Root 4.3 MK2

k1mu says to just click install on the .bat file. You mean we just connect phone to Windows PC with USB cable and click on .bat file to install?? No using Odin and .bat file in PDA? Confused!!!

swc2001 are you trying to do this on AT&T Galaxy S3?
[Verizon Samsung Galaxy S 4] swc2001:
No I am trying to do it on a Verizon SGS4

I reinstalled the drivers that k1mu gave us..... unfortunately the phone is just sitting there

I wish I knew how long the process was supposed to take.... the computer was doing some heavy growling but now is going very slow. phone has NOT rebooted yet.

from what I understand that should be the process.... plug it in and click install......

Still No Joy!

Man I wish K1MU was around!!
[Verizon Samsung Galaxy S 4] tailgunner9:
That is what k1mu says is just click on file to install. I was always use to doing it thru Odin and put file in PDA section. Maybe he will Clear it up for us. I want to try on my AT&T S4
[Verizon Samsung Galaxy S 4] swc2001:
I hope so Cause I am running naked with No Root and No Safestrap!

---------- Post added at 03:06 PM ---------- Previous post was at 02:59 PM ----------

Soooo I just tried it again.... I didnt do anything different and it worked perfect.

For whoever wants to know.... the process didnt take over 2 minutes. :D

Thank you K1MU

WHERES THAT DONATE BUTTON BRO!!
[Verizon Samsung Galaxy S 4] tailgunner9:
Root MK2

Did you just plug phone into USB on PC and Left click on the batch file and it starts installing??? No Odin??
[Verizon Samsung Galaxy S 4] swc2001:
That is correct.... I did reinstall drivers and kept flipping back and forth between mtp and ptp like k1mu said in original post.... I also restarted the computer and the phone...... so try all of that.... No Odin to use this Root!
[Verizon Samsung Galaxy S 4] jvnat:
This worked for my ATT S4 after some work. I uninstalled Kies 3 and used the Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 to install the drivers. I also had to jump between USB Media and Camera mode. I made sure to install the drivers using the Run as Admin for Windows 7. I also ran the install.bat file using Run as Admin. But it worked. Thanks!
[Verizon Samsung Galaxy S 4] decaturbob:
adb is built into his bat install file and he has included adb.exe in the zip....so no odin here to do
[Verizon Samsung Galaxy S 4] jimbob_sf:
Update (no better): I removed all the stored credentials so ADB would try to ask for access again (it did and I gave it), removed FoxFi which was forcing a lock screen, and anything else I could think of that would cause boot issues. No change. Here's what it's doing:

The script appears to run fine up until the busybox section. When it reboots as the script says, the script sees the device just as the white Verizon screen appears. Once the home screen renders and settles for a second, it reboots again. (It does this extra reboot after every boot now - not just when running the installer). When the white Verizon screen comes back and the pc "sees" the phone again, the busybox section picks up and spits the error codes.

There are files in the /system/xbin directory that are getting updated when I run the installer. It even renames busybox to busybox.old. Any insight?

C:\Local Install\saferoot>install.bat

--- Samsung Galaxy S4 Android 4.3 Root ---

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

Testing adb usability

Plug in your phone and Press any key to continue . . .

Waiting for your phone to appear

Your phone is detected and ready for rooting.

Sending files to your device...

1111 KB/s (17800 bytes in 0.015s)

6277 KB/s (100452 bytes in 0.015s)

4632 KB/s (2139595 bytes in 0.451s)

5332 KB/s (1109128 bytes in 0.203s)

39 KB/s (629 bytes in 0.015s)

Starting rooting program.

ro.build.product=jfltevzw

ro.build.id=JSS15J

Succeeded in getroot!

Remount success!

Copying files..

remount: Device or resource busy

Done.. now reboot to enable root!

Removing temporary files...

Rebooting... Please wait.

Waiting for device to re-appear...

Installing busybox

error: device not found

error: device not found

error: device not found

error: device not found

error: device not found

--- All Finished ---

Press any key to continue . . .

C:\Local Install\saferoot>
[Verizon Samsung Galaxy S 4] swc2001:
that's what mine did too but it has root now.... use TB or root checker
[Verizon Samsung Galaxy S 4] jimbob_sf:
Well, I got root. I just read the .bat file and ran all the commands by hand, in sequence. I'm all good.

THANK YOU to the developers and to those that offered help.
[Verizon Samsung Galaxy S 4] tailgunner9:
Root 4.3 OTA MK2

Yea got it in. Got ROOT now & Super U. Thanks to all you guys on here. Only thing do not like is the Custom sign under Samsung on boot. MERRY CHRISTMAS...........:laugh:
[Verizon Samsung Galaxy S 4] decaturbob:
same here, got root but have the custom sign under Samsung on boot
[Verizon Samsung Galaxy S 4] k1mu:
Sorry for not replying immediately to everyone tonight. It's my wife's birthday today and I took her out to dinner. Sometimes real life intrudes. :laugh:

The "error: device not found" means that the busybox install saw the phone appear then immediately disappear.

The one thing I can think of is that the script tells the phone to reboot, then waits for it to appear. On my SGS4, the reboot happens right away. Maybe this is a case where the phone hasn't disconnected due to the reboot so the script tries the busybox setup before the reboot.

The other possible problem is that when you start from unrooted, SuperSU prompts you for permission to run a program. If you don't respond quickly enough, the access is denied. So, I've added some more prompting to the script to tell you to unlock the phone to await the SuperSU prompt. You need to keep the phone on until that SuperSU prompt appears, then you should be OK.

Whew. I've just rooted unrooted and re-rooted about 30 times tonight.

There's another .zip in the original post with the changes as above.

I've updated the 'su' binary and changed the script to slow down the post-reboot stuff to hopefully make it more repeatable.
[Verizon Samsung Galaxy S 4] swc2001:
Good greif.... your wifes B-day! You better just step away from the phone for a day or two! LOL. thanks for takin a second to get back on though! K1Mu we sure appreciate you and Hash..... you really have no idea...... one last thing though...... I couldn't get my phone to find the Mk2 update how does one get this if not by OTA? Is there a NO WIPE version of it floating around somehere..... also do we really need MK2? is it a big deal..... If so.... why? Thanks again Bro!
[Verizon Samsung Galaxy S 4] k1mu:
Merry Christmas to you as well.

As far as the Custom flag goes, as I've said several times in this thread, that's what you get when you're rooted: you're custom. There's ways to disable that which are mentioned in this thread. (Wanam exposed, Security Hacks, Fake System Status).