Related
I'm having an issue connecting GT to windows 7 via adb. Device manager doesn't recognize the GT. I need a little help finding the drivers.
Thanx
install android sdk, run sdk manager, and choose Google. Usb driver package, Samsung drivers.
Roadk1ng said:
I'm having an issue connecting GT to windows 7 via adb. Device manager doesn't recognize the GT. I need a little help finding the drivers.
Thanx
Click to expand...
Click to collapse
I had initial difficulties connecting via ADB. Did not see my device.
I had the USB drivers installed for my Fascinate phone, so I could mount the TAB as normal, just not recognized by ADB. When I downloaded and tried to re-install the USB drivers, PC said already installed. So, I simply re-installed the new download over the old drivers, ADB immediately recognized the TAB device.
So, Fascinate USB drivers were close but not quite complete for my Tab device.
YMMV
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
kjy2010 said:
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
Click to expand...
Click to collapse
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
looking335 said:
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
Click to expand...
Click to collapse
And please my op... of course I tried the drivers from acer's site, both of them. And my sdk kit works, just like I said. But thanks!
officetally said:
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
Click to expand...
Click to collapse
Glad it was something simple!
Sometimes we always overlook the simple things.
But I would not have told on myself.to many other things could blame it on.giggles
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. :/
Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
jining said:
Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
Click to expand...
Click to collapse
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
vorbatello said:
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
Click to expand...
Click to collapse
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
jining said:
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
Click to expand...
Click to collapse
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
vorbatello said:
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
Click to expand...
Click to collapse
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
jining said:
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
Click to expand...
Click to collapse
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
vorbatello said:
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
Click to expand...
Click to collapse
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
jining said:
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
Click to expand...
Click to collapse
So I tried installing the newest Franco kernel Milestone (3), and the USB fast charge is off. I also tried installing a different CM mod, but there is no difference. I also tried installing the universal you gave me, but that didn't work, and i installed the google driver from SDK and that didn't work.
I don't know what else to do...
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
maxiiik said:
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
Click to expand...
Click to collapse
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
jining said:
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
Click to expand...
Click to collapse
Have you managed to solve this? I'm facing almost the same problem!
No, I tried for hours with no luck. I am glad I am not the only one, hopefully a solution will come to us. I have been using airdroid to transfer files from my phone in the mean time.
Im also having the same issue except my computer only recognizes my phone when its connected as a camera.
Sent from my Nexus 4 using xda app-developers app
I am having a similar problem with my daughter's Nexus 4 phone, which is not rooted nor unlocked - it is still completely stock. It was just updated to Android 4.3, however I can't say that this is the cause of the problem because she never attempted to connect her phone to the desktop machine before.
I have a Windows 7 x64 box at home, and spent over two hours last night trying to get the computer to correctly recognize the Nexus 4 phone. I was hoping that the standard MTP Windows driver would handle it perfectly, but no luck. I tried the Google usb drivers, and the ADB interface was recognized, but still no access to the internal storage. I then gave the Naked Drivers a try, and no joy there either.
I am beginning to suspect that the MTP drivers on my desktop are munged, but do not relish the thought of a Win 7 wipe and reinstall.
Anyone else have any ideas?
Thanks much!
I am having a similar problem where I have USB storage set to MTP and Windows doesn't pick it up, whereas PTP Windows will pick up but I can't access any folders other than the camera related folders like DCIM.
So my workaround is doing it the old fashioned way through CMD in windows using adb push.
Example:
Assuming you have all the stuff you want to transfer in a folder called stuff, adb is located in C:\adb, and your folder known as stuff is also in C:\adb:
C:\adb>adb push stuff /data/media/0
The above command starting from the ">" will transfer all files in the folder called stuff to the root of /sdcard. In the N4, /sdcard is symbolically linked to /data/media/0.
Of course you need USB debugging enabled for this to work...
Device Manager (Hopefully this helps)
In the start menu type device manager, in that window you should see android and or something similar at the top. You want to drop the menu down and right click what should say Google ADB Interface and delete it, make sure you check the confirmation box. After reboot your computer! Once booted plug your phone in a viola!!!
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Roktgr said:
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Click to expand...
Click to collapse
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
Click to expand...
Click to collapse
Hello,
"#1 is the phone doesn't do anything in USB debug mode." This is normal!
How I experienced the USB debugging option is that, if turned ON:
1. The Nexus does not appear in my Windows env
2. BUT when in recovery mode, I can use the "adb" commands
If USB debugging turned OFF:
1. Then I CAN see the Nexus in my Windows env
2. BUT I cannot use the "adb" commands in recovery mode.
So you definitely need to have the USB debugging option turned off if you want to see your nexus in Windows, IMO
---------- Post added at 04:16 PM ---------- Previous post was at 04:02 PM ----------
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Click to expand...
Click to collapse
I think you really have an issue with the drivers. I would install the Google USB drivers. Maybe a bit heavy but then you can be sure that drivers are fine:
http://developer.android.com/sdk/win-usb.html
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
I did remove the SM Bus Controller from device manager and then re-installed the LG device driver. It did not attempt to reinstall SM Bus drivers, but instead installed MTP drivers successfully. I had high hopes after that, but it's still not working. Sigh.
bgibson72 said:
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
Click to expand...
Click to collapse
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
elijah420 said:
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
Click to expand...
Click to collapse
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
bgibson72 said:
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
Click to expand...
Click to collapse
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
elijah420 said:
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
Click to expand...
Click to collapse
It's cool, thanks anyway. Just trying to simplify things. Don't ask why I thought the OEM's software was gonna solve that, lol.
Well, tbf, even though I don't use it (simply because I dislike vendor lock in - owncloud or a sftp session is mostly hardware agnostic.) I do understand the idea that one should expect the **** that come on the phone to work properly. It *should* be a selling point - 'our apps work for their stated purpose!'