Hello everyone, hope you're fine,
Unfortunately, I had bad luck and utterly smashed my device display (Samsung Galaxy A72) which has a PIN to unlock the device access.
My problem here is that I'm unable to accept the authorization for adb connection, just can't touch the accept popup (which I suppose is "being displayed" on the broken screen).
There is by any chance, a way to send a touch signal using the adb prompt?
The current status when I try any command except the
Code:
$ adb devices
is:
Code:
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
In case I can get this resolved, the next steps would be to try to send the adb input keyevent accordingly in order to unlock it by PIN.
Thx in advance to anyone who is able to help
Note: I'm using Linux or Mac, so MS Windows wouldn't help too much.
Related
I'm a nube and trying to root my Coby Kyros MID 7036. I get as far as using the adb shell command: chmod 0755 rageagainstthecage-arm5.bin ./rageagainstthecage-arm5.bin. After that, it gets stuck at "adb connection will be reset. restart adb server on desktop and re-login." Then I close the elevated cmd, open a new one and restart the adb server. Typing in the same adb shell command, I get past "adb connection will be reset", but my device is marked as offline. I end up having to restart the device to get it online, but then I just repeat the process! What do I do?
ijmeurer said:
I'm a nube and trying to root my Coby Kyros MID 7036. I get as far as using the adb shell command: chmod 0755 rageagainstthecage-arm5.bin ./rageagainstthecage-arm5.bin. After that, it gets stuck at "adb connection will be reset. restart adb server on desktop and re-login." Then I close the elevated cmd, open a new one and restart the adb server. Typing in the same adb shell command, I get past "adb connection will be reset", but my device is marked as offline. I end up having to restart the device to get it online, but then I just repeat the process! What do I do?
Click to expand...
Click to collapse
Try this when it prompts you to restart the connection - don't close the terminal and use:
adb kill-server
adb start-server
and then try and continue.
There's more rooting info and a system dump if you get into serious trouble here: http://www.androidtablets.net/forum...ead-first-development-index-root-utility.html
I want to unlock my cousin's tab who recently passed away and no one knows the passcode so after some googling i found that you can do it via ADB.
(https://forum.xda-developers.com/showthread.php?t=2620456)
The device successfully connects with my pc but when I execute "adb devices" it shows;
.......................... unauthorized
and running adb shell shows;
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
With the device locked Im unable to authorize my computer so I decided to search something for that too and found this article where it tells u to pull keys from another device and push it into your locked one while in recovery mode and this is where Im stuck. Whenever Im in recovery mode, adb devices shows nothing so if someone of you could help me would be awesome.
Hi, I have a Xiaomi phone with the 3 buttons apparently broken.
I'm trying the adb commands to power up the phone, but unfortunately I don't have the adb enabled on the device (infact when I try to use the command "adb reboot" the system gives me the message "device unautorized").
do anyone knows how to use the adb commands to enable the adb on the phone to power up again?
thank you very much (I'm so depreeeeessed)
ADB ( read: ADB daemon ) is part of Android OS.. Thus it should be obvious when Android isn't running you can't run any ADB command where it doesn't matter whether USB debugging got enabled or not.
Hello, I am new to this forum, I have a boot looped Samsung A51. That has been water damaged.
And when I try to use ADB and type "fastboot oem unlock" the cmd says waiting for device. Or when I type root in ADB, the cmd says unable to connect for root: closed.
So I have a boot locked phone that does not respond to ADB commands. I am wondering if the hardware is damaged? Any advice is appreciated. Thank You.
If I type adb devices, my device shows up. It just doesn't respond to any commands and I can't push any files...
I changed the resolution to 500x1080 using the android app "pixels" and restarted the phone by accident and now I cant get past the lock screen as it needs my pattern password to get in. What has happened is that the screen is cropped so far, there is no way I can input the pattern as the grid is not even on the screen anymore. I tried using USB debugging to unlock the screen but all i got was
"
.\adb.exe shell rm /data /system /gesture.key
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
"
I also tried to reset the screen size but that didnt work either:
"
.\adb.exe shell wm size reset
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
"
I would really appreciate any help as I really need to at least get my files off of the phone (i have no backups)
Thanks