FORUMS
Remove All Ads from XDA

[SOLVED] Unable to access with ADB/No RSA Fingerprint Key Window

108 posts
Thanks Meter: 68
 
By postal302, Senior Member on 27th July 2014, 09:46 PM
Post Reply Email Thread
--Edit--
This is finally solved. There was a problem with my computer's ADB RSA key, so I simply had to delete the key file and rerun ADB and I Received the RSA Key Fingerprint window instantly on my G3.

For the full description of the problem look here:
I'm having issues trying to root my phone. I'm using the ioroot method mentioned here.

I get to "* daemon started successfully *" then nothing. After a lot of troubleshooting I know it's because my phone won't allow access by my computer. I never receive the RSA Fingerprint window allowing my computer access to my phone. Here's what all I've tried:

-Put phone into Internet>Ethernet mode (and I've also tried Internet>Modem, MTP and Camera modes as well just to say I did).
-Enable Developer Options and enable USB Debugging.
-Installed the drivers linked in the ioroot page (I've also downloaded the drivers directly from LG - believe it or not ... it's the same file).
-Installed the Verizon Software Assistant from the phone after connecting to the computer.
-Updated my ADB version with the SDK Manager.
-Used different USB ports on my computer as well as two different USB cables (one of which came with the G3).
-Checked Device Manager, all is as it should be and no unrecognized devices.

When I ran the adb server without the ioroot batch file, typing "adb devices" would return my phone's serial followed by "offline." It did this until I updated ADB; then when typing "adb devices" it would return the serial followed by "unauthorized." I've tried all various methods and combinations of switching adb debugging on and off, switching developer options on and off, installing and uninstalling and reinstalling the LG drivers, unplugging and replugging the USB cable, power-cycling all devices including myself at night, doing these methods with long pauses in between (10 minutes to ensure I wasn't being impatient), scratching my head, drinking more coffee, switching to rum and swearing at all devices but nothing seems to make a difference.

What am I missing?

I've got the Verizon LG G3 in White (LG-VS985W)
Software version VS98510B
Windows laptop running Vista 32 bit (I know I know, "eeew Vista")

I was able to obtain root using a different computer, here's what I tried with my laptop after gaining root to get it and my G3 on speaking terms:
-Deleted the ADB_Keys file on the G3 (/data/misc/adb/adb_key): no change.
-Compared running Windows services between Vista and 8.1 and started services which were running on 8.1 but not vista: no change.


Here was the resolution:
There turned out to be a problem with my laptop's ADB RSA key. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.

ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's profile (C:\Users\*username*\.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile\.android), the file is simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.

Mine was located in my user folder (C:\Users\*username*\.android\). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. I went back to the C:\Users\*username*\.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.

Problem finally fixed!

Here are some VERY useful links which helped me come to this fix:
How ADB enables a secure connection
Reconstructing ADB's RSA key file
The Following 17 Users Say Thank You to postal302 For This Useful Post: [ View ] Gift postal302 Ad-Free
 
 
27th July 2014, 10:36 PM |#2  
Senior Member
Thanks Meter: 160
 
More
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG...mmiDrNq9W5aJIc

Open the .zip, run the .msi file on Windows.

I do not run the G3's auto-install software when I plug it into the PC.

I do set the G3 to "PTP" USB before initially connecting to the PC.

The adb file in the ioroot "bts" subfolder should be okay to run on Windows.

When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.

If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.

Then I can "cd .." and run ioroot.bat.

Good luck!
The Following 3 Users Say Thank You to markfm For This Useful Post: [ View ] Gift markfm Ad-Free
28th July 2014, 01:10 AM |#3  
postal302's Avatar
OP Senior Member
Flag Seattle
Thanks Meter: 68
 
More
Quote:
Originally Posted by markfm

Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG...mmiDrNq9W5aJIc

Open the .zip, run the .msi file on Windows.

I do not run the G3's auto-install software when I plug it into the PC.

I do set the G3 to "PTP" USB before initially connecting to the PC.

The adb file in the ioroot "bts" subfolder should be okay to run on Windows.

When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.

If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.

Then I can "cd .." and run ioroot.bat.

Good luck!

... no dice.

Ok, I'm switching to my Windows 8.1 machine (my laptop is my server and android-dirty-work machine).
28th July 2014, 04:40 AM |#4  
postal302's Avatar
OP Senior Member
Flag Seattle
Thanks Meter: 68
 
More
So it worked without hesitation on my 8.1 machine. I used the drivers listed in the ioroot thread (same as the drivers from LG) and the process went off without a hitch. I have no idea why my Vista machine and G3 don't get along but I'll need to figure it out when I do further adb work because I use my laptop for that.

Thank you markfm for the extra drivers.

I'll call this solved for now but if I find out further reasons why it didn't work I'll post it here for others who have similar struggles.
31st July 2014, 03:15 PM |#5  
postal302's Avatar
OP Senior Member
Flag Seattle
Thanks Meter: 68
 
More
Ok I finally solved this. It turned out there was something wrong with my laptop's ADB RSA key. All I had to do was delete the key file, run the ADB Server and connect the phone. ADB will automatically generate an RSA key if none exists. The RSA key was located in C:\Users\*username*\.android and was simply named "adbkey" with no extension. There was also a file named adbkey.pub (Microsoft Publisher) which I'm assuming is a viewable version of the key. I deleted both of these, re-ran the ADB server and voila I instantly received the RSA Key Fingerprint confirmation window on my G3.

Done and done!
The Following User Says Thank You to postal302 For This Useful Post: [ View ] Gift postal302 Ad-Free
3rd August 2014, 04:24 AM |#6  
Junior Member
Flag Palos Park, IL
Thanks Meter: 2
 
More
unable to generate RSA key on my MCB
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
3rd August 2014, 08:35 AM |#7  
postal302's Avatar
OP Senior Member
Flag Seattle
Thanks Meter: 68
 
More
Quote:
Originally Posted by scooterd

I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.

You'll have to bear with me because I'm not familiar with Mac file structure.

I would start from scratch. Do all these before trying to run adb again.
On your computer:
-Delete adbkey & adbkey.pub from the .android folder (I'm not sure where that is on a Mac, Home\.android?).
-I'm not sure if Macs have a device manager, but check that your phone is correctly recognized and the drivers are installed properly.
On your phone:
-Ensure you've got developer features unlocked
-Double check that you've got usb debugging enabled.
-Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options.
-When you're plugged in be sure to set your connection to Internet >>Ethernet (you'll see the debugging icon in the notification bar if it's connected right).

I know a lot of that is basic and redundant but if it's all done correctly then it should work. If it doesn't work it gives us a good starting point to troubleshoot.

If you want to test it open terminal, change directory to the bts folder in the ioroot folder and start adb (adb start-server), with everything done right you should get the rsa window on your phone right now. Type "adb devices" and see what comes back.
5th August 2014, 04:32 AM |#8  
Junior Member
Flag Palos Park, IL
Thanks Meter: 2
 
More
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
5th August 2014, 03:45 PM |#9  
postal302's Avatar
OP Senior Member
Flag Seattle
Thanks Meter: 68
 
More
Quote:
Originally Posted by scooterd

Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?

Use whatever mode will enable USB Debugging. If Internet>>Ethernet doesn't work then use any other mode that will. It's not necessarily important what mode your phone is in, but what mode will allow USB Debugging. If you have it in MTP, PTP, Camera or any other, and you have the USB Debugging icon in the notification bar, try the "adb devices" command and if it returns "*serial* device" then you should be good to go to root.

Once your phone has enabled USB Debugging and accepted the RSA key from your computer then the connection is made and your phone will accept the ioroot commands.
5th August 2014, 03:48 PM |#10  
postal302's Avatar
OP Senior Member
Flag Seattle
Thanks Meter: 68
 
More
Quote:
Originally Posted by scooterd

Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?

Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
The Following User Says Thank You to postal302 For This Useful Post: [ View ] Gift postal302 Ad-Free
5th August 2014, 08:07 PM |#11  
Junior Member
Flag Palos Park, IL
Thanks Meter: 2
 
More
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
Post Reply Subscribe to Thread

Tags
adb, ioroot, lg g3, unauthorized, windows

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes