Driver

MediaTek USB VCOM Driver Setup on Windows for MTK Android Devices

Published: June 30, 2026 • Applies to: MediaTek Helio and Dimensity phones — Xiaomi Redmi, OPPO, Realme, Tecno, Infinix, Nokia; Windows 10 and 11

MediaTek (MTK) Android devices use a Virtual COM Port (VCOM) interface for low-level flashing and recovery access. When an MTK phone is placed in Download Mode, Windows must load the MediaTek USB VCOM driver to expose the device as a COM port. Without this driver, SP Flash Tool, MTKClient, and similar tools cannot detect the phone. This guide identifies which phones use MediaTek chips, covers driver installation, and explains how to verify the COM port in Device Manager.

Which Phones Use MediaTek Chips

MediaTek Helio and Dimensity chipsets are found across a wide range of budget to mid-range Android devices. Brand families where you are likely to encounter MTK hardware:

Xiaomi / Redmi: Many Redmi Note and Redmi A-series use Helio G or Dimensity chips. Flagship Xiaomi uses Snapdragon; Redmi budget lines frequently use MTK.
OPPO / Realme: Most Realme number series (Realme 9, 10, 11 standard and Pro) and several OPPO A-series models run Dimensity.
Tecno, Infinix, itel: These African and Asian market brands use MediaTek almost exclusively across their entire lineup.
Nokia (HMD): Mid-range Nokia models such as the G and C series frequently ship with Helio G chipsets.
Motorola: Select budget Moto E and G models use Helio G; flagship Moto uses Snapdragon.
Samsung Galaxy A and M: Some regional variants use Dimensity; others use Exynos or Snapdragon. Check the model's spec sheet to confirm.

To confirm your specific device: look up the model number and chipset on GSMArena.com. A Helio Gxx, Helio Pxx, Helio Axx, or Dimensity xxxx SoC indicates a MediaTek device that needs the VCOM driver.

What the VCOM Driver Does

In MediaTek Download Mode (BROM — Boot ROM), the phone's chipset presents a USB interface that Windows must map to a virtual serial port. The VCOM driver performs this mapping: after installation, the phone in Download Mode appears in Device Manager > Ports (COM & LPT) as MediaTek USB Port (COM X).

This COM port is what SP Flash Tool, MTKClient, and similar utilities communicate with. Without the driver, the phone shows up as an Unknown Device under Other devices and no tool can interact with it.

Getting the VCOM Driver

MediaTek does not publish the VCOM driver standalone. It is distributed in two ways:

Option A — Via SP Flash Tool: SP Flash Tool (Smart Phone Flash Tool) is MediaTek's official firmware flashing utility. When you install SP Flash Tool, it runs a driver installation step that adds the VCOM driver to Windows. Download the latest SP Flash Tool release from spflashtool.com (the community distribution site, as MediaTek does not publish it directly). Run the installer; it will prompt to install the COM driver during setup.

Option B — Standalone VCOM driver package: A standalone MediaTek VCOM driver package circulates in the Android community and contains just the .inf and .cat files without requiring a full SP Flash Tool install. Extract the package and install via Device Manager using the manual browse method described below. This is the cleaner approach if you only need the driver and not SP Flash Tool.

Installing the Driver on Windows 10 and 11

Driver signing is the main obstacle on Windows 10 and 11. The widely distributed VCOM driver package carries a valid authenticode signature on most versions. If installation fails with a signature error, you are using an unsigned or expired-certificate package — get a newer one.

Installing via Device Manager (manual method):

Put the phone into Download Mode (described below) and connect via USB.
Open Device Manager. The phone appears under Other devices as MTK USB Port, SPUSB_Composite, or an unknown device with a yellow warning triangle.
Right-click the unknown device > Update driver > Browse my computer for drivers.
Point to the extracted VCOM driver folder. Check Include subfolders.
Click Next. Windows locates the matching .inf file and installs the driver.
The device re-enumerates under Ports (COM & LPT) as MediaTek USB Port (COM X).

If Device Manager shows the device but clicking Update driver finds nothing, the .inf file in the driver package does not match the USB hardware IDs of your specific device. The hardware IDs can be found by right-clicking the unknown device > Properties > Details > Hardware IDs. Search those IDs to find a compatible driver build.

Entering MTK Download Mode (BROM)

MediaTek Download Mode is called BROM (Boot ROM) mode. Unlike Qualcomm's EDL, BROM is not entered via a key combination in normal operation — it is activated when the phone's boot process finds no valid preloader on the storage, or via a specific voltage sequence on the USB pins.

Practical methods to enter BROM:

Volume Up while connecting USB (phone powered off): Works on some MTK devices. Hold Volume Up, then plug in USB while the phone is off. If BROM activates, the COM port appears in Device Manager within a few seconds.
Via MTKClient's auto-BROM (software method): MTKClient can send a sequence over USB that forces some MTK phones into BROM. Run python mtk.py stage2 with the phone connected. Success depends on the specific chipset and software protection level.
Hardware method (test point / short circuit): Shorting specific board test points while connecting USB forces BROM on any MTK device regardless of software. The exact points vary per board. This requires disassembly.

SP Flash Tool uses a slightly different approach: it polls the COM port and waits for the phone to be powered on or connected during the poll window. Connect the USB cable while SP Flash Tool is in Download mode and power on (or plug in without the battery for battery-removable devices) — the preloader hands off to SP Flash Tool before Android boots.

Verifying the COM Port and Testing with SP Flash Tool

Once the driver is installed and the phone is in Download Mode or preloader state, open Device Manager and confirm the entry under Ports (COM & LPT). Note the COM number (e.g., COM7).

In SP Flash Tool, open the scatter file for your device's firmware (the scatter file maps partition names to addresses). The Download tab lists all partitions. Click Download to begin. SP Flash Tool auto-detects the COM port — you do not need to select it manually. If detection fails, confirm the COM port number matches what Device Manager shows and that no other application has the port open.

MTKClient (open-source Python alternative) uses the COM port directly. Run it with the --port COM7 flag, adjusting the number to match your system. MTKClient supports partition dumping, flashing individual partitions, and reading device info without a scatter file, making it more flexible than SP Flash Tool for non-standard operations.