Related
searched and nothing that will work...any suggestions ? keeps saying mtp and cdc serial drivers not installed...and everytime i connect my phone to usb it reinstalls drivers...
i have usb debug on then tryed off...still a no go
i have the same problem but just about CDC serial driver.
All that comes after latest kies update.
I just clean up all registry and reinstalled kies. Still no results. Same error everytime
I have x86 on win7
Anyone?
Debug off, start e trouble shoot, then unplug.your.phone asap, let it trouble shoot, then it should successfully install
Sent from my SPH-D710 using xda premium
expertzero1 said:
Debug off, start e trouble shoot, then unplug.your.phone asap, let it trouble shoot, then it should successfully install
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks, but not working
Have you confirmed that the port is open in your network ?
My kies will show a usb connected but will never actually share connection. But the wifi kies browser works
Sent from my GS2ET4g
Did you try a different pc ?
Sent from my SPH-D710
tryd several pc's, and just about every trick i could google...still will not connect to device
I was also having days of trouble with this, but I can connect consistently now. Here's what worked for me on Win7-64:
Get yourself to a fresh start (uninstall drivers and Kies):
1) with your phone plugged in and USB debugging OFF (in my unprofessional experience, Kies will never connect if your phone's usb debugging is enabled), go to your Windows Device Manager. You should see either yellow bangs because your phone's drivers aren't installed correctly, or you'll have "SAMSUNG Mobile USB Composite Device" under USB controllers. Highlight it, click Properties, Driver tab, click Uninstall. Delete the device if it's still visible.
2) unplug your phone
3) If you're using the most recent version of Kies, I recommend downgrading to 2.0.2 because I read other forum posts about complaints with 2.0.3. Go to Windows Start - All Programs - Samsung - Kies - Uninstall Kies.
4) reboot
Now install stuff fresh
5) install Kies 2.0.2. I just googled it. Start Kies. Do NOT update it when you get the popup asking.
6) plug in your SGS2 (remember, USB debugging = OFF). You'll see a lot of typical driver installation bubbles. Go back to your Device Manager and confirm that you have no yellow bangs and you do see your SAMSUNG device under USB controllers.
At this point, Kies should already be connecting. I hope it works for you; it did me.
As an aside, Kies sucks. It's good to prove you have connectivity, install drivers, and to flash your firmware. If you actually want to sync Outlook contacts, Outlook calendar, and music, use MyPhoneExplorer (which btw requires USB debugging ON).
Hello,
I have searched the forums and Google, and was not able to find anyone else with this issue, so here I am.
I'm on Windows 7 x64 with a stock Canadian Galaxy Nexus 4.0.1 (yakjuux.)
I am trying to install GNex Toolkit and am unable to get past the first step. No matter what I try to do, any time I plug in the phone, it installs the default drivers.
Device installation settings are set to "never install drivers from Win Update." Phone is in development mode, I have removed Google Nexus from my devices (and checked the "delete drivers" box, though it doesn't even appear anymore), there is nothing for Samsung in Programs and Features, I have used USBDeview and there is nothing for Samsung/Nexus. I've tried using PDANet to no avail (I get error 103). I tried using "uninstall drivers" with GNTK, no dice (it seems to just remove a registry entry).
Any other ideas on how to make my PC install the drivers I want and not the default ones?
Thanks.
Read part A of this post.
efrant said:
Read part A of this post.
Click to expand...
Click to collapse
I have read that entire post and Bourne-nolonger's guide. Instead of showing up as "Android 1.0" device in Device Manager, my phone always shows up as Galaxy Nexus, with no yellow triangles or any other issues. (Yes, developer mode is enabled, and it seems to make no difference to how my computer responds.)
From Bourne-nolonger's guide:
"As soon as you enable this Windows will pick up a new device and it will attempt to install a driver - this will fail (or hopefully it will)." - mine never fails, it always installs drivers from somewhere. When I attempt to install new drivers to the Google Nexus device using UNK 0.7, Windows tells me that I already have the newest drivers.
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Scarf Face said:
[snip]
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Click to expand...
Click to collapse
Absolutely.
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
edit: tried doing the same in fastboot mode; the Device Manager recognized it as Fastboot mode, but did not let me install the proper drivers, saying that I already have the newest ones.
Scarf Face said:
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
Click to expand...
Click to collapse
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
efrant said:
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
Click to expand...
Click to collapse
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Scarf Face said:
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Click to expand...
Click to collapse
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Click to expand...
Click to collapse
Seems to be a problem with my PC, so I will try it with a different machine. Thanks for your help!
Ignore this. Wrong thread.
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
I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam
samwage123 said:
I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam
Click to expand...
Click to collapse
I don't know about the bluetooth drivers but indeed Android adb driver should work. So here is what I suggest.
Go to the Samsung Android Phone tab, and uninstall these 2 drivers in there, restart laptop, then go and download the ace 2 drivers from here and see if it works, ah btw let the phone connected during the whole process.
Thanks for the advice i followed your advice, uninstalled both the samsung and ADB then restarted my computer. I then reinstalled the drivers you provided with my device plugged in, while they were installing. I got the bluetooth drivers popup again, Also theres a new thing under my portable devices tab i will post more screenshots this is really boggling me :/
Also this popped up when installing the drivers to do with the bluetooth.....
looks like MTP won't work either eh? Well let's see if it's the phone or the pc
Firstly follow those instuctions to do some troubleshooting.
1) Go to http://www.microsoft.com/en-us/downl....aspx?id=19153
3) Download the file
6) Run it
7) Follow the instuctions (NextNextNextNext)
That's it, now the MTP devices should work correctly.*
(ALSO Try de-selecting usb debugging)
If this won't work then I guess it's a problem with the phone.I read somewhere in a thread that some dude with the same problem on a samsung phone did factory wipe, wiped dalvik, and installed another ROM, then the usb drivers problem got fixed.
Good luck.
EDIT: Also check this site here it seems to have solution regarding the bluetooth peripheral thing.
none of those links work It has also stopped coming up as mtp it now just says GT-I8160. Also i noticed when i start up my computer it fails to start until i unplug it and plug it in again (attached pictures)
Also there is no android adb anymore its just the samsung one.... is this right? i appreciate your help
I am also using a 64bit version of windows 7 if that makes any difference.
Have you tried connecting the phone to some other pc just to know which one is the problem?
I've ran outta ideas...well the problem seems to be with the device itself and if not then it's probably the usb port,maybe insert to another port or try your luck on google, search for something like "windows failed to recognize android phone"or smth similar. I'll do some more research and try to help y'out tomorrow
Sent from my GT-I8160 using xda app-developers app
I tried disabling usb debugging also i tried the drivers on my netbook. I am having really strange problems on there with odin i plug it in and odin wont pick it up and as soon as i unplug it it says added then removed very weird :/ thats only when the phone is in download mode....
Im thinking its either the cable or the phone. Im not sure though..
Remove all Samsung related drivers.
Restart pc
Use cccleaner to clean the registry
Reboot pc
Use the drivers that i have provided in the s advance forum in my all in one guide. Install the drivers without connecting the phone.
After the drivers are installed, turn off internet connection and then connect the phone.
Sent from my GT-I9070 using xda premium
Thanks for the new idea shaaan I have succesfully followed steps 1 and 2. But I am struggling to find your all in one guide would one be kind to link me ? I did a forum search with no luck. Also I am using a galaxy GT-I8160 would using the s drivers matter? and thanks for the help mojito0 I would like to think it isn't the cable or phone, as I have literaly owned them for 8 days (just over a week). I can always see if i can borrow another cable of my friend today though
edit: I found your all in one guide I am now going to attempt what you said
After removing all the samsung related drivers and restarting I get all these devices come up? The device is not plugged in either.
I dont know if this helps atall, but I finished doing what you said ignoring the drivers.... Then went to flash using odin, Put the phone into download mode and noticed that after a couple of seconds of being stuck on setup connection. It then says the GT-I8160 cannot start, Also the mtp and adb android driver is still displaying that yellow explanation mark :/ I am a newbie to android here and dont know the difference betwene the samsung adb and the android one as listed do they both need to be working?
Remove all the displayed devices from other devices, also remove that Samsung adb thingy and also there will be one Samsung related device in the usb section! Remove them all and then follow my steps.
As for your driver query, the drivers are universal for a specific range of devices. The driver version 2.0+ should work for all devices which were released in 2012
Sent from my GT-I9070 using xda premium
I have recently root my samsung tab pro 8.4 wifi version. Everything seems to work well, except USB connection to my windows7 desktop. I installed the latest version of Samsung usb driver (download from Samsung's web site for my device). Whenever I connect it, media device mode, the "installing device driver software" icon spins for couple of minutes, then I got the error of "Device driver software was not successfully installed" . In the detail dialog window, it says "MTP USB Device" failed with a red cross. what did I do wrong? thanks.
I have tried several different USB 2 ports on my computers. Also I have Developer mode turned on, with or w/o USB debugging checked. Nothing seems to work. Also the camera mode doesn't work either.
Did you install kies 3 from samsung?, this should install all the drivers you need.
http://www.samsung.com/us/kies/
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
dealcrack said:
I tried with this version of kies from samsung's website, not working. Got the same failed to install device driver message.
In windows device mananger, it shows a MTP USB device with yellow "!" mark on it. If I try to update driver from here with the driver installed on my computer, it says I have the latest driver installed already.
Click to expand...
Click to collapse
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
redpoint73 said:
Try going to Device Manager in Windows, find the device, pick the option to select from the drivers on the computer, then pick the "USB MTP drivers" (generic, not Samsung) and see if that helps.
Click to expand...
Click to collapse
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
dealcrack said:
thanks for your help. I tried your suggestion, and
I went to the Device Manager, and select the "MTP USB Device" with yellow "!" mark, choose this menu,
Update driver software->Browse my computer for driver software->let me pick from a list of device drivers on my computer
I see two drivers, however either works for my 8.4 pad. It says "This device cannot start (code 10)"
Also when I open the properties for this device in device manager, it shows its driver running is from Microsoft, driver version 6.1.7600.16385. Should be a driver from Samsung?
Click to expand...
Click to collapse
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
CuraeL said:
Are you running stock TouchWiz ROM? Just to be sure.
Otherwise you could remove all your USB drivers related to Android and start from scratch with just the Sammy driver. I had to do that for my previous OnePlus One, it just wouldn't connect. It chose a wrong driver each time I hooked it up so I had to just remove those from the driver store and then make it choose another one. That was for ADB thought, but I guess it couldn't hurt to try anyways.
The reason I'm mentioning if you're on stock ROM is because this morning, on CM nightly 01-24 I had some troubles with my tablet being read by Windows, it was fixed in 26 so.. Just wanted to mention it.
Click to expand...
Click to collapse
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
dealcrack said:
Yes, I am on the stock TouchWiz ROM, but I rooted it following steps from one thread in this forum. Before rooting, I was able to connect. I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem? Will going to CM ROM solve my problem?
Also, can you tell me steps to remove all my USB drivers related to Android in Windows 7?
Click to expand...
Click to collapse
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
dealcrack said:
I do have a LG G3 phone connecting to the same computer successfully. Will this cause any problem?
Click to expand...
Click to collapse
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
CuraeL said:
It may work to install CM11 or CM12, BUT try this toolfirst (uploaded to my personal box account) Find all your mobile device drivers in this list and mark them and go to "File" and click "Uninstall marked drivers", restart your PC and plug in your tablet. Then try plugging in LG after so it gets drivers later. I'm not sure if it will work. But it should apply new drivers. If it doesn't work, uninstall the drivers one more time and download the Samsung drivers from 3rd party and install them and apply then manually to your tablet through Device Manager in Windows.
https://app.box.com/s/7njztz17hekfkpxbjk7h79xsctnmuptn
Anyways, try this first.
Click to expand...
Click to collapse
I download this tool, and remove all Samsung or Android related USB driver. Restart my computer and connect the pad it's not working. Then I uninstall the Samsung driver software, and all USB driver. Then restart and install a samsung driver from the thread about how to root my pad in this forum. Connect my pad, no luck. Still the same problem. I am about to give up.
redpoint73 said:
Its always a possibility. I'd try to uninstall the LG drivers. You can always re-install later (if needed).
In a perfect world, the Sammy drivers would be what you want. But this is of course not a perfect world. I've had better luck using the "generic" Microsoft MTP USB drivers over the HTC drivers on my HTC devices.
Click to expand...
Click to collapse
I uninstall my LG driver too, along with all Samsung/Android usb driver with the tool from previous reply. No luck, It still shows a MTP device with yellow "!" mark.
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
dealcrack said:
Just before I about to give it up, it connects to my another computer now, which is my main computer and it had trouble connecting to. All I did was restart my pad several time and odin twrp recovery to it. It connects after rebooting. No idea what cause this problem, but it works now. thank you for all your help.
Click to expand...
Click to collapse
Glad you sorted it out, to some degree or other.
USB connectivity on Android devices is very tricky, at least on Windows (can't speak on other OSes). My HTC phone connects fine to my work laptop with the HTC drivers. On my home computer (also Win7) it frequently drops adb connection and I have to manually select the "generic" Microsoft drivers to make it work (and the HTC drivers never seemed to work completely right either). My Sammy Pro 8.4 seems to connect just fine to my home PC, however. So it seems its just a crap shoot what kind of connectivity you will get, really.