What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[HACKS] [Toolkit] Nexus Root Toolkit v1.6.0 [Updated 11/26/12]

Sounds like you might have some file/folder path issues as I did. Turns out that I had two different SDK folders (one on my SSD, Windows 7 operating system drive, C:, and one on my User Data/Files drive, X: ). Once I merged the contents into the C: path, tool worked great.

I honestly am not sure of how to do that. I did a search for SDK but it is all on C:, no other drives. I'll try it on my wife's computer when I get home.
 
I've gone through the instructions for Part 1 at least 20 times now. Instead of seeing "Mobile ADB Device" as mentioned, I'm seeing "Android ADB Interface". When I enter "adb devices" in the CMD prompt, this is the message it says ADB is not recognized. I'm running 32 Bit Windows 7.

Still no success with a different computer. The same exact problem.
 
This topic hopped to life with 4.0.4. Im glad to see some more posts. Having some reservations. I should really just try it, but with a nickname like splat. Lol
 
Still no success with a different computer. The same exact problem.

Use the system variables button on version 1.3 to update your systems path variable and reboot your comp. Or just use the list devices button in the program.

{{ WugFresh }}
 
I honestly am not sure of how to do that. I did a search for SDK but it is all on C:, no other drives. I'll try it on my wife's computer when I get home.

Version 1.3 doesn't require or rely on the sdk. Everything the program needs is localized to the extracted directory.

If you want to use adb cmds globally from the cmd line, then use the system variable button and reboot... otherwise everything is already localized. The program will work without this option.

{{ WugFresh }}
 
Hi Wug,
My phone was never rooted or flashed, but yesterday I found it in a boot loop. Just the word Google flashing every 15 seconds on a black screen with the battery heating up. It was suggested the I try to use your root tool to load drivers and flash to 100% stock. Unfortunately, I can't load a driver because the phone is showing up as "OMAP 4440". Tried to manually install, but that did not work either. Do you think my phine is history?

Thanks,
Rick
 
I just wanted to mention one other thing. I tried to do a factory reset and all I got was a picture of Andy on its back with a door open and a triange with a "?" in it. So even a factory reset failed.

Rick
 
Perfect

Just got my phone last night, ran Wug's install process and all is GREAT.

Donation sent. Thank you for such a simplistic process.
 
I just wanted to mention one other thing. I tried to do a factory reset and all I got was a picture of Andy on its back with a door open and a triange with a "?" in it. So even a factory reset failed.

Rick

When you see that, to get into stock recovery you have to then short press both volume buttons and the power button.

My http://www.wugfresh.com/dev/gnex-root-toolkit/manual-driver-configuration/ instructions include information about removing devices first. You would have to uninstall that omap device first.

As long as you can get into bootloader mode you will be able to use my toolkit, otherwise you would want to use ODIN.

You are trying to configure the fastboot drivers, meaning having your computer recognize your device as an adb device when its in bootloader mode. Step two of those instructions I posted should help you out.

If not, add me on gchat and I can try to help you out when I am available.

{{ WugFresh }}
 
Back
Top