Database Users

Finally got Root with 2gig card that came with phone

I've posted this inside another thread but decided to make a new one so others can see.
To all of you guys who are giving up - DON'T !
Here's how I finally got root on my DINC after about 3 days of trying.
I've read and watched almost every post and walk-throughs available in this forum and few others and was still unable to get into ADB Shell using any of the methods and tricks available and even though none of them worked I kept trying until I found a post on adndroidforums.com by Centsy. So along with his instructions and combination of many others here's how I achieved root:
1. Download the file from the 10 minute incredible root video on YouTube by mejdam. (can't post the link cause I'm new to the forum).
2. Unzip the file and run SDK setup.
3. As soon as SDK setup runs it gives an error message. Close it. then hit Cancel on next window.
4. While still in Android SDK and AVD Manager click on Available Packages (on the left) and then hit the plus sign in the right window for the repository. It will give you a list of packages available. Download the very last one which is the USB_Driver. It will add 'usb_driver' folder to your SDK folder where you ran sdk setup from.
5. Modify android_winusb.inf file inside the 'usb_driver' folder by adding these lines at the end of [Google.NTx86] and [Google.NTamd64] sections:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
6. I used the 2 gig Sandisk memory card that came with the phone. Had it FAT32 full formatted on the pc.
7. insert the card into the phone wait for it to be recognized
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed. Note that I do not have HTC Sync installed on my pc.
9. on the phone go to settings->applications->development->turn on USB Debugging. wait for the phone to be recognized
10. open command prompt, navigate to your SDK\Tools folder and type in: adb devices. when you hit enter it should list your phone as being connected.
11. at the prompt type: adb reboot recovery, hit enter
12. as soon as the prompt is back type: loop and hit enter to start the adb shell loop. As soon as the loop starts running, the phone should show the white HTC Incredible screen, start clicking in and out the sd card before you hear the device disconnected sound on your pc. keep clicking the card in and out until you hear device connected sound on you pc. If you still don't see THE message we are looking for after another 10, 15 seconds stop clicking the card. take the battery out of the phone, put it back in, wait for it to reboot and repeat steps 11 and 12.
I had to do steps 11 and 12 about 3 times when I said to myself - next time is the last time and if it doesn't work then I'm going to get the 2gig PNY card that everyone is saying helps them achieve root. Then all of the sudden it took a little longer for the device connected sound to come up and the mouse cursor turned to the Waiting Hour-Glass and as soon as I heard the sound I saw the good old error message we are all striving to see. After that I just followed the instructions on the 10 minute root video to get the phone rooted.
Never give up, Never surrender !
Hopefully this will help some of you guys to achieve root and thanks to everyone who's hard at work on getting this great phone rooted.

Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete

sonypete said:
Hi,
Having issues with your Step #12. You say to click the card in and out when the white HTC screen comes up and do it till the first disconnect sound. Then you go on to say keep clicking untill it connects. Then you says 10-15 seconds after the connect sounds keep clicking. Don't you mean to say keep clicking from white HTC screen till 10-15 seconds after the 2nd sound(the connect sound) So basically clicking for over 30seconds.
Please clarify as I'm thinking you meant differently thne what you typed. I too have a stock 2G sandisk card that came with my phone and so want to get this rooted without buying a PNY card hah.
- Pete
Click to expand...
Click to collapse
Basically once the white screen comes up, start clicking the card in and out until about 10, 15 seconds after the 2nd connect sound that windows give you. However, you MUST start pushing the card in and out before the 1st disconnect sound.

Okay cool. Fingers crossed I have been trying since yesterday and about to jump out the window hah.
- Pete

Wow, I got it first time with this method! Thanks a lot! I am also using the stock 2gb card that came with the phone.

Thanks man. I got this to work twice in about 4 tries. 1st time it worked I accidently selected reboot option. So had to retry this method. My clicks were medium speed not very fast and not excessively slow in case that helps anyone. About 1 a second.
- Pete
(2G Sandisk Rooter hehe)

Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!

