So with my Verizon G3, when I enter ADB sideload in TWRP it disconnects the device from the shell.. If I cancel the sideload and do a 'adb devices' command it will show it connected, but as soon as I enter sideload, run the command again and there's nothing..
Anyone have a similar experience or solution? This is very annoying
Hi!
I have RN2 with MIUI 16.6.7.0 with root access.
ADB v1.0.32
Win 8.1
If I run "adb devices" when phone is running system, I get response "s/n device" as I should. But when I boot phone to recovery (MI-Recovery 2.0.1) I get "s/n unauthorized".
I have tried rebooting PC and phone, disabling and enabling USB debugging, deleting adbkey and adbkey.pub on PC (only instance was in users/user/.android/), revoking USB debugging authorizations, changing USB ports. Nothing.
The last thing I did:
1. reboot phone to system.
2. developer options > turn developer options on/off > turn debugging on/off <> Revoke USB Debugging Authorization
3. reconnect phone to PC
4. was asked: RSA key fingerprint + always allow from this computer > OK
5. run "adb devices" gives "s/n device"
6. disconnect phone
7. power off phone
8. phone to recovery
9. reconnect phone
10. run "adb devices" gives "s/n unautorized"
11. disconnect phone from USB
12. run "adb kill-server"
13. run "adb start-server"
14. reconnect phone
15. run "adb devices" gives "s/n unautorized"
I guess something is wrong with recovery mode on the device. Any ideas?
Thank you
MK
+ run "adb shell" gives " error: device unauthorized. 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."
+ from hxxps://android.googlesource.com/platform/system/core/+/d5fcafaf41f8ec90986c813f75ec78402096af2d
"On the device, vendors public keys are installed at build time in /adb_keys. User-installed keys are stored in /data/misc/adb/adb_keys."
On my device user-installed keys are stored in /data/misc/adb/adb_keys. The only other instance of adb_keys is /bin/adb_keys. If it has any relevance.
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Namaless said:
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
Click to expand...
Click to collapse
Hi!
Thanks a million for your reply. :good:
I did all that already in steps 2, 4 and 5 and it worked. My problem is adb in stock recovery mode.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Click to expand...
Click to collapse
Damn I have much to learn (hundreds of pages in a few days and I still dont know anything . So stock recovery doesn't come with ADB access and I am trying to do something that can not be done? ClockworkMod recovery for example should have ADB support if I understand correctly?
I also have that proble my device not connected to phone what I do tell me..
Jay's said:
I also have that proble my device not connected to phone what I do tell me..
Click to expand...
Click to collapse
If problem is PC <> phone then install drivers for your phone on PC.
Or describe your problem better.
Poslano z mojega Redmi Note 2 z uporabo Tapatalk
Hello. I'm currently experiencing a problem with adb. My phone is recognized and the number shows up on adb devices command but it shows as offline. The set won't take any adb commands. Is this normal? I'm trying to use minimal adb on Windows 10.
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'm trying to learn to use adb/fastboot and here are a few random things I ran across I'd like to ask to understand better how it works.
Does adb work only when the phone's on and usb debugging also on or do some commands also work in other modes? Example: phone's off (Honor 6) and "adb devices" doesn't recognize it but all "adb reboot" commands work no problem, why?
Could some adb commands be blocked by the manufacturer? On another device (Prestigio), "adb reboot recovery" works but "adb reboot bootloader" doesn't do anything. Is there a way to safely stopping a running command?
Example: in the recovery mode, I accidentally started the adb sideload and the phone prompted me to enter the full path to the sideloaded file (in the PC terminal); trying to enter a non-existing path didn't do anything, the sideload screen on the phone was still there; holding the power button didn't help; removing the battery would probably do the trick but it's not removable so is there a safe way to stop the command? Maybe adb kill-server?