Annoyingly, I can't for the life of me get adb on my laptop to list my S7 Edge as an authorised device, rather it lists it as unauthorized. I'm running Superman 1.8.1.
I'm not a noob at this type of thing and I've tried all the normal solutions. Including:-
Deleting the keys in /users/user/.android/ in Windows 7 and issuing an adb kill-server and adb start-server.
In developer options I've looked for the Revoke usb debugging authorization, something every solution suggests, but the option isn't there. Perhaps it's removed by Samsung or it's a Marshamallow thing.
I've checked /data/misc/adb for any keys but, whilst the folder is there, it's empty.
Changed the connection type from MTP and back again to no avail.
Tried a different USB port.
Nothing results in a key prompt on the phone, so I can't currently use adb. Any suggestions would be welcome.
I am on stock rom unrooted and the revoke usb debugging is definitely there. Maybe it's rom related why the option is not there. Also have connected adb to my windows 7 without issue.
Sent from My Galaxy S7 Edge
Cheers. It must have something to do with the Superman rom then. Does anyone else on Superman have the same issue?
Related
nvm ive been an idiot,
AdbWinUsbApi.dll was not present, this makes sense as this would probably describe the USB interface...
And when phone is booted up, with usb debugging connected, adb devices doesnt show anything either, and the task manager is saying that the adb interface is connected...
Update #2:
My locked and unrooted nexus 7 is also not showing up, but the drivers are said to be installed and the device is said to be connected...? Im now wondering if this is a problem with my PC?
Try different usb ports, mainly the ones in the back of your pc. Sometimes the ones on the front cause issues. Also try other usb cables.
Also if your environment variables aren't set up correctly you'll need to CD to the directory in which adb and fastboot are located.
Hi, i've been using my nexus 4 for a long time but recently (probably since patch 4.4.2) I've had this problem where I don't get adb authentication prompt on my phone when using usb-debugging. I have Cyanogenmod latest stable version installed.
I'm using adb drivers that come with android sdk (also tried 4 others!), version of adb is recent (1.0.31) and I have verified that by typing adb version.
adb devices list my nexus 4 as unauthorized (reboot bootloader gives unauthorized too) cause the prompt doesn't appear as it should.
I've done some extensive searching and here are what I've tried (to summerize these, I've tried all solutions currently on the internet probably) - this list might be incomplete as I don't remember everything I did:
Uninstall all usb related drivers and reinstall the correct drivers again (multiple times, with reboots).
Disabling and reenabling usb-debugging. Unplug and plug phone in. restarting adb server... etc.
disabling MTP, even trying PTP and tethering (desperation).
trying to set usb secure to 0 (wasn't set to zero, any way for me to set it to zero?)
trying to manually copy keys from computer to android (very weird that this one didn't work, maybe I did something wrong?)
Edit: I think I figured out why setting secure to 0 didn't persist. Working on it, learning how to unpack bootimg.
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.
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.
Not sure If I missed it with searching or if anyone has made a post about this, sorry for repeating.
I just recently bought the Essential phone and for some reason had issues getting the USB debugging authorization to show up. Nothing seemed to fix it, tried numerous cables, usb ports, removed and reinstalled drivers, still nothing.
I realized that there is a file located in C:\Users\Current User Name(whatever the current user is)\.android called adb_usb.ini. It list device IDs of other android devices and for some reason my phone wasn't listed. After adding my device ID (the file just opens in notepad) and saving, I went back to terminal and sure enough my phone got the allow usb debugging rsa key prompt and my phone finally showed up when typing ADB devices.
The device ID is 0x2e17
Also, even though I downloaded the lasted platform tools from google, in order to issue commands in fastboot I need to type fastboot -i 0x2e17
So for example in order to unlock the bootloader I needed to type fastboot -i 0x2e17 flashing unlock. I modified Essentials flashall.sh file and added the device id to all commands in order to get DP4 installed.
Didn't work for me...however windows just gives me an error when i even connect my phone to the PC.
Update: switching usb-c cables DEFINITELY works.
Try another computer will sure fix this, or just install another system like windows 10 or Ubuntu something like that.
I was having problems when i connected my essential phone to the pc and nothing was showing up. After a lot of frustration i decided to plug my usb cable to a usb 2 port instead of a usb 3.0 and that made everything work.
So if you're having problems connecting to the pc try using a regular usb port and not a 3.0 port.