yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] cpttsubasa:
I can't wait to try this. Not new to rooting but new to Samsung. Quick question, this method doesn't wipe anything, right? Once rooted, I can backup using Titanium Backup and keep current app data?
[Verizon Samsung Galaxy S III] Noxious Ninja:
It doesn't wipe anything at all.
[Verizon Samsung Galaxy S III] naught101:
still not working

I'd love to do it this way: I don't usually use windows, and I don't always have a windows installation available. Unfortunately I'm still hitting the same problem as with the windows method:

$ ./adb push su /data/local/
failed to copy 'su' to '/data/local//su': Permission denied
$ ./adb shell
$ ls -la /
...
drwxrwx--x system system 2012-07-26 19:12 data
...

Which means that I can't see what's in /data/, much less copy files there.

Any ideas?
[Verizon Samsung Galaxy S III] Noxious Ninja:
I added a couple more questions to the FAQ.

I've seen one other report of this happening, and I am really stumped. Is this a US Galaxy S III model? Do you have any Android emulators running, other Android devices plugged in, or PDANet installed? What firmware version are you running? Can you double-check to make sure you have USB Debugging enabled?

Can you post the output of

adb shell mount

?
[Verizon Samsung Galaxy S III] cpttsubasa:
I have no idea what is happening but no matter what, I get to the screen with the question : uid and gid must be 0. And I can't get passed it. I have no other devices attached, debugging is on, unknown option is checked. Anyone else? Thanks for your help
[Verizon Samsung Galaxy S III] crazydad:
Ok so i just rooted your method and it was easy and fast!! Awesome work. Now i used the unroot method that i posted a link a few comments back and here are my results. SU did not get uninstalled and it took me from Build version I535VRLG1 which was the updated one to version I535VRLF2. When i check for software updates it wont get me back to the VRLG1. Now im curious to see whether that unroot worked even though it left Superuser in my apps. How would i be able to check if im still rooted?
[Verizon Samsung Galaxy S III] caslca:
Can you run ls -la /data/local and ls -la /data

---------- Post added at 10:27 PM ---------- Previous post was at 10:00 PM ----------

On mine it shows:

127|shell@android:/ $ ls -la /data
opendir failed, Permission denied
1|shell@android:/ $ ls -la /data/local
drwxrwx--x shell shell 2012-07-26 22:46 tmp
shell@android:/ $

I can't see /data, but I can go into /data/local/:

shell@android:/ $ cd /data
shell@android:/data $ ls
opendir failed, Permission denied
255|shell@android:/data $ cd local
shell@android:/data/local $ ls
tmp
shell@android:/data/local $ ls .
tmp
shell@android:/data/local $ ls -al
drwxrwx--x shell shell 2012-07-26 22:46 tmp
shell@android:/data/local $
[Verizon Samsung Galaxy S III] cpttsubasa:
In case someone would find this helpful: reinstalling the driver didn't do it but I installed the drivers on a different computer and the rooting method worked perfectly!
[Verizon Samsung Galaxy S III] naught101:
Definitely no other phones, or android emulators or PDAnet running. I definitely have USB debugging enabled, and install from unknown sources as well. Fimware version is 4.0.4, stock android, phone was bought from Hong Kong, shipped to Autralia already unlocked (there are no left overs from any telco that I can see). Model number is GT-I9300, baseband is I9300UBLE6 kernel verision 3.0.12-554633-user, build number IMM76D.I9300UBLE6

Output of 'adb shell mount':

$ ./adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p10 /preload ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/dm-0 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:17 /mnt/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/extSdCard /mnt/extSdCard ecryptfs rw,nodev,relatime,ecryptfs_sig=226cc91ccf79d3ed,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough 0 0

What device is usually mounted at /data/local/ on US phones?
[Verizon Samsung Galaxy S III] Noxious Ninja:
My phone:

/dev/block/mmcblk0p14 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0

