Database Info

[Q] All of a sudden no USB or adb/fastboot detction

Hi folks,
wasn't really sure where to post this thread as my phone doesn't have a separate section and since this is more of a general issue rather than one related to a specific phone model, thought I'd try my luck here.
Anyways onto the problem - was gifted a Micromax A092 a few days back. Worked fine until last night when Windows stopped detecting it. When this issue first cropped up, a few times of disconnecting & reconnecting the USB cable got the phone working again but after I plugged in another phone to transfer data and reconnected mine, the issue became permanent and continues to persist.The phone charges when connected to the wall but doesn't charge nor does it get detected when plugged into the PC.
Now when I pull the USB cable and stick it into a different port on the PC, for a second or two, the "connected in charging mode" message appears in the pull down menu and Windows detects phone memory/storage briefly before both disappear. I haven't had the opportunity to plug it into a different machine to check whether its being detected but I can assure you that the USB cable isn't the issue as every other phone in the house works with all the cables I have been using ( 3 to be precise - 2 Micromax and a Sony cable).
Another strange thing I think I should mention in the hope that it could lead to a resolution is that ever since this issue started, none of the phones are being detected by fastboot/adb and don't appear in Device Manager under Android Device as Android ADB Interface. Just two days back, I flashed an Xperia M with fastboot but now the phone doesn't show up under Android Devices, just as Sony 0104 or something. Same with a Galaxy Star Pro. I have reinstalled Android SDK, usb drivers, fastboot/adb but no dice. Opening up the command prompt in the adb/fastboot folder and typing fastboot devices doesn't list any of these phones either.
So can someone please help me in determining whether this is a software or a hardware issue? Any suggestions are welcome and truly appreciated. Thanks.

If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.

fanmile said:
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
Click to expand...
Click to collapse
Thanks for the reply
No I haven't updated Windows. Mine's a standalone Win 8.1 installation that's been running for a good few months now.
Like I said, w/o any rhyme or reason, it stopped working in the middle of the night and so did fastboot/adb. I remember typing fastboot devices and having the phone detected just prior to Windows acting up and in following time period, I don't remember installing any software or applying any Windows updates. This issue basically just came out of nowhere.
I'll take a look at the links but will it work for someone who was already using 8.1?

XenolithicYardZone said:
I'll take a look at the links but will it work for someone who was already using 8.1?
Click to expand...
Click to collapse
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.

fanmile said:
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
Click to expand...
Click to collapse
No worries man....guess what? On a whim, I plugged it back in and voila...there was detection. I have no idea how it started working but I have been at it all day and something probably did the trick though I have no clue what it was which is annoying me because if this were to happen again, I would be back to square one.
Ah I see...I did download the patch you had linked to but before I could get around to installing it, this thing started working again. Anyways good to know it won't work with the latest updates as I installed the latest Windows update just this morning myself.
Although now my phone's being detected, the fastboot problem still persists. Neither my phone or any other phones I have access to are detected via fastboot. They all show up under Device Manager as Android ADB Interface but are not recognized by fastboot. Its really irritating me because only 2 days back I flashed the Xperia M on the same damn OS but no dice now. I applied the Windows update hoping it would fix this issue but no luck so far. No software installations, no Window's tweaking...nothing. Hell I haven't even rebooted the PC in the last few days until this started happening. Strange. More research....yay
If you happen to recollect or come across any other workarounds, please do let me know.

use this driver worked for me
download these driver this is only driver fault
d-h.st/ZUh
copy link and download lenovo.zip and in device manager select android and use update driver option to install driver and its done try it works for me

get drivers from
micromax official website

OnePlus 7 Pro not detected by PC at all (only in EDL/MSM mode)

Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez

This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse

Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.

MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.

amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck

Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.

Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.

It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.

Redmi Note 7 Pro, fastboot not recognized by PC

Hello,
Had the phone for 2 years, and I was using a Google Pixel UI. I had some problem with phone auto rebooting while not in use. So I decided to install MUI, but I forgot its only in Chinese without google play.
So I have tried to install the TWRP recovery, but the fastboot is not recognized by the computer.
I have tried Xiaomi Poco X3, and fastboot its working fine on it. So its not issue with the cable.
I have installed some drivers, but it didnt help. I have tried most of the options, so not sure what I'm missing. Will try tomorrow, a different PC at work. MiFlash also cant see it.
Thanks for any help.

I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......

Any leads on the above problem guys?

Disable driver signature enforcement and download mi flash tool. It will prompt you to install all the drivers. Install them and check if it works. For me this was the solution. Another solution is to download the latest drivers from android at https://dl.google.com/android/repository/platform-tools-latest-windows.zip for windows and install it manually by using device manager. This fixes are of course only for windows

On my PC, I didn't try other devices in fast boot mode but I know that my redmi note 7 pro wasn't displaying even after installing those Google/phone drivers.
It eventually worked when I opened Device Manager and saw that my phone was showing as Unknown Device; I clicked on the option to update the driver from a folder on my PC, so I selected the folder containing the android_winusb.inf file and it worked

sumitsky33 said:
I am facing the same issue tried everything I could. I am able to to execute fastboot command on other devies such as one plus 5t but not with mi note 7 pro as it's not detected in fastboot mode no matter what I do.
It gets detected in adb but nothing pops up when I connect in fastboot mode. No devices is shown in fastboot mode. No changes in device manager when connected as fastboot.
Already tried.
-2 different cables
-Disable signature enforcement
-manually installed drivers
-3 different computers
Someone help us out..,.......
Click to expand...
Click to collapse
If you get solutions then please tell us

adb devices command doesn't work in One plus 6

My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen OS ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could use all adb commands on this device even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason? I encountered a similar thread on OnePlus 5/5T but unsolved.

Download tool and enjoy again

ashish_jha said:
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen OS ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could use all adb commands on this device even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason? I encountered a similar thread on OnePlus 5/5T but unsolved.
Click to expand...
Click to collapse
Probably test on another computer and check. If so, then reinstall ADB drivers and retry. i am sure it should work.

mm_rajesh said:
Probably test on another computer and check. If so, then reinstall ADB drivers and retry. i am sure it should work.
Click to expand...
Click to collapse
Thanks buddy. I re-installed sab driver and it worked !

One plus 7 pro usb drivers?

I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?

tarek._.n said:
I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?
Click to expand...
Click to collapse
Update : I used another pc, an amd laptop and used the tool all in one made by @mauronofrio and it worked perfectly, saving me from hours of trying things, so thank you for that!

I usually avoid this drama by disabling driver signature before installing OnePlus drivers on windows 11. Always works.