How to Use ADB on Android Without a PC (No Root)

Yes, you can use ADB on an Android phone without a PC. Since Android 11, the phone's own ADB service (adbd) can listen on Wi-Fi through Wireless debugging. An app on the same phone can pair with it and connect, exactly like a computer would. You get the same rights as adb shell from a PC: no root, no cable, no computer. You only need Wi-Fi and about a minute for the one-time pairing.

Why plain USB debugging is not enough

USB debugging lets a computer control the phone through the cable. The computer is in charge and the phone answers. An app on the phone cannot plug into its own USB port, so it has no way to use that channel.

Wireless debugging is different. It makes adbd listen on the network, so anything on the same Wi-Fi that has been paired can connect, including an app running on the phone itself. The connection goes from the phone to the phone, so nothing leaves the device.

What you need

Check your version in Settings › About phone › Android version (the exact wording differs by brand, see Wireless debugging on Xiaomi, vivo, OPPO, Samsung and more).

The ADB Kit way (step by step)

ADB Kit is an Android app with a built-in adb client. It needs no other app, no root and no PC. The Home tab walks you through five steps and ticks off the first three by itself as the phone reports them.

1. Join Wi-Fi. Connect the phone to any Wi-Fi network.
2. Turn on Developer options. Open About phone and tap Build number seven times. On Xiaomi, Redmi and POCO, tap OS version (HyperOS) or MIUI version. On vivo and iQOO, tap Software version.
3. Turn on Wireless debugging. In Developer options, switch on Wireless debugging and tap Allow for this network.
4. Pair with a code. In ADB Kit, tap Start pairing. Then go back to Wireless debugging and tap Pair device with pairing code. ADB Kit notices the code on screen and pops up a notification with a reply box. Type the six digits into that notification.
5. Connect ADB Kit. This happens by itself once pairing succeeds. Home shows Connected.

Why the notification? Android closes the "Pair device with pairing code" dialog as soon as you leave Developer options, so you cannot switch to the app to type the code. The notification lets you type it while the dialog stays open. If notifications are off, ADB Kit offers Allow notifications, or lets you type the code in the app using split screen.

The pairing is kept when you close or restart the app. Later you only need Wireless debugging switched on, and ADB Kit reconnects by itself, even though Android picks a new port each time. More on that in why the Wireless debugging port changes.

What you can do once connected

Some things work even before you connect. The Shell tab runs the app's own shell with the app's permissions (marked App shell · limited), and Launch, App info and Uninstall in Apps use normal Android screens.

Typical commands people run without a PC

pm list packages -3                              # user-installed apps
pm disable-user --user 0 com.example.bloatware   # turn off a preinstalled app (no root)
settings put global animator_duration_scale 0.5  # faster animations
dumpsys battery                                  # battery details

Disabling system apps can break things. Check what a package does first, and keep a note so you can turn it back on with pm enable.

Other ways (and why they need more setup)

• Termux with android-tools. Termux can install the adb binary, then you pair and connect to 127.0.0.1 by hand with adb pair and adb connect. It works, but you type the pairing port and connect port yourself, and the connect port changes every time Wireless debugging is turned on.
• Shizuku. Shizuku uses Wireless debugging too, but it is a service for other apps, not a terminal or tool set by itself.
• Android 10 and older. Without Wireless debugging, the phone needs a computer once: connect by USB and run adb tcpip 5555. Then ADB Kit can use Settings › Connect by IP address with 127.0.0.1:5555. This mode stops at every restart, so you repeat it each time.

Common problems

• The Wireless debugging switch does not turn on. The phone is not on Wi-Fi. Mobile data alone is not enough. Join any Wi-Fi network or another phone's hotspot.
• "Wrong code. Check the code and try again." You typed the digits wrong or used an old code. Open the pairing dialog again for a fresh code. Details in fix ADB pairing failed.
• "Pairing code not found. Keep "Pair device with pairing code" open." The dialog closed before the code reached it. Use the notification instead of switching apps.
• It was connected yesterday, now it is not. Android usually turns Wireless debugging off after a restart or when you change networks. Switch it back on. No new pairing is needed. See Wireless debugging keeps turning off.
• Taps or permission changes fail on Xiaomi. Turn on USB debugging (Security settings) as described in Xiaomi security settings.

Is it safe?

The adb shell user can uninstall apps, change settings and read app data that normal apps cannot. Only pair apps you trust, and only run commands you understand. Wireless debugging uses an encrypted, paired connection, but switch it off when you are on a public network. ADB Kit talks only to the phone itself, never to a server.

ADB Kit is free with ads. ADB Kit Pro removes the ads and nothing else.