> Attention!

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Enable USB debugging



Rep: (1944)
Enable USB debugging

The method is suitable for many Android-devices
OS and firmware: Android

Description of the problem:
It happens that for various reasons (the screen is broken, the touchscreen does not work, there is no possibility to connect a USB mouse), it is impossible to turn on USB debugging in the device. Faced with such a problem, I propose a solution and the necessary tools with which I managed to solve this problem.
The main condition is that your device should already have a custom Recovery installed.(CWM or TWRP), which will provide full root access to the device.

There have been actions:
1. On the PC, unpack the root of the C: \ drive:
Attached fileplatform-tools.zip(532.01 KB)
Attached fileQtADB-cwm_edition.zip(11.06 MB)
In the C: \ Sqlite3_Windows folder previously created in the root of the C: \ folder, unpack:Sqlite3.zip
2. Download the device to the recovery mode (using CWM or TWRP) and connect it to the PC.
3. Run QtADB.exe. If the program asks, then show her the path to adb.exe.
4. Press the "Advanced" button and make sure that the / data partition is mounted:
Attached Image

5. Press the "Files" button, in the left pane, open the C: / Sqlite3_Windows / folder and in the right pane / data/data/com.android.providers.settings/databases/ folder, then drag / copy the settings.db file from the right pane to the left:
Attached Image

6. On the PC, run the command line (cmd.exe) and execute the commands in turn:
cd C: \ Sqlite3_Windows (press the Enter button)
sqlite3 settings.db (press Enter)
update secure set value = 1 where name = 'adb_enabled'; (press the Enter button)
.quit (press Enter)
Attached Image

7.In the QtADB window, update the left panel and drag / copy the edited settings.db file to its place in the right panel with overwriting.
8. After the device is rebooted, it will be possible to work with it in the regular mode using the QtADB programs,Adb, MyPhoneExplorer and others.

Instructions for Android 6/7/8

Starting with Android 6, Google added a multi-user mode to the OS and increased security measures. In this regard, the system settings parameters stored in the Secure, System and Global tables werecarried overfrom the settings.db database to separate xml files along the way/ data / system / users / 0 / and now the procedure for enabling USB debugging using custom recovery is much simpler (sqlite3.exe for Windows is no longer required).
In the right panel of QtADB, go to the specified path, open with the text editor settings_global.xml, find the line with the name adb_enabled and set the value 1 (instead of 0) in the field value = "1"
Android 7
Attached Image


p.s. If someone has other ways to solve this problem, you are welcome to share your experience!

Post has been editedvitaly51370 - 29.02.20, 18:02
Reason for editing: Instructions for Android 6/7/8



Rep: (2808)
M



Rep: (-6)
I have a login 3 in the planet, I don’t often have such a function! Why so?



Rep: (0)
If you have Windows 7 (did not check others), and if your device is not recognized in Windows Device Manager when entering recovery mode, installation will helpUniversal adb driver. Thanks to the author, after the tambourine I mentioned, I managed to apply the method :)



Rep: (0)
* vitaly51370
3. Run QtADB.exe. If the program asks, then show her the path to .adb.exe

I unpacked everything according to the instructions. The interface does not start as on the screen, therefore I can not specify the path to adb.exe.



Rep: (1944)
* mihnik, this is a regular executable exe file for Windows, so the question is not for me.



Rep: (0)
3. Run QtADB.exe. If the program asks, then show her the path to .adb.exe

* mihnik,
It does not even connect through recovery. Handed over to repair. A week later, returned with a verdict: restarted. I worked exactly before installing custom recovery and getting root rights. Now the computer does not see again. Tell me where to dig?



Rep: (1944)
* mihnik, in normal mode, when enabled in the Debug via USB settings and installed drivers (see the post above), after executing the following commands in turn:
cd C: \
adb devices
should be something like this:
Attached Image

For recovery mode, the answer will be slightly different.

Post has been editedvitaly51370 - 10.05.15, 21:40



