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?
I have had my new Visture V97HD Retina display tablet for a week now and I am having few problems understanding what is happening with drivers/adb/fastboot and recovery. I managed to install the Win 8 RK3188 rockchip driver, but had to do it with USB debugging/disabled and driver signing disabled. Then I installed the rockchip update.Then I installed PDAnet 64bit and run a RK3188 root script and all seemed to have worked OK. Rootchecker now tells me the device is rooted. The trouble is I don't have any recovery. When I try to boot into recovery I get the little Android with red exclamation mark. Also when I run ADB cmds the device is not recognized. When USB debugging is enabled and I attach the device. I get message from the device to connect via USB, then another question asking me to press here for USB storage. When I accept and connect I can see the device in explorer but still not recognized in ADB. What is happening and what can I do to fix this?
Confused
Mossey said:
I have had my new Visture V97HD Retina display tablet for a week now and I am having few problems understanding what is happening with drivers/adb/fastboot and recovery. I managed to install the Win 8 RK3188 rockchip driver, but had to do it with USB debugging/disabled and driver signing disabled. Then I installed the rockchip update.Then I installed PDAnet 64bit and run a RK3188 root script and all seemed to have worked OK. Rootchecker now tells me the device is rooted. The trouble is I don't have any recovery. When I try to boot into recovery I get the little Android with red exclamation mark. Also when I run ADB cmds the device is not recognized. When USB debugging is enabled and I attach the device. I get message from the device to connect via USB, then another question asking me to press here for USB storage. When I accept and connect I can see the device in explorer but still not recognized in ADB. What is happening and what can I do to fix this?
Confused
Click to expand...
Click to collapse
I still really could use some help!
Mossey said:
I still really could use some help!
Click to expand...
Click to collapse
I've successfully rooted v97hd using how2 on vondroid.com. it worked for original FW and also for the latest from 05/05/13. But I need to get some image to flash. what did you want to flash ? I have the same issue with the bootloader...
I feel as if I have looked everywhere especially in these forums, but have found no answer.
I've stupidly bricked my Oneplus One by wiping off the OS, to the point where I cannot boot into recovery or bootloader. It just looks at me with a black screen. When I connect it to my laptop, there is a notifcation which says the drivers failed to installed. Also my laptop only recognises my phone as "UNKNOWN DEVICE" instead of "QHSUSB_BULK". All these guides tell me to fix my drivers. This is what it looks like in device manager. (SEE PICS)
This is what happens when I attempt to update via UPDATE DRIVER SOFTWARE>BROWSE MY COMPUTER FOR DRIVER SOFTWARE>SEARCH FOR DRIVER IN THIS LOCATION>C:\Users\Admin\Downloads\Qualcomm 2012\Qualcomm 2012\fre\Windows7>NEXT (SEE PICS)
Even when I try doing it by the HAVE DISK option, I'm greeted by this error. (SEE PICS)
I am in TEST MODE, I've tried DSEO, and booting while presssing the F8 key to dsable SE's. I have tried the ColorOS Setup.exe drivers, yet nothing. Tried ADB, nothing.
I cannot use the Qualcomm drivers, and therefore I cannot use the MSM8974DOWNLOADTOOL.
Is there anyway I can potentially make the laptop recognise my Oneplus One as QHSUSB_BULK rather than UNKNOWN DEVICE??
Is it even possible for the phone to recover? Or is it game over...?
Any aid and response will be immensely appreciated, thanks in advance!
Hello!
I was trying to downgrade a Moto E XT1021 and I don't remember how but I ended with the phone stucked in the "bootloader unlocked" screen.
Tried to access the phone on the fastboot flash mode and I can get into the mode by pushing volume down and power on for a few seconds. The problem is that I'm not able to send command to the phone because adb or fastboot doesn't detect it.
The USB cable seems to be working because on the phone screen you can read USB connected and USB disconnected every time I connect or disconnect the cable.
My guess is that there's a problem with the drivers, I've tried everything, of course installing the MotorolaDeviceManager_2.5.4.exe was the first step and then I ended up trying adb-setup-1.4.3.exe and also adb-setup-1..3.exe with no luck. I'm using Windows 7 professional 64 bits.
Right now phone driver says: Android Composite ADB interface.
Hardware ID is USB\VID_22B8&PID_2E80
If I remove the driver the device with no driver says "fastboot condor S"
I want to install 4.4.4 on that phone.
What can I do?
Thanks!
I solved it
Close the thread please.
provide the solution
draxofavalon said:
I solved it
Close the thread please.
Click to expand...
Click to collapse
at least provide the solution if anyone comes wandering again with the same problem
I really don't know why it worked, but I had several folders with adb, fastboot and firmwares and ona of the folders with fastboot detected the phone, I tried the other folder and that version of fastboot didn't detected the device; really weird.
Same software, same dll's but in different hard drives, the one on the C drive worked and the one in the D drive didn't detect the phone.
As I said, really weird.
Ive been trying to root my device for over a month now, and i havent had any luck. Ive used different USB drivers software and Hardware. Ive used different cords from stock to the ones from my job and friends yet i still have failed to root it. ADB reconizes my device no problem when its booted up, but as soon as i boot into FASTBOOT mode my computer doesnt reconize the device. What am I doing wrong or am I doomed to have an unrooted device?
I had the same issue with windows Vista.
Grab the attached file. Unzip to wherever.
Plug your phone into the pc IN fastboot mode. Open Device Manager.
Find the messed up driver, usually indicated with a yellow symbol in the list.
Right click it and update driver. Don't let it auto search for one. Manually tell it where that driver is that you just unzipped. It will show a list and chose the android bootloader one. It will warn you stating it's not correct, ignore that warning.
If you need more detailed instructions just holla.
Peace.
Did you try fastboot commands when in the bootloader? Remember that adb is only for when the device is booted up normally. Just making sure...
Sent from my LG-H901 using XDA-Developers mobile app
open device manager, you will see the device with the yellow symbol, right click and select update driver software
after browse my computer for driver software --> let me pick from a list of device drivers in my pc --> android adb interface! . click on yes. this worked for me