Database Users

ADB Device Not Found! :(

OK, posted this in the Q&A section with several responses but no real answers. Figured I'd post it here before another section where it might get locked or moved.
Anyway, ADB was working fine until a few days ago. Now it says "error: device not found." Fastboot still works just fine. I've tried everything I can think of to get it working again. I've uninstalled and reinstalled the usb drivers, removed the Android SDK from my PC and reinstalled, wiped and reflashed my device, made sure Debugging is on, and tried getting ADB to work on all 4 of my PC's. All running either Windows XP or Windows 7. No dice. Can anyone help? Thanks in advance.

The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?

UnderCoverLover said:
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
Click to expand...
Click to collapse
Thanks for the reply. If you read my OP you'll see that I've made sure debugging is on. In fact, debugging is also enabled by default after a wipe and clean flash. Unfortunately my problem isn't as simple as enabling usb debugging.

Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!

deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Thanks for the response. I'll give this a shot when I get home. FYI, I didn't change devices. Same Nexus One I've had for the past month. Just one question: When you say,
"In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices"
I don't know what this means. Where can I access this? Thanks!

Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.

markouk said:
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
Click to expand...
Click to collapse
Yeah, I've had the phone booted up normally. Thanks though.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MaximReapage said:
Click to expand...
Click to collapse
Thanks a lot.

deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!

Part Four said:
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Click to expand...
Click to collapse
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...

myn1 said:
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
Click to expand...
Click to collapse
Done and done, days ago. Still no dice. This is ridiculous.

Still having problems. Tried everything I can think of, and everything suggested to me by the XDA community. I don't know if this will help any of you guys help me, but when I type "adb devices" into a command prompt, it returns:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
And then shows nothing. So effing frustrating! EVERY computer I have (I actually have tried it on 6 different laptops and PCs) returns the same error and cannot find my Nexus One. WTF happened!? HELP!

Part Four said:
WTF happened!? HELP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217

pvillasuso said:
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
I'm sure you're trying to be helpful but, if you've read through this thread, you'd know that I've already done all of that. OBVIOUSLY, I've done all of that because, like I said, ADB STOPPED working. In order for it to stop, it must have, at some point, worked just fine. And it did. It worked perfectly until recently. So, yes, I've installed all the damn drivers I need. But, no, it's still not working. It's infuriating.

debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.

also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

temperbad said:
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
Click to expand...
Click to collapse
Yes. *Sigh*

Do you see this device ( pic ) @ device manager :
If you do , there is no reason for adb commands under DOS prompt for not workig well ... really weird

temperbad said:
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What do you mean, I'm "good?"

[GUIDE] Android Sdk with fastboot, adb and usb drivers

!!!THIS IS NOT A ROOTING GUIDE!!!
This pack contains everything you need to connect and use your nexus s on your pc
Will work on XP, Vista, 7
!!!HOWEVER 7 HAS THE BEST SUCCESS!!!
included:
* Fastboot
* ADB
* USB Drivers (32bit and 64bit)
Links:
SDK:
http://www.fileserve.com/file/RZqMfeC (sdk, fastboot, adb)
Mirror:
http://hotfile.com/dl/92897052/df7338b/SDK.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
DRIVERS:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
Mirror:
http://hotfile.com/dl/92897696/7ae5290/drivers.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
To be able to install drivers you have to have your phone booted into fastboot and connected via usb (Thanks to mmas0n)
How to force drivers to install:
Thanks to gravis86
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2a. NS Right-Click "Android 1.0", and click "Update Driver Software..."
2b. NS4G Right-Click "Nexus s", and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
How to install ADB and Fastboot:
1. download and place in the root of your C:\ drive
2. extract here (not into a sub folder)
3. now open up control panel
4. find system
5. goto advanced settings
6. goto environmental variables
7. in the box that says "system variables" scroll down to find a variable "Path"
8. highlight it
9. click edit
10. add this to the end
;C:\android\tools
Click to expand...
Click to collapse
yes the ; is needed
11. click ok
Now when you open cmd (command prompt) you can use "adb" or "fastboot" anywhere with out locating the folder first
You should be able to do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I have helped you please hit the thanks button

I have followed the directions to the letter and when I type fastboot devices it just goes back to command prompt. I tried typing fastboot oem unlock and it just said waiting on device. Adb devices typed produces "list of devices attached" I boot the phone into fastboot mode and and the usb is plugged in but I keep getting the same results. Am I preparing the phone incorrectly?The adb worked with my Vibrant but the fastboot failed there as well. I would greatly appreciate any and all help you may offer. As I am sure you can tell I am another one of those ignorant nubies.LOL

have you installed the usb drivers?
you will have to force them to install

mazodude said:
have you installed the usb drivers?
you will have to force them to install
Click to expand...
Click to collapse
Yes I have. adb works with my Vibrant but fastboot does not and neither one works with the Nexus s. I have read and reread and followed directions but nothing seems to work. Should I be looking to do something on the phone other than booting into fastboot mode? The Nexus S shows fastboot mode at the top of the screen and I have assumed that I just use the computer from there. On my Vibrant booting into recovery does not show anything about fastboot. I really do appreciate your help I am trying very hard to learn quickly so I can be of some help instead of a burden
I don't know how to force them to install. I went in an opened the folder and I assume they were installed. I do have usb debugging enabled
Edit Just copied usb drivers to C:\android and c:\android/tools and still the same results. I have done everything I can think of but i guess I am not getting the drivers installed properly.

to force them, go into control panel-> administrator tools->computer management
then goto device manager in the sidebar.
I cant remember what the device is called but you should know when you find it.
right click and hit update drivers.
hit browse for drivers and find the drivers in C:\android\google-usb_driver
Note: phone has to be in fastboot to be able to install the drivers
edit: I forgot the drivers opps
link:
http://www.fileserve.com/file/ZM9hbvH
edit: this video might help
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/

I just downloaded the drivers and placed them in C:\android and then went into device manager and hit update drivers and then browse for drivers and it said no drivers found. I was in C:\android/google-usb drivers.

have a look in the post above i just posted a link to a vid
edit: are you using 64-bit?

no 32 bit I will look for the video. Thanks so much for your kind and patient help!!!

I think there is a trick in the video to get it to see the device in fastboot
edit: there are some drivers here
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

there is no video but I did read the directions and I believe I have done all that they state. Should my PC say installing drivers when I plug my phone in? It did and said one driver failed to install.

yea.
If you don't see a video (at the top) disable ad blocking
also the driver that failed try to force it (using previous method)
If anybody could help that would be great, then I will add it to the first post

Followed this guide and unlocked and rooted my friends Nexus S.
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/

@shaolinmastr well that's good to hear

I still have no success installing the drivers. Are you sure that the drivers were in the last zip file? I have gone over and over it for the last 6 hours and am at the same place I started. NO adb and no fastboot on the Nexus S and adb working on Vibrant.but no fastboot . I guess it is time to take the Nexus S back and get a refund. It is not worth the lack of results with so much effort. Thanks for you help.

Save yourselfs the hassle and just install PDAnet and you should get the drivers to work.

I was having this same problem and used pdanet to get the correct nexus s drivers. You can dload pdanet to your PC and just plug your phone in via USB andfollow the directions.

So tmello56, pdanet worked for you?
If so I will extract the drivers and add them to the first post

WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
Sometimes Windows needs to be forced to use a driver that we know works, but Windows thinks doesn't. This is similar to what mazodude posted, but is just a few steps further. To do this:
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2. Right-Click "Unknown Device" or whatever it's called, and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
9. WIN!!!

@gravis86, very good explination will post in 1st post

Just wanted to post my results...
I was using the correct drivers, but was installing them while the phone was booted and connected. I could use ADB and mount the file system, but could not use fastboot. I then discovered that if I installed the drivers while the phone was booted into the bootloader and connected, it detected the device differently and fastboot worked.
Now rooted + custom recovery. Awesome.

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting! v1.2
Hey XDAers. Getting ADB setup and working is an essential part to rooting your Android device and helps layout the foundations to better understanding the language and using it in this environment. While not going into extreme detail, this is just a quick guide or overview on the first part of rooting; Getting ADB setup and working.
** Make sure your Transformer is not currently connected to your PC yet. We will be installing device drivers first (Step 7) and modify a setting on your tablet first before connecting to your PC (Step 8).
Step 1 :
Download and install the Android SDK.
You can download the SDK from the Google Developer's website. I have linked for you the download page and a direct link to the installer (Note: the direct link may change in the future with future versions, I will try stay on top of this and change the link)
http://developer.android.com/sdk/index.html
http://dl.google.com/android/installer_r10-windows.exe
*New Version : http://dl.google.com/android/installer_r11-windows.exe
You may or may not be prompted to install the latest version of Java if you haven't done so already, install it, and you may or may not have to reboot your computer.
Step 2 :
Once the install is complete, navigate to the directory in which you installed the SDK and launch the SDK Manager executable. It may or may not ask you to download and install the Java JDK, do so if you haven't already.
*When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already*
Answer :
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead.
Thanks Crimton!
Click to expand...
Click to collapse
Step 3:
Once the SDK Manager is launched, it will look something similar to the window below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will want to do something along the lines of update all or install all. This way it will download all the latest packages and you willhave the latest SDK tools installed.
Once that is complete, you can exit out of the SDK Manager.
Step 4:
Open up a command prompt window. You can do so by holding the WinKey+R, a run window will appear, type CMD, and hit enter.
Step 6:
Within the Command Prompt window, navigate to the Android SDK folder\platform tools folder (Command Prompt command : CD foldername\foldername\foldername\etc)
Step 7:
Now install the ASUS Sync software if you haven't loaded it previously. http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download. Just select your operating system, hit download, then install.
Why are we installing the ASUS Sync software you ask?
Well mainly because it has USB drivers that will help your PC operating system detect and display your ASUS Transformer. Without the drivers, ADB wouldn't be able to detect your device most likely!
*For other android devices, you will need similar software from that manufacture. HTC Sync for HTC devices as an example.
Click to expand...
Click to collapse
Step 8:
Enable USB Debugging on your android device / Transformer.
Go to Transformer Tablet, go to settings -> applications->Development, turn on USB Debugging.
Step 9:
Connect the USB cable from your android device / Transformer to the PC. It will begin to automatically install drivers, let it do so and complete. May ask to reboot machine.
Step 10:
Once that is done, go back to the command prompt. Run ‘ADB Devices’
You should see something like above, indicating it detected the transformer, if not, run the following ‘adb kill-server’, ‘adb start-server’, ‘adb devices’
Ok, if you are seeing something like the screenshot above then success, you have successfully gotten ADB up and working! Congratulations! That wasn't too hard now was it? You can now follow one of the root guides and follow the directions and you should be on your way to a fully rooted device. Cheers!
-------
Troubleshooting:
In the event you complete the steps above but your computer either will not recogonize the Transformer in Windows as a device, or ADB will not see it please try the following to see if this will fix it for you. You only need to try these if the above steps aren't working for you, but most people, they work fine.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
-------
Notes:
-If you want another guide on something else, let me know, and I will see what I can do.
-Yes this has been posted a million times I know, but I thought this might help out those few people that don't feel like looking around. Plus, it has nice color illustrations. Who doesn't like picture books?
-------
Credits
Crimton for Java JDK workaround when not showing as installed
sourworm for new link to SDK installer

Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.

stuntdouble said:
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
Click to expand...
Click to collapse
Will do when I get home, thanks for the tip.

Ill add this to the FAQ

One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.

I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
Glad you got it resolved, I will edit the guide and make note about java installation.

Daughain said:
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
Click to expand...
Click to collapse
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740

neilkarunatilaka said:
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Click to expand...
Click to collapse
at a glance, even that thread makes it look like more trouble than it is. but good info

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
How did you fix it? I've been struggling with this same issue for at least a month now.

n25philly said:
How did you fix it? I've been struggling with this same issue for at least a month now.
Click to expand...
Click to collapse
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk

Crimton said:
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
lol, simple solutions are good. Just wish it didn't take me a month to find that one out.

Very simple and easy to follow. Thanks OP.

I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?

randy_c said:
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
Click to expand...
Click to collapse
Sorry to hear that. Off the top of my head, I'm not sure what could be causing this. But here are a couple things you can try. And please let us know what happens next.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html

I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!

andrew53517 said:
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
Click to expand...
Click to collapse
1) First thing you can try is the famous 'adb kill-server' 'adb start-server' commands and see if that will get it going. Also 'adb usb' will restart the daemon listening on USB, so maybe that could make it usable. If not, make sure the ASUS Sync app is not running, and perhaps see if there are any running services/apps on your Transformer that could be causing the conflict. Download System Panel Lite from Market and tell it to end all apps, then try again (make sure USB Debugging is enabled)
If you tried all of that, and still no dice, make sure no USB Drives or Memory Cards are connected, then connect the Transformer (w/ USB Debugging), go to Device Manager, uninstall the USB drivers for the device if you can find it or it may show up as a USB Mass Storage device under USB Controllers, then disconnect the Transformer, reconnect the Transformer, it should reinstall the drivers for the Transformer since you already have ASUS Sync installed, then retry.
If again still no dice, try using the ASUS USB Windows Drivers and going to Device Manager and updating the drivers with those you downloaded (download the correct ones for your particular operating system, and then try again.
Now, if this still doesn't work, let me know, and I'll try think of something else. Maybe someone else has had this issue and come up with a workaround or solution, but I'm drawing a blank currently. I'll sleep on it and see if I can think of anything else
2) You don't have to type that up all the time. What you can do is navigate the platform tools folder (or whatever folder has the adb files), then if on Win 7, hold shift and right click on the folder (Platform Tools for example), and you will see an Open Command Prompt here. Hit that, and it will already be in that root folder. But in general, in a command prompt window, once you have navigate to the specified folder, you will be in that folder, so you will only need to type ADB 'command' if that makes sense.
[/LIST]

