You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.

I thought I would re-post this tutorial as I had a real nightmare setting this up originally, so I hope this helps at least someone out!

Ubuntu: Android SDK, ADB, Fastboot.

There are various great tutorials online to help you set these options for Windows, but the process of setting this up in Ubuntu Linux is rather fragmented across various different forums, and can be rather confusing! This is a tutorial I have put together after having real trouble setting it up myself, after trawling through numerous forums, and getting help from many very helpful folks on various forums!

Tutorial: This will show you how to complete the basic set up of the Android sdk, and then how to enable the 'adb' and 'fastboot' connections so as to allow you to issue commands from the terminal directly to your phone.

1. Extract the 'android_sdk_r05-linux_86.tgz' file to your 'Home' folder and rename it to 'sdk' to make things easier later on.

2. Move the fastboot file in to the 'Tools' folder inside the 'sdk' folder.

3. Now right click on both the 'fastboot' and 'adb' files (inside the tools folder) and choose 'Properties' and then the 'Permissions' tab, and ensure they both have the 'allow executing file as program' box is ticked...Now reboot the computer, sorted!

Now to set up ubuntu to recognize your phone, and the commands in the terminal:

1. Open your 'Home' folder. Press 'Ctrl' & 'H' at the same time to view hidden files, and then open the '.bashrc' file and add the following text to the top of the file:

#AndroidDev PATH
export PATH=$PATH:/home/username/sdk/tools

Obviously you will need to replace 'username' with your own

Save the file and exit.

2. Now log-in as root. Or use the following terminal command to open the 'root - File Browser':

gksudo nautilus

3. Navigate to the following directory in the root filesystem: /etc/udev/rules.d/

Your Nexus One should now be detected! As always if anyone sees anything obviously wrong with this update please let me know, I can confirm I have used this method on both my desktop and laptop running Ubuntu 9.10, and it works fine!!

I had major problems getting fastboot to work, yet adb worked fine in Karmic.

fastboot devices

returned nothing

adb devices

returned my device

Fortunately I have a really good Sun VirtualBox running XP that returned my device with both fastboot and adb, so I used virtual windows to fastboot v1.7.0 recovery.

Unfortunately, trying to push the recovery image to the SD card hung, but the USB indicator on the virtual machine was flashing, so I left it overnight. This morning it was still hung, so I disconnected and used Ubuntu to adb push and it worked fine.

I had major problems getting fastboot to work, yet adb worked fine in Karmic.

fastboot devices

returned nothing

adb devices

returned my device

Fortunately I have a really good Sun VirtualBox running XP that returned my device with both fastboot and adb, so I used virtual windows to fastboot v1.7.0 recovery.

Unfortunately, trying to push the recovery image to the SD card hung, but the USB indicator on the virtual machine was flashing, so I left it overnight. This morning it was still hung, so I disconnected and used Ubuntu to adb push and it worked fine.

I had major problems getting fastboot to work, yet adb worked fine in Karmic.

fastboot devices

returned nothing

adb devices

returned my device

Fortunately I have a really good Sun VirtualBox running XP that returned my device with both fastboot and adb, so I used virtual windows to fastboot v1.7.0 recovery.

Unfortunately, trying to push the recovery image to the SD card hung, but the USB indicator on the virtual machine was flashing, so I left it overnight. This morning it was still hung, so I disconnected and used Ubuntu to adb push and it worked fine.

I don't know why I had drama's, but this is how I got around it.

In the past when I have had problems getting fastboot to work, I use the following commands from the terminal:

My /etc/udev/rules.d/ folder contains other files... '70-persistent-cd.rules' and '70-persistent-net.rules' so if I were to guess, the filename should probably follow suit.?. which would mean '70-android.rules' should be correct, but does not yield a working solution...

My /etc/udev/rules.d/ folder contains other files... '70-persistent-cd.rules' and '70-persistent-net.rules' so if I were to guess, the filename should probably follow suit.?. which would mean '70-android.rules' should be correct, but does not yield a working solution...

Any more hints?

With 10.4 I had a problem to automount any device on usb. Also adb and fastboot didn't work. After starting PC in BIOS and disabling and reanabling all USB settings ewerything runs fine. It was posted in a german ubuntu forum

I had major problems getting fastboot to work, yet adb worked fine in Karmic.

fastboot devices

returned nothing

adb devices

returned my device

Fortunately I have a really good Sun VirtualBox running XP that returned my device with both fastboot and adb, so I used virtual windows to fastboot v1.7.0 recovery.

Unfortunately, trying to push the recovery image to the SD card hung, but the USB indicator on the virtual machine was flashing, so I left it overnight. This morning it was still hung, so I disconnected and used Ubuntu to adb push and it worked fine.

I don't know why I had drama's, but this is how I got around it.

Your device must in in FASTBOOT mode for fastboot command to work. adb only requires your device to be in USB Debug mode. So it can see your device after it fully booted.

Also: Note to Moderators, it may be worth moving this thread to another area of the forums as it is not really just for HTC Magic, I originally posted this before all the other forums popped up! Many thanks!

I also created various rules in /etc/udev/rules.d (which apparently is only for older Ubuntu distros but some got it to work that way with 10.04) as well as /lib/udev/rules.d
I've given those rules names from 51-android.rules to 70-android.rules to 11-android.rules in my despair.
Creating new rules with udev or restarting adb just doesn't seem change the fact that fastboot doesn't see my phone at all.

Back to darn WinXP in virtualbox. And I thought I had finally gotten rid of Windows.