Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

To turn off Android Debug Bridge, run adb kill-server on your computer to stop the adb server, then open Settings > System > Developer options on your Android device and toggle USB debugging off. Turn off Wireless debugging too if you used ADB over Wi-Fi. ADB stays installed, so you can switch it back on any time.
People mean different things by "turn off ADB." The table below maps each action to where it happens and whether it is reversible, so you can pick the right one before running any command.
| Action | Where it runs | What it does | Reversible? |
|---|---|---|---|
| Kill the server | Computer | Stops the host-side adb process only | Yes, restarts on next command |
| Disable on device | Android device | Phone stops accepting ADB connections | Yes, re-enable in Settings |
| Uninstall | Computer | Removes platform-tools and the adb binary | No, must reinstall |
If you only want ADB to stop running for now, you need the first two rows. The third row, removing ADB for good, is covered in our How to Uninstall Android Debug Bridge? guide.
The adb server is a background process on your machine that brokers traffic between your terminal and any connected device or emulator. Stopping it is the cleanest way to halt all ADB activity from the host side:
adb is on your PATH.adb kill-serverHost-only: This terminates the adb server process on your computer and disconnects any attached devices and emulators from that session. It does not stop the adbd daemon on the phone and changes nothing on the device itself.
It restarts automatically: The server relaunches the next time you issue any adb command, so killing it is a pause rather than a permanent off switch. To start it again deliberately, run adb start-server.
If you only want to drop one connection instead of stopping the whole server, for example a single networked device, use the disconnect command:
adb disconnectTo disable USB debugging on Android, open Settings, go to System > Developer options, and toggle USB debugging off. Then tap Revoke USB debugging authorizations to clear every computer your phone has trusted. The phone now refuses ADB connections from all machines until you switch USB debugging back on.
Killing the adb server only pauses ADB on your computer. Disabling USB debugging is the step that blocks the phone itself, including connections from any other computer:
The USB debugging toggle always sits inside Developer options, but manufacturers put Developer options in different places. Use the path that matches your phone:
| Device | Path to USB debugging | Unlock Developer options via |
|---|---|---|
| Google Pixel / stock Android | Settings > System > Developer options > USB debugging | About phone > tap Build number 7 times |
| Samsung Galaxy (One UI) | Settings > Developer options > USB debugging | About phone > Software information > tap Build number 7 times |
| Xiaomi (HyperOS / MIUI) | Settings > Additional settings > Developer options > USB debugging | About phone > tap MIUI version / OS version 7 times |
| OnePlus / OPPO | Settings > Additional settings > Developer options > USB debugging | About device > Version > tap Build number 7 times |
There is no adb command that turns USB debugging off, because ADB would be closing the channel it runs on. The toggle can only be changed on the device.
Disabling USB debugging matters for security because an approved computer can read app data, install apps, and record the screen over ADB. The lock screen and the one-time RSA prompt are the only barriers. Revoking authorizations is worth doing if you have plugged the phone into shared or public machines.
If you ever paired your device for ADB over Wi-Fi, killing the USB session is not enough; the wireless channel stays available until you close it. Shut it down on both sides:
adb disconnectThese three actions are often confused, but they operate at completely different levels. Knowing the difference saves you from, say, deleting platform-tools when you only wanted ADB to stop for a few minutes:
adb kill-server stops the adb process on your computer and removes nothing; the next adb command brings it straight back.One way to avoid managing the adb lifecycle by hand is to run your Android sessions on a cloud platform. With a Real Device Cloud, devices are provisioned and released for you, so there is no local adb server to start, kill, or secure between test runs.
No. adb kill-server only stops the adb server process on your computer. The platform-tools files, the adb binary, and your PATH entry all stay in place. To actually remove ADB you delete the platform-tools folder or uninstall it through your package manager.
No. The command terminates only the host-side server on your computer. It does not stop the adbd daemon on the phone, does not reset the device, and does not touch any device settings. USB debugging stays enabled, and the phone will accept ADB again as soon as a server is running.
Run any adb command, such as adb devices, and the server starts again automatically. You can also start it explicitly with adb start-server. If you disabled USB debugging on the device, re-enable it from Settings > System > Developer options before reconnecting.
For most users, yes. Turning off USB debugging stops the phone from accepting ADB connections, which is the main reason to disable it when you are done. For added safety, also tap Revoke USB debugging authorizations to clear trusted computers, and turn off Wireless debugging if you ever used ADB over Wi-Fi.
Turning off ADB is reversible and removes nothing: killing the server stops the host process, and disabling USB debugging stops the device from accepting connections, but the tools stay installed. Uninstalling deletes the platform-tools folder permanently and is what you do when you no longer need ADB at all.
Run adb disconnect to drop active wireless connections, then open Settings > System > Developer options > Wireless debugging on the device and toggle it off. To remove a paired computer, tap its name under Paired devices and select Forget.
On Samsung Galaxy phones running One UI, Developer options appears at the bottom of the main Settings list, not under System. Open Settings > Developer options and toggle USB debugging off. If Developer options is missing, go to Settings > About phone > Software information and tap Build number seven times.
No. Turning off USB debugging changes one setting and deletes no apps, files, photos, or accounts. The only thing it removes is the phone's willingness to accept ADB commands. Tapping Revoke USB debugging authorizations additionally clears the saved RSA keys of computers you previously trusted.
It is a real risk on a phone you carry around. With USB debugging on, any computer you approve can read app data, install apps, and capture the screen over ADB. The lock screen and the one-time RSA prompt are the only barriers. Leave it on while you are actively testing and turn it off afterwards.
No. There is no adb command that switches USB debugging off, because ADB would be disabling the very channel it runs on. Commands like adb kill-server and adb disconnect only affect your computer. USB debugging can be turned off only on the device, in Settings under Developer options.
Yes. Switching the master Developer options toggle off disables USB debugging along with every other developer setting, and hides the menu. Android remembers your previous choices, so USB debugging may switch back on when you re-enable Developer options. Toggle USB debugging off directly if you want it to stay off.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance