[Toolkit] Wug's Nexus Root Toolkit v. 2.1.9

Search This thread

gulo101

Member
Oct 4, 2010
19
0
Colorado Springs
I am not sure what the best course of action would be in your circumstance as I am not aware of a method for unpacking those ab files. Maybe try downloading that "Where's my water" app first, running it once, rebooting, airplane mode.. and then try again. This is just a troubleshooting idea... not sure why it would work.. but maybe having the app already on there would get you past that hurdle.

{{ WugFresh }}

yeah, I tried that too, same thing. it always stops at the same spot, wish there was some way to skip that app
 

Pariah3000

Member
Aug 16, 2012
33
4
I can finally post my thanks (stupid post minimums).

This tool kit has been indispensable. I used it to root my Nexus 7 and a couple times to recover it after a bit of failed shenanigans. Thank you for all the hard work WugFresh!
 
Last edited:

Doritos Bandito

Senior Member
Apr 10, 2012
95
4
Verizon finally pushed the official jelly bean update through JRO03O but that one isn't listed as one of the choices. So which one would be alright to choose?

Sent from my Galaxy Nexus using Tapatalk 2
 

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
Verizon finally pushed the official jelly bean update through JRO03O but that one isn't listed as one of the choices. So which one would be alright to choose?

Sent from my Galaxy Nexus using Tapatalk 2

I noticed that last night. I am working on v1.5.4 with that for sometime next week. For now choose "Any Build" in the pull down. By next week the toolkit should have official support as well as some other small fixes.

I also have an interesting plan for v1.6 that in theory should make the toolkit support all android devices with unlockable bootloaders that can utilize fastboot, without me updating the toolkit per device. :) I hope I can make my idea into a reality.. some of it is already coded at this stage. Stay tuned.

{{ WugFresh }}
 

landstander

Senior Member
Nov 2, 2009
233
33
KC metro area
I am not sure what the best course of action would be in your circumstance as I am not aware of a method for unpacking those ab files. Maybe try downloading that "Where's my water" app first, running it once, rebooting, airplane mode.. and then try again. This is just a troubleshooting idea... not sure why it would work.. but maybe having the app already on there would get you past that hurdle.

{{ WugFresh }}

The latest update to Titanium Backup, released just yesterday, can supposedly restore items from ADB backups... including encrypted backups. I believe that you need to purchase the Titanium Backup Pro Key, however, in order to enable this feature.

Disclaimer: Both of my Nexus devices have been rooted for quite some time, so I haven't had any need to test this new capability personally.
 
Last edited:

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
The latest update to Titanium Backup, released just yesterday, can supposedly restore items from ADB backups... including encrypted backups. I believe that you need to purchase the Titanium Backup Pro Key, however, in order to enable this feature.

Disclaimer: Both of my Nexus devices have been rooted for quite some time, so I haven't had any need to test this new capability personally.

Sweet. Thanks for the info. I actually have TitaniumBackupPro, it's a great app. I will try it out next time I get a chance.

{{ WugFresh }}
 

emylia777

Senior Member
Jun 24, 2012
107
22
hi WugFresh, 1st of all, thanks for the nice and simplest toolkit for us to root our beloved N7.

But I'd like to report the low success rate in rooting the JRO03S build. It made the N7 randomly stucked in bootloader mode. This was done on a successfully-installed PDAnet driver and 'Any Build' was chosen on the toolkit. Just want you to know, perhaps there's another workaround for this.

I, on the other hand, however managed to get my JRO03S build rooted with ur toolkit despite it being few times stucked in bootloader. Changing the USB ports did the trick. It's weird I know but that did the trick. Perhaps this info would let you improve this great toolkit in your future versions. :victory:
 

arkhan11

Senior Member
Mar 7, 2011
130
210
/data/app
fpira.com
hi WugFresh, 1st of all, thanks for the nice and simplest toolkit for us to root our beloved N7.

But I'd like to report the low success rate in rooting the JRO03S build. It made the N7 randomly stucked in bootloader mode. This was done on a successfully-installed PDAnet driver and 'Any Build' was chosen on the toolkit. Just want you to know, perhaps there's another workaround for this.

I, on the other hand, however managed to get my JRO03S build rooted with ur toolkit despite it being few times stucked in bootloader. Changing the USB ports did the trick. It's weird I know but that did the trick. Perhaps this info would let you improve this great toolkit in your future versions. :victory:

my N7 is a C90 model and came with JRO03S out of the box. I did not used the manual root guide (because of some issues in sdk setup) neither the easy tool from WugFresh. I merged both solutions using the tool to install driver, then continuing with the manual guide which is the same for any Android release. I wrote a pdf you can download from my signature.
The reason it stucks on bootloader during the procedure is a bug in the N7 bootloader. More details in the pdf.
Thanks to WugFresh for the tool :)
 

raywaldo

Senior Member
Jul 8, 2007
805
106
Southeast Louisiana
raywaldo.com
USB 3.0 ports

I, on the other hand, however managed to get my JRO03S build rooted with ur toolkit despite it being few times stucked in bootloader. Changing the USB ports did the trick. It's weird I know but that did the trick. Perhaps this info would let you improve this great toolkit in your future versions. :victory:

If you were using a USB 3.0 port, that may have been the problem.

I have experienced several issues with some devices linking via any of the 3.0 ports on my laptop. The same devices work great with my (ONLY) 2.0 port.
 

arkhan11

Senior Member
Mar 7, 2011
130
210
/data/app
fpira.com
If you were using a USB 3.0 port, that may have been the problem.

I have experienced several issues with some devices linking via any of the 3.0 ports on my laptop. The same devices work great with my (ONLY) 2.0 port.

That's REALLY interesting. It could be the cause. I don't have any usb 3.0 port on my computers.
The reason could be in usb 3.0 standard specification. I'll do some searching. If I have new, I'll post here :)
 
  • Like
Reactions: raywaldo

old_fart

Senior Member
Dec 8, 2011
1,484
400
it never rains here
If you were using a USB 3.0 port, that may have been the problem.

I have experienced several issues with some devices linking via any of the 3.0 ports on my laptop. The same devices work great with my (ONLY) 2.0 port.
.
Its never good to make 'broad' statements. Maybe it would be important to talk about a specific brand or the 'chipset' used. . More data plz, Ray.
.
The ccleaner folks, Piriform have a nice tool, speccy.
 

raywaldo

Senior Member
Jul 8, 2007
805
106
Southeast Louisiana
raywaldo.com
generalized statements

.
Its never good to make 'broad' statements. Maybe it would be important to talk about a specific brand or the 'chipset' used. . More data plz, Ray.
.

You are correct about the need for more specific data. However, the occasions when it happened, I was more focused on fixing the issue than with recording the data so I did not keep good notes. Remember, I am a couple years older than you - and probably more forgetful.:D

However, I believe that it is better to mention the POSSIBILITY (note that I did not make any definite statements) of the problem than it is to ignore the possibility. Now, others may also be observant of the possible issues and someone (like arkhan11 above) may discover whether it really is an issue.

Who knows, maybe a noob with a problem may try changing ports and fix their problem! :cool:
 

SharpIS03

Senior Member
Dec 17, 2010
406
56
Koshigaya
This toolkit rocks! Really easy to follow with the popups, really quick too! I ordered my Nexus 7 in Japan, C90 with build JRO03S. Used the "Any Build" option. Thanks a lot!
 

arkhan11

Senior Member
Mar 7, 2011
130
210
/data/app
fpira.com
.
Its never good to make 'broad' statements. Maybe it would be important to talk about a specific brand or the 'chipset' used. . More data plz, Ray.
.
The ccleaner folks, Piriform have a nice tool, speccy.

You are correct about the need for more specific data. However, the occasions when it happened, I was more focused on fixing the issue than with recording the data so I did not keep good notes. Remember, I am a couple years older than you - and probably more forgetful.:D

However, I believe that it is better to mention the POSSIBILITY (note that I did not make any definite statements) of the problem than it is to ignore the possibility. Now, others may also be observant of the possible issues and someone (like arkhan11 above) may discover whether it really is an issue.

Who knows, maybe a noob with a problem may try changing ports and fix their problem! :cool:

Ok, as I promised here's what I found.
debug was a specific made for serial ports and, as USB is a serial port. it works on ANY usb 2.0 port.
it seems you cannot use this feature in 3.0 ports if your pc has at least one USB 2.0 port (it means not native usb 3.0 controller). It could be related to the need of speed increasing within the 3.0 standard. IIRC, it was difficult to make the usb 3.0 standard retro-compatible with 2.0.

I've also found that "Debugging over a USB 3.0 connection requires the following hardware:
A USB 3.0 debug cable. This is an A-A crossover cable that has only the USB 3.0 lines and no Vbus.
USB 3.0 host controllers on the host and target computers."
(as written here http://social.msdn.microsoft.com/Forums/en-US/wdk/thread/74a03abb-ef5f-4e2a-8f27-e2282d56a986)
and that windows 7 CANNOT debug over usb 3.0 ports, that feature will be added in windows 8, as written here (http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx):
"New for Windows 8
We have added support for debugging over a network connection or a USB 3.0 connection"
Anyway it depends ALSO on the controller (www.ti.com/analog/docs/microsite.tsp?sectionId=590&tabId=2276&micrositeId=11)

So, let's summarize:
1) you need debug support on your usb 3.0 controller (if your PC has at least one 2.0 port, connect it there. it won't work on 3.0 ones)
2) there are no PCs with only usb 3.0 ports (neither ultrabooks) so where's the problem?
3) if you like windows, you have to wait windows 8 as windows 7 doesn't support debug over usb 3.0 as above (again use 2.0 ports, it's not bad!)
3) if you like linux... don't know! I love Linux but let's talk about it when there'll be only 3.0 ports around
4) if you got the latest macbook air/pro/retina, it's another story (2012 released have only 3.0 ports)
:)

Sorry if it is not a full-detailed explanation but I'm not an electronic engineering. Anyway, it gives us an idea why in described scenarios it does not work.

sources
http://stackoverflow.com/questions/9663719/usb-debugging-on-galaxy-nexus-causes-windows-7-to-freeze
http://pete.akeo.ie/2011/08/do-necrenesas-upd720200-based-usb-30.html
http://www.coreboot.org/EHCI_Debug_Port#Finding_the_USB_debug_port
http://www.google.it/url?sa=t&rct=j...sg=AFQjCNHFwNGEy8a58wmB5xAqhRnKPcB97A&cad=rja
http://channel9.msdn.com/Events/BUILD/BUILD2011/HW-258P
 
Last edited:
  • Like
Reactions: raywaldo

raywaldo

Senior Member
Jul 8, 2007
805
106
Southeast Louisiana
raywaldo.com
USB 3.0 ports

Ok, as I promised here's what I found.
debug was a specific made for serial ports and, as USB is a serial port. it works on ANY usb 2.0 port.
it seems you cannot use this feature in 3.0 ports if your pc has at least one USB 2.0 port (it means not native usb 3.0 controller). It could be related to the need of speed increasing within the 3.0 standard. IIRC, it was difficult to make the usb 3.0 standard retro-compatible with 2.0.

I've also found that "Debugging over a USB 3.0 connection requires the following hardware:
A USB 3.0 debug cable. This is an A-A crossover cable that has only the USB 3.0 lines and no Vbus.
USB 3.0 host controllers on the host and target computers."
(as written here http://social.msdn.microsoft.com/Forums/en-US/wdk/thread/74a03abb-ef5f-4e2a-8f27-e2282d56a986)
and that windows 7 CANNOT debug over usb 3.0 ports, that feature will be added in windows 8, as written here (http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx):
"New for Windows 8
We have added support for debugging over a network connection or a USB 3.0 connection"
Anyway it depends ALSO on the controller (www.ti.com/analog/docs/microsite.tsp?sectionId=590&tabId=2276&micrositeId=11)

So, let's summarize:
1) you need debug support on your usb 3.0 controller (if your PC has at least one 2.0 port, connect it there. it won't work on 3.0 ones)
2) there are no PCs with only usb 3.0 ports (neither ultrabooks) so where's the problem?
3) if you like windows, you have to wait windows 8 as windows 7 doesn't support debug over usb 3.0 as above (again use 2.0 ports, it's not bad!)
3) if you like linux... don't know! I love Linux but let's talk about it when there'll be only 3.0 ports around
4) if you got the latest macbook air/pro/retina, it's another story (2012 released have only 3.0 ports)
:)

Sorry if it is not a full-detailed explanation but I'm not an electronic engineering. Anyway, it gives us an idea why in described scenarios it does not work.

sources
http://stackoverflow.com/questions/9663719/usb-debugging-on-galaxy-nexus-causes-windows-7-to-freeze
http://pete.akeo.ie/2011/08/do-necrenesas-upd720200-based-usb-30.html
http://www.coreboot.org/EHCI_Debug_Port#Finding_the_USB_debug_port
http://www.google.it/url?sa=t&rct=j...sg=AFQjCNHFwNGEy8a58wmB5xAqhRnKPcB97A&cad=rja
http://channel9.msdn.com/Events/BUILD/BUILD2011/HW-258P

-------------------------------------------
---------------------------
That is some VERY IMPRESSIVE researching!! Thank you!!! :highfive:
----------------------------------------------------------------------
 
  • Like
Reactions: arkhan11

arkhan11

Senior Member
Mar 7, 2011
130
210
/data/app
fpira.com
-------------------------------------------
---------------------------
That is some VERY IMPRESSIVE researching!! Thank you!!! :highfive:
----------------------------------------------------------------------

I hope it will be useful for other people now I sorted it out.
If you think it's good, feel free to share the link to this post when it's necessary :)

Sent from my Nexus 7 using xda app-developers app
 
Last edited:

demandarin

Senior Member
Apr 7, 2010
7,021
2,038
Alexandria, Va
need help with nagging issue trying to revert back to stock.

As long as you can get into bootloader mode, then you can restore your device from a soft brick. The "Flash Stock + Unroot" button with "can't boot up" option checked will instruct you how to restore your device when you are stuck in a bootloop, or the google logo.. etc.

{{ WugFresh }}

Do you know of a solution was ever found to people getting stuck in various places trying to revert back to stock? I have a 2nd nexus 7 that got borked ssomehow trying to revert back to stock. I can bring up bootloader/fastboot screen. When I run the flash stock/unroot and can't boot up option, it runs. It'll seem to do everything right initially. Then towards the end it'll get stuck on sending boot.img or system img. IVE tried basically everything. Uninstalled drivers, re-installed them, different cables, different PC ports, different toolkits, etc.. I even tried manual method through ADB. No matter which method I try, they all get stuck on same part. Its crazy how it'll go fine for majority of process then get stuck. There are several others who had exact same issue. I know I had proper drivers installed. Also have the Android SDK with all platform tools installed. I was especially disappointed when even manual adb method got stuck on same part. I heard some people got it to work by using another computer bit that's not an option for me atm as i don't have another PC. Any insight as to what may be happening? I know, at least Initially, adb commands being pushed are working. As it'll reboot tablet or show signature match on top of nexus screen. But whenever it gets down to end topart where its sending extracted files(tTHST program extracts itself) it gets stuck on various portions. I know they say sending system.img can take a while but mines gets stuck. Never finishes no matter how long I leave it. Things like flashing stock recovery and stuff work as the nexus 7 takes it.

I must have a really bad soft brick..lol my only hope it seems is THST as least bootloader screen shows and my nexus 7 intiallu takes commands.

