I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I am having the same issue. ADB will not work at all with this tablet
Same here
I have the same problem; enabling USB debugging in the Developer Options menu does not seem to have any effect. Closing the settings app and restarting it results in the option being switched "off" again.
This on an unrooted, locked stock device with EMUI version 5.0 / Android 7.0
Weird ....
shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I work around this by enabling usb debugging, going into another setting menu option, then back to developer options, disabling it, enabling it, adb kill-server, adb devices, trying different combinations and eventually it works.. It's a real pain but eventually it works. Once the computer is trusted I don't need to do this anymore.
Related
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
Thanks for this. It worked like a charm:good:
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
YOU ARE AWESOME. THANKS :good::good:
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
i was looking for the solution, i'll try this tonight for my n7. will it work the same way for N4 too?
adbanginwar said:
i was looking for the solution, i'll try this tonight for my n7. will it work the same way for N4 too?
Click to expand...
Click to collapse
You got a free thanks!
It should be the same exact solution for any Nexus.
annoyingduck said:
You got a free thanks!
It should be the same exact solution for any Nexus.
Click to expand...
Click to collapse
i'm very annoyed with windows 8... argh broke most of the things...
adbanginwar said:
i'm very annoyed with windows 8... argh broke most of the things...
Click to expand...
Click to collapse
Try (i know !) to not get frustrated...
The mapping is a bit different, you'll get it with some patience, and then you'll have a good lesson in windows 8!
annoyingduck said:
Try (i know !) to not get frustrated...
The mapping is a bit different, you'll get it with some patience, and then you'll have a good lesson in windows 8!
Click to expand...
Click to collapse
Your way did not work for me. by defaul ADB drivers will installed when plugged in and not ADB composite. i followed the method 4 provided by wugfresh nrt. it worked for me, i rooted n4 and then unlocked+rooted n7_2013.
EDIT: oh, and mine works on ADB composite, weird!!
A request to OP. @annoyingduck
Could you please bring the first post in-order? The information is so cluttered that its agonizing to read.
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
You're so full of ****. Giving creedence to this crap through ignorance. Shame on you.
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
badhat said:
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
Click to expand...
Click to collapse
I'm confused... What are you trying to do? I've never used that command...
acejavelin said:
I'm confused... What are you trying to do? I've never used that command...
Click to expand...
Click to collapse
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
badhat said:
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
Click to expand...
Click to collapse
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or not.
acejavelin said:
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or now.
Click to expand...
Click to collapse
OK, I tried using a different Android SDK (grabbed from https://dl.google.com/android/repository/platform-tools-latest-linux.zip) and now it's working. There must be something about the one my distribution packaged that is broken.
Code:
$ adb version
Android Debug Bridge version 1.0.39
Revision 8.0.0_r11
$ LD_LIBRARY_PATH=$PWD ./adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /home/badhat/Downloads/adb/platform-tools/adb
I have a OnePlus 5 and I'm trying to get ADB to work in my Mac OS high Sierra. I have tried multiple threads and I still cannot get it to work. Whenever I enter ./adb devices it doesn't show my device under the listed devices and was wondering if anyone can help me
You don't need the ./
Just type adb devices
Also make sure you have USB debugging enabled in developer options
rickysidhu_ said:
You don't need the ./
Just type adb devices
Also make sure you have USB debugging enabled in developer options
Click to expand...
Click to collapse
thank you but I had figured out what happened. I was getting an error code so I used these adb & fastboot files in this link and it worked. https://dl.google.com/android/repository/platform-tools_r26.0.1-darwin.zip. it supposedly has a fix some people were working on. now everything works fine
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?
Hi all,
so i have got android installed on my switch but cannot seem to get the usb to work at all for ADB and MTP.
the switch does not show anything when it is connected by usb and it does not appear in device manager or adb on the host machine.
i have enabled developer mode and debug over USB.
i have tried to connect to ADB via the network but this lead to the authentication failing
does anyone have any ideas of what could be the issue?
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Laurin Neff said:
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Click to expand...
Click to collapse
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Roy8765 said:
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Click to expand...
Click to collapse
Just flash magisk, it's what I did and now I have root.