yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jacksheadache:
Device detected.

Click Do It.

Wait for lock screen after reboot. Device detected. Click OK. Then

Rebooting...

Step 2 - Rooting...error: protocol fault (no status)* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device not founderror: device not found

Mac OSX.
[Verizon Samsung Galaxy S III] Joey22688:
rooted my s3 fine even though I have the mtp driver problem
[Verizon Samsung Galaxy S III] dawest:
Will a factory reset remove root? I'm not completely familiar with how the root is applied here. I'm having a massive media server error and need to factory reset to get rid of the problem.
[Verizon Samsung Galaxy S III] silver04v:
Factory reset should not remove your root. Just all user data and user apps.

Sent from my Synergized vzw SGS3
[Verizon Samsung Galaxy S III] tsgeek:
Yay! I've got root! This tool worked flawlessly. I just needed to do one more manual reboot, and Titanium was able to get root access. Excellent work.
[Verizon Samsung Galaxy S III] JoeyBert:
Will toggle mods and things of that nature still work with this method? Or do I have to flash a ROM trough odin?
[Verizon Samsung Galaxy S III] Beemer533:
Sweet! Thanks for this tool, it worked great.

Now to go add Wallet and remove some VZW BS...
[Verizon Samsung Galaxy S III] spiderj:
I have read through this thread and just want to be clear. I am coming from HTC so this Samsung stuff is new to me.

Using this method, I will not be able to flash custom roms? (CM9, etc) Or i can? still trying to understand how this differs from the root66.
[Verizon Samsung Galaxy S III] trafalger888:
This just gains root access...you can use ez recovery or whatever other method to flash recovery

Root66 and others are rooms that you can flash that a pre-rooted/de-bloated
[Verizon Samsung Galaxy S III] huedawg:
I had this happen the first time . I changed file permissions on it and then it worked fine .
[Verizon Samsung Galaxy S III] sstenhjem:
Woohoo, That was easy. Now to figure out which MODs I want to do.
[Verizon Samsung Galaxy S III] tu3218:
Coming from a nexus, it was pretty impossible to brick the device. This method seems fool proof. Is it as safe as it looks? Just got my sgs3 and would love to get on the dark side.
[Verizon Samsung Galaxy S III] silver04v:
Rooting with this tool is simple and I can't imagine you facing any issues. Takes only a few mins.

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] tekrhino:
Bingo, Device is rooted.. couldn't have been made easier.

Thanks OP
[Verizon Samsung Galaxy S III] ladymeggs:
Unable to unroot

I wanted to try the unroot just to make sure all would be good if I ever had to make an insurance claim on the phone. I do not have a su file in the /system/xbin/ folder. Am I doing something wrong? It is rooted correctly and works.
[Verizon Samsung Galaxy S III] tu3218:
Okay so I'm about to root using this method. As soon as I have root, can I just install cwm recovery via RM? Then am I good to install any rom or is there anything else I need to do? Thanks for this method.
[Verizon Samsung Galaxy S III] silver04v:
I recommend ez recovery for the vzw sgs3. In play store. Allows you to flash twrp 2.2 or cwm touch and 6.xx?, best way to flash a recovery. And yes, just flash recovery after rooting with this tool.

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] tu3218:
Yeah I've heard about that. Is there a reason to do so over RM? Just wondering. And what do you recommend, twrp or cwm for this phone.
[Verizon Samsung Galaxy S III] silver04v:
I'm using twrp. Love it. It is only good for flashing non kexec roms. Anything with a kernal using kexec will not flash with twrp. So if you want to use those kind of ROMs you need to use cwm 6.xx (I forget the exact number). Also ez recovery just works. That's why I have used it.

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] tu3218:
Hmm okay. I'm sure I'll learn as I go along what rom is what. But is cwm good for any type of rom? I've always used cwm on all my phones so ill probably stick to that especially if it's good to flash any type of rom. Thanks for your help btw.
[Verizon Samsung Galaxy S III] silver04v:
Yea use the cwm 6.xx... Like I said I forget he numbers after the 6. But it's the only one with a 6 using ez recovery. That will handle any rom so far.

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] Cmotion:
I believe it's 6.0.1.0 if I remember correctly.
[Verizon Samsung Galaxy S III] enohand:
Great & quick easy to use "Rooter" tool.

