[HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux

BombaMyte said:

@BreakingTheCycle: I've already set up my SDK and whatnot, but I can reinstall Ubuntu 9.10, and try this method. TBH, I used bits and pieces of several SDK installation tutorials to get it up and running. Hopefully this method will work. I'll try it after the game, about 30 mins...

EDIT: Okay, I followed the directions listed. Once you get to setting up the partition, I get that same error. So instead of naming the partition /AndroidSDK, I just selected "/" from the drop-down menu. Installation continues, yada-yada-yada, open Terminal, adb shell, success.

Click to expand...

Click to collapse

dancerobot said:

I am running Ubuntu Jaunty 64-bit and I have an HTC Magic. I could get fastboot to work but I could not get adb to ever detect the device.

Finally, last night I found some additional rules that needed to be added to the android-rules files that did the trick! Also, in the time I was fiddling with it, I renamed my file 90-anroid-rules on someone's advice, I don't know if that is necessary but it is working for me so I am leaving it alone

So, the contents of my /etc/udev/rules.d/90-android-rules files is:

Code:

SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c01",SYMLINK+="android_fastboot"

I hope this helps some get adb to detect your device!

Click to expand...

Click to collapse

Breakthecycle2 said:

Is my .bashrc file correct?

#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
[ -z "$PS1" ] && return

# don't put duplicate lines in the history. See bash(1) for more options
# don't overwrite GNU Midnight Commander's setting of `ignorespace'.
HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi

# some more ls aliases
#alias ll='ls -l'
#alias la='ls -A'
#alias l='ls -CF'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
. /etc/bash_completion
fi

Click to expand...

Click to collapse

Breakthecycle2 said:

Ok, so I added rule 51, did all the steps for 9.10 needed. I have the sdk file in my home folder. I have tried everything and still cannot get adb to be recognized. It's runs fine on my vista partition, but not for ubuntu. Any ideas at all?

Click to expand...

Click to collapse

Ekril said:

http://developer.android.com/guide/developing/device.html

i found it here

Click to expand...

Click to collapse