Wug's Nexus Root Toolkit v1.6.3 [Updated 02/24/13]

[WugFresh]

Ok, so please excuse me for what might be a dumbquestion, but I am having problems with rooting.

So here is what I did/do:
Installed GnexRootToolkit.sfx.exe
Ran “Driver + SDK”
Now I have “SAMSUNG Android ADB Interface” in the devicemanager
Then, I go with “ Unlock and Root”
The phone reboots and I get DOS window asking if I seedevice, which I do.
Then it says “waiting for the device” and “press yes,”while the device had a menu with “Start”, “Restart Bootlog” and something elsethat I do not remember… but what do I do next?

Thanks!

You successfully set up the Samsung android adb interface for when the the phone is on. However when the phone boots into bootloader.. the driver is probably not successfully configured. So when it asks you if the device is configured.. you should say "no". And then have it configure for you. you can restart the unlock zip and try again doing that.

You will never get "waiting for device" if all the drives are completely configured.

I am silly for including more driver configuration in the "Unlock and Root" portion of this program. I am going to change that in the next release. Driver configuration isn't complete until you configure it with your phone in bootloader mode.

{{ WugFresh }}

[ImRickJamesSnitch]

You successfully set up the Samsung android adb interface for when the the phone is on. However when the phone boots into bootloader.. the driver is probably not successfully configured. So when it asks you if the device is configured.. you should say "no". And then have it configure for you. you can restart the unlock zip and try again doing that.

You will never get "waiting for device" if all the drives are completely configured.

I am silly for including more driver configuration in the "Unlock and Root" portion of this program. I am going to change that in the next release. Driver configuration isn't complete until you configure it with your phone in bootloader mode.

{{ WugFresh }}

Ok. I'm on Win XP. I know... But when I try to install the driver it can't install. I search for the Samsung driver "Samsung Android Phone" Is that the drivers name. I'm this close, I needs you Wug.

[gregg0829]

Ok. When i connect my phone it is not recognized. I am going to wait and dl wugs update when he releases it .

[WugFresh]

Ok. When i connect my phone it is not recognized. I am going to wait and dl wugs update when he releases it .

That is a good idea. :-)

{{ WugFresh }}

[jerroedr]

up and running!

[jerroedr]

i hate full wipes

[jkeben]

Has anyone looked at the adb backup instructions on xda... apparently with that you can back up your device before you unlock the bootloader

[WugFresh]

Ok. I'm on Win XP. I know... But when I try to install the driver it can't install. I search for the Samsung driver "Samsung Android Phone" Is that the drivers name. I'm this close, I needs you Wug.

To be honest, I haven't tried fully configuring drivers on xp yet. I was hoping you guys would have 7 or crap vista by now. Lol. You all do have the latest smart phone technology, why still xp!? Ok.. I am just teasing. I will look into better xp support.

People should give me tonight to work on an update.

K?

{{ WugFresh }}

[TMFGO45]

okay, so I have this thing up and going. I think I am having the same problem as the guy earlier. I do the steps in order, but when I get to the part where I need to select yes on the phone to start the unlock process, I don't have that option. And the unlock program from wug says waiting for device as well....

Is this part supposed to be automated?

According to the unlock program, I also have all the drivers installed correctly. And I am also on Windows 7...I am not to sure what is going on here.

WUG!!!!!! HELP ME!!!!!!!!

[w0wbagger]

Hey Wug, I'm sure you're being inundated with people wanting your help getting this to work for them. In my case, it seems to have worked, but I get the following message when I start up Titanium Backup after rooting via your program: "Warning: Your ROM is rooted by the "su" binary has non-optimal access rights, which may cause problems. Titanium Backup Pro can fix this problem automatically in many cases. Do you want to proceed?"

Any idea why the su.zip you included might not have optimal access rights? Thanks heaps for any insight you might provide.
Cheers.