I think this will help
KingJ50 said:
Hey this method worked to get the error but I can not write to the SDCard, I get the following when I try to push something: failed to copy 'busybox' to 'sdcard/busybox: Permission Denied
It is the same with any file and I did Apply sdcard:update.zip
Please help!
Click to expand...
Click to collapse
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.

dreamersipaq said:
Once you get error, I believe that you need to run the "apply update.zip" once and let it fail. Then you can adb to the sdcard.
PS, this method never worked for me, no matter how much I tried.
Click to expand...
Click to collapse
Same here, i still can't get to adb shell . . .

I got into adb doing the click on the 3d try but it kept failing to push the payload and then I accidentally restarted the phone. AHHHH, just spent 30 minutes doing the same thing and couldn't get back in.

Awesome, I got it to work using your method.
First I tried the "10 min..." video, but it was unclear in some areas. I had to try a few times (10+) to get it to work. Problem for me was the speed at which I was putting in and out the SD Card. I did it at some odd pattern like In (4 sec), out (.5 Sec), in (4 sec), etc. Then all of a sudden it worked.
Got it rooted .
Thanks again!

Finally got it. Thanks

Spent probably 6 hours messing with it. Not worth it anymore.

What does this mean:
8. connect the phone to the pc and use the modified inf file of Android SDK usb_driver to get the phone connected and drivers installed.
Click to expand...
Click to collapse
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."

dmauro said:
What does this mean:
I've connected the phone, it shows up when I type "adb devices", but I have no idea how to "use the modified inf file... to get the phone connected and drivers installed."
Click to expand...
Click to collapse
if your phone shows up then you may proceed further. Howerver if after quite a few tries you still can't root then you should try updating the driver with the modified inf file.
go to your device manager, you should see the very first item should be Android Phone. right click on the phone and choose update driver and point to the modified INF file.
if your pc tells you that it cannot find a better driver, just uninstall the phone from device manager (right click and choose uninstall), unplug the phone from the pc, wait about a minute and plug the phone back in - but use a different usb port just in case. Then when found new hardware manager comes up point it to the modified INF file.
Good luck.

Doesnt work for me. annoying
*edit* Finally got it 7 seconds awesome

I cannot get my inc to take the driver .inf file. I have edited it correctly, tried forcing the driver to it, and it keeps telling me that the driver is not valid for a 64-bit os. Tried doing it as a legacy device as well.
Win 7 ultimate 64-bit

dont see the plus sign
hit the plus sign in the right window for the repository well for some reason i dont see any plus sign in there to hit tell me what i might be doing wrong

Please Help If You Can
I am logged in; got the recovery; followed the instructions, and it didn't say unrevoked. so i did it again and
did a whole bunch of things
Finding update packge
opening update package
verifying update package
installing update
veridying curernt system
unpacking patches
removing unneeded files
patching system fioles
symlinks and permission s...
then I got
e:multiple firmware images
e: can't store zip image
installation aborted
Now I also cant get into ADB SHELL
when I type adb shell I get
- exec '/system/bin/sh' failed: No such file or directory (2) -
but no prompt
I will try to stay logged in and everything BUT PLEASE HELP. What do I do?

Thanks for these instructions, Op.
I was successful by exactly following your steps.
Edit to provide additional details -- I tried unsuccessfully upwards of 100 times following the instructions in the 10min video. A couple things that probably attributed to the success of this method for me:
1) Formatted 2GB card to FAT32 (4096) as recommended.
2) Uninstalled HTC Sync / HTC Driver Installer. I used the "SDK Setup" to download the USB drivers.
A tip if you're having trouble getting the USB drivers to download... I had to go to the "Settings" menu in the Android SDK and AVD Manager, and check the "Force https://... sources to be fetched using http://..." otherwise the Available Packages menu would fail to get the repository.xml.
I then applied the recommended changes to android_winusb.inf in C:\sdk\usb_driver\ and used this .inf as the Android Phone driver. It was possible to assign the driver after setting to "Debug" mode in the OS.
3) I started clicking the SD card as soon as the white screen would come up, instead of waiting for a few seconds after it appeared. I used a 2 seconds in, .5 seconds out, 2 seconds in, ... pattern.
4) After each failed attempt, instead of pulling the battery and holding volume- + pwr, I went with the ops method. This was to abort the "loop" tool on the PC, pull the battery, boot the phone normally to the OS, verify the phone was recognized by typing "adb devices" on the PC cmd prompt, commanding "adb reboot recovery" to reset the phone into recovery mode, starting "loop" as soon as the command prompt came back, and finally clicking the SD card as described above.

