missing hardward ID limited solution - Sprint Samsung Galaxy Note II

I've read some people are having trouble with GN2 when connecting it to a PC via a USB cable. I've been having that problem as well.
I've found some suggested solutions, but none worked for me:
Code 10 error device manager
Missing Hardward ID fix
I found a partial solution. It's limited in what is solves. This is good for a user who is looking just to be able the phone USB storage so you can transfer files and what not. This does not give access for ADB. This will get rid of the need to plug and unplug the usb cord, or enable or disable USB debugging or whatever else people need to a bunch of times for the phone to finally be recognized by their machines. This works in Windows 7 64bit; I assume 32 bit. Don't know about Windows 8 (if there is the problem)
Basically, uninstall the Samsung USB drivers. Then just reconnect the GN2 to your PC. Let Windows install it's drivers. You'll see failures for Ssmsung and ADB, but still have access. You'll get the same access with and with USB debugging. Below are pics showing the results of driver installation by Windows, and hardware device properties. If you click the picture, you get see a large image of the screen shot.
Without USB debugging
WIth USB debuggind turned on:
Maybe someone with more knowledge can figure out the rest to complete fix the issue. But I assume for most, this should be sufficient.

lovekeiiy said:
I've read some people are having trouble with GN2 when connecting it to a PC via a USB cable. I've been having that problem as well.
I've found some suggested solutions, but none worked for me:
Code 10 error device manager
Missing Hardward ID fix
I found a partial solution. It's limited in what is solves. This is good for a user who is looking just to be able the phone USB storage so you can transfer files and what not. This does not give access for ADB. This will get rid of the need to plug and unplug the usb cord, or enable or disable USB debugging or whatever else people need to a bunch of times for the phone to finally be recognized by their machines. This works in Windows 7 64bit; I assume 32 bit. Don't know about Windows 8 (if there is the problem)
Basically, uninstall the Samsung USB drivers. Then just reconnect the GN2 to your PC. Let Windows install it's drivers. You'll see failures for Ssmsung and ADB, but still have access. You'll get the same access with and with USB debugging. Below are pics showing the results of driver installation by Windows, and hardware device properties. If you click the picture, you get see a large image of the screen shot.
Without USB debugging
WIth USB debuggind turned on:
Maybe someone with more knowledge can figure out the rest to complete fix the issue. But I assume for most, this should be sufficient.
Click to expand...
Click to collapse
Hey....Thanks so much!! It's a good start.
With all of the brilliant developer on these boards, I'm surprised no one has come up with a fix yet. In good time!!!!

I figured most users on here aren't needing to use ADB after rooting, but want to access storage. I tried accessing using ADB, which I have installed on my PC but never use, and it wasn't connecting. I had to look up how to use it. When I asked for listed devices, nothing came up.
If you look at the threads listed, it appears it's a driver issue with Samsungs USB drivers. I figure at some point either Samsung or Microsoft will fix it, more than the developers here. Although, I think they'll probably find a solution faster.

HA! I'm glad I'm not the only one. I've been rebooting my PC to solve the issue. It only happens once in a while. I'll be watching this thread. Thanks

I know this isn't exactly on topic but I've seen this discussed here and other forums as far as "properly" ejecting the Note 2/GS3 from your PC. Some say you just pull the USB, it will not corrupt etc. I just wanted to share that you can eject(windows). Just go to Devices and Printers, you will see SPH-L900 in your list. Right-click and eject. Probably means nothing but figured I'd share for those that feel iffy about just pulling the plug

I just pull my USB. I don't do the whole eject thing. The "having" to do the eject thing basically went out when Windows 7 arrived. I've been doing this method for couple years with Windows 7 for various devices. Never an issue.
And even faster than when you mention, if on WIndows 7, you go to the task bar to the right, there is a triangle that shows all your running background apps. Click that, right click the USB icon. It should be listed. If not, there is a "open devices and printers" which takes to the same place.

Related

W7 wont recognize

I just got my data cable in an accessory bundle from hong kong(ebay). Installed htc sync and when I plug in my phone to the PC I get a usb not recognized error. I tried on a different laptop and same problem. Could it be the generic usb cable?...or did I miss something somewhere?
which os are you using. I believe if you are using win 7 64 there is an additional driver you have to install. I know i did.
windows 7 64 bit. Is the additional driver a separate download or is it in the sense folder??
when you plug it in...does it start charging? do you get the USB connection sound?
if the PC has no response to the phone being plugged in, then try swapping the cable.
if the PC does respond (in any way..lights, sounds, etc) then it's prolly a software issue.
did you actually try doing a google search on this?
something like: evo windows 7 64 "usb not recognized error"
http://forum.androidcentral.com/htc-evo-4g/22285-usb-device-not-recognized.html
http://www.htc.com/us/support/evo-sprint/downloads/
... updated version of HTC Sync
http://community.htc.com/na/htc-forums/android/f/94/tags/Windows+7/default.aspx
http://community.htc.com/na/htc-forums/android/f/94/p/5082/23208.aspx
... a problem with the USB hub.
it was a seperate download i cant find it on my pc but i got it off the guide for adb in development forum. hopefully that works for you.
Thanks for the links magic, but I found those when I actually did search before making this post. None of them worked. I did find a more detailed tut on how to root, so maybe something I missed is in it.
Still havent been able to figure it out. When I connect the device and open device manager I get an !unknown device. I click it and "view drivers" and says none are loaded. SHould I boot into safe mood and try all of this?...or disable driver signature or something??
i've had this issue in the past...in my situation is was a bad port...
you may want to reload everything on the phone though... i've ran into situations in the past were i flash a rom and the usb stops working i am able get the usb to work again by reloading the rom
skuzzie said:
Still havent been able to figure it out. When I connect the device and open device manager I get an !unknown device. I click it and "view drivers" and says none are loaded. SHould I boot into safe mood and try all of this?...or disable driver signature or something??
Click to expand...
Click to collapse
sounds like you just don't have the drivers. they're around here, or, you could update the sdk and the drivers are included in the package. you'd have to do the devmgmt.msc command w7, right click on the device, search for drivers, they're in the sdk usb driver folder.
or, someone around here posted them up somewhere. search.
Thanks for the help guys, I did all of the updates and what not, removed all the associated devices to all usb ports and none of that worked.
I decided to just go the easy route and rule of my generic cable, went to best buy and picked up a new one (data pilot) and it recognized it asap.
Thanks for the help though.
thanks for the update. TBH...the cable was lowest on my list of possible issues.

[Q] EVO Unrecognized - WTF??

Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??

htc keeps asking for MTP driver?

Dezire z keeps askinf for MTP drivee?? i recently flashed mexdroid rom, and in the beginning none of the usbs would connect my phone. I thought it was a nightly issue as it was based off of a nightly but now its using RC1.
Recently i played around, it wouldnt connect with the "ADB or Android phone driver." I fixed that and those work fine in Device Manager in Windows 7. However!, in device manager it KEEPS asking for MTP. i tried uninstalling, updating, everything!! and it just wont find my htc desire z.
ADB can find it when using command prompt. It can even logcat, and its weird why ADB can see it but windows cant. I have posted a Download link to the Logcat file. Im hoping anyone here can help me.
http://dl.dropbox.com/u/21509455/logcat.txt
thanks
edit* i think i read somewhere Android doesnt use MTP drivers....-confused-
windows 7 can see my phone and lets me safely remove it too, but wont let me see it in my computer.
issues I was having with W7 x64 were resolved by PDANet. you might try it out, although your issue is slightly different than mine... the device was entirely unrecognizable (by adb, fastboot, the whole shebang).
edit: NOTE you don't need to actually use PDAnet, it will just locate an appropriate driver and install it for you, then you can uninstall it from your PC.. unless you want to use it, of course. pretty slick.
pmcqueen said:
issues I was having with W7 x64 were resolved by PDANet. you might try it out, although your issue is slightly different than mine... the device was entirely unrecognizable (by adb, fastboot, the whole shebang).
edit: NOTE you don't need to actually use PDAnet, it will just locate an appropriate driver and install it for you, then you can uninstall it from your PC.. unless you want to use it, of course. pretty slick.
Click to expand...
Click to collapse
ive done this and it found the proper driver. "Android phone" BUT when it tries to connect with device, it says "failed to handshake with device" and proceeds to uninstall pdanet. Is it because its conflicting with windows 7 cant find the MTP driver?.... sooo confused.. never, ever had this problem
edit* after pdanet is uninstalled, the Android phone driver works fine, but MTP does not.
jark99 said:
ive done this and it found the proper driver. "Android phone" BUT when it tries to connect with device, it says "failed to handshake with device" and proceeds to uninstall pdanet. Is it because its conflicting with windows 7 cant find the MTP driver?.... sooo confused.. never, ever had this problem
edit* after pdanet is uninstalled, the Android phone driver works fine, but MTP does not.
Click to expand...
Click to collapse
that's a bugger.
when you plug the phone in, in device manager, does it show as a USB mass storage device under the USB controller section? to check: unplug all usb devices (aside from input devices like keyboard/mouse/what-have-you). plug in your phone and go to device manager (right click my computer->manage->device manager). under USB controllers, check and see if there is a USB mass storage device. assuming you have disconnected any other storage media, this is your phone.
if it does:
uninstall this driver, unplug your phone, restart, plug your phone back in.
if it doesn't:
my next step (take it for what it's worth - I'm sure there's an easier way) would be to unplug all usb devices (including keyboard/mouse - anything USB related), uninstall EVERYTHING under the USB Controller submenu, then restart and plug the phone in.
W7 should automatically recognize and reinstall the USB host controllers and hubs.
edit: are you using any other USB storage devices? thumb drives, ext harddrives, etc? do they work?
pmcqueen said:
that's a bugger.
when you plug the phone in, in device manager, does it show as a USB mass storage device under the USB controller section? to check: unplug all usb devices (aside from input devices like keyboard/mouse/what-have-you). plug in your phone and go to device manager (right click my computer->manage->device manager). under USB controllers, check and see if there is a USB mass storage device. assuming you have disconnected any other storage media, this is your phone.
if it does:
uninstall this driver, unplug your phone, restart, plug your phone back in.
if it doesn't:
my next step (take it for what it's worth - I'm sure there's an easier way) would be to unplug all usb devices (including keyboard/mouse - anything USB related), uninstall EVERYTHING under the USB Controller submenu, then restart and plug the phone in.
W7 should automatically recognize and reinstall the USB host controllers and hubs.
edit: are you using any other USB storage devices? thumb drives, ext harddrives, etc? do they work?
Click to expand...
Click to collapse
Under the usb section in device manager, i have about 8 or so usb controllers and stuff. Im using a Gateway Laptop and only one thing is using a usb port--- the mouse. Thats all. So i dont really have a clue which one is my htc phone because when plugging it in and going into device manager the only devices i remember using the phone were adb, android phone, and Now MTP. If i could pinpoint which usb controller is using my phone ill uninstall it. Other than that, what else is there? This is the strangest problem ever
Sent from my HTC Vision using XDA App
sighh, comeon guys. here ill post some pics of what is going on
Here are the pics of what is going on!!
Normal mode (no phone plugged in) - http://dl.dropbox.com/u/21509455/normal%20mode.jpg
Phone plugged in mode - http://dl.dropbox.com/u/21509455/phone%20plugged%20in.png
Uninstalled MTP & ADB driver Picture (looking for drivers) -http://dl.dropbox.com/u/21509455/phone%20uninstall%20drivers.jpg
Phone with ADB driver but no MTP - http://dl.dropbox.com/u/21509455/phone%20with%20driver%20found%20but%20no%20mtp%20.jpg
hope this helps , if you find something that can make this work let me know ASAP
140 views? and no one knows how to fix this problem?? anyone? hello?
jark99 said:
140 views? and no one knows how to fix this problem?? anyone? hello?
Click to expand...
Click to collapse
Have you tried the drivers from the official HTC Sync software? Also, are you actually trying to use the phone as an MTP device or as a USB mass storage device? I don't think you can use both at the same time (though I don't use this ROM so maybe things have changed). If you don't actually want the MTP functionality, I wouldn't worry about it.
Also, I noticed the notes for the ROM says "USB mounting is not working on a Windows OS computer" is a known issue. Not sure if that could be related...
ianmcquinn said:
Have you tried the drivers from the official HTC Sync software? Also, are you actually trying to use the phone as an MTP device or as a USB mass storage device? I don't think you can use both at the same time (though I don't use this ROM so maybe things have changed). If you don't actually want the MTP functionality, I wouldn't worry about it.
Also, I noticed the notes for the ROM says "USB mounting is not working on a Windows OS computer" is a known issue. Not sure if that could be related...
Click to expand...
Click to collapse
im trying to use it as a mass storage device, MTP isnt supposed to show up from what i read. but now it wont start without MTP
did you try what I pm'd you earlier today?
pmcqueen said:
did you try what I pm'd you earlier today?
Click to expand...
Click to collapse
windows 7 home doesnt have that script gpedit.msc
i looked all over google and it doesnt work . only pro and business versions have it.
Did the HTC Sync software not work? Also, have you tried formatting your SD card? Might be a long shot, but if it was ever used in MTP mode at one point, maybe your comp is detecting the files and thinking it's still an MTP device. Not sure if it works that way though...
Did you ever set the phone to MTP mode in the past? Like if you were ever on a Sense-based ROM. Maybe if you had it in MTP mode prior to flashing the new ROM, it stayed in it. Once again, no clue if it works that way since I've never used MTP on this phone before, but might be worth trying if you are out of options.
STILL havent fixed this MTP driver issue, have tried everything including the post above me!....NOTHING IS WORKING. why is it being recognised as mtp, when all i need is use the sd card.
this has been up for a week, seriously no one knows how to fix it?
jark99 said:
this has been up for a week, seriously no one knows how to fix it?
Click to expand...
Click to collapse
I'm guessing it's because no one else has encountered this problem before...
So what happened when you flashed back to a Sense-based ROM? I've never used one, but I thought when you connect the phone via USB, you have to choose what kind of connection you want (e.g., HTC Sync connection vs Disk Drive). Are you saying even when you choose to connect as a drive, the phone still shows up only as an MTP device (which I'm assuming is what is used when in HTC Sync mode)?
ianmcquinn said:
I'm guessing it's because no one else has encountered this problem before...
So what happened when you flashed back to a Sense-based ROM? I've never used one, but I thought when you connect the phone via USB, you have to choose what kind of connection you want (e.g., HTC Sync connection vs Disk Drive). Are you saying even when you choose to connect as a drive, the phone still shows up only as an MTP device (which I'm assuming is what is used when in HTC Sync mode)?
Click to expand...
Click to collapse
i switched to MIUI rom where i can mount sd card, and it still shows up as MTP in device manager on windows. Its not a rom issue, its a issue with WINDOWS seeing my device as a MTP and not STorage ....stupid windows 7.
jark99 said:
i switched to MIUI rom where i can mount sd card, and it still shows up as MTP in device manager on windows. Its not a rom issue, its a issue with WINDOWS seeing my device as a MTP and not STorage ....stupid windows 7.
Click to expand...
Click to collapse
Well either Windows sees your phone as an MTP device or the phone is actually reporting itself as an MTP device (not sure how it works on phones, but typically Windows communicates with firmware on a USB device to determine its classifications).
I'm guessing you already tried this since it's one of the only threads on the G2 forum when I did a search for MTP...
http://forum.xda-developers.com/showthread.php?t=901449
ianmcquinn said:
Well either Windows sees your phone as an MTP device or the phone is actually reporting itself as an MTP device (not sure how it works on phones, but typically Windows communicates with firmware on a USB device to determine its classifications).
I'm guessing you already tried this since it's one of the only threads on the G2 forum when I did a search for MTP...
http://forum.xda-developers.com/showthread.php?t=901449
Click to expand...
Click to collapse
Thankss i saw some of those. One method i didnt try, but ill try it and let you know how this goes. Thanks for the link
Sent from my HTC Vision using XDA App
Bumppp. Still no proper way to fix this!!
Sent from my HTC Vision using XDA App
anyone find any fix for this MTP ISSUE?

"Hardware ID doesn't match" error when plugging phone in

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

USB error PLEASE HELP!

USB will not function with my OnePlus 3, I've loaded drivers and still no avail.
templarsniper said:
USB will not function with my OnePlus 3, I've loaded drivers and still no avail.
Click to expand...
Click to collapse
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.
There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?
kenboyles72 said:
There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?
Click to expand...
Click to collapse
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.
TNSMANI said:
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.
Click to expand...
Click to collapse
I cant even root for the life of me now, Im on 8.0, I'm trying to just root the phone and to start the computer has to recognize it I understand but it won't, with my Oneplus 2 was fine,(I'm thinking maybe phone doesnt have the drivers built in to the file system, you know when you plug in and turn on MTP it shows the drivers app for Windows?) the only thing it errors plugging in.
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.
On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80
Fixed USB problem
kenboyles72 said:
On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80
Click to expand...
Click to collapse
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.
templarsniper said:
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.
Click to expand...
Click to collapse
If you are running Win 10, you will have to disable driver signing before the correct drivers are installed. May be that was your issue.

Categories

Resources