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
Hi,
after getting my Note 2 LTE back from repair (they changed the mainboard, speaker, vibrator and USB port) I'm now trying to root it using Odin 1.85 (have tried 3.07 too) and CF Auto Root. The problem is that neither the phone nor the PC detects any USB connection at all while in download mode, ie. it doesn't even pop up with a driver request or anything. Device manager doesn't show any change in devices either. In this case the old "nothing happens" truly applies...
I've tried with going into download mode with voldown+home+power and with 'adb reboot download', with the only difference between the two is that when using ADB it doesn't display the white text in the upper left corner.
The PC runs Windows 7 (I used this same machine to root the phone when I got it back in November, and I haven't changed anything on it, other than the usual software updates). I've tried two cables that both work when connecting the phone while booted normally. The one I'm using now worked fine to transfer about 1 GB of pictures back to the memory card.
It's running the latest 4.1.2 (JZO54K.N7105XXDMC3) and is fully charged.
EDIT: I've now tried with uninstalling Kies and the Samsung USB drivers completely but the problem remains.
Thanks,
Magnus
Note 2 Android 4.1.2 download mode connect to PC
I have the same problem. Although your post is old, yet unanswered, I'm not sure if im posting correctly, or must create a new thread.
I connected my Note 2 to PC-USB during download mode. Also no action, but device manager showed a yellow triangle, while Odin running and pointing to a file for rooting.
I read in a post once that upgrading to Android V4.1.2 prevents rooting. How can I degrade it?
Phone connects successfully in normal mode.
Samsung Galaxy Note 2, SGH-T889 of T-Mobile (locked to carrier). Android V4.1.2
Tried on 2 PCs with Windows 8.
Also tried turning phone on to Download Mode after plugging it to USB.
I tried unlocking it, the unlocking software required phone to be rooted first!
Completely new to android. Regular mode, pc recognizes easily. Download mode, not at all. No unknown device. If on the Note I pick "upgrade from adb" then the pc devise manager shows a samsung device adb device. So, it sees it. but still Odin does not see it. Tried USB debug mode on/off on the tablet. Restarted PC and tablet several times. Using original usb cable, tried various usb ports. Am I missing something obvious? I feel that I am.
I would install kies from samsung. Completely reinstall drivers from with in kies and go from there. You could actually push the recent update from kies to your tab and that will do it in odin mode. Give it a try…
Sent from my SM-P600 using Tapatalk
Bizack said:
I would install kies from samsung. Completely reinstall drivers from with in kies and go from there. You could actually push the recent update from kies to your tab and that will do it in odin mode. Give it a try…
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Using Windows 7,
Uninstalled Kies 3, reinstalled, updated, uninstalled/reinstalled all drivers. Tried usb debugging on/off (which changed the drivers) Odin perfectly detects the tablet in regular mode. In recovery/download mode I still don't even get an unknown device. It sees the Samsung Adb device, but neither kies (though maybe it shouldn't) nor odin "see" the device. Tried various usb ports, multiple computers. I am on most recent firmware for the P600
Working with tablets (first ipad 2, now the new note) make me feel like I know nothing about computers.
beleghm said:
Using Windows 7,
Uninstalled Kies 3, reinstalled, updated, uninstalled/reinstalled all drivers. Tried usb debugging on/off (which changed the drivers) Odin perfectly detects the tablet in regular mode. In recovery/download mode I still don't even get an unknown device. It sees the Samsung Adb device, but neither kies (though maybe it shouldn't) nor odin "see" the device. Tried various usb ports, multiple computers. I am on most recent firmware for the P600
Working with tablets (first ipad 2, now the new note) make me feel like I know nothing about computers.
Click to expand...
Click to collapse
Recovery and download mode are two completely different things. If you are in recovery then Odin will not see the tablet. You have be in download mode. Power the device off and restart it by holding down the power button and volume down at the same time. If you hold power and volume up you will go into recovery which does you no good for Odin.
nrage23 said:
Recovery and download mode are two completely different things. If you are in recovery then Odin will not see the tablet. You have be in download mode. Power the device off and restart it by holding down the power button and volume down at the same time. If you hold power and volume up you will go into recovery which does you no good for Odin.
Click to expand...
Click to collapse
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
beleghm said:
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
Click to expand...
Click to collapse
Samsung is the only manufacturer I have used that does download mode. Most others have bootloader mode that works with adb. Though using Odin is easier for beginners than adb.
Sent from my SM-P600 using XDA Premium HD app
beleghm said:
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
Click to expand...
Click to collapse
i don't know what the hell is going on here... mine won't work
i have the note 3 and it works fine, i just re downloaded and reinstalled kies 3, kies will recognize the tablet when it is booted normally
as soon as i boot into download mode, odin won't see it.
what gives? i have usb debugging on, i can't figure this out, what am i missing, as im sure it is super simple....
asaqwert said:
i don't know what the hell is going on here... mine won't work
i have the note 3 and it works fine, i just re downloaded and reinstalled kies 3, kies will recognize the tablet when it is booted normally
as soon as i boot into download mode, odin won't see it.
what gives? i have usb debugging on, i can't figure this out, what am i missing, as im sure it is super simple....
Click to expand...
Click to collapse
For me, I had to use the old Kies, not Kies3. I didn't even get a device showing up in device manager when USB Debugging was enabled, though if i switched USB mode from MTP to Camera, I would get a device Samsung_Android that looked like it wanted ADB drivers, but manually pointing it to the drivers included with Kies3 didn't work.
beleghm said:
Completely new to android. Regular mode, pc recognizes easily. Download mode, not at all. No unknown device. If on the Note I pick "upgrade from adb" then the pc devise manager shows a samsung device adb device. So, it sees it. but still Odin does not see it. Tried USB debug mode on/off on the tablet. Restarted PC and tablet several times. Using original usb cable, tried various usb ports. Am I missing something obvious? I feel that I am.
Click to expand...
Click to collapse
I have a sm-p600 that has been rooted and had a custom rom on it. I went to change the resolution and it rebooted and then i got a bootloop and now i am unable to get into my custom recovery and i cannot connect through adb or in download mode with no unknown device message as well. any suggestions to fix this would be appreciated.
Make sure Kies isn't running in the background, it screws with ODIN....
Hi All, sorry this is a fairly long post.
i recently "Upgraded" my SM-P605 to Android 9 and it has been working fine.
i have, however, been experiencing connectivity issue with file transfer via USB.
i have tried several cables (3 Genuine) including a brand new "Generic" cable and keep getting the "device descriptor request failed" error.
i have also tried multiple PC's, loaded all recommended Samsung drivers and finally relented and replaced the USB port in the tablet itself, which still did not fix the problem.
Convinced after all of this it must be software related, i then decided to re-install and earlier version of Android which i copied over to the Tablets internal memory.
i logged into TWRP and wiped the tablet ready to reinstall Android 7. and when i tried it says the zip file is corrupted.
i now have a tablet that wont load the zip file i have, wont read from an SD card in the tablet or OTG (via TWRP) and is unable to connect to a PC via a usb cable..
if anyone could offer any suggestions i would be extremely grateful as i dont want to "Dump" this tablet as i use it daily for work..
Why it does not read the SD card? I would expect that should work and should be the safest bet here...
-Maybe the zip file really is corrupt, which can be easily told by unpacking via pc.
-If the tablet can still charge the battery usb is most likely okay.
-Sdcards can fail by becoming read-only. Most easy to tell by unsuccessfully trying to format them in the tablet or pc , but e. g. under Windows you seemingly can successfully delete and copy stuff, everything as it should even after forced refresh via F5. But after reinserting the card or rebooting the previous state is back.
-ADB has been enabled in developer settings? Then you normally get a notification where you can modify usb mode. Charge-only won't work, but most of the rest should do (Dcim/mtp/msp...) .
-And all the time Windows has to recognize the device via PnP and auto-install drivers for the current usb mode. Besides the aforementioned storage drivers for flashing and communication a modem driver and virtual COM ports must be auto-installed.
In this department i had lots of trouble with a phone based on an old TI OMAP SoC under any Windows newer than seven. Only Download mode invoked on the phone itself was still working and only zseful to restore stock rom, while in the more flexible Fastboot mode the phone wasn't recognized by Windows.
Samsung devices seem to support Fastboot only, but call it Download mode.
To come to an end, if everything fails i'd recommend to install stock rom in "download recovery" (Fastboot?) mode via Kies. If this also fails try to put the P605 manually into Download mode (Power and Volume minus or plus), no need to press home button, as often advised. After this, work your way back to Twrp, custom rom and root.
@crwzar80
Try connecting the tablet to a Windows 7 PC/laptop, making sure it's on an Administrator account (so it can autoload/download needed stuff). Not Windows 10 or even 8.1, but Windows 7.
I had the same problem a while back ago; if your attempt with this method succeeds then report back; I had an unconfirmed hypothesis about this issue.
Hi
I would appreciate any input/help on this issue.
I bought the Korean Note 10 + 5g exynos (SM-N976N), specifically for the purposes of being able to root it. I would prefer to use the Magisk approach, because I would like to be able to use Google Pay, amongst others
Try as I might, I cannot get my PC to "see" the android phone. I have engaged developer mode, checked USB debugging, checked the the USB connection as MTP mode, and gone through several cables, going by the advice of "experts" I consulted. I even went as far as returning my original phone and buying a new one, again, on the advice of an "expert" who determined that my original phone was faulty (unlikely, since I had literally taken it out of the box and attempted the rooting before trying to load my multiple software). I am using Windows 10, 64k, with all current Microsoft updates.
I have reloaded the Samsung USB drivers, rebooted both the phone and PC several times, to no avail. When I connect, in download mode, the USB cable between the two devices, I hear the "ping" on the PC, indicating that the two have made contact, but then - nothing. I have established that the cable works fine, by connecting my Note 8 to the PC, where it shows up as a device with two drives (int and SD card)
I have installed Magisk on the 10+, and modified the stock ROM with Magisk, and then copied that over to the PC, as advised by the rooting solution; the problem is that I cannot use Odin to flash that modified ROM because Odin does not recognize any phone attached to it!
Help, Please!!
Could be the Odin version your using
Perhaps, I hadn't thought of that. I am using 3.13.1. Do you have a suggestion about using a more stable/useful one? My only issue with your answer is that it's not just Odin that isn't responding- it's the entire computer - it's as if the phone doesn't exist when connected.
I'm guessing you are using a USB 3.0 port on pc? If you have access to USB 2.0 try that....
Next thing I'd suggest (with note plugged in while in download mode)....go into device manager (right click This PC)
Find device under Modem, open properties Ports tab, Advanced Settings and manually change the port setting to a lower port assignment (preferably between 1 & 5). Reboot pc and just for kicks reset the phone into Download Mode again....Give odin a try now.
Hope one or a combination of these methods help.
Sent from my [device_name] using XDA-Developers Legacy app