FORUMS
Remove All Ads from XDA

adb device unauthorized

1,485 posts
Thanks Meter: 642
 
By ze7zez, Senior Member on 16th March 2017, 04:40 PM
Post Reply Email Thread
I noticed a certain feature of a ROM, so I conducted a test on other ROM.
If you execute the command you see on the screen something like this,

Code:
P:\>adb devices
List of devices attached
XXXXXXXXXXXXXXXX        unauthorized

P:\>adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
you might like to know that ROMs have a similar property.
Code:
aokp_mako_nougat_nightly_2017-03-15_ota.zip       - NOF27B
aoscp_mako-3.6-20170225-official.zip              - NMF26X
CARBON-CR-5.1-MOO-WEEKLY-mako-20170107-1159.zip   - NMF26V
Cosmic-OS_mako_7.1.1_20170212_1.3-OFFICIAL.zip    - NMF26V
crDroidAndroid-7.1.1-20170307-mako-v2.3.zip       - NOF26W
lineage-14.1-20170309-nightly-mako-signed.zip     - NOF27B
lineage-14.1-20170312-NIGHTLY-MLQ-mako.zip        - NOF27B
MK71.1-mako-201703121057-NIGHTLY.zip              - NOF27B
omni-7.1.1-20170228-mako-HOMEMADE.zip             - N4F26O
RR-N-v5.8.2-20170227-mako-Unofficial.zip          - NOF26W
__________________________________________________ _________________

Below I present a ROM that behave differently, but for me it's good.
Code:
P:\>adb devices
List of devices attached
XXXXXXXXXXXXXXXX        device

P:\>adb shell
mako:/ #
Code:
aicp_mako_n-12.1-NIGHTLY-20170312.zip             - NOF27B
aosp_mako-ota-eng_V10.zip                         - NMF26Q
DU_mako_7.1.1_20170310-1645.v11.2-UNOFFICIAL.zip  - N6F26U
liquid_mako-20170226-1613-nougat.zip              - NOF26W
NeXus4ever_mako-7.1-r02-20161227.zip              - NMF26Q
Nitrogen-OS-mako-20170307.zip                     - N6F26U
purenexus_mako-7.1.1-20170217-HOMEMADE.zip        - NOF26W
saosp_mako-ota-3-8-17.zip                         - N6F26U
Slim-mako-7.1.1.build.0.14-BETA-20170303-0414.zip - NOF26W
ua_mako-7.1.1-20170201.zip                        - N6F26Q
XenonHD-170215-Official-mako.zip                  - NMF26V
__________________________________________________ _________________
I made a test in Windows 8.1 64-bit, USB cable was still connected.
Only a clean installation and activation of debug USB, if it was not set by default in the ROM.
 
 
16th March 2017, 06:04 PM |#2  
TheSt33v's Avatar
Senior Member
Flag The Stupid Country
Thanks Meter: 1,114
 
More
All you have to do is accept the authorization prompt on your phone, and then the "unauthorized" will appear as "device."
17th March 2017, 01:26 PM |#3  
OP Senior Member
Flag Kraków
Thanks Meter: 642
 
More
Quote:
Originally Posted by TheSt33v

All you have to do is accept the authorization prompt on your phone, and then the "unauthorized" will appear as "device."

I am glad that there is someone with a Windows 8.1 64-bit!
So I would recommend your mind what has been written on this page 3.


---- edit ----
It seems that this feature has long existed.

Can't connect Nexus 4 to adb: unauthorized.

---- edit 2 - solved ----
I still do not know why one ROM works differently from another.
I have found a solution that points to the cause on the windows side that produces this effect.

Cant connect to Android phone using adb (adb device unauthorized)

I had something like this:
Code:
[HKEY_CURRENT_USER\Environment]
"ANDROID_SDK_HOME"="C:\Android"
but there was no c:\android directory on my hard drive.

After removing the environment variable and restarting the system, there is no longer "unauthorized" on some ROMs.
Post Reply Subscribe to Thread

Tags
adb, rom

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes