Develop Bugs

[Q] HTC Desire not working with ADB

Hello,
I have problem with my phone and adb, I have installed all driver for my htc, adb, fastboot,.. but when I try to check for connected devices in adb via adb devices command the list is empty even if windows recognize the device. I have tried it in Ubuntu, but the situation is same.
I don't know whats wrong, because it works for my Gnex and GTab.

Did you enable USB debugging on the phone
Sent from my HTC Desire using xda app-developers app

that was the first thing i made

well my phone is seen by adb when it's runing (in system) but it is not seen in fastboot mode

icefun said:
well my phone is seen by adb when it's runing (in system) but it is not seen in fastboot mode
Click to expand...
Click to collapse
...and it is perfectly OK.
The adb tool on your PC needs a adb daemon running on your device: this happens when the Android system is running (or a Recovery with adb daemon). When you are in fastboot mode the Android system has not really started loading yet, so there is no adb daemon to talk to your adb tool on PC -- hence your phone is 'not seen' by adb.
But it is seen by fastboot tool (another part of Android SDK tools) at this stage. So in fastboot mode you can flash images and do other stuff: just not with adb tool, but fastboot tool.

Well thx for eplaining my bad i thought that it will respond to adb devices like my other devices
PLS Close this thread

Need some help getting adb and fastboot workiing under Ubuntu

Hey guys, I'm trying to get adb and fastboot working under Linux. I added udev rules for adb, fastboot and flashmode(idk if this one was really necessary). Adb and fastboot are already working with my other devices, but does not seem to recognize my Xperia Play, adb devices in terminal lists nothing, same thing with fastboot devices. I tried using flashtool, it says my device is connected using fastboot and when i try to flash lupus kernel flashtool shoots an error saying my device needs to be connected with fastboot.
My Xperia is running Ics/Paranoid 4.0.4 and debugging mode is turned on
What can possibly be wrong here? Any Ideas?

Check the drivers. It could be giving you those errors because of the drivers you're using. Try to update them.

Fastboot doesn't see Nexus 5 X, ADB and filetransfer work fine

Hi guys,
i recently received my nexus 5x and would like to root it like my old nexus 5.
The drivers are installed, filetransfer from and to phone/pc is working, adb see's the device. PC is windows 7.
But when my 5x is in fastboot mode the fastboot devices command shows no results and any other command like fastboot oem unlock get stuck at < waiting for device >.
Am i missing something? Do you have any idea?
Thanks for your help!
edit: the device manager shows the 5x as unknown device when in fastboot mode

Download the latest version of fastboot.exe

Yep, I was having fastboot issues as well but it turns out that there are updated fastboot binaries for Android 6.0 that you need to get.

Fastboot doesn't see my Zenfone 2

Hi, I searched for an answer but I didn't find it, so I created this thread.
My Z00A is running on the latest official OTA version perfectly fine. It is unlocked but bricked once and I successfully unbricked it.
I installed Intel Android driver and adb on windows 10.
Booted in Android, adb sees my device when I enter "adb devices".
In the bootloader, when I enter "fastboot devices", fastboot leaves a bank space and open a new command line and if I enter any other command it says < waiting for device >.

It looks like Windows 10 didn't let the driver work properly. I downloaded the drivers from ASUS and manually installed the bootloader interface driver via legacy wizard. Then, I uninstalled the old one and now fastboot is functional.

Stuck in Bootloader - adb no devices - can't boot into system or recovery

Hey guys I'm stuck in bootloader on my taimen and I hope someone can help me.
I tried to update my OS from latest Android 9 factory image to Android 10 via bootloader, as I always do.
After executing the command
Code:
./flash-all.sh
I got a message that said that I should download and install the latest platform-tools from googles dev site, what I did. And I think that was my mistake. I downloaded the updated tools and replaced the old ones, while beeing in bootloader on my phone and connected to my MacBook.
Now I have a problem that whenever I try to boot in recovery or system I get the dead android Icon with 'No commands'. That wouldnt be a problem for me, if I could install a new .img to boot into system and start again. But unfortunately I cant find my device via adb. The List of attached devices is always empty.
What I have tried so far to solve this issue:
- tried 2 different cables and all USB ports I have - no success
- restarted adb several times - no success
- added vendor Id to /adb_usb.ini file like described in this post https://stackoverflow.com/a/7136003 - no success
Does anyone have a suggestion what I could try next? Any help is appreciated

Download Homebrew. And install adb in terminal, and try if that works . https://brew.sh/index_sv .
https://stackoverflow.com/questions/31374085/installing-adb-on-macos/32314718#32314718

I'm no expert but I thought that you should use fastboot commands from your MacBook terminal if you are in the bootloader and not adb commands. But I guess the fastboot commands don't work either since you wouldn't have a problem then!
Tips on getting to recovery mode from 'no command' screen:
https://youtu.be/P1RGEle3qN0

Hey guys thanls for your suggestions.
Fortunately I was able to resolve my issue. The problem was that I was on the wrong partition.
After setting the partition back to a with
Code:
fastboot --set-active=a
my device id appeared in the list of attached devices
Code:
fastboot devices
So I was able to reflash the flash-all.sh and now I'm on Android 10.