Database Develop

ADB device not found

I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??

ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
Yup. I have similar experiences on my linux box.
Try adb shell and see if you get a shell into the device.

ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
the one time I had that problem, killing and starting adb fixed it, but it looks like you're already doing that.

Try launching Eclipse?
When I had the same setup as you (ubuntu 9.10 + Eclipse + all relevant parts), adb "just worked".
Running under Vista32bit though, adb only works when I have Eclipse running. Don't know why. Don't care why. Felt like banging my head into a wall when I realized that. (More specifically: under Vista32bit, my Vogue shows up with only one question mark, not a whole slew like you have.)
Anyway, try making sure Eclipse is running when you try to connect via adb. Who knows. Maybe it's a cross-platform issue.

Thanks for the reply. Everything works fine in Windows Vista 32bit, although the device serial number shows up as a question mark. I read somewhere that adb is broken for the 2.6.27+ kernels. There is a proposed fix:
review.source.android.com/#patch,sidebyside,10633,1,adb/usb_linux.c
I've compiled the source, tried the new adb and still not working... maybe the next official release will be better.

I shell access and can browse filesystem with adb shell, but ddms in Eclipse doesn't show much useful information.
Excellent work by the way! And thank you.

Found a compiled version of adb with the fix highlighted on code.google.com:
h t t p ://floe.butterbrot.org/external/adb.gz
Don't forget to make it executable.

That worked for me
This was hard to find. Thanks.

I just installed Android on my Sprint touch vogue. No luck using adb to get a shell on my phone.
My environments are Debian sid 2.6.32 and/or OS X Snow Leopard. I installed the r06 SDK and adb doesn't work under either OS. ./adb devices shows nothing, ./adb shell shows device not found. Under debian, I downloaded the recompiled version of adb linked above, no change
dmesg shows:
Code:
usb 1-3.2: USB disconnect, address 28
usb 1-3.2: new full speed USB device using ehci_hcd and address 31
usb 1-3.2: New USB device found, idVendor=0bb4, idProduct=0c02
usb 1-3.2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
usb 1-3.2: Product: Android Phone
usb 1-3.2: Manufacturer: HTC
usb 1-3.2: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 31
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg2 type 0
sd 9:0:0:0: [sdb] Attached SCSI removable disk
Thanks for any help.

Might have figured something out that can help. uninstall the mass storage driver. I just did this and it connected right up.

[solved] adb devices = ??????? no permissions

exactly as the title states, whenever i attempt to view the devices connected i get that output. I've searched, and the proposed solution is to start adb as root, but whenever i use sudo before adb start-server, the output is = sudo: adb: command not found
i don't understand what's going on, is it a problem with my drivers?
edit: solved it by using this as my /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
the id vendor was wrong in all the tutorials i read.

THANKS!!!! This worked for me, Ubuntu 10.04.

hmm.. interesting... when i changed the ID it started to work on Nexus S and on HTC magic...
If you have ubuntu 10.10 it SHOULD work without udev rules..

[Q] How to get ADB running on Fedora 8 talking to a Colour Nook

I have read hundreds of postings all over the web, while trying to get adb to talk to my
autonooted Colour Nook, without success.
1/ I have the SDK installed
2/ I have the PATH adjusted
3/ I have the /etc/udev/rules.d/51-android.rules file containing
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666"
Note I extracted the 2080 from the ID in /var/log/messages when I pluged the Nook in
4/ I have tried ATTRS instead of SYSFS too
Yes, I restarted udevd on every attempt.
5/ Whenever I execute: 'adb devices', it always returns an empty list.
6/ Sniffing the USB connector with Wireshark, shows two mass storage devices and a 'network' capability reported.
7/ I have the 'Development -> USB debugging' option enabled in the 'nookcolor tools'.
8/ udev tracing shows only mass storage activity
What can I try next?
TIA
Fulko

try:
adb kill-server
sudo adb devices

sorry, tried that too, I just forgot to mention it.

