Hello guys.
I need a help with specific adb shell command because I don't want to root my phone, so if this is possible please do tell me.
I need to change in /system/emui/lite/prop/local.prop set ro.build.hw_emui_lite.enable to false
I tried with adb shell settings put system hw_emui_lite false but it doesn't work, can someone tell me how to do it?
Here is how I succeeded to enable USB debugging (also adb and remote view) on Samsung Galaxy Note 4 with broken screen.
1. Following the DeathDrifterz's advice I was able to set the device in recovery mode with ROOT access and adb :
DeathDrifterz said:
So, I have a Galaxy Note 4, broken screen, broken digitizer. Do not have access too an MHL cable or Mouse to hook up to TV. The phone has a password and usb debugging disabled, so kies and the computer won't recognize it. Not even when in download mode. I did flash CWM rcovery to the phone, but this still wouldn't allow me to see the phone in recovery mode. What did work was I downloaded the trial version of Wundershare Dr. Fone, booted phone into download mode, let the program run and start searching for files. Stopped the program. Unplugged the phone. Exited Dr Fone. Opened cmd in the platform-tools folder of the SDK platform. At this point, I was now able to see the phone, in recovery, listed under ADB Devices.
So Dr Fone took the phone from download mode (vol down + home + power, then press vol up after vibrate) to recovery mode once it started finding files. Disconnect the phone from the PC, exit Dr Fone and reconnect the phone to the PC. It will still be in recovery mode. Open cmd prompt in the platform-tools folder. adb devices shows phone in recovery, used adb pull /sdcard/ and it worked like a charm. All files on the phone have now been downloaded.
Broken screen, no digitizer, password locked, USB debugging disabled, and it was free. Took 5 minutes once Dr Fone was downloaded (will take longer if you don't have the sdk tools.)
Hope it helps.
Click to expand...
Click to collapse
2. In other forum I found tutorial how to enable USB debugging from recovery with root access :
Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken).
Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery mode.
To mount the respective directories, type:
Code:
./adb shell mount data
./adb shell mount system
Get the persist.sys.usb.config file in your system using:
Code:
./adb pull /data/property/persist.sys.usb.config /Your directory
Now open that file in a texteditor and edit it to mtp,adb and save.
Now push the file back in the device:
Code:
./adb push /your-directory/persist.sys.usb.config /data/property
Get the build.prop file:
Code:
./adb pull /system/build.prop /your-directory
Add these lines:
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Push build.prop back into the device:
Code:
./adb push /your-dir/build.prop /system/
This way you enabled USB debugging on your device. But you still can't connect. Why? Because it asks for RSA verification. If you could view your display then you could easily tap on YES to authorize the device.
3. Skipping RSA verification :
The ADB keys (after authorization) are saved in /data/misc/adb/adb_keys, so I have one Samsung Galaxy S3 with working display which already authorized my PC.
So I got the adb_keys file from it. I connected the Samsung Galaxy S3 to my PC and use :
Code:
./adb pull /data/misc/adb/adb_keys
Then reconnected the Note 4 and pushed the file in it:
Code:
./adb push /your-dir/adb_keys /data/misc/adb/adb_keys
4. Reboot! And Voila: the devices boots normally and adb connects without asking for verification.
After that I used Vysor chrome extension and Vysor apk to view the device screen and act with the device.
I installed the apk with :
Code:
./adb install apk_name.apk
Sources :
https://forum.xda-developers.com/showthread.php?t=2395047
https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
https://www.vysor.io/
It works! With the first method.
I have Samsung Galaxy s5, lineage os 14.1,
After my screen broke, I couldn't see my device through adb devices, no matter what driver I have installed - and believe me I've tried all the methods.
Then I've installed CWM recovery, adb recognized it in devices but I wasn't able to pull sdcard with adb pull command in Windows 7. I got access denied.
Then I saw this post and I got access to sdcard!
Works on OnePlus One with Lineage 14.1
Works like a charm on my OnePlus One with lineage 14.1
Just want to mention that if you have problems mounting /data and/or /system
I got help from this post: https://forum.xda-developers.com/galaxy-s2/help/mount-adb-t1107545
Basically, the dirty solution I found with help from kaukassus post was:
1.
Code:
adb mount
- to view name of available mounts and identify /system and /data
2.
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/[U]mmcblk0p28[/U]
underlined is the part that is different
- to mount the data folder. Do the same for system. Then I just followed the steps from this tutorial.
The part with the RSA verification I resolved with a little help from https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Enable ADB (2/2): RSA verification
For the RSA verification that you asked to bypass, I don't know whether it would work in your device, but it worked in my little experiment. In Lollipop, the ADB keys (after authorization) are saved in /data/misc/adb/adb_keys. Your private key is saved in computer. In Linux the directory location is $HOME/.android/. On Windows that usually translates to %USERPROFILE%.android, but keys might end up in C:\Windows\System32\config\systemprofile.android in some cases.
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse
Thanks for post
Worked top to bottom, on my Galaxy S5 6.0.1 (ALEXNDR ROM)!
Used step .2, .3 and oledolez tips aswell.
Got the screen cracked and black, went crazy because I had the SD card encrypted and couldn't get the stuff outta there...
Thanks a lot!
Hugo
GS5 CWM Stock ROM
Hello ! I broke my gs5(sm-g900f)'s screen and now it is constantly black. I tried everything on the thread and my device is always shown as unauthorized in vysor or when checking in ADB with /adb devices. This means I have succeeded to enable USB Debugging through ADB, however I must be having problems with the RSA key. Any help would be appreciated!!
Thanks in advance !
Dan
P.S The phone was completely stock when I broke it and I blindly installed cwm-6.0.4.7 and CF-auto-root with odin, so maybe there is a problem with that ?
what if the partition is encrypted? How I would enter the boot password with a broken screen?
xaviermchot said:
what if the partition is encrypted? How I would enter the boot password with a broken screen?
Click to expand...
Click to collapse
I had the same problem and fixed it in TWRP doing this command:
Note: Use this command only if your /data/ partition has the ext4 file system. There are some other similar commands for other file systems, but i don't remember they.
Code:
adb shell make_ext4fs /dev/block/[B]mmcblk0p20[/B]
(Bold part can change depending of your device)
Then just do a normal wipe and flash again the ROM.
MiroBiala said:
Here is how I succeeded to enable USB debugging (also adb and remote view) on Samsung Galaxy Note 4 with broken screen.
1. Following the DeathDrifterz's advice I was able to set the device in recovery mode with ROOT access and adb :
2. In other forum I found tutorial how to enable USB debugging from recovery with root access :
Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken).
Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery mode.
To mount the respective directories, type:
Code:
./adb shell mount data
./adb shell mount system
Get the persist.sys.usb.config file in your system using:
Code:
./adb pull /data/property/persist.sys.usb.config /Your directory
Now open that file in a texteditor and edit it to mtp,adb and save.
Now push the file back in the device:
Code:
./adb push /your-directory/persist.sys.usb.config /data/property
Get the build.prop file:
Code:
./adb pull /system/build.prop /your-directory
Add these lines:
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Push build.prop back into the device:
Code:
./adb push /your-dir/build.prop /system/
This way you enabled USB debugging on your device. But you still can't connect. Why? Because it asks for RSA verification. If you could view your display then you could easily tap on YES to authorize the device.
3. Skipping RSA verification :
The ADB keys (after authorization) are saved in /data/misc/adb/adb_keys, so I have one Samsung Galaxy S3 with working display which already authorized my PC.
So I got the adb_keys file from it. I connected the Samsung Galaxy S3 to my PC and use :
Code:
./adb pull /data/misc/adb/adb_keys
Then reconnected the Note 4 and pushed the file in it:
Code:
./adb push /your-dir/adb_keys /data/misc/adb/adb_keys
4. Reboot! And Voila: the devices boots normally and adb connects without asking for verification.
After that I used Vysor chrome extension and Vysor apk to view the device screen and act with the device.
I installed the apk with :
Code:
./adb install apk_name.apk
Sources :
https://forum.xda-developers.com/showthread.php?t=2395047
https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
https://www.vysor.io/
Click to expand...
Click to collapse
Dear experts,
I've been trying to follow the above steps but cannot get data and system mounted:
PS C:\Users\Azubi\AppData\Local\Android\Sdk\platform-tools> adb devices
List of devices attached
52001077b43913d3 recovery
PS C:\Users\Azubi\AppData\Local\Android\Sdk\platform-tools> adb shell mount data
mount: mounting /dev/block/mmcblk0p21 on /data failed: Device or resource busy"
I'm trying to access a Galaxy S5 mini with broken screen and digitizer. It's rooted and runs with TWRP and Lineage OS.
The aim is to enable usb debugging in order to mirror the screen on pc.
Has anyone been encountering this already and could help?
Many thanks
Max
I'm user of Samsung galaxy tab S3 wifi model no root.(SM-T820NZSAKOO)
so, I tried adb shell settings put global guest_user_enabled 0 but it's not works.
and, I want remove guest account use no root. what should I do?
---------------
My Question is:
How do I go about using the "adb keygen" command to generate a key pair for each device. AND where do I move those keys so that the devices can connect to each other via the ADB command line interface?
---------------
Currently, my PC is out of order. So I have no way to use ADB via a PC. What I have managed to accomplish so far is rooting my Galaxy Tab 3 [Magisk], Galaxy S5 [SuperSu], and Galaxy S3 [SuperSu]. The devices are running Resurrection Remix Oreo , Lollipop, and Kitkat 4.4, respectively.
***
*** I want to use my tablet [Galaxy Tab 3] as the ADB Host for all my other androids to connect to. This way I can issue ADB commands over the network from my tablet's Termux environment. And I know my current issue has to deal with the ADB_VENDOR_KEYS, as well as "Step 5/6" in connection handshake outlined in the screenshot from "cstyan's adb documentation" on github.
Now each device is equipped with a Terminal Emulator or Termux, and an ADB binary compiled for the ARM architecture. [Android Debug Bridge version 1.0.36
Revision e25a9312d628-android]
I can connect to ADB over the network. I've already gotten the GS5 to connect to Tab3's ADB server. I can run the "adb devices" command after successfully connecting to a specific IP address, but the command always lists the device as "unauthorized". This is shown in my screenshot from my CLI. I'm being tripped up by oversight here because this is typically done automatically, not manually.
Do I need to keygen a pair on the tablet and copy that key-pair to my other devices? Or does each device need a copy of each other device's adb key? This should work. I should just have to do the legwork manually, since this isn't the standard way. On normal Linux/Windows the adb key is stored in the User's profile root in the ".android" folder, but where is the counterpart on the device itself? I already have my Tablet's private key in "/data/misc/adb/adb_keys"
I feel I am on the last step here. Where do I place the public keys on the device? All I need to do is authorize the device using my manually generated adb key. Everything else works, and then I wouldn't need to have my PC so high on my priority list. Can someone please help clarify the step or two that I am missing here please?
Hello,
There is an stock Samsung Galaxy S21 with stock Samsung / phone operator ROM, where the owner forgot his password (not the PIN code).
I don't want to wipe the phone, as owner wants to access the data store on the phone.
It is clear, that once USB debugging enabled, I can use Android SDK tools (adb.exe) to access the file system to delete the password key files to remove the password (adb shell -> cd data/system -> su -> rm *.key)
Since the phone is locked with password, i can't access settings to enable USB debugging.
Is it possible to enable USB debugging in the recovery menu?
Thank you for your help!
Not possible.
jwoegerbauer said:
Not possible.
Click to expand...
Click to collapse
Thank you for the answer.