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
Related
I'm trying to use my new Epic to test an application I made a while ago but I can't seem to get Eclipse or the Android Eclipse plugin to recognize my phone.
The android documentation says that I need to install the USB driver package from the list of available packages in the SDK and AVD manager, but there is no USB driver package. In addition, I am unable to even mount my EPic to my computer to do simple file transfers, regardless of whether I use the drivers that Windows downloads from Windows Update or if I use the official driver package from Samsung.com. Although I will get a drive to show up when I plug my phone in, it will be a light grey and attempting to access it leads to it timing out after a few minutes.
I've attempted this on 32-bit and 64-bit editions of Windows 7, and I do have USB debugging enabled. I'm probably missing something since this is my first Android phone, but I sure can't figure it out and I consider myself pretty proficient with this type of stuff
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Aridon said:
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Click to expand...
Click to collapse
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Roisen said:
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Click to expand...
Click to collapse
I downloaded the drivers from Samsung website but am still unsuccessful in mounting my sd card to my Windows 7 64bit pc. Anybody has found a solution??
i had to edit 70-android.rules to include the samsung drivers code 04e8
I fiddled for a couple of hours and it just started working. No idea what I did, so sorry I can't be of more help to other people with this problem.
i'm not sure what this eclipse thing is, but i was having problems connecting my phone to my computer.
but after doing a battery pull, it all started working again. sounds noobish, but hey, it worked!
An odd one....
I have one of the HD2 Android releases on my phone, and it's working fine EXCEPT....
USB tethering does not work.
Now here's the odd part.
1. I have two machines. Both running Win7/x64.
2. One loads the RNDIS driver and works fine. The other can't find the driver on Windows Update.
I have no clue what's going on, but the USB signature is VID_0bb4&PID_0FFe, which is valid for the HTC Sapphire.
And, like I said, the other machine -also running Win7 - finds it just fine.
Any ideas?
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
i'm running Windows 7 x64 and when i start usb tethering from android on HD2 there is Android Device driver missing in Device Manager, I've read that Windows 7 already have Remote NDIS support so no need for seperate driver download if you have Windows Mobile Device Center but it ain't working, the same problem as you had.
Luckely, your solution and this separate driver works, Windows 7 complains about unsigned driver but who cares, USB tethering is working
Thanks!
didn't work...
i attempted installing the driver OEM106.inf, but received an error once it was loaded on my pc:
"This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"
i was having similar problems as Genesis trying to tether my Android phone via USB to my pc and receiving a Remote NDIS driver problem (same as above). I successfully tethered my phone to my PC once (and only once), but after I woke the computer from sleep mode, my pc began giving me errors on the "Remote NDIS based Internet Sharing Device" stating that windows cannot load the drivers ("rndismpx.sys" & "usb8023x.sys"). I haven't been able to tether via USB since then.
Windows Update states the driver is up to date, and when I tried Genesis3's driver fix, it only gave me the same error.
Any ideas?
Running win7/x64 on a toshiba i3, and a HTC nexus 1 running android 2.2.2
The files referenced have somehow been damaged or destroyed. Find them from another machine and put them back, and the OEM file I posted will work.
Those two files have to be on your machine - the OEM file is the pointer to them, but the base-level drivers have to exist.
you may need the latest version of htc sync
i did all my flashing on an xp computer and when i got win7 i just could not get any drivers to work. i downloaded the latest version of htc sync and all the drivers loaded just fine. time to flash this thing again ive had the same rom for two weeks
This is what I was looking for, and it worked for me, thanks!
PISSA! Tried for a while to get usb tethering to work and this did it! Took a minute for windows to sort things out after the driver update but its working! THANK YOU!
DL DesireZ V3.4 final HD2 TMOUS
Hey guys..
This thread popped up first on google and im quite a noob so pls tell me how you include this driver in windows(win7 x64)
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
Worked like a charm, thanks! I just had to update driver with provided file and it started working. Thank you very much again! Bump may not be a bad idea, maybe few more users will solve their problems with this. HD2 isn't a native Android device, so it wasn't that strange that it didn't worked out-of-the-box even with Win7 RDNIS (or sth like that) native support.
raven_raven said:
Worked like a charm, thanks! I just had to update driver with provided file and it started working. Thank you very much again! Bump may not be a bad idea, maybe few more users will solve their problems with this. HD2 isn't a native Android device, so it wasn't that strange that it didn't worked out-of-the-box even with Win7 RDNIS (or sth like that) native support.
Click to expand...
Click to collapse
After I have Device Manager opened, what do I do next?
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
thaaaaaaaaanks.
I have been trying many drivers and tools. This one worked like a charm
I lOVE YOU!
Thanks so much man. you saved me from reverting back to windows mobile, i had about given up on usb teathering with android but you saved me. Im very greatfull.
Not a problem!
still not working
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
I tried this and others ( htc sync, intel android drvrs,) but no success. Any clue what's missing?
i have windows xp, sp3....android 2.3.7 htc wildfire.
oem.inf
Genesis3 said:
Answering my own question...
If you run into this, put this somewhere on your disk and point "Update Driver" at it.
It'll work.
Now why this was on the disk of ONE machine (which worked) and NOT the other (which did not), and why Windows Update wouldn't find it either (!!!) is unknown.
All I know is that this is the file that Windows 7 wanted, and didn't have on one of the computers - but did have on the other.
Click to expand...
Click to collapse
I would like to share my solution. I modified the oem.inf file in the oem.zip(above) ,by changing the manufacturer name and device id as given in the PC 's device manager(unknown device).
It should work for xp,seven,vista.
I just got my Gtab today and can already find things I just cant live with so im trying to prep for a new ROM when there are some stable ones out there.
I have downloaded everything from the CWM recovery and root threads but i cant seem to get a driver to work... I have tried section #2 multiple times over on both XP pro x86 & Win7 pro x64 but i end up with the same 3 unknown devices on both *neither have SDK*. When i try to install the unknown USB device with the drivers supplied in nvflash it cant find anything suitable *even pointing to sub-directories*. I downloaded the drivers mentioned in the rooting thread and installed those, I went back to the DM and tried every single directory in the newly unpacked location "C:\Program Files\Samsung\etc.." which had quite a few different ones but i havent gotten anywhere.
I remember this being almost identical to the problems i had trying to root my phone so I finally found linux directions and worked from my mac. Does anyone have a clue whats going on and how to get MS FAIL OS to work?
I guess im the only person having this problem... ohh joy another android that is going to be a pain in the as to root
on your computer, uninstall ALL the samsung drivers (for any previous samsung device/phone). Then connect the tab to your computer and let it search on its own. on your tab the usb debugging should be turned off.
I think the tab is designed to let windows recognize it as usb, but if you have any previous drivers they get into the way.
Well guys I've been trying for hours now, whenever I try to install the USB drivers in order to unlock my bootloader, when I plug in my Nexus it installs the MTP drivers on it's own, if I try to install the google drivers downloaded from ADB all I get is a message saying the best drivers for my device are already installed and it doesn't let me overwrite them.
If I go with the use disk option it doesn't let me choose the usb_drivers folder because it just wants to use a .inf file, whener I follow the instructions the toolkit dictates I read the dead end with the "The best drivers for your device are already installed"
I'm so angry right now.... Please help me.
Are you on a Windows XP operating system by any chance? There are major issues with MTP mounting on WinXP regardless of the service pack you're on. Some people claim they've gotten things working by updating WMP, via a Naked Driver and even by installing the Android SDK. Let me know if you are indeed on WinXP & I'll get you some links
Did you try following Wug's Nexus Root Toolkit to install the drivers? That helped me. I cannot post a link so look around for it.
I'm running Windows 7 64 bit, thanks guys, I just gave up and did it in my sister's laptop, it worked on the first damn attempt, maybe the drivers of my N10 were screwing something up, that's my best guess.
Glad you got that sorted--just for future reference, a common recommendation for people having driver issues with their Nexus devices is to simply go into Win Device Manager, uninstall all your current Nexus & ADB drivers and restart. Then plug your phone in via USB and let the auto installation do its thing. Usually this fixes all issues w conflicting device drivers
I am new on XDA, and I am not sure what is the most appropriate place for my question, so I am asking it here.
I tried to install Samsung drivers on a 64 bit Windows 7 SP1 box, but it always BSODs at the end of the procedure. After this happens, Windows 7 starts to fail, and I have to go back to a restore point, so I don't even know if something got installed. I tried a few different versions of the drivers, but always got the same problem. I tried with a couple of different downloads, one is a file named Samsung-Usb-Driver-v1.5.49.0.exe, and another is a zip archive called usb_drivers_GalaxyS_x64.zip, which I think had been extracted from Samsung Kies installation.
From Windows Properties, I can see an entry SAMSUNG_Android marked with an error, saying that the device drivers were not installed (code 28). There are similar entries for "CDC serial" and "Video controller".
I did a lot of googling, but didn't find anybody who had exactly the same problem.
I am not sure whether this is related to the 64 bit OS, or if there is a more specific version of the drivers I should use, and the Samsung site is not of much help. Any idea will be appreciated.
Hi
Thanks for writing to us at XDA Assist. Even though this seems more like a Windows issue than an Android issue I'm going to have your thread moved to the S3 Neo q&a section here:
Galaxy S3 Neo Q&A, Help & Troubleshooting
Hopefully someone with the same device as you can help you out with exactly which drivers you should be using for your phone. Please standby while we move your thread.
Good luck!
This is really weird. I tried to solve my problem by installing Samsung Kies. Installation goes fine, Kies starts, but when I attach the phone to USB Windows crashes with a BSOD. Unless I disable USB debugging, in which case nothing happens. Needless to say, "adb devices" lists nothing.
Ok, I finally managed to connect my device and run application on it from Android Studio, which was my main concern.
To do so, I installed the latest version of Samsung Kies3. When I connected the phone after the first installation, the PC crashed with a BSOD, and at next start the drivers for my phone were uninstalled. Reinstalling them from Device manager fixed all issues, now I can see the phone both from Kies and from Android Studio.
Maybe somebody will benefit from my experience