h1. Tools installation

This page explains how to install the various tools used with Replicant. It is assumed that you are running a GNU/Linux operating system.

h2. ADB

ADB can be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools.
Note: you may need to run ADB as root if your current user doesn't have USB access privileges.

h3. From GNU/Linux distributions repositories

h4. Debian

<pre>
sudo apt-get install android-tools-adb
</pre>

h4. Parabola

<pre>
sudo pacman -S android-tools android-udev
</pre>

h3. From our released tools

1. Download the @adb@ tool, the @adb.asc@ signature and the checksum from [[ReplicantImages]] for the latest image
2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to your GPG keyring
3. Check the signature of the @adb@ tool:
<pre>
gpg --armor --verify path/to/adb.asc path/to/adb
</pre>
4. Make sure the check succeeds, *do not run the binary if it doesn't*!
5. Check the checksum of the @adb@ tool:
<pre>
sha256sum -c tools.sha256
</pre>
6. Make sure the check succeeds for @adb@, *do not run the binary if it doesn't*!

As @adb@ is built as a 32 bit binary, you will need to install compatibility libraries for 32 bits executables if your computer is running on a 64 bit architecture.
7. Make sure @adb@ can be executed:
<pre>
chmod a+x adb
</pre>

h2. Fastboot

Fastboot can be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools.
Note: you may need to run fastboot as root if your current user doesn't have USB access privileges.

h3. From GNU/Linux distributions repositories

h4. Debian

<pre>
sudo apt-get install android-tools-fastboot
</pre>

h3. From our released tools

1. Download the @fastboot@ tool, the @fastboot.asc@ signature and the checksum from [[ReplicantImages]] for the latest image
2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to your GPG keyring
3. Check the signature of the @fastboot@ tool:
<pre>
gpg --armor --verify path/to/fastboot.asc path/to/fastboot
</pre>
4. Make sure the check succeeds, *do not run the binary if it doesn't*!
5. Check the checksum of the @fastboot@ tool:
<pre>
sha256sum -c tools.sha256
</pre>
6. Make sure the check succeeds for @fastboot@, *do not run the binary if it doesn't*!

As @fastboot@ is built as a 32 bit binary, you will need to install compatibility libraries for 32 bits executables if your computer is running on a 64 bit architecture.
7. Make sure @fastboot@ can be executed:
<pre>
chmod a+x fastboot
</pre>

h2. Heimdall

Heimdall can be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools.
Note: you may need to run heimdall as root if your current user doesn't have USB access privileges.

h3. From GNU/Linux distributions repositories

h4. Debian

<pre>
sudo apt-get install heimdall-flash
</pre>

h4. Parabola

<pre>
sudo pacman -S heimdall
</pre>

h3. From our released tools

1. Download the @heimdall@ tool, the @heimdall.asc@ signature and the checksum from [[ReplicantImages]] for the latest image
2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to your GPG keyring
3. Check the signature of the @heimdall@ tool:
<pre>
gpg --armor --verify path/to/heimdall.asc path/to/heimdall
</pre>
4. Make sure the check succeeds, *do not run the binary if it doesn't*!
5. Check the checksum of the @heimdall@ tool:
<pre>
sha256sum -c tools.sha256
</pre>
6. Make sure the check succeeds for @heimdall@, *do not run the binary if it doesn't*!

As @heimdall@ is built as a 32 bit binary, you will need to install compatibility libraries for 32 bits executables if your computer is running on a 64 bit architecture.
7. Make sure @heimdall@ can be executed:
<pre>
chmod a+x heimdall
</pre>

h2. mkbootimg and unpackbootimg

@mkbootimg@ and @unpackbootimg@ can be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools.
Note: Older versions of @unpackbootimg@ are called @unbootimg@ and behave differently.

h3. From our released tools

1. Download the @mkbootimg@ and @unpackbootimg@ tools, the @mkbootimg.asc@ and @unpackbootimg.asc@ signatures and the checksum from [[ReplicantImages]] for the latest image
2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to your GPG keyring
3. Check the signature of the @mkbootimg@ and @unpackbootimg@ tools:
<pre>
gpg --armor --verify path/to/mkbootimg.asc path/to/mkbootimg
gpg --armor --verify path/to/unpackbootimg.asc path/to/unpackbootimg
</pre>
4. Make sure the checks succeed, *do not run the binaries if they don't*!
5. Check the checksum of the tools:
<pre>
sha256sum -c tools.sha256
</pre>
6. Make sure the check succeeds for @mkbootimg@ and @unpackbootimg@, *do not run the binary if it doesn't*!

As @mkbootimg@ and @unpackbootimg@ are built as 32 bit binaries, you will need to install compatibility libraries for 32 bits executables if your computer is running on a 64 bit architecture.
7. Make sure @mkbootimg@ and @unpackbootimg@ can be executed:
<pre>
chmod a+x mkbootimg
chmod a+x unpackbootimg
</pre>