Related
Hy guys I've got a bit of a problem over here. I want to use my wildfire for testing apps as a emulator in eclipse. Problem is that in SDK manager cant ''find'' my phone. So far i download the USB driver package, revision 3. But when i connect to the computer the windows cant find the drivers in directory "....\android-sdk-windows\usb_driver". Then i installed HTC sync since it has usb drivers, but still i couldnt see it in SDK manager. I runned ddms where i'm able to see my phone. At the end i deleted the drivers and installed PdaNet, the result was the same.
I wonder what i'm i missing ?
Btw what option should i choise when i connect phone to the computer ? ( Charge only, HTC sync etc. )
And yes i set my phone to USB Debug mode
I'm using Windows XP SP3 & Wildfire is not rooted ( 2.1 android )
I hope my english is fine and thank you for your answers
Anyone ?
You windows xp is 64bit ? If yes, you can't install this. And if no, try install drivers from sd card.
No i use 32 bit system , but i'll try to install them for SD
Hi! I recently upgraded my SGS i9000 to CM7 but can't get drivers to work for adb. Everything worked fine on 2.3.3 stock rom. I tried installing every possible driver, even did `Reinstall drivers` option in Kies, also tried manual driver update, without success. Device manager just shows up yellow triangle.
Yes, USB Debugging enabled. File transfer mode works fine, only debugging isn't working.
Using:
- Windows7 x64
- Samsung Galaxy S i9000
- CM7-10112011-nightly on 2.3.5 firmware
Device manager - img542.imageshack.us/img542/4683/nodrivr.png
About phone - img683.imageshack.us/img683/8615/aboutfc.png
I have same problem. CM7 stable, win7 64bit, tested samsung drivers, android sdk drivers, nothing works.
I had the same problem, but this was the fix for me. You need googles USB driver, not Samsungs if you have CM7 installed. Open up your Device manager and find eighter an unknown device or Android Composite ADB device, chose "update driver software" and "browse my computer...". The driver is located in the adb\google\usb_driver\ folder.
Could be a good idea to chose uninstall and "delete driver software" to get rid of the samsung driver first.
Thank you so much!!! It worked lika a charm
Ah alright yeah i was havin the same problem too will try this method..im on stable cm7.1 and got a x64 windows ultimate and no drivers found for samsung galaxy s
Sent from my GT-I9000 using XDA App
hencke said:
I had the same problem, but this was the fix for me. You need googles USB driver, not Samsungs if you have CM7 installed. Open up your Device manager and find eighter an unknown device or Android Composite ADB device, chose "update driver software" and "browse my computer...". The driver is located in the adb\google\usb_driver\ folder.
Could be a good idea to chose uninstall and "delete driver software" to get rid of the samsung driver first.
Click to expand...
Click to collapse
Tried this before but no luck.
edit: I don't have that folder: adb\google\usb_driver\, but i have C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver, and when i choose that folder, windows says that device driver (unknown device) is allready up to date.
You might need to open up the SDK Manager in the adb folder and install Google USB Driver package. Not sure if it is included by default in the installed version of android sdk.
hencke said:
You might need to open up the SDK Manager in the adb folder and install Google USB Driver package. Not sure if it is included by default in the installed version of android sdk.
Click to expand...
Click to collapse
I don't have folder called "adb", SDK Manager.exe is in "C:\Program Files (x86)\Android\android-sdk".
I opened sdk manager and installed "google usb driver package rev 4", then in device manager -> unknown device i tried to update device driver and choosed dir called "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" but windows says that driver is allready up to date and it's still named unknown device.
In "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" i have these files and folders:
amd64
-NOTICE
-WdfCoInstaller01009.dll
-winusbcoinstaller2.dll
-WUDFUpdate_01009.dll
i386
-NOTICE
-WdfCoInstaller01009.dll
-winusbcoinstaller2.dll
-WUDFUpdate_01009.dll
android_winusb.inf
androidwinusb86.cat
androidwinusba64.cat
source.properties
In the update driver software dialog, where you set the folder, make sure Include subfolders is ticked. You can also try "Let me pick from a list...". Hopefully it will show Android Composite ADB interface. Else, untick "Show compatible hardware" and chose Android composite adb interface if possible.
THANKS
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
I have read lots of threads about installing managers and i have also tried installing them in my netbook but i could not install them.First of all, i turn on debugging then i connect my phone to pc and i download sdk.Then i install platform tools sdk tools etc and google usb drivers.Afterwrds i go to device manager and i press update driver in anroid device and choose the google usb drivers wich are located in extras>>usb_drivers.Then i think that drivers are correctly installed and i open a command prompt in the folder where is adb located and i press "adb devices " and it says just list of devices and a blank line without any device or serial number of device. What can i do now? I was hoping unistalling the drivers but i don't know how . Furthermore i have made many changes in my system in order to install them and i don;t know how to reset factory settings to my computer which may be one of the reasons why i can't install the drivers.What should i do ?
mitsos1996 said:
I have read lots of threads about installing managers and i have also tried installing them in my netbook but i could not install them.First of all, i turn on debugging then i connect my phone to pc and i download sdk.Then i install platform tools sdk tools etc and google usb drivers.Afterwrds i go to device manager and i press update driver in anroid device and choose the google usb drivers wich are located in extras>>usb_drivers.Then i think that drivers are correctly installed and i open a command prompt in the folder where is adb located and i press "adb devices " and it says just list of devices and a blank line without any device or serial number of device. What can i do now? I was hoping unistalling the drivers but i don't know how . Furthermore i have made many changes in my system in order to install them and i don;t know how to reset factory settings to my computer which may be one of the reasons why i can't install the drivers.What should i do ?
Click to expand...
Click to collapse
Do this:
install these drivers from here http://forum.xda-developers.com/show....php?t=1998650, extract the file with 7-zip. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4, choose installing/updating drivers and select the extracted folder of the 0.72 drivers, choose install and you`re done.
gee2012 said:
Do this:
install these drivers from here http://forum.xda-developers.com/show....php?t=1998650, extract the file with 7-zip. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4, choose installing/updating drivers and select the extracted folder of the 0.72 drivers, choose install and you`re done.[/QUOTE
the link does not work it says
404 Page Not Found
The page you requested was not found. Use the search tool below to find content on our site.
Click to expand...
Click to collapse
mitsos1996 said:
gee2012 said:
Do this:
install these drivers from here http://forum.xda-developers.com/show....php?t=1998650, extract the file with 7-zip. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4, choose installing/updating drivers and select the extracted folder of the 0.72 drivers, choose install and you`re done.[/QUOTE
the link does not work it says
404 Page Not Found
The page you requested was not found. Use the search tool below to find content on our site.
Click to expand...
Click to collapse
Sorry, here is another direct downloadlink http://forum.xda-developers.com/attachment.php?attachmentid=1489856&d=1353189747.
Click to expand...
Click to collapse
gee2012 said:
mitsos1996 said:
Sorry, here is another direct downloadlink http://forum.xda-developers.com/attachment.php?attachmentid=1489856&d=1353189747.
Click to expand...
Click to collapse
one last question ... whch file should i choose to be installed android_winusb or android_apxusb? is there any difference about bits(the one for x64 the othe x86)?
Click to expand...
Click to collapse
mitsos1996 said:
gee2012 said:
one last question ... whch file should i choose to be installed android_winusb or android_apxusb? is there any difference about bits(the one for x64 the othe x86)?
Click to expand...
Click to collapse
Just select the unpacked 0.72 file, do not select the x64 and x86 ones, to install as usb drivers. The right one will be installed automaticaly.
Click to expand...
Click to collapse
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar
fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.