Related
Im having a big headache here, I have windows vista enterprise edition (the release version) and i downloaded Windows Mobile Device Center from microsoft. My problem is when ever I try to connect the device, windows installs HTC usb sync and after that I get another message saying I need to install drivers for a "unknown device" I went to device manager and sure enough somehow this "unknown device" is related to my phone, It askes to look for drivers and can not find any. Anyway, this is somehow creating a problem because I can not connect the phone with WMDC.
Thanks for your help,
Chris
Similar problems here with Vista Ultimte RTM. You can also watch here for some answers.
Ninja1
A couple weeks ago I tried to sync my Cingular 8525 but had no luck, Vista managed to find and install some HTC drivers, but I couldn't get active sync to work (mobile device center now in vista). But I could browse the files on the device. Then just today I went into device manager and manually told it to look for new drivers online, it did, found some, and installed them, then mobile device center started working and I could sync. Wahoo!
usarmy2008 said:
Im having a big headache here, I have windows vista enterprise edition (the release version) and i downloaded Windows Mobile Device Center from microsoft. My problem is when ever I try to connect the device, windows installs HTC usb sync and after that I get another message saying I need to install drivers for a "unknown device" I went to device manager and sure enough somehow this "unknown device" is related to my phone, It askes to look for drivers and can not find any. Anyway, this is somehow creating a problem because I can not connect the phone with WMDC.
Thanks for your help,
Chris
Click to expand...
Click to collapse
This just happened to me today after using wmdc on vista business for 2 months. now my device comes up as "uknow device" in the device manager and then a few seconds later I get a popup window telling me that my USB device is unknown.
Damn annoying. im trying to figure out what happened and if i cant, then ill reinstall windows vista. bloody M$ crap.
when Vista prompt u for installing the driver, you have to manually select the driver location! Select driver directory to the Windows directory... Then Vista will be able to locate and loaded the device driver... i tried it works...
good luck
ctho24 said:
when Vista prompt u for installing the driver, you have to manually select the driver location! Select driver directory to the Windows directory... Then Vista will be able to locate and loaded the device driver... i tried it works...
good luck
Click to expand...
Click to collapse
it was working fine for 2 months so I assume the correct drivers were installed. nonetheless, i will try update the driver for "unknown device" if I can find the inf file in the windows directory.
i tried it,
it says that my "Unknown Device" in the USB controllers category has the latest drivers installed.
this is too funny.
not sure what went wrong here.
Ive also uninstalled wmdc and reinstalled it many times and still no luck.
hrrrmmmmm, i feel a format and image coming up soon.
OK, i have solved the problem.
who would have thought I had 2 faulty sync-charge cables. They worked on Sunday and stopped working on Monday.
I noticed this happened after I used WM5torage. This is strange.
Anyways, things are back to normal
I have been sync with Windows Vista Ultimate both USB and Bluetooth for weeks. Especially the Bluetooth works great both sync and install software!!
Hello
I have a stock Vodaphone Magic and I'm looking to root it, but to do this I need to get adb to see it, which I'm having problems with.
When I plugged it in first to charge it used window's default drivers for the SD card etc. Trying to update the drivers with the ones included in the SDK dosn't seem to work as Windows says that they're less recent.
Also, I can't see any sort of "ADB" section in the device manager, even with USB debugging turned on in the phone.
Any help? I'd really like to root my phone so I can use WPA Enterprise!
Edit: Already read the wiki page, no help.
I remember having this problem when I first set up the Android SDK.
However in my device manager I did have a device, it wasn't called Android or Magic or anything similar. From what I remember it was a bunch of random letters and numbers.
From there I right clicked it, went to Properties, Update Driver and then pointed it to the directory with the drivers.
Thats how I did it in Windows 7, if that doesn't work for you then I'm not sure sorry.
Hi,
I recently had the same problem as you. The first time you plug in your phone sometimes Windows will assign USB drivers to the device instead of the ADB interface. To correct this, I uninstalled the drivers and pointed the computer to the ADB files as the new drivers. After those install it should be labelled correctly and work.
An odd one....
I have one of the HD2 Android releases on my phone, and it's working fine EXCEPT....
USB tethering does not work.
Now here's the odd part.
1. I have two machines. Both running Win7/x64.
2. One loads the RNDIS driver and works fine. The other can't find the driver on Windows Update.
I have no clue what's going on, but the USB signature is VID_0bb4&PID_0FFe, which is valid for the HTC Sapphire.
And, like I said, the other machine -also running Win7 - finds it just fine.
Any ideas?
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
i'm running Windows 7 x64 and when i start usb tethering from android on HD2 there is Android Device driver missing in Device Manager, I've read that Windows 7 already have Remote NDIS support so no need for seperate driver download if you have Windows Mobile Device Center but it ain't working, the same problem as you had.
Luckely, your solution and this separate driver works, Windows 7 complains about unsigned driver but who cares, USB tethering is working
Thanks!
didn't work...
i attempted installing the driver OEM106.inf, but received an error once it was loaded on my pc:
"This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"
i was having similar problems as Genesis trying to tether my Android phone via USB to my pc and receiving a Remote NDIS driver problem (same as above). I successfully tethered my phone to my PC once (and only once), but after I woke the computer from sleep mode, my pc began giving me errors on the "Remote NDIS based Internet Sharing Device" stating that windows cannot load the drivers ("rndismpx.sys" & "usb8023x.sys"). I haven't been able to tether via USB since then.
Windows Update states the driver is up to date, and when I tried Genesis3's driver fix, it only gave me the same error.
Any ideas?
Running win7/x64 on a toshiba i3, and a HTC nexus 1 running android 2.2.2
The files referenced have somehow been damaged or destroyed. Find them from another machine and put them back, and the OEM file I posted will work.
Those two files have to be on your machine - the OEM file is the pointer to them, but the base-level drivers have to exist.
you may need the latest version of htc sync
i did all my flashing on an xp computer and when i got win7 i just could not get any drivers to work. i downloaded the latest version of htc sync and all the drivers loaded just fine. time to flash this thing again ive had the same rom for two weeks
This is what I was looking for, and it worked for me, thanks!
PISSA! Tried for a while to get usb tethering to work and this did it! Took a minute for windows to sort things out after the driver update but its working! THANK YOU!
DL DesireZ V3.4 final HD2 TMOUS
Hey guys..
This thread popped up first on google and im quite a noob so pls tell me how you include this driver in windows(win7 x64)
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
Worked like a charm, thanks! I just had to update driver with provided file and it started working. Thank you very much again! Bump may not be a bad idea, maybe few more users will solve their problems with this. HD2 isn't a native Android device, so it wasn't that strange that it didn't worked out-of-the-box even with Win7 RDNIS (or sth like that) native support.
raven_raven said:
Worked like a charm, thanks! I just had to update driver with provided file and it started working. Thank you very much again! Bump may not be a bad idea, maybe few more users will solve their problems with this. HD2 isn't a native Android device, so it wasn't that strange that it didn't worked out-of-the-box even with Win7 RDNIS (or sth like that) native support.
Click to expand...
Click to collapse
After I have Device Manager opened, what do I do next?
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
thaaaaaaaaanks.
I have been trying many drivers and tools. This one worked like a charm
I lOVE YOU!
Thanks so much man. you saved me from reverting back to windows mobile, i had about given up on usb teathering with android but you saved me. Im very greatfull.
Not a problem!
still not working
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
I tried this and others ( htc sync, intel android drvrs,) but no success. Any clue what's missing?
i have windows xp, sp3....android 2.3.7 htc wildfire.
oem.inf
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
I would like to share my solution. I modified the oem.inf file in the oem.zip(above) ,by changing the manufacturer name and device id as given in the PC 's device manager(unknown device).
It should work for xp,seven,vista.
So I'm basically on Android Froyo right now, and ant to update my HD2 to 2.3.4 (Gingerbread).
However, I can't connect my phone to the computer because I don't have ADB, or something. I looked through these forums and found this thread to download it:
http://forum.xda-developers.com/showthread.php?t=907676&highlight=ADB
I've got everything done so far (I set up the environmental variable, downloaded the adb.exe, etc.), but when I connect my HD2 to my computer, this pops up:
http://i52.tinypic.com/330gpy0.jpg
And it can't locate this elusive ADB that I just installed. Then, it says that if you have a disc that came with the device, insert it so that Windows can search for the software, but I don't have it, of course.
I've tried the "Browse my computer for software" option, but "Windows could not find driver software for your device."
Anybody have any idea what to do?
Thanks in advance! =)
open google, type in how to install adb driver, hit enter.
once its all installed, remember to open windows mobile device center (without phone connected) click connections, and UNtick 'allow usb connections'
I also have a feeling that the very useful app 'myphoneexplorer' installs the adb driver when installing.
The thing is, I already installed the ADB thingy.
It's just that Windows won't "recognize" it or something, and says that I don't have the driver software. I've also tried the other methods, like USBDeview, but I can't find any HTC drivers.
Like, when I go to cmd and type out "adb devices," my phone serial number won't show up when connected. Also, I downloaded that App, and it only says that the USB cable is pluuged in and that it's "waiting for a connection" (it's already connected to the computer).
Try to install HTC Sync: http://www.htc.com/managed-assets/support/software/htc-sync/setup_3.0.5551.exe
If it still doesn't work then uninstall your phone drivers and install them again.
What version of windows are you running?
Sent from my HTC HD2 using XDA Premium App
Thank you, dawid. It recognizes it now as well as on HTC Sync.
I just figured out that all I needed was to connect it as a "Disk drive."
I really appreciate you guy's help, though. Thanks a lot!
Thank you guys
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
mseebass said:
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
Click to expand...
Click to collapse
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
bigcrav said:
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
Click to expand...
Click to collapse
Thanks for your help. I allready tried an other usb port. It did'nt work.
I wanted to avoid it but I reinstalled windows. Now it works. Thanks again.
Hmm, messed with this problem for ages yesterday, mtp installed fine in normal mode but refused when in 'usb debugging' mode
simple fix, find your wpdmtp.inf file in windows/inf
edit it like shown, look for the [Generic.NTx86] and [Generic.NTamd64] entries near the top of the file........
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
...then update the driver in device manager, use automatic search
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
I did a clean install of windows and that solved the issue for me. Thanksfor your help anyway.
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
meangreenie said:
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
Click to expand...
Click to collapse
Just FYI, just got a Nexus 4 from T-Mobile yesterday and the device ID is slightly different:
VID_18D1&PID_4EE2&MI_01
01 at the end instead of 00
---------- Post added at 09:11 AM ---------- Previous post was at 08:53 AM ----------
Fitchman said:
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
Click to expand...
Click to collapse
How/where do you install those files/drivers? There are no instructions.
lannister80 said:
How/where do you install those files/drivers? There are no instructions.
Click to expand...
Click to collapse
When Windows asks where the drivers are you point to the folder with the ones you want to use...
EddyOS said:
When Windows asks where the drivers are you point to the folder with the ones you want to use...
Click to expand...
Click to collapse
It doesn't ask. I plug in the phone, and Windows says it can't install the MTP driver.
If I go into Device Manager and find the phone (with the yellow triangle and !) and select Update Driver Software, then navigate to the i386 folder from the Universal Naked Driver (on an i5 system), it tells me that "The best driver for your device is already installed" or something similar.
Of course, if I uninstall the device from device manager (and presumably the bad MTP driver as well), it disappears, so I have nothing to point to to install the drivers.
Earlier today I reinstalled the drivers for my N4 on my work PC (Vista Business) and I had to reboot before it recognised the N4 as an MTP Device - prior to that it only saw it as an 'MTP Device'. Now it sees at 'Nexus 4'
I have a similar problem I have a kindle fire
I have install the ADB driver but am having extreme difficulties getting the MTP drivers to work
I have tried everything (every solution on Google)
and nothing works
I've tried the "Media Transfer Protocol Porting Kit"
I tried to get Microsoft help they gave me the run around and confused me even more
here is the conversation
Microsoft: "Thank you for that information
Nathaniel I was checking your product key and it is blocked that is why you can not connect these devices to your computer, you may be a victim of counterfeit software so in this case since it is an OEM computer which means that the manufacture of the computer installed Windows 7 on your computer I recommend you to contact the manufacture of your computer to see if they have an option in order to resolve this issue you are having."
me: when i contact them what do I ask for?
Microsoft: You need to ask for a new product key
me: I am confused what does this mean? that the manufacturer put windows 7 OS on here illegally? but all PC's come with windows OS so every PC in the world is suspect to counterfeiting
them: No, this could be because someone still some information of your computer and use the product key to try to activate Windows until the product key got blocked
No, the name is not involved in this case it is jut the product key
what do I do?
is there an alternative to MTP drivers?
Solved
Hi, i had the same problem described in previous posts and I managed to solve thanks to what is written by meangreenie.
In practice, in the windows\inf of my Windows 7 the file wpdmtp.inf was no longer present but there is only the "compiled" version (wpdmtp.pnf).
I retrieved the file from an earlier version founded in he folder Winsys and so the LG driver are installed without further problems.
Jon McDougal said...
You might be using the wrong driver (Android ADB) instead of the MTP driver. This happened to me the other day!
If you're in Debug Mode, you've already done the first step I was going to suggest.
Here's the second step that worked for me: Open Device Manager -> Click Android Device (top of my list) which exposes "Android Composite ADB Interface" -> Right click that device -> Update Driver Software -> Browse My computer for driver software -> Let me pick from a list of device drivers on my computer -> then choose "MTP USB Device" -> Next
Mine installed the MTP driver and then the N4 opened normally.
Click to expand...
Click to collapse
That works for me with USB Debug ticked and in MTP Mode but not in PTP Mode (on CM10.2-nightly-20130817). I absolutely can't see my pics in no way... (I suppose this is a bug from Google to be fixed in further updates). ADB and FB are correctly working as tested with NexusRootToolkit 1.7.1 Drivers Test.
May it help to delete original DCIM folder and start from a new one??
edit: Shame on me... I forgot that I've formatted my SDcard, so I've no picture in DCIM folder.... Sorry! So I can say that McDougal trick totally worked for me!
try to check the device manager to check the missing drivers with ! mark
Maybe I'm not completely getting the problem, but just doing this worked fine for me:
danielms22 said:
Enable USB debbuging in your phone. Go to Settings -> about phone -> tap about 10 times on build number item until USB debbuging is unlocked.
Also, on your computer go to the device manager, look for your phone, if you find it, right click on it, then update Driver Software, browse computer, Let me pick from a list of device drivers on my computer, USB composite device
That should do it.
Click to expand...
Click to collapse
No need for additional driver download or anything...
Finally a working solution
Finally I found a solution.
Visit answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/mtp-usb-device-drivers-will-not-install-correctly/0ee71b7c-4ae7-403f-abbb-63c7ed9a79f9?rtAction=1387606800207 and search for the "Bret B"'s answer which has also been marked as the most helpful answer. It works perfectly. He simply says..
Go to the Registry Editor (Start –> Run –>type in, “regedit” (without the quotes) then click OK.
Search the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
Go upto Edit>Find, type in or copy/paste Portable Devices
In the right hand pane you will see the (Default) value “Portable Devices” on the string
Once found, you see a string value called UpperFilters –> delete it!
Reconnect the device. Finished!