Database Develop

Help with ADB

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.

ADB Driver - Access is Denied

So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
HTC ADB Composite Device Driver (not sure exactly of this...)
Access is Denied
Click to expand...
Click to collapse
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.

Stigy said:
So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Click to expand...
Click to collapse
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess

xidominicanoix said:
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
Click to expand...
Click to collapse
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.

Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around

http://forum.xda-developers.com/showthread.php?t=532719
The link in this thread usbdeview seems to fix alot of driver issues

Stigy said:
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Click to expand...
Click to collapse
i got mines from the 1.6 sdk .. x64

Simple Solution
Here is a simple solution without having to read that long thread:
For future reference, here is how to install the drivers or fix the drivers should they not be working.
Everything you need is contained within this:
http://www.divshare.com/download/8845496-f72
This is the howto documentation
This is how to get your android phone to connect to you PC
to use functions like adb and other developer tools.
If you have installed the phone before but adb function dont work
then:
1) Run USBDeview
2) Select the list item(s) that have the word "android" within the description
3) Right Click > Uninstall
If you have done the above, or are plugging your phone in for the first time:
1) Plug in phone
2 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
2 b) If no message appears or you get a message saying drivers failed
to install. Goto device manager
2 b i) start > All Programs > accessories > run
type devmgmt.msc and press ok.
3 b) find the android device in device manager, it will have a warning icon
next to it and be in a section like unknown.
4 b) Right click and install driver
5 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
Click to expand...
Click to collapse

USBDeview is awesome but....
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.

digimancer said:
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
Click to expand...
Click to collapse
I have this same issue on an Ideos U8150 and on XP... At one point in the past it was working (before I flashed Cyanogen 7). Since then I have tried numerous driver packages, both specific to my phone and generic, and have had no luck getting past the access denied error.. I have even gone as far as changing the registry permission as well as checking all of my folder permissions... I am stumped.

Adb root - run that from command prompt.

B-man007 said:
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
Click to expand...
Click to collapse
I know it a while ago since you posted this but still, it helped me fix the "Access denied" thing which i didn't know how to fix. I installed ADB drivers 3 times... anyways, tnx :good:

So If you are like me you had this same issue in 2022. Idk if it will be a fix for you but it was for me.
follow this youtube video for the exact setup so you can get hopfully the same out com to the T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. make sure you're in administrator mode for command prompt.
2. The file name has changed from what it was so instead of doing
cd adb\platform-tools_r30.0.4-windows\platform-tools
It's now this
cd adb\platform-tools\
This will get you to the correct path if you followed the file placement in the video.
next all you have to do is type
adb devices on the command prompt. to test if it worked
other things that you might have to try is seeing if the driver it self is being blocked. you might also have to turn off and back on developer mode. View other posts in this thread if it's still stuck for you. Hopefully I helped one person at least.

[TOOL] Android Commander 0.7.9.11

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My website is down, but download is still alive.
Hi Guys!
Android Commander is windows application to keep control on your android apps and files from PC. This is a small, very very fast and intuitive app.
If someone want to try it, go a head. But remember, you doing this on your own risk! I'm not professional programmer, this is only my hobby
Program Requirements
Before you install the program you should read this:
Phone Requirements:
- ADB ROOT Access
- BusyBox
- „Settings->Applications->Development->USB debugging” must be enabled
- USB Cable
Computer Requirements:
- Windows XP/Vista/7
- ADB USB Driver
- Java JDK
- Minimum 800×600 screen resolution
Click to expand...
Click to collapse
Android Commander should works for any android device, but here is list of devices confirmed by me or users.
Before you report any problem to me, read program FAQ.
Full list of program features.
Screens:
Android Commander screenshots gallery
If you like my program, conceder a donation please!
Download is here
mirror
Program wasn't updated for a long time, but it still can work with any android device. The only think you have to do is update ADB binaries in program directory.
Click to expand...
Click to collapse
Changelog:
Version 0.7.9.11:
Changelog:
- updated adb and aapt binaries
- better work with JB
- better updates checking system (disabled as default)
- files and partitions size display improvements
- more fixes
Click to expand...
Click to collapse
Full program changelog

Ok, first off I start the app thinking it was an installer. Tells me no device is connected.
I assume the the app is now shut off since there is no indication of it running.
I plug in my phone and turn on debugging and then I get a window that says
'adb' is not a valid integer value. Then something about my adb server is out of date. Beats me what this supposed to mean.
I attempt to click the X on the warning message and it keeps poping up. So I used task manager to kill it.
WindowsXp SP3.
DroidExplorer works
Out of all seriousness I like your slim and mean approach. Just doesn't seem to work on my machine.
looks like I need a newer SDK

