yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Fallon9111:
Wino

It works fine on ubuntu and prob all linux by using wine :D

U dont even need to configure anything xD
[Nexus 7 Android Development] SoHaunted:
Wanted to say I've been using this program on my XP sp3 pc without a hitch for obtaining root, installing CWM and getting me on my way to flashing custom goodies :), I've even flashed back to stock without a problem.

I tip my hat to you sir, you do good work.
[Nexus 7 Android Development] brangalm:
Thanks again for the follow up. When I tried to select Nexus S, it didn't have a Jelly bean option, only ICS. I see you just released a new version so maybe its changed now :)

Either way this program was super helpful and straight forward. Thanks again! :)
[Nexus 7 Android Development] WugFresh:
Actually the current release doesn't support Nexus S Jelly Bean, because for whatever reason Google keeps releasing OTA's and NOT updating there factory image site (don't ask me if this bothers me...). That said, v1.5.3 will; I am going to go add an extra option in the pull down list for each device called "other build" which will work on any build but will require the user to do a few steps in cwm.

As an alternate root solution for now, boot into temp CWM with the toolkit and flash this zip: http://xdaforums.com/showthread.php?t=1538053

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Nice! Thanks for the info. I almost forgot about wine. I could probably compile a live linux disc with this through wine that would work on any computer, and then drivers wouldn't be an issue anymore. I will set my ambitions for doing that in the future. For now, I will continue working on v1.5.3.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Excellent. I am happy to hear its working well for you! Today has been super productive for me, so hopefully I can get this new version out asap for the people who are still having some difficulties.

{{ WugFresh }}
[Nexus 7 Android Development] EVOXGSR:
Trying to contact you on gTalk Wug
[Nexus 7 Android Development] Kidromulous:
OK so I got this to work but it apparently failed to install cwm.
[Nexus 7 Android Development] WugFresh:
I am working on a new release right now. But for those of you who said the new 4.1.1 broke root for you. You need the new SuperSU:

http://xdaforums.com/showthread.php?t=1538053

Either boot into temp CWM with my toolkit and flash the zip.

Or you can unzip that, and replace the Superuser.apk and Su binary in the /data/root/JB folder in my toolkit directory.

For those of you who are having any other issues about the toolkit not performing certain operations, please just wait for my next release. It should fix any of these problems.

Also let me know if you have any feature requests for v1.6. I am aiming to finish v1.5.2 today, but I am cool taking suggestions for the future. One idea I had was to create some sort of root explorer type of application, by querying 'adb shell ls' cmds and populating them into a new pull down list, to traverse down a directory structure.. and then maybe include the options to mount sytem rw/ro kinda thing, and be able to delete files and what not. Just a thought.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
That shouldn't happen, will make sure this works consistently on v1.5.2. As a workaround solution, you can use the advanced utilities Flash permanent to recovery button, and then navigate to the CWM img. They are contained within the toolkits /data directory.

{{ WugFresh }}
[Nexus 7 Android Development] snarebum:
When clicking the root button, all it does for me is Check to make sure ADB is good and then it says connected and that's it.. nothing else happens. just letting you know. I'm on 4.1.1 too.
[Nexus 7 Android Development] Kidromulous:
Ty for the quick response I got a recovery IMG and flashed via fastboot. Worked like a charm and everything is great so far. Ty for this great software
[Nexus 7 Android Development] WugFresh:
Are you using 1.5.1?

{{ WugFresh }}
[Nexus 7 Android Development] snarebum:
yeah. It unlocked it fine but like I said I click the root button and shows checking adb status then connected... then nothing happens.
[Nexus 7 Android Development] xTFGx:
drivers aren't installing for me. I'm using 1.5.1 and there's no option for 4.1.1.
[Nexus 7 Android Development] Nexcellent:
Thank you Wug!!! You are the man!

For those having trouble getting the N7 to show up in ADB, go to Settings > Storage > Menu > and check Camera (PTP) :good:
[Nexus 7 Android Development] geronemo:
@Wugfresh

Previously i followed your instructions and installed the 4.0.4 upgrade.

I am not looking to flash any other rom, at least not now.

I followed the following link to upgrade to 4.0.4.

http://wugfresh.com/Help/index.htm#page=Upgrade_to_4.0.4_on_Verizon.htm

After the official upgrade i will upgrade using your toolkit if possible.

Thanks for the great work :)
[Nexus 7 Android Development] Kidromulous:
For those with driver trouble I had the same issue. Use the drivers Wug included with the kit. Profit.
[Nexus 7 Android Development] dipole:
+1
[Nexus 7 Android Development] Heart1010:
+1 (for a linux version)
[Nexus 7 Android Development] WugFresh:
I know all the cool kids use linux, but I have always been a windows geek, what can I say? :p I will think about it...

In other news.. I haven't slept since yesterday and v1.5.2 is nearly done. I pretty much just got rid of all the batch script, and re-wrote everything in autoit. Everything has been running great since. I am going to have to run through all my tests again which takes a little while, but it should be ready for download sometime in the afternoon. :-)

If any of you catch something small like a typo, let me know before I compile this thing again.

{{ WugFresh }}
[Nexus 7 Android Development] hunter3160:
I just have quick question i get my N7 on 16th and was wondering should i update it to 4.1.1 then root it or root it as 4.1?
[Nexus 7 Android Development] thebobp:
+1.5!
[Nexus 7 Android Development] Vondis:
Not saying I haven't done something wrong but everything I try in the drivers guide does not work at all. I haven't tried anything else since I can't get passed the driver setup.

toolkit 1.5.1

JB 4.1.1

will wait on update to toolkit and try again
[Nexus 7 Android Development] b0n3:
This is great! .. I like to do stuff the old fashioned adb way .. but I am purposely reverting back to stock to try this out.
[Nexus 7 Android Development] Atamagaokashii:
Just for curiosities sake: Do we have to use SuperSU? I've noticed everyone start using it, but is there a reason for this or an option to use Superuser? I have no problems if this is the way to go, I'm just comfortable with Superuser/Elite...
[Nexus 7 Android Development] dansan382:
Just realized under advanced tools u can use this to reflash stock recovery. Hell yes' so I can get rid of clockwork mod, download this update and then reflash clockwork!
[Nexus 7 Android Development] caanda45:
In stead of doing that just flash the updated cwm also with the toolkit and not go back to stock......

Also from wug on page 25 here....

Also you can download goo manager from play and flash twrp and it removes cwm completely and replaces it with twrp and it also is a cool recovery. Thing I like the best about twrp is that in back-ups it allows for data compression which is nice to have in this tablet....
[Nexus 7 Android Development] dansan382:
I already have clockwork installed. I want to reflash stock recovery so I can load the OTA update and then reflash clockwork mod. I want the stock 4.1.1 update and just stay roots that's all. For now at least
[Nexus 7 Android Development] WugFresh:
In that case, your original plan was correct. :) Just remember that taking an OTA will most likely break root. So you will need to reroot. Unless you use one of those apps to prevent that.

{{ WugFresh }}
[Nexus 7 Android Development] caanda45:
Okay so I think I learned something tonight, so flashing back to stock recovery will allow a ota? I gather that is what a lot of us will have to do for the fix from a cold boot into recovery when google fix this?
[Nexus 7 Android Development] charlesky:
LOL! Oh well, was worth a try. I had a few niggles with the toolkit while rooting my Nexus, but they seemed to be due to the drivers getting confused and losing sync with the device state which, as you say, isn't something you can really do anything about. It worked fine on the third attempt, though, and thanks for your work.
[Nexus 7 Android Development] WugFresh:
Close. Flashing back the stock recovery will allow an OTA assuming that you haven't made any other system modifications. When you get an OTA, in order for it to actually flash, it first needs to validate that your current system is "Stock" (for all intents and purposes); the way it does this is it checks the authenticity of various system files on your device to make sure they are the original files (by parsing certain entries and using digital fingerprints). So if all you have done is rooted and installed a few root apps, its possible that you will be able to take an OTA without completely re-flashing stock; however in most circumstances; root users make lots of system modifications (flashing custom ROMs, different kernels, Overclocking.. ect).

The best way to take an OTA without any problems, is simply to re-flash stock (or even better.. if Google releases the factory image package for the build you are trying to upgrade too, don't even bother taking the OTA, and just use the Flash stock feature to upgrade).

If you make a nandroid backup right after you root, then you don't have to bother reflashing stock.. you could just restore your backup, then reflash the stock recovery, and take the OTA.

Regarding the cold boot issue. Remember that the factory image packages are comprised of numerous image files. You have the ability to just flash one of them if you want. So if you were running a custom ROM at the time they released the fix, you could just unpack the factory image package and flash the bootloader.img file with the Flash to Bootloader button.

In general, OTA's are really pointless all together as root users.. because chances are you are getting the updates before the are even out, or you are running a custom ROM... and since google releases all the factory image packages on their site.. You can just flash them to update.

The only benefit of an OTA, is that it is a true "upgrade" in that it doesn't require a wipe. But since root users make system modifications; wiping becomes necessary when you want to go back on the stock route.

That said, remember...If you use CWM to make backups, you can do selective data restores and get pretty much right back to where you were without problems, or you could use TiBackup, or the toolkits backup and restore features. Hope that helps to clarify some things. :)

{{ WugFresh }}
[Nexus 7 Android Development] lanwarrior:
This is the biggest problem I have after I root and install permanent CWM. I tried to boot into recovery using QuickBoot and I got stuck on the page where it shows the Android character with exclamation mark. I simply cannot boot into CWM!

I tried going back to stock using the toolkit, tried the root and CWM and same thing. Tried it like 2-3 times. So I cannot make nandroid backup using CWM.
[Nexus 7 Android Development] WugFresh:
Try using ROM manager to flash CWM. It will overwrite the one the toolkit flashes with the official one by Koush. Then if you wan't the touch version, you can try flashing it with the toolkit afterwards using the Flash to Recovery button; http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-grouper.img

Also if you have a root file explorer app, check to make sure

/system/recovery-from-boot.p

has been renamed to:

/system/recovery-from-boot.p.bak

and:

/system/etc/install-recovery.sh

has been renamed to:

/system/etc/install-recovery.sh.bak

The toolkit should have taken care of all of that in the permanent root script, but you could check to make sure everything ran properly for you. My guess is that you just needed to try reflashing CWM.

{{ WugFresh }}
[Nexus 7 Android Development] caanda45:
Wug in your opinion which recovery do you like the best? TWRP or CWM?

I also had the same issue as above and had to re-flash it three times and rename with the .bak extension for it ti stick...thanks again sir!!!
[Nexus 7 Android Development] lanwarrior:
Thanks for the information. I confirmed that the files mentioned below exists and has been renamed.

I will try to use ROM Manager to flash CWM.

When I re-flash using the ToolKit, will it wipe out my device again?
[Nexus 7 Android Development] caanda45:
Another token of appreciation of your work and help here......Confirmation number: 4GP25394KT9436905

---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------

No it won`t look one page back, I had to flash it 3 times in all (using rom manager and flashing cwm only) and then renaming using root explorer it for it to finally stick.
[Nexus 7 Android Development] dansan382:
yea all i did was root the device and throw clockwork on and a few root apps. id want the OTA update because im not sure if im going to throw a rom on it but most likely. ill probably decide pretty soon, if i go with CM10 or AOKP i wont care about loading the OTA obviously.
[Nexus 7 Android Development] DataHawg:
I read most of this thread and haven't seen this asked. I installed the Toolkit to my Win 7 32 bit machine and it opens in a very small window with no option to make it larger. I can't grab the edge of the box and drag it and the full-screen option at the top is greyed out. I was going to uninstall the toolkit and try installing it again but I can't find it in Control Panel. Don't see an uninstall file in the wugFresh folder on my C Drive either. I checked the Md5 sum before installing.
[Nexus 7 Android Development] WugFresh:
All files are installed locally to the install directory. Just delete the folder. Are you talking about the model select GUI? You need to select your model type first..

{{ WugFresh }}
[Nexus 7 Android Development] DataHawg:
The model select dialogue came up and I selected JRO03C even though I took the update and I'm on JRO03D but others said that would work. It's the main interface after I did that that I can't enlarge. I deleted the folder and I'm trying again. I want to select JRO03C, correct?

Edit: I downloaded and installed the Toolkit again and still can't enlarge the UI but I ignored it and proceeded. Used the Auto driver config and everything worked perfectly the first time. Outstanding job on this, Wug. Thank you.
[Nexus 7 Android Development] WugFresh:
Correct. The GUI's are not re-sizable. Is your problem that the text looks wonky, like its too big for the buttons? If that is the case change your systems DPI settings to normal (100%). Making that dynamic is on my to-do list but it is a serious pain to program.

http://www.sevenforums.com/tutorials/443-dpi-display-size-settings-change.html

Edit: Glad to hear you got it going.

{{ WugFresh }}
[Nexus 7 Android Development] DataHawg:
The text looked OK on my machine and was all inside the boxes, but some of it was cut off is all. If it ain't broke, don't fix it, right? Did a Nandroid backup right after rooting so I'm good to go.
[Nexus 7 Android Development] WugFresh:
Mind sending me a screenshot (wugfresh at gmail) when you get a chance? If its a matter of just adjusting it a fix pixels or whatever, I would like to make the fix. Nice, I am glad to hear its working well for you.

I have made serious progress on this next version for those of you who are still waiting. I just finished programming one of the biggest tasks, which was building the whole in-built automatic toolkit updater/notification system. I am really glad I finally got that coded for this upcoming release because now it will be much easier for me to roll out small fixes if need be. It also will make it so I don't have to worry about legacy mirrors floating around all over the web. If I continue at this pace, this thing could be done as early as tomorrow. Wish me luck :P

{{ WugFresh }}
[Nexus 7 Android Development] barbo:
Yes, yes - good luck! I have been reading the thread and am anxiously awaiting 1.5.3 because I see others with Windows 7 64-bit machines have had some difficulties. Your support has been outstanding. Once I get this up and running a donation will be forthcoming. You deserve it!
[Nexus 7 Android Development] saywhaa:
im on win 7 64bit and had no issues at all.

great toolkit! cant get any simpler then what you have done!

also i was having that same issue with the cold boot into cwm. i did the perm cwm flash 3 times also tried doing it from rom manager, then updating to touch, it still wasnt working.

>what solved the issue was i flashed stock recovery from "advance utilities" and then flashed cwm via rom manager, again updating to touch right after and then powered it off and was successful in cold booting into cwm.

the service first OP you give is remarkable, and it will/is appreciated.
[Nexus 7 Android Development] fApple:
As always.. thanks for the hard work Wugs! Couldnt have been easier to use!
[Nexus 7 Android Development] dparrothead1:
Thanks Wug!! This tool will remain on my desktop as long as I have my N7.
[Nexus 7 Android Development] :
Is there a way to use this tool to backup the phone if all I have access to is download mode via a jig? My galaxy nexus's powerbutton stopped working so I haven not been able to start it at all. The best I have gotten is to download mode. At minimum I need to restore the phone to factory before taking it to verizon...
[Nexus 7 Android Development] WugFresh:
For your circumstance my toolkit is not going to help you restore your device initially but it can help you back things up if you get things working again; your best bet is to first flash an ODIN tar with ODIN: http://minus.com/lblsAU7ozeSb7R

http://goo.im/stock/toro/stock/VzW-PDA-ODIN-I515EL03_ICL53F_signed.tar

http://goo.im/stock/toro/stock/VzW-PHONE-ODIN-SCH-I515.EK02_LTE.tar

Helpful resource: http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-gsm.html

Regarding trying to save data. I suppose you could try modifying the PDA tar by removing the userdata.img file from the package. That way, everything else will get restored, and your userdata partition will be left untouched. Your system data will get overwritten, but I recommend letting that happen. Then if all goes well, you could enable USB debugging through the main touch screen interface, and then use the Toolkit to back things up like user apps and your data/media partition. If there is select userdata that you want to get off the phone, then you could use the advanced utilities Pull files button. If you are trying to preserve data on your system partition for some reason, then you could try my same suggestion but remove the system.img file from the ODIN tar package as well... however this is probably not the best idea. At this stage you just want to get your phone to boot back up. Cheers. Good luck.

Edit. Forgot to mention that afterwards you are going to want to relock your device using the toolkit ....

{{ WugFresh }}
[Nexus 7 Android Development] slickie88:
Right now I'm bricked and can only access the bootloader and recovery. Stock recovery doesn't display any options (only the red triangle) and any of the CWM recoveries I've tried seem to work fine.

I've attempted flashing the stock image dozens of times via the toolkit and from the commandline, but it results in a boot loop after reboot. I can flash CMW fine, but I do not have a nandroid to restore - it was when was going to create my first one that I first encountered bootloops.

When attempting to flash stock from the commandline here's what I get:

C:\Wugs_NexusRootToolkit.v1.5.2\data>fastboot -w update image-nakasi-jrn84d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: <snip>
--------------------------------------------
checking product... OKAY [ 0.019s]
checking version-bootloader... OKAY [ 0.020s]
sending 'boot' (4884 KB)... OKAY [ 0.625s]
writing 'boot'... OKAY [ 0.330s]
sending 'recovery' (5228 KB)... OKAY [ 0.671s]
writing 'recovery'... OKAY [ 0.269s]
sending 'system' (432360 KB)... OKAY [ 53.603s]
writing 'system'... OKAY [ 21.568s]
erasing 'userdata'... OKAY [ 1.044s]
erasing 'cache'... OKAY [ 0.123s]
rebooting...
finished. total time: 78.358s

It then reboots and loops.

While I didn't do a CWM nandroid backup I did do an android backup via the Toolkit before the N7 went tits up, but I can't get it to restore; it simply sits there with the Restoring xx-xx-xxx._xx-xx.ab to your device message but never completes.

I can't mount /sdcard in CWM either. Am I looking at a partition problem? Any guidance on how to proceed would be appreciated.
[Nexus 7 Android Development] WugFresh:
Try the following;

Boot into temp CWM and wipe;

-Data

-Cache

-Dalvik (found in the advanced menu)

And then try rebooting.

Try simply temporarily booting off the boot.img file found in the package. See if you can get a clean boot.

If that doesn't work, also try booting off the modified boot.img for nakasi builds that I edited and included in the toolkit; it resides in the toolkits /data directory. Use the temporary boot button in advanced utilities to do these operations.

Try re downloading the factory image package altogether and flashing it again with the toolkit.

- - - - -

I don't understand why you are trying to restore an Android backup file while your device is boot looping. That's never going to work or fix anything.

Can you provide more details regarding what the last thing you did before you started boot looping. You said you were trying to make a nandroid? Well... What did you do before that? What did you flash?

{{ WugFresh }}
[Nexus 7 Android Development] productofusa:
Hmm, thought you knew about this, I assumed it was the same for everyone, some text is cut off in most windows generated by ToolKit 1.52. Especially that important part at the bottom. My desktop resolution is 1920 X 1200. Oh, and it did the same in 1.51

In other news (lol) this N7 still comes up in "Devices and Printers" instead of "Devices with Removable Storage" under My Computer like it used to, like where my Google Nexus lives when its plugged in. I ****ing HATE drivers, and I ****ing hate Asus for not releasing a proper driver. Mostly though Google, for all the talent these guys have you'd think.....ugh, nevermind.....gettin off track here, Lol
[Nexus 7 Android Development] slickie88:
Thanks for the suggestions Wug.

Doing this results in bootloop. I can't count the number of times I've done this after trying various other flashes and recovery attempts.

Hadn't tried this yet. Booting from your modified nakasi image also results in bootloop.

I've already downloaded it several times, on two different computers making sure to verify checksum each time. No dice.

- - - - -

I unboxed it, went through initial setup including the OTA update, installed my 30 or so apps and then spent the better part of the evening configuring them all. I then successfully unlocked and rooted using the Toolkit, installed TBI and ran backups then left it charging over night. Next morning I wake it up, update a few apps and decide that it's time to do a nandroid backup. I rebooted, intending to go into recovery, but inadvertently missed the two-finger salute window (meaning it was booting normally) and bam, bootloops from then on. Never attempted to flash a ROM or kernel; absolutely nothing out of the ordinary that I can think of.
[Nexus 7 Android Development] thename1000:
Hey I think I rooted via this method.

My N7 keeps trying to update to 4.1.1 but it's already that version. If I try to update it just goes to the recovery screen and I just reboot it.

What's going on?