[Q] need help getting unlocked bootloader(solved)

ive tried doing the tutorial at http://forum.xda-developers.com/showthread.php?t=1622425 but to no avail have got it to work i keep getting stuck at step 5 where im checking my sbk number but whenever i type the commands into cmd it says nvflaSH is not recognized as an internal or external command, operable program or batch file??? sorry cant figure it out i have all the acer drives installed and all files needed any help would be appreciated

gears177 said:
ive tried doing the tutorial at http://forum.xda-developers.com/showthread.php?t=1622425 but to no avail have got it to work i keep getting stuck at step 5 where im checking my sbk number but whenever i type the commands into cmd it says nvflaSH is not recognized as an internal or external command, operable program or batch file??? sorry cant figure it out i have all the acer drives installed and all files needed any help would be appreciated
Click to expand...
Click to collapse
Sounds like either you're not in the correct directory with your CMD window, or you didn't extract the files properly. Try extracting them again to a folder on your c: then open a cmd window there. Nvflash is really a simple app. Also, make sure you are in apx mode. Should see a icon in windows task bar, or you can check device manager.

A little tip, do search for cmd.exe on your pc, and then copy it to the folder where you would like to use it. Much easier than cd (change directory) or any other way that I know short of adding it to your right click menu. I keep a copy of it on my desktop so I can copy/paste it anywhere that I need it.

Make sure you installed the Acer drivers. At first I didn't b/c I had working ADB. You need those Acer drivers for the APX driver in there. I wasted an hour or two on that one!

strongergravity said:
Make sure you installed the Acer drivers. At first I didn't b/c I had working ADB. You need those Acer drivers for the APX driver in there. I wasted an hour or two on that one!
Click to expand...
Click to collapse
I've tried that even tried a reinstall I'm pretty sure I'm typing in the commands wrong or when it says open cmd on V6-Unlocked-ICS-HC-bootloader-MULTI-CWM folder I'm not sure does that mean just open up cmd and input that directory and then the commands or what?

gears177 said:
I've tried that even tried a reinstall I'm pretty sure I'm typing in the commands wrong or when it says open cmd on V6-Unlocked-ICS-HC-bootloader-MULTI-CWM folder I'm not sure does that mean just open up cmd and input that directory and then the commands or what?
Click to expand...
Click to collapse
Connect tablet to pc, make sure you are in apx mode , open the folder V6-unlocked.......... and click on the .bat that you want to run. It should start , no need to open cmd on the folder .

I got stuck but in different way altogether.
if you don't mind going back to 3.2.1 for a few minutes then I suggest doing that. it also installed CWM to which you can install your chosen ROM.
then after this you could just use blackthunders apx tool to flash your chosen bootloader.
I know your problem is totally different to mine and looks like you are just not in the right directory while trying to use nvflash but the way I suggest was very easy and works.
I cant post links right now but if you look in the thread for unlocking bootloader then I posted a link which should help you do it this way. its on page 47.
hope u get it sorted I spent many hours yesterday always getting stuck at various points but after many hours found an easier way.
cheers

tigermrk said:
I got stuck but in different way altogether.
if you don't mind going back to 3.2.1 for a few minutes then I suggest doing that. it also installed CWM to which you can install your chosen ROM.
then after this you could just use blackthunders apx tool to flash your chosen bootloader.
I know your problem is totally different to mine and looks like you are just not in the right directory while trying to use nvflash but the way I suggest was very easy and works.
I cant post links right now but if you look in the thread for unlocking bootloader then I posted a link which should help you do it this way. its on page 47.
hope u get it sorted I spent many hours yesterday always getting stuck at various points but after many hours found an easier way.
cheers
Click to expand...
Click to collapse
Sweet I'll try civatos way then if that doesn't work I'll give it a shot I'm still on honeycomb boot loader so why not ;-) thnx again for the help......how does black thunders tool work sorry for incompetence I thought I knew about tech :'( any help would be appreciated

