No USB Debugging popup - Android Q&A, Help & Troubleshooting

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?

Related

[Q] Is ADB Wireless broken on Android 4.2.2?

Trying to run ADB Wireless on the Nexus 7 w/ Android 4.2.2; it hangs the program when enabling (pressing the big green button) and reboots the tablet. Do you think this has got something to with this new RSA identification for ADB connection or am I just crazy? (Worked fine on 4.2.1 and below)
EDIT: I'm crazy; it's working.
You're not crazy, it wasn't working for me either. What i did to fix it was to plug in usb cable, disable debugging then reenable it, got the rsa, checked always allow this computer et voila, it's working for me now.
Sounds like you already updated your adb, which was also necessary.

VZW G3 not detected by ADB

My phone isn't being detected by adb. Almost as if USB Debugging isn't even enabled (which it is). ADB is just blank when I run adb devices.
I've installed the LG VZW G3 drivers. Any suggestions?
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Make sure you have developer options visible
Enable USB debugging
Connect your phone to your computer
Pull down and change the USB connection from installer/MTP to internet > ethernet
Open Command Prompt window where ADB is installed, and type in "adb devices"
Allow when you see the RSA prompt
Run the batch file for ioroot, type "adb reboot recovery", install from adb, run sideload command, and then reboot
Also, make sure you're running the latest version of the SDK. Mine wouldn't work until I updated. HTH!
mjforte said:
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Click to expand...
Click to collapse
+1
Sent from my VS985 4G using Tapatalk
mjforte said:
Make sure you change the USB mode to internet and then Ethernet. Took me a while to figure that out.
Click to expand...
Click to collapse
+1 - This was my problem too...many thanks!
usb drivers
blmartin said:
+1 - This was my problem too...many thanks!
Click to expand...
Click to collapse
Use the LG USB drivers for Verizon Wireless!
Change the usb connection mode to Internet/Ethernet
My adb was the problem on mine. I had to reinstall java jdk and the sdk and worked perfectly the first time I tried after that
asialove2013 said:
Use the LG USB drivers for Verizon Wireless!
Change the usb connection mode to Internet/Ethernet
Click to expand...
Click to collapse
Either I'm completly blind or ... my G3 doesn't have that option. I only got "Charge Phone", "Media Device (MTP)", and "Send images (PTP)" to configure the USB PC CONNECTION. I also have the option to switch on USB tethering, but that doesn't change anything for the better, either.
Where's that Internet/Ethernet connection mode hidden?
The internet option might not appear until the usb is connected to the pc. Recheck available options while connected.
-Set phone for PTP connection
-Plug phone into PC via USB. You should see a driver loading/loaded message on your PC
-On the phone, change USB connection to Internet, then select Ethernet on the submenu that will appear
(PTP seems to "wake up" the ADB driver on the PC side for me. This was mandatory on a couple of prior phones/tablets, so it's what I did with the G3.)
Or switch to Linux and never hear about drivers ever again!
Verizon on Windows 8.1
So, the problem I had on windows 8.1 was that when you connect the device and it asks you what action to take automatically, you need to click that and install the Verizon stuff. I had my phone in USB debugging and Ethernet mode while doing this install. After it installed everything, the window on my phone for debugging permission showed up, and I allowed it. The phone now shows up in adb. I don't know if this was obvious but I thought Id mention it anyway
After the last G3 update from Verizon, the Ethernet option is gone. I can't get it to talk with ADB any longer. I see the developer mode come up on the phone, but it never asks for security key or appears in the ADB list. Anybody have any good ideas? This is on a Mac and I've never had a problem before doing this.
EDIT: After juggling back and forth from PTP to MTP to PTP, restarting ADB, I got it to connect. No clue what the key was, but working again for the moment. The Ethernet option is still gone from the phone though so that simple fix is no longer an issue.
Averix said:
After the last G3 update from Verizon, the Ethernet option is gone. I can't get it to talk with ADB any longer. I see the developer mode come up on the phone, but it never asks for security key or appears in the ADB list. Anybody have any good ideas? This is on a Mac and I've never had a problem before doing this.
EDIT: After juggling back and forth from PTP to MTP to PTP, restarting ADB, I got it to connect. No clue what the key was, but working again for the moment. The Ethernet option is still gone from the phone though so that simple fix is no longer an issue.
Click to expand...
Click to collapse
I installed the skydragon rom, which is based on stock so probably the same. I found that PTP worked but MTP did not. This is in Ubuntu Linux.

ADB wont recognize my G3

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)

Help with broken lcd device

Hello,
recently my bluboo xtouch (android 5.0.1) got its display broken and so i cna't see anything on screen, so to get access again to it i wanted to use [email protected] but my device isn't recognized by adb.
the touch on the phone still works but i don't know how well, the phone is still working as it is receiving messages and phone call, i managed to get the phone connected to the same network of my pc.
Now, usb debugging should be on as i never turned it off (is there a way of testing if it is enabled?), the phone is set to PTP as windows recognize it as a camera and i can access the phone but only the folders called
DCIM and Pictures. Under device manager it shows up as a portable device. The problem is that it won't show up in adb, i tried a lot of solution but nothing worked (the adb_usb.ini is set to the right VID, i got the drivers for my phone installed, i got 2 version of adb (one sohuld be 32 another 36) one from a freshly new install of android studio and another that i think is the universal one).
IT DOES SHOW UP IF I PUT IT IN (VOL+)+(POWER) MODE
Now i have no clues of to get it working i thought that, if the problem is the PTP mode i would need screenshots of the ui so i can change the mode without seeing the real screen, but the rom that is used by my device
is not that popular.
Anyone has any idea on how to show it under adb devices?
Thanks in advance
NEWS
i managed to reach the "select type of connection" and i've tried charge mode (doesn't work), old for xp (it shows up as a cd rom), and now i'm trying with MTP but i got problem with drivers
NEWS II
i managed to connect the phone in mtp and to copy all the files i needed to the pc, but still i'd like to get [email protected] working, i can swap between connection mode (mtp, ptp, charge) and i can unlock the phone (cause it's fingerprint locked). My new problem is: how do i backup all of my contacts?

LineageOS 14.1 - How to activate USB massstorage access?

Hi!
I have searched XDA forum and other forum concerning LineageOS. But I have not found a solution.
My latest experiments were with installation of the adb interface on windows. At first, this worked well and I got full massstorage access. The Galaxy and its both memories did show up in Windows Explorer (like in old ages).
At the next restart of Windows (Win 7 64-bit Pro) when I connected my phone, Windows immediately did install the samsung drivers again. And since that things got even worse: No even the MTP and PTP Mode did not work, so that the Smartphone does not show up at all in the Windows Explorer!
At F-Droid, I have found an app, called USB Mountr. I tried this, but without any effort.
In the device manager of Windows I can see an „Android Composite ADB Interface”. It tells, that the device would work OK.
Now I am stuck with this and I hope, someone will help me, to activate usb massstorage access.
BTW: I have flashed my Galaxy S2 with Heimdall, running on Ubuntu. Heimdall on Windows 7 did not work, because of libusb error -12.
Latest status:
I have uninstalled the app USB mountr and did reboot the phone. Now the USBconnector is only active for charging the battery. I even get no connection in PTP or MTP mode.
Then I have deactivated USB debug mode and ADB. did a reboot, reactivated ADB and USB debug etc. and did further reboot the phone but with no success.
USB connection is nearly dead and cannot have connect with LUBUNTU Laptop. On Win 7, I get the signal tone, which is typical for connecting an USB device. The GT.i9100 shows up in Explorer but cannot be connected. Device manager tells me, that it is an Android device and all would be OK.
As a work around I am using MyPhoneExplorer on Win-7 and KDEconnect for Ubuntu.
Please can anybody tell me, what I should do, to get back at least USB connection in MTP or PTP mode???
I have the exact same problem.
I did notice, that after first boot, there was a message (several times) the MTP daemon/service stopped working (Crashed ?)
Does anyone else encounter this ?
Did anyone else resolve this ?
(Currently I was only able to get/send files to the device via BT, which is slow, annoying,
and a lot of work moving files to their required places after transmitting over BT)
Quick Fix for stuck on boot
This probably isn't the right place but you said there weren't many solutions. If your phone randomly gets stuck on boot you need to Delete Everything including system, factory data reset, flash ROM again with ADB, go through setup. The reason it probably hanged is because you installed an old version of SuperSU Binary or because you flash OpenGapps before setting up phone.
Hope this works
P.S Sorry for the late reply

Categories

Resources