make it harder to mess up obtaining fastboot
This removes the link to the platform-tools releases page to discourage using another approach to downloading and extracting it. The most common mistake made by users is doing this their own way and ending up without fastboot in their shell's path.
This commit is contained in:
parent
89ba766d85
commit
cce6d66b10
@ -154,13 +154,14 @@
|
|||||||
<section id="standalone-platform-tools">
|
<section id="standalone-platform-tools">
|
||||||
<h4><a href="#standalone-platform-tools">Standalone platform-tools</a></h4>
|
<h4><a href="#standalone-platform-tools">Standalone platform-tools</a></h4>
|
||||||
|
|
||||||
<p>If your operating system doesn't make a proper version of fastboot available,
|
<!-- https://developer.android.com/studio/releases/platform-tools -->
|
||||||
consider using the
|
|
||||||
<a href="https://developer.android.com/studio/releases/platform-tools">standalone
|
<p>If your operating system doesn't include a usable version of fastboot,
|
||||||
releases of platform-tools from Google</a>. If you have the Android SDK or intend to
|
you can use the official standalone releases of platform-tools. This is
|
||||||
do development work, you install the platform-tools package via the Android SDK
|
our recommendation for most users. The flashing process won't work unless
|
||||||
package manager which can be used to keep it up-to-date. The Android SDK is available
|
you follow these instructions including setting up PATH. If you close and
|
||||||
by itself or can be obtained via Android Studio.</p>
|
reopen the terminal after doing this, you'll need to set PATH again in the
|
||||||
|
new terminal.</p>
|
||||||
|
|
||||||
<p>To download, verify and extract the standalone platform-tools on Linux:</p>
|
<p>To download, verify and extract the standalone platform-tools on Linux:</p>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user