Remote ADB Shell

Remote ADB Shell is a terminal app that allows you to connect with the ADB shell service of other Android gadgets over the community and execute terminal instructions. This may be useful for remotely debugging Android gadgets (running instruments like prime, logcat, or dumpsys). It helps a number of simultaneous connections to different devices and retains these connections alive even when the app is within the background. This app doesn't require root on both gadget, but root may be useful to configure the target devices. If the target units are not rooted, you have to use a pc with the Android SDK and Google USB drivers to configure the them (detailed below).

This app is a wrapper across the shell that is uncovered over ADB. It maintains a 15 command historical past which is accessible by long urgent the command box. Long urgent the terminal display itself will give the option to send a Ctrl C, toggle auto-scrolling, or exit the terminal session.

This works in the actual same means that the adb shell command works on a computer. Because this app uses a local implementation of the ADB protocol in Java, it does not require root on both system or any 3rd party apps on the target gadget. The gadgets simply communicate the same protocol to every other that they'd to a computer operating the ADB consumer from the Android SDK.

IMPORTANT: Devices running Android 4.2.2 and later use RSA keys to authenticate the ADB connection. In my testing, gadgets running 4.2.2 will need to be plugged in to a pc the primary time you hook up with them (from each device with this app installed). This permits them to show the general public key acceptance dialog, which you must accept (and verify Always enable from this computer). Devices running Android 4.3 and 4.4 appear to have no downside displaying the dialog and not using a connection to a pc, so it seems like this is a workaround specific to Android 4.2.2.

To configure a inventory un-rooted target, plug the target device into a pc that has the Android SDK installed and run adb tcpip 5555 from the Android SDK's platform-tools folder. This will begin ADB listening on port 5555 on the goal system. The device can then be unplugged and will remain configured correctly till reboot.

For devices which might be rooted (although it's not required), you probably can install one of many several ADB WiFi apps to allow the ADB server to pay attention over the network. Devices with a customized ROM could have an option to enable ADB over the community within the Developer Options pane of Settings. Using either of those methods will properly configure ADB for community access with this app. The further step for 4.2.2 continues to be required for the preliminary connection.

To connect with your remote Android device, kind in the IP address of the system and the port number (5555 from the example above) in Remote ADB Shell. Tap Connect and it will try to hook up with the system and begin up the terminal.

I welcome feature requests and bug stories. You can embrace them in your app reviews or submit them on the discussion board (links below). Please rate this app should you can; it really helps me be taught what features/fixes I should concentrate on subsequent.

Developers: The customized Java ADB library I've written for this app is open-source beneath the BSD license at https://github.com/cgutman/AdbLib

The source for this app is out there underneath the Apache license: https://github.com/cgutman/RemoteAdbShell

XDA forum links:

Remote ADB Shell App Thread - http://forum.xda-developers.com/showthread.php?t=2373265

Java ADB Library Thread - http://forum.xda-developers.com/showthread.php?t=2405030