ADB unauthorized, unable to get "Allow USB Debugging" popup - Android Q&A, Help & Troubleshooting

After flashing a new stock rom and fixing my soft brick I can't get ADB to work anymore. It lists my device correctly but it tells me it's unauthorized. The problem is that I'm just not getting a pop up "Allow USB debugging" to allow access on my phone.
Well.... this is a pretty common problem you might say and there are literally hunderds of threads covering this already and I've read probably all of them and nothing seems to work.
To list a few things which are definitly checked;
- Developer mode is enabled
- USB debugging is enabled
- Revoke USB debugging authorization checked, (the option isn't there because I haven't had a pop up).
- Deleted adbkey in the .android folder
- Tried both MTP and PTP (PTP was the one that used to work)
- Switched USB cables and USB ports
- Tried different USB drivers
- Used different versions of ADB, (1.0.36 used to work fine).
Stuff about my phone;
- LG G4 h815 rooted
- TWRP as recovery
- SuperSU
- xposed installed
I'm really running out of things to try and I've probably forgot to list a few things. Is there something I can do manually? Like copying the adbkey to my phone and place it in some directory?
Does anyone have a clue on how to fix this?

Related

[Q] Dodgy Windows USB connection

So, I've been fiddling with the USB drivers and I still can't get it working properly.
ADB and windows (through explorer) will constantly drop out randomly and reconnect automatically.
Most of the times I connect my device, it's detected but is not shown in 'my computer' screen (cannot access its storage).
Thus, I can't actually copy files to it (unless through wifi).
What files should I delete to start the driver installation again? I have forcefully disabled windows update and I just want the ADB terminal to work.
Possibly relevant details:
- Using temasek's CM10.2
- USB debugging is enabled
- I sometimes use UMS mode.
- Tried using several cables.
- You can assume it's a fresh windows installation.

problem connection Marshmallow ROMs with USB cable (USB-Debugging, MyPhoneExplorer)

So far I had no problems to connect Win7x64 (Motorola and ADB Drivers installed) with various KitKat and Lollipop ROMs trough MyPhoneExplorer 1.8.7.
Motorola Driver 2.0.2.0 from 2013-07-07
minimal_adb_fastboot_v1.3.1
I now tried these Marshmallow ROMs and was not able to connect one of them to MyPhoneExplorer:
cm-13.0-20160409-NIGHTLY-condor.zip
cyanpop_condor-mm_6.0.1-v6.3-NIGHTLY-20160411.zip
Temasek-V5.9-cm-13.0-20160405-UNOFFICIAL-condor.zip
The following should be ok (as it was when working with KitKat and Lollipop ROMs):
- 'Loading only' USB mode
- 'USB-Debugging' is activated in the ROM developer settings (in case unlocked by build tapping 7x, acoustic signal of recognition is played in Win7x64)
a) MyPhoneExplorer says 'connection [over USB] could not be established'.
b) The Windows Explorer does show the device (XT1022), but no index (folders and files).
So this seems strange. I tried to update the ADB Interface Drive with an original Google Driver as I found suggestions to do so. But no difference.
Has someone else observed this? Is it possible that the Motorola Drivers do not support Marshmallow? Is there a solution or a workaround? Thanks.
1)connect your phone to PC
2)click on charging only on phone(notification drawer) select mtp
3)Now you will able to see windows explorer.
piku 123 said:
2)click on charging only on phone(notification drawer) select mtp
3)Now you will able to see windows explorer.
Click to expand...
Click to collapse
Thanks, this solves b)
But I would really like to have a) working for MM; I will try a little longer but not sure if I find a solution.
Installation of MPE-Client_1.0.40_beta2 solved the problem; connection now with 'Loading only' USB mode and MTP possible. Thanks. Hope this helps also others.
There's a xposed module for this.
https://play.google.com/store/apps/details?id=rayyan.black.fem.ind.runner&hl=en

adb Unauthorized except in 5.1.1

I currently have 5.1.1 installed on my honor 5x and am able to use adb automatically without accepting an RSA prompt (have installed twrp, rooted, etc.) but when I dload a MM stock rom and use usb debugging it is unauthorized and I get no RSA prompt I've even gone as far as to delete /data/misc/adb from my device and adbkey.pub from my desktop but there is still no pop up authorization in MM
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
ShadySquirrel said:
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
Click to expand...
Click to collapse
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Tsunetoma said:
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Click to expand...
Click to collapse
Tried toggling the debugging switch? I had issues like these on one of my previous devices, but usually these were fixed with a simple port change or debug off/on switch, if revoke->replug didn't work.
Have you checked drivers, or if dmesg says something about the device, if you're on Linux? Sometimes even running multiple adb instances (like one from terminal and one from Android Studio, for example) can cause this behviour.
Enable rsa key authentication

Connection/installation problem as ADB device - not listed

Hi,
I need to get my V30 listed as adb device in the command, but I experience big problems with this normally simple step.
I have a rooted Nvidia Shield, so a little experience with adb, but I'm too stupid to get my V30 recognized as an adb device. USB debugging is activated on the phone for sure, but I have the impression it's not because I don't know what is going on.
I have tried different things, and uninstalled the phone driver between my different approaches with the USBDeview tool.
install adb-setup-1.4.3 completely + connect V30 -> run command from the adb.exe directory on my hard drive -> no devices listed/found
used a USB 2.0 port instead of USB 3.0, still nothing.
tried to install the Google USB driver via device manager manually by selecting "android_winusb.inf" file, but Windows says the device is already installed with the newest version. It's listed under "portable devices", no clue how I can change this. My shield tablet was listed under other devices as well as adb device etc....you know what I mean. So I have no idea why the V30 makes so much problems here.
I installed the Android SDK and downloaded Google driver from there to use them for the V30 driver installation -> Windows 10 says already installed, no chance. When I uncheck the box "compatible hardware", I can only choose between some MTP device drivers, no adb or google driver or anything like that. :crying:
I tried restarting both, PC and LG V30, did a reset to factory settings of my V30.....no chance. I would like to disable some bloatware apps and use the SD card as internal storage (formatting function of the SD card as internal storage isn't available, silly I know). So no root for now, just a little extra functionality. I don't know what to do, please help me. :crying:
JogibaerNr1 said:
Hi,
I need to get my V30 listed as adb device in the command, but I experience big problems with this normally simple step.
I have a rooted Nvidia Shield, so a little experience with adb, but I'm too stupid to get my V30 recognized as an adb device. USB debugging is activated on the phone for sure, but I have the impression it's not because I don't know what is going on.
I have tried different things, and uninstalled the phone driver between my different approaches with the USBDeview tool.
install adb-setup-1.4.3 completely + connect V30 -> run command from the adb.exe directory on my hard drive -> no devices listed/found
used a USB 2.0 port instead of USB 3.0, still nothing.
tried to install the Google USB driver via device manager manually by selecting "android_winusb.inf" file, but Windows says the device is already installed with the newest version. It's listed under "portable devices", no clue how I can change this. My shield tablet was listed under other devices as well as adb device etc....you know what I mean. So I have no idea why the V30 makes so much problems here.
I installed the Android SDK and downloaded Google driver from there to use them for the V30 driver installation -> Windows 10 says already installed, no chance. When I uncheck the box "compatible hardware", I can only choose between some MTP device drivers, no adb or google driver or anything like that. :crying:
I tried restarting both, PC and LG V30, did a reset to factory settings of my V30.....no chance. I would like to disable some bloatware apps and use the SD card as internal storage (formatting function of the SD card as internal storage isn't available, silly I know). So no root for now, just a little extra functionality. I don't know what to do, please help me. :crying:
Click to expand...
Click to collapse
try installing the lg usb drivers mobileusbdrivers.com/2017/10/lg-v30-usb-drivers-download.html
madhouse24 said:
try installing the lg usb drivers mobileusbdrivers.com/2017/10/lg-v30-usb-drivers-download.html
Click to expand...
Click to collapse
This worked for me.
Sent from my VS996 using Tapatalk

Question Phone won't connect to pc via usb

My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
That's strange, either your port is damaged or you don't have drivers installed. I've heard if this happening on Windows 11, never had a problem on Linux
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
Do you have the latest USB drivers installed?
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
The drivers are installed. My home pc is what I used to unlock/root the phone.
When I look at Show Hidden Icons -> Safely Remove Hardware and Eject Media, there is an option to remove Pixel 6. Yet it doesn't display under File Explorer or XYplorer.
If I start up my Arch (linux) vm with VMware Workstation Pro under Removeable Devices there is an entry for Google Pixel 6 with the option to Connect (Disconnect from Host). The contents can be under Arch.
Have you tried different cables & different ports? Sometimes the cable is the problem for me.
Different cables/ports had no effect.
I've got the same issue, what's weird is I can move files with ADB but can't in Windows.
If you figure anything out please hit this back up?
First make sure you have a good usb cable.
Some cables are only made for charging.
Second install the USB drivers from Google.
If you can transfer files, but can not use ADB/Fastboot, then it is a driver issue.
vandyman said:
First make sure you have a good usb cable.
Some cables are only made for charging.
Second install the USB drivers from Google.
If you can transfer files, but can not use ADB/Fastboot, then it is a driver issue.
Click to expand...
Click to collapse
Cables/drivers are good. ADB/fastboot work fine it's the transferring of file/recognision of device in windows explorer that is the issue.
thecdn said:
it's the transferring of file/recognision of device in windows explorer that is the issue.
Click to expand...
Click to collapse
Switching from charging mode to file transfer mode in the Connected devices/USB menu should give you access to Android's internal storage from Windows. USB debugging or other Dev options aren't necessary.
I had this same problem. Connecting to pc would show connection options but they were all greyed out and the phone would only charge. I couldn't find any option in the standard settings to change this.
Eventually I found 'default usb configuration' in dev options. Default was set to 'charge only'. You can sort it from there.
edit to add: although re-reading op you may have tried this already.
I solved mine by setting to PTP mode then the PC started to recognize the phone connected
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
It's the stupid Windows drivers. There is an .inf file you need to either edit or delete but I forgot which. Might be wpdmtp.inf in the windows directory, right click and install. You might have to uninstall the driver in device manager first, the one with the exclamation mark if it's there. Sorry it's been about 3 or 4 years since I have done this but it's most likely a driver issue.
Mike Tanner said:
I solved mine by setting to PTP mode then the PC started to recognize the phone connected
Click to expand...
Click to collapse
I'm checking this on my work pc. It gives me access to DCIM and Pictures folders only. Which give me something to work with at least.
thecdn said:
I'm checking this on my work pc. It gives me access to DCIM and Pictures folders only. Which give me something to work with at least.
Click to expand...
Click to collapse
I agree about drivers, that they're either corrupted or incomplete. What's going on in Windows Device Manager when the phone is in a certain state?
During normal operation I assume the general purpose driver is always visible.
Device Manager > Portable Devices > Pixel 6
In fastboot mode with USB debugging enabled, is this driver showing up?
Device Manager > Android Device > Android Bootloader Interface
While Android is running with USB debugging enabled, do you see an ADB driver (the daemon may need to be started)?
Device Manager > Android Device > Android Composite ADB Interface

Categories

Resources