Skip to main content

How to disable or disconnect ADB over WiFi

ADB over Wi-Fi leaves your device open to remote connections, which can be a security risk on untrusted networks. Disabling it restores the traditional USB debugging mode and ensures that your device remains secure.


1 Revert to USB Debugging

        Connect via USB: If your device is currently connected over Wi-Fi, reattach the USB cable. This initial connection is essential to safely switch debugging modes.

          Open Terminal/Command Prompt:  Launch your terminal or command prompt on your computer.

           Switch Back to USB Mode: Enter the following command

                    adb usb

        2. Disconnect the Wireless Session

            If you’re still in a Wi-Fi debugging session, you can explicitly disconnect by running

                  adb disconnect [Your Device's IP Address]:5555

            Replace [Your Device's IP Address] with the actual IP that your device was using for the wireless session.

        3. Disable Wireless Debugging in Developer Options

    • On your Android device, navigate to Settings > System > Developer Options.
    • Look for Wireless Debugging (or “ADB over network” in some versions) and toggle it off.

        4. Restart ADB Server (Optional)

               For added assurance, you can restart the ADB server:

                    adb kill-server 

                    adb start-server

                This ensures all previous Wi-Fi sessions are terminated and that ADB is now strictly using USB.




Known Issues and Considerations

When It Will Work

• Device Still Connected via USB: Disabling Wi-Fi mode works best when the device is physically connected via USB, ensuring that commands are executed reliably.

• Stable ADB Environment: If your computer and device are on a trusted network and you’ve successfully authenticated via USB, the transition back to USB mode should be smooth.

• Post-Setup Verification: Running adb devices after disabling confirms that only USB connections are active, which indicates a successful transition.

When It May Not Work

• Lost USB Connection: If your USB connection is unstable or gets disconnected during the process, you might not be able to issue commands to revert the mode.

• System Reboots or Network Changes: In some cases, especially on older devices or certain Android versions, the wireless ADB might re-enable itself after a reboot or when a network change occurs.

• Developer Options Reset: Some custom ROMs or device configurations might reset developer settings upon restart. In such cases, you may need to re-navigate to Developer Options and manually disable wireless debugging again.

• Firewall or Network Restrictions: Certain network settings or firewall rules might interfere with the disconnection commands, requiring additional troubleshooting steps such as restarting the ADB server.


Comments

Post a Comment

Popular posts from this blog

How to extract signing certificates from macOS binary files

Code signing is a macOS security technology that you use to certify that an app was created by you. Once an app is signed, the system can detect any change to the app—whether the change is introduced accidentally or by malicious code. As Apple Developer site says ( click here for more details  on code signing) : code signing allows the operating system to: Ensure that a piece of code has not been altered since it was signed.  The system can detect even the smallest change, whether it was intentional (by a malicious attacker, for example) or accidental (as when a file gets corrupted). When a code signature is intact, the system can be sure the code is as the signer intended. Identify code as coming from a specific source (a developer or signer).  The code signature includes cryptographic information that unambiguously points to a particular author. Determine whether code is trustworthy for a specific purpose.  Among other things, a developer can use a ...
Post a Comment
Read more

How to find firmware or boot ROM version in Mac OS X

Firmware and boot ROM version of your mac can be found in two ways. Way 1 : 1. From "Apple" menu , choose "About This Mac" menu item. 2. Click " More Info " to open "System Profiler" application. 3. Under Contents -> Select Hardware Tree item. On the right side panel Under hardware overview section, we can see Boot ROM Version and SMC (Firmware) Version. Way 2 : Run the below command in terminal to get boot ROM version and SMC(firmware) version : $ system_profiler SPHardwareDataType | grep -i "Version" | awk -F ':' '{print $1 $2}'
6 comments
Read more

How to enable root login in gnome on Debian 6 or 7

Root user login in gnome is disabled on Debian system by default for security reasons. If you want to enable it for specific reasons then follow the below steps : 1. Login into Debian system 2. launch the Root Terminal from Applications -> Accessories. 3. Authenticate with password to launch the Root Terminal. 4. Open "/etc/pam.d/gdm3" with vi.          #vi /etc/pam.d/gdm3 5. Look for "auth     required     pam_succeed_if.so  user  != root   quiet_success"  , comment it out as below.     #auth     required     pam_succeed_if.so  user  != root   quiet_success 6. Save the modification with Esc+w+q+Enter keystroke. 7. Restart or reboot Debian system. 8. Login with root user in gnome. You should be now able to login successfully.   
11 comments
Read more