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?
Related
Hello
Posted this over in Pauls MoDaCo forum as well but not had any replies yet so thought it best to try here as well.
I've bricked my Desire, phone loads up but the sim and sd card aren't recognised (though I can still use wi fi).
When connecting the phone to my PC (tried windows 7 and XP) the drivers fail to install and I get various faults like the device being recognised as android 1.0 usb to a Qualcomm device.
The phone is still rooted (I can install rooted apps from the market) however after following various unbricking guides I always get stuck at stage 2 (i.e. enable sd card), if the PC won't recognise the device how can i run the 'fastboot oem enableqxdm 0' command?
I've also tried running fastboot using a terminal app on the phone but it doesn't recognise fastboot, should i be in a specific directory on the phone when running this command?
Any help greatly appreciated.
Cheers
Have you tried using a different jab port? I had to use one at the back of my pc front ports wouldn't install drivers properly.
Sent from my HTC Desire using XDA App
You need to follow the guide on modaco for unbricking your device. You have the usb brick, and it can easilly be fixed.
Follow the steps religiously and you will be up n running in no time again.
I've followed the guide lots of time, it's not that long winded so it shouldn't be to hard to follow.
I get stuck on step two, using the fastboot command.
My PC and also tried laptop (Win XP and 7), different USB ports (front and back) but each time it attempts to load drivers and I end up with it either being recognised as an Android 1.0, Android Bootloader Interface or a Qualcomm device. I then run fastboot, and get the device not recognised error.
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
celticone said:
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
Click to expand...
Click to collapse
You don't need to get into recovery for this.
You have sdk installed, so boot your phone by pressing power while holding down the volume down button.
Use a command prompt on your pc and cd to the tools directory in the sdk. If the sdk is saved to the root of your C: drive on the pc you would type
Code:
cd C:\android-sdk-windows\tools
When in there type
Code:
fastboot oem enableqxdm 0
This will re-enable your sd card and allow you to continue.
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
celticone said:
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
Click to expand...
Click to collapse
It definitely sounds like the old usb brick problem, so that's a good thing! When you tried the commands were you booted into fastboot? When you connect the phone to the computer does the phone display change from saying fastboot to fastboot usb? I think thats what it should say, can't remember to be honest!
Have you tried another usb port, and a different cable too?
Edit: I'd also try rebooting the computer to ensure any running process etc are closed.
Got it fixed, final throw of the dice this morning I connected the phone to a Vista laptop and it was recognised straight away, so downloaded HTCSync then ADB tools on to the laptop and finally got the re enable command to work.
Jeez that took for ever, strange that Xp, Win7 and Linux PCs couldn't recognise the phone but Vista did.
Still got it sorted, thanks for the help.
No worries. Glad you got it sorted.
I have almost the same problem.
but with the legend.
SD is not recognized.
Can´t Call,
Can´t connect via USB.
Is there something I can do in the built in terminal in the ROM?
adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.
No ideas?
I can connect adb over WiFi, but ofcourse it says offline.
USB debugging ticked?
A
Adb doesn't work in the bootloader. Only fastboot commands
Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.
Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.
I am trying to root LG G4 H811 (Tmobile).
I downloaded LGMobileDriver_WHQL_Ver_4.2.0.exe from LG web site and installed.
I enabled debug on phone.
Download and unzipped latest platform-tools-latest-windows (adb and fastboot) from https://developer.android.com/studio/releases/platform-tools.html
When I connect phone to laptop via USB and run adb devices, i see my phone
When i run "adb reboot bootloader" the phone does not boot into boot loader, but reboot normally.
So I powered off phone. Pressed up vol and connected USB. The phone shows "Download".
Now when I run fastboot devices, fastboot does not see the phone.
Please help me root my phone. I have tried this on two laptops, same result. Also I have tried USB2.0 and USB3.0 ports same result (fastboot cannot see the phone).
What else I can try?
Thanks
you must enable "Enable OEM Unlock" in the same menu of "USB Debug", then you can use "adb reboot bootloader".
Thank you, thank you, thank you. That did the trick. "adb reboot bootloader" is working and fastboot is able to see the phone.
Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks
jaw2floor said:
Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks
Click to expand...
Click to collapse
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:
faby GT said:
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:
Click to expand...
Click to collapse
Hi thanks for getting back to me,
I assume you meant the '15 second installer', which I just did just install successfully. I am still unable to see the device with 'fastboot devices' command.
Other info: I have factory reset the phone, made sure oem unlock is checked, tried the same process on another computer. I can get adb mode to work fine, but the command 'adb reboot fastboot' just reboots the phone as usual
jaw2floor said:
The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED.
Click to expand...
Click to collapse
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.
schmatzler said:
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.
Click to expand...
Click to collapse
If it won't work, after that just go to devices and printers and delete Xperia XA2. It will work.
Else, after installing 15 seconds, inside device manager, update the driver of your phone (or mtp device), select local, then Android device, then fastboot. Disconnect the phone and reconnect as before (volume down)
Fastboot is VOL. UP (on this device)! (Not vol. down)
So basically turn off the device, hold Vol. UP and simply connect to USB, hold Vol. UP until LED is steady blue and you are set.
Note: VOLUME UP activates fastboot and VOLUME DOWN enables flashmode and/or recovery mode
Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off
Corias said:
Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off
Click to expand...
Click to collapse
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you
BoernMe said:
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you
Click to expand...
Click to collapse
Did solve this by connecting to different PC. No cable/port/hub change did help. Looks like there was some trouble with drivers (though the same PC fastboots Z3 Tablet Compact perfectly).
Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?
that_random_guy said:
Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?
Click to expand...
Click to collapse
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
I had the same problems with my device XA2 H3113 and Win10.
My solution: Try it with Ubuntu. Just grab an 8GB usbstick, install Ubuntu via usb-installer, boot ubuntu and open a terminal
sudo apt update
sudo apt install adb fastboot
LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
Hey can you please provide me a link to the drivers? as I've been trying so many drivers and they don't work.
LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
works for me
Hey all,
I am attempting to root my 2XL, and have so far unlocked the bootloader using ADB, however when attempting to use
fastboot boot <twrp.img>
I get stuck on < waiting for any device >
Using Deuce's flashing script, I get the following:
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
Error! Fastboot not accessible!
Press Enter to continue...:
When attempting to update the device driver using the official Google USB Device driver inf, I get the error message
The folder you specified doesn't contain a compativle software driver for your device.
If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
Earlier today I was able to update the device driver, and that fixed an issue I had with ADB not working, but I've hit a wall with this and there doesn't seem to be any solutions online.
Any help is greatly appreciated.
Cheers,
Boots.
How did you unlock the bootloader if fastboot isn't working?
Does the phone show up in device manager when connected and at the bootloader screen? If yes, what is the driver info?
To check if fastboot is working, run fastboot devices in the command line.
Note that USB-C ports tend to be unstable with this phone. Connect it to a USB-A port.