Database Info

[Problem] ADB driver for vista 32-bit

i am trying to install the driver for my mytouch.
when i plug in my phone for it to install the drivers, all the drivers install normally except for the adb driver.
this is the error message i get:
"C:\Windows\system32\wdfcoinstaller01005.dll is either not designed to run on Windows or it contains an error. try installing the program again using the original installation media or contact your system administrator or the software vendor for support."
i tried searching for this problem and found nothing, anyone out there have the same problem? it must be some issue with vista, ugh

i also get this screen after it fails.

[Q] Installing USB Drivers for ADB in Recovery

It's been bugging me for a while that I can't use ADB while in recovery. It's a matter of getting the drivers installed correctly, I think, I just don't know exactly how to do it. When the phone is booted I can use ADB and MTP just fine. Odin sees my phone in download mode as well. The only problem is in recovery. I'm using TWRP 2.3.3.0, but I've had the problem on previous version of TWRP and CWM. I have the Samsung USB drivers installed, and when the phone is booted Device Manager (in Windows 7) says the drivers being used are from Samsung. However, when in recovery Device Manager shows SAMSUNG_Android_SCH-I535 with the yellow '!' and says no drivers are installed. I can try to choose the drivers to install manually, but if I point to the Samsung USB Drivers folder, Windows can't find the right drivers automatically and there are 25 subfolders with somewhat cryptic names, so I don't know which to choose.
Does anyone know how to get ADB working in recovery?
EDIT: Got it working. I don't know anything about how drivers work, but I dug around a little and it turns out the device shows different Hardware IDs when booted versus when in recovery. The drivers .inf has to contain one of the Hardware IDs given by the device so after finding the driver being used by Windows (by searching for the Class GUID given in the driver details when the phone was booted and searching through all the .infs in the Samsung drivers folder for the matching string) I just added a line with one of the Hardware IDs given in recovery so Windows would install the driver. I tested with adb devices, adb shell and adb pull default.prop and each worked fine.
For anyone interested the driver being used is in 25_escape. In the file ssudadb.inf just add the line
Code:
%CompositeAdbInterface% = ssud.Install, <Hardware ID>
under [Google.NTx86] and [Google.NTamd64], where <Hardware ID> is one of the Hardware IDs given by your phone when in recovery. In Windows, go to the Device Manger > right click your phone > Properties > Details tab > Hardware IDs in the drop down. Mine was
Code:
%CompositeAdbInterface% = ssud.Install, USB\VID_18D1&PID_D001
Then update the driver, browse for drivers, pick the 25_escape folder, and you're good to go. The driver will fail a security check because you've modified it, I ignored it.
I imagine this could cause a problem if some other device uses the same Hardware ID (e.g. if it's some sort of generic or default one that's given in recovery) but I'll cross the bridge if I come to it. There may be some safer way to force driver installation.
EDIT: After doing this you'll get a warning when you plug your phone while it's booted. It will say something to the effect of Hardware ID missing or not being able to identify the device plugged in. This isn't a problem though, ADB and MTP still work fine and the device is identified properly in Device Manager.

Yuphoria drivers won't install in Windows 7 64bit

Cannot install drivers to Windows 7. I want to let you know that Asus Zenfone 5 drivers is installed on this same machine and ADB detectes that device fine. Now after installing QUALCOMM drivers, restarting and stuff connecting Yuphoria still shows as ASUS Android Device (under My Computer>Manage>Device Manager)
Even though it shows ADB Interface Installed the device do not get detected in ADB . Any help?

Follow steps given here to install adb drivers.

Cannot recognise device in fastboot

Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?

Sorted the driver issue... didn't install it properly...

Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)

Win 10 seems to have problems. I downgraded to win 7 all sorted.

I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave

funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.

General Fix Any Driver Issues Easily (EDL,ADB or Fastboot)

Uninstall Every Driver Previously Installed Completely.
Fix adb and fastboot drivers.
plug the phone with usb debugging enabled and click check for updates in windows.
Now you'll see adb driver in windows optional update install it.
.
Fix edl drivers issue.
put the phone in edl mode and do the same thing in windows update.
this time in optional update you'll see Qualcomm drivers install it and enjoy.
also if the drivers isn't showing in windows update you have to reinstall windows.
(this happens because you install so many wrong drivers or some previously and dont able to uninstall them or you messed with some windows settings)

This thing is optional and for only those users who want to use 1.4.3 auto adb installer after installing driver from windows update.
if you want to install adb and fastboot later system wide dont install the drivers while installing it.
press n for that.
and for other press y.
thank you.