Related
I Tried guides that try to solve this from everywhere, Including here,
I used latest version of the android usb-drivers that comes with the latest Android SDK (downloaded directly from google with the SDK download GUI thinggy).
Tried to uninstall all usb roots,
Tried force removal of driver using external app and re-installations
Tried different drivers from multiple locations,
And still, whatever I try - there is notihng on the "adb devices" list
"List of devices attached"
<CR>
<CR>
C:\.......>
Everything shows up okay, on first run of the adb the 'whatever' service starts and everything is fine
Device DOES appear properly on device manager "Android Composite ADB Interface".
Windows DOES the pnp beep whenever I check or uncheck the "Debugging mode"
This hapnned both on STOCK ROM (first or second software version of the phone released) and on latest Cyanogen 5.0.6
One thing I did noticed, "Android ADB Device" Either appear under "Android" type (usb debugging on) or under USB Controllers (When usb debugging is off).
Ho, I did not mentioned the phone, I'm talking about Nexus One.
Thanks for any help.
Amm, any ideas?
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
I take it your on Windows, so I might not be much help as I use Linux strictly but try to run the command prompt as Administrator (right click > run as I think) and then
adb kill-server
adb start-server
Not sure if that will help but I know in Linux you must start the ADB server as root in order to see the attached devices, so I assume in Windows you must start it as Administrator.
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Beackman said:
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
Click to expand...
Click to collapse
I Ment just that when I said "Tried force removal of driver using external app and re-installations"
drew630 said:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Tried that just now, on windows I'm in the Administrators group, that should work... It doesn't :/
bmxrideher said:
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Click to expand...
Click to collapse
Good idea, but still no salvation :/
Try uninstalling the mass storage driver for the phone, this worked for me
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Synestr said:
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Click to expand...
Click to collapse
No problem, lol, almost a month later. Glad I could help.
Naemion said:
No problem, lol, almost a month later. Glad I could help.
Click to expand...
Click to collapse
Hells to the yea, I now has root and rom and I am a happy boy!
Thanks again
hmm >.< nothing is working for me this laptop is not detecting my (Nexus S) device in ADB
windows sees it fine, drivers are installed (for normal mode and ADB mode), mass storage works,
but ADB Devices list shows up empty
2 other phone works just fine (SGS & XT720)
Update: went to another computer and it shows up properly.... (you just gotta "luv" windows )
Try installing htc sense from htc website even if running vanilla. It will install the driver properly. Then un-install sense and keep drivers. It's the only thing that worked for me.
Sent from my HTC Vision using XDA App
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
akashi said:
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
heat361 said:
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
Click to expand...
Click to collapse
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
Click to expand...
Click to collapse
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
heat361 said:
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
Click to expand...
Click to collapse
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
Try pointing the path to the Google drivers in the android-sdk in device manager and not the naked drivers.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
This is what I did and waited for the PC to install the adb drivers.
I plugged the phone in and with the USB plugged in turned it off while holding the volume up and down keys. This made my nexus 4 go into download mode and the PC automatically installed the adb drivers. After I just unplugged and held the power button to restart the device hope this helped.
Sent from my Nexus 4 using xda premium
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
Thanks.
Click to expand...
Click to collapse
When you uninstalled what's there now, you did make sure to check the box that will remove the old drivers from your PC?
Just in case, HERE is another source for the drivers.
dinhume echoes
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
akashi said:
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
Click to expand...
Click to collapse
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
El Daddy said:
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks. I tried version 16.01 and still have this problem.
The problem is whenever I uninstall/install the ADB driver or disconnect/reconnect the USB, **ONLY** the "Nexus 4" appears on the Device Manager which I manually install the ADB drivers to. There is not a second "Nexus 4" on the Device Manager for the MTP or PTP.
On my laptop when I remove all drivers and reconnect the USB cable, I always see 2 "Nexus 4" listed on Device Manager. One for the ADB interface and the other for the MTP or PTP.
Please help!
Any ideas please?
Any Solution to ADB connection problems?
Hi was there any solution to this, as I seem to have the same issue.
I have tried different drivers and MTP & PPP modes as well as loading the PDAnet drivers and software.
Each time now I take care to remove all the drivers and also delete the drivers in all modes (Android running and Bootloader running)!
MTP & PPP load different copies of the drivers.
I can get either "Nexus 4" showing up in the device driver or "Google ADB Interface" or Android ADB interface" according to the driver loaded.
I can see the device when Android is running ie "ABD Devices" gives me the serial number and connected, then I can send an ADB command "adb Reboot-bootloader" the Nexus then reboots into the bootloader screen, the device driver changes to the bootloader driver (installs if not installed) however then I loose connection to the Nexus phone! "ADB Devices" returns none connected.:fingers-crossed:
I also tried unplugging and plugging back in the phone in bootloader mode but do not get adb to see the handset or it to react to commands.
I'm just about ready to try a toolkit to see if I can get past this roadblock!!!
Current computer is Win7-x64
This weekend I will try on a different computer.....Win8-X64
All comments appreciated
That's because you cant use adb when in boot loader. You use fastboot
Sent from my Nexus 4 using xda app-developers app
I have same problem on my work laptop DELL when my custom desktop machine works just fine with both Nexus 4 and 7. :/
I am generally good at rooting any android phone. I am having a hard time locating the drivers for the VZW LG G2. I have the zip file from the post on how to root the phone, but I am not sure which file to install.
Any input would be appreciated.
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
iowabowtech said:
If they aren't auto detected and installed after a reboot with phone plugged in, goto device manager, locate the phone and manually update driver pointing it to the LG folder full of drivers. To get the adb interface working, you may need to be in the internet connection mode with the ethernet option selected. Can't remember if that was the case or not.
Click to expand...
Click to collapse
I needed to install LG VZW_United_WHQL_v2.11.1 then go to LG website and download drivers from the G2 support page. I couldn't upload the exe file. Restart computer and all went well. I had same issue and struggled to solve.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Bxrider117 said:
So I figured out how to install the drivers but when I go to command prompt and type"adb devices" it does not recognize it as a command.
Click to expand...
Click to collapse
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
i'm having the same issue. i'm trying to root, and it won't list it at all, and i'm not getting the debugging icon on top. no serial number popping up on the abd devices and i just tried with both 3.8 and 3.10 drivers. anything?
If I remember correctly I had to go to settings>pc connection>select USB connection method and then choose Internet connection, then choose modem in order to get the debugging icon to appear.
Sent from my VS980 4G using xda app-developers app
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
thanks!
bigox said:
I'm having trouble with my PC not recognizing my phone at all. It says USB device not recognized. I'm on Windows 7 64bit if that matters.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
Most likely it's because you don't have the right drivers installed. Try installing these http://g2-lg.com/download-lg-g2-android-usb-drivers-ver-3-10/.
Sent from my VS980 4G using xda app-developers app
The drivers aren't working for me so i will link where you can get the drivers from the actual website. Please note: this link is for Tmobile D801 but you can search for your device on there.
http://www.lg.com/us/support-mobile/lg-D801
LG's website has drivers for D800 and D801. I'm looking for D802 drivers. Where can I find them or which are compatible?
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
cggorman said:
The Universal device drivers aren't universal?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Where can I find Universal drivers? Not on LGs website.
I installed this:
http://forum.xda-developers.com/showthread.php?t=1379875
And after that it worked fine. I have a ls980, so the att and t-mobile don't work for me. This did.
This took me a while to sort out. There is a certain driver package for the verizon phone. The drivers listed here dont seem to work for me. I'm using win 7. Here is what I needed to use, then everything just came together - LG VZW_United_WHQL_v2.11.1
These can be downloaded at LG's site. Make sure you search for drivers pertaining to the model number of your phone.
Hope this helps someone
EVOme said:
You must have the sdk with adb installed before you do that part. Browse to that directory, find adb, shift right click, open command prompt here. Then do 'adb devices'. You'll see serial # on left and 'device' on right. It's working then. If you get 'offline' on right, you need to update your adb.
Click to expand...
Click to collapse
I am having the same issue..what is the sdk with adb installed and what directory do i browse to? sorry for the noob questions, ive always had nexus's, so much easier to flash recoveries etc
LG Drivers failing to install
I Install LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1.exe from LG website, it installs and I get a "successful" message from the software package. However, shortly after windows pops up a bubble with "not successful". Details:
Uninedntified Device - No Driver Found
Creative Game Port - Failed
Plug in phone and select “PC Software”, since none of the other options make any sense (USB charge, Media Transfer, Tethering, and Picture Transfer). Sidebar: None of the other options seem to change anything even when tried. "Media Transfer" is the only one that seems to actually install something successfully, but nothing changes with the device list. Back on track: Get a new windows “installing” bubble. Shortly after I get another “not successful” message with the following:
MTP USB Device – Failed
I go to Devices and Printers, select the phone, and look in the properties. Click “update driver” and pick the LG folder in Program Files. It says “driver already installed”.
Rebooting the computer accomplishes nothing.
I’ve tried several full uninstalls.
No matter what I try, if I run “adb devices”, I get “List of Devices Attached” then my prompt back, meaning none found I assume.
Yes I have turned on dev mode on the phone and I get the debugging icon when the USB cable is plugged in. I’m on Win7 64. WTF is wrong with this driver?
Thanks for any help you can give!
Uncheck usb debug? Had this on my htc one x. Maybe helps
Sent from my LG-D802 using XDA Premium 4 mobile app
Anyone have any tips for this? I finally got adb working on my computer and I installed the LG drivers but when I type adb devices my phone does not show up.
Thanks
I'm having the same problem. Can anyone please help?
hanbaoquan15 said:
I'm having the same problem. Can anyone please help?
Click to expand...
Click to collapse
I had the same problem. My PC was using samsung drivers. Go into device manager with your phone plugged in and see what driver it is using for your phone with adb cmd window open. If it is not LG, then go to LG support page for this phone and find downloads for PC and get the LG mobile driver. Install it and then check device manager again. It should now show LG adb device. If not, then select update the driver in device manager and change it manually. That's how I got it working.
androiddiego said:
I had the same problem. My PC was using samsung drivers. Go into device manager with your phone plugged in and see what driver it is using for your phone with adb cmd window open. If it is not LG, then go to LG support page for this phone and find downloads for PC and get the LG mobile driver. Install it and then check device manager again. It should now show LG adb device. If not, then select update the driver in device manager and change it manually. That's how I got it working.
Click to expand...
Click to collapse
The computer doesn't recognize the phone at all. There's no USB reading from it, the only thing it does is charge the phone.
I'm not sure why this is the case, never seen this before.
Edit: Nevermind that, I restarted the phone and it works. Thank you for your suggestion
androiddiego said:
I had the same problem. My PC was using samsung drivers. Go into device manager with your phone plugged in and see what driver it is using for your phone with adb cmd window open. If it is not LG, then go to LG support page for this phone and find downloads for PC and get the LG mobile driver. Install it and then check device manager again. It should now show LG adb device. If not, then select update the driver in device manager and change it manually. That's how I got it working.
Click to expand...
Click to collapse
Thank you for your assistance. Got it sorted ans phone is rooted now.
chrisrj28 said:
Thank you for your assistance. Got it sorted ans phone is rooted now.
Click to expand...
Click to collapse
Glad I could help. I spent about an hour trying to figure it out. I don't remember where I found the answer but the key was looking in device manager to see which driver the computer was using for ADB. Mine was using a Samsung driver. So even though my computer could see the phone in file manager and view internal and external memory, ADB wouldn't see the phone.
Cheers!
androiddiego said:
Glad I could help. I spent about an hour trying to figure it out. I don't remember where I found the answer but the key was looking in device manager to see which driver the computer was using for ADB. Mine was using a Samsung driver. So even though my computer could see the phone in file manager and view internal and external memory, ADB wouldn't see the phone.
Cheers!
Click to expand...
Click to collapse
Yeah that's exactly the issue I was having, forgot I had used ADB with my note 5. Once I deleted and reinstalled the drivers it was smooth sailing.
Appreciate your assistance
chrisrj28 said:
Anyone have any tips for this? I finally got adb working on my computer and I installed the LG drivers but when I type adb devices my phone does not show up.
Thanks
Click to expand...
Click to collapse
This can also happen if you don't set USB Debug on. I was able to duplicate it yesterday.
-Dog
My H910 shows up as "Android" under "Other devices" in Device Manager. I already installed the LG Mobile Driver LGMobileDriver_WHQL_Ver_4.2.0. Anything I missed?
How do you manually update the driver within Device Manager for LG V20? The LG driver is an exe file and there is no inf or actual driver files I can point to.
ADB still cannot see the phone.
zhangla said:
My H910 shows up as "Android" under "Other devices" in Device Manager. I already installed the LG Mobile Driver LGMobileDriver_WHQL_Ver_4.2.0. Anything I missed?
How do you manually update the driver within Device Manager for LG V20? The LG driver is an exe file and there is no inf or actual driver files I can point to.
ADB still cannot see the phone.
Click to expand...
Click to collapse
See my response to your question in the other thread you also posted it in.