Related
Hi,
I know there have been threads on this before but largely they just mention installing the Vista 64 bit drivers (done that). I'm running Windows 7 64 bit with the Vista 64 bit drivers and MCR 2.8 (although I was on stock and 2.2 with the same problem). HTC Sync on the phone just will not find it on the PC. I can mount the SD card with no trouble, just problems with Sync.
Any suggestions as to what I can do? Please feel free to direct me to another thread that I've missed so long as it's not just about the drivers.
Ta
M
martint235 said:
Hi,
I know there have been threads on this before but largely they just mention installing the Vista 64 bit drivers (done that). I'm running Windows 7 64 bit with the Vista 64 bit drivers and MCR 2.8 (although I was on stock and 2.2 with the same problem). HTC Sync on the phone just will not find it on the PC. I can mount the SD card with no trouble, just problems with Sync.
Any suggestions as to what I can do? Please feel free to direct me to another thread that I've missed so long as it's not just about the drivers.
Ta
M
Click to expand...
Click to collapse
In addition to HTC sync and the drivers, have you tried getting the android sdk? I know that I had issues with HTC sync finding my phone as well when syncing it to Win7 x64, so try following this guide here, it might allow HTC sync to view the phone properly. The guide teaches you how to setup adb-usb drivers which might trigger the application to know that your phone is there.
I had the same problem, turns out one of the task killer apps that I had been using had killed the sync process. Might be a plan to check if the same has happend to you.
Florida.
Hi Princedwi and Florida,
Thanks for the replies. I'm confident that my sync process is still running as I've tried numerous reboots of phone and PC so the task killer wouldn't have had chance to stop the process. However I will give it a go just to make sure.
Regarding the SDK, I'll try that when I get home. I used to have the SDK installed but then I did a re-install of windows and haven't bothered installing the sdk yet. May well work, I'll let you know.
Ta
M
Hi,
Ok tried it at home. The SDK isn't installing in the same way as I remember it doing last time. A DOS box flashes up and then disappears when I run SDK setup.exe.
Any other ideas?
Ta
M
2.0.18 is out now... should be W7 compatible -
http://www.htc.com/europe/SupportViewNews.aspx?dl_id=847&news_id=471
I had to install the Vista 64 bits drivers twice to get them working properly. The first time my hero appeared as "HTC Hero ADB". Rebooted, connected to USB, opened notifier, selected PC-Sync and reinstalled drivers (always choosing the folder where HTC should be leaving their drivers). This second time it appeared as "MY HTC" and it worked fine then. So just try again until you see the magic word "My HTC".
yrreP said:
2.0.18 is out now... should be W7 compatible -
http://www.htc.com/europe/SupportViewNews.aspx?dl_id=847&news_id=471
Click to expand...
Click to collapse
I've installed it today on my 7 64bit ultimate installation, and still no avail, i installed the vista x64 drivers and it worked.
Gr. B
martint235 said:
The SDK isn't installing in the same way as I remember it doing last time.
Click to expand...
Click to collapse
Because from android 1.6 setup process has changed in SDK. Normally it opens a windows from where you can add the version of android SDK you want and install the driver.
martint235 said:
A DOS box flashes up and then disappears when I run SDK setup.exe.
Click to expand...
Click to collapse
Same problem here with windows 7 64bit. Not sure if it's related to java environnement installed (For example when i installed JRE on my win7 64 the JAVA_HOME env variable was not set, i had to do it manually).
martint235 said:
Any other ideas?
Click to expand...
Click to collapse
Nope for now but if I found the problem be sure i'll post it here.
Ok I found the solution. My problem is that I've installed only the JRE but according to the requirements (developer.android.com/intl/fr/sdk/requirements.html) we need the JDK also.
So i've uninstalled the JRE 1.6 (64bit) I had, and installed the JDK 1.6 (32bit as i saw many ppl having problem with 64bit and android SDK). And it worked, I run againg the "SDK Setup.exe" and it opened the windows as intended.
I had the same problem, even with 2.0.18. what I did was install HTC Sync 2.0.18 (with the drivers copied in Program Files\HTC\HTC Driver\Vista_x64). then go to device manager, ADB interface, update driver, browse for a list of compatible software and choose My HTC.
after rooting it (although I'm not sure this is the cause) it happened now and then to fail to get recognized by the computer so I followed the same steps to update the drivers to My HTC.
I can't install HTC Sync 2.0.18, it gives an error about some resource file not found and closes. I tried on two different computers with the same result. Anyway 2.0.8 works fine here after I reinstalled the 64 bits driver until it was detected as "My HTC".
the same for me.
after update to version 2.0.18 my win7 64bit didnt find my phone anymore...
So, I've never had a problem with ODIN before, but today, while trying to ODIN back to stock (Obsidian V2 isn't working, so I'm seeing if that's the problem) I got the little Windows Error Message that says "USB Device Not Recognized" and then some other bull****. I know that I installed the Drivers (at least I think they were the right drivers) and I plugged into all 4 of my USB ports and still get the same message.
I had the same issue once. Try uninstalling the drivers you have and download and install a fresh set. That worked for me.
hmmm... I tried that (numerous times) and it still isn't working. All I get is "USB Device Not Recognized: One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." The drivers are installed, reinstalled, and re-reinstalled. I even tried to go in and change it to the right drivers myself, but no dice...
I had this problem, and got it fixed. Download the 64 bit drivers, you can find the link in the vibrant bible, and it should dl as a zip file. Unzip it on your pc, then from your windows device manager, reinstall the drivers for the unrecognized device, and point it at the 64 bit drivers folder you just unzipped. It should load the drivers and be recognized. If other devices also pop up, point them at the same folder. I did this oj a 32 bit win7 system and it worked great. Good luck.
Sent from my Vibrant running Macnut R10
kuhan said:
hmmm... I tried that (numerous times) and it still isn't working. All I get is "USB Device Not Recognized: One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." The drivers are installed, reinstalled, and re-reinstalled. I even tried to go in and change it to the right drivers myself, but no dice...
Click to expand...
Click to collapse
try a different computer, i have had this happen to me, google how to uninstall ghost drivers or hidden drivers.
Br1cK'd said:
I had this problem, and got it fixed. Download the 64 bit drivers, you can find the link in the vibrant bible, and it should dl as a zip file. Unzip it on your pc, then from your windows device manager, reinstall the drivers for the unrecognized device, and point it at the 64 bit drivers folder you just unzipped. It should load the drivers and be recognized. If other devices also pop up, point them at the same folder. I did this oj a 32 bit win7 system and it worked great. Good luck.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
Wait, I'm confused... what do you mean point it at the 64-bit drivers? I'm not much of a Windows guy...
djkdawg said:
try a different computer, i have had this happen to me, google how to uninstall ghost drivers or hidden drivers.
Click to expand...
Click to collapse
I've only got the one Windows machine at my house... I can't do anything else until my mom gets back into town this weekend.
Sorry I assumed you were somewhat of an advanced user. If you are using a windows system, download and unzip the 64 bit drivers I mentioned above. Access Windows device manager from the control panel to view the systems devices. The devices that are not loaded properly will be easy to identify. You the right click on the device, choose "reinstall driver", then "have driver file" (or something very similar, i don't have the specific verbage in front of me), and then select the folder where you unzipped the previously mentioned 64 bit drivers. It should then load the drivers and recognize the device. As a note, you should have your phone in dl mode and plugged in so that windows actively sees the phone.
Hope this helps and its not over your head. I work in IT sometimes my explanations can be too technical, but i tried not to do that here. If your near central colorado I'd offer some in person help at this point. Hope you can get it fixed.
Sent from my Vibrant running Macnut R10
Br1cK'd said:
Sorry I assumed you were somewhat of an advanced user. If you are using a windows system, download and unzip the 64 bit drivers I mentioned above. Access Windows device manager from the control panel to view the systems devices. The devices that are not loaded properly will be easy to identify. You the right click on the device, choose "reinstall driver", then "have driver file" (or something very similar, i don't have the specific verbage in front of me), and then select the folder where you unzipped the previously mentioned 64 bit drivers. It should then load the drivers and recognize the device. As a note, you should have your phone in dl mode and plugged in so that windows actively sees the phone.
Hope this helps and its not over your head. I work in IT sometimes my explanations can be too technical, but i tried not to do that here. If your near central colorado I'd offer some in person help at this point. Hope you can get it fixed.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
ah, thanks... I wouldn't call myself advanced... adept at best. Before I got the Vibrant, I was a HARDCORE Apple fan... Still an Apple fan, but not so hardcore lol
So I tried doing exactly what you said and it keeps saying "Your device drivers are already up-to-date" even though it still shows up as "Unknown Device" and already said "Device Driver Software could not be found"
Did you let it auto detect the driver or did you select have disk and then browse to the unzipped driver folder?
Sent from my Vibrant running Macnut R10
Br1cK'd said:
Did you let it auto detect the driver or did you select have disk and then browse to the unzipped driver folder?
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
I tried both.
At this point, the last advice i have is to completely uninstall all drivers for the galaxy s, from add remove programs, then reboot your pc and try the 64 bit installation again before reinstalling the normal drivers, if that doesnt work, see if you can use a friends pc, install the normal drivers and see if it works on a different computer.
Sent from my Vibrant running Macnut R10
I am having problems using Galaxy S3 i9300 4.1.1 with Windows 8 RTM x64.
I have installed Kies latest (2.5.0.12094_28). And i can see device is connected and i can even take backups. But when i am trying to send mp3 files it is giving an error "File Transfer from PC to 'GT-I9300' has been interrupted"
Also when the device is connected to PC via USB, i can see the contents in Windows Explorer but if i try to delete something, or upload a document there it says i dont have permisson.
With the same phone and PC, in Windows7 or XP there is no problem.
I have tried severel options like, "USB Debugging Mode", reinstall drivers, remove ghost drivers etc.
It just never worked for Windows8.
Any ideas or solutions?
I can tell you only: get used to it...nobody likes windows 8 and most likely even big companies will most likely slack doing drivers, even those who doesnt will yake their yime to make win8 drivers-dont get me wrong, i love win8, im running it since consumer preview
Sent from my GT-I9300 using xda app-developers app
Try the USB drivers as posted on XDA via Stickies .
jje
JJEgan said:
Try the USB drivers as posted on XDA via Stickies .
jje
Click to expand...
Click to collapse
Can you give a link? Do you have a working one?
Or are you just suggesting they might work? Cos i have tried some and all failed.
No links and no search they dont work on my PC .
jje
I mess about with stuff saved on my microSD card and phone very regularly with both my Windows 8 notebook (Release Preview) and tablet (RTM), connected by USB. My notebook has the Kies software installed, whereas the tablet doesn't. I don't have the problems you speak of.
On my notebook's Device Manager, with my phone plugged in, I have a category 'SAMSUNG Android Phone' with 'SAMSUNG Android ADB Interface' beneath it. Do you have that? My version of the driver is 2.9.503.726, dated 27/07/2012. On a side note, I also have the category 'Modems' with 'SAMSUNG Mobile USB Modem' beneath it.
Have you tried uninstalling the drivers, and letting Windows install suitable drivers for you?
aegixnova said:
I mess about with stuff saved on my microSD card and phone very regularly with both my Windows 8 notebook (Release Preview) and tablet (RTM), connected by USB. My notebook has the Kies software installed, whereas the tablet doesn't. I don't have the problems you speak of.
On my notebook's Device Manager, with my phone plugged in, I have a category 'SAMSUNG Android Phone' with 'SAMSUNG Android ADB Interface' beneath it. Do you have that? My version of the driver is 2.9.503.726, dated 27/07/2012. On a side note, I also have the category 'Modems' with 'SAMSUNG Mobile USB Modem' beneath it.
Have you tried uninstalling the drivers, and letting Windows install suitable drivers for you?
Click to expand...
Click to collapse
yep, it did not work.
I have Samsung Android Phone with ADB Interface as well as Mobile USB Modem
Which version of kies are you using? Did you install the drivers seperately or using the ones that come with Kies?
Im also on legit W8 x64. No problems for me. I dont even have Kies. Lol
Sent from my GT-I9300 using xda app-developers app
I also use 64x Win8, everything's fine. Try different drivers, maybe those from the S3 All In One Toolkit
Similar problem here, using a HP Elite book with Windows 8 (My Win7 machines and 10.7 Mac have no issues)
I am in the process of trying some drivers to see if they solve this problem.
Search for galaxy s3 toolkit andbinstall the drivers in that package they deffiniyely! My main build machine is runninh win8.1
Sent from my GT-I9300 using XDA Premium 4 mobile app
Howdy.
I recently updated my YP-G1 from CM10 to CM 11 [4.4.2]. I need to use my device for Android app development (and have used it before way back when it was on stock, but haven't used it in a very long time), but am unable to get ADB/Eclipse to detect that there is a device detected. Using the emulator is not an option at this point, as I need to do some work with a real camera.
I've got the Android USB debugging enabled on the device, and the little notification that debugging is enabled comes up when I plug it in.
Things I've tried:
1) Update Eclipse/ADT (complete uninstall + reinstall)
2) Update Google USB Driver (from SDK manager)
3) Update Samsung Kies
4) Google
The only related forum thread that I've located for this situation is: http://forum.xda-developers.com/showthread.php?t=1776828, which just implies that Windows should be auto-detecting the device. Windows is not doing that.
I have noticed that the YP-G1 drivers do not show up as installed under Device Manager. Perhaps that is the source of the problem? I have not been able to rectify that situation via Kies, so I am unsure. Kies doesn't even detect that the device is connected!
If it matters, I'm running on Windows 8.
Thanks much.
P.S. -- I'd post in the CM11 thread, but since I just registered, I am not allowed to do so, unfortunately.
Edit: I got mine to work finally. I solved my issue by allowing windows to automatically search windows updates for drivers. After I did that it found them and it worked, so try that.
I too am having this issue and it's really bugging me. I've tried everything I can possibly think of but I cannot get the drivers to install. I'm using windows 7 64 bit and it sees the YP-G1 but it doesn't have the drivers so things like kies and adb won't detect it. Any solution would be very helpful.
Strange...that's what the thread I linked to suggested. I've tried that multiple times to no avail. Perhaps Windows 8 doesn't find it, while 7 does for some reason? I've tried doing searches via both Device Manager and Windows Update.
Could you perhaps upload the driver files it found? You should be able to figure out what/where those are by using Device Manager, then right click the YP-G1 and go to Properties, then the driver tab, then driver details. Maybe they'll work on Windows 8 as well as 7. I might try plugging my device into someone else's computer to see if somehow mine is just acting stupid.
Thanks for your reply!
Edit: I've plugged my device into another computer. You're right -- on Windows 7, it can find the drivers just fine. On Windows 8, it can't. Go figure. Now to figure out where to get those files and/or how to get the device recognized..... (??)
Anybody else got problems with connecting to the PC with the USB cable?
What "problems" are you having?
The Windows Explorer does not start, though there is the sound when connecting the USB. Tried uninstalling the driver and letting the system reinstall upon connecting, but still cannot see Nexus 9 in Windows explorer. In Linux get the the notification and clicking on the "open with File Manager" gives a quick error message - too quick to read. So I am wondering if anyone got this problem??
Sent from my Nexus 9 using Tapatalk
Same here
I updated my SDK files, but that didn't seem to work either. It does show up as a camera when I change from MTP, so I just started sideloading apps, files, and books to the picture folder, then using a file explorer to move them to the correct folder.
+chuckie59 So I am not alone with this problem! Have used AirDroid to copy things over.
Sent from my Nexus 9 using Tapatalk
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Same for me. Only ptp working. Google USB ADB drivers instaled
mkygod said:
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Click to expand...
Click to collapse
You'll never get it to show up as a driver letter. Android gave up on mass storage a couple of versions ago.
Sent from my Nexus 9 using XDA Free mobile app
If you are on W8.1 then you may have the "ACER Composite ADB Interface" - A Microsoft upgrade fault.
A search for "ACER Composite ADB Interface remove error delete" should give plenty of hits. Here's the first post from http://forums.androidcentral.com/google-nexus-7-tablet-2012/362325-nexus-7-not-recognized-computer-2.html :
Would you happen to know if any Acer drivers are installed on your computer? Here recently there was a Windows Update that installed the wrong driver and made it so that I had the exact same problems as you're having. Here's how I fixed it.
Go To> Control Panel>Hardware and Devices>Device Manager. In Device manager look for something along the lines of "ACER Composite ADB Interface", at least in my case I had the wrong ADB interface installed. You'll know if you have the wrong drivers if you go to Devices and Printers and right click your Nexus 7 and go to it's properties. It should be under the hardware tab where it lists it. If it doesn't just say Nexus 7 then follow these instructions. Once you find it in the Device Manager (once again in my case it was the ACER Composite ADB Interface causing the issue) right click and and uninstall it. There should be a dialogue box that pops up right after which will ask you if you want to delete the drivers. Check this box and proceed with the uninstall. After successfully uninstalling the drivers plug in or unlplug and plug back in your Nexus 7. It should show up now with the correct drivers installed.
Thanks, but I am on Windows 7. Driver is ClockworkMod Ver 7.0.0.1 dated 2012-08-27, which Windows reports as up to date (?). Works for PTP but not MTP.
I have had problems with other devices including the nexus 5 and nexus 10 to connect over mtp. Previously i used the nexus root toolkit which has some wizard to guide you to install proper drivers for mtp and adb. The toolkit is yet to support nexus 9 but you can still use the wizard to uninstall the old drivers and reinstall correct ones
Updating sdk. Uninstall and installing again driver did the trick for me
SORTED!! (sort of) Updated sdk and uninstalled and installed the driver again, but it did not do the trick for me. Gave up on Win7.
Instead had a go on XP. Initially everything the same. Noticed two choices of compatible hardware given: "Google Nexus ADB Interface" (the one I had installed already) and "USB Composite Device". Tried the latter one, and yes it did install. In the device manager it turns up as "Portable Device/Nexus 9" (and not as "Android Phone/Google Nexus ADB Interface" as before).
In Windows Explorer it is shown as "Nexus 9/Internal storage" with all the directories, and actually when inserting the USB I do get auto start. By the way, was having the USB debugging disabled. The driver is Microsoft dated 2006-02-22 version 5.2.5326.4762 - which is not what I would have expected. But it works!
Will try to get something similar to work on Windows 7
SORTED! Yes also Win 7 - and it was easy. Uninstalled the driver, plugged in the USB and it installed! Also got the auto start to choose action. It now turns up as "Portable Devices/Nexus 9" in the device manager and as "Nexus 9/Internal storage/etc" in Windows Explorer. The driver is now Microsoft ver 6.1.7600.16385 dated 2006-06-21. Strange. As long as it is working!