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

[WugFresh]

Very nice! Thanks very much for all of your hard work. I'll give the "D" a try today and see how it goes. But, in regard to my second question: is the question to determine what is going to be put on the phone or what's on it prior to running your utility? In other words, if I do the "D" build, will that flash "D" onto the phone?

It's asking what build is currently on your phone, not what you want it to be. Rooting is just a process of gaining full directory structure access, so it has nothing to do with changing your build. By selecting "D", the toolkit will simply be able to root your "K" device. The reason the toolkit asks what build you are on, is because the toolkit currently utilizes a modified boot.img (specific to whatever build you are currently on) to enable running privileged commands and ultimately be able to push the Superuser app and binary to your device (that D modified boot.img happens to work on K builds as well).

That said, if you were to flash stock with the toolkit (Flash Stock + Unroot button), it would flash IMM76D... but that's only because its the only thing available; For whatever reason, Google nor Sprint provides any of the factory images for that device officially. Because of that, I packaged an unofficial IMM76D factory image package using a smorgasbord of leaked fastboot image files, for the toolkit to utilize (when flashing stock), for the sprint device. All other devices in the toolkit utilize the official Google factory image packages, which google regularly updates to the latest builds. Sprint owners do not have that luxury, unless they start petitioning sprint, or hoping more images get leaked.

More information on my unofficial sprint factory image package can be found here; [Unofficial] Sprint Factory Image Package | WugFresh

A user uploaded the sprint IMM76K OTA update.zip to my servers I think, but I haven't had a chance to look at it yet. There is a chance I will be able to make a new unofficial sprint package (IMM76K). For now, the end user would have to flash the D package, and then take an OTA to K... but again this only pertains to flashing stock, not to rooting. Hope that clears things up for you. Cheers.

{{ WugFresh }}

[tkarakashian]

It did, and I'm good. Got 'er unlocked, rooted and running MIUI without a hitch. Thank you!

[maxal]

Any news on v1.5.3 yet?

[macutan]

Hi All,

Newbie here to the world of unlocking Android. I'm on a windows 7 64bit machine.

I have been trying to unlock and root my Nexus 7 (Build JRO03D) using the Nexus Root Toolkit v1.5.2 and while the Unlock process seems to work fine when I go and try to Root (using the "Do not flash CWM" option) the process gets stuck on step where it restarts the Tablet (Screen on PC shows "Rebooting your device into bootloader "; while on tablet it shows the recovery screen with small writing on the top left displaying "Booting Downloaded Image", also the tablet does not seem to have any response when I hit the volume or the power buttons on while on that screen). In order for me to kick the tablet out of that unresponsive state hold the power button for a few seconds until it restarts. After kicking the tablet out of this unresponsive state the root seems to continue as the PC displays that powerSU is being pushed, and other applications are being installed on the Tablet.

Once this process is over, I try to find Power SU on the device but it seems the only package that was installed is " Busybox". I install Power SU from Play Store but when I run it a pop up appears saying "there is no su binary installed and supersu cannot install it. this is a problem".

Has anyone experienced this same problem and has been able to fix it?

I have Flashed Stock + unroot a bunch of times and redid the same thing unsuccessfully. What am I doing wrong?

Thanks for any guidance.

macutan

EDIT: Somehow I just tried again (after 5 or 6 times) and it WORKED. I didn't do anything different. Would still be curious if someone has a solution other than keep re-trying. Thx

[patr1ck]

question, i used this toolkit when i first rooted my phone, thanks again btw, it made the process nice and simple for me.

after rooting superuser and busybox were installed.

i've since flashed to a different rom and now i dont have busybox. my question is, do i need busybox? i know i'm still rooted so whats the point? but then i wonder why when using your toolkit it installed both. makes me think i should have it.

[11knives]

I have been trying to unroot and flash the stock rom for my gnex cmda using toolkit V1.5.2. Basically I can get the toolkit to lock and unlock the bootloader, and flash what it say will be 4.0.4. Once I reboot, I'm still on 4.0.2 and rooted. What is the problem??? I came from aokp JB nightly, and I have a dead radio so I want to return to VZ store but want to remove root and CWM first. I thought this would be an easy fix... been at it for 3 hours now. ahhhh

[Xander]

Hi

First thing I got to say is thank you for that Tool even a complete NOOB like me is capable to work whit his Phone!
If he does things right :-)

Iīve a Galaxy Nexus and used Nexus Root Toolkit v1.5.2 to unlock and root, no problem there.
But if I try the Flash Stock+Unroot Button to flash Androit 4.0.4 IMM76I on my Phone nothing happens.

To be specific my Device: MAGURO ID: IMM76K Product: yakjuxw Adroid 4.0.4 so I cantīt get a OTA Upgrade to 4.1.1
I thought I flash 4.0.4 yakju and get OTA Upgrade to 4.1.1 but if I hit the Stock+Unroot Button select Android 4.0.4 IMM76I and Automatically download+extract the factory image selected above for me.
The Download startīs it finishes and then nothing happens. Download Status is complete but no Hashcheck happens or any other Steps where made.
Iīve been waiting 30 minutes (since I know that patience is not my strength), but nothing.
Then Iīve been downloading this image yakju-imm76i-factory-8001e72f.tgz from https://developers.google.com/android/nexus/images?#yakju here and tried it with Other/Browse entered the MD5 Checksum 31447212fb4fb00aab4ef8bdc78e7ffb and nothing happens.
Iīm sure the failure is on my side but I donīt know what else to do!

[kevin95]

I just downloaded this tool and I was planning to back up all my phone data but when I connected it and attempted to back up my contacts by following the instructions on the screen, a window popped up saying "ADB Device not found". How do I fix this?

[ManDroid]

I admit to not going through every single post, but I'm stuck on step #3 (When it launches select your model type).
About phone says Android version 4.0.4, Build number IMM30D.
In the toolkit, Under Galaxy Nexus: GSM Models, that build is not listed.

[WugFresh]

I admit to not going through every single post, but I'm stuck on step #3 (When it launches select your model type).
About phone says Android version 4.0.4, Build number IMM30D.
In the toolkit, Under Galaxy Nexus: GSM Models, that build is not listed.

Select the imm76d build. I didn't know there was an IMM30D build for gsm gnex. If you still have problems, wait for v1.5.3 to be released. I am finalizing it now and I am on schedule to release it today.

{{ WugFresh }}