I'm not sure why the write to /data isn't working, but the tool won't work, period, because /system is on a different partition.
[Verizon Samsung Galaxy S III] Noxious Ninja:
Sounds like the driver installation didn't work. The tool is currently a Windows batch file, and doesn't have very good error handling, so it doesn't give you a helpful error message in that case.

Glad you got it working.
[Verizon Samsung Galaxy S III] Desertburn:
thank you

i appreciate this procedure
[Verizon Samsung Galaxy S III] Noxious Ninja:
Update: I don't think an APK-only solution is possible.

adb shell ls -ld /data/local
drwxrwx--x shell shell 2012-07-28 08:33 local

Copying files to /data/local/ can only be done by the shell user/group, which basically means ADB. So unless there's some way to adb from the device to itself, this idea is dead. :(

It is possible to put adb in TCP/IP mode and then connect to itself, but unless you're already rooted, that still requires connecting to USB for the first step, which makes it kind of useless.
[Verizon Samsung Galaxy S III] naught101:
Ok, damn. Guess I'll have to wait for some other method..

BTW, for reference, I CAN cd to /data/local, I just can't ls it:

app_131@android:/ $ export PATH=/data/local/bin:$PATH
app_131@android:/ $ ls -la /data/local/
opendir failed, Permission denied
1|app_131@android:/ $ cd data
app_131@android:/data $ cd local
255|app_131@android:/data/local $ ls -la
opendir failed, Permission denied
[Verizon Samsung Galaxy S III] tillithz:
I just replaced my phone and am looking to root this way so I can get a custom recovery on and backup "my" phone and not rely on a stock image later....
[Verizon Samsung Galaxy S III] skinnytoo2:
I am getting same error. I reinstalled drivers and still get it. I only have one machime with windows all others are macs so cant switch.

HELP!!?!?!?!?

Thanks!!
[Verizon Samsung Galaxy S III] Hockeypuck55:
Worked great for me. Thanks.
[Verizon Samsung Galaxy S III] Desertburn:
root worked!

your procedure worked great!, any info on a good rom?is jellybean out for this yet?
[Verizon Samsung Galaxy S III] cpttsubasa:
I feel bad because I know how frustrating this is. No matter what, I could not get it to work on my primary machine. If anyone lets you borrow a machine, it's like a twenty minute process and you'd be set. One thing I *think* messed things up on my machine was the Comodo firewall. That thing is too aggressive in blocking ports apps etc. Just a thought in case your settings can be tweaked. Wish you the best and wish I had a better solution
[Verizon Samsung Galaxy S III] boynamedstacy:
Why not try running the script mentioned in post #96 for mac/linux. Then you can tell ME if it worked properly :silly: I am picking up my second S3 and don't want to have to borrow a windows machine.
[Verizon Samsung Galaxy S III] silver04v:
I used this tool this morning and everything worked out well. Made my backups and letting everything be for a little bit before I rom this thing. I'm pretty satisfied on stock right now but do have synergy 1.3 dl'd.
[Verizon Samsung Galaxy S III] psperl:
I ran that script and I got this:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
2831 KB/s (380532 bytes in 0.131s)
5488 KB/s (1862336 bytes in 0.331s)
3 KB/s (144 bytes in 0.040s)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: Allocated inode: 2134
debugfs: debugfs: debugfs: debugfs: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:99)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:263)
at dalvik.system.NativeStart.main(Native Method)
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
4328 KB/s (1468798 bytes in 0.331s)
Error: Could not access the Package Manager. Is the system running?
error: device not found

Since the last line mentioned Package Manager, I figured ti failed installing the superuser apk for some reason. I ran 'adb install Superuser.apk', and it worked.

I have root. I'm not sure if that last step was needed, but either way I have root.
[Verizon Samsung Galaxy S III] Michael58:
I try to root the phone but it's not working , atached image for the root process , USB debugging on also Unknown sources checked. any idea why i can't root the phone ?

Edit : Fix it and root .
[Verizon Samsung Galaxy S III] silver04v:
Are your drivers installed on your machine? Tried switching to different usb ports?
[Verizon Samsung Galaxy S III] MightyDollar:
Worked

