yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] WugFresh:
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 ~

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 }}
[Nexus 7 Android Development] ST3P_2:
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
[Nexus 7 Android Development] EVOXGSR:
I'm going to try this. I didn't have much luck using the other one-click out there. But this kit can restore to stock, so I'll do that and try this rooting stuff all over again.
[Nexus 7 Android Development] mintaeroboy:
Does this work with the new 4.1.1 on nexus 7?
[Nexus 7 Android Development] EVOXGSR:
everything works great except, I'm not going through with the root. I get stuck on fastboot mode with a message at the top saying "Booting downloaded image". But no action happens. fastboot is frozen and my computer has a message "Waiting for your device to finish booting up..."

Any idea what's going on? The kit worked really well unlocking and locking and restoring stock

I tried all of this on both 4.1 and 4.1.1 and get the same stuck screen results on the root feature, regardless of flashing CWM or not, just plain frozen
[Nexus 7 Android Development] WugFresh:
Ok. That is strange. Add me on gchat and hit me up and I will try my best to troubleshoot with you to find out the cause of your problem.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Man, that was quick.. I thought I was up to date.. lol.. development is never ending. I will push an update out asap. Looks like I need an updated Superuser. Can you do me a favor and try flashing this in Temp CWM recovery;

http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip

Edit.. I just realized that you phrased that as a question. Try it out. It should work. No harm in trying. I included the latest SuperSU in the toolkit, and had success with it. So go for it.

Cheers

{{ WugFresh }}
[Nexus 7 Android Development] NZtechfreak:
Same error here... Did you reach any resolution?
[Nexus 7 Android Development] WugFresh:
He did not get back at me, but maybe you can help me. Can you try replacing the modified boot.img in the toolkits data directory with this one instead: http://wug.rootxs.com/modified_boot_nakasi_4.1_JRN84D.img

So by default, you would place it here:

C:\Wugs_NexusRootToolkit.v1.5\data\modified_boot_nakasi_4.1_JRN84D.img

And then retrying the process. If that is it, I am going to feel very silly.

{{ WugFresh }}
[Nexus 7 Android Development] NZtechfreak:
Heh, already got Root using the tried and true ADB method. Restoring stock so I can try and help you out :)
[Nexus 7 Android Development] WugFresh:
Thank you very much!

