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.

[GUIDE] ADB For Beginners (Setup, Use, and More!)

Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now, [Get new sdk (1.5r3) to work]
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r3+
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.

-------bump------

Good guide, pretty simple... Ill bookmark this, so I can send people that needs help here.

i have attached a zip that has the files i use to get basic use like for doing root to stock to upgrading 2.1-2.2 and other small things.
extract to C:\fastboot
in C:\fastboot you will find a "cmd" batch file. just run it and it should be ready for you to type in adb commands or fastboot. just make sure your in debug mode by doing all in the first post for installing drivers and all that.

U seriously bumped this thread? Lmfao

help?
i was trying adb and i got!
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
K:\>adb devices
List of devices attached
HT07YHL02294 offline
HT07YHL02294 device
K:\>adb remount
error: more than one device and emulator
Click to expand...
Click to collapse

ADB
i have this message Permission Denied what should i do?

thank you D200P13 soo much. i got it working thanks to your files

X10 adb issues
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?

p2dewit said:
Can't get it to work for my X10.
ADB does not see my X10 when connected, have tried all mentioned above several times, no luck.
USB drivers seem not to install.
Do i need something special for my X10 to connect via ADB ?
Click to expand...
Click to collapse
Turn telephone i debug mode.

when i type adb it says that it's an unrecognized command.

That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App

danger-rat said:
That's because you haven't navigated to the folder where the adb file is located...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Isn't it in the android-sdk-windows folder?
EDIT
nvm found it. it's in another folder....thanks

when i run adb shell, it doesn't give me a # it gives me $. what do i do?

What are you trying to do?
Sent from my Nexus One using XDA App

Trying to flash a rom on my phone (x10) and was making sure adb is working properly before i do anything. When flashing the new rom there's some bugs that require adb to fix. From my understanding "$" means i don't have su access. Thanks for the help btw. Sorry for bothering you. Just taking proper precautions.
EDIT
Sorry again. Found my answer. I forgot to unlock my device to accept superuser permissions. Thanks for your help

to check ur phone is detected by adb....
i type "adb shell" in cmd,and according 2 u i should show #.....but it shows $ to me......why?

To check connection, type "adb devices"
"adb shell" will allow you to work remotely on your device. If the $ doesn't change to #, then you don't have root access.
Sent from my Nexus One using XDA App

If your just trying to set up adb to riot your device, I put this together to make things much easier...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App

Where is the Mac Specific version. Everything you posted is for windows mate!

[Q] adb devices = error: device not found

When i make in cmd adb devices . List of devices attached but no device.
I give adb reboot bootloader and comes: Error: device not found
What is wrong?
I can not booting. i make this in the fastboot mode

adb: error: device not found

I put the P880 in software mode. I hope this is correct.
I am using Xubuntu 12.04 and I execute the commands as user root in a shell
Code:
adb reboot oem-unlock
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Code:
adb devices
List of devices attached
[nothing]
Code:
lsusb | grep LG
Bus 003 Device 003: ID 1004:61f1 LG Electronics, Inc.
Code:
grep -i 1004 /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", ATTR{idProduct}=="61c5", MODE="0600", OWNER="<~/>
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", ATTR{idProduct}=="61f1", MODE="0600", OWNER="<~/>

Adb does not work in software update mode. You have to boot to your normal android system. Make sure usb debugging is enabled.

Thanks, I cannot activate usb-debugging, it is grey. Is it ok to use battery-loading with usb?

You can't activate usb-debugging while your phone is plugged in. Just plug out the usb-cable then it should work.

Dexxon said:
You can't activate usb-debugging while your phone is plugged in. Just plug out the usb-cable then it should work.
Click to expand...
Click to collapse
Thanks, now I get a response.
When i execute "adb reboot oem-unlock" with my Xubuntu 12.04 the phone reboots and I see a very very small red text for a short time and then this disappears and I see the phone is loading the battery.

Whats the version of your ROM?

Device: LGE LG-P880
Android Version: 4.1.2
Build: JZO54K

lg-optimus said:
Device: LGE LG-P880
Android Version: 4.1.2
Build: JZO54K
Click to expand...
Click to collapse
Your SW version is 262-000, afaik to unlock bootloader you gotta write directly to fuse, the official way won't work. There is a topic on general subforum on how to do this. Good luck

[how to]lock/unlock your bootloader without htcdev(s-off required)

READ THIIS!
*this thread is for desire 510. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or unlocked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
*i have tested this on my gsm cricket desire 510 variant(a11_ul). let me know if you try it on a different variant,or if youd like to dump partitions and have me take a look
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
other useful threads:
remove your tampered banner: http://forum.xda-developers.com/desire-510/general/how-to-remove-tampered-banner-t3179866

mine too