How to solve ADB device unauthorized in Android ADB host device

Question

When I m using a rooted Android device as ADB host to send adb command  adb devices  to Samsung S4  I received device unauthorized error message  However when I tried adb to Samsung Galaxy Nexus  it is working fine  Can anyone advise how to solve my Samsung S4 problem                                               adb devices List of devices attached 4d00f9169907301b        unauthorized                                             Thanks in advance   Edit  Found that this problem only happened to Android 4 2 2 and above  The following link explained that Google has implemented some new security features for using adb   http   nelenkov blogspot com 2013 02 secure-usb-debugging-in-android-422 html  Appreciate if anyone can help on this

User · Answer

I had to check the box for the debugger on the phone  always allow on this phone    I then did a adb devices and then entered the adb command to clear the adds   It worked fine   Before that  it did not recognize the pm and other commands

User · Answer

If anyone has similar issue of having a phone with a cracked screen and has a need to access adb    Root your phone  mine was already rooted  so I was blessed at least with that     If you forgot to enable developers mode and your adb isn t running  then do the following    Reboot your phone into recovery  Connect the phone with a cable  Open terminal  If you type adb devices you should see the device in the list  If so  type   adb shell mount  system abd shell  echo  persist service adb enable 1   gt  gt  default prop  echo  persist service debuggable 1   gt  gt  default prop echo  persist sys usb config mtp adb   gt  gt  default prop echo  persist service adb enable 1   gt  gt   system build prop  echo  persist service debuggable 1   gt  gt   system build prop echo  persist sys usb config mtp adb   gt  gt   system build prop    Now if you are going to reboot into your phone android will tell you  oh your adb is working but please tap on this OK button  so we can trust your PC   And obviously if we can t tap on the phone stay in the recovery mode and do the following  assuming you are not in the adb shell mode  if so first type exit    cd    android adb push adbkey pub  data misc adb adb keys    Hurray  it all should be hunky-dory now  Just reboot the phone and you should be able to access adb when the phone is running   adb shell reboot   P S  Was using OS X and Moto X Style that s with the cracked screen

User · Answer

Experience With  ASUS ZENFONE  If at all you have faced Missing Driver for Asus Zenfones  Follow This Link  http   donandroid com how-to-install-adb-interface-drivers-windows-7-xp-vista-623   I tried with   1  Killing and starting adb server at adb cmd   2  Switching Usb Debugging on and Off and      This is What WORKED with me   Step 1 Remove Connection with Device and Close Eclipse  Step 2 Navigate to C  Users User name  android   Step 3 You Will Find adb key  Step 4 Just delete it   Step 5 Connect again and System will ask you Again   Step 6 Ask Device to remember RSA Key when it Prompts  I think its done   If you Face The Same Problem after couple of days  just disable and enable USB debugging

User · Answer

You need to allow Allow USB debugging when the popup shows up when you first connect to the computer

User · Answer

Have you tried  adb kill-server adb shell   Sometimes adb gets stuck and first killing adb server and then starting some command forces authorization window to pop-up   Also please check adb client version on your phone  THis feature is supported from adb 1 0 31 as far as I remember

User · Answer

I found one solution with Nexus 5  and TWRP installed  Basically format was the only solution I found and I tried all solutions listed here before  ADB Android Device Unauthorized  Ask Google to make backup of your apps  Save all important files you may have on your phone  Please note that I decline all liability in case of failure as what I did was quite risky but worked in my case   Enable USB debugging in developer option  not sure if it helped as device was unauthorized but still      Make sure your phone is connected to computer and you can access storage  Download google img of your nexus  https   developers google com android nexus images unrar your files and places them in a new folder on your computer  name it factory  any name will do    wipe ALL datas    you will have 0 file in your android accessed from computer   Then reboot into BOOTLOADER mode    you will have the message  you have no OS installed are you sure you want to reboot     Then execute  double click  the  bat file inside the  factory  folder   You will see command line detailed installation of the OS  Of course avoid disconnecting cable during this phase     Phone will take about 5mn to initialize

User · Answer

For me  the emulator could not have Google Play Services enabled  It could have Google APIs or be x86 or x64 but not google play store

User · Answer

Delete the folder  android from C  users  lt user name gt   android  It solved the issue for me

User · Answer

You must be prompted in your s4 screen to authorize that computer  You can tell it to remember it  This is for security reasons  occurring in Android 4 4

User · Answer

Check and uncheck the USB Debugging option in the device  If that doesn t work unplug and plug in the USB a couple of times   At some point  the device should show a message box to ask you to authorize the computer  Click yes and then the device will be authorized

User · Answer

Get the public key from the client phone  adb host   cat  data  android adbkey pub copy the above public key to the target phone s  data misc adb adb keys location   you may need to stop the adb daemon first with stop adbd   cat  data misc adb adb keys   verify both cat outputs match   try restarting adb daemon on target start adbd or just reboot them   If you are having problems reading or writing to ADB KEYS in above steps  try setting environment variable ADB KEYS PATH with a temporary path  eg   data local tmp   Refer to that link it goes into more details       On the host  the user public private key pair is automatically generated      if it does not exist  when the adb daemon starts and is stored in      HOME  android adb key  pub  or in  ANDROID SDK HOME on windows  If needed      the ADB KEYS PATH env variable may be set to a  -separated    under     Windows  list of private keys  e g  company-wide or vendor keys       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

User · Answer

For unknown reasons  I only had    android adbkey  but not    android adbkey pub   I guess that adb was unable to push the public key to the device  and thus the device could never show the authorization dialog   After killing the adb server  removing the adbkey file and starting adb again  the authorization dialog popped up on the phone

User · Answer

Try this steps    unplug device adb kill-server adb start-server plug device   You need to allow Allow USB debugging in your device when popup

[android] How to solve ADB device unauthorized in Android ADB host device?

Examples related to android

Examples related to shell

Examples related to adb