{{ WugFresh }}
[Nexus 7 Android Development] NZtechfreak:
Same thing :(

Will head back to ADB method as I actually need Root right now, but will try and help later if I have time and it hasn't been resolved yet.
[Nexus 7 Android Development] WugFresh:
I would really appreciate your help when you are available. I would like to get the resolved asap. My gchat is wugfresh at gmail, that would be the best way to figure this out if you have the time. I am certain the solution is simple. Thank you for your help so far.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Never mind.. I am pretty sure I know what the problem is. I will post up version 1.5.1 later today.

{{ WugFresh }}
[Nexus 7 Android Development] NZtechfreak:
Cool, will definitely confirm if your fix works, will do a guide for the blog/YT and would rather use your guide than ADB since newcomers won't cope with ADB.
[Nexus 7 Android Development] dEris:
Anyone have a mirror? Current one is down.
[Nexus 7 Android Development] WugFresh:
It's down because the new version is up. ;) Check the OP. Once I heard you guys having trouble here I knew something was up, so I have been at it all morning and got a fix now. Version 1.5.1 just released. Such an epic fail of a mistake, so small.. yet screwed up my whole root script. Now everything should work properly. :) Let me know if any of you still have problems.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Cool. Thank you! I am pretty certain everything works now. I agree, sometimes people don't find cmd line utilities friendly, although to others they become second nature. My goal has been to make something as simple as possible, and try to explain it along the way.

{{ WugFresh }}
[Nexus 7 Android Development] Balzard:
If it works, this should be stickied, so that noobs like myself know the best/easiest way to proceed (there are already a few guides and toolkits, but this one seems to be much simpler!).
[Nexus 7 Android Development] Dakota0206:
For anyone on the fence...

THIS WORKS!

You will not find better or easier!
[Nexus 7 Android Development] movieaddict:
unplug ur usb and get the drivers from pdanet! thats what fixed it for me its hanging because u dont have the proper drivers. After u have the drivers go back into the toolkit and it will go smoothly
[Nexus 7 Android Development] FiveOhFour:
More details may help, you are using a Galaxy Nexus or what? Where exactly does it hang?

It seems to be a pretty common occurrence, if its hanging that just indicates the drivers arent properly installed.When functioning properly it will take 10 seconds to query. Uninstall the drivers using the included tool in one of the early steps,2 maybe, and then download the manual driver file from here (also source for 64 bit drivers) http://xdaforums.com/atta...9&d=1342290861 . Just open that and install the 32bit drivers manually from that file instead of doing the automatic driver install, and skip the automatic install step. Once the tool is installed and you click unlock it will again do the adb status test.
[Nexus 7 Android Development] Philosophy757:
I'm using Win7 and wasn't able to install the drivers using the automatic method but did them manually and it worked fine.
[Nexus 7 Android Development] FiveOhFour:
This seems to be the common theme, and if i Know Wug, which i do-the guy is like my best friend since i first read his name almost 24 hours ago now, then he is already working on updating the install process. He mentioned he cant stand unexplained computer anomalies so im sure it will be quickly done but for now its easy enough to manually do it right? Now if he could just write a program to cure the adhesive for the IPS panel and undo my screen defect than we would be golden.
[Nexus 7 Android Development] WugFresh:
Thank you the information and for all of your suggestions. I agree with your entirely; suggestion 1 and 3 should be an easy fix, although I really thought that I had fixed all the path issues for paths with spaces.. I will check over the downloader again.. regarding the timeout, it seems like it should be easy as well.. I am just not sure how I would program it, the way that is scripted now. I am sure there is a way though, there always is. I will do my best to integrate these suggestions into the next release. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
I added the suggestion about manual driver installation for 64bit setups in the OP. I am working a new solution for the auto-driver installer now, that should first check OS architecture and then install the appropriate drivers. Hopefully that works. Windows just makes it a pain to install drivers automatically.

My main goals for v1.5.3 are to integrate this better driver installer, to add in the suggestions by Mogul345, and hopefully figure out some slick way to have in-app update notifications; that way, the end-user can get the latest toolkit by just installing a smaller update package.. rather than this horrible system now, where you have to re-download the entire 129MB package.

I have never built anything with an updater before, so I am not quite sure how I am going to do it. But I figure I have to do some sort of thing where I query a server address, and then based on the output, perform the subsequent action. I don't know. Sound like an interesting challenge. Hopefully I figure it out, and it will be easier to keep everyone updated with the latest releases.

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
Sounds like a respectable outline. You noticed many people were having driver issues with the 32 bit as well when auto installed, but no issue when using the manual 32 bit drivers from the pdanet folder? assuming they are the same drivers something is just getting lost in the auto install process ?
[Nexus 7 Android Development] jarjar124:
sorry for sounding like a noob, but this only works with windows right? or this works with mac and/or linux?
[Nexus 7 Android Development] WugFresh:
Yeah. Maybe I should ditch the auto driver installer all together. I used pnputil to install the drivers, which is really the only cmd line utility available that I have had any luck with, but it seems to still be lacking. I have tried devcon.exe before but with horrible results. Maybe if windows stop focusing all there attention on eliminating the start menu and pushing their metroUI, and instead tried to improve their core OS functionality like driver installation.....Arghh.!!! but I digress...

Do people find my manual driver instructions clear? Maybe I could refine that in some way.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Yes. I built this with AutoIt which is a native windows programming language. I have heard feedback from users who have ran this through a VM though, like Parallels or VMware.

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
Honestly the manual driver install was easy enough, I will go through the process again and take a couple notes to give you cuz i thought at a few stages it could be easier and clearer, only in the sense that if you do this step than you can skip and ignore this other step if that makes sense. Once i realized that a couple of the steps were for Samsung phones only it was all fine, so it was easy enough but it could use a little clarification just for people who are literally hanging on every word of instructions. I saw this guide which sites your tool and mentions changing the way the tablet is recognized by the computer, not sure if there is any credence to that idea or not. http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
[Nexus 7 Android Development] WugFresh:
Wait.. Google released another update already? JRO03D? Why aren't they posting these on the factory image google.code site? That said. The toolkit should still work if you select the latest release available in the pull down menu: JRO03C.

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
3D is the small one, i believe, the one that adds the FCC number in the menu right
[Nexus 7 Android Development] WugFresh:
Yeah. JRO03C is in the menu and should work. I just google kept current on their factory image site with the latest releases, so I could make the flash stock feature update your device to the latest build.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
That helps. I added that guide to the OP now. I should just remove all info that uses the Samsung drivers, or maybe have the guide change depending on what device you are on. Thank you. All pointers would help. I want to make it as easy to follow and intuitive as possible.

{{ WugFresh }}
[Nexus 7 Android Development] tbogs:
I have been keeping up on this thread and today my Nexus came in. I still am unable to get the proper drivers installed. I had my HTC Rezound drivers installed and thought that was messing up with the configuration, so I removed them. Now when I try connecting my Nexus to my Windows 7 (64 bit system) there is no communication between the Nexus and computer. I have even tried installing the PDA drivers and selecting the 64 bit one and nothing is working. Not sure what else to do. Sorry I'm a noob with Nexus devices, this is my first.
[Nexus 7 Android Development] riko540:
Unfortunately it doesn't work using 3C cause the program to lock up after installing the ADB driver and I'm unable to go any further until I un-install the driver. I'm using Windows xp if that makes a difference.
[Nexus 7 Android Development] Archangel:
hmmm using 3C worked perfectly for me on my windows 7 machine?
[Nexus 7 Android Development] DJLamontagneIII:
Worked great for me same rom and win xp.... Try reinstalling the drivers
[Nexus 7 Android Development] DipRip:
Ok i have a problem. I used this to try to root and try to flash my nexus 7. Now I got the latest system update, I hit update and it tried to boot into recovery and failed. Now I cannot update it anymore 1) the update did not work and 2) when i try to check for updates it says "up to date"

