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.
Streakdroid no longer has guides posted. Need help with qdl. Win7 64bit drivers wont load. Most posts refer to "extra steps" needed to install but none are showing the steps needed. Please help or post the guide please.
I am currently running 1.9.0 and have been having stability issues and issues installing .apk's
Would like to get the 2.2.2 rom rooted and working.
Check my post here:
http://forum.xda-developers.com/showthread.php?p=14669686#post14669686
still getting nothing. Have the phone in the mode where windows is identifying it as a Qualcomm CDMA Technologies MSM. I am in test mode as per your post. When I point windows to the drivers I just says none found.
QDLTool3rd_20101022_GAUSB1A130500 ;QDL Tool I have downloaded.
Runawaywill said:
still getting nothing. Have the phone in the mode where windows is identifying it as a Qualcomm CDMA Technologies MSM. I am in test mode as per your post. When I point windows to the drivers I just says none found.
QDLTool3rd_20101022_GAUSB1A130500 ;QDL Tool I have downloaded.
Click to expand...
Click to collapse
Assuming you know how to install new devices, plug your phone in and when system manager finds your device change it to:
Qualcomm HS-USB Diagnostics 9002 (in the qdl start page states the same, must have it list device light this for it to work)
If you don't have that get latest drivers from Dell's support web page. Let me know how it works out for you.
vanemburghj said:
Assuming you know how to install new devices, plug your phone in and when system manager finds your device change it to:
Qualcomm HS-USB Diagnostics 9002 (in the qdl start page states the same, must have it list device light this for it to work)
.
Click to expand...
Click to collapse
I don't know how to tell it what a device name is. If i just turn it on it says dell mini. Holding up and on gives me "Qualcomm CDMA Technologies MSM"
go to control panel, go to system, go to device manager, go to Ports (COM & LPT). For me my is associated with COM1, so assume the same for you, doing this from memory, if you have multiple go to each one right click select update driver software, click on browser browse my computer and hopefully you see dell mini or something to that effect.
Click on let me pick, uncheck show compatible hardware, scroll down to qualcomm, in the model box scroll down till you see Qualcomm HS-USB Diagnostics 9002. Click on next follow the steps from there.
Can't remember if I had to reboot or not, but anyways you need to go through the bcd edit steps if you returned your system to normal. Now start qdl tool, holding volume button connect your usb. Hopefully next to the word port in device section you see Qualcomm HS-USB Diagnostics 9002.
If you do run the tool. If not, since I am doing this from memory, you might need to search for the exact steps to get driver update to Qualcomm HS-USB Diagnostics 9002.
I'll rememeber this for later.
I thought you HAD to run QDL tool to flash stock rom again. I didn't realize it was more of an un-bricking tool.
Flashing stock recovery with fastboot now and going to install .pkg from there see how that goes.
Runawaywill said:
I'll rememeber this for later.
I thought you HAD to run QDL tool to flash stock rom again. I didn't realize it was more of an un-bricking tool.
Flashing stock recovery with fastboot now and going to install .pkg from there see how that goes.
Click to expand...
Click to collapse
simple to flash a rom, just do a Google search, can go from any stock rom to any stock rom in less than 10 minutes. Fastboot and Update.pkg are your friends
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
your not the only one with this problem i have it too with same mt6575 someone help please
Need to uninstall device and reinstall drivers
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
ronbo76 said:
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
Click to expand...
Click to collapse
Your USB program does give a lot of information I have never seen before, but I still haven't been able to figure out how to get the driver to load.
thanks, John
I'm having the same problem installing the MT6575 USB VCOM drivers. Is there a workaround to get this installed? I"m using WIN 6 64bit
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
ivy13 said:
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
Click to expand...
Click to collapse
Tried your first method but still get Code 10 error. Could not understand your second method. Please help. Me device is Qmobile Noir A2
hye.. any progress? am having the same issue.. just for MTK6575 com port driver
Just made my Amoi N820 work
So happy
You get Code 10 becouse your windows couldn't recognize the driver but that's irrelevant becouse flashing will work
No solution?
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
orion~X said:
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
Click to expand...
Click to collapse
i have thet problem to.
is ther solution?
I HAVE SOLUTION FOR THIS PROBLEM!!
Just ignore the error Code 10! Start the SPFlashtool and load the scatterfile, click on download and connect your switch off Phone with the computer. It will work fine.
Having the Same Problem
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Hi.
me test for me not work.
iphone 4s.
plz help me.
hihi2u2 said:
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Click to expand...
Click to collapse
Did you ever get this problem solved as I have the same issue with an MTK 6592 chip based phone?
I have the same problem too.
Installation of Media Tek preloaded drivers gives me Code 10 error.
Has anyone found the solution?
my phone is totally dead without power now after I tried to flash with SP Flash tool using correct ROM. I noticed in device manager that there is a CODE 10 error in mediatek preloader usb driver.. is this the culprit? my phone can no longer be detected now in SPFlash or MTK Droid tools... so hopeless... this is a brandnew phone I bought to be given as gift to my cousin...
I did it! I did it! I did it!
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
I've been struggling with my UMI Rome for days. It has/had the black screen problem, sometimes won't enter recovery mode, sometimes wouldn't allow charge, sometimes works just fine (yesterday). Last night i mistakenly cut off power during a battery recharge. -- today it has all the above problems (bricked) so I am trying doing a flashing again using the tutorials and tools on the Tehnotone.com site. Sintetix's reply above helps me at least have a better clue on what is going on. Wish me luck! BTW, I am using a Dell Windows 10 pc. (Results to be reported here.)
Sintetix said:
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
Click to expand...
Click to collapse
I tried what you said. It wouldn't install properly. It kept saying error (code 10) and showed in device management with a caution sign every time I installed the driver. I disabled the forced driver signature thingamabop but it still does it. I guess I'm screwed. Has anyone else fixed this?
So I'm trying to flash TWRP and it's been stuck on "<waiting for device>" for three hours. I also have the latest USB drivers from Samsung. My model is SM-G530P
Most obvious reason is a poor connection between PC and Android device: the device doesn't get detected.
Install latest ADB / Fastboot drivers
Re-boot Windows PC
Enable USB-Debugging in Android's settings -> Developer options
Re-boot Android device
I did all of that
Look inside here maybe it helps.
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
jogeiscool said:
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
Click to expand...
Click to collapse
Google search for;
"USB drivers for Samsung phones"
That should find a driver install .exe named "USB drivers for Samsung phones". Install those drivers.
If it still doesn't work, try a different computer, install the drivers and Odin on that PC then see if the device will connect.
Sent from my SM-S767VL using Tapatalk
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...