Can't get my Evo to be recognized on ubuntu

igotsanevo4g

Retired Moderator
Jul 31, 2010
3,395
601
113
I got my Ubuntu/Xp dual booting from two hard drives today, all is well there, but when i go grab the SDK and stuff's, i cannot get my Evo to be seen by it at all!
I have Java installed, i navigate to the tools directory by cd ~/Desktop/AndroidSDK/tools and it doesnt recognize any adb commands or even recognize my phone is hooked up.

Most likely just a little something i dont know about, but ive searched high and low, and i cant find my answer anywhere.

Thoughts?
 
Well i tried "adb reboot", "#adb reboot", and some other random guesses.

How should i be entering them?
 
Okay in linux you have to kill the server and then start the server as root. Also you will use ./ in front of any adb commands.So here's a couple commands to get you going.I suggest maybe creating a adb.text file so you can just use is as a short cut and copy&paste.I know im lazy and get tired of typing them out.Also terminal remembers almost everything you enter so just scrolling up can help.
To get linux to see your phone do these commands in the tools dir.
./adb kill-server
sudo ./adb start-server
./adb devices
 
  • Like
Reactions: igotsanevo4g
Okay in linux you have to kill the server and then start the server as root. Also you will use ./ in front of any adb commands.So here's a couple commands to get you going.I suggest maybe creating a adb.text file so you can just use is as a short cut and copy&paste.I know im lazy and get tired of typing them out.Also terminal remembers almost everything you enter so just scrolling up can help.
To get linux to see your phone do these commands in the tools dir.
./adb kill-server
sudo ./adb start-server
./adb devices

You are the f'in bomb beezy :D
 
Couple tricks for you fellows

Add sdk to your path

Code:
nano -w ~/.bashrc

This opens your .bashrc in nano. You can use any editor you like.
At the bottom of the file, add these two lines:
Code:
#SDK path
export PATH=${PATH}:/path/to/your/sdk/tools/folder

log off, then log back in. Now you don't have to navigate to the android-sdk/tools/ folder to run any commands.

Note that your path is different, so ./ isn't needed any more:
use
Code:
adb devices
instead of
Code:
./adb devices
if you're in a different folder

Note #2 -- depending on your particular setup, you may need to remove the brackets in your bashrc line:
Code:
export PATH=$PATH:/path/to/your/sdk/tools/folder
but try with the brackets first.

Setting up udev for HTC phones
from your term:

Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
gEdit should open (as root!) a blank file. Add this line:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Save, and close gEdit.

at prompt:
Code:
sudo /etc/init.d/udev restart

Now you don't have to kill/start the server to use adb anymore
 
Awesome. Couple more of us linux folks and we might have to start a linux tips and tricks forum ;)

We Might need this...

The only Reason Im running Windows now is for the SDK

If I could nix this I could re partition my drive specifically just for linux

Please Please Please :D
 
Awesome. Couple more of us linux folks and we might have to start a linux tips and tricks forum ;)

I would also like a forum for linux, I recently started using Ubuntu and would like to learn as much as I can.