Database Users

[solved/info] - adb with ubuntu

I am running ubuntu 9.04. I have eclipse and the Android s.d.k. set up and running perfectly. But I cannot figure out how to setup a.d.b.
I apologize for the new post, but I promise I have searched for hours on this forum and Google. All I found was info on installing on Windows, and fixing a.d.b that used to work but won't work now after updating to 9.04. Anybody have a tutorial or a fix that I might have missed? Thanks in advance.

there is nothing to set up just make shure it has execute permissions, thats what had me stumped LOL
#chmod +x adb
then just plug in the g1 (no drivers required) and
#adb whatever you want
but i was using arch :O

to make it easier copy the adb executable to /usr/bin and you can execute from any directory withoud using cd /directory
Code:
sudo cp /androidsdk/tools/adb /usr/bin
sudo chmod +x /usr/bin/adb
that's how i use mine on my 8.10 and 9.04

Thanks guys, pretty sure it's working, just need to figure out how to connect to device. I will try your suggestions.

Done. Then I tried
#adb logcat
and i get
- waiting for device -
should I
#cd /bin
#adb logcat
?

I am following tutorials for windows, so it is kind of confusing. I don't think I can connect. I get
Code:
[email protected]:~$ adb start-server
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$

Here is me trying all kinds of stuff
Code:
[email protected]:~$ adb start-server
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb kill-server
[email protected]:~$ adb
Android Debug Bridge version 1.0.20
-d - directs command to the only connected USB device
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 running.
-s <serial number> - directs command to the USB device or emulator with
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 forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and install 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
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
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 specified device
adb remount - remounts the /system partition on the device read-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 updated.
- If it is "system" or "data", only the corresponding partition
is updated.
[email protected]:~$ adb get-state
* daemon not running. starting it now *
* daemon started successfully *
unknown
[email protected]:~$ devices
bash: devices: command not found
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb remount
error: device not found
[email protected]:~$ adb start-server
[email protected]:~$ adb remount
error: device not found
[email protected]:~$ adb get-serialno
unknown
[email protected]:~$

tried another usb cable, different usb port. Same stuff
Code:
[email protected]:~$ adb shell
error: device not found
[email protected]:~$ adb start-server
[email protected]:~$ adb shell
error: device not found
[email protected]:~$ ls
adb examples.desktop Templates
android-sdk-linux_x86-1.5_r2 Firefox_wallpaper.png Videos
Desktop Music workspace
Documents Pictures World of Warcraft Trial
eclipse Public
[email protected]:~$ cd /
[email protected]:/$ ls
bin dev initrd.img media proc selinux tmp vmlinuz
boot etc lib mnt root srv usr
cdrom home lost+found opt sbin sys var
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ adb start-server
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ ls
bin dev initrd.img media proc selinux tmp vmlinuz
boot etc lib mnt root srv usr
cdrom home lost+found opt sbin sys var
[email protected]:/$ adb start-server
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ adb kill-server
[email protected]:/$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
[email protected]:/$ adb shell
error: device not found
[email protected]:/$
Any ideas?

I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l
Would any of that matter.

CBowley said:
I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l
Would any of that matter.
Click to expand...
Click to collapse
Doubtful. I too am looking to get ADB running on my Ubuntu laptop, as it would save a bunch of time for me being able to use it instead of my slow windows computer (ADB is corrupted driver-wise on my main rig).
Anyone have any reasonable tutorials for lower-level linux users on Ubuntu 9.04 32-bit?

I have Ubuntu + SDK and I don't have any issue.
Are you sure you installed your SDk the correct way == you followed exaclty the android.com howto ?

it should work with ubuntu 9.04. Just follow this instructions to setup connection to your phone. mainly create rule for you device in udev.
http://developer.android.com/guide/developing/device.html
If you're developing on Ubuntu Linux, you need to add a rules file:
1. Login as root and create this file: /etc/udev/rules.d/50-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+rx /etc/udev/rules.d/50-android.rules
reboot, then if you are still having problem after this, one more thing to try to start server swith sudo.
adb kill-server
sudo adb start-server

knaries2000 said:
it should work with ubuntu 9.04. Just follow this instructions to setup connection to your phone. mainly create rule for you device in udev.
http://developer.android.com/guide/developing/device.html
If you're developing on Ubuntu Linux, you need to add a rules file:
1. Login as root and create this file: /etc/udev/rules.d/50-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+rx /etc/udev/rules.d/50-android.rules
reboot, then if you are still having problem after this, one more thing to try to start server swith sudo.
adb kill-server
sudo adb start-server
Click to expand...
Click to collapse
I think I did this part, I will double check. I did try sudo adb start-server, that didn't work. I will double check the rest. Thank you.

Oh that's why I never did it, I cannot find a rule for jaunty, only hardy, dapper, and gutsy.. I'll do more searching. Thanks for the idea.

Okay it works now. This is what I get
Code:
[email protected]:~$ adb start-server
* daemon not running. starting it now *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
HT845GZ28769 device
[email protected]:~$ adb shell
# ls
cache init.goldfish.rc sbin
data init.rc sdcard
default.prop init.trout.rc sqlite_stmt_journals
dev proc sys
etc root system
init runme.sh
#
THIS IS WHAT I DID:
created 2 files on my desktop named:
50-android.rules
51-android.rules
Then I edited both files to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Then I opened terminal and did this
Code:
[email protected]:~$sudo mv /home/chris/desktop/50-android.rules /etc/udev/rules.d
[email protected]:~$sudo mv /home/chris/desktop/51-android.rules /etc/udev/rules.d
Then I rebooted and It all worked. I am runnung ubuntu 9.04 jaunty jakelope(sp?)
Thanks for everyones help. Hope this helps someone else.

CBowley said:
Okay it works now. This is what I get-------
Thanks for everyones help. Hope this helps someone else.
Click to expand...
Click to collapse
Thank you so much, this works perfectly. Bump for someone else finding this who needs it.