kizer said:
...Then something about my adb server is out of date...
Click to expand...
Click to collapse
I had issues like this with old SDK, try to install 1.6r4.

Seems to work fine for me (wit the latest sdk)
thanks for the app, will make things a little easier for me during fresh flash's

kizer said:
Then something about my adb server is out of date. Beats me what this supposed to mean.
Click to expand...
Click to collapse
You get this message if you have an adb server running (like from droid explorer) that is a different version then you are trying to start "right now". Droid Explorer uses 1.6r3 with the current install, the next release has 1.6r4.
PanPiotr said:
I had issues like this with old SDK, try to install 1.6r4.
Click to expand...
Click to collapse
Out of curiosity, what is the app doing that "requires" busybox. With Droid Explorer, I use busybox's ls command because the stock one sucks and doesn't display all the information when doing a ls -lF, plus i dont think it supports --color=always

camalot said:
Out of curiosity, what is the app doing that "requires" busybox.
Click to expand...
Click to collapse
try to run shell "rm" or "cp" command without busybox

PanPiotr said:
try to run shell "rm" or "cp" command without busybox
Click to expand...
Click to collapse
haha oh yeah, forgot about those... how quickly i take advantage of busybox. what would I do with out it.

update!!!
version 0.3.1 available now, lots of changes!

update
Version 0.4.1 with drag&drop available now!

Hi
first of all i just wanna say thanks for the app its a great idea so thanks for your hard work.
i have a problem though it doesnt work for me im running Windows 7 x64 i have latest usb drivers (r2) and latest sdk (r4) when my G1 is connected i open the app and nothing happens it just runs in processes but when phone is not connected i get message telling me phone is not connected and i click x and it still runs in processes ive tried running it in compatibility mode for xp sp2 and 3 and as and administrator still no luck i even reformatted and did a fres install of Windows 7 x64 still not working any help would be greatly appreciated.
and ideas ???

UpGrad3 said:
Hi
first of all i just wanna say thanks for the app its a great idea so thanks for your hard work.
i have a problem though it doesnt work for me im running Windows 7 x64 i have latest usb drivers (r2) and latest sdk (r4) when my G1 is connected i open the app and nothing happens it just runs in processes but when phone is not connected i get message telling me phone is not connected and i click x and it still runs in processes ive tried running it in compatibility mode for xp sp2 and 3 and as and administrator still no luck i even reformatted and did a fres install of Windows 7 x64 still not working any help would be greatly appreciated.
and ideas ???
Click to expand...
Click to collapse
Woah! you actually did a fresh install of windows to get this app working?
anyhow, if you open a command prompt and type "adb devices" what does it output.
Make sure you have USB Debugging enabled on the device. Settings -> Applications -> Development -> USB Debugging

Thanks camalot for your help, you are good guy. And also THX to you UpGrad3 (you are first ).
BTW new version soon

hmmm doesn't seem to work well with a multi-monitor setup or maybe some other issue.
When I start it with the phone not plugged in I get the Device not found off to the edge of the monitor. (APK Manager shows on the taskbar)
Connect the phone and Refresh and it's found and click OK.
Then your app disappears... nothing the the taskbar but if I check Task Manager it's running.
Little help please
Oh yeah WinXP SP3
Rogers HTC Dream - CyanogenMod 4.2.8.1

camalot said:
Woah! you actually did a fresh install of windows to get this app working?
anyhow, if you open a command prompt and type "adb devices" what does it output.
Make sure you have USB Debugging enabled on the device. Settings -> Applications -> Development -> USB Debugging
Click to expand...
Click to collapse
usb debugging is enabled
and when i type adb devices it says this: (when no adb process was running before)
C:\Users\UpGrade>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT843KV09845 device
and with adb process already running it says this:
C:\Users\UpGrade>adb devices
List of devices attached
HT843KV09845 device
strange cause droid explorer was working before the format the reason i want this is to batch install appz to my phone cause with droid explorer sometimes it doesnt install some apps and if i want to install 1 app so not batch installing it doesnt work at it allways crashes and tries to send report to microsoft thats y i need this apart from that droid explorer is brilliant so if i use them both i have the perfect android manager
I dunno what u did with the latest version 0.5.0.1 but it works it actually opened all seems to be working thanks!

This error on 0.4.2 in recovery mode

aluspl said:
View attachment 258287
This error on 0.4.2 in recovery mode
Click to expand...
Click to collapse
m8 before u run this program in recovery mode u should type in windows cmd "mount -o rw /dev/block/mmcblk0p2 /system/sd" and "mount -o rw /dev/block/mmcblk0p2 /sdcard" then its works ok

