When I connect my HTC Desire through USB cable to my laptop, my laptop wait a while then pop a windows which says USB Device Not Recognised. My device just got the orange light lit up but there is no response other than that i.e. no menu pops up to choose "charge only, disk drive" whatsoever.
It worked just two days ago before I reflash a new ROM (RCMixHD 3.6.1).
During the flash, the SD card was not recognised too so I tried to get it work by using "fastboot oem enableqxdm 0" as instructed by one post named "USB brick/rickrolled/b0rked -> FIXED!" on MoDaCo.
But I did not flash the update.zip as required cos my problem was fixed before this step.
Can anyone help me fix this problem? Waiting online
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
FASTBOOT shows "FASTBOOT USB", Bootloader also gives me "HBOOT USB PLUG", I think the USB cable is fine.
stringer7 said:
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
Click to expand...
Click to collapse
I tried the two commands in cmd, I copy down what it gives me
E:\SDK\Tools> adb devices
List of devices attached
E:\SDK\Tools> fastboot devices
HT05HPL12963 fastboot
E:\SDK\Tools>
Ok so the fastboot result means you can connect to PC.
What happens if you connect your device whilst it's booted up with USB debugging enabled? Enable this prior to connecting in settings>applications>development.
Hi thanks for the help, I managed to unbrick the USB brick. But now even though I'm able to connect to my laptop, the adb devices still doesn't give me any device. In device manager, I got an "ADB" with yellow exclamation mark under “Other Devices”, just cannot get the right driver for it. Could it be due to the USB brick?
I'm trying to unlock the bootloader on my daughter's G4, and I have run into a heavy snag. I get "code 10" (driver can not start) when it's in fastboot mode, but I'm fully able to connect with adb when the phone's up and running. This is not my first rodeo, and I'm sure the USB cable works (original cable), I have enabled USB Debugging (or ADB wouldn't work in the first place) and I think I have done everything else that should be done. But the damn thing won't work on any of my computers, under Windows 7 or 10. Driving me nuts! Also when it's booted up I see it as an LG Mobile ADB interface, but when it's on Fastboot it insists that it is an MTP device, even if I have set it as a PTP device when it's booted up. Can anybody please tell me what I have to do to get this to work? Another thing is that if I run "adb reboot-bootloader" (or even the wrong syntax (at least I think the dash should be there) "adb reboot bootloader", which LG's page says), it will not boot into fastboot/bootloader, it reboots into Android. So I have to get into the setup by holding in vol + and plugging in the USB cable. But I don't know if this is related.
Edit: Oh, btw, I have tried to find the latest drivers, so far I'm on 4.0.0.0. They are dated May 2015.
Hi, my phone stopped being able to get a USB data connection. The port is physically intact and does not wiggle. I've tried two different Macs and one PC, different USB-A to -C cables (all verified by Benson Leung). Also toggled USB debug, MTP and PTP modes from Developer Options, rebooted phone and computer. When I plug the phone in, it only goes to Charging mode. Android File Transfer doesn't see it and 'adb devices' comes back empty. There is no notification offering me to select connection type. Did I miss anything or is it time to send it in? Thanks, Tony
What OS are you running on your Windows - checking your Device Manager under Control Panels - are all the Google / N5X drivers installed and working correctly before this ? Try uninstalling, reboot PC and re-install them - and, use different USB port to connect the cable (what kind of connections are you using ??)
Can you run ADB ?
Thanks I'm primarily using a Mac (10.10.5) but the PC was running Vista. It was a borrowed PC so I didn't install the drivers. I don't think it's a driver issue though since nothing shows up in device manager and the phone doesn't offer to switch out of charge-only mode. Also the same Mac worked previously.
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
I seem to remember the same thing happening when I got mine a couple days ago and unlocked the BL within a few hours of unboxing. I ended up doing the standard unlock followed by unlock critical commands anyway. Worked fine for me.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
I'd check and make sure your adb/fastboot is up to date, or do a reinstall just in case.
There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?
Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.
morrowa2 said:
Thanks for the suggestions but still not working. Even tried disabling driver signature verification at startup. I'm going to uninstall everything, factory reset the device and start over. Might also try a usb-c to usb-a cable. Any other thoughts?
Update: Nothing worked until I used a usb-c to usb-a cable, then it worked like a charm. Must be a Lenovo thing.
Click to expand...
Click to collapse
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone
canemaxx said:
I can't even get adb to recognize my device ....I have used multiple cables I'm about to return this phone
Click to expand...
Click to collapse
have you tried a usb-c to usb-a cable. that worked for me.
morrowa2 said:
There are so many options for adb/fastboot and drivers. Where does one find "the latest," that everyone is speaking of?
Click to expand...
Click to collapse
Latest ADB/fastboot: https://developer.android.com/studio/releases/platform-tools.html
Latest USB driver: https://developer.android.com/studio/run/win-usb.html
I had no luck except about once in 20 it'd work. Then swapped to a different USB-C port on my laptop, then it worked. FWIW, I tried USB-C to USB-C and USB-C --> USB-A (adapter) to USB-C and it didn't make a difference.
js042507 said:
Try just turning the phone off and then entering fastboot via volume down and power button. THEN, plus in your phone. Do a 'fastboot devices' and see if it shows up now. In my experience, I got my phone...checked oem unlock and all that...booted into fastboot mode via hard method. And my phone is detected instantly. I did not install any drivers, update platform tools (mine is from like 2012), and even used a third-party USB-C cable. It works every time. Also, I am using the adb and fastboot executables from an older adb minimal set. Probably from like a year or so ago. I don't ever use the SDK ones really anymore.
Click to expand...
Click to collapse
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?
tluley51 said:
I did this and when in the bootloader screen, I am able to display fastboot devices, but when I go into recovery mode and try and flash something via ADB (the November patch since I am not pulling it OTA), it seems to start but it just sits at "Verifying update package" on the phone and "loading: 'taimen-ota-******.zip'" and never progresses. Almost like the PC and the phone are not talking properly?
Click to expand...
Click to collapse
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.
js042507 said:
Like others have stated, maybe try a USB-C to regular USB-A cable. I have only used that type of cable, but didn't realize that the actual cable that comes with the phone might be a problem. I never used it to test that theory though.
Click to expand...
Click to collapse
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.
tluley51 said:
Yeah that is all I have ever used. I use a USB A to C Cable Matters cable.
Click to expand...
Click to collapse
I don't know then. I haven't attempted the update yet to provide any feedback. However, others have reported this issue in the 'November OTA' thread. I would look there.
morrowa2 said:
Trying to unlock bootloader on my pixel 2 XL. Using a windows 10 64-bit laptop, usb-c cable that came with the phone, latest drivers and up to date platform tools. Debugging enabled. OEM unlock enabled.
Phone is recognized in ADB just fine. "Adb devices" results in the the device being listed. "ADB reboot bootloader" reboots the phone into fastboot mode just fine. Once in fastboot mode, however, "fastboot devices" yields nothing.
Pulling my hair out here, and not much hair left to pull. I suspect I'm going to have to tinker with the computer's security settings to get the drivers to install correctly. Any thoughts?
Click to expand...
Click to collapse
For anyone in the future, ensure the that Device Manager is showing the 'Android Composite ADB Interface' driver installed.
Then, just download the latest Platform Tools (from https://developer.android.com/studio/releases/platform-tools), and from inside that folder, open a Powershell prompt, and then 'adb reboot bootloader'. Once you are in the 'fastboot' mode, the 'fastboot devices' command works.
I had the same problem. I fixed it by plugging in my UBS-C to USB-A cable into a USB 3 port instead of a USB 2 port.
I am facing the same issue, its been almost 20 days. Tried everything but couldn't get it worked. So dropped the idea of rooting my px2L
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
worked for me thanks.
cooltime said:
My issue was I needed to replace the drivers for fastboot mode (ADB was fine). There are two drivers, one for each mode.
fastboot doesn't see device
I've read a lot of articles about this problem but I can't resolve it. I decided to install my developer application on phone using wifi. To do this I need to do some things with my phone. The firs...
android.stackexchange.com
Click to expand...
Click to collapse
This works... Get the Google Driver.
Hey gals and guys,
my girlfriend dropped her Xiaomi A2 lite and no the touchscreen doesn't respond. The phone has the stock Android One and I can only access fastboot.
Code:
fastboot devices
recognizes the phone.
The recovery is the stock recovery.
Code:
adb devices
won't recognize the phone and gives me an empty line as output
I also can't access the phone via usb with my filebrowser. If I try, the phone makes a "bing"-sound and the filebrowser gives me:
Code:
unable to open MTP device
I am using archlinux and I also have a windows device available.
Is there any chance on getting pictures etc from the phone?
Any suggestions besides getting a replacement for the touchscreen?
Thank you so much.
Connecting via USB probably needs you to click something.
I'm guessing developer mode is not enabled...
If you've got a micro USB OTG cable, you could plug a mouse in.
If you boot TWRP (fastboot boot twrp-3.3.1-dees-troy.img) you should be able to get adb and usb transfers working. Don't need to install it, just boot it. Not sure if that works without unlocked bootloader.
If you've got a micro USB OTG cable, you could plug a mouse in.
Click to expand...
Click to collapse
This did the trick.
Thank you