Worked like a charm, thanks!

Donate to this guy!
[Verizon Samsung Galaxy S III] sigmaxaa:
Worked like a boss...really is as easy as described! Great work!
[Verizon Samsung Galaxy S III] ooofest:
Hm, the only reason I had to root was for replacing the buggy Touchwiz email app with stock ICS, but if that precludes my ability to successfully install OTAs then I might need to just find an alternative email app which is decent (i.e., haven't found one yet).

- ooofest
[Verizon Samsung Galaxy S III] anothermbdusted:
i keep getting a thing that states "uid and gid should both be at 0" are they ? y/n

any clues what this means ?
[Verizon Samsung Galaxy S III] silver04v:
Yea, right above where it says that you should see uid 0 and next to it gid 0. Just hit y then enter if it is like that.
[Verizon Samsung Galaxy S III] SpunkyXL:
How do you install recovery through this method?
[Verizon Samsung Galaxy S III] silver04v:
Use the app ez recovery after rooting.
[Verizon Samsung Galaxy S III] SpunkyXL:
thanks, will give it a shot
[Verizon Samsung Galaxy S III] nico4k:
superSU error...

SuperSU binary fails to install everytime (which means, I cant use root apps), I rebooted the phone several times, but it keeps failling anyways. anyone have a fix? :confused:

nevermind, I found the problem: i had both superSU and Superuserl installed. I removed superSU. now all works great!

thanks for the root method, way too easy. :)
[Verizon Samsung Galaxy S III] monthlymixcd:
I can confirm that this method for achieving root works on the U.S. Cellular SIII that I picked up last week. Thanks to all!
[Verizon Samsung Galaxy S III] robpet2:
just used this tool to root my Sgs3 that i just got today, everything was easy as pie.. thanks for this..
[Verizon Samsung Galaxy S III] skinnytoo2:
So I borrowed a co-workers laptop and still get same result!!! So frustrating!!!

Is the USB PC Connections suppose to be set to Media Device (MTP)?