however, for some reason i now have a "Custom" word & the Unlocked lock.

I did not have it for a few reboots, but then i installed Titanium BU & gave it root, & installed the pro version of Busy box with Smart install.

then rebooted & got the custom screen...

what does the custom screen even mean? i thought we only got that with a custom rom
[Verizon Samsung Galaxy S III] silver04v:
You flashed a recovery?

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] enohand:
no...where in my post did you see me mention anything about a custom recovery?

I used the utility.

then i installed Titanium BU

then i installed Busy Box Pro.

thats it
[Verizon Samsung Galaxy S III] silver04v:
I didn't but you can always leave stuff out so calm yourself. The custom screen comes up very random when system things are changed fyi. It goes away once returned to stock.

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] enohand:
dulley noted,.

however i did not.

the reason i posted was to find out what made the "custom" screen present itself. since i did not modify anything that should have triggered the custom screen. (unless Busy Box) triggered it.
[Verizon Samsung Galaxy S III] tu3218:
What is this custom screen?
[Verizon Samsung Galaxy S III] silver04v:
Busybox could have. It's not a big deal. Just go stock and its gone if you don't like it.

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] michael*:
I installed a system app (Cerberus) and when rebooting got the Custom + unlock image. I uninstalled and then re-reinstalled it and the Custom + unlock image went away. It seems some flag can get tripped with a system app install and the phone recognizes the change.

I suggest uninstalling Busybox and seeing if it goes away. If so, reinstall it and perhaps the 2nd time is the charm. If not, uninstall TB as well. Basically back up the process until the lock goes away and install one root app at a time until you see what is causing it.

I understand not wanting to see the unlock. With a little time and patience you'll figure out which app is causing it.
[Verizon Samsung Galaxy S III] Noxious Ninja:
Sorry if it seems I've been neglecting people... I got back from vacation and ended up being ridiculously busy at work. :(
[Verizon Samsung Galaxy S III] tu3218:
delete.
[Verizon Samsung Galaxy S III] spiderj:
Thank you for the clarification
[Verizon Samsung Galaxy S III] ihavenewnike:
It is not recognizing a Device

It is not recognizing my S3 what should I do?:(
[Verizon Samsung Galaxy S III] TechSavvy2:
Install the drivers....:)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Thank you for this tool, I successfully rooted yesterday and have SU installed as well as several other root apps. Two questions on unrooting manually for anyone to answer:

1) Does deleting: "/system/xbin/su" simply delete "/su" or the entire folder which is "/xbin/su"?

2) I have EZ recovery installed. When unrooting manually, I would return to stock recovery using this app then manually unroot correct?
[Verizon Samsung Galaxy S III] Hero:
1) It's worded kinda weird, but you will want to delete the file called "su" in the folder directory /system/xbin/ (Just so everyone knows, "su" == superuser binary. If the superuser app is having problems, update the "su" file).

2) Yes, that would work.

Nice to see more DInc people here lol
[Verizon Samsung Galaxy S III] recDNA:
And to get rid of security screen and return to stock for return all I need to do is flash an ota? Is this true even if using cwm recovery?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Haha appreciate the response and yeah its great seeing familiar names here. I'm making slow progress, just getting acquainted with the different names of files/recoveries and such. I'm doing as much reading as I can to stay informed.
[Verizon Samsung Galaxy S III] Muckrak3r:
Had the same problem, re-downloading and re-installing the drivers fixed it. Not sure why ;)

BTW - thanks Ninja! Great tool.
[Verizon Samsung Galaxy S III] omnicious:
Does this tool have an unroot option yet?
[Verizon Samsung Galaxy S III] pharrisworth:
Root VZW GSlll

Mitch

Thank You FINALLY something for Windows

$5.00 Donation

Patrick

pharrisworth
[Verizon Samsung Galaxy S III] aznguyen316:
bleh having issues on my VZW S3, using stock touchwiz blah blah.

ANyway, downloaded the file on first page. I have the samsung drivers installed and they work b/c I used it to backup my IMEI via QPST just earlier.

