MediaTek DA USB VCOM Port - Help me fix Code 10 problem - Android Q&A, Help & Troubleshooting

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?

Related

[HELP- SOLVED] unlock bootloader step#13 doesn't happen

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

[Q] THL W100 and problems with Mediatek USB preloader ....

Hi all...
I received my THL W100 yesterday from an italian reseller... I ordered it already rooted and it arrived directly fron Hong Kong with the latest firmware 130711 and prerooted with Superuser (I checked it with root checker and it's effectively rooted...).
It also has it's own recovery pre installed (when I enter the recovery mode with pover+volume up it appears an "android recovery"...)...
I wanted to flash a different recovery (the Barry63 recovery) and so proceeded with installing in one of my four pc (running win XP SP3) the drivers I founf inside the Ro.edi package... after this, I turned off my phone, disassembled the battery, put the usb cable both on my phone and on my pc and finally inserted the battery... I hear the tipical sound played when you put a new USB device in a computer and immediately after (a secondo or so...) a second sound tipical of when you disconnect your USB device... all in all my phone automatically disconnects and this results in a "non installation" of the Mediatek USB preloader I neeed to use the SPFlashtool...
I tried on anoter pc of mines, running Win XP (a modded version) and got the same result...
I also tried another pc running Win7 Home Premium , forced the installation of the Mediatek USB preloader via the "hdwwiz" method, put the usb cable in both the phone and the pc, re-connected the battery and... it recognizes the new device, starts to install the Mediatek USB preloader, but after some seconds it says "device diconnected"....
Same issue on the fourth and last pc of mine running Win 7 starter...
It's like my phone has something in the firmware (root?Recovery?) that doesn't allow me to install the Mediatek USB preloader...
Any idea about it ?
My phone works perfectly, the pc recognizes it both as USB archive and USB debug... I can do almost all the things I want (the phone is rooted and so I installed all the apks I wanted, included the MobileUncleTools... but I can not use the SPFlash tool as I can not install the MediaTek USB preloader... :crying:
Thank you in advance for you precious answers...
usb debugging
did you enabled "usb debuging" in developer settings.
android---central.com/how-enable-developer-settings-android-42
buyukbalkan said:
did you enabled "usb debuging" in developer settings.
android---central.com/how-enable-developer-settings-android-42
Click to expand...
Click to collapse
Yes... it was enabled...
Anyway I solved the problem... I discovered that what it happened to my phone is the "supposed to be" for that driver... in fact, after launching SPFlashtool and press dowload, when you plug in the battery on the phone SPFlash recognize the phone and starts flashing the right way.
Finally I succeeded in it and flashed the Barry6030 recovery. :laugh:
Thank you :good:
bigboss1970 said:
Yes... it was enabled...
Anyway I solved the problem... I discovered that what it happened to my phone is the "supposed to be" for that driver... in fact, after launching SPFlashtool and press dowload, when you plug in the battery on the phone SPFlash recognize the phone and starts flashing the right way.
Finally I succeeded in it and flashed the Barry6030 recovery. :laugh:
Thank you :good:
Click to expand...
Click to collapse
I'm happy to hear that you can handle it...

[Q] Please, help - cannot read Stock ROM with SP Flash Tool

Hello,
*I have a problem with accessing phone PreLoader on Virtual COM port.*
I have NO PROBLEM with ADB driver and access. I can also access phone as a Device in Windows.
*But I want to create backup of my phone ROM.*
I want to read the ROM with SP Flash Tool to make backup.
(I cannot post links, so see full links in .txt file attached)
Phone: Alcatel IDOL One Touch Mini
Phone model code: 6012X
Full phone specs: gsmarena.com/alcatel_one_touch_idol_mini-5669.php
Chipset: Mediatek 6572
USB driver link page: developer.android.com/sdk/win-usb.html
Driver direct link: dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
OS: Windows 7, 64 bit
What I do:
------------
- I turn phone off. (Cannot remove battery - phone can not be opened=battery is not removaable)
- Connect to Windows
- Windows popup message for a device connected !
- Browse... choose driver for Win7,64bit,..... (only first time Windows wants driver)
- In Device Manager this device appear for a second, and then disappears: [PreLoader USB VCOM Port (COM_X)]
=== Result: Phone is not visible and cannot be accessed/shown in SP Flash Tool. Tried in versions 3.1224.01 (older)
and 3.1352.01 (newer interface).
What I tried to troubleshoot:
---------------------------------
- Used USBDeview.exe (64 bit), runned as administrator. Performed manual Uninstall for all old virtual COM ports.
- Tried another USB cable.
- Tried another USB port; Tried another USB port on another insernal USB hub; Tried on extranal USB hub.
- Tried another drivers, which I have found on fourms.
- Started Device Manager as admin, show hidden devices. Now I can see m phone as a light gray device.
Every time I plug phone, Windows creates a new VCOM port. I have to uninstall them manually with UsbDeview.
When I click properties on VCOM with/without currently phone attached windows says:
"Device status: Currently this hardware device is not connected to the computer. (Code 45)".
See screenshot: postimg.org/image/o3h86dbzt/
- Googled many times for Code 45 but cannot solve this problem.
- Obviously windows can see MediaTek chipset at least for a while. Tried to connect on turned off phone. Or with
phone started in Recovery mode (Meta mode?) - Power+Volume up. No luck here too.
=== Result: Failed to succeed. Nothing of above can help.
Please, help!

Lenovo P780 SoftBrick

Hey Guys
I bricked my P780 and didnt do a backup. I formated the phone with SpFlashTool, afterwards the Flashing didnt work. And a second format didnt work too.
Now i tried nearly every possible tutorial on the web...
I am using win7
My main problem is that i am using SpFlashTool (newest version) and i get an 4032 Error if i try to download the rom.
I tried nearly every Rom for the p780 with every possible scatter file.
I tried nearly every MediaTek DA VCOM USB Driver, MediaTek PreLoader VCOM USB Driver and MTK USB Port Driver and always with no success.
I even plugged out the battery (its not removable) without damaging the phone...
Spackotus said:
Hey Guys
I bricked my P780 and didnt do a backup. I formated the phone with SpFlashTool, afterwards the Flashing didnt work. And a second format didnt work too.
Now i tried nearly every possible tutorial on the web...
I am using win7
My main problem is that i am using SpFlashTool (newest version) and i get an 4032 Error if i try to download the rom.
I tried nearly every Rom for the p780 with every possible scatter file.
I tried nearly every MediaTek DA VCOM USB Driver, MediaTek PreLoader VCOM USB Driver and MTK USB Port Driver and always with no success.
I even plugged out the battery (its not removable) without damaging the phone...
Click to expand...
Click to collapse
Hi. Because you have formated your nand you must reinstall your drivers, because your preloader now is messed up.
In order to do that you must do this:
1. Install drivers.
2. Go to device manager and let the window open.
3. Connect your phone and new hardware should appear for just a seccond or 2 max, something with MTK 6.5.XXX.
4. Click very fast on the little new thing that appear there because will desapear.
5. Now press the button to update drivers hardware. In one of my posts you will find an archive with the right drivers. Drivers are on the archive uploaded here.
6. After the drivers are installed your PC should recognize the phone.
7. After this the steps should be the same to flash your ROM. Oh and by the way: Press Firmware Upgrade button not Download. And dont forget to check DA/DL With Checksum... option
8. Waiting for feedback.
9. Good Luck.
stympy said:
Hi. Because you have formated your nand you must reinstall your drivers, because your preloader now is messed up.
In order to do that you must do this:
1. Install drivers.
2. Go to device manager and let the window open.
3. Connect your phone and new hardware should appear for just a seccond or 2 max, something with MTK 6.5.XXX.
4. Click very fast on the little new thing that appear there because will desapear.
5. Now press the button to update drivers hardware. In one of my posts you will find an archive with the right drivers. Drivers are on the archive uploaded here.
6. After the drivers are installed your PC should recognize the phone.
7. After this the steps should be the same to flash your ROM. Oh and by the way: Press Firmware Upgrade button not Download. And dont forget to check DA/DL With Checksum... option
8. Waiting for feedback.
9. Good Luck.
Click to expand...
Click to collapse
First of all thanx!
But whitch driver i should install in Point 1. ?
Second, what should i do if the device is appearing for 2 sec, the device appears straight as unknown device and then replugs itself every 30 sec
Spackotus said:
First of all thanx!
But whitch driver i should install in Point 1. ?
Second, what should i do if the device is appearing for 2 sec, the device appears straight as unknown device and then replugs itself every 30 sec
Click to expand...
Click to collapse
Hi. The drivers i uploaded to you at my post!
For the new device you must have the device manager window open ! Only there you will find the preloader.
stympy said:
Hi. The drivers i uploaded to you at my post!
For the new device you must have the device manager window open ! Only there you will find the preloader.
Click to expand...
Click to collapse
Well the device appears straight as MTK USB Port, , there is no 2 sec TimeFrame when the device apears as MT65xx
an yes, i installed your driver, i am even using a new installation of win7
Hi guys.. sory to butt in... but im experiencing the same problem where in my case i have lenovo s720 instead.
Does the solution works for u?? Mine says something about partition manager eror.
beckham_totti said:
Hi guys.. sory to butt in... but im experiencing the same problem where in my case i have lenovo s720 instead.
Does the solution works for u?? Mine says something about partition manager eror.
Click to expand...
Click to collapse
The solution should work for you! Or else search on this forum itself and you will get your answer!

Elephone P9000 Root No PC

Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot, Universal Androot, Root Genius, Baidu
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
ThisIsMyMaster said:
Once you got into android modding, an unrooted phone becomes almost useless.
Now my problem is that I´ve got one.
Couple of days ago my Elephone P9000 arrived from amazon but I can´t connect it to a PC since it says that no device is detected.
Yes, the drivers are installed properly!
I thought that isn´t a problem because there is Kingroot.
Turns out the following rooting apps don´t work for me:
Kingroot (Kingoroot), iRoot, z4root, Framaroot, Towelroot, Oneclickroot.
Custom Recovery isn´t installed because, of course, no root.
Now how do I root?
Click to expand...
Click to collapse
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=12240&page=1&ordertype=1#pid129322
jotei66 said:
The first thing you need to accomplish is to get your PC to recognize your phone, rooting from there is going to make life easier, but yes, I know you already know that. If your using windows 10, maybe check this thread out on Elephone Forum:
(link removed)]
Click to expand...
Click to collapse
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
ThisIsMyMaster said:
That´s the tutorial that I was going to do but when my phone is shut down, my pc doesn´t detect the device and flash tool neither.:crying:
Click to expand...
Click to collapse
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
jotei66 said:
Firstly is your PC finding your phone ok with the PC on? If yes.. all good - if no you need to sort this out first.
Then, ensure you have installed the MTK driver on your PC (these are the Media Tek drivers which will find your phone when it is off) instructions here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Then flashtools should work fine with your phone off.
Just a tip using FlashTools (Im on windows 10 - I dont know if this applies to other windows)
In flashtools, press download first (without phone connected), give it 5 secs and then connect your phone to your PC with the volume up button pressed at the same time. Once you see FlashTools starting to flash your phone, release the volume button. I have to do this all the time in order for my phone to be found on Windows 10.
Click to expand...
Click to collapse
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
ThisIsMyMaster said:
To start of, I am using Windows 10 as you do.
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer.
There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Windows explorer acts like no device is connected at all.
When I connect my phone as it is turned off, I still get the notification "USB Device wasn´t recognized." and
windows explorer still doesn´t care as well as the flash tool.
The link you gave me isn´t the one I previously used to install the drivers so I gave it a try.
There are two different ways mentioned in the posts #1 and #4 so I started with the first one.
(Spoiler: Both don´t work for me!)
Everything worked until a step almost at the end where I am told to connect my off-switched phone to the pc.
The tutorial tells me that there should now be a preloader unknown device or something at Device Manager > Ports (COM & LPT) that I would need to proceed further.
I didn´t get that one.
Dead end for me so I went on to the next tutorial in post #4.
In that post I am told to remove a MTK USB Port at Device Manager > Ports (COM & LPT) right after installing the .inf driver files (Yes, I installed the 64 bit version and do have a 64 bit PC).
Ignoring that step didn´t help any of the problems I had before so I got a dead end here, too.
The "Volume-Up-Trick" did help me neither, probably cause of the not working drivers.
Click to expand...
Click to collapse
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
When I connect my phone when it´s turned on, I get the small icon in the taskbar that allows me to remove the device safely or open devices and printer. There, my device is put to a section called not specified and it has a small yellow icon.
Only is it called "P9000" which is alright.
Click to expand...
Click to collapse
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
jotei66 said:
Ok first things first, lets make sure your P9000 is fine with your phone on. You said:
(make sure in dev options on your phone USB debugging is ON and USB config is MTP)
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Once windows installs this, a box should pop up showing your P9000 internal storage and SD Card (if you have one in phone)
To ensure that your PC is now finding your phone ok, restart PC and plug your phone in - you should be prompted by windows to choose a default action when this device is connected (I choose transfer files or something similar). Then everytime you connect your phone, a box will pop up showing allowing you to access your P9000.
Now onto when your P9000 is switched off... (the important part for flashing etc)
I followed the instructions at post #4 as I believe due to the anniversary update on windows 10 (the January update I believe) .. if you do not have the January update installed on your PC you would use the instructions #1
Don't worry too much if you receive "USB device not recognised" initially, (from what I have understood this is normal with the Anniversary addition of windows 10) it should disappear after few seconds or so. From what I worked out following post #4 you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed (its VERY important when you uninstall the device you untick the delete drivers too, otherwise you have essentially deleted the MTK drivers & would have to start from scratch from post #4)
For me, when I connect my p9000 when its off it still shows "USB device not recognised", then after a few seconds this goes away and I dont have any errors under Device Manager > Ports (COM & LPT) & flashtools works fine as long as I press vol up as I connect my phone.
Hope this helps, I had a headache when I tried to install MTK drivers with my windows 10 (Anniversay Update Edition) - good luck, it was kinda trial and error
Click to expand...
Click to collapse
I am running the Anniversay Update Edition and don´t get an popup window when connecting my phone turned on.
As far is I can tell, a working connection with the device running is more important in the first place.
Now I don´t quite understand your instructions at this point:
jotei66 said:
So from that you simply need to (In Device Manager) right click > Update Driver Software > Browse My PC for Driver Software > Let me pick from a list of device drivers from my PC > then choose MTP USB Device
Click to expand...
Click to collapse
In Device Manager right click, but where?
Blank space? Definetly not.
According to the linked tutorial, I´d have to right click on something like "unknown device" or something similar.
But that doesn´t show up in my list.
In the next section you said:
jotei66 said:
you are kinda installing a MTK device (just so you can install the drivers) and then uninstalling that device BUT keeping the drivers installed
Click to expand...
Click to collapse
I can understand the point but after installing that driver package, there is no MTK device in my device manager that I could uninstall.
I seriously need to thank you for wasting so much time on me:angel:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
I seriously need to thank you for wasting so much time on me
Click to expand...
Click to collapse
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
jotei66 said:
When you plug your p9000 (while its turned on) into your laptop/pc... in Device Manager, probably under Universal serial Bus Controllers do you see a unknown device, or anything with a question mark / unknown device beside it ? If so, that's where you right click and follow instructions above to get your PC to recognize your handset. At this point just concentrate on getting pc to recognise while its on, then hopefully we can then move to setting up when its off.
lol its all cool
PS: Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
I can´t believe how stupid I am...
jotei66 said:
Just to make sure, in device manager, press View from top menu and "show hidden devices".. maybe it could be hidden?
Click to expand...
Click to collapse
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Edit: After a couple of reboots of all my devices, I get back to where I was before: USB Device wasn´t recognized and Flash Tool doesn´t do anything.
ThisIsMyMaster said:
I can´t believe how stupid I am...
Well, that solved all of my problems...
Almost...
Drivers are fully working for me now so I wanted to flash TWRP with SP Flash Tool to be able to flash the superuser .zip file.
Since drivers work now, flash tool started flashing and gave me the error you can see in the attached screenshot.
Fortunately, my phone isn´t bricked or anything.
Click to expand...
Click to collapse
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
jotei66 said:
All cool & its an easy thing to miss when your not looking for it (or for that matter if you dont know that menu even existed)
That error is a preloading error, I'm assuming your flashing TWRP Recovery and like you I had similar issue - I shared a simple solution here that worked for me here (it should work fine as long as you are on Stock Elephone 2016810 Base onwards so I believe, Elephone changed the preloader or something like that in later ROMS)
So Basically, you download the Stock Elephone 2016810 Base ROM from HERE & unzip
Grab Flash Tools ver v5.1612 (if your not using that version) HERE - https://www.androidfilehost.com/?fid=24591000424940027
Then download TWRP_3.0.2.8.zip HERE & unzip
Copy the the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_2016810 Rom folder.
In Splash Tools, first flash the Elephone_P9000_2016810 Rom open "MT6755_Android_scatter" from _810 file & ensure the recovery section location points to "recovery.img" in the _810 folder also
Once your stock _810 ROM is flashed successfully, you then flash TWRP (with only recovery ticked) and ensure the recovery location points to "recovery_TWRP_3028_P9000" and your TWRP should flash fine. Make sure your using Flash Tools ver v5.1612, that worked fine for me.
There maybe an easier solution someone can point you too, but I know this worked for me no problems - you should now have TWRP recovery on stock _810 ready for you to flash your chosen ROM
Click to expand...
Click to collapse
I´m going to try this now.
Do I have to go back to Stock 20160810 if I have 20161107?
Do I have to go back to Stock 20160810 if I have 20161107?
Click to expand...
Click to collapse
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
jotei66 said:
I guess if you download the 20161107 ROM it should work, I'm really unsure, its a newer ROM so I guess it should
Click to expand...
Click to collapse
It didn´t work.
I did all the steps you´ve told me and ended up with the exact same problem I´ve experienced before: USB Device not recognized and SP Flash Tool doesn´t do anything after pressing the download button.
I was going to reinstall the drivers like you told me form post #4 here: https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
That didn´t do anything, I still have the same problem of my pc not recognizing my phone.
At least connecting my phone when it´s running works now.
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Fran Montero said:
you have to press and keep vol + when connecting the turned off phone to the computer after clicking download in FlashTools.
Regards
Click to expand...
Click to collapse
Tried it, didn´t help
ThisIsMyMaster said:
Tried it, didn´t help
Click to expand...
Click to collapse
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
jotei66 said:
MMmmm .. have you tried a different USB port? maybe a different lead if you have one? (I have two leads and I know one doesnt work for me, dunno why)
Also, after pressing download in SplashTools.. count to say 7-10 secs and then press Vol UP and connect your phone.... (I know this sounds bit stupid, but it works for me, if I connect straioght away I get errors too ref driver )
Click to expand...
Click to collapse
No, that doesn´t help either.
I think it has to do something with installing the drivers cause after installing them, in Device Manager no new drivers are displayed except for two Mediatek Preloader USB VCOM Port (COM5) and (COM6).
But those only become visible when I check "show hidden devices".
The tutorial said that some more things should have been installed but I didn´t get any error messages so I don´t understand what shouldn´t have worked.
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
jotei66 said:
Sorry Im at a loss really, maybe follow this tutorial my brother followed to reinstall the MTK and try again with all the above steps, good luck
https://www.youtube.com/watch?v=NbJCbdfPlF8
Make sure your PC is in driver signature disable mode when flashing etc btw
Click to expand...
Click to collapse
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
ThisIsMyMaster said:
Didn´t help either.
Current state:
Phone On > Everything working, I get the popup window and data transfer works :good:
Phone Off > USB wasn´t recognized, Flash Tool isn´t working, no recognition in windows explorer, phone is charging, vol+ doesn´t help
MTP and USB Debugging are activated
While installing the drivers I got no error messages and everything looked same as in the tutorial
Click to expand...
Click to collapse
Good to hear you can atleast use your phone to transfer etc while on
Just curious (although Im sure you have followed the video / other tutorials to the letter) but
(1) did you ensure when following video tut that when uninstalling the legacy device you unticked the driver box to ensure the drivers were actually kept installed?
(2) Check Device Manager, under the Ports (COM & LPT) section and remember you shouldn't have anything referring to a MTK device in there - ie like MTK USB Port (Com 3) ? (If you have it needs uninstalling)
(3) Seems obvious I know but you are connecting your phone and using FlashTools when your Windows Driver Enforcement is disabled? ( Literally restarting with advanced options & choosng Disbale Driver Enforcement) Many users think once you have installed the driver you can use it with Windows Drivers enforcement enabled, but you have to be in disabled mode.
Finally if you doubled checked all of those, then maybe try a different version of FlashTools (worth a try) and also try running FlashTools as Administrator when you open it - good luck

Categories

Resources