Hovatek Forum MOBILE Android Mediatek drivers for windows 10
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Mediatek drivers for windows 10

Mediatek drivers for windows 10

Pages (2): Previous 1 2
X3non
X3non
X3non
Recognized Contributor
22,062
11-03-2019, 04:10 PM
#11



(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

as i mentioned earlier code 10 doesn't mean its not installed
have you actually tried connecting an MTK to the PC in preloader mode., e.g flash or read backup using sp flash tool or any other tool?
This post was last modified: 11-03-2019, 04:10 PM by X3non.
Jane1
Jane1
Jane1
Junior Member
28
11-03-2019, 04:32 PM
#12
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?
hovatek
hovatek
hovatek
Administrator
49,590
11-03-2019, 05:01 PM
#13
(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

I use Windows 10 and CM2MTK on it without problems.
Use the drivers and guide @ https://www.hovatek.com/forum/thread-440.html
Just ensure to disable signature verification because its an unsigned driver.
BTW, hope you're not holding any button when connecting to PC
This post was last modified: 11-03-2019, 05:02 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
hovatek
hovatek
hovatek
Administrator
49,590
11-03-2019, 05:35 PM
#14
(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?

Please stick to https://www.hovatek.com/forum/thread-26965.html

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Jane1
Jane1
Jane1
Junior Member
28
11-03-2019, 07:37 PM
#15



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?
This post was last modified: 11-03-2019, 07:37 PM by Jane1.
shankar1790
shankar1790
shankar1790
Senior Member
474
12-03-2019, 02:04 AM
#16
(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?

Try to update your pc if there any update (KB)available for it.
Try updating your usb driver also
Jane1
Jane1
Jane1
Junior Member
28
12-03-2019, 07:31 AM
#17
Which USB drive do you mean? Mediatek? Do you have a link to the latest( the one you successfully installed and use)?Thanks
X3non
X3non
X3non
Recognized Contributor
22,062
12-03-2019, 10:33 AM
#18
(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

quick question, is there anything wrong with the phone you used in testing the drivers you installed? bricked? whats the phone model and chipset?
also launch device manager and check if it refreshes after you connect the phone when the phone is switched off (repeat without holding any buttons then repeat while holding vol down button)
if it does, what does the phone get detected as?
This post was last modified: 12-03-2019, 10:41 AM by X3non.
Jane1
Jane1
Jane1
Junior Member
28
12-03-2019, 12:47 PM
#19
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

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) (COM40)
MODE : PRELOADER PORT
PORT : 40
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!


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) (COM40)
MODE : PRELOADER PORT
PORT : 40
Waiting BOOT ack ...
PRELOADER : ACK confirmed!
BROM : Init BROM
BROM init passed!
CHIP : MT6735 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : SecLevel : 0x00000005
BROM : SecMode : SBC+SDA
BROM : PRELOADER PORT
MODE : 0_base : BASE_v1712 | Manual : Enabled
Fail to disable Dog!
AGENT : Look for suitable BootChain in DA ...
AGENT : DA_SWSEC_CRYPTO20.bin
AGENT : Found MT6735
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA ...
BROM : DA sent
BROM :Transfer control to DA ...
DA : AGENT started!
NAND : DEVICE NOT FOUND
NAND : 000000000000000000000000
eMMC : OK
eMMC : 150100514531334D420D5D73AAE9BA01
DAInf: 4 : 2 : 155
DA : DRAM ready!
DA : BOOT to 2nd DA ...
DA : Receiving HW info

EMMC: 150100514531334D420D5D73AAE95401
EMMC: VEN : SAMSUNG | OEM : 01 | DEV : QE13MB
EMMC:
BOOT1 : 0x00400000 [ 4.00 MB ]
BOOT2 : 0x00400000 [ 4.00 MB ]
RPMB : 0x00400000 [ 4.00 MB ]
USER : 0x3A3E00000 [ 14.56 GB ]

SRAM: 0x00020000 [ 128.00 KB ]
DRAM: 0x80000000 [ 2.00 GB ]

CHIP : MT6735 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000 , EVOL : 0x0000

RNID : C431A427F790FE04DE6FDC4AB8D47469

STATUS : BLANK FLASH
BSTYLE : EMMC FLASH BOOT

DA : USB : HIGH-SPEED

Boot done!

Patch Level : O00623
Display ID : 00WW_3_31C
Ver. CodeName : REL
Ver. Release : 8.0.0
Sec. Patch : 2018-06-01
Build Time : 1528455819
Product Model : NE1
Product Brand : alps
Product Name : NE1_00WW_FIH
Product Device : NE1
Product Manfct : alps
Product Info : NE1
Board Platform : mt6737m

USERDATA : ENCRYPTED

IMEI[0] : 356802083967199
NVRAM check : Passed!

Done!
Elapsed: 00:00:58



But why it needs the second time??
X3non
X3non
X3non
Recognized Contributor
22,062
12-03-2019, 03:34 PM
#20



(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??

can't say for sure, maybe wrong connection. you can compare any changes you made from the first conn to the second one
important thing is that the driver works
Pages (2): Previous 1 2
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram