Thanks for the feedback. We’ll incorporate the suggestions in the article.

A few things to note – which I found eventually in the comments but you may wish to add them to the main article for some clarity.

Item 1. The Google supplied OEM image contains the flash-all.bat file. I got stumped on this when I did not see it initially until I read through the comments and discovered that it was included in the Google OEM image compressed file. As well, the file I got from Google was a tar file inside of a tgz file. Windows users need to know that they should use 7zip or similar third party program to uncompress the tgz file first, then again to uncompress the tar file and THEN copy those resulting set of files to the same directory where the user extracted your ZIP file contents.

So if you change Step 1 to include the following:

1.a: Download and extract Fastboot/ADB ZIP file contents to a new file called “Google” on your computer. The folder name “Google” is suggested, but feel free to name it as you wish.
1.b: If you do not already have the USB drivers installed on your computer then install them from the Google/Drivers folder or download the latest version from Google and install them (I strongly suggest the latest drivers, especially for Windows 7 and newer versions).
1.c: Download the OEM image you wish to use from Google. This file will be in TGZ format and you will need to decompress it using 7zip or some other third party compression program (WinZip, PowerDeskPro, etc.). The contents of the TGZ file will be a TAR file, this also will need to be decompressed and the contents of the TAR file now should be copied to the same folder you extracted the Fastboot/ADB ZIP file to in step 1.a above.

Item 2. My computer doesn’t seem to like the ADB drivers very well. Fastboot would show my device with the command “Fastboot Devices” but ADB would not should any devices with the command “ADB Devices” and as well, when I tried to run “ADB Shell” I would get a “No Devices Found.” However, this did not prevent Flash-all.bat from doing it’s thing and it worked successfully like a charm once I solved the ADB driver issue below.

I discovered that the device ID, once you put the Nexus 7 into Fastboot mode, would change on a rooted device and the driver would get confused. The solution for this involves modifying the driver’s INF file with the following:

For 32 bit versions of Windows, under the [Google.NTx86] section locate the part that is commented “;Google Nexus 7” and all the following two lines to the bottom of that section if they are not already there:

%CompositeAdbInterface% = USB_Install, USBVID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USBVID_18D1&PID_4EE0

For 64 bit versions of Windows you would add these lines to the section under the [Google.NTamd64] header.

The first line is for rooted devices, and the second is for unrooted devices.

Your article is a life-saver, however it does assume a certain degree of tech savvy of the user so breaking down the steps, as well as providing a list of pre-requisites the user needs to accomplish first might be really helpful for those just starting out.

Glad it worked. Hope to see you here more often.

Glad it worked.

Great, glad it worked.

You just use” Nexus Root Toolkit” advanced option