After I started using my Win 7 system, I had to do the whole process of updating and flashing my device. After like 3 hours going back and fourth to find the solution, I found it is a pretty strange way. In a place where I would never have thought before:
The problem is about Drivers.
I've found there are two type of drivers:
1. ADB/Bootloader interfaces (usb_drivers we download from Android SDK). This are useful in the first part of the HOWTO since we need to run some ADB commands. This might be also useful during the rooting process
2. MyHTC drivers (both boot and standard). This are the basic HTC drivers for using with several software like HTC Sync AND for flashing phone. This are installed during the HTC Sync installation process.
How to know which driver is using at each time?
Under Control Panel -> System -> Device Manager -> We might find a driver called Android Phone.
1. With the phone in the Start menu into it we might see either:
a) ADB Interface
b) My HTC
2. If we go into the bootloader (rebooting device, volume down + power button) we might see
a) Bootloader
b) My HTC
If we need to FLASH, the we need in both parts My HTC
If we see anything else, we need to update the driver. Just by going into properties of the driver, Controller, Updating Controller -> Find Controller into the PC -> Select from the list of controllers of this PC -> Use Disk and we must look for the HTC Driver that is installed during the HTC Sync Installation process (Normally this is into Program Files-> HTC -> HTC Driver).
Finally we can update the driver by selecting the My HTC one from the list.
This worked perfectly for me, and make me discover this issue that may help some people. I write this as a complement for my guide for flashing to make it wider and more complete: http://forum.xda-developers.com/showthread.php?t=603286
Sorry to bump an old thread, but I'm having this issue with a friends HTC Legend.
MiSSigNNo said:
by going into properties of the driver, Controller, Updating Controller -> Find Controller into the PC -> Select from the list of controllers of this PC -> Use Disk and we must look for the HTC Driver that is installed during the HTC Sync Installation process (Normally this is into Program Files-> HTC -> HTC Driver).
Finally we can update the driver by selecting the My HTC one from the list.
Click to expand...
Click to collapse
What do you mean exactly by going into the properties of the driver? (Win 7 64bit)
Thanks.
MiSSigNNo said:
After I started using my Win 7 system, I had to do the whole process of updating and flashing my device. After like 3 hours going back and fourth to find the solution, I found it is a pretty strange way. In a place where I would never have thought before:
The problem is about Drivers.
I've found there are two type of drivers:
1. ADB/Bootloader interfaces (usb_drivers we download from Android SDK). This are useful in the first part of the HOWTO since we need to run some ADB commands. This might be also useful during the rooting process
2. MyHTC drivers (both boot and standard). This are the basic HTC drivers for using with several software like HTC Sync AND for flashing phone. This are installed during the HTC Sync installation process.
How to know which driver is using at each time?
Under Control Panel -> System -> Device Manager -> We might find a driver called Android Phone.
1. With the phone in the Start menu into it we might see either:
a) ADB Interface
b) My HTC
2. If we go into the bootloader (rebooting device, volume down + power button) we might see
a) Bootloader
b) My HTC
If we need to FLASH, the we need in both parts My HTC
If we see anything else, we need to update the driver. Just by going into properties of the driver, Controller, Updating Controller -> Find Controller into the PC -> Select from the list of controllers of this PC -> Use Disk and we must look for the HTC Driver that is installed during the HTC Sync Installation process (Normally this is into Program Files-> HTC -> HTC Driver).
Finally we can update the driver by selecting the My HTC one from the list.
This worked perfectly for me, and make me discover this issue that may help some people. I write this as a complement for my guide for flashing to make it wider and more complete: http://forum.xda-developers.com/showthread.php?t=603286
Click to expand...
Click to collapse
in english please? I can't understand HOW you are doing this... I am trying to flash a HTC Desire S with Android ICS (latest from htcdev WWE) and it connects fine, but when I get to "Waiting for Bootloader........" it does that for a minute, then says "Error [171] USB Connection Error" The phone shows the HTC logo with black screen. My laptop says "USB Device Not Recognized" too and it fails. What can I do to fix this? I have installed the ADB and SDK also the HTC drivers and HTC Sync, tried everything please help
mattygaga2012 said:
in english please? I can't understand HOW you are doing this... I am trying to flash a HTC Desire S with Android ICS (latest from htcdev WWE) and it connects fine, but when I get to "Waiting for Bootloader........" it does that for a minute, then says "Error [171] USB Connection Error" The phone shows the HTC logo with black screen. My laptop says "USB Device Not Recognized" too and it fails. What can I do to fix this? I have installed the ADB and SDK also the HTC drivers and HTC Sync, tried everything please help
Click to expand...
Click to collapse
I'm not sure if this applies to HTC Desire S... this was meant to be used for HTC Tattoo (HTC Click)
MiSSigNNo said:
I'm not sure if this applies to HTC Desire S... this was meant to be used for HTC Tattoo (HTC Click)
Click to expand...
Click to collapse
Ah I see. Any idea how I could probably fix this? I'm using Windows 8 and I have scoured XDA and the internet for 29 hours straight for answers and turned up empty. I have no MicroSD card to perform the update using the PB99xx.zip method and all other methods are useless. I just want a straight-forward RUU update for my phone but can't seem to do it without that silly Error 170/171 and USB Device Not Recognized errors
Am trying to unlock my n1 so I can get to install cyanogen rom but am stuck after installing Android sdk and Usb drivers, am following some steps but am stuck trying to locate the USB driver, this is part of what was stated in the direction (You can check if your Android USB drivers are installed by going to “Printers & Devices” on Windows 7.* (and I think you can check Device Manager for other versions of Windows). I check the device manager on my pc and still didn't locate it,anybody have an idea like where I can find the USB drivers.
this has been discussed 100 times and is also in the "informative links" sticky.
Please do a search. The driver comes with the SDK.
ive tried everything i can think of.. my computer will not detect my driver for my nexus so i can use adb... can anyone help?
did u already try following step 2 in here?
http://forum.xda-developers.com/showthread.php?t=636795
Are you using the sdk or did you just install the available driver? I played hell getting the driver to fly with the sdk. Downloaded the driver seperately and connected the phone in usb debugging then navigated to the phone in device manager and pointed it at the driver manually.
windows 7 needs TWO separate drivers, not just the one that you can find in the tools folder that comes from modaco. the second driver can be found in the sdk, which you will have to get from the android developers site.
there are a number of threads about this. look for them
Download the sdk from the android developer site, then download the driver through the update function.
Install droid explorer and Android commander .
both will help you or even setup everything for you .
i have no problems with my nexus one on my theree versions of windows 7 (ultimate, enterprise and home premium) and completed the setup within 30 minutes using both mentioned above
Be sure that Debugging is checked under Settings/Applications/Development
Hello
Im brand new to Android and adb/fastboot.
I have looked at tutorials on youtube all day, and for everybody else their devices just pops up when you type adb devices.
I get nothing
I have done it correctly, because I get all the commands when I type adb/fastboot.
Im running windows8, could that be the problem?
Do I need some kind of extra USB drivers for my google glasses?
I do find my glasses as a camera tho.
EDIT:
So after watching a few more tutorials I understood my problem. Its windows8 usb drivers thats not correct.
I have tried to install correct drivers and edit the .ini files that need editing, but now I encountered a new problem.
Windows wont let me install correct usb drivers for google glass.
When I have device manager open, windows have already installed them as “Portable device – Glass1″
I click uninstall and they disaper from my device list, once I click “scan for new hardware” I can see that they reapper on my device list as other devices. Within 2sec windows autoinstall them as “portable device -glass1″ again.
So I try “update driver software” but this dont work either, I select the correct file and path, but I keep getting this message “windows has determined the driver software for your device is up to date”.
Im running windows8.
Any help is appreciated.
EDIT2:
As far as all the tutorial movies tell me to disable driver signing I have done so.
If all of the adb commands were working, then chances are you need to enable debugging on your Glass. Settings >> Device info >> Turn on debug
Update:
The way to bypass windows8 and installing usb drivers, is that I need to use the option "Have Disk" and then install usb drivers that way.
All works fine now.
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.