Database Develop

windows 7 usb help

First off sorry I'm sure flammage is coming but I've looked and looked through google and through xda my last ditch effort is to make a post.
I can not get windows 7 to recognize my I've downloaded the latest SDK with usb drivers but each time I try and update drivers I get "windows has determined he driver software for your device is update. Please help me

Go look for the PDANet drivers. You may have to actually install PDANet, but it's painless. Install those drivers, and adb will work for you.
This is mentioned in various stickies and other guides around the board.

This option didn't work please help pda install but didn't overwrite the driver

You need to reboot and hit f8 I believe, then choose the option to allow installation of unsigned drivers. Then try to reinstall the drivers when you boot

Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.

Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot

disgustip8ted said:
Windows 7 does not allow the installation of unsigned drivers unless the option is disabled on boot
Click to expand...
Click to collapse
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.

codesplice said:
Download an application called "USBdeview", which will let you view/modify the drivers for all devices regardless of whether they're attached or not. Find all the drivers related to Android, HTC, NexusOne, and adb, and delete them. Then install pdanet, and don't connect your phone until it instructs you to.
Click to expand...
Click to collapse
Thank you so much for this help all I had to do was download usbdeview the actual program it self told win 7 what to do so now my nexus one works on win 7, thank you!

No problem! Glad I could help

codesplice said:
I'm 95% sure that's only for the 64-bit version of Windows - Vista had the same requirement.
There are ways around it, such as using the Driver Signature Enforcement Overrider application (DSEO), or just manually configuring your computer to run in test/debugging mode.
At any rate, I don't think that you should have any issues with the PDANet drivers, as I installed them on my Win 7 Pro x64 OS before I had disabled driver signing (I did that later to screw with some homemade video drivers).
More detailed instructions on getting the drivers working are available here.
Click to expand...
Click to collapse
well played, i think youre correct.
ill have to grab that util for work...

disgustip8ted said:
well played, i think youre correct.
ill have to grab that util for work...
Click to expand...
Click to collapse
DSEO is a pretty nifty utility for sure. Provides easy one-click (okay, a few clicks, actually) access to disabling the driver signature enforcement - and even an easy way to eliminate the "Test Mode" watermark that would appear in the bottom-right of the desktop while operating in Test Mode.
There are other methods to bypass the signature enforcement without turning on Test Mode, but I've found that to be the best option. Other approaches use a boot-time hook to basically insert the F8 (and other keys as appropriate - down, down, enter or something like that) keystrokes to "automanually" disable driver signature enforcement for that boot. Any third-party application that accesses things that early in the boot process makes me a bit nervous!

problem: Wlan on windows xp pro sp2

hello people,
i've installed windows xp sp2 with a step by step guide on xda (this one http://forum.xda-developers.com/showthread.php?t=436982) without problems.
At the end, when we have to install wlan drivers, i've noticed that marvell sdio sd8686 appear in the hardware list but there is also a yellow ! on this hardware with the error code number 10, windows cannot start hardware.
I've tried with some other drivers that i found on internet but with the same results. Someone can help me?

en_ky said:
hello people,
i've installed windows xp sp2 with a step by step guide on xda (this one http://forum.xda-developers.com/showthread.php?t=436982) without problems.
At the end, when we have to install wlan drivers, i've noticed that marvell sdio sd8686 appear in the hardware list but there is also a yellow ! on this hardware with the error code number 10, windows cannot start hardware.
I've tried with some other drivers that i found on internet but with the same results. Someone can help me?
Click to expand...
Click to collapse
Hi en_ky!
I was following the other installation method "Installing Windows XP with Windows Post Install (WPI)" that you can find on this forum, but basically should be the same.
Anyway, regarding WLAN on the WPI method it says:
"13. WLAN: Drivers are copied to c:\wlandrivers, install from there when you are asked for them later". This step is just before installing CYGWIN
After finishing with SwapResolution,
"Now it usually asks about the WLAN drivers, see step nr. 13."
"If it asks about drivers for Windows Mobile, just answer yes until it finishes."
"To get Wifi working, you have to copy the "copy HTC Shift XP Drivers\WLAN\sdbus.sys to c:\windows\system32\drivers\ say yes to the replace dialog and reboot."
"DO THIS IN SAFE MODE ONLY. This is how I got mine to work. I had the same problem with the yellow and not working wifi code 10 in the device manager."
"If you copy this without being in safe mode, it will not work because after the reboot the system will replace the overridden version with the old one again."
So check again all the steps and do the last one in Safe Mode (I think here is your problem)!
Good luck!

thank you for your reply,
I tried to resolve my problem with help of windows update and an eterneth connection for internet. At first it doesn't start with the same yellow ! But after a restart, it starts!!!!
Many thanks to you in any case; i know that your answer will be usefull for another person with this problem!

[Solved] ADB Driver doesn't want to install/work on Windows XP.

Yesterday i had a problem with a Win XP computer where the ADB driver just didn't want to install. The worst part was that on that particular PC it worked correctly some time ago.
After a lot of digging around I've found out that the problem was that somehow the "WDF01005" (which is actually "Microsoft Kernel-Mode Driver Framework Feature Pack 1.5", on some sites it was listed as "KMDF Coinstaller 1.5") was not installed. Of course, searching the net for it didn't get me any closer to a solution.
Anyways, to make a long story short, i managed to fix it by creating the uninstall registry entry for it, it seems that i did have it installed (or maybe i had a newer version installed) all along just that the reg-entry got deleted.
Here's the reg file :
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Wdf01005]
"SystemComponent"=dword:00000001
(just save it into "fix_wdf01005.reg" and double click it to install it with Regedit, or you can add the key manually and add a DWORD value with the name "SystemComponent" and value of 1.)
So, if you ever get the error that Windows XP cannot install the "Android Platform Sooner Single ADB Interface" driver then you might want to see if you have the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Wdf01005" key as it is used by the driver installation and if it's missing then it fails and the driver is not installed.
I hope it helps others too,
P.S. i just tested, it worked for my Samsung phone too, it also failed to install the Android ADB driver and thus the ADB command said "error : device not found", now it worked correctly, it even found the drivers it needed through Windows Update so i didn't have to install anything manually.

Thank you so much! This worked like a charm!
My Windows XP used to work with adb, now it fails to install it.
Then I read this thread and now adb is working happily on my Samsung Galaxy Gio!
Thanks!

Thanks man.
you really helps me a lot.
[sorry for bad english]

instructions for domies...
Can you tell me exactly how do that, please? I'm having the same issue. The file doesn't exist in my registry. How do I get it?

Thanks. You're a blessing.

hi i have not problem with installation in my windowx xp...but its takes too long...i think some time 10 to 20 mins..so is there any way to install adb driver installation fast...plz suggest me solution...thnks and advance

adb devices

Hello
Im brand new to Android and adb/fastboot.
I have looked at tutorials on youtube all day, and for everybody else their devices just pops up when you type adb devices.
I get nothing
I have done it correctly, because I get all the commands when I type adb/fastboot.
Im running windows8, could that be the problem?
Do I need some kind of extra USB drivers for my google glasses?
I do find my glasses as a camera tho.
EDIT:
So after watching a few more tutorials I understood my problem. Its windows8 usb drivers thats not correct.
I have tried to install correct drivers and edit the .ini files that need editing, but now I encountered a new problem.
Windows wont let me install correct usb drivers for google glass.
When I have device manager open, windows have already installed them as “Portable device – Glass1″
I click uninstall and they disaper from my device list, once I click “scan for new hardware” I can see that they reapper on my device list as other devices. Within 2sec windows autoinstall them as “portable device -glass1″ again.
So I try “update driver software” but this dont work either, I select the correct file and path, but I keep getting this message “windows has determined the driver software for your device is up to date”.
Im running windows8.
Any help is appreciated.
EDIT2:
As far as all the tutorial movies tell me to disable driver signing I have done so.

If all of the adb commands were working, then chances are you need to enable debugging on your Glass. Settings >> Device info >> Turn on debug

Update:
The way to bypass windows8 and installing usb drivers, is that I need to use the option "Have Disk" and then install usb drivers that way.
All works fine now.

Cannot Get Drivers Installed for Windows 8.1 - Manual Installation or SDK

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.