Mobile development
Choose a template, enter literal parameters, and review the command and its effects.
adb devices -l
POSIX sh output for macOS, Linux or WSL. Paths are literal; variables and ~ are not expanded.
Parameters stay in this browser. No device is connected and no command is executed.
The device list ignores target options. Other templates use -d, -e or -s; the default leaves selection to ADB.
Command preview is current.
The ADB command builder turns a small set of Android tasks into a command you can inspect. Select a device serial when several phones or emulators are attached, then supply the parameters required by that task.
This ADB command generator covers installing an APK, reading logs, taking a screenshot, moving files and selected app maintenance. The preview is shell text; it is not a report that the device completed anything.
The ADB command builder quotes local paths and separately protects arguments interpreted by the device shell. A space or apostrophe in a filename stays part of that filename instead of becoming a new command argument.
Switching from log reading to app-data deletion immediately changes the risk panel. Installation, file writes and restarts have their own explanations, so a valid command is never presented as proof that its effects are harmless.
Listing devices is server-wide. For other templates, default selection works only when ADB can identify a single target; use the serial option to disambiguate multiple devices. A sample serial does not prove that an emulator exists.
An APK path belongs to your computer. Screenshot output first belongs to the device and must end in .png; a second path names the local copy. Enter literal paths, including spaces, without adding your own shell quotes.
Automatic building waits 350 ms. Turn it off to review edits before building with Ctrl/Cmd+Enter. Example and Clear first show changed fields; applying can be undone once, restoring the form and its previous command.
Use adb install APK parameters with optional replacement or test-package flags. Uninstall takes an application ID, not an APK filename. Keeping data changes the -k flag but does not preserve the installed app.
The adb logcat filter accepts one tag and a minimum priority. An empty tag targets all logs; a named tag adds *:S to silence other tags. Snapshot mode uses -d; turn it off for continuous output. Format is independently selectable.
The adb screenshot template uses screencap followed by pull, connected with &&. Pull runs only if capture succeeds. Separate pull and push templates preserve the source/destination order and quote both paths.
Clear data includes an explicit Android user; normal reboot has no bootloader or recovery option. Copy and text download contain the current command only, without hidden form drafts or a fabricated execution result.
Select the serial target and enter the identifier from adb devices -l. The generated -s argument applies to the selected command. -d selects one USB device and -e one emulator; either can still be ambiguous when several matching targets exist.
Choose Screenshot and pull, then supply an absolute device .png path and a local destination. The first command saves a PNG with screencap; && lets pull follow only after a successful capture. Existing files may be overwritten.
Yes. Your host shell parses the command first; adb shell sends a command string to the device shell. A quoted path may lose its first layer before reaching Android. This builder applies separate literal quoting at both boundaries.
Enter one exact tag and a minimum priority. The command includes Tag:I, for example, plus *:S to suppress other tags. Leave the tag empty to use *:I across tags. Actual visibility also depends on device permissions and log buffers.
pm clear is not cache-only: it clears the application’s data as well. The Clear app data template is marked as destructive and includes the selected Android user. Do not use it if you need to preserve the app’s settings or session.
Enter the path itself, including spaces, without surrounding shell quotes. Pull treats paths as host argv values; screenshot paths also need remote quoting. This tool supplies those layers, but cannot check whether the source is accessible.
Does a preview differ from your device’s documented syntax?
Use the ADB command builder to check the target, literal paths and command effects together. Copy only the current preview, then review it in the shell environment it was built for.