How to Enable USB Debugging on Samsung Galaxy Phones

USB debugging lets your Samsung Galaxy phone talk directly to a computer through a USB cable, giving you access to ADB commands, app sideloading, and system-level troubleshooting. We tested the steps below on a Galaxy S24 running Android 15 and a Galaxy S7 on Android 8, and the process is nearly identical across all Samsung models.

#What Is USB Debugging and Why Would You Need It?

USB debugging opens a direct communication channel between your Samsung phone and a computer using Android Debug Bridge (ADB). Developers use it to push test builds, pull crash logs, and run shell commands on a connected device.

You don’t need to be a developer to benefit from it. USB debugging is required for tasks like rooting your Android phone, sideloading APK files that aren’t on the Play Store, and recovering data from a phone with a broken screen. According to Google’s Android developer documentation, Developer Options and USB debugging are available on every Android device running 4.2 or later.

If your Samsung Galaxy S7 won’t turn on, USB debugging can also help you pull files off the device through ADB recovery commands before doing a factory reset.

#How to Unlock Developer Options on Samsung

Before you can toggle USB debugging, Developer Options must be visible in your Settings menu. Samsung hides this menu by default to keep casual users from changing system-level settings.

1. Open Settings

2. Scroll down and tap About Phone (on some models, it’s About Device)

3. Find Software Information and tap it

4. Tap Build Number exactly 7 times

5. Enter your PIN or pattern if prompted

You’ll see a toast message that says “Developer mode has been enabled.” Go back to the main Settings screen, and Developer Options now appears between About Phone and Biometrics and Security on most Samsung phones.

In our testing on a Galaxy A54 running Android 14, the Developer Options menu appeared instantly after the 7th tap. No restart was required.

#Step-by-Step USB Debugging for Each Samsung Series

The toggle location is consistent across Samsung models, but the Settings menu layout can differ slightly depending on your Android version and One UI skin.

#Galaxy S Series (S7, S8, S9, S10, S20, S21, S22, S23, S24)

1. Open Settings > Developer Options

2. Scroll down to the Debugging section

3. Toggle USB Debugging on

4. Tap OK on the confirmation prompt

On the S7 and S8 running Android 8, the toggle appears as a checkbox rather than a slider, but the function is the same either way and enabling it takes the same four steps listed above.

#Galaxy Note Series (Note 3, Note 4, Note 5, Note 8, Note 9, Note 10, Note 20)

Identical steps. Open Developer Options, toggle USB Debugging, confirm.

#Galaxy J and A Series (J3, J5, J7, A10, A20, A50, A54)

Same process as the S and Note series. Open Settings > Developer Options, locate USB Debugging, turn the toggle on, and accept the prompt. Budget Samsung phones in the J and A series use the exact same Developer Options layout as flagship models. We confirmed this on a Galaxy J7 running Android 9, and a Galaxy A54 running Android 14 had the toggle in the same spot.

#Connecting Your Phone to a Computer via ADB

Turning on USB debugging is half the job. You also need ADB set up on your computer to actually send commands to your phone.

1. Download Android SDK Platform Tools for your operating system (Windows, macOS, or Linux)

2. Extract the ZIP to any folder

3. Plug your Samsung phone into the computer with a USB cable (use the one that came in the box if possible, since cheap cables sometimes lack data wires)

4. On your phone, a popup asks “Allow USB debugging?” with your computer’s RSA fingerprint. Tap Allow and check “Always allow from this computer” if you’ll connect regularly

5. Open a terminal or command prompt, go to the platform-tools folder, and type adb devices

6. Your phone’s serial number should appear in the list

On Windows, you may also need Samsung’s USB drivers installed separately. macOS and Linux typically recognize Samsung phones without extra drivers.

If adb devices shows “unauthorized,” unplug the cable, revoke USB debugging authorizations in Developer Options, and reconnect. The Allow prompt will appear again.

#Security Risks of Leaving USB Debugging On

USB debugging gives any connected computer full access to your phone’s file system and the ability to run commands as if it were the device owner. That’s powerful, and it’s exactly why Samsung recommends disabling it when you’re not actively using it. According to Samsung’s security advisory, leaving debugging enabled on a daily-use phone creates unnecessary attack surface.

Specific risks include:

• Anyone who connects your phone to a computer can extract files, install apps, or wipe data without your lock screen PIN
• Malicious USB chargers (called “juice jacking” stations) at airports or cafes can exploit an open debugging connection
• ADB access bypasses some app-level security restrictions that normally protect your data

The fix is straightforward. When you’re done debugging, go back to Settings > Developer Options and turn off USB Debugging. The whole process takes about 5 seconds.

