USB debugging via Recovery: how to enable on Android with a locked screen

Have you forgotten the password for your Androidsmartphone, and USB debugging was disabled? Or is the device stuck at the logo after an unsuccessful update, and the only way to save the data is to connect via ADB? In such cases, standard methods for activating developer mode are not available, but there is a way out: enable debugging via USB debugging recovery (recovery mode).

This method works even on completely locked devices where it is impossible to enter the settings. We will analyze step-by-step guide for Samsung, Xiaomi, Huawei and other popular brands, explain what tools you will need, and warn about possible risks. Important: the method requires the presence of custom recovery (for example, TWRP) or access to stock recovery with support ADB sideload. If you have a standard recovery without additional functions, read alternative solutions at the end of the article.

Why standard methods of enabling debugging do not work

Under normal conditions USB debugging activated through the menu Settings → About phone → Build number (7 taps) and further in Developer options. But if:

• 🔒 The screen is locked with a password, pattern or fingerprint;
• 📱 The device does not boot beyond the logo (bootloop);
• 🔄 The settings have been reset and debugging is disabled automatically;
• 🛠️ The smartphone is “bricked” after the firmware,

—then the standard path is not available. This is where recovery comes to the rescue - an alternative boot mode that allows you to control the device at a low level. However, not all recoveries support the necessary functions. For example, stock recovery from Samsung or Huawei is often limited to basic options like resetting data.

Key difference custom recovery (for example, TWRP or OrangeFox) - the presence of a terminal ADB, the ability to mount partitions and edit system files. It is through them that you can manually enter debugging parameters in a file build.prop or download a modified one settings.db.

What you will need to enable debugging through recovery

Before you start, prepare:

• 🖥️ Computer with Windows, Linux or macOS;
• 🔌 Cable USB Type-C/Micro-USB (original, without damage!);
• 📦 Installed drivers ADB i Fastboot (you can download from official Android website);
• 📱 Unlocked bootloader (bootloader) - for most brands, except Xiaomi and some models Samsung;
• 🛠️ Custom recovery (for example, TWRP) - if the stock recovery does not support ADB.

If you have a stock recovery, check if it contains the item Apply update from ADB or ADB sideload. On some devices (for example Google Pixel or OnePlus) this option is present by default. For the rest, you will need to first install TWRP.

⚠️ Attention: On devices with a locked bootloader (for example, Huawei or Sony), installation custom recovery is impossible without unlocking. This will lead to a complete data reset!

Also prepare:

• 📄 A backup copy of important data (if the device somehow turns on);
• 🔋 Battery charge at least 50% - to avoid sudden shutdown;
• 🔍 Information about the device model and version Android (can be found through fastboot getvar all).

Install ADB and Fastboot on the PC|

Download the firmware or modified settings.db (if required)|

Check for custom recovery|

Disable the antivirus (it can block ADB)|

Connect the phone to the PC and make sure that it is detected in Device Manager-->

Step-by-step guide for devices with TWRP

If your smartphone has TWRP or another custom recovery supported ADB, follow these steps:

1. Turn off the device. data-i="109">(or on older models); mount the partition).

   • 📱 Samsung: Power + Volume Up + Bixby (or Home on older models);
   • 📱 Xiaomi/Redmi: Power + Volume Up;
   • 📱 Google Pixel/OnePlus: Power + Volume Down, then select item Recovery Mode.

INSERT INTO secure (name, value) VALUES ('adbd', '1');

After the reboot USB debugging will be enabled automatically. Connect the device to the PC and check availability with the command:

adb devices

⚠️ Attention: On some firmware (for example, MIUI or EMUI), after such manipulations the protection may work Anti-Rollback, which will lead to blocking of the device Before editing settings.db Make sure the firmware version is compatible!

Alternative method: editing build.prop

If access to settings.db is impossible (for example, due to partition encryption /data), you can try enabling debugging via file build.prop. This method is less reliable, but sometimes. works on older versions Android (up to 9.0).

1. In TWRP go to Mount → System (if the partition is not mounted).

2. Open the file /system/build.prop in a text editor ( TWRP has a built-in editor).

3. Add the following lines to the end of the file:

   persist.service.adb.enable=1
   persist.service.debuggable=1
   persist.sys.usb.config=mtp,adb

4. Save the changes and reboot the device.

After reboot, check if the device appears in the list adb devices. If not, return to the method with settings.db.

Features for different brands

The process of enabling debugging through recovery may vary depending on the manufacturer. Let's consider the nuances for popular brands:

Xiaomi/Redmi/POCO

On devices with MIUI protection Anti-Rollbackis often used, which blocks changes to settings.db. Alternative method:

1. Install TWRP for your model (for example, through fastboot flash recovery twrp.img).
2. In recovery, select Mount → Data and format the partition (this will delete all data!).
3. Download modified settings.db for MIUI (search on 4PDA according to the device model) and replace the original file with it.

Samsung

On most devices Samsung stock recovery does not support ADB. Solution:

• 🔧 Install TWRP via Odin (requires an unlocked bootloader).
• 📁 Use the method with build.prop, like this how /data on Samsung is often encrypted.

Huawei/Honor

Devices Huawei s Kirin-processors have a closed bootloader. If it is locked:

• 🔓 Unlock the bootloader through the official service Huawei (unlock code required).
• 📥 Install TWRP for Kirindevices (for example, OrangeFox).
• 🛠️ Use the method with settings.db, but be prepared to reset the data.

⚠️ Attention: On devices Huawei with EMUI 10+ and newer editing settings.db can lead to activation eRecovery and a forced reset!

Frequent errors and how to avoid them

When enabling debugging through recovery, users often encounter the following problems:

• 🚫 The device is not detected in adb devices:

  Check the drivers, try a different cable or USB port. On Windows sometimes installing drivers manually through Device Manager helps.

• 🔒 Cannot mount /data:

  If the partition is encrypted, try entering the password in TWRP (item Mount → Data → Decrypt Data). On some firmware this is not possible - you will have to format /data (data loss!).

• 📉 After the changes, the device froze:

  Return to recovery and undo the edits in build.prop or settings.db. If the system does not boot, reset via Wipe → Factory Reset.

• 🛡️ Protection triggered Anti-Rollback:

  On Xiaomi this leads to blocking of the device. The only solution is to flash the official firmware via Mi Flash Tool with clearing all data.

On devices with Android 12+ and higher, editing settings.db can lead to resetting all settings during the next system update. Scoped Storage.

Security: risks and how to minimize them

Enabling USB debugging via recovery is a powerful tool, but it is fraught dangers:

• 🕵️ Attack vulnerabilities: If debugging is enabled, an attacker with physical access to the device can steal data via ADB.
• 🔧 Violation of system integrity: Improper editing build.prop or settings.db can lead to bootloop.
• 📵 Loss guarantees: Unlocking the bootloader and installation custom recovery void the warranty of most brands.

How to reduce risks:

• 🔐 After solving the problem disable debugging with the command:

  adb shell settings put global adb_debug 0

• 📱 Set a strong password on the device and turn it on encryption.
• 🛡️ Use Magisk to hide the root status from applications (if installed TWRP).

⚠️ Attention: On devices with Samsung Knox (for example, Galaxy S/Note) any manipulations with the recovery lead to flag trigger Knox 0x1which blocks operation of Samsung Pay, Secure Folder and other functions.

FAQ: Answers to frequently asked questions

adb sideload settings.db