Database Users

ADB does not prompt to accept any USB debugging authorization after root

Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!

__adam_ said:
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
Click to expand...
Click to collapse
I finally solved this problem.... I don't think it was particular to the Galaxy Tab A.
In order to get adb working again I had to put the device into recovery mode (power down, then power up while holding power, up-volume, home button). I then went to the terminal application of the Team Win Recovery. In terminal I issues "stop adbd" then "start adbd". At this point the device now shows up on the local host PC when I run "adb devices" (it shows up as "recovery" rather than unauthorized). I can adb root/shell to the device now. This is really all I need to do. I expect this will solve my problem in non-recovery mode as well. Or, at this point I can push my PC pub key to the device and it should be fine.

Nexus 7 2012 bricked, adb/fastboot connection ok but unauthorized. Can You help?

Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?

Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.

Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.

Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.

Following
I have the same error and like to follow

Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.

thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.

No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.

Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.

Trying to sideload apps to my LG Smartwatch Sport through my Mi mix...please help!

Hi All,
I have been trying for hours (more than a week actually all in all) to sideload apps to my Lg Smart Watch Sport.
I have found more than one thread that speaks to how to achieve this and I have followed to a T as far as I know.
I have ADB and Fastboot installed and when I enter adb devices it shows my phone is connected.
Each time I follow the script after the adb connect localhost:4444 script I get the message 'no connection could be made because the target machine actively refused it (10061)'
I have debugging and bluetooth debugging on my Sport and phone has debugging as well.
I have tried the Android Wear APK Tools app as well and it just say error, cannot install.
I am using a MI Mix in case it matters.
Im not sure if the problem is my computer (Windows 10) or the Mi Mix but I have hit a dead end.
Anyone out there that can help I would sure appreciate it!

Best source is this: https://developer.android.com/training/wearables/apps/debugging.html
Edit: on the first connection with "adb devices" you should get a dialogue on your watch asking for authorization

ranf said:
Best source is this: https://developer.android.com/training/wearables/apps/debugging.html
Edit: on the first connection with "adb devices" you should get a dialogue on your watch asking for authorization
Click to expand...
Click to collapse
I have been trying for days to get this to work and that tutorial got me up and running.....I cant thank you enough.

make sure you open Command Prompt with Admin privileges.

ADB device - unauthorized

Hi there,
I've got a problem; my device is not seen properly by latest Minimal ADB (unauthorized), I've tried many solutions such: reconnecting, re-enabling usb debbuging, restarting adb servers, deleting adbkey file from /.android. Is there something else I can do? Thanks in advance,
Paul

zaaaki said:
Hi there,
I've got a problem; my device is not seen properly by latest Minimal ADB (unauthorized), I've tried many solutions such: reconnecting, re-enabling usb debbuging, restarting adb servers, deleting adbkey file from /.android. Is there something else I can do? Thanks in advance,
Paul
Click to expand...
Click to collapse
You are using linux? If yes, try sudo.....
If not, do not restart device in fastboot and plug it in pc. Plug it when booted in system and type adb reboot bootloader. Be sure to have adb turned on in developer options.

After doing what u said; I've got:
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."
I've already done kill/start multiple times. What's more, I have no RSA popup whatsoever.
Paul

zaaaki said:
After doing what u said; I've got:
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."
I've already done kill/start multiple times. What's more, I have no RSA popup whatsoever.
Paul
Click to expand...
Click to collapse
Linux ???????

I am using Windows 10 x64,and I have been using it since I got P8 Lite. And I have done copule of things with my device like instaling twrp; but for some reason I cannot do that this time.
Paul

zaaaki said:
I am using Windows 10 x64,and I have been using it since I got P8 Lite. And I have done copule of things with my device like instaling twrp; but for some reason I cannot do that this time.
Paul
Click to expand...
Click to collapse
Go to developers options and click on revoke usb debugging authorizations and conform the prompt.
No reconnect the device to PC and check for RSA prompt in phone and accept it.

I haven't got revoke option, I believe it is due to custom kernel I installed, so the question is if I install custom ROM, the kernel is going to be reinstalled with ROMs one, what should I do tho?

zaaaki said:
Hi there,
I've got a problem; my device is not seen properly by latest Minimal ADB (unauthorized), I've tried many solutions such: reconnecting, re-enabling usb debbuging, restarting adb servers, deleting adbkey file from /.android. Is there something else I can do? Thanks in advance,
Paul
Click to expand...
Click to collapse
This should fix it.
1. Go to the /.android folder and take copy of "adbkey.pub" file.
2. Rename copy as "adbkeys" Without any file extension.
3. Move "adbkeys" into your phone /data/misc/adb
4. Not sure if necessary but set permissions to 640 (-rw-r-----)
5. You might need to restart adb server "adb kill-server"
Now when you try it should work as expected.

It didn't work.

Reinstall phone driver. It may work

Did it and nothing.

zaaaki said:
Did it and nothing.
Click to expand...
Click to collapse
Factory reset your phone it will then prompt for RSA Key.

Did factory reset, but it didn't help, I'm on custom emui with elsa kernel.

What are you wanting to do with ADB?
What is your end goal?
Is there another way of doing it?
Another stupid question have you tried a different cable as I have had the same issue it was the cable

I want to try custom roms, and flash new TWRP, and what if I flash new rom then I'll want to go back, but can't coz I cannot connect to adb.
I was able to make it work; I restored backup.

I mean, fastboot is the one you need in order to flash twrp. Does it not recognise your phone if you plug it in while in fastboot mode?

Unable to adb

Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?

Did you get permissions on your phone when popup appears?

No. The phone doesn't pop up the permission question. But I don't know why.

Don't know but as long as you don't give permission you can't sideload

Euclid's Brother said:
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Click to expand...
Click to collapse
Try the usb driver and SDK platform tools directly from Essential website:
https://www.essential.com/developer/current-builds

I am using the drivers from Essential website. However, I was using the lastest Unified Android Toolkit for the adb command. Looks like it may be outdated, as the adb.exe and it's dll's in the link from Essential website is newer. I will try the platform tools from there and see if there is a difference.
Thanks!

Is USB debugging enabled in Developer settings?
Are you in Fastboot? Did you try "fastboot devices"?

ADB devices returns your device is offline?