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)
Related
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
But when I reboot my tablet as USB mode and from my laptop I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
I have already unlock and rooted my tablet.
Why I can't see my device id ? Please help
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yeah this process is correct. Even I've experienced this.
What I did is:
Removed the USB cable connection and reconnect.
Kill adb.exe
Restart adb.
Then device was shown to be connected.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yes, I did that but still the same. Any other suggestions?
If on windows make sure your driver's are installed.
Type in cmd
adb kill-server
adb start-server
If that doesn't work try a different usb slot. You could also try moving adb and it's dependencies to your system32 folder. It's where all your commands are stored for cmd. You won't have to navigate to the android sdk tools.
Sent from my SPH-L710 using Tapatalk 2
Have you enabled Debugging on in your phones Developer settings?
ngaisteve1 said:
Yes, I did that but still the same. Any other suggestions?
Click to expand...
Click to collapse
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
no need for that.
close any adb process either from task manager or by typing: "adb kill-server" in adb console
close everything and use this customized adb file I attached, it'll show your device.
it also has instructions and necessary files for rooting your device.
Problem
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
I have LG Optimus G (E975) i wipped all from the device and now i can't put cm11 on it, adb sideload do not work, and list of devices attached is empty. what must i do to put CM11 on my phone?:crying:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
I have the same issue on my nexus 4. Yesterday it showed up with adb devices, now it's an empty list. I have USB debugging enabled and tried restarting the server. Nothing works. Any ideas?
ldemon360 said:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
Click to expand...
Click to collapse
unplug the device and adb kill-server then replug the device and try
turn debugging off and then on again
I had the same problem. In my case, i had forgot to enable usb debugging after new rom.
ngaisteve1 said:
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
Click to expand...
Click to collapse
In your case just disable USB debugging and then enable again.
fix the driver
I had this issue.
In my case when I went to device manager I could see the Device and wasn't installed correctly and could not load the drivers even after having installed them on the PC.
SO I clicked update drivers.
Select that will chose the drivers to install and select the Android Devices - ADB driver.
You will get a warning, but just ignore it and load the ADB driver for the phone.
Ensure you are in the sideload option of the recovery
Now
adb devices
it should show up as Sideload
Now sideload
Cheers
Dirk
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Thanks, this worked for me.
Just add ur device id in adb.ini
Same issue was faced by me on my micromax Q334 and xolo era, I search lot for that and finally just adding hardware id the device are detected under adb.The steps are clearly shown in my video below..
It will definitely going to sort this problem..
For that just right click on adb driver ,navigate to detail tab and search for hardware id then add to adb.INI
I have also uploaded video on that YouTube: Fix adb connection issue(Adb driver installed, but device not listed)
device listed as "? recovery"
hey,
am trying to connect honor 6(h60-L04) but am not able to see the proper name for my device is just showing "? recovery" and am trying to update the android version coz of the device is in reboot-loop so help me out here
if there is any other option to recover device give me link.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
not work my friend, the list of devices is empty
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
vern.zimm said:
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
Click to expand...
Click to collapse
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.
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.
As the title suggests, bootloader unlocked no problem, tablet was connecting to ADB at the time, tried to flash recovery which as far as I can tell was not successful (I can't boot to recovery, get the injured Android icon), now I can't connect to ADB (get the "List of devices attached" result). So I'm completely stuck, can't move forward, can't go back to stock, what do I do?
Edit: Apparently it's an issue with my PC, my wife's PC worked fine, why it worked to unlock the bootloader and then stopped I have no idea. Can anyone link me to a solution to get ADB working on my PC again? I tried removing/re-installing drivers, rebooting, you name it, no luck.
With your device booted into recovery or the system do you get anything in device manager? If you get a device with a yellow exclamation mark, right click it. Go to where it allows you to choose a driver from a list on your computer. Select adb android composite (or something like that)
Sent from my Nexus 5 using XDA Free mobile app
Thanks for replying.
So before unlocking the bootloader, with USB debugging enabled I could get the tablet to connect using the ADB driver and could access it with ADB but could not access storage for file transfer, with USB debugging disabled and switching the driver manually to the MTP driver I could access storage but not ADB. I have had other device drivers installed on this PC for my Galaxy phones, I had issues initially with the tablet connecting but showing a yellow exclamation mark, then I removed all of the Android USB devices using USBDeview and installed the 15 second ADB tool to get it working, I'm on Windows 8.1 BTW.
After unlocking the bootloader, with USB debugging enabled I cannot get the tablet to connect using the ADB driver and but it does show as an ADB device with no yellow exclamation mark, I just get the "List of devices attached" result and anything that tries to access the device via ADB hangs or fails. I can still switch the driver to MTP and access the storage just fine.
My wife's PC is a Win7 box and has never had android drivers or ADB installed, I used the 15 Second ADB installer on her PC and the tablet works for ADB and storage access with USB debugging turned on, so there's something I'm missing that needs to be wiped out or reset on my box.
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
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!