Database Users

[Q] trouble installing adb USB drivers on windows

I am attempting to root my HTC Panache (MyTouch 4G) with this guide.
The problem is with the first step which is installing adb and the USB driver. The guide referred to the cyanogenmod wiki on installing the android SDK. I believe that I followed all the instructions correctly but it does not show that my drivers are installed properly in windows device manager and CMD.
{
"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"
}
So here is the entire process that I took:
installed java sdk exe
downloaded Android SDK zip file and extracted to root C:\
opened SDK Manager
installed "Android SDK Platform-tools, revision 6" (revision 4 not available) and "Google USB Driver package, revision 4" packages in SDK manager
went into control panel > system > advanced settings > environment variables > double clicked "Path" > added ";C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools"
downloaded and replaced the default "android_winusb.inf" file with the modified file from the cyanogenmod wiki
enabled "USB debugging" and ensured USB was in "charge only" mode in phone
opened CMD and typed in "adb devices", didn't show anything
opened windows device manager and found an "Android Phone" device with the yellow exclamation mark instead of "Unknown Device" with ADB listed under it as mentioned in the cyanogenmod wiki
right clicked and update driver software, clicked browse and located the "C:\android-sdk-windows\extras\google\usb_driver" folder with the modified .inf file
"Windows was unable to install your Android Phone"
I've been trying many things for hours so any help would be appreciated! Thanks in advance.

Try these drivers...
http://www.multiupload.com/HBVGRC92IP

Ace42 said:
Try these drivers...
Click to expand...
Click to collapse
Success!
All I needed to do was install the .exe you gave me, restart the computer, device manager > right-click the unknown android phone device and "scan for changes", then the driver automatically installed! confirmed with cmd > adb devices.
Thank you!

qayum said:
Success!
All I needed to do was install the .exe you gave me, restart the computer, device manager > right-click the unknown android phone device and "scan for changes", then the driver automatically installed! confirmed with cmd > adb devices.
Thank you!
Click to expand...
Click to collapse
Np, the generic drivers normally don't install anyway, have to use the htc ones instead.

Ace42 said:
Np, the generic drivers normally don't install anyway, have to use the htc ones instead.
Click to expand...
Click to collapse
Off-topic but, another problem.
I've successfully generated the CID with SimpleGoldCard but it seems that the gold card IMG generator website psas.revskills.de/?q=goldcard is down.
Will it be online again? Is there any other way to get the IMG file?

qayum said:
Off-topic but, another problem.
I've successfully generated the CID with SimpleGoldCard but it seems that the gold card IMG generator website psas.revskills.de/?q=goldcard is down.
Will it be online again? Is there any other way to get the IMG file?
Click to expand...
Click to collapse
I have no clue what the gold card is really, I last heard about it when people were rooting the magic. Since you mentioned CID, are you trying to unlock the phone fir other carriers ?

Ace42 said:
I have no clue what the gold card is really, I last heard about it when people were rooting the magic. Since you mentioned CID, are you trying to unlock the phone fir other carriers ?
Click to expand...
Click to collapse
No, I do not need to unlock it. The phone is from my carrier Mobilicity, but people referred me to use the Videotron HTC Panache guide (link to thread in OP) because it has a newer ROM version and making a gold card allows to "flash RUU files with a different CID to your own device - in other words, it allows you to flash files that were not made for your phone."
Basically, there was a back-to-school sale on the HTC Panache from Mobilicity and people who wanted to root (and unlock) it followed the guide above.
Please give me any suggestions, thanks!

Odin is not recognize by my phone since CM 10.1 been installen on my phone
Good day!
Since Cyanogenmod 10.1 nightly been installed on my phone, Odin does not see the phone anymore even is the USB debugging is active on the phone. I am able to see the phone using the command ADB devices -l. I need Odin back because I want to put back the stock firmware on my phone which is Jelly Bean 4.1.2. from Virgin Mobile.
Can someone tell me why ADB can see my phone and not Odin?
Thank you!

[GUIDE] Fix ADB USB driver for Rockchip RK3066 - Ployer Momo7 Dual Core

