Database Users

[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

[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="" />.

[Tut][Easy] Recover lost IMEI of your Yureka/+

Hello Guys! Yesterday I was experimenting with my Yureka and accidently I lost IMEI of my phone. I searched YuPlayGod as well as XDA. There are some methods to recover/restore/change IMEI but unfortunately they are not working or they are too difficult to follow for a normal user. I kept searching for the solution and finally came to this. This work is not mine and the credit goes to the respective authors. I just have wrote this tutorial for the reference!
Beware: Changing IMEI is illegal. This tutorial is for those who are having their valid IMEI and have accidently lost during flashing or recoving from a brick. Please refer to your country law for the same.
**Although this tutorial is fully tested as I just have recovered my IMEI, yet I take no responsibility if something wrong happens with your device.**
Difficulty level: Easy
Things Required:
A PC or a laptop with windows as the Operating System, ADB driver installed
Qualcomm USB Composite Device 901D Driver (Link Given)
CKT Qwrite_Writer Tool (Link Given)
2 valid IMEIs to write. Refer to the box or bill for IMEI. It must be there
Your Yureka and a USB data cable
Step 1
Assuming your Yu is rooted. If not, Root it. Enable USB debugging. Install Terminal Emulator and type in the following commands in sequence
$ su
# setprop sys.usb.config diag,adb
Click to expand...
Click to collapse
This basically enables USB Diag mode of your phone. Now connect your phone to PC. You would see something like “Installing device driver software” which would fail eventually. Don't worry! We are about to install the Driver.
Step 2
Extract Qualcomm USB Composite Device 901D Driver at a easy to reach location and install it. There is no executable to install. You will have to install it manually using the Device Manager. See Post 2 for instruction.
Step 3
Assuming you have done the previous 2 Steps. Now the original task begins. Extract CKT Qwrite_Writer Tool to any easy to reach location and run an executable “Qwrite_Writer.exe”. You should see the following window.
{
"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"
}
The left side is to write the IMEI, Right side is to Read.
In left side, IMEI_1 : Enter your first IMEI and check the checkbox associated with it.
In left side IMEI_2: Enter your second IMEI and check the checkbox associated with it.
** Leave other things as it is. Do not touch any other setting as you may mess with it **
Now Click the start button at the Right side of the Message Box. And voila! You got your IMEI back :laugh: :good:
Downloads:
Qualcomm USB Composite Device 901D Driver: https://www.androidfilehost.com/?fid=385035244224398036
CKT Qwrite_Writer Tool: https://www.androidfilehost.com/?fid=673368273298918104
Credit:
To the original authors of the respective stuffs.

How to install Qualcomm USB Composite Device 901D Driver
How to install Qualcomm USB Composite Device 901D Driver
------------------------------------------------------------------------------
After enabling USB Diag Mode, connect your phone to PC/Laptop. Go to Control Panel and Open Device Manager. In Device Manager you will see your phone in Other Devices section. As AO5510 in my condition. Right click it and chose “Update driver software”. Then “browse my computer for driver software”. Then “Let me pick a list of device driver on my computer”. Then Next > Have Disk > Browse > and browse to the folder where you extracted the Qualcomm USB Composite Device 901D Driver. You would see a file named “htcser.inf”. Select that file and hit Ok and then follow the On-Screen-Process to finish the installation.

androidfilehost.com/?fid=385035244224398035 (IMEI WRITER SOFTWARE) this given link is not working . please update it soon.

rohitjaiswal said:
androidfilehost.com/?fid=385035244224398035 (IMEI WRITER SOFTWARE) this given link is not working . please update it soon.
Click to expand...
Click to collapse
Link updated in OP

Link not working
itsdroid said:
Link updated in OP
Click to expand...
Click to collapse
CKT Qwrite_Writer Tool: fid=673368273298918104
not working 404 error

it worked...thanks

[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.