One other quick question. I eventually got frustrated with it and relocked it with adb command. Another piece of evidence showing adb and drivers working correctly. I was going to send it in to Google but haven't yet. Since my tablet is in the state its in(stuck on google screen. Never boots up. Likely do to previous wiping trying to revert back to stock with vsrious tools), could I use your tool to unlock it again(would it work)? Or what adb command do I type to unlock my nexus 7 again?I know how to use ADB bit don't know/memorized all the various commands yet. I need it unlocked to try to revert back to stock again,correct? im ready to give it another shot at trying to solve this problem. I gave up for a few weeks..lol
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1805
    Unlocking, rooting, relocking and unrooting simplified! (and much more!)

    VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.

    ~ my goal for this project is make the entire process as smooth and simple as possible ~

    https%3A%2F%2Fxdaforums.com%2Fimg.xda-cdn.com%2FGjk3UTsOYMSzkx4KT3SZlCiruqY%3D%2Fhttp%253A%252F%252Fi.imgur.com%252FGDhJYE8.jpg


    https%3A%2F%2Fxdaforums.com%2Fimg.xda-cdn.com%2FpzfGGfwJWl0dnds_9og1tODaVzU%3D%2Fhttp%253A%252F%252Fi.imgur.com%252Fq1o1kav.jpg


    Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/

    Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/

    More information & Download Links: http://www.wugfresh.com/nrt/

    Changelog: http://www.wugfresh.com/nrt/changelog/

    Enjoy! ^_^

    {{ WugFresh }}
    36
    Hey, great work! Have you ever thought about making a mac or linux port? I'd really love to help you make one!

    Email me: stevepink8@gmail.com
    29
    For those of you who have 1.5.5 already, the 1.6.0 update package is officially live now. I am updating my site right now with new information and the full version.

    I was able to do everything I set out to do in this release. Support for the Nexus 10, 4, new 3G Nexus 7. 4.2.0 support, and what I spent the most time on - a fully web backed system, that autograbs the latest files the toolkit needs, and populates everything from text files I maintain on the web, making keeping the toolkit updated with the latest files nearly instantaneous.

    Lots more info coming. Enjoy ^_^

    p.s. thank you all for your patience.

    {{ WugFresh }}
    21
    Working on it now. Been really busy though with another project though; https://capsules.io/ks.html

    I will try my best to get the toolkit updated asap in my limited free time. There are some other changes/updates I need to integrate as well, but not too many. Cheers.

    {{ WugFresh }}

    Coding went pretty smooth this round. v1.8.3 is up. (Yes, it supports 4.4.3)

    Enjoy ^_^

    {{ WugFresh }}
    19
    Ok, so my coding is going really well today. I really think I will be done tonight. Yay!

    A word to the wise though; The program now uses Goo.im as the backend for everything because my host just couldn't handle it. They were nice enough to allocate me a large quantity of direct downloads (more than enough) through the program, but there is a daily cap; 30 per day per unique IP. That said, triggering a check for update, will register as a download because it downloads a small text file. So I recommend against checking for updates repeatedly today because your IP will get blocked and when the update is actually out later tonight you won't be able to use the updater, and will have to download the full version.

    That said, the full version is going to be SIGNIFICANTLY smaller. The toolkit will now be entirely backed by an automated file list on the web. This means, the toolkit will only grab the files it needs. So if you only have a Gnex, it won't come with all the files for every single nexus device, but rather.. it will download them when you select that in the toolkit (if it doesn't detect them already in the local directory).

    The device and build lists will now be populated from a text file that the toolkit can grab from the web. That means, in the future when a new build comes out, I can make it so the toolkit self updates within 20 minutes with everything it needs, and that build will be listed. Same goes for autoupdating CWM, TWRP, and SuperSU. The toolkit will therefore will always be up to date with the latest files. And I wont have to go crazy hard coding all of this like I have been.

    Ok.. Back to coding for me. Thank you all for your patience. The slight delays in this release will ultimately speed up all future updates forever. ^_^

    {{ WugFresh }}