its basically GUI program which installs a bootloader of your choice in a few clicks.
of course u dont need the ICS bootloader if you were to choose to install FLEXREAPER rom after going through my method.
just install it by the recovery menu after going back to 3.2.1.
cheers
EDIT: If your already on the honeycomb bootlaoder (just noticed) you should be able to do it pretty easy and civatos way will work fine

Dug up this old threaad because i didnt feel the need to create a new one and still never solved this :/ no matter what i do it seems i get stuck at entering downoad mode it enters apx mode fine but wont enter download mode im on ics locked bootloader and have tried uninstall reinstall of drivers multiple times also tried switching pc's. Is there any preferred os to do this on? and does 64 bit vs 32bit matter?
Edit.....nevermind guys tried on a whole different comp and worked fine

[Q] Nexus 7 Fastboot Does Not Work

I am sorry if this topic is covered in other threads. I search around and could only find the developer thread and I am not yet allowed to post there.
--------------------------------------------------------------
I have a new Nexus 7 running Jelly Bean 4.2.1. I have activated developer mode and checked the "USB Debugging" box. Other than that, it is in the default configuration.
I want to root it, so I went to http://forum.xda-developers.com/showthread.php?t=1809195 and downloaded the Google Nexus Toolkit.
After identifying my device (Android 4.2.1 (Build JPP40D) for Wi-Fi Only 32GB), the first option was the install drivers. I did that. The 2nd step was to backup the device and I did that with no problems.
The 3rd step was to Unlock the Bootloader (requires Fastboot Mode). When I try to do this, it says that a Fastboot Device was not found.
I am at a loss here as to what to do?
I have some screencaps. I hope this helps.
Ideas?

http://forum.xda-developers.com/showthread.php?t=1741395

simms22 said:
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
TY, this says I need to be able to use "adb and fastboot". That is the problem. I do NOT know anything about fastboot. I turn off my nexus and then hold the volume up and volume down buttons then turn it on. I get a screen that looks like the image I have attached.
However, I do not know what to do from here. I press the volume up and down keys to change "Start" other options, but Fastboot is not one of the options.
Ideas?

You don't have the right drivers installed. When you see the boot loader screen, you should see 'android fast boot interface' or similar in your device manager.
Sent from my Nexus 7 using xda app-developers app

Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Keep clicking OK a few times, it might find it.
if not, then, press the volume down button until it says reboot bootloader or reboot recovery, sorry i can not remember 100% right now,
press ok a few times more, well keep pressing it and it will find it

