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] adb and fastboot drivers for Windows

If someone has problems installing the official Motorola adb and fastboot drivers for Windows, try the following, this works for me:
1. download the UniversalADB driver from @Koush here: https://github.com/koush/UniversalAdbDriver
2. install it
3. locate the file android_winusb.inf in the folder (may vary) x:\Program Files\ClockworkMod\Universal Adb Driver\usb_driver
4. open it with any texteditor
5. add the following two lines (somewhere in the devices section) and save the file:
Code:
MotorolaADBInterface = USB_Install, USB\VID_22B8&PID_2E76&REV_0228&MI_01
MotorolaBootLoaderInterface = USB_Install, USB\VID_22B8&PID_2E80&REV_0100
6. let Windows install this driver from koush's directory once in adb mode and once in fastboot mode (two drivers!)
7. enjoy!

Work fine thanks

Is the phone recognized by RSD Lite in fastboot mode with these drivers?
I have the Motorola drivers, using Windows 7 SP1 32-bit.
With USB debugging enabled I get a "Mot Composite ADB Interface" device in device manager (Driver Version 2.0.1.0).
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
{
"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"
}

t-bon3 said:
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
Click to expand...
Click to collapse
Got the same with the universal ADB/fastboot drivers damn.
[edit]
The MotoG PID is missing in PST.ini and/or sdk_common.ini, maybe we have to add it manually or wait for a new RSDlite

hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )

Worked great. Thank you

maty3ux said:
hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )
Click to expand...
Click to collapse
Not yet, last version is 6.1.6

I do not understand this instruction:
shaftenberg said:
let Windows install this driver from koush's directory
Click to expand...
Click to collapse
Windows doesn't attempt to do anything when I connect the phone in ADB mode. Device Manager lists XT1034 under Other devices and says "The drivers for this device are not installed. (Code 28)". If I do "Update Driver Software" manually and direct it to the "ClockworkMod" directory, Windows says it cannot find driver software for the device. If I right click on the "android_winusb.inf" file and choose Install, Windows says the "file doesn't support this method of installation".

adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated

The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.

Thank you!!
it works for me
i installed Motorola device manager and this application
reversegear said:
The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.
Click to expand...
Click to collapse
that's right .. i didn't do that too and it works

I've tried this and when I try to install it, it says "The INF file you selected does not support this method of installation." What do I do?

Didnt work for my moto g
sir, i am really new at this backup thing.
i just want to backup my injustice save game, so that i can restore it to previous point if something goes wrong.
i downloaded latest version on universaladbdriver but still my laptop didnt recognised my MOTO G.
i want to use HELIUM/CARBON for backup and i cant proceed till this problem is removed
please help me, i am new to xda as well.
THANKS
my os is win7 32 bit

hey
same problem i cant install adb or motorola drivers in my pc windows 7 64bit. the links with drives dont work for me..any solution? i want to unlock my bootloaderrrrrrrrrrrr :silly::silly::silly: (when i start to install the adb drivers stuck )
https://www.youtube.com/watch?v=RDA8PpPSFuk here i found solution for me i hope u help guyz(turn the music off )

Gronnd said:
adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated
Click to expand...
Click to collapse
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..

nuri-d said:
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..
Click to expand...
Click to collapse
To solve this when u are in ADB go in device manager, find ur phone with yellow exclamation mark ( !), right click, insta driver-> manual-> android single sooner ADB interface! It will work like a charm!
Sent from my XT1032 using XDA Free mobile app

