adb shell commands

These are the Android Debug Bridge (adb) shell commands you can run during a manual session, which includes installing apps, managing permissions, analyzing performance, and more. The commands are available for Android devices.

A manual session with the <code>adb</code> shell open.

Public devices

Public devices are shared across all Kobiton users, so they run a restricted shell. Kobiton checks each command before it reaches the device and rejects any command that can disrupt the device or affect other users. A rejected command returns a message stating that shell access on this device is restricted. The device stays online and the session continues.

Read-only diagnostic commands run normally. For example:

  • dumpsys display

  • dumpsys battery

  • getprop ro.build.version.release

  • pm list packages -3

Commands that restart, power off, or reconfigure the device are rejected. For example:

  • reboot -p bootloader

  • svc usb

The restriction applies wherever you reach the shell on a public device:

Private and local devices

You can run most adb commands on private and local devices—​as long as they don’t harm the device or alter systems in real-time.

These are the type of commands we don’t allow:

  • kobiton/i

  • logcat/i

  • monkey/i

  • top/i

  • com.domobile.applock/i

  • com.domobile.applockwatcher/i

  • com.sp.protector.free/i

  • com.manageengine.mdm.android/i

  • com.manageengine.mdm.samsung.knox/i

  • com.manageengine.mdm.samsung/i

  • com.manageengine.admp/i

  • com.android.systemui/i

  • com.android.settings/i

  • com.android.vending/i

  • com.google.android.webview/i

  • monkey -p com.myAppPackage -v 10000 -s 100