android-platform-tools mit Homebrew Cask installieren

Projektlinks

• Homepage

Befehle und Aliase

• adb
• etc1tool
• fastboot
• hprof-conv
• make_f2fs
• make_f2fs_casefold
• mke2fs

Projektgeschichte

The Android Debug Bridge is documented by Android as a command-line tool for communicating with a device, installing and debugging apps, and running shell commands. The platform-tools package became the distribution vehicle for adb and fastboot as Android separated SDK components into independently updated downloads.

Google's Platform-Tools release notes show the package as a continuously updated SDK component rather than a standalone application. Its history is therefore tied to Android device protocols and host tooling: adb for development and debugging, fastboot for bootloader-level flashing, and small filesystem/image helpers used by the Android build and device ecosystem.

Adoptionsgeschichte

The toolset is installed by Android Studio and the Android SDK Manager, but package managers also carry it because many users need only adb and fastboot. Homebrew distributes it as a cask, making macOS command-line Android workflows possible without installing the full Android Studio application.

Its adoption spread beyond app developers into CI pipelines, hardware labs, custom ROM communities, recovery workflows, and test automation. That mixed audience explains why platform-tools is treated like a core system utility package even though it is officially an SDK component.

Wie es verwendet wird

Common use centers on `adb devices`, `adb install`, `adb shell`, log capture, port forwarding, file transfer, and fastboot flashing or boot commands. The Android documentation also records `ANDROID_USER_HOME` as the parent for Android tool configuration, with the default user directory under `.android`.

Package users care about version freshness because adb and fastboot need to track Android platform behavior, USB/device protocol changes, and security fixes. Installing platform-tools from a package manager gives scripts a stable executable path while still following Google's SDK releases.

Warum Paket-Nerds sich dafür interessieren

This is a classic package-manager split: a large vendor SDK is reduced to the few host binaries people actually put in PATH. It is especially valuable on macOS and CI runners where installing Android Studio would be slow, stateful, and unnecessary.

The source lives in Android's public Gitiles infrastructure rather than a conventional GitHub project, which is a useful reminder that official source-control URLs are not always the same shape as community package metadata expects.

Zeitleiste

• 2008: Android SDK tooling ships with early public Android development releases.
• 2010s: adb and fastboot become the common host-side tools for app debugging, device automation, and bootloader workflows.
• 2020: Android Platform-Tools 30.x release notes document ongoing package-specific releases.
• 2026: Homebrew cask metadata lists Platform-Tools 37.0.0 for macOS.

Related projects

• Android Studio and the Android SDK Command-line Tools provide the broader SDK management surface around platform-tools.
• AOSP hosts adb source under the Android source tree; fastboot and filesystem helpers are related host utilities in the Android platform toolchain.

Quellen

• https://android.googlesource.com/platform/packages/modules/adb
• https://developer.android.com/tools/adb
• https://developer.android.com/tools/releases/platform-tools
• https://developer.android.com/tools/variables
• source_facts.package-manager