WNC_ADB unauthorized MacOS

ernastovich's picture


I have the att  LTE starter kit, and I'm not able to get it up and running. i've hit problem after problem, and there's simply insufficient information out there to adequately troubleshoot. 

The internal program that is suppoused to launch some code to connect to the network and transmit a packet of information appears to be not working. The user guide explains that the internal address which the devices uses to identify itself with the network is the probable issue, this requires us to connect the device to a computer to correct the issue. 

Enter ADB. I'm working on a MacOS (latest software level). I have followed (I think?) the installation procedure for adb, and I am at the dreaded part where adb is supposed to find the device attached. 

I keep running into trouble with the adbkey.pub file. I create the file making usre that .pub is its extension, make sure the internals say wnc000000, but as soon as I run adb, every single time, the file contents are modified, goes from 9 bytes to 717 or 719 bytes. The proposed solution in the user guide, is to inidividually start the server and then perform the adv devices command. I have tried this, and the situation does not change. The ultimate solution to this problem in the user guide is to repeat this process ad nauseam. I've tried it at least 40 times now, and I don't think its going to change its mind any time soon. 

One trick i tried to use is to lock the adbkey.pub file so that the software cannot write to it. This worked as far keeping the contents of the file unchanged, wnc000000 is still there, and its still only 9 bytes, but the system still returns WNC_ADB unauthrozied. I have tried to do this both as user, and as sudo, every combination possible. 

Can anyone please shed light as to what the software is actually trying to do so that maybe I can troubleshoot it a little bit more effectively? I don't understand what this whole process is for, and why the software keeps writing to a file when the user guide says its not supposed to.

It'd be even better if one of you has the solution to this annoying issue.

Thanks for your time, looking forward to hearing from you all! 

TONYWYANT's picture

I have exact same problem on my mac. I  also tried it on a Windows machine with exactly the same results. My device comes up, but cannot connect(blinking yellow LED). Since I can't access the device via adb to check APN, etc, it is useless.

sumoxo's picture

Thanks for the reply. I also think that they are useless now and won't be of any help. 

However, if anyone has any solution to it, feel free to update this thread.

TONYWYANT's picture

After getting no help on this issue from AT&T and Avnet, I looked further into ADB and discovered changes that may have caused the described method of installing adbkey.pub from working. Long story short: use an older version of adb, such as the one found here:


And one should be able to connect to the device, update APN, etc...

Chaddychaddy's picture

I'd love to hear their response regarding this.

Sam | https://www.fairfieldtrees.com/

justinlem08's picture

That sure was understandable. We can always have new beginnings. roof replacement solon

crystalbr8wn's picture

I'm happy to find this post. Tree Service Worcester MA

Jade38's picture

Thanks for posting this information. I find it interesting and informative. I can't wait to read lots of your posts. www.bostonmoldremovalservices.com/


chuck's picture

This is exactly what I'm looking for! Thanks for sharing.



Ryan for Commercial Roofing