Everytime i tried to use USB Tethering with my Xperia U on my Windows 8.1 (Bing's single language Edition [Genuine Licence]) have always lags or even freeze the taskbar and some other tool settings on my operating system. After some testing and googling a little bit i found a solution for this Microsoft Issue: Update your NDIS 5 Driver to NDIS 6.x.
Verify if your device is using RNDIS 5 driver (1):
Open Device Manager from Control Panel and expand “Network Adapters.”
Plug in your device and enable USB Tethering so that the device is detected as Remote NDIS based device.
This should now create a Network Adapter named as “ [Your Device Name] Remote NDIS based [internet Sharing/network] Device.”
Right-click the Adapter and select Properties.
Select the Driver tab and then click Driver Details.
You can see the driver files if the files are named usb8023x.sys and rndismpx.sys you are using RNDIS 5 Driver.
Updating your driver:
Option 1: Update your driver NDIS driver manually by selecting the driver's list option on windows wizard driver's update. Unselect show all compatible hardware option, you will get a Microsoft's driver list. You should seek for a RNDIS 6 USB device and click next. This should work on 32bits or 64bits edition.
Option 2 (64 bits only)(2): Just Download and update your NDIS driver from the attachment below. On Driver's Wizard installation must go through selecting the driver from a list.
Sources:
http://support.microsoft.com/kb/2923775 (1)
http://www.driverscape.com/download/remote-ndis-compatible-device (2)
https://msdn.microsoft.com/en-us/library/windows/hardware/dn449742%28v=vs.85%29.aspx. Microsoft says NDIS 6.4 is included on Windows 8.1, don't know why windows chooses RNDIS 5 over RNDIS 6 on my laptop.
Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards
MHP2013 said:
Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards
Click to expand...
Click to collapse
Try this before installing the NDIS 6 driver:
http://www.tomshardware.com/faq/id-2165451/dont-windows-windows-automatically-download-device-drivers-icons.html
If above didn't work try to disable driver signature verification:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
Perfect, Thanks for this fix! Didn't need the driver as RNDIS6 driver is already included in Windows 8.1
NDIS Compatible works without huge driver lockups, but RNDIS6 USB Adapter also works like a charm. (Nexus 5)
Facing the same problem, here.
Tried both options, still facing the same problem..
Any ideas?
I am having the same issue in Windows 10 64-Bit.
Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.
Ano59 said:
Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.
Click to expand...
Click to collapse
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?
DubleJayJ said:
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?
Click to expand...
Click to collapse
As OP said, manually select the proper driver.
Windows 10 best solution: rename the RNDIS5 .inf file
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Something is not logical in this tutorial :
The content of the inf file in the attachment is rndiscmp.inf; but this file is already in Win8.1 system (C:\Windows\Inf). Hash are similar
This could explain why windows refuses to install it again and says "the last drivers is already installed"
Renaming extension of wceisvista.inf doesn't work for me in Win 8.1
Maybe you could tell us the name of driver files when using RNDIS 6 Driver ...
This thread is also important for resolving playability issues with the game XCOM 2, so thank you very much for the fix to a problem completely unrelated to Android You guys are awesome!
Thanks, worked for my Galaxy S6.
You can use one of the below drivers from that list. One of them may work, try them all:
USB RNDIS Adapter
USB RNDIS6 Adapter
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device > this was the one that worked for me
inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank You :good:
Thx! Worked!! Windows 10 64 bit.
Hi guys, i get some issues here where it looks like i have only NDIS 5 on my windows 10.
I tried manually select driver, but i can only see this one : Remote NDIS based Internet Sharing Device
i tried inkaine's method, usb8023x.sys is still there but rndismpx.sys is missing. So i think i'm still using this annoying NDIS 5.
I don't understand why it's so hard to update this driver.. :silly:
inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank you so much. This issue has been bothering me for years and your solution along with OP's solution helped me. Thanks
Hey ive been having this issue for a while now and im using a htc one m8 to tether with but for me it wont let me manually update the drivers or modify the wceisvista.inf im using windows 10 pro as well.
Windows 10 fix - Worked for me
Hello all,
None of the steps worked for me, however i followed one more set on steps that i found on the net (unable to post links yet )
anyways, the steps are
Open Device Manager (right click on Computer > Manage > on the left side, under System Tools choose Device Manager)
Choose the problematic device in Network Adapters (for me it's called HTC Remote NDIS based device)
Right click on it and choose Update Driver Software...
Click Browse my computer for driver software
Click Let me pick from a list of device drivers
Uncheck the box Show compatible hardware
For the manufacturer, choose Microsoft Corporation
Now you will have two options:
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device
I chose the second one and it solved the problem, but if it doesn't work you could try the other one. In my case, the driver that was being used was neither of these, but a special driver from Android SDK ADT bundle.
Pick one and click Next.
If a dialog comes up, confirm by clicking Yes.
Wait a few seconds for the connection to restart. If it doesn't work, try disabling and reenabling USB tethering on the phone, or reconnect the USB cable.
PS: Microsoft Corporation or Microsoft Inc. or Microsoft might be present in manufacturer. search among the three
Related
This must have been covered before but search does not seem to be working for me here.
I want to access the mem card in my Fuze (stock ROM) on my work PC but it needs to load a driver for the new USB device it detects. I do NOT want to install ActiveSync on the machine, only the driver that will allow the USB connection to work in Disk Drive mode.
Anyone know what file and where I could find it would allow this connection to work?
Installing applications is prohibited by company policy and installing ActiveSync would be detected. Installing a USB driver would not be.
Anyone?
the_nite_owl said:
This must have been covered before but search does not seem to be working for me here.
I want to access the mem card in my Fuze (stock ROM) on my work PC but it needs to load a driver for the new USB device it detects. I do NOT want to install ActiveSync on the machine, only the driver that will allow the USB connection to work in Disk Drive mode.
Anyone know what file and where I could find it would allow this connection to work?
Installing applications is prohibited by company policy and installing ActiveSync would be detected. Installing a USB driver would not be.
Anyone?
Click to expand...
Click to collapse
What OS are you using? Windows 2000 and definitely XP and Vista are plug and play. I'm using XP and the driver is here:
c:\Windows\system32\drivers\USBSTOR.SYS
If that driver isn't on your system, have you tried using the "Found New Hardware" wizard to connect to microsoft to automatically download the driver for you?
LBchinksTA said:
What OS are you using? Windows 2000 and definitely XP and Vista are plug and play. I'm using XP and the driver is here:
c:\Windows\system32\drivers\USBSTOR.SYS
If that driver isn't on your system, have you tried using the "Found New Hardware" wizard to connect to microsoft to automatically download the driver for you?
Click to expand...
Click to collapse
XP. The driver is not found by the wizard. I have had this on other systems before.
It is installed during the ActiveSync install. If you uninstall ActiveSync the driver is left behind and will still function but corporate policy has gotten strict on unapproved installs and traces are always left behind even after uninstall.
I will look on my home device for the file and see if I can move it to my work PC and get it working.
Thanks.
I recently crashed my vista hard drive and decided to give windows 7 a try, its working wonders right now. The only problem is that I'm trying to put Nandroid back up on my computer again. I am at the step of trying to get the fastboot loader. It worked on Vista, but now it is saying that the "Driver is not intended for this platform." Is that due to windows 7? Is there a work around for this? Any help would be amazing, thanks.
I used Fastboot on Win7 7100 build yesterday, and it worked fine. Did you set everything up according to this post:
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
This is all that I did, and everything worked flawlessly. Good luck.
hmm..yeah, i did do everything according to the tutorial exactly, do you have email, aim, gmail, etc? could you help me?
use the newest driver in this SDK..
http://developer.android.com/sdk/1.5_r1/index.html
If you dont see the ADB Device or whatever its called in the device manager you need to delete a generic volume and scan for hardware changes.... HTC talks about it here. I had to do it also...
http://www.htc.com/www/support/android/adp.html
Troubleshooting
fastboot.exe (on Windows) doesn't detect the ADP device properly
In some cases, Windows detects the ADP1 bootloader as a USB mass storage device, preventing fastboot.exe from accessing it. To resolve the issue, you can dissociate the USB Mass Storage driver from your ADP1 on your Windows machine and install the proper driver instead, as described in the steps below:
1. Boot the device into fastboot mode, as described above, and connect the device to your machine over USB.
2. Navigate to Start > Control Panel > System > Hardware > Device Manager > Universal Serial Bus Controllers. Observe that the ADP device is listed as a USB Mass Storage Device.
3. Right-click USB Mass Storage Device and select Uninstall. Windows then prompts you with a "New Hardware Found Wizard" message. If Windows doesn't prompt you, you can manually re-detect devices by selecting Action > Scan for hardware changes.
4. Install the USB driver included in the Android SDK, as described in Setting up a Device for Development on the Android Developers site.
thanks southsko, i'll try this and let you guys know how it works.
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
i had the same problem earlier tonight, i figured since i was running win7 i might as well try using the virtual xp out. I started the VM up and the attached the phone using the drop downs and it worked flawlessly.
yup .. it's working fine for me too.. if you are using 64 bit version ... u need to use the 64 bit usb driver too... u can get it here
http://forum.xda-developers.com/showthread.php?t=446274
Also you may have trouble installing it in Windows 7 unless you turn off driver signing at boot menu. Hit F8 and select no driver signing and you should be able to install it no problem... u will also have to disable driver signing each time you plan on using adb/fastbboot
foxlin said:
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
Click to expand...
Click to collapse
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
trmacdonal said:
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
Click to expand...
Click to collapse
I am in bootloader mode, and I am an admin. It didn't give me the option to install it anyways. That is interesting. I am currently still using the windows 7 beta. I have tried manually selecting the specific driver files. It is still not working, any other ideas?
I finally got it! thanks everyone. The solution was instead of having it search through the files, there is actually an option below it to pick the driver from a list, the list wasnt the right one originally, then i manually changed the directory and it worked. Thanks for the help everyone!
billc.cn said:
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
Click to expand...
Click to collapse
How come when I installed this on Beta I got the message that I could not install a non-digitally signed driver? I was not able to install it myself until I disabled it at boot... maybe the 32 bit version is signed.
Has anyone else using XP had any issues installing the USB Driver for the Magic? I've tried every possible method to get it to work and it just will not install. A method that appears to work for some is in this link-
http://www.mail-archive.com/[email protected]/msg09692.html
Although this did not work for me. There was also a suggestion of copying the inf file and renaming certain strings by one digit. Any suggestions?
I used the latest SDK with the included driver. Set the environment paths. Nobody has any other suggestions?
renaming the inf file solve the prob for me.
radonsg said:
renaming the inf file solve the prob for me.
Click to expand...
Click to collapse
What did you rename it to? I renamed it to android_usb_Magic.inf like the linked post said.
Hi Gimpeh
This worked perfectly for me. The issue was once it installed the Windows drivers there was no way back. However, follow this
So you plugged your Android phone into your Windows machine having forgotten to switch on USB debugging…
Menu > Settings > Applications > Development > USB debugging
Then Windows detected your device as a USB-Mass storage device and won’t change the settings, regardless of how many times you uninstalled the device. Thread on it here.
This solution worked for me and didn’t require editing the registry settings (I don’t know if the reboot is unnecessary).
(1) Plugin phone
(2) Uninstall any drivers that mention “HTC Android Mobile USB Device”
(3) Unplug phone and restart
(4) Install and run USBDeview
http://www.nirsoft.net/utils/usb_devices_view.html
(5) Using USBDeview find the Android device (for some reason Windows hides uninstalled drivers instead of deleting them), right click on it and uninstall.
(6) Follow the official instructions to the letter this time.
http://developer.android.com/guide/developing/device.html
Click to expand...
Click to collapse
http://blog.zedray.com/2009/06/16/when-adb-won’t-detect-your-android-phone…/
Good luck!
This is pretty close to the instructions I followed earlier. No resolution. All HTC device drivers have been removed. Although there is a composite USB device installed (not labeled HTC). I know sometimes if windows does not recognize a device it will show it as a composite.
Install HTC Hotsync - http://www.htc.com/sea/SupportViewNews.aspx?dl_id=573&news_id=169
Have your phone plugged in first then install the app. You don't need the additional drivers it list. Just the Hotsync program.
That did the trick for me.
edit the inf file under the x86 folder inside the usb driver.
replace the vid_0bb4&pid_0c02 with vid_0bb4&pid_0c03
cos somehow my htc is recongnise as vid_0bb4&pid_0c03 instead of vid_0bb4&pid_0c02.
Hotsync didn't work and neither did replacing the string from 02 to 03. I got it to recognize at work on a Vista machine but since then it will not recognize on my home XP or any other Vista machine. When I select Have Disk and select the INF file it says something to the effect of There is no driver information for this device.
Additional Note: Although the device was recognized on that one vista machine, it would not recognize when it was in HBOOT mode.
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
radonsg said:
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
Click to expand...
Click to collapse
CTRL+F Put in that key and found nothing.
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Cheesebaron said:
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Click to expand...
Click to collapse
How would you go about flashing the recovery.img in Ubuntu. I didn't see any drivers for linux.
Driver
http://developer.android.com/sdk/1.5_r2/index.html
Additional work for linux(add rules)
http://developer.android.com/guide/developing/device.html
I finally figured the damn thing out. For some reason windows recognized the ION as a Video device and installed it as such. I figured it out after I got irritated and just uninstalled everything that wasen't plugged in.
woa.
TT is strange. Which version of windows? vista or xp?
Its XP Home on a HP Mini. I'm glad I finally have it figured out. I've probably spent 20 hours on this issue alone. I even went to Ubuntu since Windows was being...well windows.
I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?
Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim
Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?
More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!
Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.
Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.
I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.
One thing I forgot. Do not unplug your device between uninstall and hardware scanning.
AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim
whenever I try and install the samsung usb drivers for my S3 the installer always fails with this message: "The MSS installation for SAMSUNG USB Driver for Mobile Phones V1.4.6.0 has failed."
I had the universal naked drivers installed on this PC before for my tbolt and transformer prime, but it wasn't compatible with the S3 yet. There is an updated universal naked drivers that supports the S3, but when I try and back up my IMEI and put the phone into RMNET+DM+MODEM mode, the naked drivers don't recognize my device. in the regular MTP+ADB the drivers work fine.
so I imagine I need the samsung drivers to install for this to work. does anyone have any ideas how I could get the samsung usb drivers to install properly? I've also tried the V1.5.5.0 version as well and the installer fails as well. I've removed the universal naked drivers and tried to install without it and I still get the error. same thing in windows safemode. I'm running Windows 7 Enterprise 64 bit.
has anyone else had trouble with this? and any idea how to get the installer to work? thanks
Lots of people have been having this issue. I'm having it on XP at the moment... until now.
Per another thread I read here (for the Dell Streak, thread here: http://forum.xda-developers.com/showthread.php?t=1291293) you can force Windows to use the generic driver instead of the Samsung one.
Basically, I edited a copy of the INF to match my device info, then entered the info into the [Generic] area of the INF. I then told Windows to allow me to manually select the driver, and pointed it to this INF file. Voila... I now have generic driver support for MTP in XP SP3. I imagine the same thing might work with other versions of Windows, since I'm not really using any non-Windows drivers.
jackmei2 said:
whenever I try and install the samsung usb drivers for my S3 the installer always fails with this message: "The MSS installation for SAMSUNG USB Driver for Mobile Phones V1.4.6.0 has failed."
I had the universal naked drivers installed on this PC before for my tbolt and transformer prime, but it wasn't compatible with the S3 yet. There is an updated universal naked drivers that supports the S3, but when I try and back up my IMEI and put the phone into RMNET+DM+MODEM mode, the naked drivers don't recognize my device. in the regular MTP+ADB the drivers work fine.
so I imagine I need the samsung drivers to install for this to work. does anyone have any ideas how I could get the samsung usb drivers to install properly? I've also tried the V1.5.5.0 version as well and the installer fails as well. I've removed the universal naked drivers and tried to install without it and I still get the error. same thing in windows safemode. I'm running Windows 7 Enterprise 64 bit.
has anyone else had trouble with this? and any idea how to get the installer to work? thanks
Click to expand...
Click to collapse
Download and install PDAnet app to your computer, this app will install the driver for you. You have to select "Samsung" during the install. Once done you can uninstall the app but the driver stay.
If PDA net doesn't work for you, go into device manager and select your phone, click on properties, advanced, and install the drivers manually.
So, I came across another way to get the drivers to load without any INF file hacking. If you simply tell Windows (XP in my case) to update the driver, then tell it you will manually point to it, you can find a suitable one in the folder C:\Program Files\SAMSUNG\USB Drivers\25_escape (after you install the MSS driver pack, of course).
Unfortunately, in my case, I use MediaMonkey to manage this, and it doesn't seem to notice the "difference" between my phone and my wife's (both SGS3s). That's their fault, though... they clearly have some bugs in there.
that's the problem... the MSS pack fails to install. I tried copying the samsung\USB Drivers folder from my desktop (which the driver install worked on) to my laptop and manually pointing to the folder, but it says it can't find a driver for it. kind of odd. I'll have to try the PDA net drivers to see if that will work. thanks for the help guys
Dawg5 said:
If PDA net doesn't work for you, go into device manager and select your phone, click on properties, advanced, and install the drivers manually.
Click to expand...
Click to collapse
Thanks this worked for me