I had a similar problem on W7 x64, no driver available for my phone (Moto G LTE, XT1039) even with the Universal ADB driver from CWM and the two lines of the first post added in the INF file.
But, you can notice that all Motorola phones in the android_winusb.inf file refer to the same driver : MotCompositeInterface.
So I went to the Device Manager, found my phone, chose to Update the driver, Find a driver from my computer, Choose from List (sorry if the names are not accurate, my Windows version isn't in English).
Then, you can select ClockworkMod, scroll down to Mot Composite ADB Interface and choose it as your driver.
It worked for me (both in adb and fastboot mode), I was able to unlock my bootloader and flash a recovery using it.
Hope this helps !

Hi, I tried all the solutions in this post unsuccessfully, but I found one here: stackoverflow.com/questions/22217792/android-moto-g-mobile-doesnt-show-in-the-devices-list-of-eclipse
that is the simplest and the only one that worked for me.
Download 'Adb Driver Installer' from here adbdriver.com/downloads/
after this connect your Moto G and start the AdbDriverInstaller.exe it will list your device and then press install.
Click to expand...
Click to collapse

ADB driver connection

Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?

rayjr13 said:
Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?
Click to expand...
Click to collapse
Yes but I know if you update to Windows 10 it can cause issues you need to reinstall moto drivers
Sent from my XT1585 using XDA Premium 4 mobile app

My Turbo 1 connect just fine not T2 I'll try it again when the wife brings it back

I had a small issue. I think mine cleared up when I installed Vysor, and installed the drivers through that.
http://koush.com/post/universal-adb-driver
Give this a shot and let me know how it goes. btw, Vysor is pretty fun.

Solution update (2017-2018 version) for recent Ubuntu-based Linux and Windows 10
(NOTE: I am unable to post complete URLs due to having an insufficient number of XDA Forum posts at this time. The bulk of this post and the information contained within is available by searching for my GitHub account (maxieds) and selecting the most obvious pinned repo description. My GitHub page is also linked off of my XDA Forum profile just to be clear. )
Preface: I realize that this thread is somewhat dated, but so is this antique 2015-era phone, so I figured it's worth pointing out a recent solution to those patient Google searchers who like me are still using the device. This solution (works for me on a recent 2017 Debian-derivative Linux box, and/or a loaner Windows 10 laptop) is to avoid the proprietary Motorola software and drivers you will stumble onto from the official ADB links from Android Studio. All you need is the standard Google USB drivers and a more recent list of phone USB device ID properties. I haven't tested, and so cannot confirm, but I suspect that this method should get ADB up and functioning on other hard-to-configure deviant phones using the list of Linux udev supported configurations from this recent (and often updated): <GITHUB>/M0Rf30/android-udev-rules. My modification for the DROID TURBO 2 phone is forked <GITHUB>/maxieds/android-udev-rules. If you find this information helpful, I'd appreciate it if you would STAR my repo on GitHub (<GITHUB>/maxieds/android-udev-rules/stargazers). As a variant of the the old Unix joke goes in obscure 20-year-old Slashdot references: How do we fix Windows? ... Well, I propose we port WINE to Windows ... With this in mind and in this spirit, let's port the oh-so-wonderful Linux UDEV config to Windows.
NOTE: the DROID TURBO 2 didn't work out-of-the-box on Ubuntu either however, even after installing other variants of the udev rule sets, so my mod is necessary to fix at least this stubborn class of Motorola devices. One possible explanation for why this device doesn't work like nearly every other Android phone is a USB3 bug where file explorer, etc. works on the same USB port, but ADB fails. The purported non-software work around is to chain the phone's USB connection in serial to a cheap self-powered USB hub that effectively masks this bug, but I had no such luck with this experimental fix and of course your mileage may vary. More likely, the cause is that the phone preempts the typical detection sequence by changing the id of it's ATTR{idProduct}=="2ea4" to ATTR{idProduct}=="2ea5" (or some other related ID) when it is connected through USB debugging for use with ADB. See the following image detailing the respective dmesg and lsusb changes pre/post enabling USB debugging on a device connected via USB in Linux:
{
"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"
}
===== Ok, so here, goes with the updated device details: =====
Recent (2017,2018) Solution for Using the DROID TURBO 2 Phone with ADB:
Recently, I finally got into Android development using my Motorola DROID TURBO 2 phone ... only to find that the phone isn't recognized out-of-the-box on either Linux or Windows. After searching around for a while, I finally have found a solution on Linux, which I then "ported" to Windows 10 using the stock Google USB drivers which are easy to find and install with Android studio. The solution is essentially this:
on Linux (after installing Android Studio / ADB / Android Tools in Ubuntu):
Use this updated udev file to get the TURBO 2 recognized: <GITHUB>/maxieds/android-udev-rules. The working forked file basically required setting a few non-standard udev options and inputting the complete device spec found with
Code:
lsusb
LSUSB Outputs: Bus 001 Device 0XX: ID 22b8:2ea5 Motorola PCS, where the XX is a decimal integer local to the running linux box
Click to expand...
Click to collapse
. After following the instructions at the referenced link, running
Code:
adb devices
from your favorite terminal should display the device. Now happy ADB and Android debugging to you and your ancient phone! (AND please be sure to STAR my repos!)​
in Windows 10 (Enterprise): First, install the Google USB Driver using the SDK manager in Android Studio (under Extras). This puts the driver files in (on my local text box) "Program Files (x86)\Android\android-sdk\extras\google\usb_driver\*". I had to right-click, install and enter the administrator password for the local box to install this. At this point, you can open up "Computer Management > Device Manager" (as ROOT) and see if your phone is automatically recognized by the stock Google USB driver. Mine is not, so we have more work to do. From the GitHub repo (<GITHUB>/maxieds/AndroidADBExtraUSBConfig) I have created, copy the two files under android_google_usb_driver_mod into the default folder for the Google USB Driver files (linked on Windows 10 as above). Repeat the process to install the driver.
Hopefully, now you can get the Motorola DROID TURBO 2 device up and developing with ADB and Android Studio! :good:
---------- Post added at 09:40 AM ---------- Previous post was at 09:32 AM ----------
Since I was unable to post the links to the GitHub repos relevant to the recent solution to this problem, maybe this will get past the XDA Forum filters. Here's a QR-Code to the Wiki page on my repo where you can find complete information and files for implementing the custom USB setup needed to get the DROID TURBO 2 phone working out-of-the-box with ADB under Android Studio: <img src='https://chart.googleapis.com/chart?cht=qr&chl=https%3A%2F%2Fgithub.com%2Fmaxieds%2FAndroidADBExtraUSBConfig%2Fwiki%2FFirstBootConfigurations&chs=180x180&choe=UTF-8&chld=L|2' alt=''>. A link to the original image file (which should have been displayed in the above post) using the repo site is also provided as follows: <img src="https://github.com/maxieds/AndroidADBExtraUSBConfig/blob/master/images/idproduct-discrepancy-illustrated.png" alt="" />.

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.