Header Ads

Fetching...

How To Install Mediatek VCOM USB Drivers


 

When preparing to do other development things apart from  charging your phone via PC or transferring data, things like rooting a phone or flashing it, you need to have the right drivers installed on PC. This guide shows how to install drivers for Mediatek phones on PC. One thing that should be noted tough is that most phones come with PC USB drivers that install on PC when phone is connected. They may or may not the drivers need to do things like flashing a phone.

For Windows 7 and 8:
Download these drivers and double-click the installer. Allow the driver software to install if any warning dialog box displays.

For Windows 10:
These drivers will make the connection to your MTK device possible form a Windows 10 PC on a 32 or 64 bit configuration. The drivers here are unsigned so if you are running Windows 10 64 bit you are required to temporary disable the driver signature verification enforcement in order to be able to install.

To determine the version of windows 10 that you have (32 bit or 64 bit:
Right-click on Start then click on System. In the System window that opens, in System section, you will find your version of Windows next to System type
To disable windows 10 64 bit driver signature enforcement:
- On your 64 bit Windows 10 desktop click on Start then on Settings
- Click on Update & security then in the left pane click on Recovery
- Under Advanced startup click on Restart now button
- Click on Troubleshoot then on Advanced options
- Click on Startup Settings then on Restart button
The computer will restart with the Startup Settings screen.
To disable the driver signature enforcement until next restart press on number key 7 or F7 on your keyboard.
After restart you can proceed with the unsigned MTK drivers installation for your 64 bit Windows
After you install the unsigned drivers, to use them again in the future, you have to repeat this procedure.

To install the MTK VCOM USB drivers on 32 & 64 bit windows 10:
- Download the drivers archive and extract the folder from inside on to the desktop:
- Right-click on Start then click on Device Manager
- In the Device Manager Window right-click on the first item – your computer name
- Click on Action then Add legacy hardware
- On the Welcome to the Add hardware Wizard window click on Next button
- Select Install the hardware that I manually select from a list (Advanced) and then click on Next Button
- Click on Show All Devices then on Next button
- In the Add Hardware window click on Have Disk… button
- In the Install windows click on From Disk Browse… button
- In the next window – Locate file – browse for the folder that you have extracted on the desktop at the beginning
- Select the version of the driver according to your Windows 10 version – x64 for 64 bit and x86 for 32 bit and click Open button
- Click the OK button to load the driver
From the list of drivers select MTK USB Port and click on Next button
If a red warning window will open, click on Install this driver software anyway

This action will add the following drivers in to the operating system:
-MediaTek DA USB  VCOM Port
-MediaTek PreLoader
-USB VCOM Port – for transferring the firmware to your device
-MTK USB DEBUG Port
-MTK USB Modem Port
-MTK USB port – for transferring
-PreLoader to your device (and recovery in case of bad or corrupt firmware)

You now need to remove the device that we have installed but leave the drivers in the operating system.
To do that, in the Device Manager window you expand Ports (COM & LPT) section
- Right-click and click Uninstall on the MTK USB Port
- In the Confirm Device Uninstall window make sure that the box
Delete the driver software for this device is empty
You need to leave the drivers in the operating system and only remove the device that you added
- Click on the OK button to finalize.

Now, when you will connect your dead (or turned off) MTK device to the Windows 10 computer by USB, the device will be recognized either through a MediaTek Preloader USB VCOM Port interface or as a MTK USB port if it is bricked or it has bad/corrupt firmware.

No comments

arnoldgarry256. Powered by Blogger.