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?
Device- karbonn titanium octane plus, rebrands - nibiru mars one H1, walton primo v1
i will try to be as informative as possible.
I found my phone off in my pocket, tried to turn it on but freezes on boot/logo screen for some seconds and displays some random horizontal lines on over the logo screen like it crashed or something.
also charging logo screen(screen before the charging animation screen appears) shows some lines and reboots again to charging logo screen and do not shows charging animation.
i was using stock ROM , I thought i would flash stock ROM again using TWRP(installed earlier) but recovery is not opening.
So I tried connecting to my laptop.
In the past, I've used SP flash tool to flash recoveries, it worked fine.
drivers are fine.
now it rarely detects "MediaTek preloader usb vcom port" like it should be, but mostly it detects "MTK usb port" which is useless and don't works.
flashing works only when "MediaTek preloader usb vcom port" is detected and don't work when "MTK usb port".
when "MTK usb port" is detected, SP flash tool just detects, doesn't do anything and after some seconds shows error "S_DL_GET_DRAM_SETTING_FAIL" and solution "Please check your image to matches with your phone which is to be downloaded." please do not focus here as device should have detected as "MediaTek preloader usb vcom port".
when it rarely detects "MediaTek preloader usb vcom port", the flashing process starts but strucks in the middle and fails.
drivers installed in laptop are correct .
what should i do now ???
any other tools can i use ?
I have an issue after flashing Aerom: Unfortunately I forgot to untick preloader when I flashed the rom. Installation went fine but device is not detected anymore by preloader driver. I tried different windows PCs without success. Flashing with SP Tools is not possible.
Bootloader (and ADB) mode working. Fastboot detects the device (in device manager it is listed as HTC Dream) In developer settings ADB and oem unlock are Activated. If I try to unlock boot loader via "fastboot oem unlock", I cannot select "Yes" (Volume up) on the device, only "No" (Volume Down)....not rooted, no custom recovery
How can I recover the right preloader or install custom recovery?
alohahe3000 said:
I have an issue after flashing Aerom: Unfortunately I forgot to untick preloader when I flashed the rom. Installation went fine but device is not detected anymore by preloader driver. I tried different windows PCs without success. Flashing with SP Tools is not possible.
Bootloader (and ADB) mode working. Fastboot detects the device (in device manager it is listed as HTC Dream) In developer settings ADB and oem unlock are Activated. If I try to unlock boot loader via "fastboot oem unlock", I cannot select "Yes" (Volume up) on the device, only "No" (Volume Down)....not rooted, no custom recovery
How can I recover the right preloader or install custom recovery?
Click to expand...
Click to collapse
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Brilliant, it´s working now. Thanks a lot.
[Solved] Bricked -Brom Protocol Error- during flashing recovery with SP Flash Tool
tldr; Doing nothing fixed my phone
In my case, I received a "Brom Protocol Error" during the flashing of a recovery with SP Flash Tools. Phone was bricked, didn't turn on anymore.
When connecting to my pc, I would see "USB VCom Driver" be active but whatever I tried, SP Flash Tools would never start flashing again. The phone also never activated the "USB preloader Driver". Trying to get to meta-mode with connecting USB while pressing Volume+ didn't work either.
Solution worked out to be : Let the phone drain its battery. Over a few days I had removed the back cover and had been watching YouTube-movies about shorting test-points, the phone laying on my desk not charging. Right before I desoldered the battery I connected the phone again and pfew : It went to "USB Preloader Driver" and I could flash again
Connect to P9000, YES
Was completely lost on how to flash a new ROM to the phone. Have used SP Flash many times before. Without knowing the +Volume trick was completely lost. Wasted weeks on this. Thank you alohahe3000.
nephster said:
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Click to expand...
Click to collapse
Didn't appear
nephster said:
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Click to expand...
Click to collapse
Mediatek USB VCOM didn't appear. Instead, "unkown device" appeared under "other devices". Can someone help me because I'm about to finish flashing my Tablet and it's Nextbook 7 Premium. Thanks a lot!
nephster said:
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Click to expand...
Click to collapse
I know this was a LONG time ago, but after spending two days trying so many things to save my p9000 this finally did it. Thank you VERY much!
Wonderful I only had the Elephone a few days, mine had a very temperamental SIM slot and I couldn't get NFC to work for anything useful. A shame, as it had lots of potential, I thought. Glad you are getting your money's worth out of your one!
The thing is, I am having trouble flashing the Stock ROM to my Lenovo A1000G as it has been dead and it doesn't turn on anymore.
I have installed MTK / MediaTEK drivers (After reading multiple threads and guides over the internet) and I have installed these 3 specifically -
1) MediaTek DA USB VCOM Port
2) MediaTek PreLoader USB VCOM Port
3) MTK USB Port
But the thing is whenever I try to plugin the device to the Computer pressing the Vol (-) button - it shows up in the Ports section as MediaTek DA USB VCOM (Android). Now since it is appearing like that, I cannot flash or do anything in general. Because the device is getting detected by the PC but the one that shows up in the port is showing up as the wrong one. It should have showed up as MediaTek PreLoader USB VCOM Port but it isn't happening like that. I have tried so many variations to install drivers / uninstall it. It just doesn't work.
Can someone please help, since I don't have much knowledge. I do have the Stock ROM ready and the device is probably hard bricked, so can't install drivers using the Pdanet method. So what can I do?
No help? Please someone. Bump
__PUMA__ said:
The thing is, I am having trouble flashing the Stock ROM to my Lenovo A1000G as it has been dead and it doesn't turn on anymore.
I have installed MTK / MediaTEK drivers (After reading multiple threads and guides over the internet) and I have installed these 3 specifically -
1) MediaTek DA USB VCOM Port
2) MediaTek PreLoader USB VCOM Port
3) MTK USB Port
But the thing is whenever I try to plugin the device to the Computer pressing the Vol (-) button - it shows up in the Ports section as MediaTek DA USB VCOM (Android). Now since it is appearing like that, I cannot flash or do anything in general. Because the device is getting detected by the PC but the one that shows up in the port is showing up as the wrong one. It should have showed up as MediaTek PreLoader USB VCOM Port but it isn't happening like that. I have tried so many variations to install drivers / uninstall it. It just doesn't work.
Can someone please help, since I don't have much knowledge. I do have the Stock ROM ready and the device is probably hard bricked, so can't install drivers using the Pdanet method. So what can I do?
Click to expand...
Click to collapse
I understand you are worried but please don't create duplicate threads and only bump once every 24 hours
Regards
Sawdoctor