search

MasterDevX / Termux-ADB

Install ADB & FastBoot Tools in Termux!
1.68k stars 276 forks source link

$ADB_VENDOR_KEYS is not set #13

Open CODeRUS opened 4 years ago

CODeRUS commented 4 years ago 
$ adb shell
error: 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.
CODeRUS commented 4 years ago

device is authorized for sure on the popup dialog

MasterDevX commented 4 years ago

Try restarting adb server (adb kill-server; adb start-server). If it won't work, try to revoke ADB authentications in developer settings. And if this also will give no result, try reinstalling ADB.

piagzaa24 commented 4 years ago 
$ adb shell
error: 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.
sunshinewithmoonlight commented 4 years ago

This problem is not fatal to connecting devices. But if you want to eliminate the error, please enter the following in ~/.bashrc : 

alias adb='ADB_VENDOR_KEYS=/data/data/com.termux/files/home/adbfiles/adbkey adb'

In addition, you should execute adb devices and adb connect <ip>:<port> before executing adb shell. You should not delete files under ~/adbkey.

By the way, I use adb to connect my phone to itself: 

su -c 'setprop service.adb.tcp.port 5555' && su -c 'stop adbd' && su -c 'start adbd'
adb devices
adb connect 127.0.0.1:5555
diabl0w commented 4 years ago

This problem is not fatal to connecting devices. But if you want to eliminate the error, please enter the following in ~/.bashrc :

alias adb='ADB_VENDOR_KEYS=/data/data/com.termux/files/home/adbfiles/adbkey adb'

In addition, you should execute adb devices and adb connect <ip>:<port> before executing adb shell. You should not delete files under ~/adbkey.

By the way, I use adb to connect my phone to itself:

su -c 'setprop service.adb.tcp.port 5555' && su -c 'stop adbd' && su -c 'start adbd'
adb devices
adb connect 127.0.0.1:5555

I am having a similar issue... the difference is that I can still connect as long as I confirm the "Authorize Debugging" dialog box that comes up. The problem is that it doesn't remember the device after authorizing it. I have to confirm the dialog box every time, unlike on my computer. The strange part is that the adbkey.pub key is correctly located in the /data/misc/adb/adb_keys file. In fact the key is duplicated in the adb_keys file dozens of times because of all the times I keep confirming the dialog box. Why does it keep asking me to authorize?

sunshinewithmoonlight commented 4 years ago

I am having a similar issue... the difference is that I can still connect as long as I confirm the "Authorize Debugging" dialog box that comes up. The problem is that it doesn't remember the device after authorizing it. I have to confirm the dialog box every time, unlike on my computer. The strange part is that the adbkey.pub key is correctly located in the /data/misc/adb/adb_keys file. In fact the key is duplicated in the adb_keys file dozens of times because of all the times I keep confirming the dialog box. Why does it keep asking me to authorize?

I don't know why. It's the same with me.

lavaed commented 4 years ago

I am having a similar issue... the difference is that I can still connect as long as I confirm the "Authorize Debugging" dialog box that comes up. The problem is that it doesn't remember the device after authorizing it. I have to confirm the dialog box every time, unlike on my computer. The strange part is that the adbkey.pub key is correctly located in the /data/misc/adb/adb_keys file. In fact the key is duplicated in the adb_keys file dozens of times because of all the times I keep confirming the dialog box. Why does it keep asking me to authorize?

I don't know why. It's the same with me.

it's the same with me.

seba-plpl commented 1 year ago

I am having a similar issue... the difference is that I can still connect as long as I confirm the "Authorize Debugging" dialog box that comes up. The problem is that it doesn't remember the device after authorizing it. I have to confirm the dialog box every time, unlike on my computer. The strange part is that the adbkey.pub key is correctly located in the /data/misc/adb/adb_keys file. In fact the key is duplicated in the adb_keys file dozens of times because of all the times I keep confirming the dialog box. Why does it keep asking me to authorize?

I don't know why. It's the same with me.

Hi All, i'm facing the same problem. Every time i kill and start adb server or reboot a device, adb devices command or adb connect is asking me to authorize computer. Because of that, i cannot automatize my tests :-( Did anyone find a solution for that?