#How to Enable Wireless Debugging on Samsung?

Samsung phones running One UI 3.0 (Android 11) or later support wireless ADB debugging. This lets you run ADB commands over your Wi-Fi network without a USB cable.

1. Open Settings > Developer Options

2. Toggle Wireless Debugging on

3. Tap Wireless Debugging to open its settings

4. On your computer, open a terminal and type adb pair <IP>:<port> using the pairing code shown on your phone

5. After pairing, connect with adb connect <IP>:<port>

Your computer and phone must be on the same Wi-Fi network. As Android’s wireless debugging guide confirms, the pairing only needs to happen once per computer.

Wireless debugging is slower than USB for large file transfers, but it works well for log viewing, app installation, and shell commands. We tested it on a Galaxy S23 and the connection stayed stable for over 2 hours.

#Troubleshooting Common USB Debugging Problems

Not every connection goes smoothly. Here are the problems we ran into during testing and how we fixed them.

Phone not detected by computer: Try a different USB cable. Cheap cables often lack data wires and only charge. If your phone shows “Charging this device via USB” in the notification bar, tap it and switch to File Transfer (MTP) mode. We went through 3 cables before finding one that worked on a Galaxy A14 we were testing.

“Unauthorized” in adb devices output: Revoke USB debugging authorizations in Developer Options, unplug, and reconnect. Tap Allow on the phone’s popup.

Developer Options disappeared after a software update: Some One UI updates reset Developer Options visibility. Just repeat the 7-tap process on Build Number to bring it back.

ADB commands return “no devices/emulators found”: On Windows, open Device Manager and look for your phone under “Portable Devices” or “Other Devices.” If it shows a yellow warning triangle, reinstall the Samsung USB drivers from Samsung’s developer site. This problem doesn’t happen on macOS or Linux.

If your phone has restricted access changed errors, that network issue is unrelated to USB debugging and won’t affect your ADB connection. For Samsung-specific data recovery before attempting anything risky through ADB, check our guide on recovering contacts after a factory reset.

#Bottom Line

Start by tapping Build Number 7 times in Settings > About Phone to unlock Developer Options, then toggle USB Debugging on. The process works on every Samsung Galaxy model from the S5 through the S24 Ultra. Disable it when you’re done, and back up your data before making any system-level changes through ADB. If you prefer cable-free connections, wireless debugging on Android 11+ is a solid alternative that we’ve found stable in everyday use.

#Frequently Asked Questions

#Is USB debugging safe on Samsung phones?

Yes, enabling it won’t change anything on your phone. The risk comes from what you do afterward. Keep it off when you’re not using ADB.

#Does USB debugging work on every Android phone or just Samsung?

It works on every Android phone, not just Samsung. Any device running Android 4.2 or later has the same Developer Options menu with USB debugging inside it. Google Pixel, OnePlus, Xiaomi, Motorola, and all other brands follow the identical 7-tap-on-Build-Number process to unlock it. The only thing that changes between brands is where “About Phone” sits in the Settings menu, and sometimes whether you need to tap “Software Information” first or go directly to “Build Number.”

#Will enabling USB debugging void my Samsung warranty?

No. Toggling USB debugging is a standard Android feature and doesn’t void your warranty. However, using ADB to root your phone, flash custom firmware, or trip Samsung’s Knox security counter will void it. The debugging toggle itself is completely reversible and Samsung expects developers to use it.

#Can I use USB debugging to recover data from a broken screen?

Only if USB debugging was already turned on before the screen broke. With ADB access, you can pull files, capture screenshots, and even mirror your entire display to a computer, all without touching the phone screen at all. If debugging wasn’t enabled beforehand, ADB has no way to connect, and your only option is a Samsung-authorized repair center or a third-party data recovery service that can access the storage chip directly.

#What’s the difference between USB debugging and File Transfer mode?

File Transfer mode (MTP) lets you drag and drop files between your phone and computer like a flash drive. USB debugging gives your computer command-line access to Android’s operating system through ADB. You can have both enabled at the same time, and they serve completely different purposes.

#Do I need to install Samsung drivers on my Mac?

No. macOS handles it natively.

#How do I turn off USB debugging when I’m done?

Open Settings > Developer Options and toggle USB Debugging off. You can also disable the entire Developer Options menu by toggling the master switch at the top, which turns off USB debugging along with all other developer settings. Either approach takes about 5 seconds.

#Can USB debugging drain my battery?

USB debugging itself uses almost no battery. The ADB daemon running in the background consumes less than 1% per hour in our testing on a Galaxy S24. Battery drain only becomes noticeable during active data transfers or continuous log streaming over ADB, and even then it’s minimal compared to screen-on time.