"Hardware ID doesn't match" error when plugging phone in - Sprint Samsung Galaxy S III

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

Related

[ADB] Device cannot be started (Code 10)

For some odd reason, I lost adb functionality (i.e. any adb command issued receives "error: device not found"). I looked in Device Manager and noticed that MyHTC was gone! I looked at my phone and USB debugging was enabled and in charge only. I could put it in USB Drive mode and the PC would recognize it as a USB Mass Storage Device so that I could exchange and view files but no adb.
I searched and searched on this issue for hours and installed over a half a dozen "androidusb.inf" driver files several times over. Every install generated the Code 10 error where Device Manager was lacking some information from the driver file and could not start the device. I reinstalled HTC Sync and gave that a try...nothing. Downloaded USBDeview and uninstalled all HTC drivers including the HTC Android USB Device and tried again to no avail. WTF?! What else am I supposed to do?
Well, in a "what the hell, let's give it a try" kind of moment, I decided to toggle the USB debugging off and then back on (and yes, it was checked and on the whole time). WORKS!!! WHAT THE CRAP?!! MyHTC is back in Device Manager and everything is back to normal. I'm glad but irritated!
I share this story in hopes that if someone else stumbles on this problem, they will not have to go through the same headache as I did. Just thought this was odd considering how many times I have plugged and unplugged and never had any problems with adb.
Toggle USB Debugging....so simple. *rolleyes*
Same Issue
I've got the same issue on my EVO 4G. Just installed the latest CM7 and now it tell me device not recognized. If I manually install the drivers it gives me the same code 10. I can't bring up the phone as a storage device and toggling the debugging is not working. Any ideas?
SillyJay said:
I've got the same issue on my EVO 4G. Just installed the latest CM7 and now it tell me device not recognized. If I manually install the drivers it gives me the same code 10. I can't bring up the phone as a storage device and toggling the debugging is not working. Any ideas?
Click to expand...
Click to collapse
You installed the hboot drivers correctly?
Boot into recovery, with usb debugging enabled, connect to pc, it should install the drivers.
Still the same
Even when I reboot into recovery it still gives me "USB Device not recognized." I previously had MikFroyo on my phone with no problems. I'm at a loss.
SillyJay said:
Even when I reboot into recovery it still gives me "USB Device not recognized." I previously had MikFroyo on my phone with no problems. I'm at a loss.
Click to expand...
Click to collapse
You most likely have a bad cable, do you have another one you can try?
Possibility
Not at the moment but that may explain it. Still seems weird for it to just go out right as I change to CM7, but still a possibility. I am going to run and grab my other cable. Thanks for the advice.
No Luck
The new USB cable didn't fix the problem. Also, in device manager, even with the driver installed its labeled as "unknown device."
If I boot into hboot the computer recognizes it.
**update: After rebooting from the hboot, my phone is recognized by the computer however, a disk drive is not coming up in "my computer." I have USB storage turned on but Im not getting anything.**
Any help would be much appreciated!
Sad Day
Apparently the Micro USB port on the bottom of my phone is going bad... I talked with some other people who've had the same problem. HTC knows that the ports aren't very sturdy as well. Well... sad day for me.
Also if you're getting the notice from windows saying that you your device will run faster in a 2.0 usb port and you know the port is 2.0 ... chances are your port is going bad as well.
*****UPDATE*****
Flashed to MikFroyo and none of the above stated problems. I would venture that it was CM7 but apparently everyone else is able to use it so who knows.

[Q] Yet another "no more prompt" on the phone

