Related
"USB Device Not Recognized"
I have searched for so long trying to figure out what's wrong. I'm out of idea's on how to fix it, nothing will recognize my Evo.
Tried on 4 different computers, two of them running 7, one running xp, and last running vista, all say the same thing, computers not the problem.
Downloaded htc sync, disabled/enabled usb debugging, restarted the phone many times, restarted computers, and even changed the default usb connection to HDD and HTC sync.
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
b1indsided said:
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just tried that and still not recognizing it.
Which HTC Sync did you try? I think the latest is 2.0.40
http://www.htc.com/us/support/evo-sprint/downloads/
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
http://kenshinjeff.18jan.us/2009/06/12/adb-error-device-not-found-android-phone/
or here
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
stratman71 said:
Which HTC Sync did you try? I think the latest is 2.0.40
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
Click to expand...
Click to collapse
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
guesswhatimevan said:
"USB Device Not Recognized"
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Click to expand...
Click to collapse
Did you do the 3 click method?
guesswhatimevan said:
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
Click to expand...
Click to collapse
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Philosuffer said:
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Click to expand...
Click to collapse
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Sorry but bump, i relly need help with this.
It still says unknown device when i try to connect my phone in recovery mode.
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Mast3rpyr0 said:
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Click to expand...
Click to collapse
Just tried that and it's a no go, still the same problem, Also tried another cable today and that didn't help either.
I have light leakeage at the bottom of my phone, so i think i'm going to take it in for that and just get a replacement.
guesswhatimevan said:
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Click to expand...
Click to collapse
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Philosuffer said:
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Click to expand...
Click to collapse
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
guesswhatimevan said:
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
Click to expand...
Click to collapse
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Philosuffer said:
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Click to expand...
Click to collapse
It shows up in usb controllers instead of other devices as he shows in the guide. If i try to update the driver it just tells me it's already up to date.
>Sorry yea it does say unknown device in device manager.
Gotta bump, would really love to just fix this instead of driving 30 mins to a sprint store.
So i followed the guide for installing apb drivers, but even in recovery mode my phone still shows up as unknown device in device manager.
Ok, well I just ran into this myself on my secondary computer. Have you tried a different USB port on your PC?
My front ones were giving me unknown device, but as soon as I plugged it into one of the ports on the back of the mobo ADB showed right up in device manager.
Factory reset it and get it exchanged.I belief is the SD card failure issue.
Sent from my PC36100 using XDA App
I have the same problem and posted this question on 3 forums including the HTC support forum and nobody has been able to find the correct solution.
I know the cable and the port is good because I can connect my Samsung Moment to it and it works perfectly. On the Evo, I've downloaded the latest HTC Sync from the official HTC site, tried the one on the microsd card, checked and un-checked USB debugging, and still it doesn't connect.
The Evo won't connect to my Win 7 computer at home, Win XP at work, but it will connect to my daughters computer which is running Win XP also (all 32 bit).
I bought this Evo from Best Buy exactly 28 days ago today. Do they give you 30 days to return it, or is that only the Sprint store?
They do give u 30 day trial.go get it exchanged or...........
Sent from my PC36100 using XDA App
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
maatsby said:
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
Click to expand...
Click to collapse
I bought the phone and it came with 1 cord (with HTC label) that can be connected to the charger, I guess there are only 1 cord for charging and connect to PC? This is the cord that I use. In addition to that I have also tried Motorola, Sony Ericsson (both also for Android phone) and Nokia cord but all can't.
The ROM is actually older version stock ROM from RUU.exe. I saw from few Desire thread they were using this method to restore the ROM to before the USB Brick condition so I thought to try it.
BUMP!
Anyone know what should I do to resolve this problem?
Are you running the very latest HTC Sync on your PC? I'm using 3.0.5606. You can get it here: http://www.htc.com/www/help/
Also, connect your phone and go into Device Manager on your PC. Check to see if you have an entry for Android USB Devices and that the phone shows up. See attached screenshot for how mine looks. This is the best place to check to see if your PC has installed the drivers correctly.
In answer to your question about the cable, yes it's the same cable that attaches to the PC or to the mains charger. I've sometimes had connection problems caused by a dodgy cable, but I've used others apart from the HTC one without issues.
Edit: Also, when you install HTC Sync it should warn you to disable Antivirus software during the installation. This can be really important! I ignored it the first time around, thinking it was just a silly precaution, and had loads of problems with the phone not being recognised. Had to uninstall, temporarily disable AV, and re-install HTC Sync. Once it has finished installing, you can turn your AV back on.
Thank you for your reply preacher6.
Yes, I'm using the latest HTC Sync, v3.0.5606, just downloaded yesterday and reinstall everything.
When my phone connected to the PC it didn't appear as Android USB Device on my Device Manager, it only appear as Unknown Device in USB Controller:
So I guess I can rule out the cable as I have tried about 4 cables already.
For the installation part, I have disable the anti virus and also running the setup program as administrator. When installing there is no problem whatsoever that crop out.
Another point is, even on Fastboot it appear as Unknown Device in the PC.
I would try to update the driver manually - right click on the Unknown device, go to "install driver" or "update driver", then browse to the "Program Files\HTC\HTC Driver" folder. See if it picks up and installs the correct driver.
I've tried manually update the driver as per your advise but it says there is no compatible driver in that folder even though androidusb.inf is in that folder.
I'm running Win 7 64bit. does the driver also work for 64bit OS?
Should do, yes, I'm on Win7 64 bit myself. There is this folder on my PC:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
Is the unknown device present when the phone isn't connected? Just to make sure that is actually the phone - if it's still there when the phone isn't connected, it's some other device.
Otherwise try uninstalling the unknown device and then rebooting the PC, then forcing the installation of the drivers again.
The folder is same as yours.
The unknown device does not present when my DHD is not connected, so I'm certain it is the phone that appear as unknown device.
I have tried uninstalling the unknown device > reboot PC > installing the driver but it still won't install.
Another thing is, I check on the Device Manager > Unknown Device properties > Details" for it's Hardware Ids and it shows as USB\UNKNOWN. I think it should show a strings of the device id? Correct me if I'm wrong.
Yep, there should be a proper device ID string, on charge mode mine shows a hardware ID of USB\VID_0BB4&PID_0CA2&REV_0226&MI_01.
At this point the best thing I can suggest is to try on another PC. If it works, your drivers are screwed up and you'll need to strip them and reinstall. But if it doesn't work on another PC, it's possible you have a hardware problem with the phone.
xb360 said:
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
Click to expand...
Click to collapse
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
dmastman83 said:
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
Click to expand...
Click to collapse
Yes. Holla if you still need help
marknoll said:
Yes. Holla if you still need help
Click to expand...
Click to collapse
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
FossaFX said:
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
Click to expand...
Click to collapse
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
marknoll said:
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
Click to expand...
Click to collapse
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Install the SDK on PC and update all android versions.
Well guys it was just my PC, i made a system backup for four days and that was all the problem(the USB port of my PC)
FossaFX said:
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Click to expand...
Click to collapse
After installing and updating SDK...go into platform folder and open it. Hold mouse in field and hold shift and right click mouse. Chose "open cmd here"..that will open a cmd prompt window. In regular mode on phone,type "adb devices" should return numbers (ex: hta3829g)..if in bootloader mode,type "fastboot devices" should return numbers.
This SDK helps PC see your phone when its plugged in. Especially handy when a PC won't install drivers for your phone
Sent from my ATRIX HD
Are you also stating that your device will no longer charge when plugged in?
Sent from my ATRIX HD
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Allane176 said:
Hey guys,
I've been wary to flash the ROM of my Nexus 7, as it actually boots into the normal OS and does everything fine.
The basic problem is that I can't transfer anything to and from the device over USB. USB debugging is on and I have tried PTP and MTP.
One of the solutions I have been looking at is bad drivers on Windows' part, and that is where I am currently blocked. If USB debugging is off, Windows refuses to acknowledge my tablet's existence. If debugging is on, some drivers from Microsoft automatically install and the tablet is labeled as "unknown device".
My USB controller is up to date with the correct drivers provided by ASUS for my motherboard (ASUS Z87-A). I recently re-installed Windows 7 to put it on a larger SSD, and with this same motherboard, it now does not detect correctly.
If I try to uninstall the "unkown device" it simply disappears until I unplug and replug in the tablet. If I try to manually direct it to the correct drivers, it tells me that the USB drivers are incompatible with my device. The USB drivers are the ones downloaded directly from Google.
I can still access the fastloader.
If you need more information, just let me know.
Click to expand...
Click to collapse
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Aerowinder said:
When you first got the device, did you go straight into fastboot without booting it and plugging it in while in Android? Does that question even make sense?
Click to expand...
Click to collapse
That would have been roughly a year ago. I believe I did boot straight into the OS.
mdamaged said:
Use this as a possible quick-fix (not all mode combinations will work right): http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, then reboot.
Use this as a more complete fix (recommended in your case): http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Click to expand...
Click to collapse
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Allane176 said:
That would have been roughly a year ago. I believe I did boot straight into the OS.
To the first quick-fix, the ADB drivers are installed, but they are not the drivers that are utilized when the Nexus 7 is plugged in. Like I said, it instantly installs some generic Microsoft drivers, and refuses to recognize the ABD drivers are compatible for the device.
As such I can't even begin with option 2.
Click to expand...
Click to collapse
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
mdamaged said:
With the device plugged in, go into device manager and find the device, uninstall that device, and make sure you check the box to uninstall the drivers from the system, then leaving the N7 plugged in to the PC, reboot the N7, as it comes up it should redetect, it's important to leave the device plugged in while it is rebooting.
Click to expand...
Click to collapse
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Allane176 said:
There is no check box to uninstall the drivers: imgur.com/PhL4UNt
Where "unknown device" is my N7. Still, I tried rebooting it while leaving it plugged in, and it would not recognize correctly.
Click to expand...
Click to collapse
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download these, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
mdamaged said:
You may want to make sure you are not using a hub or USB 3.0 port for this btw.
Put the device into in MTP mode with debugging on, unplug the device, then download, unzip them somewhere, right click on the unknown device associated with your Nexux 7, click Update driver software, click "Browse my computer", navigate to where you saved the unzipped contents, and select usb_driver folder, let it do its thing, reboot your PC. Plug the device back in, preferably into a different USB port then what you have been using, it should then show up as a Google ADB driver (or similar), you can test it with the command: adb devices see if that works, if not, leave the device plugged in, and reboot the device.
Let me know if that works or not, and I will continue in a new post.
Click to expand...
Click to collapse
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Allane176 said:
Ok, plugged directly into a USB 2.0 port at the back of my motherboard. Recognized as Unknown Device when plugged in, disappears completely when unplugged.
So, here's exactly what I did: Plugged in device -> clicked on "Update Driver software" -> unplugged device -> Browse my computer for driver software -> directed to correct location -> replies: "The best driver software for your device is already installed", and it is not using the ADB drivers.
Going into "Driver Details" tells me that there are no drivers that have been installed.
Click to expand...
Click to collapse
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install Wugs NRT, as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: http://www.nirsoft.net/utils/usb_devices_view.html, but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
mdamaged said:
Don't unplug the device, do like this, put it in MTP/debug on, leave it plugged in, "Update Driver software" -> Browse my computer for driver software -> direct to correct location.
I know my method works, I've done it to that laptop, my htpc, and my gaming rig flawlessly.
You may have to use a tool to remove all instances of those drivers and reboot, Wugs toolkit has the app, let me see if I can find the direct download for the app or you can just download and install Wugs Toolkit.
Here is the app, but I'd still recommend you install ], as the kit has a walk-through telling you which device IDs to look for to remove. Here is the actual tool wugs uses: , but again, unless you know which ones to remove, you're better off using Wugs tool kit device drivers walkthrough built into NRT.
Click to expand...
Click to collapse
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Allane176 said:
Well, NRT is precisely where I started this whole thing.
Here is a picture detailing where the Nexus 7 is connected, and for reference, ALL the USB ports on my case, be it at the front or from the motherboard, are controlled by a hub: imgur.com/pP5ZbMv
Every other device's location is described as "Location 0" except for the Nexus 7 when it's connected.
Unfortunately at this point I'm probably just going to use Dropbox to transfer files when I need to.
Click to expand...
Click to collapse
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
mdamaged said:
I guess something is trashed in your system, maybe using a previous motherboard driver would work, dunno, sorry it didn't work out.
Click to expand...
Click to collapse
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Allane176 said:
Well thank you very much anyway. I'm sorry I couldn't have been more clear initially.
Click to expand...
Click to collapse
No problem, maybe you'll work on it again and you'll figure it out. Also, you can use airdroid for transfer of files, I hear it works really well.
Got a weird one - got the M9, able to connect it at work and on a laptop but not the computer I've got ADB and everything on.
Phone simply does not recognize as a USB drive, I get that it's looking for "Android phone" but it never shows as a device. (MTP, ADB, etc) Suggesting where the HTC drivers I just downloaded results in me getting that they're not what it's looking for.
This is a computer that has worked for my EVO 4G, 3D, 4G LTE, One m7, m8 along with being fine with a host of other devices.
I've uninstalled and reinstalled everything I know to do but no ADB, no MTP. Not a recognizable device to windows other than being "Android Phone" with no drivers findable.
Some things I've done:
Installed HTC Sync
Deleted HTC Sync
installed HTC drivers pack
removed
Bang head on keyboard
Plug into different USB ports
Change cable
Just one computer, the one that I've used with no problem for ages, wants to be a punk
Have you tried enabling USB debugging?
-settings
-about
-software information
-more
-tap build number 7 times
Then go back to settings and enter developer options and check USB debugging
NotSatan said:
Have you tried enabling USB debugging?
-settings
-about
-software information
-more
-tap build number 7 times
Then go back to settings and enter developer options and check USB debugging
Click to expand...
Click to collapse
Yup. I just get "Android Phone" as an unrecognized device. I've also set to Disk Drive, MTP, debugging on and off.
Just plugged in the M8, same issue... so it's something that's not M9 specific...
Well that's as far as my expertise goes haha.
mildlydisturbed said:
Got a weird one - got the M9, able to connect it at work and on a laptop but not the computer I've got ADB and everything on.
Phone simply does not recognize as a USB drive, I get that it's looking for "Android phone" but it never shows as a device. (MTP, ADB, etc) Suggesting where the HTC drivers I just downloaded results in me getting that they're not what it's looking for.
This is a computer that has worked for my EVO 4G, 3D, 4G LTE, One m7, m8 along with being fine with a host of other devices.
I've uninstalled and reinstalled everything I know to do but no ADB, no MTP. Not a recognizable device to windows other than being "Android Phone" with no drivers findable.
Some things I've done:
Installed HTC Sync
Deleted HTC Sync
installed HTC drivers pack
removed
Bang head on keyboard
Plug into different USB ports
Change cable
Just one computer, the one that I've used with no problem for ages, wants to be a punk
Click to expand...
Click to collapse
Was this resolved? Having this same issue...
It looks like you are just trying to get ADB?
* Make sure USB debugging is enabled (I know you said it is).
* Make sure your computer is not blacklisted on your phone from making connections to ADB.
* Make sure any htc sync or driver package is totally removed.
* Make sure your keyboard still works enough after the head banging. You will only need a mouse, enter, space, a, b, c, d, e, i, s and v to complete the following; but more is always better just in case you need an h or something.
Look in Device Manager. Is it an unknown device (is there a yellow exclamation mark or something next to it)?
Try deleting the driver that it's using - like actually choose to delete the driver software from your machine, not just remove the device.
Once you're totally clean and the phone shows up with a yellow !, try update driver -> let me choose -> have disk -> your android sdk's extras/google-usb-driver .inf.
Pick one of the ADB ones, not sure if it'll be composite or the other one, then test with
Code:
adb devices
in your cmd window.
If it shows up, cool. If not try the other ADB usb driver from the inf...
xfinrodx said:
It looks like you are just trying to get ADB?
* Make sure USB debugging is enabled (I know you said it is).
* Make sure your computer is not blacklisted on your phone from making connections to ADB.
* Make sure any htc sync or driver package is totally removed.
* Make sure your keyboard still works enough after the head banging. You will only need a mouse, enter, space, a, b, c, d, e, i, s and v to complete the following; but more is always better just in case you need an h or something.
Look in Device Manager. Is it an unknown device (is there a yellow exclamation mark or something next to it)?
Try deleting the driver that it's using - like actually choose to delete the driver software from your machine, not just remove the device.
Once you're totally clean and the phone shows up with a yellow !, try update driver -> let me choose -> have disk -> your android sdk's extras/google-usb-driver .inf.
Pick one of the ADB ones, not sure if it'll be composite or the other one, then test with
Code:
adb devices
in your cmd window.
If it shows up, cool. If not try the other ADB usb driver from the inf...
Click to expand...
Click to collapse
Thanks. I tried this and nothing helped. Finding the device from ADB devices isn't the issue. It is that the SD card does not show up in Windows Explorer. Other than taking the SD card out and using a micro SD card adapter for my PC, I cannot transfer files via USB. See attached image. The MTP is the issue. Why doesn't HTC Sync/Drivers from HTC.com fix this? -_-;
Oh, I'm sorry I misunderstood your need. Well if adb works yes can always push/pull... Which version of Windows are you on? Is it possibly a 32/64 bit driver issue? I'm reaching here, HTC sync should cure whatever ails you... I hate MTP.
xfinrodx said:
Oh, I'm sorry I misunderstood your need. Well if adb works yes can always push/pull... Which version of Windows are you on? Is it possibly a 32/64 bit driver issue? I'm reaching here, HTC sync should cure whatever ails you... I hate MTP.
Click to expand...
Click to collapse
Windows 7, yea it's probably a64 bit problem.
typhoonikan said:
Was this resolved? Having this same issue...
Click to expand...
Click to collapse
Resolved after I updated to windows 10
mildlydisturbed said:
Resolved after I updated to windows 10
Click to expand...
Click to collapse
Not for me. Would love a solution.
Bump. Help? So annoying.
typhoonikan said:
Bump. Help? So annoying.
Click to expand...
Click to collapse
I' having the same issue. M9 not recognized as an MTP device on Win 10 64 bit. Running CM 12.1. Adb works, and the device shows up in Device Manager as "MTP USB Device" under "Portable Devices" section. Right clicking gives only propertied and scan for h/w change option, there is no option to update device driver. Phone shows up as HTC M9 under "Unspecified" category in "Devices and Printers".
My Lg G2 runs CM12.1 as well and works fine as mtp device. (Adb works too). I have been trying everything to get M9 working, but failed.
EDIT
Solved the issue trying random things! The issue was the xposed module "Xposed Media Scanner Optimizer" which was preventing MTP mode by not allowing media scanner to run.
droidphile said:
I' having the same issue. M9 not recognized as an MTP device on Win 10 64 bit. Running CM 12.1. Adb works, and the device shows up in Device Manager as "MTP USB Device" under "Portable Devices" section. Right clicking gives only propertied and scan for h/w change option, there is no option to update device driver. Phone shows up as HTC M9 under "Unspecified" category in "Devices and Printers".
My Lg G2 runs CM12.1 as well and works fine as mtp device. (Adb works too). I have been trying everything to get M9 working, but failed.
EDIT
Solved the issue trying random things! The issue was the xposed module "Xposed Media Scanner Optimizer" which was preventing MTP mode by not allowing media scanner to run.
Click to expand...
Click to collapse
I do not have that module installed, so that can't be what is keeping Windows from noticing my phone as a storage device.
Also, if i hadn't mentioned it before, I am able to see my device with adb devices in the command prompt.
typhoonikan said:
I do not have that module installed, so that can't be what is keeping Windows from noticing my phone as a storage device.
Also, if i hadn't mentioned it before, I am able to see my device with adb devices in the command prompt.
Click to expand...
Click to collapse
Most likely it is a driver conflict or missing drivers. Uninstall all portable device drivers and start again.
I wish I stole my HTC M9.
typhoonikan said:
I do not have that module installed, so that can't be what is keeping Windows from noticing my phone as a storage device.
Also, if i hadn't mentioned it before, I am able to see my device with adb devices in the command prompt.
Click to expand...
Click to collapse
I have the same issue, nothing! MTP device driver is not present...adb works but MTP nothing.
Please, someone check if the win 10 installed is N version? maybe is this the problem, maybe....
Thanks
Something to try. Connect your phone to the PC, then go into device manager and look for portable devices. The phone should be listed there and most likely you will see a yellow triangle on it. Click on it and choose to uninstall. After it uninstalls, unplug the phone from the PC and then plug it back in. Allow it to fully re-install before doing anything.
DeeZZ_NuuZZ said:
install another theme from themes Manager which is dark, or has dark Keyboard. the easiest way
Click to expand...
Click to collapse
Nope. I've played with device manager for over an hour at a time. Windows doesn't like m9.
Well, my understanding is that the driver used for mtp for Android devices is the same driver that is used for Windows Media Player. When you connect your phone to the PC and open Windows Media Player, is the phone listed there? If not, then you may have something interfering with media scanner. Have you tried starting the M9 in safe mode and then connecting to the PC?
Weird. You must bring it to store to fix
After upgrading to Android Q suddenly my pc can't recognize my pixel as a android device also i can't connect any wired things such as dongle jack or USB Transfer (USB charging options disappeared).
Planning to downgrade to Pie but the problem is my device can't be detected on my pc. Any solutions? Thanks
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
simplepinoi177 said:
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
Click to expand...
Click to collapse
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
blancheSX said:
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
Click to expand...
Click to collapse
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
I have this issue before, and after all i got my phone detected. But when i flash it, it say unbootable slot in fastboot screen. After couple onf time, it cant be flashed again and die.... My phone cant turn on in fastboot mode again, it bricked
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
If anyone is still having the issue of PC not recognizing device in fastboot, please be sure you have UNinstalled the older version(s) of SDK Tools from yhour PC and make sure to INSTALL the latest versions.
You can find the latest version linked in the 9x guide in my signature.
Also, make sure you have both older and newer USB cables handy. The Pixel has a nasty reputation for being finicky with USB cables, try diff cables and different USB ports on your PC.
There is also a basic troubleshooting guide in the same link in my sig.
Best regards!
simplepinoi177 said:
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
Click to expand...
Click to collapse
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
dallas90733 said:
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
Click to expand...
Click to collapse
i tried those tuturial and ended in error code : 10, device cannot started.
SageWilliams said:
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
Click to expand...
Click to collapse
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
blancheSX said:
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
Click to expand...
Click to collapse
blancheSX said:
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
Click to expand...
Click to collapse
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Only THEN, once these two things are extracted and installed (as is the case in the first step) and you revoked the authorizations, can you plug in your device and USB cord. Watch your phone/device, as it will ask for authorization to connect to your computer, and you’ll have to make sure the box is checked that says “don’t ask this every time” or “remember this device” – I can’t recall off-hand – and then make sure to “Allow” it. By doing this, you can be sure that your computer and device are talking correctly.
*One suggestion that isn’t mandatory is that you select where it says “USB charging” and change it to “MTP” or “file-sharing” (sorry, again, I can’t recall specifically off the top of my head…)
If all things are working well, if you can open up a command prompt (a.k.a. “cmd”, and also make sure you are running it “As an administrator”) and direct it to the platform-tools directory (hopefully you followed my suggestion and kept it simple so it will either be at the root “C:\” or on your Desktop “C:\Users\[username]\Desktop” so it won't be too difficult directing it there...), and run the commands
Code:
adb devices
and
Code:
fastboot --version
.
Hopefully, if you do all of these things, it might get things reset and working from a stable established set up.
If it somewhat works, but the device in your "Device Manager" is showing up something "funky", then it'll take a rather nuanced Windows troubleshooting technique to resolve where I would have you correct the wrong entry/driver in the "Device Manager" and have it specifically point to one of the contents of the .zip files; shown prior.... We'll tackle that if need be and if all this initial beginning troubleshooting doesn't pan out...
Let me/us know how it works out, good luck, and hope this all ends up being helpful…
simplepinoi177 said:
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Click to expand...
Click to collapse
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
blancheSX said:
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
Click to expand...
Click to collapse
Yeah...I figured as much...I was just making sure to lay down the "ground work" before proceeding...
If you're still willing....what I had planned next was to walk you through manually updating/"editing" the driver (on the PC) to directly look at the Google usb drivers specifically to try and get around the whole "device descriptor" and other (detection) error codes.......
Might want to try uninstall the SDK toolkit, reboot PC, then install the latest SDK toolskit.
Also having both USB 2.0 and 3.0 cables saved me more than once, and is a known thing on the 2XL.