yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Surge1223:
I looked at your script im just wondering why you have it

remove vroot and then push supersu to system and change permissions? I dont have vroot installed but I guess if it was me I would make the script run something like this:

1. Move supersu, su binaries, and busybox to /system

2. Change permissions of supersu, su binaries and busybox

3. Use mv instead of cp and overwrite and rename vroot files.

4. Use the wild card * to remove remnants of vroot (busybox find / -name *mgyun.shua* etc.,) and then rm rf as needed.

5. Reboot

That way you could probably run the entire script from terminal. But hey if your way works then theres no reason to change anything.
[Verizon Samsung Galaxy S 4] :
Not sure, ill check it out. Also, thank you very very much for serving! /hugs

---------- Post added at 08:45 PM ---------- Previous post was at 08:43 PM ----------

\

LOL! Did you try my script?
[Verizon Samsung Galaxy S 4] blazingwolf:
I just tried it and it put SuperSU on my device but not the binary. So not really working.
[Verizon Samsung Galaxy S 4] Sir_Eagle:
Re-run vroot and get the chinese superuser back and root works. Run LilTechPrincess script and it gets rid of chiness but won't update SuperSU binaries.
[Verizon Samsung Galaxy S 4] :
The biggest reason is that SuperSU runs from xbin, and vroot runs from /bin. I found that if you remove or overwrite the vroot version, which Im using to fix the others, even for a second then you lose root and have to start over...
[Verizon Samsung Galaxy S 4] Kchitown1977:
[MENTION=870113]Lil[/MENTION]tech privilege and a honor to serve. And ty
[Verizon Samsung Galaxy S 4] FriendlyPA:
I am new to rooting galaxy s4, last time I rooted a phone, I was on motorola droid. What does rooting with Vroot give me? Will I be able to instal custom roms?
[Verizon Samsung Galaxy S 4] Surge1223:
Supersu uses /system/bin/.ext/su and /system/xbin/su . That's how it updates its binaries. If you didnt add and chmod the /system/bin/.ext/ folder that's probably the reason peoples binaries aren't updating, but its an easy fix. Great job on making the tool for people though, its not easy to get rid of vroot lol.
[Verizon Samsung Galaxy S 4] lazer9:
Currently there is no working recovery so no flashing of Roms at this time. It will give you the ability to run root apps, remove bloat... ect...
[Verizon Samsung Galaxy S 4] :
It was my first time ever doing something like that, so you're welcome to modify it and make it better. It wont bug me at all. I vrooted my phone like 50 times testing that. haha
[Verizon Samsung Galaxy S 4] Bfitz26:
Got it thank you
[Verizon Samsung Galaxy S 4] :
Did the tool work OK?
[Verizon Samsung Galaxy S 4] Bfitz26:
U was having issues with drivers restarted o

Pc and phone and it was bugging out took some tinkering also the batch tool gave me some issues to saying no device found had to direct adb to my phone manually to give it root permissions and then it was good not my first Rodeo so no biggie

---------- Post added at 07:50 AM ---------- Previous post was at 07:47 AM ----------

Also the recovery.sh is the stock recovery right I got excited thought maybe u got a custom recovery to work LOL! Ps I had a heart attack when I rebooted my phone and showed a unlocked Samsung logo thought I bricked my baby thanks for that haha
[Verizon Samsung Galaxy S 4] customize lord:
video

if you successfully completed this process if you are able i would love for a video of how you did it or some info.
[Verizon Samsung Galaxy S 4] fattyjian:
One Last Time ><

