ToolsInstallation » History » Version 9
Wolfgang Wiedmeyer, 05/07/2017 10:12 PM
updates for Replicant 6.0
1 | 5 | Paul Kocialkowski | h1. Tools installation |
---|---|---|---|
2 | 1 | Paul Kocialkowski | |
3 | This page explains how to install the various tools used with Replicant. It is assumed that you are running a GNU/Linux operating system. |
||
4 | |||
5 | h2. ADB |
||
6 | |||
7 | ADB can be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools. |
||
8 | 2 | Paul Kocialkowski | Note: you may need to run ADB as root if your current user doesn't have USB access privileges. |
9 | 1 | Paul Kocialkowski | |
10 | h3. From GNU/Linux distributions repositories |
||
11 | |||
12 | h4. Debian |
||
13 | |||
14 | <pre> |
||
15 | apt-get install android-tools-adb |
||
16 | </pre> |
||
17 | |||
18 | 6 | Denis 'GNUtoo' Carikli | h4. Parabola |
19 | 7 | Denis 'GNUtoo' Carikli | |
20 | 6 | Denis 'GNUtoo' Carikli | <pre> |
21 | pacman -S android-tools |
||
22 | </pre> |
||
23 | |||
24 | 1 | Paul Kocialkowski | h3. From our released tools |
25 | |||
26 | 4 | Paul Kocialkowski | 1. Download the @adb@ tool, the @adb.asc@ signature and the checksum from [[ReplicantImages]] for the latest image |
27 | 9 | Wolfgang Wiedmeyer | 2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to your GPG keyring |
28 | 1 | Paul Kocialkowski | 3. Check the signature of the @adb@ tool: |
29 | <pre> |
||
30 | 4 | Paul Kocialkowski | gpg --armor --verify path/to/adb.asc path/to/adb |
31 | 1 | Paul Kocialkowski | </pre> |
32 | 4. Make sure the check succeeds, *do not run the binary if it doesn't*! |
||
33 | 5. Check the checksum of the @adb@ tool: |
||
34 | <pre> |
||
35 | 9 | Wolfgang Wiedmeyer | sha256sum -c tools.sha256 |
36 | 1 | Paul Kocialkowski | </pre> |
37 | 6. Make sure the check succeeds for @adb@, *do not run the binary if it doesn't*! |
||
38 | |||
39 | 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. |
||
40 | 7. Make sure @adb@ can be executed: |
||
41 | <pre> |
||
42 | chmod a+x adb |
||
43 | </pre> |
||
44 | |||
45 | h2. Fastboot |
||
46 | |||
47 | Fastboot can be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools. |
||
48 | 2 | Paul Kocialkowski | Note: you may need to run fastboot as root if your current user doesn't have USB access privileges. |
49 | 1 | Paul Kocialkowski | |
50 | h3. From GNU/Linux distributions repositories |
||
51 | |||
52 | h4. Debian |
||
53 | |||
54 | <pre> |
||
55 | apt-get install android-tools-fastboot |
||
56 | </pre> |
||
57 | |||
58 | h3. From our released tools |
||
59 | |||
60 | 9 | Wolfgang Wiedmeyer | 1. Download the @fastboot@ tool, the @fastboot.asc@ signature and the checksum from [[ReplicantImages]] for the latest image |
61 | 2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to your GPG keyring |
||
62 | 1 | Paul Kocialkowski | 3. Check the signature of the @fastboot@ tool: |
63 | <pre> |
||
64 | 4 | Paul Kocialkowski | gpg --armor --verify path/to/fastboot.asc path/to/fastboot |
65 | 1 | Paul Kocialkowski | </pre> |
66 | 4. Make sure the check succeeds, *do not run the binary if it doesn't*! |
||
67 | 5. Check the checksum of the @fastboot@ tool: |
||
68 | <pre> |
||
69 | 9 | Wolfgang Wiedmeyer | sha256sum -c tools.sha256 |
70 | 1 | Paul Kocialkowski | </pre> |
71 | 6. Make sure the check succeeds for @fastboot@, *do not run the binary if it doesn't*! |
||
72 | |||
73 | 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. |
||
74 | 7. Make sure @fastboot@ can be executed: |
||
75 | <pre> |
||
76 | chmod a+x fastboot |
||
77 | </pre> |
||
78 | |||
79 | h2. Heimdall |
||
80 | |||
81 | Heimdall can be installed from the repositories of your GNU/Linux distribution (if available), from our released tools or from the developer's website. |
||
82 | 2 | Paul Kocialkowski | Note: you may need to run heimdall as root if your current user doesn't have USB access privileges. |
83 | 1 | Paul Kocialkowski | |
84 | h3. From GNU/Linux distributions repositories |
||
85 | |||
86 | h4. Debian |
||
87 | |||
88 | <pre> |
||
89 | apt-get install heimdall-flash |
||
90 | </pre> |
||
91 | |||
92 | 8 | Denis 'GNUtoo' Carikli | h4. Parabola |
93 | |||
94 | <pre> |
||
95 | pacman -S heimdall |
||
96 | </pre> |
||
97 | |||
98 | 1 | Paul Kocialkowski | h3. From our released tools |
99 | |||
100 | 4 | Paul Kocialkowski | 1. Download the @heimdall@ tool, the @heimdall.asc@ signature and the checksum from [[ReplicantImages]] for the latest image |
101 | 9 | Wolfgang Wiedmeyer | 2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] of the latest version to your GPG keyring |
102 | 1 | Paul Kocialkowski | 3. Check the signature of the @heimdall@ tool: |
103 | <pre> |
||
104 | 4 | Paul Kocialkowski | gpg --armor --verify path/to/heimdall.asc path/to/heimdall |
105 | 1 | Paul Kocialkowski | </pre> |
106 | 4. Make sure the check succeeds, *do not run the binary if it doesn't*! |
||
107 | 5. Check the checksum of the @heimdall@ tool: |
||
108 | <pre> |
||
109 | 9 | Wolfgang Wiedmeyer | sha256sum -c tools.sha256 |
110 | 1 | Paul Kocialkowski | </pre> |
111 | 6. Make sure the check succeeds for @heimdall@, *do not run the binary if it doesn't*! |
||
112 | |||
113 | 3 | Paul Kocialkowski | 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. |
114 | 7. Make sure @heimdall@ can be executed: |
||
115 | 1 | Paul Kocialkowski | <pre> |
116 | chmod a+x heimdall |
||
117 | </pre> |
||
118 | |||
119 | h3. From the developer's website |
||
120 | |||
121 | Instructions to install heimdall can be found on the developer's website: http://glassechidna.com.au/heimdall/ |