Hi.
I have a Mi8 (China version), bootloader unlocked officially, clean-flashed xiaomi.eu 9.5.30.
When I connect the phone to the laptop (Windows 10 64bits) the laptop does not react at all. The phone charges, but the device manager does not show anything.
I've tried:
- ROM clean flash: Same result. In fact the issue started before I clean-flashed the 9.5.30.
- Several cables, including the original: Same with all of them.
- Several USB ports in the laptop: Same result with all of them.
- Other devices in the same laptop (USB keys, drives, mouses...): The USB ports are working.
- Rebooting.
- Changing the default USB connection mode in the Developer options.
- Booting recovery mode: no reaction.
- Booting fastboot: here is the only reaction which is an error 43 (Device failed enumeration) in Windows Device Manager. I tryed to uninstal the drivers, update them and a couple of other tricks in the registry. Nothing worked.
- Reinstalling the Mi software (unlocker, Mi manager application...), the adb drivers, etc...
Any idea?
i have the same problema you solved ?
Nope
Related
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
SOLVED...sort of...
I used a workaround. I used a Windows 7 computer and there it worked perfect.
roel1976 said:
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
Click to expand...
Click to collapse
hi, i had same USB problem, windows7 worked for this old phone
after installing cm 13(ROM) on my phone everytime when i connect the phone to my pc , mtp usb device failed to install, i tried every method from the web but still it's not woking
Hi guys,
my OnePlus 3t received an OTA to version 4.5.0 ( OxygenOS).
Since that day, when i connect it to PC I only see it in Device manager as "Unknown USB Device ( Device Descriptor Request Failed).
OS is win 10 x64, but i tried others also.
already reinstalled USB drivers.
Any thoughts?
- Uninstall all Oneplus related drivers (+ software)
- Restart windows
- Install Oneplus drivers and connect again
ivgenyr said:
Hi guys,
my OnePlus 3t received an OTA to version 4.5.0 ( OxygenOS).
Since that day, when i connect it to PC I only see it in Device manager as "Unknown USB Device ( Device Descriptor Request Failed).
OS is win 10 x64, but i tried others also.
already reinstalled USB drivers.
Any thoughts?
Click to expand...
Click to collapse
Fir3start3r said:
- Uninstall all Oneplus related drivers (+ software)
- Restart windows
- Install Oneplus drivers and connect again
Click to expand...
Click to collapse
Try using the tool USBDeview to uninstall/delete all USB drivers that appear to be related to Android. Reboot computer.
Install OnePlus drivers. Reboot computer.
Then connect the device and see what Windows recognizes it as.
Verizon N960U (in file transfer mode)
Windows 10
Device Manager can't seem to find a proper USB driver. The phone just shows up as "MTP". I've tried manually installing a couple different ones, nothing seems to work. USB Debugging is on.
Any ideas?
Try uninstalling the drivers windows thinks it should use and try again
I'm running an older version of OMNIROM with Microg on my Zenfone 8 (US). Obviously, the bootloader is unlocked. I've got TWRP on it also. A few days ago I had a problem where the cell service just died. I couldn't enable Mobile Data and had a little x over the cell signal bars. I finally got the cell service working by wiping Dalvik Cache, Data, and internal storage. However, since I just wiped my phone, I'd like to update it to Android 12 (either OMNIROM or LineageOS). However, my Windown 10 PC does not see the phone when I try to use ADB or Fastboot. It doesn't list any device.
Things I've tried:
-In addition to the ASUS cable, tried OnePlus 6's cable
-4 different USB ports on my PC (2.0 and 3.0)
-Numerous ADB drivers, including ASUS' driver, and many generic drivers
-Three different ADB/Fastboot installations
-Ran Windows' device troubleshooter
-Tried installing driver with Windows ignoring driver certificates
I do have USB Debugging enabled. I can see the phone when it is running the ROM and set to File Transfer.
Any suggestions on what I could try to get my phone recognized?
I've been at this most of the day. I post here, then try one more driver change, and it works. Well, it worked enough to get fastboot to recognize it, so I flashed stock.
The driver change I did was to pull up Devices and Printers in Win10. I right-clicked on the Zenfone 8, selected Properties | Hardware. It showed that there was no driver installed for the device. I clicked on Update Driver, and pointed it to the folder with the ASUS official drivers (which I had installed previously in a different manner). I let it do its thing. Rebooted, and it worked. I hope this helps somebody else.
Yippee38 said:
I'm running an older version of OMNIROM with Microg on my Zenfone 8 (US). Obviously, the bootloader is unlocked. I've got TWRP on it also. A few days ago I had a problem where the cell service just died. I couldn't enable Mobile Data and had a little x over the cell signal bars. I finally got the cell service working by wiping Dalvik Cache, Data, and internal storage. However, since I just wiped my phone, I'd like to update it to Android 12 (either OMNIROM or LineageOS). However, my Windown 10 PC does not see the phone when I try to use ADB or Fastboot. It doesn't list any device.
Things I've tried:
-In addition to the ASUS cable, tried OnePlus 6's cable
-4 different USB ports on my PC (2.0 and 3.0)
-Numerous ADB drivers, including ASUS' driver, and many generic drivers
-Three different ADB/Fastboot installations
-Ran Windows' device troubleshooter
-Tried installing driver with Windows ignoring driver certificates
I do have USB Debugging enabled. I can see the phone when it is running the ROM and set to File Transfer.
Any suggestions on what I could try to get my phone recognized?
Click to expand...
Click to collapse
Any change to try Linux on your PC ? e.g. via LIveCD or in a virtual machine with access to the USB port?
bnsmb said:
Any change to try Linux on your PC ? e.g. via LIveCD or in a virtual machine with access to the USB port?
Click to expand...
Click to collapse
I could try it on my laptop which only runs linux, but at this point, I'm past that, so I really don't need to go back and try it again.