I have an international version of galaxy s4 lte, I9505XXUEMJ5 will it work with it? >< really dont want to lose my warranty just wanna double confirm. :(
[Verizon Samsung Galaxy S 4] :
I don't know for sure if it'll work on an international version, but my gut feeling would tell me yes. also this root method and my tool do not trip to Knox counter.
[Verizon Samsung Galaxy S 4] fabrilas:
I confirm that on s4 on i9505 works, but hangs on the line "cleaning up files". You have to reboot manually and works.

My question is: it works on all 4.3 firmware version?
[Verizon Samsung Galaxy S 4] rslu2:
Don't have the ability to shoot a video. I follower Merdinh's (post #169) method which is easier than typing boogeeman69's (post #84) original method. The killer is syntax if you have never worked adb before. The capture from the bottom of Post #158 makes it a little easier to see the spaces and the responses you should be getting from terminal. Remember you have to be in adb shell not just adb when you start.

Did not try LilTechPrincess' batch as I was already rooted.
[Verizon Samsung Galaxy S 4] :
The best I know it should.
[Verizon Samsung Galaxy S 4] k1mu:
I already answered this, but here's a bit more detail.

That's a "unix domain" socket - it can only be used by processes running on that specific device. Notice the word "unix" at the front.

If it was "tcp" or "udp", that would be a way different problem.

It's how the su binary talks to the Superuser program that puts up the permission prompt.

This is not an indication of anything to worry about.
[Verizon Samsung Galaxy S 4] fabrilas:
but why do you not restart automatically, but you have to do it manually?

Thanks
[Verizon Samsung Galaxy S 4] rolltide78:
Ok so I'm new to rooting an android phone but not new to linux/ios jailbreaking/etc. I'd like to get this verizon s4 stock 4.3 rooted and load the Google Play Edition on it and then upgrade to kit kat when that update is pushed. Is this possible at this time? Sorry for my lack of completely understanding the process.
[Verizon Samsung Galaxy S 4] :
I started a new thread for my tool here: http://xdaforums.com/showthread.php?p=47449193#post47449193
[Verizon Samsung Galaxy S 4] lazer9:
Unfortunately at this time on 4.3, you can only achieve root apparently via these described methods. There is no functional recovery so rom flashing is out of the question at this point. You can run root apps, freeze apps, debloat, ect... Just no flashing of anything at this point.
[Verizon Samsung Galaxy S 4] rolltide78:
Ok that's what I figured but it's hard deciphering what is confirmed around here. Thanks guys for your help.
[Verizon Samsung Galaxy S 4] FriendlyPA:
That's what I thought. Thank you for your help!!!!
[Verizon Samsung Galaxy S 4] -Lawless:
Am I missing something on this?

I was under the impression the the Google Play Edition was a Phone sold by Google with original android on it.

Not a ROM that could be installed.

https://play.google.com/store/devices/details/Samsung_Galaxy_S_4?id=samsung_galaxy_s4&hl=en
[Verizon Samsung Galaxy S 4] riker147:
I'm not positive, but I think there were 2 GP ROMs in the development section.
[Verizon Samsung Galaxy S 4] rolltide78:
Yes supposedly you can root and S4 (prior to 4.3) and load the S4 google edition rom it.
[Verizon Samsung Galaxy S 4] -Lawless:
Ok. I can't find it but that doesn't mean it's not there.

Doesn't matter at this point anyway until they get safestrap or an unlocked bootloader anyway.

Thanks
[Verizon Samsung Galaxy S 4] :
The Galaxy S4 is a Google released phone that is running a Google Play Edition which is built from AOSP (about as vanilla Android as it gets). Basically this means it doesn't have any of the TW (Touchwiz) functions/looks. TW is proprietary to Samsung.

So, there are some people who released GPE (Google Play Edition) ROMs for the S4. To install them you need to have either an older version of the S4, before the boot loader was locked, or Safestrap installed, neither of which is available in 4.3.

Hope this helps!

<3 Angie
[Verizon Samsung Galaxy S 4] boogeeman69:
Actually, root of your internal memory refers to the phone folder in windows explorer, which is indeed, /sdcard/

Not to be confused with the SDCARD, or /storage/ext-sdcard
[Verizon Samsung Galaxy S 4] super_f:
56822585 90

OK but that's why I asked for a clear answer from the begining so there will be no misunderstandings!

So once again! There are three options:

1. The root location of the device (which contains the folders like acct, cache, config, d, data etc.)

2. The root of the internal sd card (/sdcard)

3. The root of the external sd card (/storage/extSdCard)

SO WHICH IS THE RIGHT ONE. I WANT A C-L-E-A-R ANSWER FROM SOMEONE THAT HAS DONE IT SUCCESSFULLY!

(I myself put the files on both option 2 and 3 so it worked for sure but there are people who need an exact answer!)
[Verizon Samsung Galaxy S 4] jwendt79:
2
[Verizon Samsung Galaxy S 4] :
Why dont you use my tool?
[Verizon Samsung Galaxy S 4] super_f:
Your tool is very helpful but I'm currently making a guide for the proccess in another forum so I want the initial instructions first. Do you also agree that the correct location (for the original method) to put the root files is the (/sdcard)? I'll update my guide with your tool as an alternative as soon as you update it and make all the final changes.
[Verizon Samsung Galaxy S 4] Sir_Eagle:
2. The root of the internal sd card (/sdcard)
[Verizon Samsung Galaxy S 4] larue05:
Thank You Very Much...

To all the hard workers in this thread. My wife and I both have GS4s, unrooted on Verizon. When the 4.3 OTA got pushed to our phones it greatly screwed up several core functions. My wife couldn't even open up the dialer to place calls. Going into Verizon they told us we had to do a factory reset so that the 4.3 update would stop conflicting with the old software.

This pissed us off pretty big time being told we would lose everything, and so it finally gave me a reason to root (before doing the factory reset) so that I could get TB on the phones to backup some special application settings. Photos, and Contacts were already being backed up to Google so no issue there.

After reading all of this thread I made the plunge to root both our phones with the Vroot method and then getting the SuperSU binaries installed. In our situation I actually had to do the full root process, then factory reset, then re-do the root process to initialize TB as a SU application.

Everything went flawlessly, and nothing was unexpected.

Both our phones are in working order now, and we can actually place calls.

So Thanks very much.
[Verizon Samsung Galaxy S 4] spc_hicks09:
We're all glad we could help. Let the people with tin foil hats sit there and sulk and wish they had root. While the rest of us who have EXTENSIVELY tested this, enjoy the benefits. Just want to add that SuperSU had an update for me recently and binaries updated without issue :)
[Verizon Samsung Galaxy S 4] super_f:
The Chinese site updated the version of VRoot to 1.7.3. Do we need to do something different in the proccess of rooting?
[Verizon Samsung Galaxy S 4] spc_hicks09:
Shouldn't have to.
[Verizon Samsung Galaxy S 4] Timebomb606:
Did you update this elsewhere or from the play store? Mine didnt update and ive yet to be able to update binaries.

Root is working and phone is finally de-bloated.

Thanks everyone for their help.
[Verizon Samsung Galaxy S 4] spc_hicks09:
Updated from the Play Store just fine.
[Verizon Samsung Galaxy S 4] asr1901:
Will this work with a stock 4.3 (MJ7) unrooted device? Will this method allow me to flash different ROM's?

Thanks!!
[Verizon Samsung Galaxy S 4] lazer9:
Yes, reports say it will.

No to 2nd question.
[Verizon Samsung Galaxy S 4] obededom:
please forgive me if this has been answered, this tread is in desperate need of a cliff notes section for important upates.

I rooted with vroot, still have chinese SU, how do I flash a recovery that I can flash roms with?

just wanna debloat dis beach
[Verizon Samsung Galaxy S 4] lazer9:
There is no way to flash a recovery for flashing roms at this point - ONLY ROOT is all you get here.

You can debloat by being rooted.
[Verizon Samsung Galaxy S 4] obededom:
can you point me to a list of what is safe to pull out of the stock 4.3?
[Verizon Samsung Galaxy S 4] lazer9:
I'm not on 4.3 so can't honestly answer that for you, however, there is a thread in the themes/apps section of this forum that lists removable "Bloat" on prior builds. I will try to find that post for you.

Edit: check the 2nd post of this thread --->>> http://xdaforums.com/showthread.php?t=2395307&highlight=bloat (Debloat list for ME7) Should give you a decent start.
[Verizon Samsung Galaxy S 4] reybie:
It probably got updated so you can't remove their su binaries... :D
[Verizon Samsung Galaxy S 4] super_f:
Are you sure about that or is it just a guess? Have you tried the new method with no success?
[Verizon Samsung Galaxy S 4] reybie:
It was just a guess :) I have not tried the vroot method or the kingo one. Not too comfortable giving some unknown dev free access to my phone where I have personal and work stuff stored. I've been watching this thread waiting for a root method developed by someone known around here.

I lost root from a stupid mistake :o :crying:, so I'll sweat it out for a bit :)
[Verizon Samsung Galaxy S 4] matt1733:
you might be in for a long wait :(
[Verizon Samsung Galaxy S 4] larue05:
To address this I used the new 1.73 Vroot for both of the phones that I mentioned in my post back on post #358 and had no problems.
[Verizon Samsung Galaxy S 4] spc_hicks09:
Well it's a good thing this isn't happening then.....

Please stop spreading false info. This has already been tested numerous times to have no ill effects.
[Verizon Samsung Galaxy S 4] paradisewasted:
Been trying to get chinese superuser off all day and last night. Gained root fine. In fact I have used vroot at least a dozen times after failed attempts to remove Chinese su. Followed adb commands from page 18 and no luck. Gained # and put in commands, but on 8 anf 9 I believe it is system is "read only". Also used liltechprincess tool many many times and gets stuck on cleaning up and I reboot phone Chinese is gone and SU installed but lost root and cant update binaries. Very frustrating. Anyome else having these same issues??
[Verizon Samsung Galaxy S 4] reybie:
I am aware that a lot of folks have installed it and gained root (tested) but the unknown is still unknown. This is not spreading false information, just voicing out concerns. If others take that as fact then it's not my fault.
[Verizon Samsung Galaxy S 4] asr1901:
I guess the only benefit to rooting this way is to freeze bloat. If your goal is to tether, just get foxfi.. works great and only $6.

I wish I read this forum a long time ago. I just got my S4 two weeks ago and it was 2-3 OTA's back. Perfect, you could press the Home key to circumvent tether protection, etc. I don't know why I took the OTA, I think I read a post somewhere saying that the tether thing still worked. Thank god for FoxFi or I would really be upset about the whole thing. I've wanted to try flashing ROM's, but it's not critical. Plus, Nova launcher can do 99% of the stuff I wanted to try.
[Verizon Samsung Galaxy S 4] spc_hicks09:
What is unknown? Plenty of people have tested this thoroughly and found nothing of serious concern.
[Verizon Samsung Galaxy S 4] kwheel596:
Completely stock as I fudged it originally and had to do the full wipe ODIN. VROOT worked for me. I removed that and tried the Kingoapp one. That one not only didn't work...but their website is outrageously slow. Took 26 minutes to download the installation file.
[Verizon Samsung Galaxy S 4] Tada10:
On MJ7 here and something just blocks the crap out of both. No root here yet.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Surge1223:
If anyone that has tried this methods wants to help get figure out what exactly is happening with these apps then could you send me or post a zip containing the output from the following commands:

su
adb shell
busybox lsof
busybox lsattr
busybox cat /*
busybox du -alh /system/*
busybox ls -las /*
busybox ls -l -a /data/*
[Verizon Samsung Galaxy S 4] LilTechPrincess:
Standby

On it, stand by.
[Verizon Samsung Galaxy S 4] jwendt79:
Was gonna try it...but the program from the kingoapp website is taking forever to download. Is there another link anywhere?
[Verizon Samsung Galaxy S 4] LilTechPrincess:
Looks Clean

I don't personally see anything that looks suspicious.

---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------

I will send you a link via PM. The mods seem to not want it posted right now. So, be warned... some are suspicious, I am not.
[Verizon Samsung Galaxy S 4] jwendt79:
Thanks...is this confirmed to be working?
[Verizon Samsung Galaxy S 4] LilTechPrincess:
Works

It most definitely works. I have reloaded and rooted my phone 4x with it today, and no issues. The only controversial part is that some claim it has malware. I have no reason to believe thats true.
[Verizon Samsung Galaxy S 4] jpolzner:
You were able to update the SuperSU binaries? Or you were simply able to achieve root?
[Verizon Samsung Galaxy S 4] :
I can't update the SU binaries, but am fully rooted. I wonder if haxxor had better luck... ill txt him and ask
[Verizon Samsung Galaxy S 4] kdo23:
I wonder if we'll in general get the updates through app on mj7. I updated from mi1 but updated the binary before. Don't know enough about this knox and selinux enforcing.
[Verizon Samsung Galaxy S 4] LilTechPrincess:
More...

I actually suspect that the SE Linux kernel is as much to blame for not being able to update the su binary as the actual app itself. I am able to fully modify my system partition via root shell, but a lot of GUI based apps cannot.
[Verizon Samsung Galaxy S 4] Surge1223:
I haven't got done looking through the logs yet but this sticks out so far

11924/system/bin/app_process/system/app/Superuser.apk
11924/system/bin/app_process/data/data/com.mgyun.shua.su/databases/download_status.db
11924/system/bin/app_process/data/data/com.mgyun.shua.su/databases/app_info.db
11924/system/bin/app_processanon_inode:inotify
11924/system/bin/app_process/dev/ptmx
11924/system/bin/app_processpipe:[29717]
11924/system/bin/app_processpipe:[29717]
11924/system/bin/app_processanon_inode:
11942/system/bin/mksh/system/framework/framework-res.apk
11942/system/bin/mksh/system/framework/core.jar
11942/system/bin/mksh/dev/urandom
11942/system/bin/mkshpipe:[28435]
11942/system/bin/mkshpipe:[28435]
11942/system/bin/mkshanon_inode:[eventpoll]
11942/system/bin/mksh/system/app/Superuser.apk
11942/system/bin/mkshanon_inode:inotify
11942/system/bin/mksh/dev/pts/0
11949/system/bin/.suv/dev/pts/0
11949/system/bin/.suv/dev/pts/0
11949/system/bin/.suv/dev/pts/0
11949/system/bin/.suvsocket:[29724]
11949/system/bin/.suv/dev/com.mgyun.shua.su.daemon/11949.stdout
11949/system/bin/.suv/dev/com.mgyun.shua.su.daemon/11949.stderr
11949/system/bin/.suv/dev/com.mgyun.shua.su.daemon/11949.stdin
11949/system/bin/.suv/dev/__properties__
11949/system/bin/.suv/sys/kernel/debug/tracing/trace_marker
11949/system/bin/.suv/system/framework/framework.jar
11949/system/bin/.suv/system/framework/twframework-res.apk
11949/system/bin/.suv/system/framework/framework-res.apk
11949/system/bin/.suv/system/framework/core.jar
11949/system/bin/.suv/dev/urandom
11949/system/bin/.suvpipe:[28435]
11949/system/bin/.suvpipe:[28435]
11949/system/bin/.suvanon_inode:[eventpoll]
11949/system/bin/.suv/system/app/Superuser.apk
11949/system/bin/.suvanon_inode:inotify
11949/system/bin/.suv/dev/pts/0
11953/system/bin/su/dev/null
11953/system/bin/su/dev/null
11953/system/bin/su/dev/null
11953/system/bin/su/dev/ptmx
11953/system/bin/susocket:[24427]
11953/system/bin/su/dev/com.mgyun.shua.su.daemon/11949.stdout
11953/system/bin/su/dev/com.mgyun.shua.su.daemon/11949.stderr
11953/system/bin/su/dev/com.mgyun.shua.su.daemon/11949.stdin
11953/system/bin/su/dev/__properties__
11960/system/bin/su/dev/pts/2
11960/system/bin/su/dev/pts/2
11960/system/bin/su/dev/pts/2
11960/system/bin/su/dev/__properties__
11969/dev/com.mgyun.shua.su.daemon/sh/dev/pts/2
11969/dev/com.mgyun.shua.su.daemon/sh/dev/pts/2
11969/dev/com.mgyun.shua.su.daemon/sh/dev/pts/2
11969/dev/com.mgyun.shua.su.daemon/sh/dev/__properties__
11969/dev/com.mgyun.shua.su.daemon/sh/dev/tty
12091/system/bin/app_process/dev/null
12091/system/bin/app_process/dev/null
12091/system/bin/app_process/dev/null
12091/system/bin/app_process/dev/log/main
12091/system/bin/app_process/dev/log/radio
12091/system/bin/app_process/dev/log/events
12091/system/bin/app_process/dev/log/system
[Verizon Samsung Galaxy S 4] :
Later on a friend of mine is going to decompile the su file and see what's in it
[Verizon Samsung Galaxy S 4] open1your1eyes0:
I have a few high level devs looking into these root exploits to see exactly what is going. Don't worry guys, we'll get to the bottom of these odd and sketchy methods. Whatever it is, the exploits themselves for actually gaining root are working so we're trying to see if we can recreate them into our own guaranteed safe method.
[Verizon Samsung Galaxy S 4] joeyx2:
You think maybe they don't want it open source so that Verizon will have trouble trying to patch it? Just a thought.
[Verizon Samsung Galaxy S 4] jwendt79:
Thanks for looking into this! I was debating using one of these methods for the last couple hours. But the more I read the more hesitant I got. Think I'll hold of to see what you guys come up with.
[Verizon Samsung Galaxy S 4] jpolzner:
This is a exploit that covers a lage range of devices written by Chinese devs...... I seriously doubt they care about what Verizon will do.
[Verizon Samsung Galaxy S 4] joeyx2:
I see your point but let me reword that. So ANYBODY can't patch the exploit. Though I will say of I was on stock mj7 I wouldn't do it. Long time ago I had some transactions from my account in China or Japan (long time ago so I can't remember) and luckily my bank realized I can't make transactions over seas and in the US on the same day. I think it was when using apps to root was popular and that's how they got my info. Be careful everybody!
[Verizon Samsung Galaxy S 4] Kchitown1977:
Updating binaries still not having luck
[Verizon Samsung Galaxy S 4] TemporalShadows:
reybie's concern is legitimate - you're the one spreading false info, and I'd kindly ask both of you to back off and stop criticizing people who are more cautious than you.

Nobody has proven that vroot is harmless and causes no problems. The problems might simply be hidden at first. The fact is, VRoot hides what it's doing. We know more now about what vroot does, but there are still unanswered questions, such as what does vroot send back through its SSL connection to that server in China? It could be sending back your phone's SIM ID and IMEI, enough to clone your line and run up your bill quite a bit. You would have no idea until the bill came in, and they might not clone it right away. That's just the most obvious possibility, there are plenty more.

Just because people have used it and "found nothing of serious concern" just means that whatever it is hasn't been found yet, not that it doesn't exist.

By the way, here's more detail on the exploit used: https://www.codeaurora.org/projects/security-advisories/missing-access-checks-putusergetuser-kernel-api-cve-2013-6282

I haven't seen that info shared here yet.
[Verizon Samsung Galaxy S 4] spc_hicks09:
Lol. OK.
[Verizon Samsung Galaxy S 4] hahalolppl:
Why doesn't someone just contact the dude who wrote vroot and freaking ask him all these questions?!?!?
[Verizon Samsung Galaxy S 4] skny:
Thanks for this write up. Worked like a charm - although I had to close TB after the reboot & then re-open it for it to have root access, which makes sense. I also then went an uninstalled the Chinese SuperSU via TB, just to clean things up a bit.

Quick question: in order to "keep" my root - would it be advisable to buy the pro version of SuperSU so that I have access to the "Survival Mode" feature? Anything else I need to do to prevent if from being overwritten? I am new to the SGS4 - so I don't know how OTA's work. Am I able to disable them from notifying or coming down automatically? Thanks!
[Verizon Samsung Galaxy S 4] matt1733:
when you use the root de la vega the super su version you get has the option to enable survival mode and you dont even have to buy it !
[Verizon Samsung Galaxy S 4] skny:
Not on mine for some reason. "Survival mode" is grayed out and says I need SuperSU Pro.

Either way - I assume this is something I want to do? And I'll keep searching around and reading to make sure I maintain my root & don't get overwritten by an OTA from Verizon.