yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] CheriePie:
Thanks! I was thinking of looking into that, but I recall that it wasn't updated for the longest time and probably wasn't worth the expense. Looks like the dev is back working on it again though so I'll revisit it.

I thought for sure it had to do with the system itself because it's 2 different apps that are exhibiting this behavior, and both previously worked fine on my HTC Evo 4G LTE which I just replaced. Too bad there's not a free version that I can see... $3.99 is a bit steep for an app that went over a year without updates.

Anyhoo... I did just do a couple other tests successfully, and copied a file to the /system directory so apparently it's just a problem with these particular apps.

Thanks again though, for confirming. :)
[Verizon Samsung Galaxy S 4] nnbengboy2:
I got root browser working, and its a free app. But yeah, it seems the root explorer in es file explorer is broken on this phone/build.
[Verizon Samsung Galaxy S 4] HipHopIsLyfe37:
This root method is so dirt nasty. Easiest root method I have ever done on any of the phones I've worked with! Thanks!

But the question is, where should I go next? Normally I'd install a custom ROM, but that isn't available yet. I installed the free version of Titanium Backup. Any other great apps that let me do cool ****? I have an S4 on Verizion and unfortunately I only have 4GB of data to work with, so no tethering for me :-/ Any suggestions would be awesome!
[Verizon Samsung Galaxy S 4] FMinMI:
Hello all.

I just got my S4 and have done nothing to it yet. Says it is running MJ7 and I am going to follow the procedures outlined above to hopefully root it. But today a Verizon update notice came up. I did a search and see they are again pushing an OTA update (past MJ7).

QUESTION: Should I do the OTA first and then this OR do I do the above procedure first? Or will things get screwed up with this OTA looming?

Also, with MJ7, is there a 'root keeper' that works? When I rooted my S3, I think I used OTA Rootkeeper but I don't believe it will work...

Thanks and happy holidays.

Frank
[Verizon Samsung Galaxy S 4] Arsenic1234:
I actually took the MK2 update because people said SS works on that baseband.

But when I try to run this root, it just sits on daemon started successfully and nothing ever happens after that.

I look for something on my phone to approve but nothing pops up.

And I made sure to download the KIES software so I know it sees the phone.

Does this root work on the new MK2 update?
[Verizon Samsung Galaxy S 4] decaturbob:
Safestrap is not functional on Mk2 or MJ7 base. Not sure where you read that. Its under development by hashcode with some preliminary testing being done....ongoing development. Not to jump the gun

powered by hashcode safestrap hyperdrive 10.2
[Verizon Samsung Galaxy S 4] k1mu:
You can root now then take the OTA. When I did, I kept root. Perhaps due to using "Survival Mode" in SuperSU Pro.

The MK2 update is also rootable using this tool in case the upgrade removes root.
[Verizon Samsung Galaxy S 4] k1mu:
Interesting - I see the same thing with ES File Explorer. SuperSU grants it root permission, then ES complains "Sorry test failed".

I'll take a look at the logs and see if I can detect anything interesting happening.
[Verizon Samsung Galaxy S 4] k1mu:
Nothing in the logs helps with understanding this. However, apparently there's a version of ES Root Explorer that works.

See this thread and especially post #18 in that thread.

It looks like it's not a problem with gaining root, it's something in the filesystem type that's confusing ES Root Explorer.
[Verizon Samsung Galaxy S 4] swc2001:
On the touchwiz for the SGS4 can you make the back ground scroll? I would like to do this without a new launcher...... this and the no landscape are the only things I dislike about Touchwiz.
[Verizon Samsung Galaxy S 4] upther:
Wanam allows for scrollable wallpaper.
[Verizon Samsung Galaxy S 4] FMinMI:
Thanks for the reply. I did what you suggested and followed the procedures in the first post. Decided to do the Kies install to make sure the drivers were good. WOW, what a mess that was. Downloaded, ran, said no to the crap but it still took a long time. It loaded a ton of stuff. Then it said it was out of date, so another download. Then it said that download would not work with my S4 so I had to download version 3. Glad I did that on my test computer (will reimage back to get rid of all that stuff).

But finally Kies said it saw my S4 so I ran the script.

It appeared to go right saying: (see attached screenshot)

daemon started successfully

files were sent

starting rooting program

succeeded in getroot!.

Remount success...

copying files

done now reboot to enable root!

removing temp files

rebooting.

And when it started up I did see "Custom" and I have the unlocked icon

But then it said

