Mediatek drivers for windows 10
Mediatek drivers for windows 10
(11-03-2019, 03:06 PM)Jane1 .
I started WIndows in TEST mode, and tried to install the drivers again . But it finished in the same way - CODE 10.
Any idea how to continue?Thanks
(09-03-2019, 09:26 AM)Jane1 Thanks for your reply.
But CODE 10 is a problem.
Here is the log from Infinity box
Infinity-Box Chinese Miracle MediaTek Service Module [ MTK ] v2.05
Load IDBase v123080 Ok!
Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection ...
PTFN : MediaTek PreLoader USB VCOM (Android) (COM36)
MODE : PRELOADER PORT
PORT : 36
Error : Failed to open port!
Error : Fail to init protocol!
I tried to install those drivers on different computers( with WIndows 10) and received the same error code 10 .
Anyone tried to install that drivers on windows 10 successfuly?
Thanks
(11-03-2019, 04:32 PM)Jane1 I did try. It does not work.
It finishes with
Error : Failed to open port!
Here is the log of Infinity box
Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection ...
PTFN : MediaTek PreLoader USB VCOM (Android) (COM36)
MODE : PRELOADER PORT
PORT : 36
Error : Failed to open port!
Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!
Reconnect Power/Cable!
Any further idea?
(11-03-2019, 07:37 PM)Jane1 I followed procedure outlined at https://www.hovatek.com/forum/thread-440.html
(BTW, the installation also ended with Code 10 there.)
I run windows in TEST mode so that signature verification should also be disabled in this mode. ( or is it not??)
Can anyone let me know which code he receives when he installs the drivers?
Is it also CODE 10?
(12-03-2019, 07:31 AM)Jane1 Which USB drive do you mean? Mediatek? Do you have a link to the latest( the one you successfully installed and use)?Thanks
(12-03-2019, 12:47 PM)Jane1 Thanks a lot for your help and a clue. I found out that the first attempt to identify finishes with the error, but for the second time it is OK. Here is the log of the working Nokia 3
...
But why it needs the second time??