I put all the files into a folder onto my desktop, made sure to change the folder permissions to uncheck read-only (as that's what it had before and I searched this thread seeing this helped for someone). Anyway, reboot once, fine, second reboot fine and when it goes to testing superuser...

I DO NOT see this: "uid=0(root) gid=0(root)" as people say should be observed.

there's nothing after that, it just asks if uid and gid are 0, but I don't see anything from that question and from the "testing superuser" part. There's not information above the question to see any uid and gid numbers... I've tried it three times now different downloads and extractions... any ideas?

attached image.
[Verizon Samsung Galaxy S III] Picao:
I have tried this on 2 S3's and finally gave up. Went back to the original way by Odin and Root66. Just works but I cant figure out why the program never completes.
[Verizon Samsung Galaxy S III] eaglesfan398:
Does this root method and odin both work fine on the latest kernal version that currently ships with all the galaxy s3's?
[Verizon Samsung Galaxy S III] aznguyen316:
So Odin and Root66 method is okay? I guess I'll have to go that alternative route. Wanted the easy way. But I guess I'll have to try when I get home from work this evening.
[Verizon Samsung Galaxy S III] tillithz:
read what is above the screenshot text and look for the 0 or 1. this is normal nothing is wrong with this screenshot

yes.
[Verizon Samsung Galaxy S III] aznguyen316:
the problem is there is nothing above the screen shot text as you can see the windowbar of the command window there. The cmd box is not scrollable either. The first line of text is the "testing superuser" and then what you see is all there. There's nothing more to read...
[Verizon Samsung Galaxy S III] ihavenewnike:
Unroot method?
[Verizon Samsung Galaxy S III] droidstyle:
Flash back to stock with odin or use adam outlers casual all in one program.
[Verizon Samsung Galaxy S III] LXative:
I had the same problem after rooting. Disconnect your phone from USB, reboot your computer, reinstall the drivers (make sure your computer is connected to the internet). The computer will install and update the drivers, and you will be good to go.
[Verizon Samsung Galaxy S III] fafinaf:
Are there any Mac instructions? I'm on OS X 10.7.4 MacBook Pro. Thanks in advance. Didn't see anything regarding installation or guides for Mac users, hope it's ok I post here.
[Verizon Samsung Galaxy S III] lespaul0143:
Does this unlock the bootloader, too?
[Verizon Samsung Galaxy S III] aznguyen316:
I used the Casual to un root. Now I seem to get issues trying to re-root. The popups mentioned that I may have problems re-rooting. Is there anyway to be able to root again?
[Verizon Samsung Galaxy S III] mischiefse7en:
Worked just as you described it, THANKS!

EZ Unlocker in the play store
[Verizon Samsung Galaxy S III] Deadpool14:
I just bought a SIII yesterday and tried running this but I get a "protocol failure" error. Any ideas what could cause this? I have USB debugging enabled and it is loading up as a Camera device. It is also a US Cellular device and I have a baseband version LG4 (the guy at the store ran the update when I got the phone).
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Whenever I try to run the batch file it shows the menu and everything but at the bottom its says "You did not select and option. Exiting..." "Press any key to continue . . ."

Therefore I cant navigate to any of the 4 options and if i press anything It will just exit.

I have tried running it as admin but still doesnt work. I think there is a problem with running scripts that use cmd since the galaxy nexus toolkit I use also has a problem launching cmd.

Could someone please help me out? Im really trying to root my S3
[Verizon Samsung Galaxy S III] bby144:
ii
[Verizon Samsung Galaxy S III] BrUhNiGGs:
So I ran this on my other pc (laptop) and the batch file ran fine and I pressed 1 to root, I thought it was going good up until the point where it said there is no adb recognized in the internal or external. I have USB Debugging checked and Unkown Sources also. I have reinstalled the drivers multiple times and nothing worked. I confirmed in the device manager that it shows my s3 as an adb interface. So I dont know why I am getting this error. I need to root my S3 but I cant find a way!
[Verizon Samsung Galaxy S III] Ratzinc:
Worked perfectly, followed the instructions to a t
[Verizon Samsung Galaxy S III] eman3316@optonline.net:
So for the Verizon version it is the file in post 1, right?

Also, for unlocking the bootloader, there is no newer bootload that might be on my phone that I received yesterday that I should be worried about, is there?

Can someone please post the latest bootloader or something I can check before unlocking?

Thanks!
[Verizon Samsung Galaxy S III] gatewayad:
Perfect.... Thanks so easy a Caveman could do it :)

---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------

http://rootzwiki.com/topic/32456-app-ez-unlock-easiest-way-to-unlock-your-bootloader/
[Verizon Samsung Galaxy S III] lespaul0143:
It just keeps hanging at "Waiting for device to be detected".

I've tried every usb port, reinstalled drivers, triple checked unknown sources and usb debugging... and still, it just hangs.

EDIT: I just kept trying and it eventually worked.
[Verizon Samsung Galaxy S III] keymaster911:
On your first post.. There is 2 downloads. With one do i download first and last. Going to be running clean rom tomorrow hope. If i dont brink my phone first.

Sent from my SCH-i705
[Verizon Samsung Galaxy S III] jncokilla:
I did everything as it said. Still No Root. I restarted it 2 times. now what Please Help Me
[Verizon Samsung Galaxy S III] FrostyOrDie:
This is my first Samsung and I'm not used to these methods of gaining root. is this method still working with the most recent software?

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] Hulk0069:
I just rooted my phone, with the ops beginning thread,I followed it to the tee, oh I tried it , the first time nothing second time it worked just give it time (your computer) to recognize your phone, make sure you follow the instructions.you be ok.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
All you need to download is the Samsung USB driver and the root Debug tool R2. Download the Debug R2 tool underneath the Credits in the OP.

Yes. There are only two software versions of the VZW GSIII: VRLF2 and VRLG1. The second one being the most up to date HOWEVER it hasn't been pushed as an OTA. This root method is really not difficult so long as the driver installs and you follow the directions.
[Verizon Samsung Galaxy S III] Galloway:
Awesome Tool!!!!

Just confirmed this still works on the newest Canadian LH1 firmware for SG3 I747M! Awesome job and thanks!!! Donation will be going to devs come pay day (funds are a little low right now), did just send some to Noxious Ninja now though :)
[Verizon Samsung Galaxy S III] FrostyOrDie:
I just got a factory replacement with the latest VRLG1. just wanted to make sure. Thank you.

Sent from my SCH-I535 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S III] FrostyOrDie:
this was the easiest root method I have ever encountered. I almost dont believe that just happened and need to continue looking for a root method that makes me wanna pull my hair out like all the HTC and Motorola devices I've done.
[Verizon Samsung Galaxy S III] sd5500:
I seem to be stuck at;

Step 1 - setup...

Copying Files:

Copying su:

been like this long time.

ok, update. It went through on 2nd attempt, but ez-unlock gives me a balnk white screen after install from playstore. Says not responding. Does this mean I'm not rooted?

Ok, I'm good. Needed ez-unlock to have su permission.
[Verizon Samsung Galaxy S III] silver04v:
Did you deny su permission when it started the first time by accident? Go to superuser app and go to ez unlock, click on it and forget. Then go into app and try again?

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] atoy74:
I'm a little lost. I stared the process normally, adb recognized the device and I'm stuck at step 2 -

ECHO Step 2 - Rooting...

ECHO.

ECHO If you see the following error, you may ignore it:

ECHO.

ECHO rm: File not found by ext2_lookup while trying to resolve filename

ECHO.

ECHO This just means there wasn't an existing root found on your phone.

It was on that screen for an extraordinarily long time. I restarted adb and tried the process again. Now I get to the initial "Waiting for device to be detected..." and nothing happens.

I've also done the adb devices command which states "List of devices attached" but no longer shows me a device. More specifically it's not showing my vendor number, or anything in general. It was before.

I've restored back to factory but the issues continue.

Any help would be appreciated.
[Verizon Samsung Galaxy S III] silver04v:
Is unknown sources and usb debugging still checked on?

Sent from my Synergized vzw S3!
[Verizon Samsung Galaxy S III] atoy74:
Yeah, I've triple checked.

---------- Post added at 10:52 PM ---------- Previous post was at 10:26 PM ----------

Seems my device not being listed in ADB was caused by MTP. So, thats fixed and good news.

The bad is i'm still getting stuck on step 2. I tried running the commands manually and the process seems to stop at

adb shell toolbox chmod 777 /data/local/debugfs

Anyone know why that would happen there?

---------- Post added at 11:27 PM ---------- Previous post was at 10:52 PM ----------

On a hunch, I tried this on a 32bit Win7 machine. Success!
[Verizon Samsung Galaxy S III] juancaperez2000:
hey noxius i remember that you said that you will try to work on unroot tool like this one, are you still having that i your plans, thanks
[Verizon Samsung Galaxy S III] cnlson:
VRAGL7