Installing busybox

error: device not found

error: device not found

--All Finished--

It then started (or did I start it???) SuperSU and it complained about KNOX (not sure what it is) and asked me if I wanted to have it resolve the issue. I said YES and it said all was good.

So, my two questions - what happens without busybox and did I do the correct thing for KNOX (having SuperSU circumvent it)?

I still have the OTA update popping up but am ignoring it for now.

Thanks all.

Frank
[Verizon Samsung Galaxy S 4] jball:
Root works great no problem.

How do I configure it correctly .

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] CheriePie:
Actually the version linked in that thread is older appears to be older the version I have installed (3.0.5 vs 3.0.7) so I didn't bother to install it, figuring if it was fixed back then, it should still work in the current version.

HOWEVER, I did manage to fix the issue!! Hopefully it didn't break anything else, time will tell... or perhaps you will know. But here's what I did...

I had allowed SuperSU to disable Knox on it's initial launch, but obviously was still seeing this issue. So I went back into TiBU and froze any remaining apps with knox in the name and rebooted. After rebooting, I was able to successfully enable Root Explorer in ES File Explorer (and use the mount R/W in Solid Explorer).

Here's a list of what's been frozen:

- com.sec.enterprise.knox.attestation 1.0

- com.sec.knox.eventsmanager 1.0

- KNOX 1.0 (link)

- KNOX 3.0

- Knox Notification Manager 1.0 <--- this is the one that was already frozen/disabled by SuperSU

- KNOX Store 1.0

I'm only just now coming to Samsung and Verizon after many years with HTC and Sprint so I'm not all that familiar with Knox yet and how it works. So I'm not sure if freezing all of the above will have any detrimental effects on the system. Right now, I'm not seeing any yet and can happily report that the /system mounting r/w issues with both ES File Explorer and Solid Explorer are working again.

As an aside, even though I don't believe it's related, I also purchased and installed Root Explorer while I was troubleshooting and discovered that Root Explorer did correctly allow /system r/w mounting even before disabling those additional Knox apps/entries in TiBU. (Though ES and Solid req those other entries be frozen before it'd allow to mount /system as writable.)

I guess I should do a bit more research on the required components of Knox and what kind of repercussions if any, can come from freezing all of those additional ones. Unless you care to fill me in... ;)

Thanks so much for your responsiveness.
[Verizon Samsung Galaxy S 4] FMinMI:
Just to let everyone know: I followed the instructions in the first message and then confirmed I was rooted using Root Checker Basic. I then accepted the OTA upgrade (which took me from MJ7 to MK2) after purchasing and installing SuperSU PRO and turning on Survival Mode (someone had recommended it since Voodoo OTA keeper was known not to work on 4.3). After the update finished, I rechecked both the boot screen and Root Checker Basic -- root was still there.

This had to have been the easiest root I have done in the past 6 phones I have owned! Thanks guys!

Now to find a tether program that works with a rooted phone...

Cheers.

Frank

Michigan
[Verizon Samsung Galaxy S 4] k1mu:
You should disable Knox when SuperSU asks you. If you don't, you'll get a lot of warnings about programs using their root permissions.

As for the busybox install - the "device not found" means that the phone re-appeared with adb access booting then disappeared right away. That's behavior that shouldn't happen. However, it doesn't hurt. You can always install Busybox Free from the Play Store and install that.

What busybox does is to provide a large number of standard UNIX shell commands. Applications that expect root may also expect that busybox is installed as well, so it's a good idea to complete that install.
[Verizon Samsung Galaxy S 4] FMinMI:
Thanks. I did go ahead and load BusyBox from the store and did a normal load. All is well...

Cheers.

Frank
[Verizon Samsung Galaxy S 4] k1mu:
When you run saferoot, it installs /system/xbin/su with 6755 permissions, or "-rwsr-sr-x" in the format that your program uses.

You don't need that on a phone running 4.3, so when you update the su program using SuperSU, it ends up with "-rwxr-xr-x".

So, you need to tell the author of whatever root checker you're using to update that program.
[Verizon Samsung Galaxy S 4] jball:
I see

I can confirm that it's where it should be using my root explorer. I'm definitely not denied root access .

Thank you for the explanation

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] rithvik14:
Question.Why did you put it on your sd card when you can just click install.bat on your computer and plug your phone in?

---------- Post added at 04:05 AM ---------- Previous post was at 04:00 AM ----------

