Anyone have a line on how I can get this?
Do you mean an adb driver for USB debugging support? If so, I've found that if you install the PDANet client for your version of Windows, it installs a driver that ADB likes. You have to make sure to uninstall the Dell PC Suite first though, if you have that installed.
as far as i'm aware (i'm running win7 atm) there are no specific windows 7 drivers.
Just download the latest Android SDK and run adb from there. Works a treat.
Just install the Dell PC suite. You'll need to restart. after your pc restarts it should be fine. I did this yesterday when I bricked by streak. fastboot = annoying.
Synyster_Zeikku said:
Just install the Dell PC suite. You'll need to restart. after your pc restarts it should be fine. I did this yesterday when I bricked by streak. fastboot = annoying.
Click to expand...
Click to collapse
If the process you used caused you to "brick" your phone, why would you suggest others to follow??? If it didn't work for you, it most likely wont work for others...
Still no luck getting this to work.
go to device manager choose android 1.0 or whatever its called, choose to update drivers, manual option, the bottom option, have disk, choose the folder with the usb drivers from the sdk and then select android.
the drivers work fine then..
if you're trying to get pcsync to work then this isn't related
download Fastboot.exe & Koush's Recovery > unzip to your c:\ , renaming to something like c:\streak ...... Go to control panel>system>device manager ...... rigght click "android 1.0" > let me pick > show all devices > Android phone or Google INC ( i didnt find Google INC in mine , only found Android phone ) > Android Bootloader Interface
It will the bring up a warning , just click "ok" and it will bring up another dialogue saying the device is installed successfully
Hope this helps
Related
Hi.
I have a cracked screen (soon to be fixed) Dell Streak 5.
When I connect it to my PC it detects it as USB Input device and install the driver for it.
If I try to change the driver and use QDL Tool Windows says the @location does not have hardware information). I tried Windows 7 and XP with the same results.
MAC and Linux detects it as Qualcomm but there is nothing I can do as there is no ADB server nor FASTBOOT.
The only post regarding this does not have any replies so I dont know what to do.
Best Regards.
Anyone knows? A little help would be appreciated.
where did you get the drivers?
Maybe you can get the dell drivers or load the SDK for android it will install drivers too.
What is the end result you want?
alperin1 said:
where did you get the drivers?
Maybe you can get the dell drivers or load the SDK for android it will install drivers too.
What is the end result you want?
Click to expand...
Click to collapse
I have Android SDK installed, which works properly with other phones.
My question is why does my Streak is recognized as a USB Input Device?
Is it normal?
To get my streak working I had to install dell drivers (got it via here just click on downloads tab and install software but don't launch program after drivers have installed http://www.unlockstreak.com/pages/d...?ref=874b1d7212afe8cc4672f2f53d9976c12a5ea0e5).
After this I launched QDL Tool held vol up and inserted usb cable which launched Qualcomm HS-USB 9002 driver which won't be found, you need to go to drivers which should be in a folder that comes with QDL Tool.
So should go as Drivers - Driver_2.067 - Win 32 (or 64 if your running a 64 bit system) - Whatever OS you are running - qcser - Select 2nd option of Qualcomm Drivers and search for Qualcomm HS-USB 9002 should install when you double click on it and should be ready to go.
Check if QDL Tool has recognised driver via communications port if not close down and reopen.
Click on RUN if driver success and should start restoring Streak, should know when complete as it goes green when done and good.
Note: When installing driver have to manually install it so a case of Update Driver, Browse my computer, Let Me pick, Have Disk, Browse when it shows path to select, then go to path whever QDL is extracted (eg Desktop) and follow folder paths above to get it installed.
Hope this is clear and also hope it helps!!! Good Luck
passion8059 said:
To get my streak working I had to install dell drivers (got it via here just click on downloads tab and install software but don't launch program after drivers have installed http://www.unlockstreak.com/pages/d...?ref=874b1d7212afe8cc4672f2f53d9976c12a5ea0e5).
After this I launched QDL Tool held vol up and inserted usb cable which launched Qualcomm HS-USB 9002 driver which won't be found, you need to go to drivers which should be in a folder that comes with QDL Tool.
So should go as Drivers - Driver_2.067 - Win 32 (or 64 if your running a 64 bit system) - Whatever OS you are running - qcser - Select 2nd option of Qualcomm Drivers and search for Qualcomm HS-USB 9002 should install when you double click on it and should be ready to go.
Check if QDL Tool has recognised driver via communications port if not close down and reopen.
Click on RUN if driver success and should start restoring Streak, should know when complete as it goes green when done and good.
Note: When installing driver have to manually install it so a case of Update Driver, Browse my computer, Let Me pick, Have Disk, Browse when it shows path to select, then go to path whever QDL is extracted (eg Desktop) and follow folder paths above to get it installed.
Hope this is clear and also hope it helps!!! Good Luck
Click to expand...
Click to collapse
Thanks for your info but it's not helping.
It seems than something else was damaged when I cracked the screen because it never detects "Qualcom..."
Best Regards.
Hi I recomend taking your sd card out and put that directly into your pc and if you cant do that maybe borrow a friends smartphone or card reader.
Sent from my Dell Streak using XDA Premium App
stevepork said:
Hi I recomend taking your sd card out and put that directly into your pc and if you cant do that maybe borrow a friends smartphone or card reader.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
Problem fixed!!
The phon had the Volume and Power Flex ripped off, so the phone did not power.
I replaced it and the phone is running now.
Best Regards and thanks to you all.
Warm regards to the community here. I'm using Samsung & LG android devices past 2 years, with lots of custom roms and kernels; but have no experience dealing with Sony device. I am currently helping one of my friend to install Cyanogenmod on her Xperia mini pro sk17i, and help is required. I assure you, I won't have flooded the forum with a new thread if i'd found the answer. So hoping for a gentle guidance..
Here is what i did :
I followed the instructions given at Sony's website from step 1 to 12 : http://unlockbootloader.sonymobile.com/instructions
- I checked that Bootloader unlock allowed is "Yes", and managed to get my unlock key from Sony.
- I downloaded and installed Android SDK manager, also downloaded Google USB driver package revision 4. Also, i managed to download the zip file from Sony and successfully copied & replaced the android_winusb.inf file in the instructed folder.
- Now, at the step 13 mentioned in the guideline, i'm really stuck. I turn of the phone, press & hold volume up while inserting the usb cable.... there appears small blue light at the top of the device. But, nothing else happens.
>> I mean, the instruction says that i should be asked to point the drivers by computers, but my computer asks for nothing. I'm running on windows7 x86, intel core i3.
Please guide me what is going wrong ?? .... however, i should mention that my computer does gives me a notification sound, kind of what usually happens when i attach anything in the usb port.... but, on the screen, it shows no any notification or no any pop up... just nothing at all. I tried the whole procedure on an another computer running windows7 x64, intel core i5, but still stuck at the same problem.
Your help will be very much appreciated. Thanks in advance.
Have you checked "unknown sources" and "usb debuging" on?You will found them both in settings>applications if i translate it right from my greek menu
T3sla said:
Have you checked "unknown sources" and "usb debuging" on?You will found them both in settings>applications if i translate it right from my greek menu
Click to expand...
Click to collapse
Yes, of course both things are checked. To test the things, i also checked upon SEflashtools, and the device shows up there. However, if i command adb devices, it didn't show up on my second corei5 computer, but id did show up on my previous corei3 computer.
I tried out almost all i can do from my previous experiences of dealing with galaxy and optimus devices.. yet, this one is beating me.
Use drivers and tools from this guide and post the results (also mount sdcard to MSC mode)
If link doesn't work download latest flashtool.On installation folder there is a folder named "drivers".Run the file inside.
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
mooside said:
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
Click to expand...
Click to collapse
Same here.
- tried to uninstall Devide from the DeviceManager
- reboot PC
- connect my mini (with Vol-Up, blue LED turns on)
- choosed the "Android Booloader Interface"-Driver
- But Device-Manager says it's "Android ADB Interface"
My Datas:
root
CWM (installed through Installer from Market)
StockRom
Windows 7 (32 bit)
greeting
rookie
mooside said:
you have to manually install the driver of your android phone, go to the device manager on your computer, it should appear as S1 boot Fast boot in other devices, update the usb driver with the dowloaded diver android_win_usb.
your device shluld appear as android ADB Interface then you can proceed to step 14 which sadly where I got stuck too. I can't get a a response back from the said step. inform me if you have luck on the next steps...
Click to expand...
Click to collapse
vsrookie said:
Same here.
- tried to uninstall Devide from the DeviceManager
- reboot PC
- connect my mini (with Vol-Up, blue LED turns on)
- choosed the "Android Booloader Interface"-Driver
- But Device-Manager says it's "Android ADB Interface"
My Datas:
root
CWM (installed through Installer from Market)
StockRom
Windows 7 (32 bit)
greeting
rookie
Click to expand...
Click to collapse
Maybe this video can help you.
Thanks friends. Finally got it working ! .... it appears it was surely driver problem. Tried all the given driver links and installed them, and at least one of them must have solved my problem.
Unlocked the bootloader, and flashed nightly 20. Returned the phone back to her.
Thanks again !
officialreloaded said:
Thanks friends. Finally got it working ! .... it appears it was surely driver problem. Tried all the given driver links and installed them, and at least one of them must have solved my problem.
Unlocked the bootloader, and flashed nightly 20. Returned the phone back to her.
Thanks again !
Click to expand...
Click to collapse
Glad i was able to help you
What worked for me:
I removed these lines from the INF:
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
That worked.
greetings
rookie
I've got an Xperia U (st25i) unbranded firmware 6.0.B.3.184, but my Windows 7 x64 doesn't show adb device at all, I have a working mtp device (that looks like it cannot be disabled). Same device works fine in adb on linux, even passing the usb device to a vmware machine with linux.
I've tried with Xperia_P_Xperia_U_Xperia_sola_drivers.zip and install PC Companion, but the adb devices still does not show, if I force add the adb interface from inf, windows 7 says it cannot start, there is same problem on windows 7 x86. Windows xp x86 instead automatically installs mtd devices but prompts for the adb device drivers, so I can give him the drivers. Any clue?
Make sure PC is connected to internet then connect the device in fastboot mode. Win7 downloads and installs drivers automatically.
Sent from my Blade using Tapatalk 2
Had the Same issue. Just Google for win7 64bit and xda. Sorry i have no Link. But Problem solved easy
Rapier07 said:
Make sure PC is connected to internet then connect the device in fastboot mode. Win7 downloads and installs drivers automatically.
Sent from my Blade using Tapatalk 2
Click to expand...
Click to collapse
I don't need fastboot drivers, just adb to develop, I'm always connected, but adb interface does not show at all in device manager, I don't have unknown/failed devices in device manager
sherpya said:
I don't need fastboot drivers, just adb to develop, I'm always connected, but adb interface does not show at all in device manager, I don't have unknown/failed devices in device manager
Click to expand...
Click to collapse
You have the "wrong" drivers installed. Use the drivers provided with c:\flashtool\drivers
-> then turn off internet on pc before connecting phone. <- prevents windoze from auto install via update
xperia mt27i
gazhead said:
You have the "wrong" drivers installed. Use the drivers provided with c:\flashtool\drivers
-> then turn off internet on pc before connecting phone. <- prevents windoze from auto install via update
xperia mt27i
Click to expand...
Click to collapse
The only driver windows automatically install is the mtd (that doesn't need internet because is in win), I don't have the device VID_0FCE&PID_5171&MI_01 but only VID_0FCE&PID_5171
It's a bit strange a common developer should download a non sony tool to develop with a sony phone
I had a similar problem with my XS, I get around it by enabling 'install PC companion' in connectivity settings under 'xperia'. Then when you plug the phone in, on your phone select install. It should then appear both as an MTP device the PCC installation, just cancel that latter.
I've used the wrong thread title, it should be x64 not x86, I've just verified that windows 7 32bit downloads and installs the adb driver, I had similar problem with gt7500 on windows xp 64bit, http://forum.xda-developers.com/showthread.php?t=1434319
I've solved modifying the inf file, I think I cannot change inf on windows 7 x64 because the driver becomes unsigned. Perhaps gt7500 works fine on windows 7
Heh... You stiill refuse to listen.
Install drivers provided with flashtool. Just doit and report back
mt27i
tested with internet disconnected and drivers pack in flashtool-0.9.1.0-windows.exe, same thing, windows shows only mtp device
check this out:
http://forum.xda-developers.com/showthread.php?t=1554632
more drivers:
http://www.mediafire.com/?2fxtdec2fxacux1
sherpya said:
It's a bit strange a common developer should download a non sony tool to develop with a sony phone
Click to expand...
Click to collapse
eeh.. its GOOGLE Android default tools. adb fastboot etc its all Android getit?
Request
thebrainkafka said:
Had the Same issue. Just Google for win7 64bit and xda. Sorry i have no Link. But Problem solved easy
Click to expand...
Click to collapse
Tell Me how Please....:crying:
I just solved this issue for my Xperia S.
Here are the steps:
1. Install driver on flashtool (I also install the pc companion)
1. On device manager, open the MTP device, and select reinstall device driver
2. Choose install the driver manually and list the compatible driver
3. It would only show one "USB Composite Device" for this device and install it
4. After the driver installed, the adb device just shows up!
Hello,
This must be a dumb question because all the guides seem to skip over this part but I'm having trouble installing the Windows 7 drivers. I downloaded the drivers, connected via USB, right clicked on the Android 1.0 in the device manager and updated the drivers. Everything seemed fine. Then I boot into fastboot and get a "Drivers were not installed successfully" pop-up.
I thought maybe I messed up and was supposed to install the drivers while in fastboot rather than while the phone was all the way booted up. So I rebooted the phone, uninstalled the drivers, booted in fastboot and tried to install the drivers while in fastboot. When I try it this way I right click on Android 1.0 in the device manager, go to the update driver option, select my file (there are two files in the driver folder I downloaded, androidusb and htcrndis, I tried them both) and I get an error before it can finish installing the driver. It says:
Windows found driver software for your device but encountered an error when trying to install it:
HTC Remote NDIS based Device
This device cannot start. (Code 10)
I'm sure it's something simple but I cant figure it out. Thanks for any help.
So, I have searched Reddit and other sites for clues and help and I have had no luck. I have even contacted an android developer and had him try on his computer and had no luck.
I am trying to install Lineage OS for 17.1 and am currently trying to root my device. I have downloaded Google USB Drivers directly and tried from Android Studio. It detects my device fine. I go into command and run adb device, it detects my device. I reboot the device into fastboot, windows detects the driver but has no driver to install. I manually install the driver and it says it "Windows could not find the drivers for your device" despite me pointing it to "...AppData\Local\Android\Sdk\extras\google\usb_driver" which is where the driver is located. I click let me pick, install it under Andoid Devic -> Android Bootloader Interface. It says "Successfully Updated Driver" but put the device in "Other Devices" with a "?" on the icon and "Unknown Device". Even tried to see if it still worked but no device was detected (fastboot device). The Google Pixel C is "Waiting for fastboot command . . . . " but that's it.
Tried both drivers downloaded. Windows updated and no driver download. Restart windows countless times. New usb cable. Different usb port including usb 2 and 3. Nothing.
Developer reported same. Any ideas appreciated!
Thanks!
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
jwoegerbauer said:
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
Click to expand...
Click to collapse
Sorry for the slow response.
Same issue. I wouldn't expect otherwise though because the ones straight from Android Studio and Googles website doesn't work. Still shows "Unknown Device" and won't let me install the driver after showing "Waiting for fastboot command. . . ."
Drivers work fine until in fastboot mode.
Waiting for fastboot command. . . .
@slitterell
I'm pretty sure the USB driver ( does NOT mean ADB and/or Fastboot drivers ) you've installed is the culprit: Uninstall it and install the one suitable at 100% to your phone, will say the Google USB driver.
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
@slitterell
The mentioned Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.
So it should be the correct USB-driver in your case.
The latest is attached.
slitterell said:
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
Click to expand...
Click to collapse
Google's driver package doesn't have Product ID of the Pixel C mentioned in its inf file, so it doesn't work for you. Interesting that you got adb connection anyway. So, maybe Windows has installed automatically some driver but it didn't had entry for the bootloader/fastboot.
Here is how people have added those adb entries. Bootloader entry can be found from device manager and added the same way...
https://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
Or you could just use my Yet Another Universal ADB Driver Package
https://forum.xda-developers.com/an...staller-universal-adb-driver-package-t3595277
http://yet-another-universal-adbdriver.blogspot.com/
and hope for the best...