Wireless ADB Controller

Managing Android Debug Bridge (ADB) connections often means being tethered to your computer with a USB cable. This can be restrictive, especially for developers and power users who need more flexibility. The Wireless ADB Daemon (wadbd) Controller is a lightweight yet powerful Magisk module designed to liberate you from that cable. It provides comprehensive control over your device’s wireless ADB service.

With this module, you can effortlessly initiate the wireless ADB daemon during your current session, configure it to launch automatically every time your device boots, specify custom ports for the connection, and even perform advanced ADB key management tasks like backing up, restoring, or importing keys. For an even more user-friendly experience, the module also fully supports the KernelSU and Apatch WebUI.

Getting Started: Installation and Usage

  1. Begin by installing the module through your preferred root manager (Magisk, KernelSU, or Apatch).
  2. Perform a device reboot to ensure the module is properly activated.
  3. Launch your preferred terminal application (such as Termux) and acquire root privileges by running the su command.

Module Commands

Control the wireless ADB daemon directly from your terminal using these simple commands.

wwwwwwwwwaaaaaaaaadddddddddbbbbbbbbbdddddddddoosednftni----faasibrc<tbamaelpulbpcseoseloktar-eruorto-tpr->no-ek-nk<eb-ep<yobyapsootato<http>h<a>ptohr>t>---------EDSEDIBrRnihnimaeeasoaspcsvbawbaoktolblbruokelteltpreeheeswewaaiwiwnubarisritalerterahcllealedokeltelbreaseusekidussssseztssyeuhAoA.dpoDAfDAprBDBDuaaiBwBbddzo.iobbenrnof__denikktlbleeKheobeyyeesoossystotsstopAw.eDiacBtui.htfhitoehrdeizpseopreAtcD.iBfiweidthpoourtt.prompt.

Note: If you do not specify a port, the module will default to using port 5555.

WebUI Integration

For users who prefer a graphical interface, this module integrates seamlessly with the KernelSU and Apatch WebUI. This allows you to manage the wireless ADB service with simple toggles and inputs directly from your web browser, providing a convenient alternative to the terminal commands.

<div style=“display: flex; justify-content: center; align-items: center;”> <img src="https://github.com/rhythmcache/wireless-adb-controller/raw/main/e1.png" alt=“WebUI Screenshot” width=“45%”> <img src="https://github.com/rhythmcache/wireless-adb-controller/raw/main/e2.png" alt=“KernelSU Screenshot” width=“45%”> </div>

Detailed Command Guide

Here is a more detailed breakdown of what each terminal command does.

wadbd on [port]

This command activates the wireless ADB service on the designated port. It will also conveniently display the connection command (e.g., adb connect IP:PORT) that you need to run on your computer to establish the connection. If no port is specified, it will automatically use the default port 5555.

wadbd status

Use this command to check the current operational state of the wireless ADB daemon. It will confirm whether the service is currently active or inactive.

wadbd off

This command immediately terminates and disables the wireless ADB service for the current session.

wadbd enable-on-boot [port]

This is a “set it and forget it” command. It configures the module to automatically start the wireless ADB daemon every time your device boots up. (Defaults to 5555 if no port is specified).

wadbd disable-on-boot

This command reverses the previous one, disabling the automatic startup of wireless ADB during the boot sequence.

🧪 Experimental Features

⚠️ Use at your own risk. These features and commands are considered experimental and are not guaranteed to work correctly on all device configurations or Android versions. They are provided for advanced users and debugging purposes. These functions are not available in the WebUI and will not be added.

wadbd --import-keys <path-to-adbkey.pub>

This command is useful for situations where your device fails to show the standard authorization prompt when you try to connect via ADB. You can use this to manually import your computer’s public ADB key, pre-authorizing it. The adbkey.pub file is typically located at:

wadbd --backup <path> / wadbd --restore <path>

These commands allow you to manage your device’s adb_keys file. You can create a backup of all currently authorized computers or restore from a previously saved backup. This is helpful when switching ROMs or setting up a new device.

wadbd --clear-keys

This is a security-focused command. It revokes all currently authorized ADB keys, effectively forcing any computer that wishes to connect to re-authenticate.

Download Link

Module Info

Search on : Google Bing Yandex