I dont understand what else I could be doing wrong...ugh!! :crying:
[Verizon Samsung Galaxy S III] dsherry:
Thank you thank you thank you Noxious Ninja (best wishes for your wedding; I'm tossing some $$ your way), caslca et al.!!!!!!!

I tried this script by hand in bash and it worked like a charm. One note: make sure you don't already have Superuser installed... otherwise adb install Superuser.apk will fail. I was able to recover from this failure by manually uninstalling Superuser (Settings --> Application Manager --> Superuser --> Uninstall), followed by re-executing adb install Superuser.apk

Oh, one more note: upon running the command ||, I received the following output:

-->$ adb shell "/data/local/debugfs -w /dev/block/mmcblk0p14 < /data/local/debugfsinput"
debugfs 1.42 (29-Nov-2011)
debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: Allocated inode: 2134
debugfs: debugfs: debugfs: debugfs:

I just wanted to stress that although this appears to be an error, nothing on my system was affected negatively and I was able to gain root and finish installing Superuser.apk.

THANK YOU AGAIN |:D
[Verizon Samsung Galaxy S III] anothermbdusted:
Testing superuser...

'adb' is not recognized as an internal or external command,

operable program or batch file.

uid and gid should both be 0.

Are they? (y/n):

this is what i see and dont know if i should go past it or not

this is how I fixed my problem : had to extract the debugs folder to my desktop click on the adb to install then clicked as per instructions worked like a charm and tyvm for your hard work
[Verizon Samsung Galaxy S III] newuser134:
It seems that the firewall app "DroidWall" from the market won't do anything on the stock rooted Verizon rom, which was rooted using the method here in OP, but if the Sprint rooted rom is used from invisiblek's rooting method from here http://xdaforums.com/showthread.php?t=1756885 , it works just fine.

I haven't tried root66 yet, but thought I could maybe avoid the lengthy root process thru Odin if someone here, maybe OP might be able to shed some light on this and might already know why or have a good guess. My guess is that there's some small piece of linux code that is missing during the rooting process that may enable the right su permissions for DroidWall. If someone already knows it works under Root66, maybe it can help figure out why it doesn't with this rooting method.

What it does under the Verizon rom is that no matter what app is selected to be disabled from data access, still gets data access with no problem. Yes, I know, firewall is enabled, and I'm in "blacklist" mode, so selected apps should be disabled. When I was originally rooted with the Sprint rom, it worked just fine disabling apps from accessing WiFi or mobile data.

It must obviously be some linux code or settings, since I'm rooted on this rom as well. I've already emailed the app dev, but thought maybe that I could find someone here in the meantime that has run across the same problem. Any dev's here might know what's causing this?

Has anyone maybe rooted using Root66, and know or can try if DroidWall works with that rooted rom, so I can avoid wasting time trying it if someone else already has?

Thank you
[Verizon Samsung Galaxy S III] hopesrequiem:
Pardon my silly question, but this is an automated process that doesn't require use of adb from what I can see ?
[Verizon Samsung Galaxy S III] Noxious Ninja:
Sorry for not answering questions much... I've been out of town for a few days, and I'm about to go on another trip for the rest of the week.

I updated the OP and FAQ to mention the need to extract the files before running the script. That should solve the problems for a couple of people I've seen in this thread (skinnytoo2, Michael58, maybe others).

That error shows up because I'm trying to clean up existing su binaries if there are any; if you've never tried rooting before, it doesn't find any files to clean up. Nothing to worry about.

It uses adb behind the scenes, but doesn't require you type any commands manually.
[Verizon Samsung Galaxy S III] Cmotion:
Any more success stories rooting on a Mac using the script from a few pages back? I'm slowly working up the courage to do so, but would love to hear from others who have tried.
[Verizon Samsung Galaxy S III] Lock-N-Load:
Hell.. just decided to do it and make some mods I was dying to make (wifi notification hack, etc.)

We will find out what having a custom recovery and root does when it is OTA time.. I pray nothing major.

I also backed up my root with OTA Voodoo Root Keeper. I also made a list of mods I did and their URLs on the web so I can remember what I have to undo if needed.
[Verizon Samsung Galaxy S III] ADC_112358132134:
Have you tried this or can anybody else confirm if this works? I want to root but I want to be able to return to stock if need be, preferably without flashing a new ROM.
[Verizon Samsung Galaxy S III] keenano:
I keep getting the error "server not running" or "waiting for device to be detected..."
[Verizon Samsung Galaxy S III] Renegade360:
Rooted no problem. No to figure out what I want to modify.
[Verizon Samsung Galaxy S III] voodoomanx:
Works great. Used it twice flawlessly. Thanks for a great root tool.
[Verizon Samsung Galaxy S III] Noxious Ninja:
I've probably used that method 20 times to unroot while testing the tool. If you've made any modifications while rooted, it won't undo those, but it will unroot you.

That sounds like the drivers aren't working. What version of Windows are you using? Can you double-check that USB Debugging is enabled? Do you see the phone show up in My Computer when you plug it in?
[Verizon Samsung Galaxy S III] keenano:
Windows 7 running on my mac. USB debugging is enabled and the phone does show up in My Computer.

---------- Post added at 09:40 AM ---------- Previous post was at 09:14 AM ----------

Yep, tried it on another computer and it is going through the reboots as I type this.

Thanks.
[Verizon Samsung Galaxy S III] ADC_112358132134:
Thanks. Just used your method and it worked perfectly. I got an 'error device offline' the first time, but I switched out of the USB 3.0 port on the back back to a regular USB 2.0 port on the top of my computer and everything went smoothly.
[Verizon Samsung Galaxy S III] ooofest:
Easy, fast, nice UI.

Thanks much. Now, to see if the stock ICS email app is an improvement over the buggy one from Samsung (assuming they are different).

EDIT:

And, the AOSP ICS email app has the same "disappearing Inbox emails" problem as the Samsung version, so am going back to stock and unrooting, then calling Verizon Support about this buggy POP3 behavior.

Nice to know I can easily and quickly root at any time!

- ooofest
[Verizon Samsung Galaxy S III] newuser134:
Dear OP, please read and help if possible:

Ok, after some research, I've found out that this root method has a slightly different outcome than Root66 or the sprint-based flashable roots through Odin:

With this, the Superuser.apk app is located in /data/app, so it is installed as a user app and not a system aoo. The owner is "system" (all other apps in /system/app have owner "root", and the permissions don't have the first 2 special permissions checked like Superuser.apk does if rooting by flashin /system through Odin. The app is also named "com.noshufou.android.su-1." instead of Superuser.apk. The su binary is newer and different in size, but it's in the correct location, /system/xbin, and has the right permissions and owner.

I'm not sure this is the only reason, but this lead to Titanium backup not getting root permission at first, and I have a feeling this is the reason why DroidWall is not blocking any apps from using data. I tried moving the Superuser.apk from one of the flashable /system root methods into /system/app and setting the correct permissions with root explorer (3-1-3-2), but after reboot I lost root, so I had to restart from my NAND backup.

Does anyone know how uninstall Superuser from /data/app and install it as a system app under /system/app? Obviously just moving it into /system/app and fixing permissions and owner doesn't work.

Could anyone try to help me figure out why DroidWall won't work if rooting a stock phone using the script/adb method rather than flashing a rooted stock rom?

Thank you
[Verizon Samsung Galaxy S III] Noxious Ninja:
You could try modifying the script. Instead of the 'adb install Superuser.apk', it would be something like 'adb push Superuser.apk /system/app/'. I would be kind of surprised if that actually made a difference though... Titanium Backup worked perfectly the first time I tried after rooting.

EDIT: Actually, that would require an insecure kernel. You should be able to save the APK somewhere, run adb shell, remount /system as rw, then copy it over. Or have the script push it to /data/local, then add a line to debugfsinput to copy it into /system/app.
[Verizon Samsung Galaxy S III] newuser134:
Wouldn't using RootExplorer from Android do the same, if I mount /system/app as R/W, copy Superuser.apk over, then fix permissions? When I did that and deleted the original copy from /data/app, it unrooted me upon reboot. The other question I have is why is Superuser.apk called "com.noshufou.android.su-1.apk in your version of rooting? It still shows up as Superuser in the app tray, but it took me forever to find with that name, and also, in Titanium, it doesn't show up AT aLL for backing up the app.

I don't think the location of the apk is the reason for DroidWall not working either, but I've tried everything else, and it won't work, any app gets right through. I tried it again by restoring my NAND backup from my previous root version with the Odin flash method, and it worked right away. Both installations use the same version 1.7.1 of DroidWall. Somehow something is missing or different in iptables rules. I can't find any dev with knowledge of this to help me figure it out though. I've noticed with the firewall blocking a lot of the useless apps (that mainly use data for ads), the battery life gets A LOT longer. Thought this information may help shed some light on this. I can't think of what else could be the cause.
[Verizon Samsung Galaxy S III] jonathonparker:
Bootloader

Does this method unlock your bootloader? It did give me root access and I just got my phone yesterday and the box says "Updated" so I'm guessing it does work on the new update :)
[Verizon Samsung Galaxy S III] PJnc284:
Bootloader hasn't been unlocked yet on either version.
[Verizon Samsung Galaxy S III] shassouneh:
Worked.....half-way

Everything seemed to work and I see the SuperSU binary. However, when an app asks for root, no UI is presented. It appears (based on the SuperSU log) that it silently denies ALL root requests but does not have a mechanism to change this default behavior.

help! I really don't want to flash a rooted rom since I customized everything the way I like.

Note: Automatic response is already set to "prompt"! No update is available in the Play Store market for SuperSU either
[Verizon Samsung Galaxy S III] sparkym3:
I have edited my original tool to be more generic so that it should work for the Galaxy SIII as well as multiple other devices. So, if you liked Noxious Ninja’s port of my tool (this thread) and would like to try it on your other devices, please head over to this post and give it a try.

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