Database Info

[Q] Nexus S Root-Windows requests 'Android 1.0' hardware driver (and other weirdness)

Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.

Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928

webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!

haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!

bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders

The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.

jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.

I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid

I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!

Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!

Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S

Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App

Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"

When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work

matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!

thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App

matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!

I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box

[Q] ADB no devices

Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.

Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.

ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.

Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?

it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it

ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim

ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.

davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.

enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.

Unable to copy files to Nexus 5

Please help.
I have rooted and installed SuperSu and TWRP on my device.
I tried to connect my phone to my computer, it gets detected and drivers are installed.
When I cannect it as MTP, the drive on the phone does not appear on my coimputer. When I change to PTP, it appears as camera. But I can't copy files to it.
I have tried with another computer with the same result.I have rebooted the computers and I also reset my phone which didn't help.
What am I doing wrong?
Thank you

xdm9mm said:
Please help.
I have rooted and installed SuperSu and TWRP on my device.
I tried to connect my phone to my computer, it gets detected and drivers are installed.
When I cannect it as MTP, the drive on the phone does not appear on my coimputer. When I change to PTP, it appears as camera. But I can't copy files to it.
I have tried with another computer with the same result.I have rebooted the computers and I also reset my phone which didn't help.
What am I doing wrong?
Thank you
Click to expand...
Click to collapse
enable adb in developer options and then connect to your pc, that fixed connection for me

thenobol said:
enable adb in developer options and then connect to your pc, that fixed connection for me
Click to expand...
Click to collapse
if you mean usb debugging, I have already done that...

xdm9mm said:
if you mean usb debugging, I have already done that...
Click to expand...
Click to collapse
Do you just not see the device within you folders? Might be a driver issue, I had some problems with that initially.
Also, I had issues trying to transfer pictures/videos from my PC to the phone as well. IT would start the transfer but started crashing a few times before I was able to transfer everything over successfully. But that might just be a Win 8.1 compatibility or driver issues as well.

skyo12 said:
Do you just not see the device within you folders? Might be a driver issue, I had some problems with that initially.
Also, I had issues trying to transfer pictures/videos from my PC to the phone as well. IT would start the transfer but started crashing a few times before I was able to transfer everything over successfully. But that might just be a Win 8.1 compatibility or driver issues as well.
Click to expand...
Click to collapse
Yes I don't see the device. Maybe it's caused by the old Nexus 4 drivers.. anyway I uninstalled "Android Device" from my computer's device manager, unplugged the phone, then it miraculously installed the drivers... I'm copying mp3's to my phone now.
Thanks

Sounds like a driver issue. Google "Android naked usb drivers" those worked well for me

[Solved] USB suddenly stopped working

I have a Nexus 5 that I have had about a month now and I had the USB on it working before about a week ago. I plugged it in today and neither my desktop or laptop could recognize it anymore. Both computers are running Windows 8.1.1 and the issues seems to be new as I can neither get USB storage or ADB to find it. The closest I can get it to working is to switch the USB mode to PTP and it reads that but I don't want to pull photos off. When I have it in MTP, it makes the sound of it plugging in and my phone shows it is plugged into a computer but Explorer shows nothing and it says it is working normally in device manager. I've tried everything from enabling and disabling debugging, restarted both my phone and computer tried reinstalling the drivers (both by the computer automatically finding them and manually installing them) but nothing seems to work. Is it possible that Windows Update could of broke the drivers since my computer installed updates yesterday? I also have Linux on my laptop and it appears to read fine with Linux.

That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA

EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
OK thanks. I'll give it a try because it was showing up as ACER ADB Device under device manager
EDIT: I updated the drivers and used the USB composit drivers instead and it got MTP working again. When I set it to USB composit, it installed Google's ADB drivers and the Nexus 5's USB drivers so everything is working again. Thanks for your help

EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
I can´t manually update driver because of this:

when i update the acer adb it says the driver is up to date and everything is all same. what to do?

Thanks! Thought I was going to go crazy. Worked for me...

i set the driver to MTP as mentioned above and the phone started to show up on the explorer but now i couldnt copy any files from my laptop to the
phone. It displays like that and if clicked yes then the copy wouldnt happen.what is the problem.

Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.

wangdaning said:
Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.
Click to expand...
Click to collapse
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.

Big tree said:
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.
Click to expand...
Click to collapse
That msg comes when you're in PTP mode I think...Only certain formats are supported.
Check under storage, expansion menu and make sure you are set to the first option...not PTP.
Above guy mentioned to have phone in USB debugging mode when setting up drivers.

If the device is showing then you need to point to the drivers for it (download them from google). I reinstalled windows a few days ago and had the acer issue (device first shows up in device manager as nexus 5 then switches to acer), windows wants it to be an acer device. Stop windows and then install the correct drivers,
For me I had to click the auto install in windows tray and tell it to stop. After a few times it worked.

No I'm connecting in MTP mode. Ahh its gettn irritating.

