I have searched extensively to no end. When I ./adb devices in terminal, it lists my phone but says 'unauthorized.'
I do not get a prompt on my phone to authorize its connection to osx.
I have rest phone to factory spec. Still nothing.
Thoughts?
lablunk said:
I have searched extensively to no end. When I ./adb devices in terminal, it lists my phone but says 'unauthorized.'
I do not get a prompt on my phone to authorize its connection to osx.
I have rest phone to factory spec. Still nothing.
Thoughts?
Click to expand...
Click to collapse
I had this issue on a stock rom with ADB in Windows and in Linux. This apparently is a known "issue" with the stock rom when the USB mode is set to MTP.
The "fix" is to make sure you are in Network mode (either Internet or Modem is fine). You might have to disconnect and re-connect the USB cable a couple times (and re-select the Nework mode) before it will actually connect with ADB. If it pops up with the ADB Verify Server Fingerprint window on the phone, you have sucessfully made an ADB connection.
Hi all,
I recently bought a OPT and wanted to root it, but I can't get the RSA Fingerprint dialog to appear.
What I've done:
Installed Android SDK and platform tools and all that stuff according to the guide in the general section
Installed Koush's universal drivers and also specifically installed the Oneplus drivers
Rebooted rebooted rebooted both my computer and phone multiple times
Revoked USB authorization multiple times (according to some this works, but not for me)
Tried both MTP and PTP
Switched off and on developer options and USB Debugging
Factory reset my phone
When I start a command prompt in the platform tools directory and execute "adb version", " Andoid Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android" pops up, so I think my ADB is working properly. But when I execute "ADB devices" the ADB server starts up and then nothing is listed under connected devices.
I'm using Windows 10. Any help would be greatly appreciated. Thanks!
This might work
This didn't work for me, but give it a try.
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332
I have carefully followed the instructions in [GUIDE] Unlock/Root/Flash for Nexus 6P.
However, when I type "adb devices" at the command prompt, I just get "List of devices atttached" without a serial number. When I try "fastboot devices" when in bootloader, the cursor comes back without any message. What should I try next. Thanks in advance.
PrevailNow said:
I have carefully followed the instructions in [GUIDE] Unlock/Root/Flash for Nexus 6P.
However, when I type "adb devices" at the command prompt, I just get "List of devices atttached" without a serial number. When I try "fastboot devices" when in bootloader, the cursor comes back without any message. What should I try next. Thanks in advance.
Click to expand...
Click to collapse
Did you add the current version of platform-tools to your environment variables path? Did you also install the Google USB drivers from the sdk? Also on the phone you have USB debugging enabled and then when you plug it into pc it will ask for authorization on your phone.
Yes, I am running adb and fastboot from within the platform-tools folder. USB debugging is enabled as well as OEM unlocking in developer options. I switch from USB charging to file transfer (MTP) when plugging in. The USB drivers seem to be working fine, since I have no trouble transferring files, etc. Just don't know what else to try to get adb working.
I can't find the video that helped me but this is what I remember.
Go to device manager, locate the phone, tick the drivers tab, update drivers, browse, let me pick, have disk, and locate your drivers (I uswd the straight up Google drivers). At some point you have to choose from 3 ADB choices, it's the top one, Android ADB Interface. Good Luck, it worked for me.
BTW- for me fastboot found my phone but not ADB.
PrevailNow said:
Yes, I am running adb and fastboot from within the platform-tools folder. USB debugging is enabled as well as OEM unlocking in developer options. I switch from USB charging to file transfer (MTP) when plugging in. The USB drivers seem to be working fine, since I have no trouble transferring files, etc. Just don't know what else to try to get adb working.
Click to expand...
Click to collapse
Did your phone ask to authorize your PC when you plugged it in?
Gizmoe said:
Did your phone ask to authorize your PC when you plugged it in?
Click to expand...
Click to collapse
I get two notifications when plugging in the 6P. One says, "USB debugging connected". The other says, "USB for charging. Touch for more options".
PrevailNow said:
I get two notifications when plugging in the 6P. One says, "USB debugging connected". The other says, "USB for charging. Touch for more options".
Click to expand...
Click to collapse
OK. Unplug your phone. Go to dev options. Turn off USB debugging. Also revoke USB debugging authorizations. Then re-enable USB debugging and plug phone in. It should now ask if you want to allow USB debugging for your PC on your phone screen. Check to always allow device.
Gizmoe said:
OK. Unplug your phone. Go to dev options. Turn off USB debugging. Also revoke USB debugging authorizations. Then re-enable USB debugging and plug phone in. It should now ask if you want to allow USB debugging for your PC on your phone screen. Check to always allow device.
Click to expand...
Click to collapse
What he said, this is key to get ADB working.
Gizmoe said:
OK. Unplug your phone. Go to dev options. Turn off USB debugging. Also revoke USB debugging authorizations. Then re-enable USB debugging and plug phone in. It should now ask if you want to allow USB debugging for your PC on your phone screen. Check to always allow device.
Click to expand...
Click to collapse
I did as you suggest, but I continue to get the same two notifications, just as before.
The first says "USB debugging enabled. Touch to disable USB debugging.", without any request to authorize my specific PC.
PrevailNow said:
I did as you suggest, but I continue to get the same two notifications, just as before.
The first says "USB debugging enabled. Touch to disable USB debugging.", without any request to authorize my specific PC.
Click to expand...
Click to collapse
It's a driver or port issue then on your PC. Are you trying in a USB 2.0 or 3.0 port? I got mine in a 3.0. In device manager it should say under Android devices tree " Android Composite ADB Interface". Try switching ports or if you see it listed wrong in device manager manually update the drivers.
---------- Post added at 06:21 PM ---------- Previous post was at 06:16 PM ----------
It is important though that you get the toast notification about allowing USB debugging and it will show you an rsa fingerprint.
You said you had a second notification that said "USB for charging". Have you tapped that notification and changed it to file transfer?
jiggyb21 said:
You said you had a second notification that said "USB for charging". Have you tapped that notification and changed it to file transfer?
Click to expand...
Click to collapse
Adb works in charging mode. They are not even getting the authorization toast to allow USB debugging on PC.
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
@PrevailNow If you have any other phone software installed try disabling or uninstalling it. Other phone manufacturers tools can cause problems with adb as well.
Gizmoe said:
@PrevailNow If you have any other phone software installed try disabling or uninstalling it. Other phone manufacturers tools can cause problems with adb as well.
Click to expand...
Click to collapse
I think you are right about this. I appear to be making some progress. After removing a previous installation of Sammy Kies, I got the PC authorization request for debugging, and the adb interface driver shows up now, as expected, in the device manager.
I am also able to get "adb" to return my serial number; but "fastboot" doesn't detect any attached devices. I have deleted and reinstalled all 4 SDK packages, but "fastboot" still doesn't detect my 6P. I just don't know what else to try, so any ideas would be appreciated. I thank those who have already responded with helpful information.
You're using old platform tools, I guarantee it...
Sent from my Nexus 6P using Tapatalk
Phone is rooted, TWRP installed, (almost) everything is OK.
What is not OK is that now I cannt ADB connect. The "Allow USB debugging" window with the RSA key does not open at all.
Another thing I've noted - the "Revoke USB debugging authorizations" option in the Developer options - does not exist.
Any ideas as to how to solve this ?
I'm using linux (Arch, 64 bit). Another phone (an older, stock Moto G2) connect with ADB without any problem - so this is not a problem on the computer side, nor a USB cable problem.
Thanks.
Ben
Solved (almost).
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
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!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
ben-moto said:
After more googling I've found a solution on stackoverflow (as a new user I cannt insert a link) :
Code:
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!
Now the G5+ is recognized as a "device" with adb.
It's a partial solution because the "Revoke USB debugging authorizations" option is still missing.
Hope this helps future generations
Click to expand...
Click to collapse
+1 to this solution. I have a very similar problem on my HTC One M8. No prompt, also missing the "Revoke USB debugging authorizations" option.
Between this thread, a few others, and that same stackoverflow answer, I was able to come up with a couple of solutions:
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
I'm experiencing this now, except I still have my "revoke USB auth" option under Dev Options.
I'll try the adb push method now...
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?