I have done a clean install of cyanogen 4.2.9.1 cause i had too much stuff on my fone so i thought id clean it up a little bit and since that android commander is not working again so its something to do with my phone does anyone kno what may be wrong ? thanks.

new version available

this program is so strange for me if i do a clean install of cyanogen it doesnt work well version 0.5 didnt and after a day or two when i have lots of apps installed to the phone it works i dont understand and now the latest version 0.6 doesnt work but it works in the places 0.5 didnt e.g. it allways opens up no matter what even on clean install so this has been improved only now it doesnt detect my phone when connected i have attached screenshots to help me explain they are here:
when i open the program i receive this message:
and when i click ok it opens like this:
please fix this cause i really like this program and appreciate ur work

as i said before, it's not program problem. this error showing because of program can not read informations form your phone. many people had issues like you (also on different forums), and every time problem was with SDK/ADB.

[Q] ADB Won't Recognize Kindle

Have the drivers sparkym3 has linked in his post. Have any and all other devices disconnected(made that mistake already) Have ADB access on and have allow installation from unknown sources checked as well. Tried the micro usb cable that came with the kindle a long with the cable that came with my Galaxy S 3. Computer sees the Kindle without issue but ADB can't seem to find it. Where am i going wrong.
Sh!!!!!tttt my bad for posting this here please move or delete.

Did you check to see if the Kindle shows up in your device manager as Composite ADB Interface?

androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
as such u mean?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or should it appear differently

was just going to post same thing mines doing same i just fallowed gide

Abiddar said:
was just going to post same thing mines doing same i just fallowed gide
Click to expand...
Click to collapse
care to elaborate?

Aali1011 said:
care to elaborate?
Click to expand...
Click to collapse
Installed all drivers computer recognizes my kindle its in device manager but my adb wont recognize
---------- Post added at 05:17 AM ---------- Previous post was at 05:12 AM ----------
Abiddar said:
Installed all drivers computer recognizes my kindle its in device manager but my adb wont recognize
Click to expand...
Click to collapse
fixed mine
uninstall driver for kindle and reinstall and re connect kindle and u should be good

Abiddar said:
Installed all drivers computer recognizes my kindle its in device manager but my adb wont recognize
---------- Post added at 05:17 AM ---------- Previous post was at 05:12 AM ----------
fixed mine
uninstall driver for kindle and reinstall and re connect kindle and u should be good
Click to expand...
Click to collapse
tried and nothing

Aali1011 said:
Have the drivers sparkym3 has linked in his post. Have any and all other devices disconnected(made that mistake already) Have ADB access on and have allow installation from unknown sources checked as well. Tried the micro usb cable that came with the kindle a long with the cable that came with my Galaxy S 3. Computer sees the Kindle without issue but ADB can't seem to find it. Where am i going wrong.
Click to expand...
Click to collapse
I posted this in the development thread. If you have the SDK installed and you get "error: device not found" or something to that effect when you run Adb Shell, you need to do the following steps.
Navigate to the [your user name]/.android folder under C:\Users
Edit the adb_usb.ini file by adding the following line of code at the end:
0×1949
Close and save the file.
Now find the folder where your SDK is installed, and open the usb_driver folder. In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Reboot and then run adb shell again. It should recognize your device. This worked for me.

Zagzagel said:
I posted this in the development thread. If you have the SDK installed and you get "error: device not found" or something to that effect when you run Adb Shell, you need to do the following steps.
Navigate to the [your user name]/.android folder under C:\Users
Edit the adb_usb.ini file by adding the following line of code at the end:
0×1949
Close and save the file.
Now find the folder where your SDK is installed, and open the usb_driver folder. In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Reboot and then run adb shell again. It should recognize your device. This worked for me.
Click to expand...
Click to collapse
what are you using to add the lines of code. It is simply just opening the file up in notepad? I intend to try this when i get home.

Aali1011 said:
what are you using to add the lines of code. It is simply just opening the file up in notepad? I intend to try this when i get home.
Click to expand...
Click to collapse
Attached is the adb_usb.ini, just locate it in c:\%user%\.android directory and remove the ".txt" at the end.
Try rebooting your computer after installing the drivers, then plug in the KF HD.

