WNC_ADB unauthorized after copying adbkey.pub to ~/.android

Solved
llin's picture
llin
Junior(0)

Hardware: AES-ATT-M18Q2FG-SK-G

OS: Ubuntu 16.04 client on Windows 10 host. 

SIM : registered on AT&T IoT portal

~$ lsusb
Bus 001 Device 003: ID 1435:3182 Wistron NeWeb 

~$ sudo adb devices

List of devices attached

WNC_ADB unauthorized

 

~$ ls ~/.android/
adbkey  adbkey.pub

 

I have restarted virtual machine and power cycled my M18W2FG board.  Nothing changed. 

 

PeterF's picture
PeterF
Moderator(16)

You need to kill the adb server after installing the adb security key on your Ubuntu Linux host
ie.the sequence of commands is as follows:
cp adbkey.pub ~/.android/
adb kill-server
sudo adb devices

 

PS: Detail of this procedure is shown at ~5 minutes into training video #1
Under the "Trainings" tab of http://cloudconnectkits.org/product/global-lte-starter-kit
ie.
https://vimeo.com/247404116

llin's picture
llin
Junior(0)

Thank you, Peter. I have done so.  Regardless, I got a fresh installed Ubuntu 16.04 PC.  Same thing happens. 

$ ls ~/.android/

adbkey  adbkey.pub

$ adb kill-server

$ sudo adb devices

List of devices attached

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

WNC_ADB    unauthorized

 

PeterF's picture
PeterF
Moderator(16)

Please examine the default adbkey.pub that is in your ~/.android folder/

 

It's content should be wnc000000   
You can change this key to something more secure later

 

Add read permission to this file if necessary:
chmod +r adbkey.pub
 
chmod

 

 

jflynn129's picture
jflynn129
Moderator(4)

 

Try killing the adb daemon and restarting it. 

sudo adb kill-server

Then

sudo adb devices

That will restart the daemon with admin privilege and provided the key is present it will find it 

 

jflynn129's picture
jflynn129
Moderator(4)

 

Try killing the adb daemon and restarting it. 

sudo adb kill-server

Then

sudo adb devices

That will restart the daemon with admin privilege and provided the key is present it will find it 

 

jflynn129's picture
jflynn129
Moderator(4)

 

Try killing the adb daemon and restarting it. 

sudo adb kill-server

Then

sudo adb devices

That will restart the daemon with admin privilege and provided the key is present it will find it 

 

jflynn129's picture
jflynn129
Moderator(4)

 

Try killing the adb daemon and restarting it. 

sudo adb kill-server

Then

sudo adb devices

That will restart the daemon with admin privilege and provided the key is present it will find it 

 

jflynn129's picture
jflynn129
Moderator(4)

 

Try killing the adb daemon and restarting it. 

sudo adb kill-server

Then

sudo adb devices

That will restart the daemon with admin privilege and provided the key is present it will find it 

 

mikes's picture
mikes
Junior(0)

Its pretty awesome and I love this. https://liteblue.guru/