LG G3 (D852) MTP Problem - G3 Q&A, Help & Troubleshooting

Okay so before anyone says this has been solved before it hasn't, I have scoured the internet left and right and I have not found any way to fix this problem. Also just as a pre FYI it's not just the LG G3, it's also happening with my work provided Samsung Galaxy S5 and my girlfriend's S7.
So here we go, no matter what I have tried or pulled off, I cannot get my new (old) laptop to recognize any device I plug into any of its 5 USB ports (3 USB 3.0, 2 USB 2.0, 1 USB 3.0 enabled with Super Charger), now as for the details, the laptop has windows 10 installed and to be more specific it's an msi gt70 0nc, so it's a higher end gaming laptop and I have tried everything and it just won't connect to any phone I plug into it.
And before anyone says if I've tried another laptop I have, to be specific I've plugged both phones into my lady's HP Envy with Windows 10 and both were recognized just fine.
If anyone is wondering here are the measures I've taken:
Installed LG United Mobile Driver (almost every version available)
Installed LG Mobile Driver (once again, every version available)
Installed LG PC Suite (Doesn't detect phone)
Tried switching phone between USB debugging and MTP PTP And Charge Only and every combination in between.
Have tried uninstalling and reinstalling Windows Media Player as it carries the MTP protocols.
Have tried installing the Media Feature Pack for windows 10 N and KN off of the Microsoft website
Have tried uninstalling the drivers manually and forcing an update on the drivers with no avail.
Have tried messing with the BIOS USB Settings on the laptop.
Disabled driver signature enforcement
Tried Safe Mode on both Laptop and Phones
Installed the Universal Google Driver
Installed ADB and fastboot (ADB doesn't detect the phone)
Installed KIES to try the Samsung (Doesn't detect phone)
Tried forcing generic MTP inf files
I'm honestly insanely frustrated and all I want is for this device to show up in my computer so I can install some roms and tinker. I've been trying all I could for the past 24 hours (Lost sleep) with no avail. Nothing seems to be wrong with the USB Ports as I have a Logitech unifying receiver plugged in for a mouse and it works, it just seems like this laptop doesn't like Android devices.
Going to device manager and forcing an update does nothing, the device sometimes shows up as "Unknown Device", sometimes shows up as "LGE Android Net MTP Device" and sometimes as "LGE Android Mtp Device", forcing the update yields the result "The driver installation file for this device is missing a necessary entry, This may be because the INF was written for Windows 95 or later. Contact your hardware vendor" This happens with both the LG and the Samsung. Any help would be appreciated. If anyone needs any more information or logs don't hesitate to ask.

Sure hope you find a solution and post it. I have EXACTLY the same issue. The last paragraph of your description is identical to the error message I am getting.
---------- Post added at 10:41 PM ---------- Previous post was at 09:52 PM ----------
Wow. All I did was uninstall and reinstall Media Player 11 and it started working. No driver error and computer detects phone now.

Related

[Q] Can't connect to Kies through USB tried several things...

OK, did a search in this forum for "Found New Hardware SAMSUNG Mobile MTP Device" as well as "connect to Kies USB XP" and other variations of these. I believe I have tried all suggestions that I have found, but advice would be appreciated
Firstly, I have a Dell mini 10 running xp that my E4GT connects to fine through Kies. My E4GT is running StarburstROM 1.9.5 with LoStKernel 1.0.0.8+EXP
My old HP pavilion, running the same version of XP however just says over and over "Found New Hardware SAMSUNG Mobile MTP Device" and the new hardware sound plays about every 5 seconds.
After a fresh install of the most recent version of Kies, I tried
Different USB ports
Different cables
Making sure no files have extensions longer than 15 characters. (or was it 16...?)
Recovering the drivers through Kies
Downloading and reinstalling/reapplying the USB drivers found in various links here on XDA
Uninstalling and reinstalling Kies
Going to Device Manager, right clicking on the yellow triangle of the samsung mtp device and directing the computer to install drivers from there
Still I get an endless loop of Found new hardware. Unplugging results in "a problem occurred during hardware installation...etc" Any thoughts I haven't tried yet?
Make sure usb debugging is not checked in settings/development/applications.
what? i thought usb debugging had to be checked?
and either way it shouldn't matter if the phone is in download mode, correct? maybe i am wrong. i would assume that since he got it to work on a different computer it is not a setting on the phone and a problem with the computer reading the device's drivers.
Yeah, USB debugging is off. Tried it with it on just for giggles, but no joy. I may just have to accept that it won't connect to that compy. Can't get it to connect to Kies or even connect just for file transfer. Had same trouble with my OG epic. Maybe something about the original driver install from back then....
I'll try manually removing all drivers associated with the device and see if a reinstall from scratch (again) will work. I'll also check the .net version again, but I think I already did that. Thanks all!

"Hardware ID doesn't match" error when plugging phone in

Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
You may not want to try this either but try a system restore
Sent from my SPH-L710...if some one helps you press the thanks button
Volknochi said:
Okay, this is the second time this error has popped up and it's starting to get on my nerves. Anytime I plug my phone into ANY USB port, and this is counting both 2.0 and 3.0 ports, I get the error bubble: Hardware ID Missing. Windows cannot identify the device plugged into the SAMSUNG Mobile USB Composite Device." Honestly, this is beyond irritating.
For one, I am not going to reinstall Windows 7. That's too much hassle for this. Second, ever since someone plugged their Droid into my USB cable so they could charge up their phone, this message started appearing. I tried to reinstall drivers (Samsung driver exe said it couldn't install), uninstall, disable, etc etc, but finally managed to get the damn computer to read it when I stuck it in the 3.0 USB port. Now, just 10 minutes ago, I plug the phone in, I get that error, on a 3.0 USB port.
So, now I have no idea what is going on, nor how to fix it. I've tried searching, but there are no answers. Or, the possible "solutions" don't even work even remotely close.
I could really use some help on this. And, again, please do not mention "Reinstall Windows". That's just too much of a hassle and I'm not going to do that.
Click to expand...
Click to collapse
I had the same issue what ended up fixing it for me was watching when I plugged the phone in after a clean driver install and stopping Windows from downloading and installing an updated driver. Dont know if its the same for you but that fixed it for me. I was really frustrated by it and found no help either.
probably an easy fix
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
I won't do a system restore, that won't do anything. Not to mention it would erase some programs that were installed (not related to phone). So, not doing that. Also, my computer will not automatically update any drivers or any thing else, as I have it set to manual mode.
And, I do not have Kies installed. It never worked for me properly, when it came to driver installation. I've done the "go into device manager" bit many times before, it still likes to play the "Hardware ID doesn't match" card. Drivers won't install either. I don't know what it is, but damn this is the most stubborn thing I've ever encountered.
i've post this in other forums today. what i do to get it working is i toggle USB debugging and try it out, then start toggling the ptp and mtp until it works. the combo that works for me is turn on debug, plug in computer, unplug, turn off debug, plug in. if it doesnt work then i toggle back and forth MTP and PTP. 5 tries at most, for me. Also, i did a nandroid back to my oem ICS that was 2 weeks old and just rooted. the problem is worse there. i'm using freegsmr6 with trinity kernel on Tmo. hope it helps.
Ditto
Yeah that whole "Hardware ID missing" was an irritating situation. This is what I recommend as far as making it work.
1. Plug in.
2. When you get the error message, I think its because of a conflict with the ADB interface. Go to Settings, Developer Options, and check off USB Debugging.
3. Plug in once again and it should work. If not, try toggling between Camera and MTP.
I have Windows 7 Ultimate and it works fine for me
I always get that error as well with my SGS 3. I have to reinstall Kies everytime it does that which is annoying.. ANyone has a permanent solution about this?
Fix for me was...
1-plug in phone. Get the hardware ID message. Leave phone plugged in.
2- open device manager. Click on. Android Phone and Uninstall Samsung Android ADB Interface. Also check the "delete software driver" when the dialog box shows.
3-still in device manager. Scroll down to Universal Serial Bus Controllers. Uninstall Samsung Mobile USB Composite Device.
4-unplug phone.
5-reboot pc.
6-install SAMSUNG USB drivers from their site or from here
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
7-reboot or not. Plug in phone.
This worked for me and no issues for the last 6 days. YMMV..
this works!
stevounit said:
yeah that whole "hardware id missing" was an irritating situation. This is what i recommend as far as making it work.
1. Plug in.
2. When you get the error message, i think its because of a conflict with the adb interface. Go to settings, developer options, and check off usb debugging.
3. Plug in once again and it should work. If not, try toggling between camera and mtp.
I have windows 7 ultimate and it works fine for me :d
Click to expand...
Click to collapse
But why this problem now out of nowhere when everything worked fine before.
Sent from my SPH-L710 using xda app-developers app
Hardware ID missing - SOLVED!!
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
UPDATE!! (Oct.11.2012)
After a few Kies updates and going through various ROM's:
- the procedure listed above works 100% but a few steps are just not needed (redundant) - see bellow
- the problem is mostly caused by Windows "forcefully" trying to install its own drivers, rather than allowing Samsung's suggested.
- Samsung's fault is providing "updated" drivers that don't always work (hence, use the suggested 1.4.6.0 drivers)
- Following EVERY Kies update, DISCONNECT from internet before plugging your phone (otherwise you'll have to go through this, AGAIN).
Some suggested here that plugging the phone into a different USB port (without disconnecting from internet) would be the culprit - which happens to be true, but as a mere effect, not the cause: every time an unknown device is plugged into a different USB port, Windows is trying to download/install the appropriate drivers if it doesn't recognize the hardware - and there you are again.
So, the simplified procedure becomes:
1. Not needed - leave Kies installed, as is - no harm at all
2. N/A
3. YES
4. Not (always) required
5. MUST
6. MUST
7. MUST
8. Yes
Furthermore, if still interested in connecting your I747(M) as UMS (USB mass storage) the solution presented here works. I tested it myself - read my comment on this post for the very few existing hiccups.
- while installing the USB mass storage device drivers you don't have to disconnect from the internet
Install Drivers
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
For someone experiencing the "hardware ID missing" error, just reinstalling the drivers won't do anything. Like many others, I've been banging my head trying to solve this for quite some time; the suggested steps are truly a compilation of successful ideas and trials mingled with tons of frustration, coming from my own experience as well as from many different people and forums.
If, on the other hand, you had a different type of connectivity issues - without this error, then, yes, reinstalling the drivers is Samsung's recommendation.
billard412 said:
definitely don't need to reinstall windows or do a restore. But just to be sure, you don't have kies installed right? Seems to cause problems.if there's no kies installed, go into the device manager and find your phone whatever it's listed as right click and uninstall. Check the little box that says, "delete the driver software for this device". do this for any devices relating to yours. Including the stuff under modems,ports,USB controllers.and tick that box that delete driver software for this device every time you uninstall something. Now, not saying it's necessary but wouldnt hurt, reboot the pc. Then with your phone unplugged, reinstall the Samsung drivers for the phone. Now to make sure windows doesn't DL its own drivers,disconnect from the internet and plug the phone back in. Should be all good.
Click to expand...
Click to collapse
Just wanted to say thank you. Did this and the last 2 days, works everytime. I made sure that after the first time I plugged the phone in after doing all this, and the screen pops up asking what I wanted to do, made sure to check the box for "do this everytime" and then choose the view folder option or whatever that is.
Thank you again,
Whiteice
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thank you so much for this. This solution worked for me.
nacos said:
1. Uninstall any previous instance of Kies/USB driver
2. Download the latest Kies, specific to your S3.
3. Download Samsung USB drivers 1.4.6.0 (I've tried newer versions but they all failed)
4. REBOOT
5. Disconnect from internet (VERY IMPORTANT!!! - forcing Windows to install local drivers ONLY)
6. With the phone disconnected, install Kies + USB drivers downloaded in steps 2,3
7. Connect the phone and let Windows install the drivers.
8. Reestablish the internet connection.
I've done just that, I've connected my S3 to the PC several times, I've also rebooted twice and I've never seen that stupid message again - while of course everything works as expected.
:good::good:4 days later, several times rebooted (phone and PC), several connections with Kies and I have NEVER seen that error again - it works!!
Click to expand...
Click to collapse
Thanks for this i will try it tomorrow as still new to these tabs.
For moment i change to camera PTP and it pops up, so at least i can use it for now.
Will let you know how i get on.
Best wishes :good:
adamspud said:
One thing I have tried which might help others - I had the Android Developers toolkit installed on my machine, which I've removed and I also removed the HTC Sync software which was for my old desire.
Rebooted, installed the SG Toolkit (can't remember which post I found it in) and then chose option one after selecting firmware to install drivers.
I cancelled the "Windows Updates" bit of the driver detection and it found the first item, and had "item disconnected" for the remaining three.
Unplugged and plugged back in and voila it works.
This worked for approx 5 mins and then stopped, however I did all the above with debugging on, debugging is now off and all seems well (touch wood). However looking at putting on a different kernal to expose storage as mass storage and also get around cifs issues.
Hope this helps someone.
Click to expand...
Click to collapse
The Android Developers toolkit DOES install the USB drivers 1.4.6.0 - which seems to be the ONLY one that works, BUT the rest of the steps suggested in my previous post are needed in order to get rid of the problem - otherwise the fix is just temporary.
Re-loading OS drivers corrected issue.
tyler1037 said:
Have you tried just installing the drivers directly from Samsung? That is all I did when I had problems and it worked.
Click to expand...
Click to collapse
I removed the updates to Kies on my Note and uninstalled the Kies update on the PC which is what started this issue of the OS not recognizing the device and then a fresh driver load for my phone from the Samsung site. Worked Perfectly, Thanks!
Cowoholy

S4 not recognized when plugged in via USB

The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
rjsmer said:
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
Click to expand...
Click to collapse
As stated, I have tried to use two other USB cables aside from just the one that came in the package.
Since all cables work on the laptop, but not this computer, I have pretty much singled it out to be a windows or a driver issue. :\
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
scott14719 said:
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
Click to expand...
Click to collapse
PC is i7 920, 12GB DDR3, Intel x58
Laptop is i5 2430M, 6GB DDR3, Sandy Bridge
Both are Win7 Pro, neither have Kies (I always just downloaded the drivers themselves) but I'm downloading it now to give it a try. As of now, nothing recognizes the phone on PC.
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Shuurei said:
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Click to expand...
Click to collapse
Samsung Kies isn't yet compatible with the sgh-m919. Samsung rep told me soon last night
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
SBERG117 said:
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
Click to expand...
Click to collapse
Enabling dev options and USB debugging was the first thing I did once I turned on the phone. Tried it both with and without, still not recognized either way. Still recognized on laptop.
I've also reinstalled windows altogether, since that fixed my issue last time around, but it's no good this time still. Clean install, formatted. No good. Previous steps from first post also taken, still no good. Tried the PDAnet method as well, no good.
At this point I am wondering if it might be an x58 issue, which would really suck, but it's the only thing I can think of given all the steps I have taken.
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
x58 issue
luckyduck69 said:
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
Click to expand...
Click to collapse
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Confirmed x58 and S4/general USB connectivity issues
Shuurei said:
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Click to expand...
Click to collapse
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Shuurei said:
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Click to expand...
Click to collapse
Here's my craziness.
USB connection was working yesterday. Today, it is not.
I have uninstalled/reinstalled the Samsung Windows drivers/Kies
I have even adjusted my southbridge voltage to 1.2V in my BIOS
Still, no joy.
Curiously, when I boot the phone into download/ODIN mode and connect it, ODIN recognizes the connection. Reboot back into normal mode, and no USB connection is recognized. It is not showing up in my Device Manager as an unrecognized device. It just doesn't know it is there (unless phone is in download mode).
UPDATE: Solved. I had installed this ROM (http://forum.xda-developers.com/showthread.php?t=2261013). Reading back over the thread, it provided instructions for re-enabling the USB recognition of the phone. Had to re-enable the developer options and reset USB debugging. Makes sense now.
HI
I'm facing this issue today, I've tried two different laptops, both have Windows 7 x64 installed. I've tried every USB port on the two machines, I've tried with three different cables, I've downloaded and installed every USB driver there is. no use!
I'm out of options here and I can't think where to look further.
any help please?
shuurei said:
the device acts as if it is being charged.
Steps i have taken so far:
-uninstalled t-mo samsung mobile drivers and reinstalled
-deleted (uninstalled) all recognized usb devices via usb deview
-tried to connect without samsung drivers installed and all usb devices uninstalled
-tried to connect with samsung drivers installed and all usb devices uninstalled
-tried to connect without samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on samsung's site (1.5.14.0) and with the one found here on xda from 25apr2013 (1.5.23.0)
-tried to connect using different usb ports
-tried to connect using a different usb port on a different usb controller altogether
the kicker:
Device is recognized instantly... On my laptop.
This means:
-it is not the usb cable i am using (even though i have tried 3 different cables altogether regardless, including the one that came with the phone)
-it is not the device itself
possible: Windows issue? Last time this happened was long ago when i had gotten a mytouch 3g slide. I eventually just reinstalled windows since i had been meaning to then. I don't want to do it now though because i have too many things installed on here to start a fresh install... But i suppose if nothing else works, that's what i'll have to do.
Before that though, i would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
很想帮你啊 可是英文水平比较拙计
ok so now I'm guessing it is not windows, I tried on another machine with Windows Vista and got the same error.
any thoughts, anyone?
Did a factory reset for the phone
no it works!
don't know why
I just picked up this phone a couple days ago and last night tried to get the USB to work with no luck. I've tried everything I can think of. It does work in PTP mode but not MTP mode. I was able to use odin to on it though, so I was able to root it.
I've tried both in linux and on windows xp. I've never had an issue with any phone on linux and have installed/removed drivers numerous times on XP.
Tried 3 different cables, Factory reset with and without USB installed, tried pretty much everything I could find while googling similar problems (removing old registry entries, installed media player, etc)
I have adb installed on my linux box and even with debugging enabled I can't even get adb to connect to the phone.
Definitely something strange going on. Maybe I'll switch to cm10.1 to see if that makes a difference
I cant get my computer (windows 7) to connect with the phone when the phone is on, and was hoping some one might have found a fix.
This might fix it...
Shuurei said:
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
Here's a link with a list of things to try what you may not have tried to fix your problems.
A small number of devices I have worked on have a weird thing, that the first time I plug the cable into the computer, it connects but won't show up on the screen. unplugging the USB cable from the machine for maybe 3 seconds, and reinserting makes the connection work... go figure! :>)
Aloha and Good Luck!
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335

*Solved* LG G3 No longer connects to PC via MTP/PTP - Only Charge-only

Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Edit: *SOLVED*
Ok so turns out the issue is, and this is just my case, my motherboard has various utilities, one of which is a USB 3.0 boost option.
When I did an upgrade to Windows 10, it somehow screwed up various programs on my PC including registry etc.
I reinstalled the particular utility (I was actually trying to fix my graphics clock etc so happy coincidence) which also re-installs the USB 3.0 Boost software which in turn has fixed my USB Ports.
So if you have a custom built PC (my Motherboard being a Rampage 4 Formula). Check the Mobo Utilities/Drivers for any conflicts.
I have the exact same problem, and I can't seem to find a solution for months now. It's really annoying and depressing
nicholsonr said:
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Click to expand...
Click to collapse
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
ludoke said:
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Using the drivers on that page you have advised gives the following.
Device Manager shows a Warning on it in USB controllers as "LGE Mobile USB Composite Device". It automatically "malfunctions" according to Windows 10 and I can't change the connection interface on the phone.
Going into the properties on that device in Device Manager lists the following;
This device cannot start. (Code 10)
A device which does not exist was specified.
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
Click to expand...
Click to collapse
This didn't work. Already tried
Fixed my problem
I've had the same issue with my LG G3 in being unable to connect the device to my laptop. I'm not sure if the cause was a phone software update or the upgrade from Windows 8.1 to Windows 10. Either way, I searched and fixed it tonight by installing updated drivers. Hope this helps others as well.
Hmmm, I cannot post the link! technobuzz dot net lg g3 drivers
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!

Huawei W1 no connection with pc

I have no idea what I do wrong, but this is what I tried:
I enabled adb mode on my Chinese watch
The watch is in fastboot mode
I installed all drivers, pdanet didn't work (no usb connected)
Once I put my cable in my laptop and it said: USB error, try again later or something like that?
no adb response in the commands. just blank... in the devices list, there is no sign of my watch...
It charges normally. I could really use your help
Somehow I found the chinese wear OS so I can use it. at least that is something. Is there any way to get in in English or Dutch without adb?
My other laptop seems to see a 'unknown usb device'. no adb device found...
I have no idea... maybe it's due to the unofficial cable?
I bought an expensive cable, the original, but no laptop can see the watch (windows 10 and windows 7)
The old cable is some sort of ok with the windows 7. I get an error 43 in devicemanagement.
Please help... I have no idea what I can do now...
https://forum.xda-developers.com/showpost.php?p=73472794&postcount=15
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71653349&postcount=12
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
i am also bugged with this.
the win7-pc says unknown usb device detected. i turned dev mode and adb on.
then i tried to manually install the driver from the android sdk. when i try to select the driver windows says there were no driver found (but the driver is there) and i should make sure that the driver is written for x64-systems. WTF?
and even the watch does not charge wenn via usb 2.0 or 3.0 connected - but its connected cause of the message from the pc.
in the device manager the watch is listed as unknown device.
that's exactly my problem...
I have done everything. I'll try to connect it to my linux pc, I got an old laptop with ubuntu or something like that (haven't used it in ages)
maybe that will do the trick. I installed everything manually. my win10 can see an unknown device as well... but that's about it...
maybe dev mode is not working on some watches even when its enabled. or it has something to do with the 2.0 Version auf AW and it affects not every watch.
Its funny. I've been trying to get my HW1 watch to connect to my PC for a year now. Have tried numerous different cables and the original that came with my watch didn't work. Different PCs haven't worked either. Unless I'm that unlucky with all these OEM cables or the ADB debugging toggle really doesn't work for USB connections. It works just fine for bluetooth and wifi, neither of which allow you to unlock the bootloader. Guess I've got to wait for the next update manually and try again.

Categories

Resources