You would need to use odin to reflash the bootloader
[Verizon Samsung Galaxy S 4] jball:
Your supposed to download the zip and extract it.then open the extracted folder and open the

"install .bat" as administrator. I had to switch from MTP to TPT only after it rooted and rebooted so busy box would finish installing. Use this on a Computer

It also sounds like you don't have your USB drivers installed properly

ROOTED ATT MK2 using Tapatalk

---------- Post added at 05:15 AM ---------- Previous post was at 05:12 AM ----------

:_)

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] k1mu:
Yeah, you can't run this from your phone.. it MUST be used over the ADB protocol. Unzip onto your PC, Mac, or Linux system, then run the appropriate rooting script. I've successfully rooted using Windows 7 and MacOS using this.
[Verizon Samsung Galaxy S 4] jball:
Worked on my Windows 8 HP laptop

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] AndroidLonghorn:
Thanks K1mu. I just tried running the new file. Now it just say s Waiting to unlock. My phone is unlocked and nothing pops up. I'm running it from Windows 8.1 as an administrator. My phone is the AT&T Galaxy S4 and the baseband is MK2. I have not tried kingo or vroot.
[Verizon Samsung Galaxy S 4] k1mu:
What says "Waiting to unlock"? Can you please post a log of what shows up in the comment prompt window when you try to run the install.bat file? (To copy that, click on the icon on the upper left corner, choose "Edit->Mark", then highlight the text. Use "Edit->copy" to copy the text. I'll need to see the entire log from the beginning.
[Verizon Samsung Galaxy S 4] AndroidLonghorn:
Ok, I just realized that I failed to enable usb debugging after I did a factory reset. I enabled it, and I ran the new script, which runs now, but I still get "Error opening /system/xbin/daemonsu" for write: Text file busy"

I still get the no binary installed error. Thanks again for the help!
[Verizon Samsung Galaxy S 4] rithvik14:
Also, does this root create a splashscreen like for safestrap recovery?
[Verizon Samsung Galaxy S 4] Maxim726X:
I get the same exact message...
[Verizon Samsung Galaxy S 4] richmelchr:
damn it man, you are awesome. this worked perfect. Definitely the most easy root I have ever performed. I even did it drunk :)
[Verizon Samsung Galaxy S 4] Sparatan117:
Holy.... crap

I downloaded it and thought "there's no way it's this simple, what else do I need to download"...

Sure enough... worked like a charm. FTG... First Time Go...

props, you are obviously a coding lord....
[Verizon Samsung Galaxy S 4] WordsworthESP:
According to k1mu, that's not a problem. Apparently it means you already have daemonsu installed. Have you previously rooted?

ANYONE HAVING ISSUES GETTING STUCK AT THE DAEMON STARTED OR ISSUES WITH ES FILE EXPLORER, READ BELOW!!!

Those stuck at Daemon Started, toggle your USB connection from and back to Camera mode, and voila! It begins.

Knox appears to block the Busybox install before SuperSU gets a chance to disable it. There may be a better/easier way to remedy this, but I had to unroot and root again and it ran without a hitch.

As far as ES File Explorer goes, it's not an issue with the app, it's somehow related to the above issue. I can't claim to know enough as to explain why, but I can tell you after my unroot/root process I have full root, and with the exception of V4A no longer working since my partial-root loss... everything is working as it should.

My (barely-educated) guess is it could be that we are rooting from MULTIPLE firmwares, and prior to MK2 (AT&T 4.3) there was no Knox. It may also have something to do with our Security settings, though I believe that is less likely. I hope k1mu eventually adds some of this info to the OP, especially the part about Camera mode.

Edit

: SuperSU just released an update, and the update notes mentioned: Fixed non-priv root on some SELinux/Enforcing devices. I'm not sure what that means exactly, however, you do have to make sure to update the binaries after updating SuperSU.

Sent from my AT&T Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] jball:
No splash screen bud.its root not Safestrap

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] WordsworthESP:
Unless he's asking about the Samsung Custom screen, which in that case, the answer would be yes.

Sent from my AT&T Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] jball:
He did mention "splashscreen" and

"Safestrap".

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] todd3835:
Thanks so much for this. Using this, I was able to get HD11 working between this root, and then the latest SafeStrap! Without you, I'd still be on me7 / 4.2.2!
[Verizon Samsung Galaxy S 4] agriff:
Thanks, very much for this. Been waiting for someone smarter than me to crack this nut.

Quick question... I now have a 100mb file in the root /system directory named ".randompad". Is this something left over from the rooting process or just part of the stock ROM I just never noticed before? Then, is it safe to remove? Thanks
[Verizon Samsung Galaxy S 4] Maxim726X:
You're right, I did have the phone rooted at one point... Totally forgot until you mentioned it. I tried what you suggested and I'm still stuck on the same error. What else should I try?
[Verizon Samsung Galaxy S 4] k1mu:
That's nothing to do with the rooting process.

That being said, I wouldn't remove it if you don't know what it's for. It may be a one-time pad that's used to decrypt some file and if you remove it then you won't be able to use that file.
[Verizon Samsung Galaxy S 4] k1mu:
I've updated the program to allow the case of already rooted. I'm now able to run this multiple times without getting "text file busy" errors.

The scripts also now make sure that the su program is set up with the expected permissions so root checkers won't fail.

I've edited the OP to make the troubleshooting steps separate, hopefully that'll keep people from missing the text that was there about toggling camera mode.
[Verizon Samsung Galaxy S 4] pbman1953:
If I understand right, there's a newer update after MJ7?

After reading this thread I tried to run an update and it kept failing

Thanks
[Verizon Samsung Galaxy S 4] Maxim726X:
Perfect, worked like a charm... Thanks so much.

Appreciate the prompt responses. Anyway I can buy you a beer?

EDIT- Actually... It didn't work. It did initially but now it doesn't appear to be rooted (verified with rootcheck). Am I supposed to do something else after the program is run?
[Verizon Samsung Galaxy S 4] Drayk:
My post isn't a contribution to this thread so much as an opportunity to get in a 1st post on XDA.

Longtime Blackberry guy currently using a GS4 SGH-I337.

Sorry for taking up thread space but I'm just trying to summons up enough "sac" to pull the trigger on this. I've loaded plenty of BB OS leaks and this root seems like it's a pretty similar process as a BB leak. Just open the install.bat file & you're off to the races. My apprehension is, if something goes wrong. I'm not familiar enough with rooting/android modding as I am BBOS installs. I did force stopped Knox thinking it could block this install.

But.... with the help from XDA, I hope to be "up to snuff" with this stuff.

BTW

, I did the OTA 4.3 update when it came out so.... I'm trying to root 4.3 on AT&T.

Side note: I did/do have a GS3 I rooted using odin, but every indication says this is a completely different install.... a "point n shoot" sort of deal

Glad to be a part of the XDA family.... Happy Holidays, peeps!
[Verizon Samsung Galaxy S 4] Trak-X:
Hello all.

Thanks for this root method.

If it helps anyone, here is a list of phones i managed to root using your method:

Verizon Galaxy S4 - MJ7

ATT Galaxy S4 - MK2

Verizon Galaxy S3

Galaxy S3 - I9300 - LF2

Kindle Fire HD

Update:

Tried now on Verizon HTC One and worked. Managed to get root after it went to kernel dump.

Second update:

Tested now on a Galaxy S4 with MK2, freshly update. No issues on rooting -WORKED LIKE A CHARM. Issues appeared after rebooting. A folder i just created under system got permissions reset to read only for owner. Without root, i had no access to see the content. Ran su, and changed permissions to 755. Issue solved. Same issue for a certificate that i manually pushed to /etc, it only had read permissions for owner.
[Verizon Samsung Galaxy S 4] hipjudge:
Success But...

Thank you guys for developing this root! I just ran it and to get it to work I had to copy all of the files out of the "Files" folder up into the same folder as the su and install files. Once I did that it worked perfectly.

Does anyone have a way to remove root and the "Custom" screen? I'm paying for the insurance and they won't fix anything as long as they see that unlocked padlock on boot. Thanks.
[Verizon Samsung Galaxy S 4] dovedescent7:
cant seem to get this to work on at&t s4 i337 running mk2..

enabled debugging,tried running install bat 2x no go...

anything special needed to use this exploit on i337?
[Verizon Samsung Galaxy S 4] SCWells72:
I literally just did this on my MK2/i337 S4. I had to do two manual things, though:

On line 10 of install.bat, I had to specify the path to adb as files\adb.

The part starting at line 54 didn't succeed after the reboot because it was asking for me to approve root access for those commands and it timed out before I could approve it. I just ran those lines explicitly from a cmd.exe and, when the first one ran, approved root access. The rest ran through fine after that.

With that done, I'm running a Titanium Backup of my S4 right now! Great stuff!!!
[Verizon Samsung Galaxy S 4] k1mu:
That indicates that you didn't use the included batch file or shell script to install the files. It's there specifically to help avoid complications like that.