I am struggling to make my USB debugging works for Momo7 dual core with RK3066 chip. This is what I found to make it works at least for my Windows 7 64bit. This should be the same with other RK3066 devices also.
1. Install ADB driver
After connect to USB (make sure USB debugging enabled and don't mount the mass storage device) You will find that MOMO7 is not recognized in the Device Manager. The simple way is to install Moborobo, it will find and install a driver for you.
If you dont want to install Moborobo, you can use standard adb driver comes from SDK but you need to edit the android_winusb.inf file to add
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
in both Google.NTx86 and Google.NTamd64 area.
For other model and manufacturer, just change the VID and PID which you can get from Device Manager > Properties > Details > Hardware Ids.
2. Use suitable ADB
Using adb from Android SDK is not working for some/almost RK3066 device (I think). I tried a few adb embedded from the other application like SuperOneClick but not working. No device found if you run "adb devices". I almost giveup but suddenly adb from ROOT.bat here contain is the only adb that can see my device.
Credit goes to bindassdost to point to the adb in the first link here
and yuvarajv to mentioned the adb embedded in root script contain ROOT.bat here

Root Momo7 & Momo8 Dual Core
The Momo7 & Momo8 using RK3066 can be root by using a Chinese program ZhuoDaShi. http://www.dashi.com/

Thank you for posting the solution for adb. I am using Cube U9GT4 tablet. I was also having the same problem of device not getting listed. But now I am able to use the adb.exe from your zip. Thanks again ... :good: :good:

Thank you. This worked for my MINIX Neo G4 with an uncommon pid.
btw, you needn't install the sdk or usb drivers at all or go through that driver modding thingy, the pdanet drivers also work out of the box

thank you very mutch !!! it works for me and my rk3066 China tablet !!! now ADB work

Thank you, it worked with Qware TB-1517 :good: (RK2926)

had very similar problems with the timingpower Mini PC RK3066. I could not get the USB driver to install no matter what I tried (Win 7 both 32 and 64 bit)
Moborobo worked for me but I did not like the way it installed (and kept installing) Moborobo apps on my device - particularly as it had access to a rooted device under adb.
I will now do a full reset, restore my original ROM and try the alternative adb method described in the first post.
I am probably being over cautious but you can't be too careful these days!

htc6500uk said:
had very similar problems with the timingpower Mini PC RK3066. I could not get the USB driver to install no matter what I tried (Win 7 both 32 and 64 bit)
Moborobo worked for me but I did not like the way it installed (and kept installing) Moborobo apps on my device - particularly as it had access to a rooted device under adb.
I will now do a full reset, restore my original ROM and try the alternative adb method described in the first post.
I am probably being over cautious but you can't be too careful these days!
Click to expand...
Click to collapse
Hi there.
I've found another way by installing the Rk30XX driver from BQ, :
https://s3.amazonaws.com/Drivers/ADB_drivers_RK30.rar
1- Extract the folder and you will have a folder "bq edison" with two folders inside (tools and usb_driver).
2- Unninstall previous drivers and install the usb_driver from this folder, using device manager.
3- Go to folder tools, that contains patched files (adb and dll's) and copy them. Take note to their names
4- Now go to the SDK_FOLDER\plataform_tools\ and backup the files with the same name that you copy on step 3 (just rename them... to something like adb.exe.bck)
5- Now copy the files and open a terminal, perform 'adb kill-server' , 'adb start-server' and 'adb devices' will show your ID device .D
This worked with a RK30XX device as well my Denver TAC70071 with an RK2928 chipset , since the USB vendor id and pid is present on the driver.
PS.: Sorry for my poor english

It works!
Dimitrico said:
Hi there.
I've found another way by installing the Rk30XX driver from BQ, :
(URL deleted, use above)
1- Extract the folder and you will have a folder "bq edison" with two folders inside (tools and usb_driver).
2- Unninstall previous drivers and install the usb_driver from this folder, using device manager.
3- Go to folder tools, that contains patched files (adb and dll's) and copy them. Take note to their names
4- Now go to the SDK_FOLDER\plataform_tools\ and backup the files with the same name that you copy on step 3 (just rename them... to something like adb.exe.bck)
5- Now copy the files and open a terminal, perform 'adb kill-server' , 'adb start-server' and 'adb devices' will show your ID device .D
This worked with a RK30XX device as well my Denver TAC70071 with an RK2928 chipset , since the USB vendor id and pid is present on the driver.
PS.: Sorry for my poor english
Click to expand...
Click to collapse
Hi Dimitrico,
This works with my DFP1008R china noname tablet with RockChip RK2918 and Android 4.0.3 too!
Tried lots of ADB drivers, but the key is special adb.exe from this pack!

how to avoid windows 8.1 security warnings ?
{
"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"
}

Thanks, Finally got ADB working on my JXD 7800.
I kept thinking it was the driver turned out to be the ADB build.. what makes this one special?
eh.. anyway now how do I get fast boot running? anyone know of a special build of that?

I suggest use auto installer for win 7/8
http://minix.com.hk/downfile/RK_DriverAssitant.zip
for rooting "Uberizer":
http://www.techknow.me/forum/index.php?board=154.0

Restored Hard-brick But Still Some Problems...

So my xiaomi m2s was bricked pretty bad, I couldn't even enter the recovery. So I followed this thread and restored my phone by installing the 'aries_images_4.11.21_4.1_cn' fastboot package. So when my phone finally booted up I noticed some problems I also had prior to this brick. My sdcard storage couldn't be mounted, not in the ROM and neither with an usb cable. I tried, for example downloading something but always got an error. When I go to fastboot and try to flash m11kkaa's flashtools with miflash, I always get this error:
{
"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"
}
This happens with all fastboot packages by the way, not only m11kkaa's. And I've tried this on 3 different computers with each having the windows driver signature enforcement disabled on boot.
So my question is: Is my phone DEAD?

infinitely said:
So my xiaomi m2s was bricked pretty bad, I couldn't even enter the recovery. So I followed this thread and restored my phone by installing the 'aries_images_4.11.21_4.1_cn' fastboot package. So when my phone finally booted up I noticed some problems I also had prior to this brick. My sdcard storage couldn't be mounted, not in the ROM and neither with an usb cable. I tried, for example downloading something but always got an error. When I go to fastboot and try to flash m11kkaa's flashtools with miflash, I always get this error:
This happens with all fastboot packages by the way, not only m11kkaa's. And I've tried this on 3 different computers with each having the windows driver signature enforcement disabled on boot.
So my question is: Is my phone DEAD?
Click to expand...
Click to collapse
Connect with usb cable and boot to recovery.In cmd "adb reboot dload" .Now you can flash a miui fastboot package with miflash.

T3sla said:
Connect with usb cable and boot to recovery.In cmd "adb reboot dload" .Now you can flash a miui fastboot package with miflash.
Click to expand...
Click to collapse
I don't get an adb connection with my computer. This was also a thing I had prior to this brick... It seems like my phone cannot communicate with my computer (except for the pin shortcut method and regular fastboot).

infinitely said:
I don't get an adb connection with my computer. This was also a thing I had prior to this brick... It seems like my phone cannot communicate with my computer (except for the pin shortcut method and regular fastboot).
Click to expand...
Click to collapse
Try these.

T3sla said:
Try these.
Click to expand...
Click to collapse
I gave this a try, even though I already had the latest platform-tools installed through android studio > SDK manager. Anyway this little installer puts it in C:/adb. It didn't work either. This is what I always get:
This is what my driver looks like in windows when I connect in fastboot:
EDIT:
I seem to have gained a working sdcard again by flashing m11kkaa's 'aries_core_recovery_single' package through fastboot (pin short circuit method) but I still have no connection with my computer through USB. The only way I can transfer files to my phone are through FTP.

infinitely said:
I gave this a try, even though I already had the latest platform-tools installed through android studio > SDK manager. Anyway this little installer puts it in C:/adb. It didn't work either. This is what I always get:
This is what my driver looks like in windows when I connect in fastboot:
EDIT:
I seem to have gained a working sdcard again by flashing m11kkaa's 'aries_core_recovery_single' package through fastboot (pin short circuit method) but I still have no connection with my computer through USB. The only way I can transfer files to my phone are through FTP.
Click to expand...
Click to collapse
I had a similar problem, i tried installing and uninstalling drivers with no luck.I concluded that something with the driver or windows files was wrong and could not fix it so finally i made a fresh install of windows and everything is fine now.?I know it's not the easiest thing to do so you can try first on a different pc to check if the problem is with the phone or your pc.

T3sla said:
I had a similar problem, i tried installing and uninstalling drivers with no luck.I concluded that something with the driver or windows files was wrong and could not fix it so finally i made a fresh install of windows and everything is fine now.?I know it's not the easiest thing to do so you can try first on a different pc to check if the problem is with the phone or your pc.
Click to expand...
Click to collapse
I've tried the same on a clean installed windows 7 in VMware, got the same result:
The driver looks different though:
I have also checked with google's adb driver installer but it doesn't find any attached devices.

infinitely said:
I've tried the same on a clean installed windows 7 in VMware, got the same result:
The driver looks different though:
I have also checked with google's adb driver installer but it doesn't find any attached devices.
Click to expand...
Click to collapse
If it's not working on the host machine then it doesn't on the virtual installation on vmware.I tried that too.You can make a backup of your current windows installation and then try a clean install and see if it's working.Or you can try on another machine.

T3sla said:
If it's not working on the host machine then it doesn't on the virtual installation on vmware.I tried that too.You can make a backup of your current windows installation and then try a clean install and see if it's working.Or you can try on another machine.
Click to expand...
Click to collapse
Wouldn't it be a hardware issue then? Lol...

infinitely said:
Wouldn't it be a hardware issue then? Lol...
Click to expand...
Click to collapse
How can be a hardware issue if after a clean windows and adb drivers install it's working fine?Lol...

T3sla said:
How can be a hardware issue if after a clean windows and adb drivers install it's working fine?Lol...
Click to expand...
Click to collapse
I was talking about the computer. Anyway, I doubt that will fix my problem since I have already tried it on 3 different computers and it was always the same outcome...

kingroot infected?

Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?

loganwaffle8 said:
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
Click to expand...
Click to collapse
see rootjunky's supersume video
https://www.youtube.com/watch?v=3O3DcpeS_Ic
or manually install supersu with a terminal emulator
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Ill try the rootjunky method in a few hours, I tried the terminal emulator installed and it just forceclosed all apps and rebooted.
Sent from my KFTBWI using XDA Labs

So I got a bit impatient, and decided to retry the w0lfdroid method. The same thing happened from last time (apps wouldnt open) and so I decided to reboot.
As the device began to shutdown, SuperSU appeared for a few seconds, then my device switched off. I believe I have bricked my device as it has been stuck on the 'fire' logo for the past 10 minutes. Congrats to me ._.

I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?

loganwaffle8 said:
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
Click to expand...
Click to collapse
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing or XDA
extract files
run KindleDrivers.exe
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"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"
}
Sent from my KFFOWI using XDA Labs

Thanks
Have I done it right? I hope I've done everything. Also when I open ADB a load of text flashes down the cmd box for about a second then it closes. Ran as administrator and everything. Hoping I can get this fixed by the weekend...

Ok, I think I got it.
Doing adb devices gives me G000HH0454340LB9, I beleive this is the correct device?
Anyways, plan is:
Boot into recovery on device and select apply update from adb
Get the 5.1.1 update (firmware it originally had) and place it in the folder adb installed in.
Do adb sideload (file name)
Wait (maybe grab a cup of coffee?)
Hopefully success, back to stock firmware!
Afterwards ill root with kingroot and then remove using rootjunky supertool.

Ok, this is getting kinda annoying.
Placed the update-kindle-32.5.4.1_user_541112720 .bin file in the same folder I have adb installed.
Booted devices into recovery mode, selected apply update from adb
Open adb, do adb sideload update-kindle-32.5.4.1_user_541112720
Get error message 'cannot read update-kindle-32.5.4.1_user_541112720'
Have ALL correct drivers and stuff installed @sd_shadow

Can anyone help? I really need this fixing...

loganwaffle8 said:
Can anyone help? I really need this fixing...
Click to expand...
Click to collapse
try downloading the firmware again, or try a different version like 5.1.2
which version is on it now?
Sent from my KFFOWI using XDA Labs

The version on my device before it was bricked is 5.1.1. I'm staying on that version since its the easiest to root.

[Guide] Fix for device not working in fastboot / unable to install official driver in Windows 10 / 11

If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"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"
}

Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much

Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.

anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com

in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.

I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.

I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance

Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.

Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.