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.
Related
I currently have 5.1.1 installed on my honor 5x and am able to use adb automatically without accepting an RSA prompt (have installed twrp, rooted, etc.) but when I dload a MM stock rom and use usb debugging it is unauthorized and I get no RSA prompt I've even gone as far as to delete /data/misc/adb from my device and adbkey.pub from my desktop but there is still no pop up authorization in MM
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
ShadySquirrel said:
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
Click to expand...
Click to collapse
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Tsunetoma said:
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Click to expand...
Click to collapse
Tried toggling the debugging switch? I had issues like these on one of my previous devices, but usually these were fixed with a simple port change or debug off/on switch, if revoke->replug didn't work.
Have you checked drivers, or if dmesg says something about the device, if you're on Linux? Sometimes even running multiple adb instances (like one from terminal and one from Android Studio, for example) can cause this behviour.
Enable rsa key authentication
Hello,
I have some rooted devices running under android 5.0 in with I have removed some stuff + the settings. BUT the user is able to add applications - including wifi managers- thru ADB commands.
My question is : can i disable the USB debugging thru a command of ADB?
I installed a Substratum overlay which screwed up my phone and now every time I boot into system the screen remains black. I'm on RROS 6.0.0 (Android 8.1) so I was only able to install a TWRP without decryption thus I can't access system/data in order to delete the overlays there. The only way to access it now would be over ADB while the phone is booted to system. The problem is, although I've enabled USB debugging I'd have to enable USB file transfer (default set to charge only) in order to be able to access my phone via USB. Right now I always get the output:
Code:
[email protected]:~$ sudo adb devices
List of devices attached
???????????? no permissions
Is there any way to enable USB file transfer or just generally access /system/data without any inputs while being in system? I know, I could just do a factory reset but I'd rather avoid that... Any help would be appreciated!
Hello, I have an old alcatel onetouch idol S with some pictures and videos in it I'd like to get. The touchscreen is broken though, so I can't access the phone.
I'm trying to use ADB tools to pull all de data from the phone the problem is that USB debugging isn't enabled on it. So I launched the phone in Clockworkmod and clicked update from ADB. From there ADB tools could detect the phone. The problem is that when I type "adb devices" , under "attached" it's written sideload, but for all the tutorials I've watched it should be written "device" so naturally when i typed the command to backup de data (adb pull / data / media / clockworkmod / backup ~ / Desktop / Android-up) it didn't work (adb: error: connect failed: closed).
So does anyone know what to do so that the phone is detected as a device, or a command that works even though the phone is in sideload ?
Or maybe activating USB debug with adb ?
You can't activate USB-Debugging via ADB: This MUST be done in device's Settings->Developer Options.
jwoegerbauer said:
You can't activate USB-Debugging via ADB: This MUST be done in device's Settings->Developer Options.
Click to expand...
Click to collapse
Yeah that's what I thought but my touchscreen is broken so that's not going to happen :/
hubble_ said:
Yeah that's what I thought but my touchscreen is broken so that's not going to happen :/
Click to expand...
Click to collapse
If device is rooted, another option would be to have an APK that starts on device's boot and then modifies Android's settings.db what you could try to sideload.
Recover files from phone with a broken screen, no USB debugging and set as "Charge"
Hey,
So, I'm trying to recover files from my previous phone, a Xiaomi Redmi Note 5 Pro. It can boot Android and also get into recovery mode, but I can't see anything on the screen (it's completely black) and I think it doesn't register touches either.
The big problem is, USB debugging is off and USB mode is set to charging only (no MTP).
If I enter TWRP, adb recognizes it (it's listed when you type "adb devices"), but what can I do from there? Is there a way to enable MTP through TWRP adb? I tried some commands like "adb shell" or "adb shell <command>" but it says these commands don't exist or just gives me a list of some other commands.
Is there just no way to recover my files?
Thanks for your help regardless.
@Ulfys
From your description it seems like you already have ADB access from the recovery ROM and it looks like you have access to your data partition. Therefore you can backup your data and migrate it to a new phone
Note: Being in Recovery mode you can only use adb pull, adb push and adb reboot
That doesn't help if I want to recover my files in the internal storage, though. And I don't have any other rooted device with TWRP - even if I had one, flashing another phone's data partition isn't a great idea.
Enabling MTP somehow would be a lot more convenient.
Ulfys said:
Enabling MTP somehow would be a lot more convenient.
Click to expand...
Click to collapse
Enabling MTP requires to have access to Android terminal: adb shell
EDIT:
IMO the only option you have is to pull data from device: adb pull