Hi,
So before going on, I've now spent couple hours trying to fix this issue, looking for tips and threads without luck.
I'm using a rooted DHD, with an Affinity rom. It works perfectly fine.
Yesterday, a friend asked me to install a custom rom on his tablet, which I did.
I had to clean all my Android drivers because the tablet wouldn't be recognized properly by my computer (no ADB driver).
In the end it didn't help and I had to use a fastboot method, which ended well.
Now, my phone doesn't prompt me what I want to do when I plug it to my computer.
I, once again, clean the usb drivers, installed HTC Sync and all its dependencies but the software doesn't recognize my phone (I couldn't care less, but I suppose it's part of my "no prompt" problem).
Of course I tried with and without AV, firewall... No luck (and I think I rooted my phone with both them ON anyway). I tried other USB ports as well
If I plug the phone without HTC Sync and its drivers installed, Windows 7 installs 3 out of 4 drivers, the last being in this suite I suppose.
I tried using the drivers provided with the sdk, they're not for that missing driver.
With the suite installed, I end up with 2 new devices on my devices manager : one "Android USB Device" labeled "My HTC" and one "mobile device" labeled as "J:" (drive name) which means no ADB drivers.
Of course, USB debug and ask when connect are both ON. I tried turning them ON and OFF, but still no luck (except a new driver installation).
ADB drivers start to install as soon as uninstall the "HTC Drive Installer" component, which is weird.
So I don't really know what to do now except that it's driving me nuts as I cannot do anything else than charging the phone now.
Is this a case of "USB brick" ? The threads I read about it all talk about "stock roms".
Try Multi Mount SD Card from the Market.
https://market.android.com/details?...vaWQubXVsdGltb3VudHNkY2FyZC53aWRnZXQuZnJlZSJd
Thanks for the alternative, it works fine
I'd still like to know how to fix this though, if anyone has any clue about it.
It's a sense rom?
Sense roms have an option to permanently put the usb state to charging or storage, etc, without prompting you again. It's an option you tick, in the settings (usb connections, or usb sync maybe? sorry, I don't use sense).
Yes it's a sense rom, with the "always ask me" option activated
Exactly. Yes.
That's strange.

[Q] USB Drivers install lies. My phone is not in use.

So, I've tried, several times, to get the USB drivers installed. I have been rejected, every time, with a pop-up telling me my phone is in use & I need to restart the phone & my computer.
I have never had my device connected to my computer. I've tried the install even while my phone is completely shutdown.
I do not have Kies installed.
I'm on XP.
Has anybody else seen & defeated this?
jmags5 said:
So, I've tried, several times, to get the USB drivers installed. I have been rejected, every time, with a pop-up telling me my phone is in use & I need to restart the phone & my computer.
I have never had my device connected to my computer. I've tried the install even while my phone is completely shutdown.
I do not have Kies installed.
I'm on XP.
Has anybody else seen & defeated this?
Click to expand...
Click to collapse
Any other device plugged into USB at the time?
Also screen shot the error message
I went out of town, for work, & I was able to root from a different machine.
I was not able to get THAT box to see my gn2 except as a camera. I'm not sure what that was all about. Pretty high probability I was doing something wrong.
Sent from my SPH-L900 using xda premium
some people, like me, have had issues with Samsung's USB drivers.
Try uinstalling whatever drivers you tried. Than just plug in the phone. See what Windows does. If you can connect the phone to the PC, then I think you got a bad installer. I would suggest downloading them directly from Samsung or Sprint or whatever your favorite driver spot is.

[Q] USB Device Not Recognized & No Previous Solution Working (Win7)

I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
self bump, since it's been three or four days with no reply. I could really use advice on this.
In your laptop, when you go to Devices manager, do you see an unknown device? If you try searching online for the appropriate driver through Windows Update, does it find any helpful driver?
CTurmoil said:
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
Click to expand...
Click to collapse
I was dealing with this on my Win7 rig, and came across some advice that helped. If you have an SD card installed, turn the phone off, remove it and then reboot and connect the phone to the computer. I don't know why it worked for me, but it did.
Good luck to you.
CTurmoil said:
I'm trying to root my Samsung Galaxy SIII, and whenever I try to connect it to my laptop, it gives me the "USB device not recognized" error. I have tried everything I can think of.
Kies uninstalled, registry cleaned, searched my computer to erase every file linked to Kies, and no dice.
Installed, uninstalled, reinstalled, re-uninstalled, re-reinstalled drivers. Nothing.
After every driver change, rebooted computer and phone, nothing.
Factory reset the phone since one post I found had that work, still nothing.
So right now I have a laptop with no Kies, Samsung drivers installed, a factory reset phone, and the USB cable still won't work. It is the cable that came with the phone. The phone is Android 4.1.1, an SGH-I747, build number JRO03L. This is extremely agitating since I can't even connect my phone to see the files on it! I had a Motorola Atrix and had a similar problem, but fixed it with a simple driver reinstall. I've even gone into the hidden code menu and set the USB mode to MTP+ADB, and the UDAP (or whatever) is set to PDA. That won't even work. At this point, I'm willing to do anything. I hate stock ROMs, and want to remove all the crap this phone has on it, especially that damn voice thing and Kies.
Click to expand...
Click to collapse
Possibly two things download revouninstall to uninstall your drivers it searchs bolth registry and system for left over files (delete them)
I had same problem all I did was use revouninstaller to uninstall old drivers (it scans entire system and registry for left overs. a must.
Then I used these drivers, also when letting your installing drivers (turn internet off) don'lt update them there older, but they work for everyone who does this. If you need a better guide search there is one somewhere but point is use these drivers and don't update them (smile) works with adb everything you won't see a difference these drivers work better. peace.
Drivers------>Samsung Drivers 1.4.6.0 search for 1.4.6.0 drivers samsung fix for more info later
search for revo uninstaller
Whenever I have this problem, I must manually install the driver.
Open device manager.
Go to the unrecognized device that you know is your phone.
Properties and "update driver".
Tell it you have your own driver.
Don't let it "search" for a driver.
Manually point it to the exact driver file you need.
Works every time for me.
I took out the SD card to try all possible solutions posted.
Uninstalled drivers and installed the older versions that one of you linked me to, didn't help.
Tried directing Device Manager to install the driver manually, but I have no idea where to find it. If you have the driver file or at least the name and version, I can get it and use that.
I can't believe how much trouble it is just to hook an android phone to a computer, this happened with my Atrix as well.
Have you tried and different cable ?
So I was having a problem with my laptop recognizing my S3 when connected via USB. The notification would not appear in the status bar that a connection was made, and neither Fedora Linux or Windows 7 would recognize that the device was connected. I tried reinstalling Kies/drivers under Windows, and checking the output of dmesg/lsub on Linux. Nothing.
Did some googling and found this thread that help solve the problem!
http://blog.vacs.fr/index.php?post/...ot-detected-problem-on-Android-Samsung-phones
I found the problem. It was the cable. Somehow, it was severed where the cable connects to the mini-USB connector. I discovered this when the entire mini-USB piece fractured and fell off, revealing the tangled and snapped wires. I went today to AT&T to buy a replacement, and it worked on the first try. I don't know how the cable got damaged like that without being detected, but there we go. Now how do I set a question as resolved?

Is there a fix for the MCP connection fail thing?

Hi,
I'm having some issues where the MTP driver fails to load. Tried all the obvious stuff and did a lot of reading of forums and stuff but can't find a fix. Could anyone help me to fix it please?
Here's what hardware I have and what I've tried so far:
Tab Pro 8.4 16gb wifi UK model, rooted.
Connected via cable to Dell XPS 17, latest USB drivers installed, win 7 x64.
First of all, I enabled USB debugging and windows installed drivers for all except MTP.
Tried installing the Samsung driver package, same problem. Uninstalled at present.
Installed kies, didn't work, wouldn't even connect to the device. Uninstalled.
Followed the instructions on the wiki but the suite software installs the driver succesfully but then windows won't accept the driver. Tried the workarounds in the wiki but still no luck.
Tried rebooting the tablet and leaving the cable connected.
Tried wiping the cache.
Tried restarting both the tablet and laptop after reinstalling software and drivers, still no luck.
Found several workarounds on my travels, one was a command line for windows to add to usergroup ( it's on the laptop downstairs, will add it to the post tomorrow).
One post said to change a registry entry...really? Tried that, and another registry trick, but still no.
Using the same laptop, I had similar problems trying to flash a custom rom onto an s4, but the CM installer worked first time. I've done a fresh install of win 7 since then.
Can anyone shed any light on this for me please? Is there any kind of workaround? Running out of ideas!
Thanks
Fixed this, well, kind of. Here's a quick rundown of what I did, for people like me who are struggling with connection problems.
I thought I had tried everything, was going to dump the whole thing and then remembered that I'd fixed some previous USB problems (sound card) by doing a clean boot.
First, remove Kies.
The only other thing that is required are the samsung mobile drivers from their website. I tried with and without and this would only work with them installed.
Restart your tablet, make sure MTP is selected.
You can find out how to do a clean boot for you version of windows here.
Leave your device connected via USB cable. Once you have clean booted into windows, windows will attempt to install the drivers from windows update, let it do this. It can take a minute or two to complete. You should then see a green tick in the notification area rather than the dreaded red cross.
If, for some reason, the driver doesn't install first time, you can unplug and then plug back in the USB cable and this should do the trick.
What I did find, is that the connection wasn't consistent, I could restart either my laptop or tablet and then it wouldn't connect, so I'd have to go through the above process again to get it to connect.
Doing this allowed me to flash the Clockworkmod recovery with odin 3.09, but for whatever reason, I was still unable to use the recommended Eimdall suite to flash cyanogenmod.
In the end, I downloaded the CM11 zip file to my tablet (via http) and then used ES file manager to move it to the SDCard root and then clockworkmod picked it up from there.
Also, once CM was installed, there were no connection problems at all, as far as I can see.
Hopefully this will help others in the same predicament.

Categories

Resources