This is a very common question. To unroot, open SuperSU and tell it to unroot.

To clear the custom padlock, install the Xposed Framework, then Wanam Xposed. In Wanam, Security Hacks, Fake System Status.

If you're bringing it in for service, you should flash a no-wipe ROM. That'll kill root, but it's easily gotten back.
[Verizon Samsung Galaxy S 4] k1mu:
No, there's nothing else to do. I'd verify by opening SuperSU. If it doesn't tell you that it couldn't get root permissions, you're rooted.

Which "rootcheck" are you using? I've just tried four different root checkers in the Play Store and they all say that I'm rooted.
[Verizon Samsung Galaxy S 4] k1mu:
"No go" isn't very descriptive. Is it hanging waiting for the device?
[Verizon Samsung Galaxy S 4] k1mu:
I've re-uploaded with the correction to line 10 in the install.bat. Thanks.
[Verizon Samsung Galaxy S 4] cameronsutor:
Issue with .bat script

I was running into a problem, and maybe I am the only one, but I thought I'd mention my fix just in case someone else ran into the same issue.

I extracted the files in the zipped folder to C:, then double-clicked the "install.bat" file to run it, I would press "Enter" to continue, then I would immediately get an error that stated that "files" was not a valid command, or something to that effect (I was unable to grab a screenshot of it because it was gone in a second). Since it was apparent there was an issue with the script pointing to the correct place (although I don't see how), I went ahead and moved all the files in the "files" folder to the root of C: (which put it in the same directory as install.bat). I then edited the install.bat file to match the moved file(s).

Take a look at the attached file and use it if you'd like. k1mu, I hope you don't mind me changing and posting your file, but it was the only thing that worked for me and I thought it may help someone else stuck in the same situation.

C
[Verizon Samsung Galaxy S 4] koreo:
Ive been rooted for a few days. No problems. Now what?

I used to run Cyanogenmod on my old Dinc and loved it. Is there a cyanogenmod out now that I can flash now that Im rooted?
[Verizon Samsung Galaxy S 4] decaturbob:
Read some threads here...unless you are a mdk base and loki'd there is no custom Roms or recoveries. The only exception is safestrap users can flash tw based stock Roms...no custom kernels. Read some threads

powered by hashcode safestrap hyperdrive 10.2
[Verizon Samsung Galaxy S 4] tailgunner9:
Root 4.3 OTA MK2

So which file on page one do I need to Download to root my SGH-i337 with OTA 4.3 MK2?? Is this SAFE? Almost new phone so do not want to screw it up. Thanks Guys....:confused: saferoot.zip - [Click for QR Code] (2.08 MB, 116 views Is this the file that you have added line 10 into now and works without doing line 10 Manually?
[Verizon Samsung Galaxy S 4] jball:
VERY

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] k1mu:
As the original post states, once you've unzipped, there will be two files (install.bat and install.sh) and a folder called "files".

If your unzip utility isn't smart enough to re-create the folder structure, then unzip everything, make a folder called "files" and move everything but the install.bat into that folder. Then it will work.

The way you did this was to unzip everything into C:\ and ignore the folder structure in the zip.. then you had to edit it to use "\adb" versus "files\adb" because you didn't have the files folder.

It got you there, I guess, but I think you need to find a better unzip tool. :)
[Verizon Samsung Galaxy S 4] k1mu:
Yes, that's the file. And yeah, this is safe. If it fails, it won't cause any damage.
[Verizon Samsung Galaxy S 4] Glynix:
I can't seem to get this working no matter what. I had an MJ7 build phone and tried this method and no go. So I figured well its working for people on MK2 so why not upgrade anyway and try again. Tried again and no success. Then tried wiping data/factory reset, cache, etc, and then retry this root method and still not working. When I run install.bat my CMD promp flashes on and off so fast I cant see what it says. I do noticed the word unexpected in there and its some type of error like that. How can i get my cmd to stay up longer to copy whole error for you guys? Or does anyone know what might cause this? I have tried multiple versions of samsung drivers. ADB,busybox issue maybe? Please help!

thank you :laugh:
[Verizon Samsung Galaxy S 4] k1mu:
After three reports of the same problem, I tried it on a clean pc, and of course the install didn't work. Please try re-downloading - hopefully it's fixed now. If you tried this and it just flashed an error message and exited, please give it another try. Apologies.