Rep: (0)
* DennyZ,
DennyZ @ 11/18/2014, 3:37 PM*
If you have Windows 7 (did not check others), and if when entering recovery mode your device is not recognized in the Windows Device Manager, then the installation of Universal ADB Driver will help. Thanks to the author, after the tambourine I mentioned, I managed to apply the method

It did not help (In general, does not see the computer phone. Cords and computers changed.
Oppanki! Just started dancing with tambourines, as the bodies saw the light !!! Taki did not understand the reason !!!

Post has been editedmihnik - 04.01.15, 09:43
Reason for editing: Adding text



Rep: (0)
Sooner rejoiced (Again nivkakuyu !!! And I noticed that the connection is lost after using Navitel navigator. Ie, for the first time, the usb connection disappeared after installing the program, and yesterday, after using it, there is also no connection.



Rep: (0)
* vitaly51370
vitaly51370 @ 01/03/2015, 13:12*
mihnik, in the usual mode, when enabled in the "USB debugging" settings and installed drivers (see the post above), after executing the following commands in turn:
cd C: \
adb devices
should be something like this:
Reduced by 52%

828 x 570 (25.74 KB)

For recovery mode, the answer will be slightly different. The visibility of the device in recovery mode depends on how custom recovery is done.

And I like this)

Attached images
Attached Image



Rep: (1944)
* mihnik,
1. On the PC, unpack the root of the C: \ drive:
platform-tools.rar
Done that way?
It is to the root of the C: \ drive and no additional folders, especially with Russian letters in the title!

Post has been editedvitaly51370 - 06.01.15, 15:51



Rep: (0)
* vitaly51370
vitaly51370 @ 01/06/2015, 15:43*
Done that way?
It is to the root of the C: \ drive and no additional folders, especially with Russian letters in the title!


Attached images
Attached Image



Rep: (0)
Thanks for the instruction! In general, everything seemed to work out, I got to the file system. commands listening. but there is a nuance.
The body can only be seen in the recovery. If you load in normal mode - the device is silent. even in Windows is not defined. the screen is broken. you need to see the body in normal mode in order to work from a remote desktop (which software you need to save and tear out the info from it, the easiest way to do it manually is through the graph interface than digging through the guts.)
what am i doing wrong? =)
device nehus4.



Rep: (1944)
* jq87, Let's say “USB debugging” is not enabled, but there are other modes for connecting a device to a PC (with pre-existing / installed drivers in Windows) USB Mass Storage or MTP. And if the PC does not see the device, it turns out that in the normal mode, the Android OS does not load or is damaged. And in the recovery-mode, it loads its own mini-OS with a minimum set of functions for servicing the device, completely independent of the normally installed OS. By the way, what version of Android is installed?



Rep: (0)
why not see the tabs advanced, etc.
I go to the menu and there they are inactive

Attached images
Attached Image



Rep: (1944)
* tigranu444 in general, the work of the qtADB program is not discussed here, for it there is a corresponding theme . And then, what is this version of the program (I did not post this)? In what mode is the device connected (similar to the fastboot mode)?



Rep: (0)
Can the fastboot mode not plow due to the fact that the laying is not included?



Rep: (1944)
* tigranu444 to work fastboot-mode does not require the inclusion of "USB debugging", because This mode works via USB before the OS boots.

Post has been editedvitaly51370 - 26.01.15, 23:49



Rep: (0)
And here I have

install adb to disk c: \ Users \ Misha should help. In cmd you write c: \ Users \ Misha and you put it stupidly on disk c. put it like this C: \ Documents and Settings \ SVS and all the buzz

Post has been editedSlavon-80 - 17.02.15, 18:12
Reason for editing: removed too much



Rep: (13)
adb_enabled in the tableglobal is located and not in secure
1. ****
2. ****
3. update global set value = 1 where name = 'adb_enabled'; (press the Enter button)
4. ****


Full version    

Help     rules

Now: 01.12.20, 15:09