ToolsInstallation » History » Version 4
Paul Kocialkowski, 07/06/2014 09:30 AM
1 | 1 | Paul Kocialkowski | h1. Tools Installation |
---|---|---|---|
2 | |||
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 | h3. From our released tools |
||
19 | |||
20 | 4 | Paul Kocialkowski | 1. Download the @adb@ tool, the @adb.asc@ signature and the checksum from [[ReplicantImages]] for the latest image |
21 | 1 | Paul Kocialkowski | 2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] to your GPG keyring |
22 | 3. Check the signature of the @adb@ tool: |
||
23 | <pre> |
||
24 | 4 | Paul Kocialkowski | gpg --armor --verify path/to/adb.asc path/to/adb |
25 | 1 | Paul Kocialkowski | </pre> |
26 | 4. Make sure the check succeeds, *do not run the binary if it doesn't*! |
||
27 | 5. Check the checksum of the @adb@ tool: |
||
28 | <pre> |
||
29 | md5sum -c tools.md5 |
||
30 | </pre> |
||
31 | 6. Make sure the check succeeds for @adb@, *do not run the binary if it doesn't*! |
||
32 | |||
33 | 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. |
||
34 | 7. Make sure @adb@ can be executed: |
||
35 | <pre> |
||
36 | chmod a+x adb |
||
37 | </pre> |
||
38 | |||
39 | h2. Fastboot |
||
40 | |||
41 | Fastboot can be installed from the repositories of your GNU/Linux distribution (if available) or from our released tools. |
||
42 | 2 | Paul Kocialkowski | Note: you may need to run fastboot as root if your current user doesn't have USB access privileges. |
43 | 1 | Paul Kocialkowski | |
44 | h3. From GNU/Linux distributions repositories |
||
45 | |||
46 | h4. Debian |
||
47 | |||
48 | <pre> |
||
49 | apt-get install android-tools-fastboot |
||
50 | </pre> |
||
51 | |||
52 | h3. From our released tools |
||
53 | |||
54 | 4 | Paul Kocialkowski | 1. Download the @fastboot@ tool, the @fasboot.asc@ signature and the checksum from [[ReplicantImages]] for the latest image |
55 | 1 | Paul Kocialkowski | 2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] to your GPG keyring |
56 | 3. Check the signature of the @fastboot@ tool: |
||
57 | <pre> |
||
58 | 4 | Paul Kocialkowski | gpg --armor --verify path/to/fastboot.asc path/to/fastboot |
59 | 1 | Paul Kocialkowski | </pre> |
60 | 4. Make sure the check succeeds, *do not run the binary if it doesn't*! |
||
61 | 5. Check the checksum of the @fastboot@ tool: |
||
62 | <pre> |
||
63 | md5sum -c tools.md5 |
||
64 | </pre> |
||
65 | 6. Make sure the check succeeds for @fastboot@, *do not run the binary if it doesn't*! |
||
66 | |||
67 | 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. |
||
68 | 7. Make sure @fastboot@ can be executed: |
||
69 | <pre> |
||
70 | chmod a+x fastboot |
||
71 | </pre> |
||
72 | |||
73 | h2. Heimdall |
||
74 | |||
75 | Heimdall can be installed from the repositories of your GNU/Linux distribution (if available), from our released tools or from the developer's website. |
||
76 | 2 | Paul Kocialkowski | Note: you may need to run heimdall as root if your current user doesn't have USB access privileges. |
77 | 1 | Paul Kocialkowski | |
78 | h3. From GNU/Linux distributions repositories |
||
79 | |||
80 | h4. Debian |
||
81 | |||
82 | <pre> |
||
83 | apt-get install heimdall-flash |
||
84 | </pre> |
||
85 | |||
86 | h3. From our released tools |
||
87 | |||
88 | 4 | Paul Kocialkowski | 1. Download the @heimdall@ tool, the @heimdall.asc@ signature and the checksum from [[ReplicantImages]] for the latest image |
89 | 1 | Paul Kocialkowski | 2. Make sure you have added the [[ReplicantReleaseKey|Replicant release key]] to your GPG keyring |
90 | 3. Check the signature of the @heimdall@ tool: |
||
91 | <pre> |
||
92 | 4 | Paul Kocialkowski | gpg --armor --verify path/to/heimdall.asc path/to/heimdall |
93 | 1 | Paul Kocialkowski | </pre> |
94 | 4. Make sure the check succeeds, *do not run the binary if it doesn't*! |
||
95 | 5. Check the checksum of the @heimdall@ tool: |
||
96 | <pre> |
||
97 | md5sum -c tools.md5 |
||
98 | </pre> |
||
99 | 6. Make sure the check succeeds for @heimdall@, *do not run the binary if it doesn't*! |
||
100 | |||
101 | 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. |
102 | 7. Make sure @heimdall@ can be executed: |
||
103 | 1 | Paul Kocialkowski | <pre> |
104 | chmod a+x heimdall |
||
105 | </pre> |
||
106 | |||
107 | h3. From the developer's website |
||
108 | |||
109 | Instructions to install heimdall can be found on the developer's website: http://glassechidna.com.au/heimdall/ |