Hello, i'm looking for help with debugging an application from the new enviroment Android Studio. When i press the debug logo, it installs on my device successfully, however i get this message constantly from the ADB Log (DDMS): "DeviceMonitor: Adb rejected connection to client '19322': closed" thus i cannot debug.
I have tried rebooting PC and rebooting device several times but that doesn't help.
I'm running Avast AntiTheft which has an option to prevent USB debugging, but that one is disabled.
Can somebody point me in the right direction
tynor said:
Hello, i'm looking for help with debugging an application from the new enviroment Android Studio. When i press the debug logo, it installs on my device successfully, however i get this message constantly from the ADB Log (DDMS): "DeviceMonitor: Adb rejected connection to client '19322': closed" thus i cannot debug.
I have tried rebooting PC and rebooting device several times but that doesn't help.
I'm running Avast AntiTheft which has an option to prevent USB debugging, but that one is disabled.
Can somebody point me in the right direction
Click to expand...
Click to collapse
Nobody got a hint for this? It's really frustrating not to be able to develop
Related
Hi there,
I recently bought a Lenovo Yoga 8 tablet and I'm trying to install cyangenmod on it. When I'm in USB debug mode I don't get RSA key fingerprint popup screen with always allow this computer. I've tried several drivers and launched the Android SDK and updated it, but still no luck. I've tried setting it from MTP to PTP and vice versa, but still doesn't work sadly.
cdn.androidpolice.com/wp-content/uploads/2013/02/nexusae0_Screenshot_2013-02-12-11-47-41_thumb.png
This is the promt popup I'm talking about, whatever I do I can't get this popup to come up. Any ideas why i'm not getting the popup?
I'm trying to root my Verizon LG G3 on 5.0.1 VS98524B, but now ADB wont recognize my device. Yesterday I was trying to root it using a one click root tool but it would fail (it would say successful, but would not achieve root). today I decided to use the LG flash tool to restore my phone and try again. then I saw that the tool (which claims to support all g3 models on all firmwares above kitkat) did not support VS98524B, but there is another that does, but surprise surprise, adb no longer finds my phone.
update... I have found that ADB on Ubuntu does find and recognize my device, and the security prompt comes up on my device. (does not come up for any window computer)
I have tried; restoring my phone again, installing and reinstalling the drivers, use different computers (2 win 7, one win 10), use different cables, on different ports, change between ptp and mtp, toggling and untoggling usb debugging, restarting my computer, etc.
adb doesn't find the phone while running a root tool, or just doing the adb devices command in cmd....
looked at many threads, and not many (if any) seem to have this problem, and all who did were able to solve using one of the steps I mentioned above....\\
any help?
update... Using Ubuntu adb does recognize my device, and prompts the security pop-up on my phone. (the pop-up does NOT come up for any windows pc)... but I cant figure out how to root the device using Ubuntu)
RESOLVED-- I uninstalled (again) the drivers, and grabbed new updated ones from the LG webpage (which ARE different than the suggested drivers on the root tool page.) then installed the android studio on my computer, and redownloaded adb... not sure which of these steps made the difference, but it worked! now rooted.
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
hawkswind1 said:
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
Click to expand...
Click to collapse
I don't think there's been an Internet/Ethernet option since before 12B, or at least before 23C.
@Coltonbyu, choose MTP for your connection type.
hawkswind1 said:
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
Click to expand...
Click to collapse
I did as you said, but the prompt never appears on my phone, which is odd, as it appeared before the factory reset, but will no longer appear for any windows pc. (it does appear on Ubuntu though)
Alright, I've tried installing the drivers from Verizion and also using the drivers from the Android SDK and either way I have the same problem. ADB devices shows my phone, however whenever I try to push, pull, or reboot (the only commands I have any use for atm) the command prompt hangs like it's trying to access the device but no matter how long I leave it the device will not reboot, nor will any files appear in the correct folders on either the device or my computer.
I'm trying to root my phone and this is a pretty major roadblock.
Note:
USB Debugging enabled
ADB drivers installed
Phone shows up on "adb devices"
There is no error or any other output in the console. The best way to describe this problem is that ADB hangs.
I'm running Windows 8.1 and my phone is running Android 4.1.2
Also, I don't know if this is normal but, In order to get the notification that "USB debugging connecting" I have to use the internet connection option on the phone. When using MTP, Charge only and PTP that message doesn't appear and I don't see an ADB device show up in device man.
Things I've Tried
Uninstalling all Android drivers and redownloading/installing them after restart
Restarting my phone multiple times
Running adb kill-server / adb start-server
Changing USB ports7
Thanks!
Try installing drivers from LG. This seems the right one but double check:
http://www.lg.com/us/support-mobile/lg-LGVS930
Hi, i've tryied to install andromeda with substratum but when i enable usb debug wont show any autorization dialog and "adb devices" says "unauthorized".
I've tryied to revoke permission deatch and reattach the cable or disable and re enable debug mode, but nothing to do
Did you get some kind of message on the phone about the connection needing you to accept it? I enabled usb debuging and adb wasn't authorized. I looked at the phone and it had a message I need to click on about a trusted connection or something and once I did that adb connected and did what I needed.
I was able to install - got the ADB pop up about devices - clicked and then installed the Andromeda ap (after installing substratum) my problem is that I can't get the Sumbstratum themes to stick - not sure what I am dong wrong - probably user error...but anyway - good luck getting yours connected.
Solved with other pc
What if we are not able to use anothe PC for the process?
How can we reset the ADB log in the PC that was refused in the first place?
Thanks!
I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
1337haXXor said:
I'm aware there is another thread on this, but his solution was simply switching the cable. For me, adb is currently working on multiple other phones, but on the G8X, it simply doesn't list the device. Any idea?
I do NOT have the full Android SDK, only the "minimal ADB and Fastboot" package, which just comes with adb, fastboot, and a couple other things. I love it and hope I don't have to install the full SDK for fastboot to work. D:
USB debugging is enabled, the device is connected as "File Transfer," and everything else is as it should be.
Click to expand...
Click to collapse
Same issue. Trying to use the Button Mapper app, and windows Button Mapper Setup keeps saying "Make sure the device is connected and USB Debugging is enabled."
Help?
You must try multiple times until a notification shows up to trust your PC.
hasso96 said:
You must try multiple times until a notification shows up to trust your PC.
Click to expand...
Click to collapse
Actually it was more "complicated" than that, as it said it ran an older version of the server than the phone at first. I googled some more, and managed to solve it. It was the installation of the LG USB mobile driver. I tried with the windows stock one at first, then tried Google USB driver from the SDKmanager, and even an universal driver didn't work. And even then when it was installed, THEN it said "unauthorized" and I had to just accept the connection on my phone
It's sorted now!
THANK YOU SO MUCH! Man, I wasn't expecting a reply after all this time, figured my unit was somehow defective or something. This worked perfectly! To others suffering, here's the direct link to the LG drivers, current version as of now, 4.4.2: tool.lime.gdms. lge .com/dn/downloader.dev?fileKey=UW00120120425 (Remove the spaces before and after the "lge").
Now I can tweak my system settings, debloat, use Button Mapper. Thanks again!