First, F8? Really?? F12 went EOL a few weeks ago... Yikes.
Anywho.. This is what I have.
Code:
# more /etc/udev/rules.d/50-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666", OWNER="youruser"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2080", MODE="0666", OWNER="youruser"
AND read here
http://nookdevs.com/NookColor_USB_ADB

[Problem]Problem with detecting device on linux

Hello I have problem with my adb on linux mint 15. Fastboot see a device but adb not. I try everything.
Outputs;
51-android.rules
Code:
#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE=0666
adb_usb.ini
Code:
GNU nano 2.2.6 Plik: adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0bb4
lsusb
Code:
Bus 001 Device 006: ID 0bb4:0ff0 HTC (High Tech Computer Corp.)
Please help me.

What are you trying to run? Make sure to run as root in Linux. Aka sudo
Sent from my HTC One using XDA Premium 4 mobile app

[Q] Fastboot not working - ADB ok XT1068

Seems to be different to the common problem in that ADB works ok in normal mode fastboot doesn't. In recovery mode the phone is not seen and neither works. This on 3 computers with both linux and windows eg:
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
Bus 002 Device 005: ID 22b8:2e76 Motorola PCS
[email protected]:/home/jc# adb devices
List of devices attached
ZX1D223SWB device
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# adb reboot recovery ## results are the same as pwr on vol down
[email protected]:/home/jc# adb devices
List of devices attached
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
-----No sign of phone ---------​
Phone has 4.4.4 version 21.11.23 with unlocked bootloader
Any ideas to flash recovery

[Solved? product ID change] Fastboot not working - ADB ok XT1068
jc56au said:
Seems to be different to the common problem in that ADB works ok in normal mode fastboot doesn't. In recovery mode the phone is not seen and neither works. This on 3 computers with both linux and windows eg:
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
Bus 002 Device 005: ID 22b8:2e76 Motorola PCS
[email protected]:/home/jc# adb devices
List of devices attached
ZX1D223SWB device
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# adb reboot recovery ## results are the same as pwr on vol down
[email protected]:/home/jc# adb devices
List of devices attached
[email protected]:/home/jc# fastboot devices
[email protected]:/home/jc# ./mfastboot devices
[email protected]:/home/jc# lsusb
----- Lots of stuff --------
-----No sign of phone ---------​
Phone has 4.4.4 version 21.11.23 with unlocked bootloader
Any ideas to flash recovery
Click to expand...
Click to collapse
After another 4 hours of my life tried:
adb reboot bootloader
while usb connected and lsusb showed:
"Bus 002 Device 007: ID 22b8:2e80 Motorola PCS"
Note the different id
and selected recovery by <up>- TWRP appeared without any further computer stuff.
Had previously tried: "fastboot flash recovery TWRP2801-titan-motog-2014.img"
and following "waiting for device" had closed xterminal

@jc56au: On Windows I have all kinds of adb problems but on Linux it works just fine for me.
It may sound funny but are you using 3.0 USB port? If so then switch to 2.0 XD

LuK1337 said:
@jc56au: On Windows I have all kinds of adb problems but on Linux it works just fine for me.
It may sound funny but are you using 3.0 USB port? If so then switch to 2.0 XD
Click to expand...
Click to collapse
Window was W7 both 32 and 64 bit
Linux was Ubuntu 14,04 32 bit and Debian 64AMD with multiarchi386
With so much fiddling not sure but probably 3.0 however vital part appeared to be the "adb reboot bootloader" bit

jc56au said:
Window was W7 both 32 and 64 bit
Linux was Ubuntu 14,04 32 bit and Debian 64AMD with multiarchi386
With so much fiddling not sure but probably 3.0 however vital part appeared to be the "adb reboot bootloader" bit
Click to expand...
Click to collapse
Yes. For fastboot to work, you have to put your phone in fastboot (bootlader) mode. That is the screen you get when pressing power+ vol.down. Only then you can use the fastboot commands.