Question Phone not detected by PC

A couple days ago my mobile data just stopped working. I had a couple updates I had been ignoring because it would remove the root. I finally gave in and ran the updates. Data returned. Root gone. I connected to my home computer to begin the root process, but my phone would not be recognized by the PC and would not show anything related except that it was charging. It's a new cable, barely used. I tried on my work computer with a different cable and still nothing except "charging". To the best of my knowledge, it connected to my computer just fine prior to the updates.
I've checked Developer Options for anything that says "USB". Toggled USB debugging, revoked authorizations, etc. "Select USB Configuration" is a weird one, all I have are: "Charging", "MTP", "PTP", RNDIS (USB Eathernet)", and "MIDI". But in "Default USB Configuration" I have: "No data transfer", "File transfer / Android Auto", "MIDI", "PTP", "USB tethering". I've selected every option, but (again) no reaction from my phone or PC.
My final options are wipe and reset, or take it to a store; I'm wanting to avoid both of these if possible. Does anyone have an idea of what else I can try?

Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?

IamTheBRAVE said:
Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?
Click to expand...
Click to collapse
I'll take a look at that tonight.
To answer your questions, phone boots and everything else seems to operate just fine. Just checked and boot screen says "Orange State Your device has been unlocked and can no longer be trusted", then like 30 seconds later it boots. It no longer has root after the updates and the only way I know to do it is through adb and fastboot commands. But also I backup my photos to my home PC when it gets pretty full. Also, also I occasionally do mobile development at home and test things on my phone.

The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.

IamTheBRAVE said:
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
Click to expand...
Click to collapse
Ya, I wasn't too worried about the bootloader message, just being thorough. I'll try the android folder at home also, but for what it's worth I don't have anything android-related on my work computer and it doesn't connect either.
Both are Win10

In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?

IamTheBRAVE said:
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
Click to expand...
Click to collapse
Phone doesn't show anywhere in Device Manager, and no yellow triangles. IIRC, drivers were installed by my phone when I plugged it in at home. I actually don't remember the last time I plugged into my pc at work before now.

Then look for your brand's android drivers and install them. I think that's the issue. Plugging the phone alone would install generic android drivers not your specific ones.

Short version: Nothing worked.
I had already tried searching for "oneplus 9 drivers". The main site doesn't offer anything, so there are a couple search results that really feel like scam sites. But they're the top results, so maybe I'm wrong. I installed the results from the search, and also searched xda and the one result I found.
I downloaded the ISO for mAid. Ran it in a VM. I couldn't really figure out what to do in it to troubleshoot. I was also discouraged because if my computer won't recognize the device, then why would the device show up in a VM?
I found and removed adbkey and adbkey.pub from "Users\<me>\.android\".
I had a brief bit of hope. I doubt the drivers caused it, so I'll probably remove those again. I got the device to appear in Device Manager but with a yellow triangle. It only seemed to happen when switching between "No data transfer" and "File transfer / Android Auto". The device was displayed as "Unknown USB Device (Device Descriptor Request Failed)". I doubt that provides much help though.

Have you tried clearing out the dust bunny's in the usb port on phone?

Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com

MrSteelX said:
Have you tried clearing out the dust bunny's in the usb port on phone?
Click to expand...
Click to collapse
Yup. Folded some paper after the previous stuff. A little bit came out, but not so much that I'd think it's the issue. I have a floss stick thing, but it was a bit thicker and was moving the piece inside the slot.

IamTheBRAVE said:
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com
Click to expand...
Click to collapse
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds

tconn said:
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
Click to expand...
Click to collapse
Took a look on OP9 forum, doesn't look like there is one. We have that on OP9Pro. Here's a link to the drivers, should work for you i think.
10.26 MB file on MEGA
mega.nz
You can use this thread as tutorial for root (you don't need all parts of it)
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com

"Device Descriptor request failed" tells you that the very first step of USB enumeration failed.
So you're talking about flakey cable, bad connection, interference OR the device was not initialized properly.
So try different ports, different computers, something different.
The first step is getting it to the point where it connects solidly (even if it can't/won't find a driver).
Unfortunately you can't tell Windows to use common sense and install a WinUSB driver. That's why we have Zadig: https://zadig.akeo.ie/
Unfortunately (again), adb.exe expects the correct DeviceInterfaceGUID. Ok, you can patch adb.exe or you can use Zadig with a custom .cfg file to specify the DIGUID.
Here is an example .cfg file. You'll have to fill in the VID/PID/MI if you ever get your phone to connect solidly and you can see that info in the DeviceManager.
So, go to Zadig, select Device > Load Preset File, select Options > List all devices, find your device and hit install.
Code:
[device]
Description="Standard Google Device"
VID=0x18d1
PID=0x4ee7
MI=0x00
GUID="{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}"
Good luck.

Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!

tconn said:
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
Click to expand...
Click to collapse
Try using a toothpick. Just try not to bend port too much.