How can I get the latest patch that fixes the screen flicker?
[Nexus 7 Android Development] roenick34:
thk , is very very easy fantastic tool for root the nexus 7 .
[Nexus 7 Android Development] o0boiboi0o:
Apart from some new functions (like ability to queue files to be flashed), there isnt much difference between CWM and TWRP right? Both function the way they should and main difference is on the UI. Am I right?
[Nexus 7 Android Development] Mallikanth:
Not just that.

AFAIK TWRP is better supported / updated more often than CWM.

Personally I also find it easier to use.
[Nexus 7 Android Development] WugFresh:
The main difference for me is "Open Recovery Script" which is what the toolkit uses to automate the flashing of zip files when rooting, and it also make the "Open Recovery Script Flash Manager" via the "Flash zips.." button possible. The openess of the recovery is what makes it great, CWM restricts this type of access. Also TWRP has more selective backup options.

{{ WugFresh }}
[Nexus 7 Android Development] pdrift:
Hello, i have a 16GB Nexus 7 wifi running 4.2. I previously unlocked the bootloader manually and I was planning on rooting it but after

reading several threads about issues I decided to wait until things got sorted out. Then I came across this thread and when the updated toolkit came out I decided to try it. problem is I cant pass the driver test. I've tried solution #1 and 2. I keep getting ADB device not found.

USB debugging is checked on the N7 and i've tried different cables and ports. I dont think its a hardware issue. I've uninstalled drivers and tried reinstalling them several times. I'm using a laptop with windows 7 64 bit.
[Nexus 7 Android Development] oconnell84:
I meant "still get nothing" in regards to actually downloading the files needed and putting them where the program looks but it still did not work. In the end everything I needed was complete but without using this program. Thanks for the response and all the work you put in.
[Nexus 7 Android Development] gogol:
Can I use this version to re-root my Nexus 7 which I have updated to Android 4.2.1?
[Nexus 7 Android Development] shaneydroid:
Used the toolkit on 2 different Nexus 7s without any problems til now.

Needed to restore my Nexus 7 to factory defaults so used the toolkit to do a backup first.

Did a regular backup then did another one with shared storage added.

After restoring I used the toolkit to restore the backup and found it had only restored about half my apps.

Not only that but only around half those apps have retained their settings.

What could have gone wrong?
[Nexus 7 Android Development] Mallikanth:
Yes
[Nexus 7 Android Development] k5mitch:
Worked great returning to stock, so I returned my N7 wifi and just ordered my a N7 3g.
[Nexus 7 Android Development] CBers:
You could have downloaded the zip file from the Google servers and saved anywhere on your device.

Then, using TWRP, you could have installed it using the INSTALL option and navigating to the zip file.

That's how I did the 4.1.2 and 4.2 updates.

I did the 4.2.1 update on both my Nexus 7 & 10 via OTA and then restored root via VOODOO ROOT KEEPER.
[Nexus 7 Android Development] WugFresh:
Now I get to show you all my favorite feature of v1.6.0 ^_^

In the the toolkit, got to Help > About, and agree to redownload the master lists. Now use the "Change..." button again to select your model... You will notice that 4.2.1 is now listed. ;) :good:

Tada!

{{ WugFresh }}
[Nexus 7 Android Development] bizz2012:
Hi,

I don't know if anyone can help me but.

My brother last night updated my Nexus 7 from the JR9 Modaco ROM to 4.2 using the OTA. Now when I boot up I get the error message, the android man with a red X.

I have booted into temp recovery and I can find my backup I made in TWRP but when I go to "Restore" nothing is listed there.

My backup for some reason is in sdcard/0/TWRP/BACKUPS/file name

How can I point TWRP to my backup so I can restore my JR9 mod?

Thanks

Can i do it using this toolkit?
[Nexus 7 Android Development] Eddie Dickens:
Thank you for the update, WugFresh!

I'm still waiting for my update to 4.2.1 (Germany) on the 3g ...
[Nexus 7 Android Development] bonzer2u:
nice......

