Connected to usb, seems all drivers installed properly, but not ADB interface.
Device Manager shows: Adb interface: unknown device.
Device status: This device is not configured correctly. (Code 1) To reinstall the drivers for this device, click Reinstall Driver.
Trying reinstall using C:\Program Files\LG Electronics\LG United Mobile Driver or C:\Program Files\Android\android-sdk\extras\google\usb_driver
always get:
Cannot Install this Hardware
There was a problem installing this hardware:
Android Platform Sooner Single ADB Interface
An error occurred during the installation of the device
Fatal error during installation
Using WinXp
Any help will be highly appreciated.
Arrrggghhhhhhh.......
After 4 hrs of trying ADB is working!
After tons of google search, driver reinstall and restarts found
program PdaNet junefabrics.com/android/download.php
It has drivers and after driver install removed pdanet.
Then connected, phone stopped installing drivers on lge android platform usb modem, so i turned off android debugging driver and install continued and then get balloon message that drivers ready to use turned on usb debugging again get:
Found new hardware wizard.
Drivers was installed automatically, no need of selecting location, and ADB is working!!!
Thanks to PDANET !!!
Related
I was trying to install PDANet yesterday onto my laptop, I follow all the isntructions during installation and allow the drivers to be installed. I choose Samsung as my phone. At one point it asks me to connect my phone to my PC, which I do. It proceeds to dl 4 things, 3 out of the 4 download and install fine, but the ADB Driver installation fails every time (this is windows downloading drivers, not the installation itself). I have tried finding ADB drivers on my own with little success.
to confirm before the question is asked, yes the USB debugging option is turned on. ADB driver just keeps failing to download and install using windows.
same issue with my HP laptop
Driver name is S3c6410 Android ADB
Hello,
This must be a dumb question because all the guides seem to skip over this part but I'm having trouble installing the Windows 7 drivers. I downloaded the drivers, connected via USB, right clicked on the Android 1.0 in the device manager and updated the drivers. Everything seemed fine. Then I boot into fastboot and get a "Drivers were not installed successfully" pop-up.
I thought maybe I messed up and was supposed to install the drivers while in fastboot rather than while the phone was all the way booted up. So I rebooted the phone, uninstalled the drivers, booted in fastboot and tried to install the drivers while in fastboot. When I try it this way I right click on Android 1.0 in the device manager, go to the update driver option, select my file (there are two files in the driver folder I downloaded, androidusb and htcrndis, I tried them both) and I get an error before it can finish installing the driver. It says:
Windows found driver software for your device but encountered an error when trying to install it:
HTC Remote NDIS based Device
This device cannot start. (Code 10)
I'm sure it's something simple but I cant figure it out. Thanks for any help.
I was installing my Titan2 device on my Windows7 x64 desktop when downlaoding a podcast. It is a AMD system.
When I plugged in the Titan2, the installer started by now I keep gettings an error (!) givign a code 10 driver installation error.
Driver Error for Windows Phone 7 driver (under portable devices in device manager)
"This device cannot start. (Code 10)"
Every time I plug in my titan2 cable onto the PC, the driver attempts to install but always returns with this error. So basically Zune doesn't see my PC. The error (according to MS) seems to be a driver version issue. I can uninstall the device through the USB (connected devices) Eject Windows 7. It seems it doesn't recognize this is a Titan2. Any suggestions
ms driver
For Windows driver issues no matter which version of Windows or type of connected device, I would normally suggest uninstalling the driver through device manager if you have the original driver or can download it through Windows update, rebooting to be sure all the driver hooks are removed, then plugging your device back in and letting the driver be downloaded and installed fresh.
Good Luck!
mf2112
I recently acquired an SGP312 from ebay and the seller upgraded it to 5.0.2 without anyone asking for it (it was supposed to be NIB now who knows).
I have not unlocked the bootloader but I did confirm it is locked and can be unlocked.
I'm trying to connect it to my PC so I can get it rooted but I'm running into issues with the device being recognized.
I installed the Android SDK USB drivers & copied over android_winusb.inf and fastboot appears to be working fine. Windowns (7) Device Manager, Flashtool, and the Sony flash tool (Emma) all see the tab.
However, none of the other connection modes appear to work.
Flash mode will initially connect with Flashtool but the the device disconnects:
31/037/2015 23:37:03 - INFO - Device connected in flash mode
31/038/2015 23:38:04 - INFO - Device disconnected
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Device Manager shows an Other Devices with SGP312. I tried doing the Update Driver Software option with the drivers from the Sony developer site or the Android SDK drivers but no go.
I then boot up normally and connect either with or without ADB turned on and get the same Device Manager and driver results and PC Companion won't see the phone, either.
kadiir said:
31/038/2015 23:38:21 - ERROR - Drivers need to be installed for connected device.
31/038/2015 23:38:21 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Download this package of drivers and install properly (Tick Flashmode, Fastboot, Common Drivers Lagan, Xperia Tablet Z drivers).
Sorry, I forgot to mention I ran the flash tool driver utility in the flashtool\drivers directory and chose the first 2 options and the XTZ-specific option but I'll give that a shot and report back.
While I did see a driver I missed I have little change in results other than MTP in non-USB debugging mode attempted to install a driver and failed:
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device
The system cannot find the file specified.
That reminds me that when I try to manually install the driver while in usb debugging mode it has the same message but with USB Composite Device where it says MTP USB Device.
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
kadiir said:
I think I'll try this on my laptop as this PC had issues earlier this year with corruption that I thought I had fixed and I'm wondering if the corruption was more widespread than I thought.
Click to expand...
Click to collapse
Seems to be this is an issue, because flashtool driver packages installed fine for me on WinXP/7/8.
Also pc-companion usually installs everything that is necessary for its fuctional, so must be OS problem.
Yep, that was it. Man, I should've checked that first. Sorry for the waste of time.
Quick question - do you know which ADB Interface I install from the SDK drivers? Is it ADB Interface or ADB Composite Interface? Or do I do 2 passes and install both?
Never mind - did some googling and got my answer. Thanks!
So, I have searched Reddit and other sites for clues and help and I have had no luck. I have even contacted an android developer and had him try on his computer and had no luck.
I am trying to install Lineage OS for 17.1 and am currently trying to root my device. I have downloaded Google USB Drivers directly and tried from Android Studio. It detects my device fine. I go into command and run adb device, it detects my device. I reboot the device into fastboot, windows detects the driver but has no driver to install. I manually install the driver and it says it "Windows could not find the drivers for your device" despite me pointing it to "...AppData\Local\Android\Sdk\extras\google\usb_driver" which is where the driver is located. I click let me pick, install it under Andoid Devic -> Android Bootloader Interface. It says "Successfully Updated Driver" but put the device in "Other Devices" with a "?" on the icon and "Unknown Device". Even tried to see if it still worked but no device was detected (fastboot device). The Google Pixel C is "Waiting for fastboot command . . . . " but that's it.
Tried both drivers downloaded. Windows updated and no driver download. Restart windows countless times. New usb cable. Different usb port including usb 2 and 3. Nothing.
Developer reported same. Any ideas appreciated!
Thanks!
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
jwoegerbauer said:
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
Click to expand...
Click to collapse
Sorry for the slow response.
Same issue. I wouldn't expect otherwise though because the ones straight from Android Studio and Googles website doesn't work. Still shows "Unknown Device" and won't let me install the driver after showing "Waiting for fastboot command. . . ."
Drivers work fine until in fastboot mode.
Waiting for fastboot command. . . .
@slitterell
I'm pretty sure the USB driver ( does NOT mean ADB and/or Fastboot drivers ) you've installed is the culprit: Uninstall it and install the one suitable at 100% to your phone, will say the Google USB driver.
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
@slitterell
The mentioned Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.
So it should be the correct USB-driver in your case.
The latest is attached.
slitterell said:
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
Click to expand...
Click to collapse
Google's driver package doesn't have Product ID of the Pixel C mentioned in its inf file, so it doesn't work for you. Interesting that you got adb connection anyway. So, maybe Windows has installed automatically some driver but it didn't had entry for the bootloader/fastboot.
Here is how people have added those adb entries. Bootloader entry can be found from device manager and added the same way...
https://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
Or you could just use my Yet Another Universal ADB Driver Package
https://forum.xda-developers.com/an...staller-universal-adb-driver-package-t3595277
http://yet-another-universal-adbdriver.blogspot.com/
and hope for the best...