ToolsInstallation » History » Revision 15
Revision 14 (Denis 'GNUtoo' Carikli, 11/28/2019 10:19 PM) → Revision 15/19 (Denis 'GNUtoo' Carikli, 11/28/2019 10:41 PM)
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 the tools ADB as root if your current user doesn't have USB access privileges. h2. h3. From GNU/Linux distributions repositories Many distributions already have packages for the most common tools h4. Debian h3. <pre> sudo apt-get install android-tools-adb </pre> h4. Parabola <pre> sudo pacman -S android-tools android-udev heimdall </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-adb android-tools-fastboot heimdall-flash </pre> h2. Installing it from Replicant h3. From our released tools Some of the tools are also built with the Replicant releases. 1. Download the @adb@, @fastboot@, @heimdall@, @mkbootimg@ @fastboot@ tool, the @fastboot.asc@ signature and @unpackbootimg@ tools, with their corresponding @.asc@ signatures files the checksum from [[ReplicantImages]] for the latest image. 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 each tools: @fastboot@ tool: <pre> gpg --armor --verify path/to/adb.asc path/to/adb gpg --armor --verify path/to/fastboot.asc path/to/fastboot gpg --armor --verify path/to/heimdall.asc path/to/heimdall </pre> gpg --armor --verify path/to/mkbootimg.asc path/to/mkbootimg 4. Make sure the check succeeds, *do not run the binary if it doesn't*! gpg --armor --verify path/to/unpackbootimg.asc path/to/unpackbootimg 5. Check the checksum of the @fastboot@ tool: <pre> sha256sum -c tools.sha256 </pre> 4. 6. Make sure the check succeeds, succeeds for @fastboot@, *do not run the binary if it doesn't*! As the tools are @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. 5. 7. Make sure tools @fastboot@ can be executed: <pre> chmod a+x adb chmod a+x fastboot chmod a+x </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> chmod a+x mkbootimg 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 unpackbootimg heimdall </pre> 6. You h2. mkbootimg and unpackbootimg @mkbootimg@ and @unpackbootimg@ can now use be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools. As they weren't installed in Note: Older versions of @unpackbootimg@ are called @unbootimg@ and behave differently. h3. From our released tools 1. Download the system path, @mkbootimg@ and @unpackbootimg@ tools, the @mkbootimg.asc@ and @unpackbootimg.asc@ signatures and the checksum from [[ReplicantImages]] for the latest image 2. Make sure you need have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to go in your GPG keyring 3. Check the directory 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 were downloaded in and add a './' in front don't*! 5. Check the checksum of the commands. tools: For instance <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 want will need to obtain install compatibility libraries for 32 bits executables if your computer is running on a list of commands accepted by adb you 64 bit architecture. 7. Make sure @mkbootimg@ and @unpackbootimg@ can use the following command: be executed: <pre> ./adb --help chmod a+x mkbootimg chmod a+x unpackbootimg </pre>