Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?
CyanFrank said:
Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?
Click to expand...
Click to collapse
Airdroid. No need for a cable.
When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
If the MTP makes it stutter it could be a problem with MTP or simply that MTP does more traffic and is uncovering lower level problems.
CyanFrank said:
...There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
Click to expand...
Click to collapse
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.
manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.
Click to expand...
Click to collapse
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install
Renate said:
When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
Click to expand...
Click to collapse
No, phone is charging and debugging is enabled so that I see two notifications.
Tried the first command and phone started disconnecting just like with MTP enabled. ADB had stopped working.
manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager?
Click to expand...
Click to collapse
It used to, but apparently I messed up with drivers while trying to solve the issue, so it's not working right now.
hammered58 said:
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install
Click to expand...
Click to collapse
Yeah I noticed LeMobile drivers are available to download. There is Android Composite ADB device listed as "LeMobile" but ADB still not fixed.
And it seems like I'm back to sqaure one because there's the very first issue I had: after choosing MTP on my phone all options become gray and it returns back to "only charging" after few seconds. Sometimes it even starts disconnecting/connecting.
Yeah it seems something is particularly wrong with my home PC because MTP works flawlessly with my work PC. Didn't have to install any drivers etc.
Do you have the latest windows platform tools installed?
Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.
Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
Yes.
{
"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"
}
bobby janow said:
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.
Click to expand...
Click to collapse
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.
CyanFrank said:
Yes.View attachment 5774787
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.
Click to expand...
Click to collapse
That could be the one. If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one. I searched and there are a bunch of "solutions" out there and I hope you find the correct one before you have to reinstall the whole darn OS. I'll keep looking though. I was so frustrated by it I wanted to throw the laptop out the windows. lol. I still think it's one pesky driver.
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.
EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.
Click to expand...
Click to collapse
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.
bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.
Click to expand...
Click to collapse
I mean I probably would do the same but if OP is already at the point of reinstalling Windows, I figured I would provide some less annoying options. Virtual machines have saved me immense amounts of frustration over the years and Player is phenomenal for something free of charge.
bobby janow said:
If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one.
Click to expand...
Click to collapse
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick.
Click to expand...
Click to collapse
Yeah, actually didn't think about that, thanks. I'll give it a try when I get enough time.
bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall.
Click to expand...
Click to collapse
As I said, I have no USB A-C cable that supports data transfer. But I'll borrow one to at least try.
And the thing is it might not fix the problem as well if drivers are screwed up.
If you have another USB-C port, I would try that as well. Sometimes different ports, even on the same controller, can have different results.
Unfortunately I have just one USB-C port.
CyanFrank said:
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
Click to expand...
Click to collapse
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.
bobby janow said:
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.
Click to expand...
Click to collapse
Yeah, I tried that as well.
And forgot to mention that I borrowed USB A-C cable and MTP actually worked. It's not as stable as it should be (sometimes it disconnects) but still it works.
Related
ADB was working perfectly fine until this morning. Now it says Device Not Found. Any suggestions on how I can get it working again? Thanks in advance.
Bump. Anyone know?
Does fastboot work then?
Are you on windows? window 7?
Try every USB port on your computer, my win7 machine will only recognise my device through one usb port.
liam.lah said:
Does fastboot work then?
Are you on windows? window 7?
Try every USB port on your computer, my win7 machine will only recognise my device through one usb port.
Click to expand...
Click to collapse
Windows 7. Fastboot works just fine. Never had this problem before. My Nexus shows up as connected and working in Windows Device Manager. WTF is going on? Frustrating.
Tried all USB ports. All of them recognize the device, but "adb remount" returns: "error: device not found."
Part Four said:
Windows 7. Fastboot works just fine. Never had this problem before. My Nexus shows up as connected and working in Windows Device Manager. WTF is going on? Frustrating.
Tried all USB ports. All of them recognize the device, but "adb remount" returns: "error: device not found."
Click to expand...
Click to collapse
Do you have the Allow USB Debugging option checked? Maybe it got unchecked on accident.
Diceman4 said:
Do you have the Allow USB Debugging option checked? Maybe it got unchecked on accident.
Click to expand...
Click to collapse
Yeah, thanks. I've had it checked. I've tried to adb remount on all 4 of my computers tonight and none of them are finding my device anymore. Might be time for a wipe and reflash. Anyone else have a suggestion before I commit to a wipe?
I guess I'm going to wipe and reflash.
1)make sure usb tethering is off.
2)maybe reinstall the latest driver from http://developer.android.com/sdk/win-usb.html ?
I just wiped and reflashed and still no dice. Might as well just go back to my nandroid backup and keep searching for answers.
I know this might be a little late, but I would like to post how I solved my problem. I too was experiencing this problem, no matter what USB Port I plugged my phone into, it just would not work. It kept saying "error: device not found." After searching on Google for a quite a while, I decided to again play around in device manager. I remember a long time ago, a client of mine had a problem with certain USB Devices not working, the solution was to go into Device Manager expand "Universal Serial Bus controllers" and right click each "USB Root Hub" and click "Uninstall."
This did the trick for me. After I hit the right USB Root Hub, my computer detected three new Android controllers that needed drivers: CDC, CDC Abstract, and Android Composite. I installed the downloaded Android drivers for the Android Composite and guess what, IT WORKS!
Hope this helps someone.
Mike Lierman
Founder and Owner of
Invise Solutions
invisesolutions.com
0vermind said:
I know this might be a little late, but I would like to post how I solved my problem. I too was experiencing this problem, no matter what USB Port I plugged my phone into, it just would not work. It kept saying "error: device not found." After searching on Google for a quite a while, I decided to again play around in device manager. I remember a long time ago, a client of mine had a problem with certain USB Devices not working, the solution was to go into Device Manager expand "Universal Serial Bus controllers" and right click each "USB Root Hub" and click "Uninstall."
This did the trick for me. After I hit the right USB Root Hub, my computer detected three new Android controllers that needed drivers: CDC, CDC Abstract, and Android Composite. I installed the downloaded Android drivers for the Android Composite and guess what, IT WORKS!
Hope this helps someone.
Mike Lierman
Founder and Owner of
Invise Solutions
invisesolutions.com
Click to expand...
Click to collapse
Unfortunately this didn't work for me. I tried uninstalling every single USB device/port/hub on two of my systems, then rebooting and letting it do its thing, then plugging in my Nexus and installing the ADB drivers. Still can't connect via ADB. This is a complete mess. No clue how/why this happened or what I can do to get it back.
0vermind said:
I know this might be a little late, but I would like to post how I solved my problem. I too was experiencing this problem, no matter what USB Port I plugged my phone into, it just would not work. It kept saying "error: device not found." After searching on Google for a quite a while, I decided to again play around in device manager. I remember a long time ago, a client of mine had a problem with certain USB Devices not working, the solution was to go into Device Manager expand "Universal Serial Bus controllers" and right click each "USB Root Hub" and click "Uninstall."
This did the trick for me. After I hit the right USB Root Hub, my computer detected three new Android controllers that needed drivers: CDC, CDC Abstract, and Android Composite. I installed the downloaded Android drivers for the Android Composite and guess what, IT WORKS!
Hope this helps someone.
Mike Lierman
Founder and Owner of
Invise Solutions
invisesolutions.com
Click to expand...
Click to collapse
Thanks it helped me
try going into the device manager and removing the driver. Remove your phone from your computer then reconnect it. Upon the request to allow drivers to install, tell it you want to install from a specific location and point the driver installer to a known good copy of the ADB driver.
-------------------------------------
Sent via the XDA Tapatalk App from my Nexus One
Hey Guys,
Firstly just got my captivate a couple of days ago and i am still struggling to get to install drivers and have my pc detect the phone. I am totally new to android (coming from iphone)... there might be some obvious things that I might be missing here...
Here is what has happened so far
I have pretty much tried all the drivers on the web and I am still unable to see the drives on my PC. Driod explorer is unable to detect the phone. Device manager is showing a USB device by the name "SAMSUNG Android USB Composite Device".
In the phone i have enabled usb debugging. Once the cable gets connected, I also open notification and enable USB storage.
I am still not able to see the drive or have any applications in my pc detect the phone. What am i missing?
A simple usb device installation has never given me so much trouble. Starting to get frustrated.
Appreciate any pointers in resolving this issue.
Thanks
So you chose "Mass Storage" in settings? And once you connected, pull down the drop down men you, press USB, and then press the "Mount" button?
Mine worked just fine on WinXP and Win7 64 bit once I enabled mass storage and then confirm "Mount" each time you connect.
yes I did choose mass storage option & mount it.
I am able to see the usb drives in windows xp. But cant resolve the issues with win 7 64bit. I am using the following drivers
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
s1lverdream said:
I am able to see the usb drives in windows xp. But cant resolve the issues with win 7 64bit. I am using the following drivers
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
Click to expand...
Click to collapse
I know a few people who had connections problems too. They were able to fix it using this driver: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
Some others were also able to do it using the Samsung Kies program.
Just one thing, though. You said in your post you're selecting 'Mass Storage'. Did you try selecting 'Kies' (this is even without installing the Kies program)? Try doing that. Also, try having USB debugging off when you perform the aforementioned test.
All I can get with debugging on or off and mass storage is this
{
"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"
}
no matter what drivers i use. I cant mount it on Windows 7 but I can on vista
My desktop is running Windows 7 64-bit, and I couldn't get it to recognize my phone for anything, even with the drivers from Samsung. The computer doesn't even pick up the phone as a device, much less one it recognizes. I had to use my netbook (Windows 7 32-bit/Linux) to do all my phone-related hacking stuff.
I'm using Win 7 64-bit and here's what I did after reading some suggested steps in another thread:
Install Samsung Kies first, before ever connecting the phone.
Run the program, then connect the phone to a USB port on the motherboard. Not one on the front of the case.
Windows SHOULD start installing the drivers.
I think I selected the Kies option on the phone the first time. Three or four different drivers were installed I believe. When I connected the phone again and selected Mass Storage, two or three different drivers were installed by Windows.
Does this mean I have proper drivers:?
Hi guys,
I just bought a new hp computer with win 7 64 bit os. I am able to use microsoft synctoy to syn itunes to my cappy. Does this mean that I have the proper usb drivers installed on my computer for my phone. I was thinking about rooting my phone and wanted to have the correct drivers installed.
Thanks, I consider myself a newby to the forum and to rooting, so any help would be appreciated.
drewfs7270
Has any headway been made on this as I just got windows 7 64 bit, and am having a similar problem. Tried various drivers and whatnot but still cant seem to get the usb to mount like a flash drive. It is being recognized and can receive commands like reboot into download mode from AOI toolbox, but no mounting.. Kinda driving me up the wall bc Ive been stuck on the same rom for a few weeks now and Im itching to get back to flashing all the fresh new cm7 stuff out and just in general new roms.
The newest Kies will install a driver pack when you download it now.
MAkE SURE YOU REMOVE ANY SAMSUNG DRIVERS THAT ARE CURRENTLY INSTALLED
1.) download the newest Kies http://www.samsungapps.com/about/onPc.as?COUNTRY_CODE=CAN&LANGUAGE_CODE=ENG
2.) Install it. While it's installing it will install a driver pack.
3.) Plug your phone in.
This works for X64. I just used it on my own pc last week.
jack_slapped said:
Has any headway been made on this as I just got windows 7 64 bit, and am having a similar problem. Tried various drivers and whatnot but still cant seem to get the usb to mount like a flash drive. It is being recognized and can receive commands like reboot into download mode from AOI toolbox, but no mounting.. Kinda driving me up the wall bc Ive been stuck on the same rom for a few weeks now and Im itching to get back to flashing all the fresh new cm7 stuff out and just in general new roms.
Click to expand...
Click to collapse
Turn on USB Debugging.
Lol I know how to enable USB debugging man. What I'm saying is windows wont allow it to mount for some strange reason. Going to try the kies driver mentioned earlier. Maybe that will work.
So I tried the kies drivers, and Im getting the same problem. The drivers will install and it will even trick me by showing the removable letters for my storage, but then after a second or so they disappear. When looked at under device manager they are just shown as unknown device. I just wanna backup my data like I used too.
jack_slapped said:
So I tried the kies drivers, and Im getting the same problem. The drivers will install and it will even trick me by showing the removable letters for my storage, but then after a second or so they disappear. When looked at under device manager they are just shown as unknown device. I just wanna backup my data like I used too.
Click to expand...
Click to collapse
I definitely don't want to insult anyone's intelligence here (which usually means I am going to). i assume we've tried restarting the computer again.....a couple of times.......and if that doesn't work, then manually uninstalling all the drivers which have been installed so far and then starting over using just kies?
Yea, all those mentioned have been tried.
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't know if this means anything, but windows can recognize my device. Sorta. I tried flashing to stock in hopes that would fix the problem, but it didn't. Isn't it strange that I can flash my phone but not be able to mount my storage??
Sent from my SAMSUNG-SGH-I897 using XDA App
okay...
So i was able to connect to my Win 7 64 bit computer for a little while ... had to in order to update to Mini Keis 2.2 (ran into problems there but fixed it <if you have questions about it PM me>)
But now that i am in 2.2 i am not able to connect. I get an error saying drivers could not be installed. I have uninstalled the original drivers and installed the ones from AT&T and also tried the ones from Samsung... still same problem. Does anyone one have an idea as to what i can do to solve this problem.
Thanks to any one who can help
I've had luck by doing the following:
Had my phone plugged in - it went fubar - computer didn't recognize the phone.
Re-installed USB drivers (ones Design Gears posted and the ones linked in the Q&A sticky btw) over the top of the existing drivers with the phone plugged in - USB De-Bugging on.
Rebooted PC - winblows found the phone and everything was peachy. Windows 7 64 is definitely nice - but still has issues with detecting drivers and USB devices sometimes. Its still Windows after all
If it works on another PC than you know its a software issue with windows.
If your still getting the same error on another PC - then its possible that your internal card might be fubar.
Well I have tried EVERYTHING. Multiple drivers, uninstalling, reinstalling, rebooting, usb debugging on/off, flashed to stock....Nothing. Windows 7 64bit. I hate hate hate you and hope you die of viral infection.
Hey, everyone, I tried posting about this in the CM7 general discussion thread, but no one seemed apt to respond.
I think this was a problem that popped up in the 60s or 70s in terms of nightlies, but I'm having it again now since around the 155 mark.
I'm on 160 and when I plug my NC into the USB cable, I no longer get any options to connect for file transfers in the notification area. If anyone could help me out with this, I'd really appreciate it. It's just so perplexing and no one seems be having this issue except me. If it's user-side error, that's fine as well, I'd just like to know how to fix it.
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
votinh said:
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
Click to expand...
Click to collapse
1. No, nothing comes up.
2. The notification area remains blank.
3. I'm running it off eMMC.
Thanks for taking the time, by the way!
If so, unplug the usb cable then replug in a few times and see what happens.
If still nothing, try to use other usb cable.
Oh, btw, have you had Nookcolotweaks app installed?
I do have Nook Tweaks installed, yes. I'm using the cable that came with the Nook, but I'm not sure I have any other cables around.
Do make sure you check OFF the USB Host feature (reboot and reconnect)
I gave that a try, too, but still nothing. So confusing!
Don't be so hard on yourself.
Let try it on different computer if you have.
Also try difference usb cable.
Last, if nothing works, update latest nightly build
When you disconnect and reconnect the nook in testing/trying to get it recognized... unplug usb cable from computer... its made a difference at times.
I know this sounds basic but in applications-settings ensure you have usb debugging checked. Sometimes when flashing different nightlies, settings change.
Sent from my NookColor using Tapatalk
Thanks again for all the help, everyone! I made sure USB debugging was checked and tried unplugging/replugging the cable, but there's still no notification coming up.
A new development:
I tried connecting it to my Windows PC instead of my Linux and it brought up this message that said it didn't recognize the device. I also tried to get ADB to see it and it can't. Does this information help or am I in trouble here?
Next time, do clearly indicate that you are using Linux or Windows. I'm sure many members here are Linux but still far less support than Windows world.
When I provided those suggestions in previous posts, I meant in Windows.
Anyway, back to your issue.
1. "it didn't recognize the device" because of missing adb usb driver. You need to get it installed first in order to use ADB, however it has nothing to do with your usb mass storage function. For now, you don't need to worry about it just yet.
2. Back to my question before, have you seen any "removable" on the PC (Windows)
Along with USB Host uncheck, if still having problem, I would suggest you either downgrade to the earlier versions or wait until tomorrow and update with another nightly build.
Good luck
I have the ADB drivers installed in Windows, as far as I know. I've used it before.
I typed "adb devices" into the prompt and it doesn't see the NC at all. Since one of the nightlies seems to be what prompted this sudden change in connectivity, I guess I'll just hope that one of the new ones can fix it. Thanks again.
Also, Windows doesn't show anything "removable" except for my external HD.
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
arda99 said:
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
Click to expand...
Click to collapse
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
junkrobot said:
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
Click to expand...
Click to collapse
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
If you've installed ADB drivers, you might want to remove it as this might mess up usb storage.
arda99 said:
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
Click to expand...
Click to collapse
Alrighty. I have those two. I've connected my NC to ADB both wirelessly and and with the cable in the past, so this should all be straightforward anyhow. It just plain refuses to cooperate.
Go to the Marketplace and download "Nook Color UMS" app. Follow instructions and it will mount properly. I had the same issue used it and it mounts proper through the app.
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 5B9EA9C73066E8F655D14BBA8318C176
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
jadengore said:
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
Click to expand...
Click to collapse
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
1wayjonny said:
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
Click to expand...
Click to collapse
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
agrabren said:
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
Click to expand...
Click to collapse
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
AndrewNeo said:
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
Click to expand...
Click to collapse
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
PR0XIDIAN said:
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
Click to expand...
Click to collapse
The issue with the touchscreen is the driver. While it runs great in Android, it doesn't work in recovery, making a touch-based recovery a nightmare. Believe me, I already tried for a few days. I'm sure with enough time, I could get it working, but I didn't want to invest that much time with all the other things on my plate at the moment. I just don't expect recovery to come out this week with touch.
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Fix Fastboot issues on Windows 8: http://www.youtube.com/watch?v=XSisjVwcPbE
wwjoshdew said:
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
Click to expand...
Click to collapse
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
1wayjonny said:
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
Click to expand...
Click to collapse
haha. She's a trip though. Thanks a lot dude, you don't see to many "screen captures" that show the computer rebooting and everything! lol
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Evo_Shift said:
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Click to expand...
Click to collapse
I had the SAME PROBLEM! I uninstalled the drivers, and chose from the list manually! Eventually you choose have disk and there is a long list of things. Find NVIDIA Fastboot from that list.
{
"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 swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Evo_Shift said:
I swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Click to expand...
Click to collapse
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
wwjoshdew said:
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
Click to expand...
Click to collapse
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
I finally got it. I am pretty sure it is because of incorrect adb drivers getting auto installed on me when I plugged in the Shield. I wish you could force Windows not to autoinstall drivers when you plug something in and instead always choose your own location. Once I deleted enough of the incorrect drivers and installed the correct drivers to the SHield again it seems to work.
1wayjonny said:
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
Click to expand...
Click to collapse
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
hmm...
I have only "Nvidia Shield" not Nvida Shield ADB in my devices Manager - adb is enabled
Code:
adb devies
List of devices attached
(none)
wwjoshdew said:
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
Click to expand...
Click to collapse
Had this issues so I installed the "manual" way and still commands wont work in fastboot
Edit: followed the video as opposed to the sceenshots above. Good to go now.
1wayjonny said:
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Click to expand...
Click to collapse
Is APX mode available on NVIDIA Shield? I've used APX mode before on my Notion Ink Adam (Tegra 2), but I have read that the OUYA (Tegra 3) has APX mode encrypted or something so you would have to know the key to use it.
Would be nice to have APX mode on the Shield, but probably not necessary.
~Troop
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.