Zagzagel said:
I posted this in the development thread. If you have the SDK installed and you get "error: device not found" or something to that effect when you run Adb Shell, you need to do the following steps.
Navigate to the [your user name]/.android folder under C:\Users
Edit the adb_usb.ini file by adding the following line of code at the end:
0×1949
Close and save the file.
Now find the folder where your SDK is installed, and open the usb_driver folder. In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Reboot and then run adb shell again. It should recognize your device. This worked for me.
Click to expand...
Click to collapse
I have tried this and have not had luck. In Device Manager, it shows up as Android ADB Interface (does not have the word Composite like everyone elses'). Is this significant? I also get a pop up on my kindle about USB Compatibility with a link to download a file transfer utility. I have transferred files before, although now I don't appear to be able to.

same here haven't been able to get this to work. Still the same ADB doesn't see the device at all.

Aali1011 said:
same here haven't been able to get this to work. Still the same ADB doesn't see the device at all.
Click to expand...
Click to collapse
Keep trying. Following this guide is what did it for me https://developer.amazon.com/sdk/fire/connect-adb.html . I did this and every other method on my laptop with no luck (USB drivers crapped on me altogether, nothing works now). I finally got it to work on my computer after several attempts. Even once its working, its still fragile and requires you to unplug and reconnect often. And don't forget to turn on ADB on the Kindle (obvious, but sometimes it happens!) Good luck!

Aali1011 said:
same here haven't been able to get this to work. Still the same ADB doesn't see the device at all.
Click to expand...
Click to collapse
Unzip the attached android.zip to C:\users\"your user"(such as administrator)\
Also, the sparkym3's derive is needed to install.
you can see the attached pictures.

jst07 said:
I have tried this and have not had luck. In Device Manager, it shows up as Android ADB Interface (does not have the word Composite like everyone elses'). Is this significant? I also get a pop up on my kindle about USB Compatibility with a link to download a file transfer utility. I have transferred files before, although now I don't appear to be able to.
Click to expand...
Click to collapse
I'm in exactly the same boat.
I was able to transfer files, but after I installed the driver, I wasn't able to do so.
It shows up as "Android ADB Interface".
And of course, I tried doing everything mentioned, and I can't get into it.

dotvezz said:
I'm in exactly the same boat.
I was able to transfer files, but after I installed the driver, I wasn't able to do so.
It shows up as "Android ADB Interface".
And of course, I tried doing everything mentioned, and I can't get into it.
Click to expand...
Click to collapse
That is exactly what I was seeing on my HP laptop, but it has wonky usb drivers (have had issues with other devices). They're total broke now, it wouldn't even recognize my GNex anymore. If you can, I'd recommend trying another computer - friends or other. I don't know if that Device name has any significance, but when I did get it to work on my desktop computer it was listed as "Android Composite ADB Interface"

jst07 said:
That is exactly what I was seeing on my HP laptop, but it has wonky usb drivers (have had issues with other devices). They're total broke now, it wouldn't even recognize my GNex anymore. If you can, I'd recommend trying another computer - friends or other. I don't know if that Device name has any significance, but when I did get it to work on my desktop computer it was listed as "Android Composite ADB Interface"
Click to expand...
Click to collapse
Yeah, I also can't get it to connect to my GNex either. I'm trying on another computer now but still no progress...

For those who are having driver issues; try this program to clean your device drivers in Microsoft Windows.
GhostBuster
Here is my simple instructions, but do advise you to read the actual online documentation.
Under the Status Column RIGHT click on each item, and select "Add Device".
Check "Create System Restore Checkpoint", then Select "Remove Ghosts".
Select DEVICE(s) only in the following Catagories:
Android Phone
Disk drives
Kindle Fire
Other devices
Portable Devices
Storage Volumes
Universal Serial Bus controllers
I hope this is helpful for someone, this worked very well for me.

The exact same thing is happening to me. No matter what I do, I cant' get adb to recognize it. It says "Android ADB Interface" instead of "Android Composite USB Interface" or whatever.

This works for me
TheDoolster said:
The exact same thing is happening to me. No matter what I do, I cant' get adb to recognize it. It says "Android ADB Interface" instead of "Android Composite USB Interface" or whatever.
Click to expand...
Click to collapse
I was having the same issue like you guys. After playing around with it, I got it working.
1. uninstall all Kindle Fire HD drivers in control panel
2. download/install the Kindle Fire HD drivers from Android SDK extra
3. reconnect your Kindle Fire HD. It should say Android Composite USB Interface in Device Manager
* If that doesn't work, try restore your KFHD to factory settings. I actually did that first.

Windows update to ver. 20H2, Build 19042--Pixel 5 no longer recognized

On one of my laptops, Windows 10 performed a significant update to a new major version. All completed well, except that now my Google Pixel 5 is no longer appearing as a USB device. I have 2 laptops. Below is a device manager capture of the two laptops with the Google Pixel 5 plugged in. It appears that Windows decided to reclassify how Android phones now appear (no longer under "Portal" and now under "Android Devices"). My Pixel 5 doesn't show up, instead there's a "Google Nexus ADB Interface." Well, I uninstalled it and it automatically installed again... a check for online updates says it's the latest. But in Windows Explorer I do not see my Google Pixel 5 when setting to File Transfer mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've ditched my days of being involved in firmware updates because the latest phones are so capable now, especially with customizations. I thought perhaps a driver update directly from Google would be in order, but I'm unable to find anything... only stuff for the SDK.
I posted about this on Reddit r/GooglePixel, and got no help. If anyone here has a useful idea, please share. Thanks!

I think a few things could be happening. First, if you do not have ADB tools (Android ADK) installed, it may default to the phone name because it isn't finding the ADB interface, but the other phone interfaces (PTP for example). Was the Android SDK installed on the old version too?
Also, do you happen to have it linked to your computer with "My Phone"? You may get a more accurate name if you have linked it.
But ultimately, what is your goal?

bitpushr said:
I think a few things could be happening. First, if you do not have ADB tools (Android ADK) installed, it may default to the phone name because it isn't finding the ADB interface, but the other phone interfaces (PTP for example). Was the Android SDK installed on the old version too?
Also, do you happen to have it linked to your computer with "My Phone"? You may get a more accurate name if you have linked it.
But ultimately, what is your goal?
Click to expand...
Click to collapse
Yes, I had the ADB tools, Android SDK installed on only one computer., my primary. (On the older one it didn't have ADB. <--- FALSE). ClockworkMod was installed. But I wiped that clean.
Interesting, on my other computer I rechecked--I do have Android SDK installed on it... I just didn't put ClockworkMod on it.
Not sure what you mean by linking it with "My Phone." I have a USB-C cable, which has worked before just fine. My device is simply named "Pixel 5."
Btw, after installing all ADB drivers, I'm finding that when I plug in my Pixel 5, the "Google Nexus ADB Interface" node appears again under "Android Devices." What's going on? Is Windows somehow retrieving the ADB drivers from somewhere in a CAB file or something?
My goal is simple--I want to connect my Google Pixel 5 to my laptop and have it available as a USB storage device so I can transfer files to and from the device. I've done this for years... and this latest Windows update somehow screwed things up for me.
EDIT: For what it's worth, I was able to connect to Microsoft Windows Support via chat, for free. The technician looked this up and said it's a known issue for some configurations. Apparently there will be an update in a few weeks and he suggested rolling back to the previous version if I can't wait.

cytherian said:
Yes, I had the ADB tools, Android SDK installed on only one computer., my primary. (On the older one it didn't have ADB. <--- FALSE). ClockworkMod was installed. But I wiped that clean.
Interesting, on my other computer I rechecked--I do have Android SDK installed on it... I just didn't put ClockworkMod on it.
Not sure what you mean by linking it with "My Phone." I have a USB-C cable, which has worked before just fine. My device is simply named "Pixel 5."
Btw, after installing all ADB drivers, I'm finding that when I plug in my Pixel 5, the "Google Nexus ADB Interface" node appears again under "Android Devices." What's going on? Is Windows somehow retrieving the ADB drivers from somewhere in a CAB file or something?
My goal is simple--I want to connect my Google Pixel 5 to my laptop and have it available as a USB storage device so I can transfer files to and from the device. I've done this for years... and this latest Windows update somehow screwed things up for me.
EDIT: For what it's worth, I was able to connect to Microsoft Windows Support via chat, for free. The technician looked this up and said it's a known issue for some configurations. Apparently there will be an update in a few weeks and he suggested rolling back to the previous version if I can't wait.
Click to expand...
Click to collapse
Nonsense. I have the same Win 10 version and everything connects the same. They are clueless and reverting might bring way more problems than you wish to deal with. It's a driver issue plain and simple. There is a .inf file that needs to be reinstalled but I'll be darned if I remember which and what exactly to do. I'll research it a little tomorrow and see if I can find the solution. Whatever you do don't follow Microsoft help forums, you'll be installing crap that won't help.
edit: Ok this is what I did way back and it worked. Good luck. https://forum.xda-developers.com/t/...allation-on-windows-10.3570625/#post-71364316

bobby janow said:
Nonsense. I have the same Win 10 version and everything connects the same. They are clueless and reverting might bring way more problems than you wish to deal with. It's a driver issue plain and simple. There is a .inf file that needs to be reinstalled but I'll be darned if I remember which and what exactly to do. I'll research it a little tomorrow and see if I can find the solution. Whatever you do don't follow Microsoft help forums, you'll be installing crap that won't help.
edit: Ok this is what I did way back and it worked. Good luck. https://forum.xda-developers.com/t/...allation-on-windows-10.3570625/#post-71364316
Click to expand...
Click to collapse
Thanks...
Yeah, I've been around the block enough times to know that Microsoft Windows O/S installations are often buggy and fragile. I never take a major upgrade with ease. I always expect there may be an issue. And rolling back is only a very last resort.
In my case, I do not get an unknown or MTP device listed in the Device Manager. I tried doing the INF install... both with the wpdmtp.inf file and the Google provided android_winusb.inf.... No change. Every single time I plug in my Google Pixel 5, I get an "Android Devices" node with "Google Nexus ADB Interface" showing. And, still no device listed in Windows Explorer when I switch to USB File Transfer mode.

@cytherian It was worth a shot. My laptop says something different although it's basically the same I think. Mine says, "LeMobile Android Device" and under it Android composite ADB Interface. So even though I know you know these things and probably have tried each and every one I'll list them as I'd do them.
Make sure you have the very latest Platform tools
Try a different USB port
Try an A to C adapter rather than C to C
Try a different cable.
I think since it reinstalls auto then your laptop's drivers are fine. Mine is dated 2016 so I'm sure yours is the latest. It's gonna be something simple, you'll figure it out. In the meantime can you use a different computer that recognizes it and do the file transfers there?

bobby janow said:
@cytherian It was worth a shot. My laptop says something different although it's basically the same I think. Mine says, "LeMobile Android Device" and under it Android composite ADB Interface. So even though I know you know these things and probably have tried each and every one I'll list them as I'd do them.
Make sure you have the very latest Platform tools
Try a different USB port
Try an A to C adapter rather than C to C
Try a different cable.
I think since it reinstalls auto then your laptop's drivers are fine. Mine is dated 2016 so I'm sure yours is the latest. It's gonna be something simple, you'll figure it out. In the meantime can you use a different computer that recognizes it and do the file transfers there?
Click to expand...
Click to collapse
Yep, tried USB port change... no dice. Cable is same I've been using, but tried another. Both work on my other laptop. I am really not planning to delve back into firmware flashing, but maybe I should just go install the latest Android SDK and all the drivers from that to see if that somehow fixes things.

cytherian said:
Yep, tried USB port change... no dice. Cable is same I've been using, but tried another. Both work on my other laptop. I am really not planning to delve back into firmware flashing, but maybe I should just go install the latest Android SDK and all the drivers from that to see if that somehow fixes things.
Click to expand...
Click to collapse
Yes try that for sure.

I uninstalled ClockworkMod, but this driver keeps appearing. I went to USBDeview, found 3 listings for the ClockworkMod, deleted them...
STILL... when I plug in my damned Pixel 5, this ClockworkMod driver keeps coming up! I searched the Registry. Found a few entries. Deleted them. Restarted my computer. Plugged in my Pixel 5... It's Baaaaaaaaaaaaaaaaack!
What in the world?

cytherian said:
View attachment 5258887
I uninstalled ClockworkMod, but this driver keeps appearing. I went to USBDeview, found 3 listings for the ClockworkMod, deleted them...
STILL... when I plug in my damned Pixel 5, this ClockworkMod driver keeps coming up! I searched the Registry. Found a few entries. Deleted them. Restarted my computer. Plugged in my Pixel 5... It's Baaaaaaaaaaaaaaaaack!
What in the world?
Click to expand...
Click to collapse
To remove the driver:
Open and admin command prompt
Type dism /online /get-drivers
Look through the list for the above driver. Provider Name, Date, and Version should all match. Use the Published Name in the command below
Type dism /online /remove-driver oemXXX.inf
Do be careful, there are no "are you sure" prompts with this method.
You should also be able to force it to the Google USB driver as well if you have it downloaded from the android SDK. Use the update driver button and browse to the extras\google\usb_driver folder.

l7777 said:
To remove the driver:
Open and admin command prompt
Type dism /online /get-drivers
Look through the list for the above driver. Provider Name, Date, and Version should all match. Use the Published Name in the command below
Type dism /online /remove-driver oemXXX.inf
Do be careful, there are no "are you sure" prompts with this method.
You should also be able to force it to the Google USB driver as well if you have it downloaded from the android SDK. Use the update driver button and browse to the extras\google\usb_driver folder.
Click to expand...
Click to collapse
I ran DISM and did not find ClockwordMod indicated anywhere in the driver list.
I went ahead an plugged in my Pixel 5... the "Android Devices" node appears. "Google Nexus ADB Interface" is there again. It shows that pesky ClockwordMod driver again. And when I run DISM, there's no indication of "ClockworkMod" anywhere. I do see the AndroidUsbDeviceClass, android_winusb.inf, dated 8/28/2014, version 11.
Still, can't get access to my Pixel 5 in Explorer...

cytherian said:
I ran DISM and did not find ClockwordMod indicated anywhere in the driver list.
I went ahead an plugged in my Pixel 5... the "Android Devices" node appears. "Google Nexus ADB Interface" is there again. It shows that pesky ClockwordMod driver again. And when I run DISM, there's no indication of "ClockworkMod" anywhere. I do see the AndroidUsbDeviceClass, android_winusb.inf, dated 8/28/2014, version 11.
Still, can't get access to my Pixel 5 in Explorer...
Click to expand...
Click to collapse
Did it have enough buffer to scroll all the way to the beginning of the driver list? DISM Should list all third party drivers. You might want to do:
dism /online /get-drivers > drivers.txt
notepad drivers.txt
Another alternative since it sounds like the correct driver is indeed installed
Update driver button
Browse for driver
Let me pick from a list
Select Android Composit ADB Interface
EDIT:
I re-read the thread and it seems you're trying to get usb storage to work. That should be a different driver all together. The one you're looking at should be for the android debug bridge and should disappear if you turn off USB debugging. To confirm, go to the details tab of the device properties and see what hardware ID it is.
USB\VID_18D1&PID_4EE1 = USB Storage
USB\VID_18D1&PID_4EE1&MI_01 = ADB

l7777 said:
Did it have enough buffer to scroll all the way to the beginning of the driver list? DISM Should list all third party drivers. You might want to do:
dism /online /get-drivers > drivers.txt
notepad drivers.txt
Another alternative since it sounds like the correct driver is indeed installed
Update driver button
Browse for driver
Let me pick from a list
Select Android Composit ADB Interface
EDIT:
I re-read the thread and it seems you're trying to get usb storage to work. That should be a different driver all together. The one you're looking at should be for the android debug bridge and should disappear if you turn off USB debugging. To confirm, go to the details tab of the device properties and see what hardware ID it is.
USB\VID_18D1&PID_4EE1 = USB Storage
USB\VID_18D1&PID_4EE1&MI_01 = ADB
Click to expand...
Click to collapse
Yes, I thought it was implied... wanting Windows Explorer access to files would mean USB storage. I did have sufficient buffer to scroll through the whole list. In fact, I copy/pasted it into a text editor for easy searching.
Devices showing up under "Google Nexus ADB Interface":
USB\VID_18D1&PID_4EE1&REV_0440
USB\VID_18D1&PID_4EE1
NOTE - In Events I see this:
Device install requested
Device not migrated
Driver service added (WinUSB)
I should also note that in the System Tray, for USB devices, I see "Pixel 5." I have the option to eject if I wish. So, Windows is seeing the device but perhaps somehow the wrong driver is being mapped?
What really bugs me is... WHY is this "ClockworkMod" driver even showing up? Is Windows dynamically picking it up somewhere?

cytherian said:
Yes, I thought it was implied... wanting Windows Explorer access to files would mean USB storage. I did have sufficient buffer to scroll through the whole list. In fact, I copy/pasted it into a text editor for easy searching.
Devices showing up under "Google Nexus ADB Interface":
USB\VID_18D1&PID_4EE1&REV_0440
USB\VID_18D1&PID_4EE1
NOTE - In Events I see this:
Device install requested
Device not migrated
Driver service added (WinUSB)
I should also note that in the System Tray, for USB devices, I see "Pixel 5." I have the option to eject if I wish. So, Windows is seeing the device but perhaps somehow the wrong driver is being mapped?
What really bugs me is... WHY is this "ClockworkMod" driver even showing up? Is Windows dynamically picking it up somewhere?
Click to expand...
Click to collapse
Windows loads drivers based on the hardware IDs. For some reason the ClockworkMod driver is claiming to be for one of those hardware ids. Now that I know it's supposed to be the storage driver try this:
Update Driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
See if "MTP USB Device" is listed
Another option to identify the clockworkmod driver
Details tab
Inf name
If it starts with oemXX.inf it should be safe to use dism to remove it

You know what's so bizarre?
Published Name : oem47.inf
Original File Name : android_winusb.inf
Inbox : No
Class Name : AndroidUsbDeviceClass
Provider Name : ClockworkMod
Date : 8/27/2012
Version : 7.0.0.4
Notice it's indicating the original filename as "android_winusb.inf."
Well, sure enough oem47.inf is in the Windows/INF directory, and it has "ClockworkMod" info in it.
I tried removing it with dism /online /remove-driver /driver: oem47.inf
Failed. Error: 50, "This command can only be used with an offline image."
I discovered that I could rename the files (oem47.infx, oem47.pnfx), then move them off to a TEMP folder. I rebooted... and oddly, "oem47.inf" is still showing in the DISM driver list. I ran USBDeview, noticed it was still there, so I deleted it. Ran the DISM get-drivers cmd again... STILL showing up. It did NOT mysteriously reappear in Windows/INF. So I figured it must be in the registry. The only registry entries I could find is "oem47.inf" among others in "Owners" of various DLL files.

cytherian said:
You know what's so bizarre?
Published Name : oem47.inf
Original File Name : android_winusb.inf
Inbox : No
Class Name : AndroidUsbDeviceClass
Provider Name : ClockworkMod
Date : 8/27/2012
Version : 7.0.0.4
Notice it's indicating the original filename as "android_winusb.inf."
Well, sure enough oem47.inf is in the Windows/INF directory, and it has "ClockworkMod" info in it.
I tried removing it with dism /online /remove-driver /driver: oem47.inf
Failed. Error: 50, "This command can only be used with an offline image."
I discovered that I could rename the files (oem47.infx, oem47.pnfx), then move them off to a TEMP folder. I rebooted... and oddly, "oem47.inf" is still showing in the DISM driver list. I ran USBDeview, noticed it was still there, so I deleted it. Ran the DISM get-drivers cmd again... STILL showing up. It did NOT mysteriously reappear in Windows/INF. So I figured it must be in the registry. The only registry entries I could find is "oem47.inf" among others in "Owners" of various DLL files.
Click to expand...
Click to collapse
see if pnputil will do the job. I could've sworn I've used DISM to remove online drivers before.
pnputil -d oem47.inf
or
pnputil -f -d oem47.inf

Thanks! That did the trick --> pnputil -d oem47.inf
And... I plugged in my Pixel 5... low & behold, Windows tells me it discovered a new device, setting it up... and...
YES!
I see it now in Windows Explorer!
So this was the problem. A LEGACY issue, with a leftover INF file. Somehow this was taking priority, because in the OEM list, the proper one is oem87.inf.
What an ordeal. Can you imagine if a novice had to face this?

cytherian said:
Thanks! That did the trick --> pnputil -d oem47.inf
And... I plugged in my Pixel 5... low & behold, Windows tells me it discovered a new device, setting it up... and...
YES!
I see it now in Windows Explorer!
So this was the problem. A LEGACY issue, with a leftover INF file. Somehow this was taking priority, because in the OEM list, the proper one is oem87.inf.
What an ordeal. Can you imagine if a novice had to face this?
Click to expand...
Click to collapse
Glad you got it worked out. It is a bit of driver hell. Side effect of supporting nearly every piece of hardware that one could plug into a computer. They should make it easier to manage them though. I'm actually surprised that it's still using a third party driver (oemXX.inf). My 20H2 system is using a built in driver, wpdmtp.inf.

l7777 said:
Glad you got it worked out. It is a bit of driver hell. Side effect of supporting nearly every piece of hardware that one could plug into a computer. They should make it easier to manage them though. I'm actually surprised that it's still using a third party driver (oemXX.inf). My 20H2 system is using a built in driver, wpdmtp.inf.
Click to expand...
Click to collapse
Thanks. Yes, at this late stage of the game, Windows Device Management should be revised. It's the same old interface we've had for almost 2 decades. Such a PITA to update drivers. The thing is, the Google Pixel 5 is from... GOOGLE. A software giant. Wouldn't Microsoft ensure that those drivers will be picked up and not allow an obsolete driver to override? Just boggles my mind.
Well, on my system now, the Pixel 5 is being supported by the same driver as yours, wpdmtp.inf. It seems to have been mapped when Windows 10 recognized the Pixel 5 as a new device. It was the old driver that was blocking the installation, somehow.

cytherian said:
Thanks. Yes, at this late stage of the game, Windows Device Management should be revised. It's the same old interface we've had for almost 2 decades. Such a PITA to update drivers. The thing is, the Google Pixel 5 is from... GOOGLE. A software giant. Wouldn't Microsoft ensure that those drivers will be picked up and not allow an obsolete driver to override? Just boggles my mind.
Well, on my system now, the Pixel 5 is being supported by the same driver as yours, wpdmtp.inf. It seems to have been mapped when Windows 10 recognized the Pixel 5 as a new device. It was the old driver that was blocking the installation, somehow.
Click to expand...
Click to collapse
Right, and that driver is dated 6/21/2006. The clockworkmod driver is dated 2012. I suspect that Window's logic matches the device id first and then looks for the latest driver available. In this case the question is why was the clockworkmod driver claiming to be for the storage device id rather than the ADB device id. I'd have been curious to know if you could have manually chosen the older (and correct) driver.