Yes it has to be rule 51, not 50 with Jaunty. Google doc is not up to date yet.
see this thread :
http://groups.google.com/group/andr...read/thread/ab6e89c4b51cd905/a05c2a749cd55b88
> this was in /etc/udev/rules.d/50-android.rules
> But it seems to also work like this : (method for Ubuntu 9.04 :
> http://www.frandroid.com/2371/ubuntu-904-et-android/ )
> -> in /etc/udev/rules.d/51-android.rules :
> SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4", MODE=”0666"
Ubuntu 9.04 already has a rules/50-something file so you need to make
sure that the android rule is > 50. Otherwise whatever you define gets
reset. We should update the doc to just state rule/51-android.rules
which will work right now till the base configuration changes once
again
> Also take care if you copy/paste this rule : looks like double quotes
> (") may be wrongly copied from html page, and then it did not work for
> me before I retyped them.
Hmm thanks for the info. That's a new one.

Edit
Ok sorry a little OT, but I responded to this because I did not see an answer posted. I Seem to be having problems with posts showing up when I am logged in... but not when I am logged out... really weird. After I logged out at least another dozen posts showed up in this thread.

you need to change the rule from 50 to 51 on ubuntu 9.4
didnt realise the answer was posted sorry. but its def the right answer

CBowley said:
I am running ubuntu 9.04. I have eclipse and the Android s.d.k. set up and running perfectly. But I cannot figure out how to setup a.d.b.
I apologize for the new post, but I promise I have searched for hours on this forum and Google. All I found was info on installing on Windows, and fixing a.d.b that used to work but won't work now after updating to 9.04. Anybody have a tutorial or a fix that I might have missed? Thanks in advance.
Click to expand...
Click to collapse
sudo bash -c "echo SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"0bb4\", MODE=\"0666\" > /etc/udev/rules.d/51-android.rules"
sudo /etc/init.d/udev restart
killall adb
adb shell

Adb installation instructions for Ubuntu

The Absent-Minded Professor and I just installed adb on Ubuntu; here is how to set up adb on Ubuntu Linux, Gutsy through Maverick.
Our port of the BX theme to CM6 stable is forthcoming.
first command after installing and updating sdk and extracting the tgz file to your home directory is== sudo gedit /etc/udev/rules.d/70-android.rules
NOTE: In the above file replace ## with the number 50 if you are running Gusty/Hardy/Dapper (50-android.rules) or with the number 70 if you are running Karmic Koala/Lucid Lynx(70-android.rules
after the window pops write this in the file==SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″ then save and close
the follwing commands is== sudo chmod a+rx /etc/udev/rules.d/70-android.rules
Then reboot.
Open a terminal and type== sudo gedit .bashrc
The file contents should be as follows== export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
Save and close.
Run the command== adb devices
If you see a serial number like this:
List of devices attached
HT99PHF02521 device
then you are done.
If you get error messages such as "no such command," cd to /home/user/android-sdk-linux_x86/tools and use the adb commands in this way:
./adb devices
./adb shell
etc.
If you get an error message here referencing insufficient device permissions, do the following:
./adb kill-server
sudo ./adb start-server
Now ./adb devices should work.
Courtesy of laie1472 and The Absent Minded Professor
Thanks to Esau Silva (http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/) and Tobias Eisentrager (http://www.mail-archive.com/[email protected]/msg14211.html).

[Q] Want to go back to previous stock version DI18 i believe need help!!

Ok, so I updated my phone manually to 2.2.1 and I just found out its a test build not actual update. So I wana go back to previous version before this one and just use the stock 2.1 that was already on my phone. I don't know what odin is or anything like that but i updated entirelly from my phone no comp needed. I just installed update.zip from my sd card and it worked fine. So can I do the same thing and just download the previous version and flash it real quick back to 2.1 like it was? And what's this modem update thin.g I need to do?

TorelliB said:
Ok, so I updated my phone manually to 2.2.1 and I just found out its a test build not actual update. So I wana go back to previous version before this one and just use the stock 2.1 that was already on my phone. I don't know what odin is or anything like that but i updated entirelly from my phone no comp needed. I just installed update.zip from my sd card and it worked fine. So can I do the same thing and just download the previous version and flash it real quick back to 2.1 like it was? And what's this modem update thin.g I need to do?
Click to expand...
Click to collapse
First download DI18 from :http://forum.xda-developers.com/showthread.php?t=794138
then follow the instructions at : http://forum.xda-developers.com/showthread.php?t=773032
in step 5, obviously use the DI18 file you downloaded instead of the file step 5 says.

For you those going back to stock or are stock and u flashed 2.2 and want to downgrade or resort back to stock use this method.
Rooted/clockwork users skip the first step...
1. Do the one click root/clockwork/etc Here
2. Then Flash the zip file Here
3. Then flash the get rid of clockwork zip Here
4. Your are back to stock without using odin yay!!!
The get rid of clockwork doesnt work... might have to ask dcrocks to reupload or if someone has it that would be great.
I use the d118 stock zip and it removes root...

davidrules7778 said:
For you those going back to stock or are stock and u flashed 2.2 and want to downgrade or resort back to stock use this method.
Rooted/clockwork users skip the first step...
1. Do the one click root/clockwork/etc Here
2. Then Flash the zip file Here
3. Then flash the get rid of clockwork zip Here
4. Your are back to stock without using odin yay!!!
I use the d118 stock zip and it removes root...
Click to expand...
Click to collapse
Link 3 doesn't work FYI

kenvan19 said:
Link 3 doesn't work FYI
Click to expand...
Click to collapse
Thanks ill have to find that file elsewhere..
The get rid of clockwork doesnt work... might have to ask dcrocks to reupload or if someone has it that would be great.

davidrules7778 said:
For you those going back to stock or are stock and u flashed 2.2 and want to downgrade or resort back to stock use this method.
Rooted/clockwork users skip the first step...
1. Do the one click root/clockwork/etc Here
2. Then Flash the zip file Here
3. Then flash the get rid of clockwork zip Here
4. Your are back to stock without using odin yay!!!
The get rid of clockwork doesnt work... might have to ask dcrocks to reupload or if someone has it that would be great.
I use the d118 stock zip and it removes root...
Click to expand...
Click to collapse
When trying to do step 2, I cannot flash the "modem updater" part of it, any ideas? clockwork just tells me that "installation is aborted (status 7)"

So I'm home now and trying this method but I can't find any instructions on how to use oneclickroot on a mac, anyone have a link?

Actually, I was able to find out how to get the stuff working but now I'm stuck trying to get it to find my phone. I know its a dumb question but no matter what I do it says looking for phone. Any tips?
Here is what my log says:
Original one click made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue...
Starting adb server
./run.sh: line 23: adb: command not found
./run.sh: line 26: adb: command not found
./run.sh: line 33: adb: command not found
./run.sh: line 35: adb: command not found
Phone is not connected. Press any key to continue.\n./run.sh: line 35: adb: command not found

kenvan19 said:
Actually, I was able to find out how to get the stuff working but now I'm stuck trying to get it to find my phone. I know its a dumb question but no matter what I do it says looking for phone. Any tips?
Here is what my log says:
Original one click made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue...
Starting adb server
./run.sh: line 23: adb: command not found
./run.sh: line 26: adb: command not found
./run.sh: line 33: adb: command not found
./run.sh: line 35: adb: command not found
Phone is not connected. Press any key to continue.\n./run.sh: line 35: adb: command not found
Click to expand...
Click to collapse
I am having this exact same issue

edit: too many tabs open. *facepalm*

kenvan19 said:
Actually, I was able to find out how to get the stuff working but now I'm stuck trying to get it to find my phone. I know its a dumb question but no matter what I do it says looking for phone. Any tips?
Here is what my log says:
Original one click made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue...
Starting adb server
./run.sh: line 23: adb: command not found
./run.sh: line 26: adb: command not found
./run.sh: line 33: adb: command not found
./run.sh: line 35: adb: command not found
Phone is not connected. Press any key to continue.\n./run.sh: line 35: adb: command not found
Click to expand...
Click to collapse
I recently wiped my computer, so I don't have the one-click right in front of me. Will you open run.sh in a text editor and find out what is on lines 23, 26, 33, and 35?

I've got the same issue "adb: command not found" after installing EB13 and attempting to re-root.
Lines 23, 26, 33, 35:
Code:
:23 $adb kill-server
:26 $adb start-server
:33 state=$($adb get-state | tr -d '\r\n[:blank:]')
:35 state=$($adb get-state | tr -d '\r\n[:blank:]')
Some context might be useful, lines 20 - 41:
Code:
echo -e "\nStarting adb server"
$adb kill-server
which sudo > /dev/null 2>&1
if [ $? -eq 0 ]; then
$adb start-server
else
sudo $adb start-server
if [ $? -ne 0 ]; then
$adb start-server
fi
fi
state=$($adb get-state | tr -d '\r\n[:blank:]')
while [ "$state" != device ]; do
state=$($adb get-state | tr -d '\r\n[:blank:]')
read -n1 -s -p "Phone is not connected. Press any key to continue.\n"
done
root=$($adb shell id | grep uid=0)
if [ -z "$root" ]; then
echo -e "\nCopy and run the exploit (may take up to two minutes)"

2.2: cannot downgrade

hi.
i'm trying to root my HTC Legend (stock froyo) but i'm stuck to the downgrade step.
i've created the gold card but when i try to downgrade i get always this:
Code:
C:\Program Files (x86)\Android\android-sdk\tools>crackin.bat
"Copying tools"
2301 KB/s (698452 bytes in 0.296s)
1190 KB/s (76044 bytes in 0.062s)
2413 KB/s (655360 bytes in 0.265s)
"Freeing primary PERM linker"
rm failed for /data/DxDrm/fuse/*, No such file or directory
rm failed for /data/DxDrm/fuse, No such file or directory
rmdir failed for /data/DxDrm/fuse/, No such file or directory
cannot create /data/DxDrm/fuse: directory nonexistent
Unable to chmod /data/DxDrm/fuse: No such file or directory
"Freeing secondary PERM linker"
rmdir failed for /data/DxDrm/fuse/, No such file or directory
rmdir failed for /data/DxDrm, No such file or directory
link failed Permission denied
"Rebooting to normal mode to unlock CHMOD links"
rmdir failed for /data/dontpanic, Permission denied
rm failed for /data/DxDrm, No such file or directory
link failed File exists
link failed Permission denied
"Rebooting to normal mode to downgrade ROM"
/dev/mtd/mtd0: Permission denied
cr--rw---- 1 1001 2002 90, 0 Mar 5 17:17 /dev/mtd/mtd0
error writing misc: Permission denied
"Freeing links"
rm failed for /data/DxDrm, No such file or directory
rm failed for /data/dontpanic, Permission denied
any idea?

- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.

same problem here..try many way as stated!!

Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
thanks for your answer.
please, tell me if i'm right.
i should follow these downgrade steps http://forum.xda-developers.com/showthread.php?t=725430 till the end when i keep receiving the reported error, then i should install visionary, temproot, and from a command prompt (starting from the "tools" directory of the android SDK? and the misc1-2.img goes there?) i should type those command.
and then?
run the RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe?

thanks man!
i did it!

I get error [171] anyone have any idea what is the reason ??
please hepl
I tried every way i managed o find
hboot - 1.00.0000
radio-7.13.35.05
soft 3.14.161.1
kernel 2.6.32.17

Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
i get permissions denied on the last step
/data/local/flash_image misc /data/local/misc1-2.img
help please?

Ohh c'mom dude! What does "adb shell" return? What does "su" return?
Sent from my HTC Legend

chris.chhoeu said:
i get permissions denied on the last step
/data/local/flash_image misc /data/local/misc1-2.img
help please?
Click to expand...
Click to collapse
Did you get the # symbol after the su command? If not, then you have to do temp root again.

What does ADB say? Do you have Debug Mode eneabled?
Sent from my HTC Legend using XDA App

temproot on boot or temproot now pls ?? thanks m8

"Temproot now"
Sent from my HTC Legend using XDA Premium App

[Q] [GUIDE] Downgrade G2 (2.3.3) & DZ (2.3.3) & mT4g (2.3.4) w/ S-ON to Stock Froyo

[Q] [GUIDE] Downgrade G2 (2.3.3) & DZ (2.3.3) & mT4g (2.3.4) w/ S-ON to Stock Froyo
i would like to downgrade using this thread. the sdk is not recognizing that i have installed jdk. is there anyone out there that would be willing to help me out . i searched and found there is no method to root 2.3.4 yet. i have not had any luck getting past installing sdk. i would appreciate help.

dirtyreturn said:
i would like to downgrade using this thread. the sdk is not recognizing that i have installed jdk. is there anyone out there that would be willing to help me out . i searched and found there is no method to root 2.3.4 yet. i have not had any luck getting past installing sdk. i would appreciate help.
Click to expand...
Click to collapse
I used the sdk zipped file and extracted it to local disk c:

if you don't mind another couple questions WOLF26915. im using windows 7 command prompt . am i supposed to? so far i got to
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\mine>cd\
C:\>cd androidsdk
C:\androidsdk> cd androidsdk\platform-tools\
The system cannot find the path specified.
C:\androidsdk>cd platform-tools
C:\androidsdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\androidsdk\platform-tools>adb push fre3vo / androidsdk/data/local/tmp
Android Debug Bridge version 1.0.26
-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. Overrides ANDROID_SERI
AL
environment variable.
-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
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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 forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
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
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
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 reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP 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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\androidsdk\platform-tools>

dirtyreturn said:
if you don't mind another couple questions WOLF26915. Ok, i downloaded the sdk zip file placed it to c:/, right now is is installing updates or recommendations. do you think i will be set to use after it's done?
Click to expand...
Click to collapse
ya you should be good but if you are not here is a guide to help setup adb/fastboot http://forum.xda-developers.com/showthread.php?t=928370

if you could take a look at updated post.

dirtyreturn said:
if you don't mind another couple questions WOLF26915. im using windows 7 command prompt . am i supposed to? so far i got to
C:\adb>adb devices
List of devices attach
SH12SRM02177 device
C:\adb>adb shell
$ adb push fre3vo data
adb push fre3vo data/l
adb: permission denied
$ adb shell cat /dev/m
adb shell cat /dev/msm
adb: permission denied
$
Click to expand...
Click to collapse
ok you are doing it wrong type this
adb push fre3vo /data/local/tmp (hit enter)
adb shell (hit enter)
then you should see $ now type
chmod 777 /data/local/tmp/fre3vo (hit enter)
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF (hit enter)
then go to next step

i get permission denied. did i need to create folders for this data->local ->tmp ?

dirtyreturn said:
i get permission denied. did i need to create folders for this data->local ->tmp ?
Click to expand...
Click to collapse
ok if you don't mind pm me your number maybe we can get it done

s should be on right? is gingerbreak alright to use? hboot 0.86.0000, radio 26.11.04.03_M. Update is unzipping. is ROM Manager reliable for a new user?