Android

Build ADB commands in the browser — you still run them

Pick an action and fill the form. We assemble a copyable adb line with optional -s <serial>. This tab does not install anything, does not open USB, and does not see your device.

Leave empty to target the default connected device.
Generated command
adb devices
Tip: If you see multiple devices, set a serial with -s. For paths on Windows, quoting is added automatically when needed.

When to use this — and when not to

Use it when you know the job (install this APK, start this activity, filter logcat) and you want a line that quotes paths correctly. Use it with the Intent URL generator when the next step is am start.

Do not expect this site to reach the phone. There is no WebUSB ADB here. Wireless debugging, pairing codes, and adb connect still happen in platform-tools on your machine.

How the command is built

The script reads the action dropdown and the visible fields. If Device serial is set, every command starts adb -s SERIAL. Arguments with spaces are wrapped in double quotes. Install can add -r (replace) and -g (grant permissions). Start-activity concatenates the component or the intent you typed — it does not validate that the activity exists on the device.

Failure modes: a wrong serial silently targets nothing useful. adb install of a path that only exists in the browser will fail on the machine — the path is whatever you type, not a file you dropped here. Quotes can still break on exotic Windows paths; read the line before you run it.

Worked example

Action: Install APK. Path: D:\builds\notes-24.apk. Replace + grant checked. Serial: emulator-5554.

adb -s emulator-5554 install -r -g "D:\builds\notes-24.apk"

Run that in a terminal where adb devices already lists emulator-5554. If the APK’s applicationId is a .debug suffix and you expected production, you installed the wrong flavor — the generator cannot see the file.

Mistakes people make

  • Clearing data on a production device because the serial field was empty and adb picked the USB phone.
  • Using debug applicationId in uninstall after installing a release build.
  • Treating generated am start as proof the deep link works in Gmail or Chrome.

How this differs from Android Studio and adb itself

Studio’s Device Explorer and the real adb binary talk to the daemon. This page only prints text. See the ADB and intent guide.

Related

ADB & intents without Studio · Deep link tester · Intent URL generator

Frequently asked questions

Does DroidXP run ADB on my device?

No. Copy the line. Run it where platform-tools are installed.

How do I target one of several devices?

Fill Device serial. We prefix adb -s.

Are the commands safe?

They are ordinary ADB. Uninstall and clear-data are destructive. Read the line.