I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.

andrew53517 said:
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
Click to expand...
Click to collapse
If you get a chance, try this on a Windows XP or Windows 7 machine that you haven't connected the Transformer too yet, and follow the guide exactly, and I'm pretty sure it will work without a problem I'm just thinking something has happened when it loaded up the drivers for you initially and that is why you are having the issues, or some background process on either Windows or the Transformer is making the device seem "busy", thus giving you the not ready error, as this process has worked for many many other users.

I was just thinking about it. Maybe I can try that on my downstairs computer. Ill give it a shot Sunday night and see how it goes...ill let you know...

Nexus 7 not showing up in Windows

Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?

C'mon... Somebody..:? Anybody?

Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium

do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.

androidkid311 said:
Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried that. Doesn't work. Nothing makes it register.
Billchen0014 said:
do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.
Click to expand...
Click to collapse
Tried this too. I've been using the new factory cable and it doesn't work. I've tried five different cables and different usb ports. Also tried factory resetting and different roms as well.

Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck

Wilks3y said:
Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck
Click to expand...
Click to collapse
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.

Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Username invalid said:
Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
Click to expand...
Click to collapse
Is tha driver different from the drivers I downloaded from the SDK manager?

nicholi2789 said:
Is tha driver different from the drivers I downloaded from the SDK manager?
Click to expand...
Click to collapse
It is version 7.0.0.1.

nicholi2789 said:
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.
Click to expand...
Click to collapse
No worries mate best of luck !!
Let us know if not and I'll try find another way

I found this while searching. http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip . USB drivers for win 8 problems-
Sent from my Nexus 7 using Tapatalk 4 Beta

best and quick solution. Open "settings"
nicholi2789 said:
Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?
Click to expand...
Click to collapse
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC

iralamanoj said:
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC
Click to expand...
Click to collapse
Haha, thanks for the help, but I wish it were that simple. It was a first Gen Nexus7 by the way too.
I'm no novice to the ways of Android, and i tried everything under the sun to get it to work. Nothing Would make it show up on the computer.
Anyways, it just ended up turning off one day (with a fully charged battery too) and wouldn't turn back on. I ended up calling Asus and they repaired it for me. It had a burnt out USB port. They fixed it and it's up and running fine now.
Long story short, be careful what you buy on eBay one, and two, Asus has EXCELLENT customer support. From the day I called them to the time I got it back fully repaired only took 7 days exactly. And I didnt have to pay for shipping. If you ever have a problem with an Asus product don't hesitate to call them.

I just solved my problem. The Nexus 7 was not showing up in the device manager and windows explorer. Once usb plugged it would charge but do nothing.. In device manager I found "ACER Composite ADB Interface". I googled it and this is the problem. apparently Windows update install this thing but it doesn't work with the Nexus 7. You have to uninstall it (don't forget to check the delete from computer box or else it will reinstall itself). Then look for this : ASUS Android Composite ADB Interface Driver 8.0.0.1 for Windows 7 64-bit and download it.(sorry I can't post links)
Now with your Nexus 7 plugged in update your driver by selecting the browse my computer option and locate the file you just downloaded and there you go it should work. After months of searching it's finally working. :victory:

[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)

The MTP fix is ONLY for the STOCK ROM and handles the case
USB debugging disabled - MTP working
USB debugging enabled - MTP not recognized
If you cannot get MTP working at all, I suggest you
uninstall your current device drivers
using device manager/devmgmt.msc or Nirsoft USBDeview
you may want to
set devmgr_show_nonpresent_devices=1
prior to starting devmgmt.msc and
view hidden devices within devmgmt.msc
REBOOT
reinstall
The ADB fix is for getting ADB to work while in Recovery (tested on stock and twrp).
Google USB device drivers can be found here:
Driver info/download - http://developer.android.com/sdk/win-usb.html
Direct download - https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Nirsoft USBDeview can be found here:
http://www.nirsoft.net/utils/usb_devices_view.html
use this to remove old driver assignments, sort by date and choose Nexus 7 entries
====
MTP mode (with USB debugging enabled)
I got tired of having to disable USB debugging to get the MTP device recognized.
This happens because the USB ID for the MTP device changes when USB debugging is turned on and isn't recognized by windows anymore. The particular problem is the compatible IDs list from the tablet is not advertising USB\MS_COMP_MTP when USB debugging is enabled and windows doesn't know to use the MTP drivers.
I created the following driver .inf file to fix the problem so you can have usb debugging enabled and still have MTP working.
I only tested it on Windows XP.
This ONLY fixes the problem where MTP works with USB debugging DISABLED, but stops working when you have USB debugging ENABLED.
If you can't get MTP working under any circumstance, you have some other problem. Try
double checking
Settings->Storage->3 dots->USB computer connection->Media device (MTP) is enabled
removing your drivers using Nirsoft USBDeview and rebooting
When you turn on USB debugging and windows asks for an MTP driver, just provide the following and it should install the driver hooks and start recognizing the MTP device from that point on.
Let me know if there are any issues and I'll try to address.
mtp_driver.zip is for USB debugging enabled and stock ROM
INFO: this same method of fixing the unrecognized IDs might not work for custom ROMs. I have forced the MTP USB ID for a custom ROM to be recognized and it does so successfully, but when the windows MTP driver tries to initialized the device, it fails. This indicates there may be additional issues with the MTP support on the custom ROM side.
====
ADB support (within Recovery)
I wanted to get adb working in TWRP and adb sideload working in stock recovery but adb wasn't recognizing the device.
Here we have the same problem as above. The USB IDs for the ADB interface change when you are running Recovery and are no longer recognized by the driver. You'll notice that when you are running TWRP you will see an unknown device called "flo". This is actually the ADB USB interfaced but windows doesn't know that.
I created a simple fix for this problem. Just download the official Google USB/ADB drivers from above. Then download android_winusb.inf.zip from the attachment. Unzip the Google drivers and replace the android_winusb.inf file in the Google drivers with the one in the attachment.
android_winusb.inf.zip - unzip this file to get android_winusb.inf. Replace the file of the same name in the Google USB drivers with the one in this zip file
If you feel replacing a file is too complicated, the following attached file has all the changes done for you. Just unzip to get the adb_driver folder, right-click on the "flo" device, choose install drivers, and point the driver install to the adb_driver folder
adb_driver.zip - if you want everything already done for you, this file includes the driver inf and the driver so you don't need to replace anything. This will work for adb within both Android and Recovery.
platform_tools.zip - this is adb 1.0.31 that supports RSA identification introduced in Android 4.2.2
====

Wow or strange should be more of the reply. I have done this before but it never worked. Thanks for the help. For anyone else needing help here is what I did. First opened the Nexus Tool Kit, then Full Driver Installation Guide, launched USBDeview, then - In particular look for devices with Vendor ID - "18d1" or... "04e8" - Simply right click these devices, and select the option to: - "Uninstall Selected Devices", final step unplugged the device and plugged it back in and it worked. Also MTP enabled USB Debug unchecked. Thanks again...
-AkWingnut

sfhub said:
This fix is ONLY for the STOCK ROM and handles the case
USB debugging disabled - MTP working
USB debugging enabled - MTP not recognized
If you cannot get MTP working at all, I suggest you uninstall your current device drivers (using device manager/devmgmt.msc) and reinstall.
Google USB device drivers can be found here:
Driver info/download - http://developer.android.com/sdk/win-usb.html
Direct download - https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
====
I got tired of having to disable USB debugging to get the MTP device recognized.
This happens because the USB ID for the MTP device changes when USB debugging is turned on and isn't recognized by windows anymore. The particular problem is the compatible IDs list from the tablet is not advertising USB\MS_COMP_MTP when USB debugging is enabled and windows doesn't know to use the MTP drivers.
I created the following driver .inf file to fix the problem so you can have usb debugging enabled and still have MTP working.
I only tested it on Windows XP.
This ONLY fixes the problem where MTP works with USB debugging DISABLED, but stops working when you have USB debugging ENABLED.
If you can't get MTP working under any circumstance, you have some other problem.
When you turn on USB debugging and windows asks for an MTP driver, just provide the following and it should install the driver hooks and start recognizing the MTP device from that point on.
Let me know if there are any issues and I'll try to address.
mtp_driver.zip is for USB debugging enabled and stock ROM
EDIT: I removed the following file since it appears the issue with MTP on Paranoid is on the ROM side. The USB IDs were different and the driver inf I provided was able to get the windows side to recognize the MTP device and associate the MTP drivers, but when the MTP driver tried to initialize the MTP device, it wasn't responding properly.
mtp_driver_ubdebug_paranoid.zip (experimental) is for USB debugging enabled Paranoid ROM
If you need it just let me know.
Click to expand...
Click to collapse
There is a easier way if your running Windows 8 go into device manager while the nexus 7 is plugged in it show Google adb interface something like that so click on it and find hardware updates then from there hit manual update it give youa search option and another just pick manual it show the adb one or mtp select the one for mtp and you should be okay I will post pictures later on so it makes it easier to understand my instructions
Sent from my Nexus 7 using xda app-developers app

dakunclear said:
There is a easier way if your running Windows 8 go into device manager while the nexus 7 is plugged in it show Google adb interface something like that so click on it and find hardware updates then from there hit manual update it give youa search option and another just pick manual it show the adb one or mtp select the one for mtp and you should be okay I will post pictures later on so it makes it easier to understand my instructions
Click to expand...
Click to collapse
Not sure if this is particular to newer versions of windows or you have installed some previous drivers which allow MTP to show up when you do the manual driver install but for winxp even though it has the MTP driver on the system it won't give you the option to use it when you click on Android phone/devices, Portable devices, or Imaging devices categories under the manual driver install option. It just says no compatible drivers.
I'm a little suprised if your win8 install is showing MTP as a compatible driver, why it didn't just auto-install this from the beginning w/o user intervention?
The problem some folks are encountering (at least on older windows) is that since the tablet no longer advertises USB\MS_COMP_MTP in the compatible ID list, windows doesn't know what type of device this is, thus it doesn't provide you with any device drivers to use.

Added support for ADB within Recovery (tested on stock and TWRP)

Wow!
Welcome back! Hope we held down the fort well enough while you've been away!
Sent from my SPH-L900 using Tapatalk 2

Thanks, been a while. Haven't been around to look at the fort yet. Have new toy to play with.

sfhub said:
Thanks, been a while. Haven't been around to look at the fort yet. Have new toy to play with.
Click to expand...
Click to collapse
Welcome back! It's good to see you deving again!
Stop by the Pub some time. There are plenty there that would love to say "Hi!" to you.
Bugging up my phone, so you don't have to!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Need help? [email protected] on GTalk or by Email

TrayLunch said:
Welcome back! It's good to see you deving again!
Stop by the Pub some time. There are plenty there that would love to say "Hi!" to you.
Bugging up my phone, so you don't have to!
Need help? [email protected] on GTalk or by Email
Click to expand...
Click to collapse
Say hi, pass him a round, and thank him for his work
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2

Great to see your work again SFhub! You've been missed.
Sent from my GT-I9505G using Tapatalk 4

notianag hovels
My New nexus 7 was connected to PC(windows7), USB debugging enabled:
I can see files from the PC.
But adb can't reach Nexus..
D:\>adb version
Android Debug Bridge version 1.0.29
D:\>adb devices
List of devices attached
while I connect my Galaxy SIII to PC, adb works:
D:\>adb devices
List of devices attached
cc05905f device
Anyone have any clue what happen to the Nexus7?

molo88 said:
My New nexus 7 was connected to PC(windows7), USB debugging enabled:
I can see files from the PC.
But adb can't reach Nexus..
D:\>adb version
Android Debug Bridge version 1.0.29
D:\>adb devices
List of devices attached
while I connect my Galaxy SIII to PC, adb works:
D:\>adb devices
List of devices attached
cc05905f device
Anyone have any clue what happen to the Nexus7?
Click to expand...
Click to collapse
You need adb versions 1.0.31 or greater. Earlier versions do not support the RSA identification introduced in android 4.2.2
I added platform-tools.zip to the first post which contains the adb version you need so you don't need to do large downloads.

thanks
work flawless
thank you very much

Worked perfectly with CleanRom 1.6
Many Thanks !!

shortyboy said:
Disable debugging in developer options or gotto this thread
http://forum.xda-developers.com/showthread.php?t=2391236
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Myster said:
Worked perfectly with CleanRom 1.6
Many Thanks !!
Click to expand...
Click to collapse
Just wondering how u did that? http://forum.xda-developers.com/showthread.php?t=2447839

I honestly do not know ...
I use an Outlook sync application called Android Sync ( http://www.android-sync.com ) which comes with the option to install universal android drivers and device specific drivers so maybe a driver from that package in combination with this mtp fix worked

debbuging mode
Hi,
im new to xda and this was the most similar topic to my issue with MTP i could find, so sorry if i'm posting it in wrong one.
Im having the opposite problem. Its not like i cant live with that, since i can move my files freely as long as i enable usb debbuging. But still, its bothering me.
I can connect my Nexus 7 only with debbuging mode enabled. When i disable usb debbuging, win7 wont recognize my nexus as MTP device (PTP works). I can see Nexus 7 in device manager as "other device" but windows isnt able to install drivers correctly.
I tried to fix it by uninstalling the old nexus drivers (both manually and with usbdeview) but after a reboot im having the same issue.
When i try to update the drivers manually, it wont let me use the drivers distributed by google and asus support.
Anyone had the same issue?
Thanks and sorry for my English

Similar problem. Driver was installed and working. USB debugging on and only PTP modus gave me access in Windows. MTP never works. After reboot no connection possible at all. Only for adb in fastboot modus connection was possible. Deinstalling, reinstalling do not fix the problem. Reimaging Windows solves the problem till I reboot Windows...

Thank you so much for the information!
I was trying to sideload kitkat when my computer stop recognizing my nexus in recover! Your modified ini did the trick!

Hi! This doesn't work in windows 8.1 pro 64 bit. I get this:
I tried two different downloads with the same result so the hash mismatch is not because corrupt files. I'm clueless.
Correction: the modified ini doesn't work, nor the adb driver or the original driver.
FIXED: You have to boot windows with driver signature enforcement disabled. This is something that got implemented in windows 8. The issue is that the driver isn't signed and in windows 8 you can't install unsigned drivers unless you do this advanced bootup.