I have the android sdk installed and fastboot drivers, but in cwm I still have the small little yellow warning sign in my computer management window. Is there a set of development drivers I forgot to install on my pc? Or rather are they with the cwm sources?
Have you installed Sony Ericsson PC suite? There are no dedicated drivers required for recovery. Just the standard USB drivers.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk
No just the drivers for normal USB, drivers from google's development for adb and fast boot.
sent from my xperia play running CM9 thx to chevyowner
If you download FlashTool and install it, in the drivers folder it has compilation of all drivers necessary.
Also for the correct fastboot google usb driver, you also have to overwrite the inf file from here: http://dl-developer.sonyericsson.com/customROM/windows/downloadinf.zip
Also they probably prefer questions to be posted in Q&A section.
cj360 said:
No just the drivers for normal USB, drivers from google's development for adb and fast boot.
sent from my xperia play running CM9 thx to chevyowner
Click to expand...
Click to collapse
Just install the PC suite then and CWM will detect phone
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk
So this?
Thanks now I just gota fix my pc and find a way to get the drivers for my wifi card to work....
Related
I need the drivers to manually load on my comp for adb.
Does anyone know how i can get them or have them by any chance?
thanks...
I downloaded mine through Android SDK.
Go to "Android SDK and AVD Manager > Available Packages > Usb Driver package"
Sent from my T-Mobile G2 using Tapatalk
The regular android adb drivers don't work on all versions of windows. For example I know they don't work on windows 7 64 bit. Corylulu had this same problem and modified his drivers somehow, so now they work. They're on XDA somewhere.
Sent from my T-Mobile G2 using XDA App
Do a search.
If you install PDAnet you'll get all the drivers you need. Then just uninstall and keep the drivers.
+1
or google even reading is important...bricks are cheaper
ADB drivers
ddgarcia05 said:
Do a search.
If you install PDAnet you'll get all the drivers you need. Then just uninstall and keep the drivers.
Click to expand...
Click to collapse
Yes! this worked pefectly, TY!
Sorry to bring up an old thread, I installed PDA Net today to try to get this to work. So far no dice. I have also downloaded HTC_Driver_64 & HTC_Driver_32 and still there has been nothing that works. Could it be that these drivers do not work with CM-7.0.3-vision?
they work. no issue with roms.
try usbdeview and just uninstall all android drivers and be careful not to delete any drivers you specifically added for other things or else youll have to reinstall them. google that shizzle up "usbdeview" its also in cm wicky.
Sent from my HTC Vision using XDA Premium App
I should have mentioned that I am also on Windows 7 64 bit.
Since this last post I have been trying to update all of the drivers on this Sony VAIO VGN-CR190 laptop. Seems like I had some old drivers installed for the ports. Hopefully updating them will help the situation.
That usbdeview is a pretty cool program. I went and installed the x64 version, and did will see if it can help debug what the deal is with my USB connection. Thanks.
You can download HTC sync from here
That has the usb drivers and works on win7 x64
-Nipqer
Nipqer said:
You can download HTC sync from here
That has the usb drivers and works on win7 x64
-Nipqer
Click to expand...
Click to collapse
Thank you very much, that finally worked and I can now use AppInventor & Sync.
Saweet
Thanks for the help!! I installed the HTC Sync, followed the how to install instructions (found on the download link site), plugged my phone and then BANG! my pc installed the drivers.
In platform tools opened up cmd to test it out (did this by typing in "adb devices") BOOM! it recognized my device .
Disclaimer for the noobs: BANG and BOOM were written for the sole purporse of humorous effect and should not be interpreted as actual steps or file names.
how do i keep the drivers?sorry im new at this
trying to root my phone but htc synd dsnt recognise it.
ddgarcia05 said:
Do a search.
If you install PDAnet you'll get all the drivers you need. Then just uninstall and keep the drivers.
Click to expand...
Click to collapse
Uninstalling pdanet should keep the drivers, but if you follow the xda or cyanogen wiki you can download the proper ones from there. Otherwise strawmetals pdf guide will have the links too (many say his guide is the easiest to follow)
Sent from my HTC Vision using xda premium
Set your computer to dual-boot a Linux distro. You won't need the drivers, just a copy of 51-android.rules.
no matter what i try the semc hsusb device driver wont install. ive tried various drivers with no luck. anybody know how i can fix this?
i have that problem too on my win7 pc. the same goes for when i connect my hbh-mw600 via bluetooth to the pc.
guys, try to manually install the drivers from this link - it's a generic driver for windows(x86 and x64)
should work for you as well as I'm using it also on my windows 7 ultimate 64-bit
if it works for you, give thanks to the original source and OP of that thread
which usb driver should i be pointing at? that file has a few in it.
zombiej79 said:
which usb driver should i be pointing at? that file has a few in it.
Click to expand...
Click to collapse
When you connect your device, once pop-up showed that you don't have the driver, just manually point to the folder where you placed the files and it will automatically scan that folder for the drivers.
Sent from my LT15i using XDA Premium App
guys, try to manually install the drivers from this link - it's a generic driver for windows(x86 and x64)
should work for you as well as I'm using it also on my windows 7 ultimate 64-bit
if it works for you, give thanks to the original source and OP of that thread
i m trying to download for that link now.
Hey all, not really a big issue, but when I plug my device into my laptop, I can mount it as usb storage and move files etc but for some reason my computer notifies me that the device drivers were not found. Additionally, when I go to device manager on my laptop, it says "other devices" and lists 4 items saying Android. Like I said, not really a big deal for me, since I'm not pushing stuff using adb etc. but does anyone have any idea what's going on?
PS- I am running the awesome audio aokp rom build 1.3
Download the drivers for the phone on the computer
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
Download the drivers for the phone on the computer
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
where should i download the drivers from, i've already rooted my device and just out of curiosity i wanna start using adb
btw my computer already has samsung drivers installed
Just go to Samsung.com......you can DL drivers there.
I managed to install flashtool drivers on w8 64bit, but my pc does not recognize the arc s in fastboot mode. See attatchments
How to fix?
I installed drivers using this http://forum.xda-developers.com/showthread.php?t=2044804
Did You selected to install fastboot, flashmode and Xperia Arc drivers in "Flashtool Drivers Setup"? (C:\Flashtool\drivers\Flashtool-drivers.exe)
Maybe bad USB cable?
Maybe bad USB cable?
Yes, you have to install the driver first as @duona said
Sent from my Xperia Arc S using xda premium
I cant get adb drivers to work with 8.1. I've tried every driver in the book. Followed a few guides , erased drivers , reinstalled , even at one point tried reinstalling windows , different USB port, different cable . now I am no means a novice , but is there something simple I'm missing ? Any help appreciated
Sent from my HTC One_M8 using xda app-developers app
unbroken said:
I cant get adb drivers to work with 8.1. I've tried every driver in the book. Followed a few guides , erased drivers , reinstalled , even at one point tried reinstalling windows , different USB port, different cable . now I am no means a novice , but is there something simple I'm missing ? Any help appreciated
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
perhaps uncheck mtp and select camera and turn off debugging ? boot into recovery while connected ? that installs a driver also. have you installed a "naked driver " ?
unbroken said:
I cant get adb drivers to work with 8.1. I've tried every driver in the book. Followed a few guides , erased drivers , reinstalled , even at one point tried reinstalling windows , different USB port, different cable . now I am no means a novice , but is there something simple I'm missing ? Any help appreciated
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
been in your place it sucks @@
anyways, i dont exactly remember what was the solution but I think it was pdanet.
download it from here http://pdanet.co/a/ it should install the adb
hope it works
unbroken said:
I cant get adb drivers to work with 8.1. I've tried every driver in the book. Followed a few guides , erased drivers , reinstalled , even at one point tried reinstalling windows , different USB port, different cable . now I am no means a novice , but is there something simple I'm missing ? Any help appreciated
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Need more info about your problem. what happens when you type adb devices?
If I'm not mistaken there were a few people that had the same issue and it turned out to be a bug when trying to use a USB 3.0 port on their computers. If you are using a USB 3.0 port for your cable you might wanna try plugging it into a USB 2.0. FYI I could be remembering completely wrong
I did everything but an engineering hboot with USB 2.0 port on an Intel x79 chipset motherboard on Windows 8.1.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I had this problem too but got around it. I had no problem getting the device detected in Fastboot mode, but ADB was a problem. What I did was download and begin installation of the latest HTC sync manager with the phone already connected. It seems the first thing it does is install updated drivers then asks if you want to continue with the installation. I didn't want to install sync manager, so I cancelled the install. However the drivers remained. After a reboot I checked Device manager and sure enough Android 1.0 device was there with working drivers.
Checked the device was recognised with the ADB command ADB DEVICES, but showed no device connected. I then unplugged the USB cable and plugged in to another USB 2.0 port and voila device gets deteced by ADB.
I also had to use this version of ADB http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip and it had to be the original HTC USB cable and USB debugging enabled in Developer options.
Now for some reason I have to swap USB ports each time ADB doesn't detect the device and pretty much works each time.
I think it's usb3 issue , adb doesn't work on usb3 ports,
there was a subject on how to convert usb3 port into usb2 search the forums
USB 3.0 worked fine for me on 8.1. I used Sooner ADB drivers and manually picked them.
Sent from my HTC6525LVW
Ya usb3.0 worked for me too on two systems but I do know others had issues so I wanted to point it out.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I have no issues on win 8.1 I use the Google USB drivers that are with the sdk. The first time, I do have to go into device manager and update the driver. When it asks do you want to locate the driver or pick it from a list select pick from a list. There should be an Android entry if you installed the USB driver. Select that and then select adb interface. You'll also have to do the same for fastboot mode the first time.
Sent from my HTC One_M8 using Tapatalk
I couldn't find a working version of ADB for 8.1 however I installed HTC Sync from the virtual CD and that installed all the drivers. Uninstalled sync manager cos I don't use it and the drivers remain and work fine.
graffixnyc said:
I have no issues on win 8.1 I use the Google USB drivers that are with the sdk. The first time, I do have to go into device manager and update the driver. When it asks do you want to locate the driver or pick it from a list select pick from a list. There should be an Android entry if you installed the USB driver. Select that and then select adb interface. You'll also have to do the same for fastboot mode the first time.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
check your usb 3 controller. Is it intel 3.0 usb controller. if you see intel xtensible controller in device manager this could be the issue, it can break adb on all ports. here is a link to a fix for this usb problem i can confirm it works as i have had this issue myself. Hope this helps
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
Had the same issue when trying to achieve root. Booted Windows to advanced start up and disabled the driver enforcement and everything just went smooth from there. Drivers installed just fine and everything just worked.
Sent from my HTC One_M8 using Tapatalk
unbroken said:
I cant get adb drivers to work with 8.1. I've tried every driver in the book. Followed a few guides , erased drivers , reinstalled , even at one point tried reinstalling windows , different USB port, different cable . now I am no means a novice , but is there something simple I'm missing ? Any help appreciated
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
search for all-in-one-toolkit for the M8. it has links to installing drivers, u can use that toolkit to flash RUU, kernel, recovery, unlock bootloader and even run commands.
I used pdanet to install drivers for fastboot, you might wanna try it.
Sent from HTC One m8, or maybe not anymore
Rosch89 said:
Had the same issue when trying to achieve root. Booted Windows to advanced start up and disabled the driver enforcement and everything just went smooth from there. Drivers installed just fine and everything just worked.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
This is likely the issue.