Windows 8.1 Device Manager is misidentifying android USB tether as an MTP device, thus preventing me from even installing the generic "Remote NDIS based Internet Sharing Device" because it only wants to look for compatible MTP drivers, I feel like there is a way to do with this Zadig but I'm not sure how to use it for anything except for the preset devices. I'm attempting to set up my economy VR ghetto rig :silly: , but this is getting in the way of a smooth video connection for Trinus VR, wifi isn't cutting it.
Try uninstalling the driver and installing ADB drivers
popthosegaskets said:
Try uninstalling the driver and installing ADB drivers
Click to expand...
Click to collapse
First thing i tried, i've done everything you'd probably think of that would solve it, I noticed though that when i go to uninstall the driver, no matter what it doesn't have a checkbox to delete it as it normally would.
I remember having some trouble like that with one of my test phones, but the ADB driver install solved the issue. As I recall, I had to do it manually: Browse my computer for driver software>Let me pick from list>Uncheck Show compatible hardware, and choose one of the alternatives (had a few listed due to several test phones)... I think one of the Google, Inc> Android Composite ADB did the trick. That might depend on the phone. Is there maybe some docs/manual for your phone that could explain how to sort this out?
Let me know if you find a solution. And maybe join the Trinus VR forums to discuss further?
I'm the dev for Trinus VR btw, so any problem and solution that I can find to help users is always welcome to know about
loxai said:
I remember having some trouble like that with one of my test phones, but the ADB driver install solved the issue. As I recall, I had to do it manually: Browse my computer for driver software>Let me pick from list>Uncheck Show compatible hardware, and choose one of the alternatives (had a few listed due to several test phones)... I think one of the Google, Inc> Android Composite ADB did the trick. That might depend on the phone. Is there maybe some docs/manual for your phone that could explain how to sort this out?
Let me know if you find a solution. And maybe join the Trinus VR forums to discuss further?
I'm the dev for Trinus VR btw, so any problem and solution that I can find to help users is always welcome to know about
Click to expand...
Click to collapse
The Google Inc driver is the universal driver, so it should work across most Android platforms and its derivatives.
Related
My computer keeps popping up finding new hardware when I ##3424# to go into DM mode.
I have activesync and htcsync, as well as the drivers that work up to the touch pro as well.
Give me a few minutes, I'll look into it. You might have just hit something big (from what i've seen of this so far)
You may have just found a gaping hole that could be some fun. Can't say much more, but i'll post back with some updates if this means anything.
They are attached. I modded some other drivers I found earlier. Simply, download and install :
http://www.vzam.net/uploadedfiles/WModemDriverInstaller.exe
Run specified 32bit/64bit installer, grab files out of %TEMP%, change value "0b03" to "0c08". Update driver for phone from task manager with that drivers folder. 32-bit modded drivers attached. I don't know how to talk to HTC DIag though.
Could someone try this on unix/linux? I don't have a working box (just sold my eee) Hopefully the drivers install and you get something. Looks like possibly a modem though.
http://www.mediafire.com/?ondwg2xiwyy
PS - if this file is agains the rules, can a mod remove it? Thanks!
32 bit drivers work
Drivers work with 32 bit windows 7 if you edit the USB device ID in the files, I haven't been able to do anything of interest with it yet aside from read from the phone using QPST and QXDM, it needs to be CID'd to do anything of use, I have no idea how to go about doing it with an andriod based device.... any suggestions?
The Hero drivers work great.
Just download the Hero drivers. Then use the latest version of QPST, with ##DIAG#.
Works great. You probably don't need to go through all of that other pain to accomplish the same goal. Good find though.
So is this a dead end?
So I set out to root my phone and am in the process to trying to install the USB drivers so i can use ADB. At first, windows installed it's own drivers, which obviously didn't work. I tried to update the drivers in the device manager to the ones located in the google-usb directory, but it said i already had the latest installed.
Next i decided to uninstall the current drivers completely and start over. I then told it to install the drivers that were located the in the google-usb directory. It said no drivers were found. They were obviously there, so i manually gave it the "android_winusb.inf" driver as per the cyanogen mod wiki page instructions on installing the drivers. It then said that "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I'm new to this so thanks for any help at all. I really want to learn my way around this kind of stuff.
Try it with your phone in mass storage mode with debugging on.
Still no luck. I've had it in debugging mode and charge only. Switched to disk drive mode and no change
Just download HTC Sync and use the drivers it provides. Should work for using adb.
Sent from my ADR6400L using XDA App
Now it can't even find HTC Sync on my computer... It's installed and i just used it the other day. Maybe it's something to do with the fact that i uninstalled the drivers it had? It can't communicate now?
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
setexascustoms said:
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
Click to expand...
Click to collapse
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
jwa0042 said:
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
Click to expand...
Click to collapse
You're more than welcome. You might re-title the post with [Solved] at the beginning so anyone with the same problem know to look here.
Just wanted to mention here that this was noted a while back and the CM Wiki will be updated with an easy way to correct this for Thunderbolt as well as other devices soon.
what's the solve?
Guys / Gals
I was able to fix my problem of not being able to connect my phone, a Samsung Note 3, and the error I got was from Microsoft MTP. I believe it is Media Transport Protocol. I searched for days; this was a pain in the neck problem. iPhone users seem to have the same issue. I have seen a couple of solutions suggested here on XDA, but they did not work for me. One solution advised to remove the drivers via Windows, mine is Win 7 btw, Devices and Printers screen, they stated to make sure to check the remove driver checkbox. But MTP does not have any such checkbox that I see in my setup. Maybe we are different Windows versions or something. Regardless, what worked for me was to reinstall Windows using the Upgrade option right after you select install. This procedure does not usually damage your personal files; but like every other post here:
1- Do back up everything.
2- I am not responsible for any damaged files, computers, anything.!.!.! Ok?
I backed up my files on an external drive. The only thing I had to reinstall was VMware Workstation 11, and afterwards I was able to launch it fine. In fact I am typing this post from the Ubuntu guest within the restored Win 7. During the install I noticed Windows took some time "repairing .Net". So maybe folks who have more knowledge of Microsoft products can look into this as a quicker fix?
After you are done, test your phone's connectivity and if it is working, create a restore point as soon as the install is done since Windows is going to install a slew of updates right after. You can label restore points something like "Phone Driver Works" or anything else, which implies a successful milestone.
Send me an email if any of this is unclear. I am so glad this is fixed for me. I'll post some of the links, which helped me figure this out.
Hi, I recently changed to Win 8.1 (x64) and for some reason the OS is not recognizing my phone or my tablet (both have MTP interface).
Apparently the drivers (MTP & ADB) are correctly installed, I see both of them on the device manager with no errors, and I can even connect through ADB. Also, in the devices and printers site I see them under the unspecified type. I also see them on the safely remove menu (but the icon is a generic device, not a multimedia one).
I've tried countless solutions, and also all types of drivers. Sometimes I get error 10, sometimes nothing.
I've read one solution that is to install the media feature pack for N versions of Windows but that's not my version. But then I remembered that I messed up with the system codecs not long ago. Maybe there is a connection?
Apart for MTP and ADB devices in device manager, I have a hidden device under "other devices" category with the name of the phone (GT-I9300 in this case). That's the name that should be seen on the explorer to access the phone's files.
Anyway, I can't explorer any android device through MTP.
Any solution or approach to find the error?
I will provide any info you guys need.
Thx in advance!
Anything? I've been trying things literally all day and I'm starting to feel very fustrated...
I've tried this:
http://forum.xda-developers.com/galaxy-s3/themes-apps/guide-troubleshoot-mtp-driver-t2518821
And nothing at all. It's not the phone because I only changed from win7 to 8.1, I did nothing to my phone. And also it's not just my phone, also my tablet or any other mtp device. Also, the driver seems to work well on device manager, the problem is that threre's no device in explorer to open it.
Any ideas??? I'm freaking out!!
Problem solved. Guess what was the cause: the Media Scanner Optimizer Xposed module. Don't know why though. If anyone knows how to fix it please tell me, otherwise it will remain deleted from my phone.
Thanks.
Hi, I'm new to the N9, have had the tablet about a week. I have tried connecting it to my windows 7 Pc and the N9 isn't recognized. I have tried all the basics, all drivers are current, set tablet to mtp, and not found. I have connected to a friend's Windows 10 PC and the N9 is found immediately. My N9 is a wifi only device, non rooted. I have 2 other Android devices that my W7 PC finds with no issue. Anyone else experience this, and or have any suggestions on how to fix this issue ? Not looking to root at this point. Any help and guidance would be greatly appreciated
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
In some cases, you need to enable ADB on your N9 before plugging it into your PC (Settings -> Developer Options -> Android Debugging).
peterk-1 said:
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
Click to expand...
Click to collapse
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
eckharttim said:
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
Click to expand...
Click to collapse
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
peterk-1 said:
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
Click to expand...
Click to collapse
Thank you for your help I greatly appreciated it. After trying pretty much everything, I decided to see if the ruu's for my two phones would run on W10. They did, so I then proceeded to update my W7 to W10. N9 communicates perfectly now with my PC. Thank you