Please!
when I received my magic i foolishly just plugged it in. Now I can't load the USB driver that comes with the SDK! Everytim I uninstal the windows driver it simply reload it automatically without stopping to ask if I would like to point it to a diffrent driver.
If I update the driver and point it at the x86 driver it just says that it can't find a better driver than the one that is already loaded!
how do I stop win xp from automatically loading whatever drivers it feels when detecting new gear?
palexr said:
Please!
when I received my magic i foolishly just plugged it in. Now I can't load the USB driver that comes with the SDK! Everytim I uninstal the windows driver it simply reload it automatically without stopping to ask if I would like to point it to a diffrent driver.
If I update the driver and point it at the x86 driver it just says that it can't find a better driver than the one that is already loaded!
how do I stop win xp from automatically loading whatever drivers it feels when detecting new gear?
Click to expand...
Click to collapse
Do this
I have no idea in which section to write this, so General seams like the best choice.
I have a Galaxy Y testing device with a broken boot.img. I am trying to get Odin working in Windows 7 in order to flash a new boot.img to this device, but I can't get the Samsung USB drivers to work and my Windows knowledge is now that great as I mostly work on Linux computers, but no fastboot on Samsung devices.
There are two drivers listed in the Device Manager. The Regular Samsung USB drivers, and something called Samsung USB CDC. It's the CDC I seam to have issues with. It just shows an error message that states "The device could not start (Code: 10)". I have already talked to Samsungs online support, but there is not much support to find there. They know nothing about Windows or how to get anything working on it. And google's search engine, which usually is the best friend for something like this, did not come up with much either.
I should mention that I run Windows in VirtualBox. However, I already have HTC Sync Manager fully working with an older HTC device, so this is not a VBox issue. Also, Windows do find the device just fine, it just can't start one of the drivers.
I have tried installing Kies. I have also tried installing other separate driver versions. Nothing is working.
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
WooHooGuy said:
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
Click to expand...
Click to collapse
I love the idea of a multi driver for all devices, much like on my linux boxes, so thanks for that. However, I get the same issue and same error message. I will try to reinstall windows and see if that will work. It has been many many years since I ran windows as my daily OS, but I do remember that formatting was the best way of fixing issues with it. If this is still no go, I will try to put windows directly on my netbook to see if this could be a Virtual problem anyways, but I don't think so. USB stuff is working fine on the Virtual OSX.
Will report back later
EDIT:
Nothing is working. All I have installed, is the naked driver. When I plug-in my HTC Desire or HTC Wildfire S, the driver is working fine. But when I plug-in the Galaxy S3 or the Galaxy Y, I get the "The device cannot start (Code: 10)".
So HTC devices are working, but Samsung is not. The same problem I had with separate HTC and Samsung drivers.
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
-CALIBAN666- said:
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
Click to expand...
Click to collapse
Thanks, but I have tried that version, and the one newer (1.5.23). I did manage, efter some reinstalls, to get 1.5.18 (I think is was) to work on the real installation. So maybe my issue is with virtualbox, I just can't see what. I have disabled everything in linux that could block something, I have disabled firewall and such on the virtual windows, I have tried checking and changing perms on the linux device nodes, and tried running VB as root.
At least I got the Galaxy Y running again, but I don't like having unresolved issues so VB is going down
I would just like to share an error I found when turning on USB tethering on Windows 8 using a Samsung Galaxy S4 i9505.
Earlier, I was turning on USB Tethering for the first time. It worked fine for a few seconds while my computer was still in the process of installing the new drivers. The connection was all fine while it was running on the stock Microsoft Remote NDIS drivers.
But after it finished installing the Samsung NDIS drivers on my computer, USB Tethering suddenly stopped working and I couldn't find any local area network on my Network Connections folder.
I found out there was a problem with the drivers. I tried updating and it just said that the driver I'm using is the latest from Samsung.
If this happens to anyone else, go to Control Panel > Device Manager and look for the Samsung NDIS drivers. Right click then go to Properties > Drivers >and do a Driver rollback.
Using the stock Microsoft Remote NDIS driver seems to fix it.
I'm currently looking for a working driver from Samsung and if anyone has a link please post it. Thanks! :good:
New driver works
trikpat_A said:
I would just like to share an error I found when turning on USB tethering on Windows 8 using a Samsung Galaxy S4 i9505.
Earlier, I was turning on USB Tethering for the first time. It worked fine for a few seconds while my computer was still in the process of installing the new drivers. The connection was all fine while it was running on the stock Microsoft Remote NDIS drivers.
But after it finished installing the Samsung NDIS drivers on my computer, USB Tethering suddenly stopped working and I couldn't find any local area network on my Network Connections folder.
I found out there was a problem with the drivers. I tried updating and it just said that the driver I'm using is the latest from Samsung.
If this happens to anyone else, go to Control Panel > Device Manager and look for the Samsung NDIS drivers. Right click then go to Properties > Drivers >and do a Driver rollback.
Using the stock Microsoft Remote NDIS driver seems to fix it.
I'm currently looking for a working driver from Samsung and if anyone has a link please post it. Thanks! :good:
Click to expand...
Click to collapse
Hi Trikpat
The Samsung driver dated 14-08-2013 works
Windows 8 Pro 64 bit
BR
Flemmingk
Hey all!
Anyone got any idea what to do when MTP to a computer on the LG G6 does not work? Tried installing the drivers from LGs website and all Im getting is code 19 from the device manager on the device, and it wont show at all in windows...
Running windows 10
https://www.lifewire.com/g00/how-to...?i10c.referrer=https%3A%2F%2Fwww.google.se%2F
Got it working for me if anyone else comes across this issue
Natherul said:
Hey all!
Anyone got any idea what to do when MTP to a computer on the LG G6 does not work? Tried installing the drivers from LGs website and all Im getting is code 19 from the device manager on the device, and it wont show at all in windows...
Running windows 10
Click to expand...
Click to collapse
Enable usb debugging in the developer option.
That did nothing for me, but as I stated in my own reply I got it working now, it was a conflict with some registry values on my computer
Hey there,
i've the problem, that the oneplus USB driver didn't work on Windows 8.1.
Hast onyone an Idea what i can do?
It still looks Like this.. i've tried many versions...
Thank you.
Manually add the driver it should work
Install the proper USB driver pack for your computer! You can download it from here! I think this web have the guide for it.