I am running vista ulimate 64 bit. I have the Samsung moment with Android 1.5. I can not get the usb driver to install on my computer.
I downloaded the android 64 bit usb driver from the sdk developer site, as well as an alternate download I found from one of the threads in this forum.
Followed these steps:
1) Type "bcdedit /set testsigning on" at an admin command prompt
2) Reboot
I have test mode in the corners...
When I point windows to the proper directory, it is not able to install the driver with the following:
Problem Event Name: PnPDriverNotFound
Architecture: x64
Hardware Id: USB\VID_04E8&PID_681C&REV_0222
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
HELP!!???
What do you mean by the first step, I have never seen that before in any adb guide? Just go to device manager, uninstall the current driver under adb interface and install the 64 bit driver.
are these the drivers you tried to install for your phone?
What are you trying to do on your phone, just see the SD Card?
I've tried several times to get these drivers to upload here and couldn't so use this link
Couldn't link either, good gosh
He said something about the SDK so I assumed he was talking about ADB...
@elephant007:
Hi,
My Windows7 is not detecting following drivers:
CDC Abstract Control Model (ACM)
CDC ACM Data
XDA
I am trying to connect my DIAM100 (Running 2.2 Froyo) as a USB Storage.
If you have the drivers can u email them to me?
I am trying to connect Archos (android 2.2.10) to Windows 7. I don't find a proper Windows 7 USB driver.
I tried Ext2 driver but, it does not support Windows 7. I am not able to find Ext 3/4 driver for download.
Please someone help me finding out Win 7 USB driver for Archos.
Upon connecting my Nvidia Shield K1 Tablet (2017) to my Windows 10 machine I get an error:
"The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
First thing I did was enabled USB debugging in Developer Options, Set USB Configuration to MTP, swapped cable, and swapped USB ports
I have followed the instructions at https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB and keep getting the error:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it's designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
I have also attempted to use the "CodeWorks-1R8-windows_b181" aswell which seemingly installed the same USB drivers but still same error.
ADB Devices and Fastboot Devices do not show any devices detected.
My phone is getting detected using same cable, I don't understand what else to do other than find x64 Nvidia Shield USB drivers but all the resources point to either of the 2 softwares above. Is my only other option making a Linux Mint bootable?
Other System Info:
Windows 10 Enterprise
AMD Ryzen 5 2600X
16GB RAM
I have made a Linux Mint USB bootable and installed ADB/Fastboot and still it will detect my phone but not my shield. I'm just using some Galaxy S7 cables, Ive seen on other forums that the shield is picky about cables for data transfer but could that really be the case? I'd test it but I don't have a premium cable laying around
I have been trying to install the Google USB Driver so I can flash a custom rom. when I tried to install it, I got this error: "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows x64-based systems"!
I'm using Windows 10, x-64-based.
Any solution?
Does not really help with Win10 but that convoluted USB-driver situation in windows is one of the reasons why I switched to Linux.
Still, if google's own installer doesn't help:
https://developer.android.com/studio/run/win-usb
...perhaps another, more OEM-specific driver will work:
https://developer.android.com/studio/run/oem-usb#InstallingDriver
I have an rca tablet I can not get any drivers to work to get to replace/update the firmware and I was wanting to ask if anyone has found anything that works.
I have tried mediatek, rca and all other drivers I can find and nothing seems to work on windows 10 64.
Thank You
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
xXx yYy said:
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
Click to expand...
Click to collapse
Thank You will give a try
I have a Windows 7 64 bit system and I am trying to find drivers to access an rca rct6703w13
I have tried every driver I can find and nothing seems to work does anyone know something that will work?
I would be very grateful if anyone could help?
Thank You
Oh boy, I still remember this pain trying to find and use such drivers on Windoze:
- try another port
- try another cable
- try this driver or that one
- try doing a rain dance with 3 days old undies on your head, and turn only clock wise, unless it's full moon, then turn counter clockwise but stop briefly after ever two and a half turns
Maybe, as workaround, you could boot from a linux CD and try your approach from there.
Whenever I flash from my debian, it works: If "fastboot devices" still doesn't show anything then usually I have forgotten to plugin the cable
By using my "Yet Another Universal ADB Driver" Package (see the link in my signature) one can remove all the old adb drivers if that is the issue, but this case seems to be more interesting...
On win10 it seems that the adb is embedded to the winusb driver the same or similar way (registry wise) that my package is using. Now that I have tested, the behavior is similar with my devices. When using file transfer connection the adb is not recognized. With others, charging, photo, midi the abd works fine. To make adb work with file transfer one have to install the correct driver. In this case google's general driver could be okay, one match for vendor and product ids in it ...
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
What I tested using virtual win7 64bit, it seems to behave the same way... which is a bit weird as I've tested it with my driver package. Worked okay then I think. The Android device used has changed since though.. It worked on win10 back then too.. the change has to have happened later.. or I didn't use file transfer..
@steadfasterX 's maid or salt or whatever it's called nowadays might be usable in this case. It's a Linux having SP flash tool etc. available..
edit: tested and it turned out that the updated phone is the problem... using another phone my driver package worked as expected..
@resxwni01
1. Don't confuse USB-driver and ADB-driver: the USB-driver since ever is by default part of any OS, so also of Windows OS. The ADB-driver is an extra protocol what allows you to communicate with a phone's Android ecosystem via an USB-connection.
2. Latest generic ADB-driver ( correct: ADB client ) got released August 2022 and is officially versioned 33.0.3.
3. AFAIK a 64-bit version of ADB-driver doesn't exist.
With regards to install this ADB-driver on a Windows 7,8.1,10,11 PC:
It's NO USB-driver installer - as introduced above by @CXZa - needed what unnecessarily bloats the Windows registry with crap.
You
1. simply create on any mounted drive of Windows PC a folder named "ADB",
2. extract there to the 3 files what are in the attached ZIP file,
3. add path of created folder "ADB" to Windows environment variable PATH, thus ADB-driver is systemwide accessible -
how to is described here
How to Set the Path and Environment Variables in Windows
Information on how to set the path and environment variables in Windows 2000, Windows XP, Windows Vista, and Windows 7.
www.computerhope.com
@jwoegerbauer , you're funny guy...