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.
Related
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)
My end goal is stock lolipop rooted.
I botched a flash and now I cant get developer mode / ADB working.
When I started, my tablet was stock ROM, towelroot. I connect tablet in developer mode, flashed dual recovery and everything was great. I copied the pre-rooted lolipop ROM to my SD card and flashed it. HOWEVER instead of turning off the device, I selected reboot from recovery. This resulted in boot loop.
SOOOO, I figured no worries, just flash old ROM and try again. So did this:installed Androxyde Flashtool
opened XperiFirm
downloaded 1276-8392 and 1274-8801 (I've tried the rest using both ROMs btw)
Tools>Bundler>Create>Selected folder>selected SGP312 for device
For branding I entered the above ie 1276-8392
For version I entered the ver ie 10.5.A.230
Flashmode>checked boxes to wipe everything
The flash goes through without a hitch. Under about tablet, I see
Model : SGP312
Android Ver : 4.4.2
Kernel : 3.4.0-perf-g32ce454, [email protected]#1
Build Number : 10.5.A.0.230
I activate USB debugging and unknown sources, connect to USB and Flashtool returns: Device connected with USB debugging turned off
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
I downloaded Sony's ADB drivers, tried to manually update device driver and windows7x64 kicked back driver is not for your device.
I edited the INF to include the hardware ID exactly as it appears in device manager and tried again. This time windows let me load the driver. It shows up in device manager as 'Sony sa0107 ADB Interface Driver'
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Is there a way to verify developer mode on the tablet? What else can I try? The tablet gives me a notification when I connect 'usb debugging mode connected, ready to install software'
Thanks!
_sadpanda said:
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Thanks!
Click to expand...
Click to collapse
I had a very similar problem in 2014. I do not want to discourage you, but at the end I send it back to sony for a repair. They gave me a new tablet and said that the mainboard was broken.
Nevertheless, there is a thread in Sony cross device general, where people like you end up: http://forum.xda-developers.com/showthread.php?t=1849170
You can try and search for help there, maybe you have more luck then me.
Its odd... ADB was working and stopped after flash. Is this what you had or just no connection from the start?
Sorry, I misread your post. I thought your tablet would not start and you could not get flashmode working. Sorry for that.
What you could try:
1. Be sure you actually activated USB debugging in developer options
2. When you connect the device, you should get a prompt on the tablet to allow usb debugging from that computer
Maybe try "revoke USB debugging authorisations" in developer options and reconnect
3. Install the drivers from flashtool/drivers/ or install sony pc companion. Delete your old driver from device manager.
4. try switching between MTP and MSC mode in usb connectivity menu
Since ADB worked before it was probably no driver problem. Now you cannot be sure. Most probably you tapped away the said prompt of allowing usb debugging when connecting.
If none of this helps I don't know of anything more. Maybe try different usb ports or even computers.... Or try to flash again
bernddi said:
4. try switching between MTP and MSC mode in usb connectivity menu
Click to expand...
Click to collapse
UGH!!! I'm a jacka$$. I totally forgot about that menu/setting. fixed instantly.
Hello All,
Just picked up the Le Max 2 last week (Le X820), what a fantastic phone!
My question though. I have enabled USB debugging on, but cannot get ADB to connect in fastboot? For some reason when I plug it into the PC it only brings up PTP, MTP or charge only. No matter which I pick the phone never asks for authorisation as my other phones do? This I’m guessing is why ADB can’t see it?
I’ve tried toggling it on and off and revoking permissions etc., but no joy.
bump
Same problem with my Le X821 (Indian)
manic_minor said:
Hello All,
Just picked up the Le Max 2 last week (Le X820), what a fantastic phone!
My question though. I have enabled USB debugging on, but cannot get ADB to connect in fastboot? For some reason when I plug it into the PC it only brings up PTP, MTP or charge only. No matter which I pick the phone never asks for authorisation as my other phones do? This I’m guessing is why ADB can’t see it?
I’ve tried toggling it on and off and revoking permissions etc., but no joy.
Click to expand...
Click to collapse
Even I face the same problem, I have enabled usb-debugging and toggled between Charge only and MTP, still ADB does not list my device
Any ideas folks? SDK dev' kit installed. ADB and fast-boot installed. USB debugging on? Have also tried the USB driver cleaner and the universal android USB drivers.
Also tried the adb wireless app,no go?
I am also having this issue.
I have used the Google Generic Driver for Android
I also couldn't get adb working from the booted into normal rom state. But fastboot worked ok from fastboot mode for me.
I had attempted to NOT even look up fastboot devices. I actually honestly proceeded with "adb reboot bootloader" then "fastboot flash recovery recovery.img" BUT instead of recovery.img I downloaded directly from Twrp "twrp-3.0.2-1-x2" and flashed that and it all worked out.
FIXED
****************FIXED*******************
Took a clean intall of Win 10. Permissions popped up after plugging in phone. Now rooted.
I've been having issues with adb on pie. It just doesn't recognise my phone. I've tried uninstalling and reinstalling the drivers but it doesnt work for me. Although, the pc can recognise my phone but not in adb. Whenever i run a adb command i don't get a prompt on my phone asking to allow the pc which is weird. I need help here.
Just had the same issue. On Windows. Reinstalled the adb drivers, didn't help. This, I think, is what resolved it for me, YMMV:
While the phone is plugged to PC,
disabled USB Debugging in Developer Options,
observed a toaster notification on Windows about updating/installing drivers for my phone,
enabled USB Debugging again, clicked Allow on the dialog that popped up,
and I was back in business.
nameanyone said:
Just had the same issue. On Windows. Reinstalled the adb drivers, didn't help. This, I think, is what resolved it for me, YMMV:
While the phone is plugged to PC,
disabled USB Debugging in Developer Options,
observed a toaster notification on Windows about updating/installing drivers for my phone,
enabled USB Debugging again, clicked Allow on the dialog that popped up,
and I was back in business.
Click to expand...
Click to collapse
Thanks. I'll try this once i get back home.
Me too
mayankjet said:
Thanks. I'll try this once i get back home.
Click to expand...
Click to collapse
I have the same problem, and it waas not fixed disabling and enabling USB debugging. Did you found the solution? Or someone found? Or God if you are there listening? Or the devil, i am ready to sell my soul for this.
marcebil said:
I have the same problem, and it waas not fixed disabling and enabling USB debugging. Did you found the solution? Or someone found? Or God if you are there listening? Or the devil, i am ready to sell my soul for this.
Click to expand...
Click to collapse
I think i had to update the adb to its latest version.
Sent from my Nokia 7.1 using XDA Labs
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!