[HOWTO] Linux ADB, fastboot, mass storage

sado1 · January 2nd, 2010, 02:46 PM

Thanks to screaminbug for clue about udev rules.
On Android 2.x modified adb file may be no longer needed, 1.x probably does still need it though - try without changing adb file first.

1. Download and unpack somewhere Linux SDK: Android SDK | Android Developers and install Platform Tools with SDK Manager that you can run in terminal with

Code:

tools/android

(there should be some way to install them in console with that tool, can't check it out now since I'm not on Linux at the moment... try 'tools/android help')

2.Download fastboot for Linux: HTC - Developer Center and adb: http://floe.butterbrot.org/external/adb.gz. Copy adb&fastboot to the sdk/platform-tools folder; cd to that folder in terminal and add necessary permissions:

Code:

chmod +x adb
chmod +x fastboot

3. In folder /etc/udev/rules.d/ create files(don't forget to replace user with your username!):
50-android.rules

Code:

SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666", OWNER="user"

90-android.rules

Code:

SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666", OWNER="user"

4. Refresh udev rules:

Code:

reload udev

5. In file /home/user/.bashrc (replace user with your username) add line:

Code:

export PATH=${PATH}:/home/user/android-sdk-linux_x86/tools:/home/user/android-sdk-linux_x86/platform-tools

Replace /home/user/android-sdk-linux_x86 with your sdk directory path.
6. Log out&in to the terminal/start new terminal window if in X. Everything should work now.

Code:

sado@sado-pc ~/ $ adb devices
List of devices attached 
I7500T9UxvXGy9F    device

sado@asdf-pc:~$ fastboot devices
????????????    fastboot

Rastaman-FB · January 3rd, 2010, 04:16 AM

cool, ill link this in the stickies
nice work

turkievicz · January 3rd, 2010, 09:05 AM

Congratulation....Very good, finaly I WIN....hehehehe

Mr.DNA · January 5th, 2010, 06:09 AM

Does this mean it is possible to update the firmware via Linux?

Andronix · January 5th, 2010, 06:56 AM

Quote:

Originally Posted by Mr.DNA

Does this mean it is possible to update the firmware via Linux?

It's possible, someone somewhere posted exact commands to untar the odin files directly.

o2cool · January 11th, 2010, 02:16 PM

I keep getting command not found and when i go to the tools dir and run ./adb i get bash: ./adb: No such file or directory

Not sure whats going on thanks for any ideas

turkievicz · January 11th, 2010, 02:21 PM

Quote:

Originally Posted by o2cool

I keep getting command not found and when i go to the tools dir and run ./adb i get bash: ./adb: No such file or directory

Not sure whats going on thanks for any ideas

The adb are in the sdk/tools dir ?
Did you make: chmod +x adb ?

o2cool · January 11th, 2010, 02:24 PM

Quote:

Originally Posted by turkievicz

The adb are in the sdk/tools dir ?
Did you make: chmod +x adb ?

Yes as per directions above even tried 666 all permissions

turkievicz · January 11th, 2010, 02:32 PM

Quote:

Originally Posted by o2cool

Yes as per directions above even tried 666 all permissions

Take a look:

Code:

[root@p185191 tools]# chmod 666 adb
[root@p185191 tools]# ./adb
bash: ./adb: Permissão negada
[root@p185191 tools]# chmod 755 adb
[root@p185191 tools]# ./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 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 updated.

  - If it is "system" or "data", only the corresponding partit

o2cool · January 11th, 2010, 02:33 PM

In my attempt to figure it out i did change a few things in the rules files such as: usb 1-6: New USB device found, idVendor=0bb4, idProduct=0c01

so i changed the idVendor and idProduct to match what was connected

o2cool · January 11th, 2010, 02:35 PM

:~/android-sdk-linux_86/tools$ chmod 755 adb
:~/android-sdk-linux_86/tools$ chmod 755 fastboot
:~/android-sdk-linux_86/tools$ ./adb
bash: ./adb: No such file or directory

turkievicz · January 11th, 2010, 02:37 PM

Quote:

Originally Posted by o2cool

:~/android-sdk-linux_86/tools$ chmod 755 adb
:~/android-sdk-linux_86/tools$ chmod 755 fastboot
:~/android-sdk-linux_86/tools$ ./adb
bash: ./adb: No such file or directory

Did you try as root ?

o2cool · January 11th, 2010, 02:39 PM

Quote:

Originally Posted by turkievicz

Did you try as root ?

root:~/android-sdk-linux_86# cd tools/
root:~/android-sdk-linux_86/tools# chmod 755 adb
root:~/android-sdk-linux_86/tools# chmod 755 fastboot
root:~/android-sdk-linux_86/tools# ./adb
bash: ./adb: No such file or directory

o2cool · January 11th, 2010, 02:43 PM

Quote:

Originally Posted by o2cool

root@Elite:~/android-sdk-linux_86# cd tools/
root:~/android-sdk-linux_86/tools# chmod 755 adb
root:~/android-sdk-linux_86/tools# chmod 755 fastboot
root:~/android-sdk-linux_86/tools# ./adb
bash: ./adb: No such file or directory

this might be a dumb question but i am running a 64bit OS. i have multilib support so it shouldn't matter

turkievicz · January 11th, 2010, 02:53 PM

I'm using too, a Fedora fc12.x86_64.

sado1 · January 11th, 2010, 03:41 PM

Something is wrong. Can you post 'ls' output from tools folder just to clarify?

o2cool · January 11th, 2010, 05:36 PM

And fixed, sorry for freaking out guys, works great. Thank you everyone for the help!

Rastaman-FB · January 12th, 2010, 02:50 AM

added to Guides

thanks

screaminbug · January 12th, 2010, 03:53 PM

Quote:

Originally Posted by Andronix

It's possible, someone somewhere posted exact commands to untar the odin files directly.

Where? When? How?

OK. Ignore second and third one. Was it on this forum? Can you remember? Maybe you have it in your browser history somewhere? I was searching the web, but couldn't find it anywhere. I've searched entire Internet.

If this is possible it would be great to know how.

Mr.DNA · January 12th, 2010, 06:53 PM

Agreed. I spent a good chunk of time today looking as well, and could not find anything.

Ended up finally taking a flash drive in to a windows machine at work to upgrade to IK5, but it would really be nice to be able to do this from home.

Rastaman-FB · January 13th, 2010, 03:27 AM

could it be this
HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki

screaminbug · January 13th, 2010, 07:58 AM

Quote:

Originally Posted by Rastaman-FB

could it be this
HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki

It's a good read, but I don't think that's it. But I suppose the information of an alternate way of flashing recovery could be useful.

screaminbug · January 24th, 2010, 12:46 PM

If this doesn't work for you for fastboot (wasn't working for me), try putting this in 50-android.rules:

Code:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="d00d", MODE="0666", OWNER="owner"

Where owner is your username.

And reload your udev rules:

Code:

reload udev

Mr.DNA · March 11th, 2010, 08:02 AM

I finally got around to playing with this. I have adb working (I think), but I can't get the recovery.img to flash.

Code:

./adb devices

identifies my phone, however

Code:

./fastboot flash recovery recovery.img

hangs on < waiting for device >, although my phone boots into fastboot mode without problem.

I have successfully gotten this to work on xp machines before. Currently using Ubuntu 9.10. Any ideas?

edit: I can successfully push/pull files as well.

Mr.DNA · March 11th, 2010, 08:54 AM

doh! this worked:

Code:

sudo ./fastboot flash recovery recovery.img

I am new at this.

puccaso · April 14th, 2010, 09:18 AM

i cant seem to get this to work
?
i followed all the steps,
and nada
i am using revision 5 of the sdk,
i have the 1.6 firmwire on the phone

what do you guys think is the prob?

Mr.DNA · April 15th, 2010, 01:48 AM

There is a lot of variation in the steps to follow, even in this thread. Can you be more specific about what you actually did and at what points you are having troubles?

tomas.splatch · April 26th, 2010, 07:00 AM

I had to download a special patched version for adb, nothing else worked for me. No udev rules required, just unpack and run as root:

http://floe.butterbrot.org/external/adb.gz

sado1 · April 26th, 2010, 02:22 PM

Well, this binary was in this howto before the new SDK release which was supposed to have Galaxy detection problem fixed. Sometimes it worked for me, sometimes not - it's possible that it worked on 1.5 Galaxo and didn't on 2.1 GAOSP and 1.6 Galaxo (it doesn't work in 4.6 and 5.0 recovery too, but fastboot is ok). Anyway thanks for the clue as it works for me now at 1.6 Galaxo

updating howto.

Russ Dill · April 27th, 2010, 05:01 PM

Quote:

Originally Posted by screaminbug

If this doesn't work for you for fastboot (wasn't working for me), try putting this in 50-android.rules:

Code:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="d00d", MODE="0666", OWNER="owner"

Where owner is your username.

And reload your udev rules:

Code:

reload udev

Anyone have a consolekit/policykit integrated rule yet?

confiq · May 14th, 2010, 10:32 AM

Quote:

Originally Posted by o2cool

And fixed, sorry for freaking out guys, works great. Thank you everyone for the help!

how did you fix it?
I'm getting this with strace

Quote:

confiq@confiq-bigcomp:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/confiq/android/android-sdk-linux_86/tools:/home/confiq/android/android-sdk-linux_86/tools/:/home/confiq/android/android-sdk-linux_86/tools
confiq@confiq-bigcomp:~$ strace adb
execve("/home/confiq/android/android-sdk-linux_86/tools/adb", ["adb"], [/* 37 vars */]) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f59154e3000
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40
close(3) = 0
munmap(0x7f59154e3000, 4096) = 0
exit_group(1) = ?
confiq@confiq-bigcomp:~$ file /home/confiq/android/android-sdk-linux_86/tools/adb
/home/confiq/android/android-sdk-linux_86/tools/adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
confiq@confiq-bigcomp:~$ adb
bash: /home/confiq/android/android-sdk-linux_86/tools/adb: No such file or directory

It's interesting it did work few days ago

using ubuntu 64bit 10.4 and it's not 32/64 bit related.
ideas?

confiq · May 14th, 2010, 12:18 PM

Code:

apt-get install ia32-libs

helps!
Why they didn't build for 64 bit?

gastr · June 22nd, 2010, 06:07 PM

hello guys,

thanks for the HOWTO! alas it's not working for me. after modifying the udev rules as above i have working adb but not fastboot. viz:

$ adb devices
List of devices attached
I75009t3k6ty device
$ fastboot devices
$

(ie. nothing returned at all)

i'm not sure what information to post that might by useful :-/

i tried making the modifications to 50-android.rules as suggested by screeminbug, but it didn't help.

any ideas anyone?

thanks!

gastr · June 22nd, 2010, 06:47 PM

oh wait, it's only supposed to print something if the phone is in recovery mode, right? i do get the ????? response shown in the first post if i have booted in recovery mode.

i'm new to this :/

jocala · September 10th, 2010, 11:08 AM

Sorry to bump an old thread, but this howto doesn't seem to work for the Epic 4G. Does anyone have adb/fastboot working for this phone? My distro is Debian sid. adb works great under OS X, btw.

Lelouch · September 10th, 2010, 03:54 PM

Another job for DaSchmarotzer (do your magic).

Btt, sorry friend can't help you there, this IS a Galaxy I7500 thread and I'm sure that no one here has the same phone like you (I'm sorry, if I guessed wrong). Maybe someone on Epic 4G part of the forum can help you. Try your luck there.

jocala · September 10th, 2010, 03:58 PM

Thanks for the reply anyway. Sorry for the mispost

partyelite · May 12th, 2011, 12:15 PM

the link to the fastboot is not working, can anyone post a working link?

confiq · May 13th, 2011, 02:50 AM

Quote:

Originally Posted by partyelite

the link to the fastboot is not working, can anyone post a working link?

HTC - Developer Center

it worked for my Nexus S too...

vivaldi265 · May 21st, 2011, 03:58 PM

This post in awesome. I was a huge help to setup my Captivate to connect with Ubuntu 11.04 as a mass storage device. Massive Big-ups, my youth.

v1nsai · August 5th, 2011, 01:13 PM

Quote:

Originally Posted by confiq

Code:

apt-get install ia32-libs

helps!
Why they didn't build for 64 bit?

Awesome! Thanks for posting this, I was going insane. The "no such file" error is very misleading, that wasn't the problem at all. Just goes to show you, you can't trust the machines *glares at computer*.

adtoes · August 29th, 2011, 11:29 PM

all install went off without a hitch

toews@kidlapp:~/android-sdk-linux_x86/tools$ adb devices
List of devices attached

and that's all it returns....

any ideas ty!!

ps. amaze post!! ty

frank.sposaro · September 22nd, 2011, 10:28 AM

Quote:

Originally Posted by o2cool

And fixed, sorry for freaking out guys, works great. Thank you everyone for the help!

Did he every say how this issue was fixed?
I just did a fresh install of the sdk and now I have the issue

sposaro@mobicommand:~/android-sdk-linux_x86/platform-tools$ ./adb
bash: ./adb: No such file or directory

Any help? I've never seen this issue before.

Thanks

frank.sposaro · September 22nd, 2011, 10:29 AM

That is normal.
You need to make sure that you actually have either a device plugged in, or an emulator running.

EdAndInn · October 22nd, 2011, 01:24 PM

sudo cp adb /usr/bin/.
sudo cp fastboot /usr/bin/.

This way, you will never need to define path for adb.

bradm0 · November 27th, 2011, 02:50 PM

Looking for a current link for fastboot. When I try the two that I see in the thread
Welcome to HTCdev
Welcome to HTCdev

I get redirected to htcdev.com. I've registered and signed in but I can't seem to find it. Thanks.

bradm0 · November 27th, 2011, 03:35 PM

Did some googling and found a post on an ubuntu forum that had fastboot in a post. Worked on my Mandriva 2010 install. Only problem now is adb devices sees my phone but fastboot returns nothing, no errors, not nothing. Any ideas? Thanks.
$ adb devices
List of devices attached
HT0ALHJ11526 device

$ fastboot devices
$

elelab · January 23rd, 2013, 09:50 PM

i switch to root account and fastboot works.

su
fastboot

is this dangerous?