U.B.D.Man...
[Nexus 7 Android Development] pdrift:
Well I managed to get it working. I uninstalled everything, rebooted then tried again from scratch and it worked! :)

Thanks for such a great tool!!
[Nexus 7 Android Development] tamanaco:
First of all thanks to WugFresh for such great toolkit. Yesterday after 1.6.0 was released I decided to Unlock, Root and install TWRP recovery in my new 32GB N7. I had already installed about 30 Apps and had been playing with the device and waiting for NTR 1.6.0 for a few days. I understood that Unlocking the N7 would wipe my data so I first tested my PC USB connection to the N7 which was using the USB "Naked" drivers and everything passed. I then went ahead with the unlocking and everything went without a hitch. N7 reboots, I followed the Android initial configuration prompts and walked away for a minute or so. To my surprise the N7 was downloading and installing all the 30+ applications that had been wiped during the unlocking process. I guess this is because I selected to sync everything with Google. Happy here... maybe this needs to be mentioned somewhere. I then proceeded to root and install the custom recovery... again without a hitch. Toolkit worked perfectly. I installed bunch of new apps and customized and configured the N7. Now, my problem... to be clear it's "unrelated" to the Toolkit, but I just wanted praise the toolkit and ask for some help from the folks in this thread. When I woke up this morning I noticed that now we have the new OTA JB 4.2.1 and decided to flash it using TWRP. Could not leave good enough alone... I tried to flash the OTA zip for 4.2.1, but it failed. I think I know what the problems is. I used Titanium to backup my Android devices and during this process I usually "integrate" updated Google apps in the ROM to save space. I'm afraid the OTA process is checking the MD5 of these apps before proceeding and fails. Any advise as to how should I go about installing the 4.2.1 OTA, short of going back to stock and having to redo everything. Thanks
[Nexus 7 Android Development] hamurabi1:
I try to reflash stock recovery (CVMR)...I did exactly you say. I use toolkit and restore stock recovery. My N7 reboot into bootloader, flash stock recovery and normaly reboot to device. After that i could not boot into recovery mode...just got to the android sign with red exclamation mark :(
[Nexus 7 Android Development] bonzer2u:
go into the advanced section and reflash your recovery partition. I used the twrp 2.3.2.1 img file when mine went sideways, works like a champ.
[Nexus 7 Android Development] limpet:
I tried to install the update zip with toolkit temporary recovery. This worked for the last two updates, but this time it failed.

After reset, initial configuration, and app downloading, I noticed an OTA update notification. I told it to go ahead and 4.2.1

installed itself. Everything worked fine and I went ahead and rerooted with the toolkit.
[Nexus 7 Android Development] WugFresh:
Stock recovery is the android sign with the red exclamation mark. To enter into the menu you have to press both volume buttons and the power button at the same time.

{{ WugFresh }}
[Nexus 7 Android Development] Guti1977:
That's awesome WugFresh, Root Keeper didn't work for me and I was really lazy to give a shot to the ABD method for re-rooting my tablet. However your almighty toolkit made that happen. :good:
[Nexus 7 Android Development] cheloPR:
That would be great!...
[Nexus 7 Android Development] Logan_M:
Thanks for the awesome update! Worked perfectly and rooted in under two minutes with the new version of the toolkit.
[Nexus 7 Android Development] nhk200356:
Update 4.2.1 and rerooted

I did the 4.2.1 update on my Nexus 7 via OTA and then rerooted via NEXUS ROOT TOOLKIT .

Everything good .Thanks
[Nexus 7 Android Development] itenos:
Cannot sdb pull from my device

Hi, I just installed the toolkit for the first time because I wanted to backup my internal SD card before upgrading to 4.2. I'm on 4.1.2 rooted und bootloader unlocked with various system files integrated into system with Titanium therefor the OTA won't work for me.

Installing the toolkit and all the drivers it seemed to work fine. I first created a Android Backup which went through. Next I tried to backup my virtual SD card and the process didn't show any errors but after not even one second it said Process finished. I can find the freshly created subfolder but obviously nothing in it.

Same problem goes with a Nandroid backup in temporary TWRP. After pressing the backup button it says backup failed.

Any suggestions?

UPDATE: I managed to back up the SDcard by manually pulling from /storage/sdcard0. The built in command tries to pull from /data/media and this doesn't work

Further the "Flash zips" if file is on the computer doesn't work either! It starts pushing the file to the Nexus but after one second it continues into booting into recovery. Pushing manually instead works perfectly
[Nexus 7 Android Development] 3kgt:
Root ok.

But when installing busybox nothing happens, install and uninstall same ****..it says its installed, but i still have the same gray icon and the install uninstall? is that ok? and im the noob here!

making backup (full backup) with pc ..nothing happens.

Unable to locate android secure partition

backup failed

Hmm i cant backup with TWRP either! :S