adamz2013 said:
Unfortunatly no one will help you here, they will just give you links to docs you have already read.
Click to expand...
Click to collapse
You are replying to a post from December 16th. Doubtful that the OP is still waiting on an answer.
Nice pot shot at people that do try to help, though. Either that or an unmet entitlement issue. No one in here is entitled to an answer for anything. Anything you or others provide in response to an inquiry is a gift, plain and simple. The answers might even be completely wrong or crap; but they are still a gift.
If the OP is still waiting, then they should know that all the detail that they showed (screenshots) are immaterial as they were taken with the device booted into the OS (composite ADB + MTP/PTP showing in Device Manager) instead of the mode that was having communication difficulties - fastboot/bootloader mode.
Immaterial information does not imply that the wrong driver is installed for a different operating mode for which similar information was not provided.
Most of the trouble in these types of post are due to the fact that the posters have no clue how WINDOWS drivers are managed/installed/ etc. That has everything to do with WINDOWS and user skills, and almost nothing to do with the device on the other end of the cable.
Having said that, the principal reason there is confusion is due to the following set of circumstances:
- Casual Windows users are "accustomed to" doing a single install of a driver package when they buy a new device. Even when that device might have many logical endpoints across the USB bus. (Think of a multi-function printer - it might have an SD card slot on it, the printer, a scanner function, etc). When that multifunction behavior exists, usually the OEM provides a "driver installer" package which will actually install multiple drivers, depending on the plurality of USB endpoints in the device.
- Unfortunately, if you carefully inspect any of these three driver bundles:
- Google (SDK) USB Driver
- Asus Nexus 7 USB Driver
- XDA "Universal Naked Driver"
you will find that (as shipped) NONE OF THEM will work for all of the following modes of the Nexus 7:
- Fastboot mode
- ADB Mode, OS (Single or Composite)
- ADB Mode, Custom Recovery
- APX Mode
- PTP Mode*
- MTP Mode*
That's right. As shipped NONE OF THEM will handle all of these cases. The "as shipped" part is a reference to the fact that a trivial edit of the "android_winusb.inf" file for any of them will allow a single driver to handle all fastboot and ADB modes.*
* The MTP/PTP drivers are meant to be handled by MS Windows generic class drivers; in the case of Windows XP you might need to install a Windows Media package to get the MTP driver - I'm not sure that it is part of Vanilla XP SP3
So, anyhow - people get confused because they "install the driver" for one mode (usually ADB), and then are surprised when they boot the device into a different mode (fastboot or ADB running under custom recovery) and surprise, surprise - their PC says "unknown device".
My advice?
Install the Asus Nexus 7 Driver for everything but the Custom Recovery ADB mode, and then install the Universal Naked Driver for that.
Or, prior to installation fix up the android_winusb.inf file that comes with the Asus driver so that it also supports
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001
%GoogleNexus7ADBInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
Then a single driver will support everything but APX, MTP, and PTP. The latter two of which are provided by Mister$oftie, and the first of which is currently of unknown value to Nexus 7 rooters.
cheers

That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.

juicejuice said:
That is actually a nice clear description, worthy of a wikipedia entry Seriously though the driver situation with Android gives me the sh17s sometimes.
Click to expand...
Click to collapse
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.

bftb0 said:
Neither Linux nor OS/X require any drivers to use either ADB or fastboot.
It's a Windows problem, not an Android problem.
Click to expand...
Click to collapse
I am a Mac user, and I'm having problems with fastboot. My nexus is unlocked, and I'm trying to flash the lastest 5.1 factory image. I was rooted long ago, but really have no need for root, and lost it during one of the OTA's. I'm not a noob by any means, but none of my terminal commands are working, because fastboot has decided to disappear on me. Any suggestions would be appreciated.
I can't even get TWRP because I don't have root, and I can't get into fastboot.
Edit.....I'm an idiot....I figured it out. On top of it all, my USB cable sucks too so that didn't help any.

[Q] Controlling Nexus 4 on the PC after breaking screen, possible?

Hey guys,
Haven't been here for a while. Okay, so I have a bit of a dilemma and every solution I've found requires something I just can't do. Here's the situation: my screen is broken, it has a lock screen, not in developer's mode, not unlocked.
This means:
I won't be able to transfer my files over, as I have to get past the lock screen
I can only install applications from Play store on my computer, but can't launch them
No use for any method that requires phone to be rooted
Can't even activate any USB options to transfer files some other way
Still need to be able to control it to create backups and such of important SMS messages, get files off
Does anyone have any suggestions at all? I don't want to have to resort to replacing the screen, as that'll end up costing me enough time and money where it's more cost-effective to purchase a new phone; however, I really need what's on my phone as soon as possible. Thanks in advance.

I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key​11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.

machoman1337 said:
I think I have a solution for you: http://forum.xda-developers.com/showthread.php?t=2177440 Specifically, you'll want to read this post:
In the future, always enable USB debugging in case of incidents like this. You can then use ADB commands to do a heck of a lot of things. Of course, it does make your phone data vulnerable if it gets stolen, but I'm willing to take the risk, plus 10 wrong PIN tries = reset anyway.
Click to expand...
Click to collapse
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.

ikarma said:
Now with 4.2.2 the adb device appears as offline and the only way to bring it online is to use the touch screen.... I have an important email on my phone just looking at me and its driving me completely INSANE that I cannot get to it.
I have to wait 4 days to get a screen in just to get to this important email..... THANKS GOOGLE!
oh and tmobiles insurance is a joke $100 deductable... the clear your phone. my way $79 new screen and same phone.
Click to expand...
Click to collapse
where did you get the screen for $79???

hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device

michaeliang said:
hi, what does this mean?
2. Install the USB driver from the SDK so that it appears as an ADB device
Click to expand...
Click to collapse
1. It means that if you have the SDK Manager installed on your computer, somewhere between the last packages at the bottom of the list, you'll see "android drivers" (or something similar). With those drivers, your device will show up in "Device manager"(the Windows' one) as an adb device.
2. But if you don't want to get the SDK Manager and be quicker, you can download only those drivers, directly from the "Google developers" page and install them manually by going to "Device manager", right clicking on the Nexus 4 (it will appear with a yellow triangle on it, maybe), then "Update driver", "...BROWSE computer...", then click again on "Browse", then go to where the drivers have been downloaded and select the entire folder by highlighting it and clicking ok (or something). The folder with the driver would look like this "latest_usb_driver_windows" and inside you'll see another folder called "usb_drivers". That's what you need to select and install.
So that's what you need to do to make your phone appear as an adb device in "Device manager". And, of course, adb let's you do a lot of stuff to your phone through your computer, but probably you already knew that.

[guide] fix wiped nexus 7

So this is a guide on how I alone fixed my Nexus 7 after accidentally wiping EVERYTHING with TWRP while trying to flash SmoothRom 5.2.
I searched here in XDA, Google and so on for solutions. I found many, but all required using ADB, which I'm really not good with when it comes
to pointing out the location of ADB using the command prompt. So little by little I gathered hints and accidentally invented my own solution.
Using an old laptop that has no WiFi card thus cannot be connected AND running Windows XP, along with my trusty old LG Optimus S running CM9 as my download device and flash drive. I'm going to skip the details on all the mistakes I made. Basically my Nexus 7 could only go into fastboot and TWRP 2.5.0.0.
1. I downloaded the Google Nexus 7 provided in a site other than XDA
because the Goo.im provided site would endlessly refresh on my Optimus S.
Original XDA link can be found here: http://forum.xda-developers.com/showthread.php?t=1809195
2. Since the toolkit program added to the desktop requires the downloading
of a stock factory build, I navigated to the source of the program instead and
used tkmain.exe to access the main menu. You guys will probably not need
this step, just in case you have no internet on your computer.
3. Device not recognized. Obviously I haven't mentioned anything on drivers.
Fastboot mode was pointless as I got the device detected but anything I'd
try with the toolkit was an error. So I booted my Nexus 7 into TWRP. That has
SEPERATE drivers as I learned from trial and error. Using the device manager
I updated the drivers for my device which appeared as "Android" (was "Unknow " in
fastboot) MANUALLY and pointed the folder to the toolkit's folder, from there,
the "Drivers" folder (generally should be C:\Google_Nexus_7_ToolKit\drivers)
and it automatically installed the proper driver which made my device appear
as a Google Galaxy Nexus. (Use these same steps to get fastboot drivers)
4. Serials now appeared in toolkit. That's good! From there I closed the toolkit,
moved my old CM10 (cm-10.1.2-grouper.zip) which I had before wiping everything
into the provided "put_files_to_push_here" folder found in the main folder of
the toolkit. Then opened the toolkit again as mentioned in Step 2, used option
(13.) Push Files to Device, next menu option (2.), typed "yes", typed the name of the
zip file mentioned in the third sentence of this step ( you will type in yours)
and then typed "/sdcard/" and waited.
5. At the end it confirmed that the file was successfully pushed and asked some
other questions I typed "no" to. Note that during that waiting period something
appeared mentioning "blabla failed: Success." I'm assuming that's natural as I got
that and no other words appeared until the file was confirmed pushed. The end
Hopefully this may help any other future accidental wipes of users or visitors themselves on XDA. I did everything possible to not come and post a "help me" forum and well this guide is my outcome. This would be my second post after my disaster with my Kindle Fire HD 7.
Maybe this will be obsolete as the new Nexus 7 is soon to be released, but for those who purchase the first late, here you are.
GOOD LUCK and now to figure out how to get my SmoothRom without that "acore" error.