I'm running cyanogenmod 7 on my evo 4g and when I plug it into a computer it only charges and never prompts me if I want to connect as a disk drive. It used to but now it just stopped. I had a backup of my rom so I put it on my girlfriends evo and hers still connected to the pc like normal but mine will not give me the option to hook up through USB. My computer says unknown device. Any help would be great. I can provide more info if you need.
More info. It gives me code 43 in windows 7. I was able to hook it up in xp but when I tried doing anything it no longer was able to detect the phone. I did a factory reset and it still doesn't work. I'm at a complete loss. I feel the only thing left to do is revert completely back to stock losing root and starting from scratch.
perhaps try completely uninstalling the device from windows in Device Manager. Then plug it in again and let it re-install the drivers
sitlet said:
perhaps try completely uninstalling the device from windows in Device Manager. Then plug it in again and let it re-install the drivers
Click to expand...
Click to collapse
I've tried that on two different computers with windows 7. My gfs fone reads fine with the exact same rom but mine wont.
It seems like the drivers on the phone are corrupted or something. At one point I found a forum that suggested to turn off bluetooth and a few other things. I decided to see if turning off my wifi would do anything and finally my phone showed the usb debugging notification and the mount as usb notification but it wouldn't mount so I restarted my phone and now it's back to doing nothing but charge the phone.
The only difference between the two phones is the rom then? Perhaps make a backup and flash a different rom or re-flash your current rom to see if that helps
sitlet said:
The only difference between the two phones is the rom then? Perhaps make a backup and flash a different rom or re-flash your current rom to see if that helps
Click to expand...
Click to collapse
I actually took a backup of my rom and put it on my gfs phone and hers worked. we had the exact same rom. I will try installing a different rom however and i'll let you know what happens.
Okay so I had a back up of sinister rom so I restored it and now it asks me if I want to connect as a usb device and so I do and my computer still says usb device not recognized or whatever.
Wow so I tried a backup of sinister rom that I had and suddenly it asked if i wanted to connect as a disk drive but windows was still saying usb device not recognized. I reverted all the way back to stock losing root privileges and it still doesn't work. It appears to me that it is a hardware problem. I don't know what else to do.
ok, so I hooked my phone up to a computer with ubuntu on it and my phone showed up but then when I went to explore the sd card it said permission denied. Then I hooked it up in windows 7 and it showed unknown device under universal serial bus controllers(as usual) but it also had it under modem, which is what I want.
Okay, got it working on this computer. After plugging the phone in several times it still said device not recognized. I have also been pushing ##data# and it was saying the same thing. I decided to shut my phone off one last time and when I hooked it up i pushed ##diag# and now it works. ****ing stupid. Glad it's working now.
UPDATE: Now all of the drivers install when I plug the phone in except the HTC DIAG doesn't appear even when i enter diag mode on the phone. this is the only driver i need installed but i can't install it because the computer isn't picking up that part of the device....This is getting irritating.
Turns out my port is ****ed up. I'm gonna have to order a new one and replace it.
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
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
mdamaged said:
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
Click to expand...
Click to collapse
Didn't work, followed your steps in the other thread. I guess I'll just have to wait until a flashable zip for L :/
edit- And btw I tried it on both of my hard drives, one with windows 8 and one with windows 7, didn't work on either.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
wantabe said:
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
Click to expand...
Click to collapse
Thanks mate, didn't work though so I'm not sure what is going on. I'll just wait until zips get created but thanks for the help guys.
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
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.