So the OTA came in last night and I accepted it. So i lost local search and root.

rerooted using this and can confirm it did work.

only thing i noticed is that it seems like this *sever not running*

did not show up before. not sure if it is significant or not. but did think you might want to know.

now on to reflash local search and maybe google now on
[Verizon Samsung Galaxy S III] steveo11284:
I can confirm this works just fine on the latest OTA update as well. I didn't notice the *server not running* thing. Either way, I now have root again w/o any issues!
[Verizon Samsung Galaxy S III] xsteven77x:
Still a great tool even on latest OTA ty.
[Verizon Samsung Galaxy S III] eaglesfan398:
Unroot

Is there any news on a possible unroot method?

---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------

Were you rooted before you accepted the update via this method or did you unroot first?
[Verizon Samsung Galaxy S III] alphis:
Very nice. The root is made possible by using the tmp directory trick. My only question is about that debugfs binary. Is it essentially a busybox like program? allowing a copying (via write) etc? Who made this debugfs program?
[Verizon Samsung Galaxy S III] h311sdr0id:
I have always seen the "Server Not Running" for the most part when I use this tool. BUT, it still WORKED
[Verizon Samsung Galaxy S III] crackerhacker:
I have rooted 3 different sgs3 with this method and they have all said server not running when it reboots but it works fine and have not had any problems with the tool.
[Verizon Samsung Galaxy S III] ooofest:
Would you mind possibly adding this info to the original post? It works easily, but I had to search for it in order to recall your instructions from the last time I rooted/unrooted :) .

BTW, I also confirmed that the 07/24/2012 version of your root package successfully rooted a phone that was stock and had been updated by Verizon with their September OTA.

Thanks,

- ooofest
[Verizon Samsung Galaxy S III] savesheep:
Quick question - I have TWRP 2.2 installed, did the update and it rebooted to recovery. I assume it did not finish since TWRP didn't know what to do with the restart. Any ideas where the update file is stored on the internal memory? Or should I flash stock recovery to do the update. (if so, where can i find stock recovery). Thanks!

---------- Post added at 11:38 AM ---------- Previous post was at 11:29 AM ----------

Figured it out. Used EZ-Recovery off the android market to flash stock recovery. Update is taking right now. Does this mean the phone will need to be re-rooted?
[Verizon Samsung Galaxy S III] SpunkyXL:
sweet..thanks
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If your phone upgrade to the latest OTA successfully, yes you need to re-root if you want to use any roms/kernels/mods. Just know, it's rather pointless to go stock if you're just going to root and flash another rom.
[Verizon Samsung Galaxy S III] pharrisworth:
Latest OTA update Failed

I've been rooted for a couple of months using Ninja's Toolkit, Now the latest OTA from Verizon Failed with error 402. Seems odd that I would need to unroot for the update to work. I'm used to it removing root from a phone, and then having to re-root.

Ideas anyone? phone works just fine as it is, but if the 4.1 update come out, I DO want that one Ü
[Verizon Samsung Galaxy S III] eaglesfan398:
I didn't un root when I took the ota updates. It worked fine. But then again the update for me was only 30 mb cause my phone had an updated sticker. At least that is the reason why but don't quote me on it.
[Verizon Samsung Galaxy S III] ooofest:
Did you install a custom recovery, perhaps?

- ooofest
[Verizon Samsung Galaxy S III] pharrisworth:
No, I installed Verizon boot unlocker application, but never used it. The update gets about a quarter of the way through and then dies.

The system reports error 402, and I can't find a darned thing about it. I don't think unrooting it is going to help.
[Verizon Samsung Galaxy S III] Fstall303:
Tried this method. Debugging and allow outside sources both checked. Never roots. Takes me to this screen . Any ideas?
[Verizon Samsung Galaxy S III] pharrisworth:
Check out the last couple of posts here

http://xdaforums.com/showthread.php?t=1842313&page=2

pharrisworth
[Verizon Samsung Galaxy S III] ooofest:
I rooted and unrooted a couple times using Ninja's methodology before accepting the OTA, so I was essentially back to stock when the notice arrived. It installed without an incident, fortunately.

I don't see why unrooting would be needed, either - but, it can't hurt to try. Unrooting is remarkably quick and painless using Ninja's method.

- ooofest