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.
Related
for the past 18 months I have been able to access my G1 via USB. I could mount it easily and ADB was set up correctly. for some reason this week, it stopped working. now when I plus it in, I get the "USB Not Recognized" error in XP, and my device no longer shows up as an adroid phoen in Device Mgr. It now says unknown device.
I have tried updating the driver with no luck.
Any ideas would be great,
Thanks
Something similar happened to me. After trying to mess around with Live Wallpapers and DroidExplorer, my phone doesn't show up. I get the "Error: Device not found".
I have the latest USB driver, but yet device manager keeps saying that it's up to date when I try to reinstall (however under Driver Details, Vista says the location of the drivers are on System32 and they're Microsoft drivers....)
Edit: after searching Google for answers, I stumbled on a Google Group and found that someone fixed their issue (similar to mine) by installing HTC Sync. I did, and voila! ADB works again.
http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
OUTSTANDING!! That did it. Thanks a bunch, and thanks for the link!
fixed for real now
So the above didn't do it for me, here's what I did:
download and extract USBDeview
Open it up and remove the 3 or 4 entries that say "android phone"
Unlplug (if its plugged into USB) your phone and replug it in, the "found new hardware" window should pop up and be sure to install the drivers that came with the SDK.
That took care of my USB mounting situation, but I still couldn't get adb or fastboot to see my device. Turns out I had adb.exe and fastboot.exe in my WINDOWS/System32 folder as well as in the SDK/tools folder (prolly from when I updated the SDK). Having them in 2 spots seemed to cause problems so I removed them from the SDK/Tools folder. Alternatively I could have removed the other set, but I didn't want to go to my SDK folder every time to use them, this way I can access ADB from any folder on my computer.
This is all from memory so if something's not clear, lemme know. All I know is ADB and Fastboot are working now.
HI,
I've had success installing my other android devices on my windows 7 x64 computer, have even used my (ADB) Nook Colour on a windows 7 32Bit laptop fine.
Problem: Android Composite ADB Driver wont install/ isn't found, Device is Auto Nootered on 1.1 using rooted stock firmware.
Tried:
I have the .android folder in my user profile dir with the device ID in it
Followed various wikis and guides (that worked for the 32Bit version)
Watched the driver load/unload in device manager as I tick 'Development Mode (enable ADB)'
Tried various driver packs from here and googles latest offering, still only matches up with Android ADB Driver not the Composite (wont even show me the composite one)
Wireless ADB works and is disabled, worried about installing CWM using wireless for some reason USB feels safer to me
Thinks I noticed:
Hardware ID is listed as USB\VID_2080&PID_0002 which matchs up with %SingleAdbInterface% in the ini file for the driver, composite aka %CompositeAdbInterface% has &MI_01 on the end. Not sure if that means its not getting the right hardware ID from the device when ADB/ Development mode is enabled of if having the wrong driver loaded on it shows up the wrong Hardware ID.
Things I havent tried, enabling ADB on the Nook using sqlite3 method, but if it works on another coputer didn't think it would be a good idea.
Plan:
Install CWM, flash CM7 or similar to device.
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
ouldsmobile said:
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
Click to expand...
Click to collapse
Same here!
This one is weird...
I'm on win7x64 and I *have* got adb to work at times. When I was first rooting my new NC (1.1.0), I fiddled with it and I had it running over usb fine. But now, when I plug in the usb and I either get that the device is unrecognized or it goes into usb sync mode. Haven't quite figured that out...
But, ultimately, I just use adb wireless for any adb stuff, although it's "not recommended". It's worked perfect for me all along.
Check this link
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
loupnook said:
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
Click to expand...
Click to collapse
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
UR Welcome and USB Automount?
NewZJ said:
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
Click to expand...
Click to collapse
Glad to help. What do you mean USB Auto Mount? I kind of thought that should happen?
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I've installed DropBox but it keeps asking for an SD card, which isn't a big issue, just i haven't found the time to go buy one. Is there a way to use db without an SD card?
unfortunately no, db requires external storage. if you opened the apk to recode its default directory maybe but im not sure its possible
usb auto mount I can disable in nook tools but its a persistant system that defaults every reboot, I dont like to see it popup while using the nook when I plug it in just one of many peeves
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
GateheaD said:
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
Click to expand...
Click to collapse
I thought that as well and flashed back to the EC 1.0.1, sideloaded 1.1 update and repartitioned, used cw to add HC back and all that, and still had the same issue. Came down to the ini file not having a NookColor section.
Did you check the link http://forum.xda-developers.com/showthread.php?t=987409
I'm no stranger to drivers, I could force it to use the driver by changing the ini files but it still wouldn't appear in ADB Devices.
Flashed Nooky FroYo and now the device driver states the hardware ID has the missing '&MI_01' which means the composite driver works out of the box.
I used IOMonsters Easy USB installer and it seems to have installed the drivers for Windows 7 64Bit Fine
After running the install .exe I also had to execute the Inst64.exe
Hello
Im brand new to Android and adb/fastboot.
I have looked at tutorials on youtube all day, and for everybody else their devices just pops up when you type adb devices.
I get nothing
I have done it correctly, because I get all the commands when I type adb/fastboot.
Im running windows8, could that be the problem?
Do I need some kind of extra USB drivers for my google glasses?
I do find my glasses as a camera tho.
EDIT:
So after watching a few more tutorials I understood my problem. Its windows8 usb drivers thats not correct.
I have tried to install correct drivers and edit the .ini files that need editing, but now I encountered a new problem.
Windows wont let me install correct usb drivers for google glass.
When I have device manager open, windows have already installed them as “Portable device – Glass1″
I click uninstall and they disaper from my device list, once I click “scan for new hardware” I can see that they reapper on my device list as other devices. Within 2sec windows autoinstall them as “portable device -glass1″ again.
So I try “update driver software” but this dont work either, I select the correct file and path, but I keep getting this message “windows has determined the driver software for your device is up to date”.
Im running windows8.
Any help is appreciated.
EDIT2:
As far as all the tutorial movies tell me to disable driver signing I have done so.
If all of the adb commands were working, then chances are you need to enable debugging on your Glass. Settings >> Device info >> Turn on debug
Update:
The way to bypass windows8 and installing usb drivers, is that I need to use the option "Have Disk" and then install usb drivers that way.
All works fine now.
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.
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.