When I tried to install it, it failed and now when I try again it says
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
you dont install anything. you extract the android sdk into the c:\. then you copy the two files mention in the thread to c:\windows\system32. you then go to start>run>cmd(enter). type adb devices. ADB is ALL COMMAND LINE. THERE IS NO PROGRAM YOU INSTALL
what two files?
blackfire1 said:
what two files?
Click to expand...
Click to collapse
~sigh~ are you sure you read how to do this at all?
adb.exe and AdbWinApi.dll are the two files that need to go to system32
and then install the drivers from your usb_driver folder from the SDK. Use the AMD one if you're using a 64bit OS or the Intel one for 32bit OS.
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
blackfire1 said:
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
Click to expand...
Click to collapse
System Restore and try it again.
that has nothing to do with adb. that means your driver installer that is resident in windows is corrupted. unless you can system restore to a point at which it was working, the only real fix is going to be a new windows install. not entirely sure how one breaks the library for installing device drivers, but hey, thats what you've got.
Ok the problem was solved when I used my other computer.
I have followed these steps..> http://forum.xda-developers.com/showthread.php?t=532719 <... ok correct me if im wrong i pluged in my phone pops up found new hardware and it give me three options...
1.Locate and install driver software
2.Ask me later
3.Dont show this message again for this device
I did option 1 then it gives me unidentified device installed and when i go into cmd and do the commands it show......
list of devices....
Nothing
when i click safley remove icon(bottom right) it show that my device is a USB mass storage device...I think this might be the problem idk im all confused...
WHAT NOW
Anyone help if can please THANKS...tear drop no adb for now
YES YES F***ing Yes ok sloved finally ok so this is what i did i went into device manager right click on unidentified driver then click update driver software, and then click browse my coputer for software update, then browse to C:\sdk\usb_driver\x86 then next and all done YES excited
jgu71424 said:
1.Locate and install driver software
2.Ask me later
3.Dont show this message again for this device
I did option 1 then it gives me unidentified device installed and when i go into cmd and do the commands it show......
list of devices....
Nothing
Click to expand...
Click to collapse
Did you follow these steps in the guide?
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
Click to expand...
Click to collapse
If you installed it properly, you should have "HTC Dream Composite ADB Interface" in your device manager.
jashsu said:
Did you follow these steps in the guide?
If you installed it properly, you should have "HTC Dream Composite ADB Interface" in your device manager.
Click to expand...
Click to collapse
Yes i did and it gave me a pop up with three options i chose option 1(read top for options) and it gave me what i said on top page...
Oh i have windows vista ultimate 32-bit
I was in the process of rooting my phone, and while in recovery i accidentally wiped everything after i did a back up. Now when i try and reboot the phone it tells me there is no OS to reboot to. I tried downloading a stock rom to adb push into the phone but my computer wont even recognize it from the command prompt. Im kind of stuck now and dont know what to do can anybody please tell me if i have any other options??
Sounds like a driver issue try this
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Latest drivers are here
http://d-h.st/FXC
koshinobi said:
I was in the process of rooting my phone, and while in recovery i accidentally wiped everything after i did a back up. Now when i try and reboot the phone it tells me there is no OS to reboot to. I tried downloading a stock rom to adb push into the phone but my computer wont even recognize it from the command prompt. Im kind of stuck now and dont know what to do can anybody please tell me if i have any other options??
Click to expand...
Click to collapse
Which recovery are you using?
EDIT: Sorry I didn't fully read the title. Did you try sideloading the ROM. Here is a link on how this is done.
http://teamw.in/ADBSideload
bigdaddy619 said:
Sounds like a driver issue try this
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Latest drivers are here
http://d-h.st/FXC
Click to expand...
Click to collapse
i just tried doing that but there was no option for a "adb usb device" i installed all the latest drivers and still nothing
Hi guys,
Sorry for my bad english but i have this problem
When i connect my Moto X to my computer Motorola device manager don't detect my phone and when i check on Device Manager of windows, show me this
I reainstalled Motorola Device Manager but that is still not working, please guys help me...
My only advice is to do yourself a favour and go buy a copy of windows 7.
Life will be much better overall after.
Sent from my Moto X cell phone telephone.....
AxelGom said:
Hi guys,
Sorry for my bad english but i have this problem
When i connect my Moto X to my computer Motorola device manager don't detect my phone and when i check on Device Manager of windows, show me this
I reainstalled Motorola Device Manager but that is still not working, please guys help me...
Click to expand...
Click to collapse
I got mine working with the following steps, but I had it working on Win8 before updating to 8.1 so it may or may not work for you:
Right click the xt1058 option that shows it has a problem
Select update driver software
Select browse my computer
Select "Let me pick from a list of device drivers on my computer"
Select ADB interface and hit next
Select Mot Composite ADB interface and click next
After that I was able to get it to connect with mtp, get fastboot responses, and use the adb commands again properly
It works like a charm!
kasouti said:
I got mine working with the following steps, but I had it working on Win8 before updating to 8.1 so it may or may not work for you:
Right click the xt1058 option that shows it has a problem
Select update driver software
Select browse my computer
Select "Let me pick from a list of device drivers on my computer"
Select ADB interface and hit next
Select Mot Composite ADB interface and click next
After that I was able to get it to connect with mtp, get fastboot responses, and use the adb commands again properly
Click to expand...
Click to collapse
Thanks! solve my problem...
Emerson4br said:
Thanks! solve my problem...
Click to expand...
Click to collapse
kasouti said:
I got mine working with the following steps, but I had it working on Win8 before updating to 8.1 so it may or may not work for you:
Right click the xt1058 option that shows it has a problem
Select update driver software
Select browse my computer
Select "Let me pick from a list of device drivers on my computer"
Select ADB interface and hit next
Select Mot Composite ADB interface and click next
After that I was able to get it to connect with mtp, get fastboot responses, and use the adb commands again properly
Click to expand...
Click to collapse
I have that same problem with mine BQ EDISON 2 QUADCORE... I will try that way too... tell you guys later...
kasouti said:
I got mine working with the following steps, but I had it working on Win8 before updating to 8.1 so it may or may not work for you:
Right click the xt1058 option that shows it has a problem
Select update driver software
Select browse my computer
Select "Let me pick from a list of device drivers on my computer"
Select ADB interface and hit next
Select Mot Composite ADB interface and click next
After that I was able to get it to connect with mtp, get fastboot responses, and use the adb commands again properly
Click to expand...
Click to collapse
TY SO MUCH, WAS LOOKING FOR FIX FOR HOURS. I didnt notice that option at the bottom im so stupid..
How to get MTP and PTP working
I know this is an old thread. But after an hour of research I figured out the real problem.
You simply can't install the MTP or PTP driver properly because you may have Windows 8.1 Pro N
N is a special version used in Europe where there is no media player and software around it installed to give 3rd party media players a chance.
Howerver, to solve the problem and get the phone found you have to install the device drivers AND the Media Feature Pack for N and KN versions of Windows 8.1 .
I'm sorry. I would post the direct link to the microsoft download site. But I have never posted in this forum till now and so I'm not allowed to post outside links yet.
But if you copy & paste the following in google you'll be fine and find it in no time: Media Feature Pack for N and KN versions of Windows 8.1
After you have installed it and rebooted your system the drivers are found and you can see your phone (or camera) in the device manager.
Hope that helps some ppl.
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.