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.

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.

From GNU/Linux distributions repositories¶

Debian¶

sudo apt-get install android-tools-adb

Parabola¶

sudo pacman -S android-tools

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 Replicant release key of the latest version to your GPG keyring
3. Check the signature of the adb tool:

gpg --armor --verify path/to/adb.asc path/to/adb

4. Make sure the check succeeds, do not run the binary if it doesn't!
5. Check the checksum of the adb tool:

sha256sum -c tools.sha256

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:

chmod a+x adb

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.

From GNU/Linux distributions repositories¶

Debian¶

sudo apt-get install android-tools-fastboot

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 Replicant release key of the latest version to your GPG keyring
3. Check the signature of the fastboot tool:

gpg --armor --verify path/to/fastboot.asc path/to/fastboot

4. Make sure the check succeeds, do not run the binary if it doesn't!
5. Check the checksum of the fastboot tool:

sha256sum -c tools.sha256

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:

chmod a+x fastboot

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.

From GNU/Linux distributions repositories¶

Debian¶

sudo apt-get install heimdall-flash

Parabola¶

sudo pacman -S heimdall

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 Replicant release key of the latest version to your GPG keyring
3. Check the signature of the heimdall tool:

gpg --armor --verify path/to/heimdall.asc path/to/heimdall

4. Make sure the check succeeds, do not run the binary if it doesn't!
5. Check the checksum of the heimdall tool:

sha256sum -c tools.sha256

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:

chmod a+x heimdall

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.

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 Replicant release key of the latest version to your GPG keyring
3. Check the signature of the mkbootimg and unpackbootimg tools:

gpg --armor --verify path/to/mkbootimg.asc path/to/mkbootimg
gpg --armor --verify path/to/unpackbootimg.asc path/to/unpackbootimg

4. Make sure the checks succeed, do not run the binaries if they don't!
5. Check the checksum of the tools:

sha256sum -c tools.sha256

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:

chmod a+x mkbootimg
chmod a+x unpackbootimg