Related
I bought a new laptop and it's 64 bit running Windows 7. I'm trying to install the 64 bit USB driver & get it to recognize my phone but it simply won't work.
The following two things keep running and running with the words "installing driver software" after them:
CDC Abstract Control Model (ACM)
S3C6410 Android ADB
I have no idea how to get this to work so any advice is greatly appreciated!
ps - USB debugging is checked in my application settings.
There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!
musclehead84 said:
There are lots of people having problems with 64 bit windows nit recognizing the epic. My suggestion is to try.another USB cable. I use my wife's evo cable and it works fine for me. Good luck man just keep trying. Try different ports, cables and also check.to.make sure the USB slot is clear from any obstructions.
Sent From My Evo Killer!
Click to expand...
Click to collapse
I've done all those things.
Install the 32-bit drivers even if you're on a 64 bit computer
iSaint said:
Install the 32-bit drivers even if you're on a 64 bit computer
Click to expand...
Click to collapse
I was going to try that but didn't want to screw anything up...so that should work then?
droid newb said:
I was going to try that but didn't want to screw anything up...so that should work then?
Click to expand...
Click to collapse
Yes, I have 64bit computer and mine works with 32bit drivers.
Doing the same thing with 32 bit that it does with 64 bit.
droid newb said:
Doing the same thing with 32 bit that it does with 64 bit.
Click to expand...
Click to collapse
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck
jdelano said:
Here is a link to the drivers I installed on my Win 7 Ultimate 64bit machine. (i put them on my google documents site)
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I have had no issues using odin or mass storage.
Hope this helps, good luck
Click to expand...
Click to collapse
That's the same one I've been trying all this time. I just don't understand why this won't work.
The ACS Module has never installed for me but my device works fine
watermoore said:
The ACS Module has never installed for me but my device works fine
Click to expand...
Click to collapse
So would you be able to Odin back to stock if you needed to?
droid newb said:
That's the same one I've been trying all this time. I just don't understand why this won't work.
Click to expand...
Click to collapse
When you ran the setup for the driver, did you run it as administrator?
Right click on setup.exe and select that option from the menu.
Sorry you're having such a bad time, that has got to be mega-frustrating.
I've read also, that some people run the 32 bit drivers on win 7 64bit and they report that they work for them just fine.
hey man i feel your pain. I have been having the same exact problems as you. I also have tried the 64 bit/32bit drivers, uninstalling/reinstalling them, everything i can think of or have been told to do to no avail. It use to work fine until i got the first froyo update eb13 and ever since its been like this. My laptop keeps telling me to replace my device.
I did get on a computer at work with win XP and i plugged my phone into it and the device installed but im not sure about the drivers. Im limited to what i can do at work. So maybe it has something to do with windows 7 cause my laptop is brand new as most people having this problem are to.
Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.
I just had this problem recently. It wasn't the drivers - instead, it was the USB port I was using. If you're on a desktop, try a usb port on the back of the pc. If you're on a laptop, give all the usb ports a go.
Sent from my SPH-D700 using XDA Premium App
I am on a laptop and i have repeatedly try all usb ports and still a no go. It really seems like something changed after EB13 cause i never had a problem before.
dazednconfused1144 said:
Did the drivers change after the EC05 update. Neither of my computers will recognize my phone now after I updated the modem. I even tried reinstalling the links you have in this post and updating drivers and still a no go.
Click to expand...
Click to collapse
Nope; I have a win7 ultimate 32 laptop and a win 7 ultimate 64 desktop. Both see my phone just fine. Same drivers from when I first rooted after xmas to DK28 from 2.1.
I have heard of people having an issue with something bent on the phone's usb connector, it stops from getting full connection.
I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...
jerbeck24 said:
I'm having the same issue, but I can connect when I uncheck USB debugging. With it checked, it won't connect. I'm trying to root with 2.5.5...
Click to expand...
Click to collapse
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!
droid newb said:
That worked!!!!!!!!!!!
Wooooooooooooooooooo!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
No problem...problem for me is, it needs to be checked in order to root...
I'm just going to odin back to EB13 and CWM3 and restore my latest back up of ACS 1.0.2
OS: Windows 8 x64
Phone: Verizon DINC2 rooted with CM9
I rooted and flashed my phone on Windows 7 with no issues. Windows 8 will not recognize my phone. Device manager shows: Other devices->Android Phone with a warning symbol over it.
I've tried installing HTC sync
I tried installing Win7x64 drivers via this method: http://forum.xda-developers.com/showthread.php?t=2232799 but I get an error message saying "Windows was unable to install your Android Phone"
I've tried using different USB ports (non 3.0) and different USB cables and still nothing. Could this be a ROM issue, I know CM7 is the only one officially supported for DINC2.
Has anyone else had any luck with Windows 8?
NamesTwister said:
OS: Windows 8 x64
Phone: Verizon DINC2 rooted with CM9
I rooted and flashed my phone on Windows 7 with no issues. Windows 8 will not recognize my phone. Device manager shows: Other devices->Android Phone with a warning symbol over it.
I've tried installing HTC sync
I tried installing Win7x64 drivers via this method: http://forum.xda-developers.com/showthread.php?t=2232799 but I get an error message saying "Windows was unable to install your Android Phone"
I've tried using different USB ports (non 3.0) and different USB cables and still nothing. Could this be a ROM issue, I know CM7 is the only one officially supported for DINC2.
Has anyone else had any luck with Windows 8?
Click to expand...
Click to collapse
Sorry, but i'm not surprised. Win7 drivers. Are you technical? MIght be able to work with it though.
right click on the file and look at my screenshot. I'm not sure how win8 is different, but that might work
sjpritch25 said:
right click on the file and look at my screenshot. I'm not sure how win8 is different, but that might work
Click to expand...
Click to collapse
I installed the HTC 4.0 driver in compatibility mode, then in device manager added legacy hardware. Phone shows up as My HTC under Android USB Devices now, but I get error Code 10 device cannot start in device manager.
Bummer. I'm out of ideas until that driver is updated to win 8
Sent from my ADR6350 using xda app-developers app
sjpritch25 said:
Bummer. I'm out of ideas until that driver is updated to win 8
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
Doubtful that it will ever be updated since it is such an old phone now. Thanks for trying to help anyway though.
When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?
Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app
Disregard. I figured it out. It was a driver issue after all.
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.
thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
fixed mine by just forcing it to reinstall the drivers.
fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.
Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app
To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.
hi, i have problem connecting my arc s in fastboot to flash kernel i install drivers but windows say Unknown USB Device
is fix on the way
Doktor-X said:
hi, i have problem connecting my arc s in fastboot to flash kernel i install drivers but windows say Unknown USB Device
is fix on the way
Click to expand...
Click to collapse
same here
same
the same
The same
http://flashtool.net/disabledrivers.php
Someguyfromhell said:
http://flashtool.net/disabledrivers.php
Click to expand...
Click to collapse
Yeh tat didn't help..
as suggested in another forum, i disabled one of my usb root hubs in the device manager....it didnt give me that enumeration error and installed the driver but my pc only detects my phone in flash mode(even though i press the button for fastboot)...
It's a common problem with the fastboot drivers at the moment.
The really strange thing is that things still don't work properly if you have 8.1 with XP running in vmware.
Hopefully some smart cookie will work it out
Sent from my Xperia Arc S using XDA Premium 4 mobile app
try
i'll try this thanks
The same problem. I tried UpdateService and PCC , it still does't work!
Someguyfromhell said:
Apparently something was changed in 8.1, making the current method useless.
For now, nothing can be done, you will just have to wait until a new solution is made or move back to Windows 8 or any previous OS.
Click to expand...
Click to collapse
There is no known solution at the moment. Just wait until a solution is found or return to older version of Windows.
i m also having have problem ... in sonypcc its given unable to connect change to window 7 r later
altshift said:
i m also having have problem ... in sonypcc its given unable to connect change to window 7 r later
Click to expand...
Click to collapse
PCC works perfectly on Windows 7.
Someguyfromhell said:
PCC works perfectly on Windows 7.
Click to expand...
Click to collapse
bt mine is window 8.1
hi
my phone is Xperia Mini and recently i update to windows 8.1 .
but when i want conect it in flash mod or fast boot ,
the windows say "usb devise not recognized"
what have to do?
cmureza said:
hi
my phone is Xperia Mini and recently i update to windows 8.1 .
but when i want conect it in flash mod or fast boot ,
the windows say "usb devise not recognized"
what have to do?
Click to expand...
Click to collapse
Use another PC, which has earlier version of Windows. There are no fastboot drivers, which work with Windows 8.1, nor there is a solution to make the older ones work.
http://forum.xda-developers.com/showthread.php?t=2095087
This might help
esarve said:
http://forum.xda-developers.com/showthread.php?t=2095087
This might help
Click to expand...
Click to collapse
Works on Windows 8 but not on Windows 8.1.
Someguyfromhell said:
Works on Windows 8 but not on Windows 8.1.
Click to expand...
Click to collapse
If you have usb 3.0 you can try it is working http://forum.xda-developers.com/showthread.php?p=46997772
Sent from my MT11i using xda app-developers app
I found this guide - http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
I have USB 3.0, but I don't use Intel-based stuff. Maybe if I update to 8.1, I might try. For now, up to you to test, if you are willing to.
hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help
sergio1231 said:
hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help
Click to expand...
Click to collapse
I have the same problem. I fixed it before on my nexus 10 by trying a different kernel. Let me me know if it helps.
Sent from my Nexus 7 using XDA Premium HD app
Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app
Jhall8 said:
Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app
1
I'm telling you that there is no firmware on the tablet. what do you advise.
sergio1231 said:
I'm telling you that there is no firmware on the tablet. what do you advise.
Click to expand...
Click to collapse
Plug it in to a computer.
Boot into recovery if you have one
Adb devices......hopefully it shows and work from there.
Or boot into bootloader mode (after getting the twrp IMG)
Fastboot flash recovery......
Then you can side load your favorite OS
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #
jblaze10 said:
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #
Click to expand...
Click to collapse
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ur right, I wish I knew more about it. I'm in that phase now where I'm digging thru Xda for info such as adb backups among other things. Hey no prob, take it easy.
Sent from my Nexus 7 using Tapatalk