Vivo and iQOO USB Driver Setup for Windows and ADB

Vivo and its gaming sub-brand iQOO both run Funtouch OS (or OriginOS in China), a heavily customized Android skin that requires a manufacturer-specific USB driver for ADB and Fastboot connectivity on Windows. The driver installation path differs slightly between MediaTek-based and Qualcomm-based vivo/iQOO models, and enabling Developer Options in Funtouch OS requires a non-obvious step. This guide covers everything from driver download to verifying ADB connectivity.

Where to Get the Vivo USB Driver

Vivo distributes its official USB driver through two channels:

• vivo PC Suite — a full desktop suite for device management, SMS sync, and backup. Available from vivo's regional support websites (vivo.com/en or the relevant country subdomain). Installing PC Suite automatically registers the USB driver.
• Standalone USB Driver — a lighter package without the full PC Suite. Vivo hosts this on its developer support pages, typically labeled "vivo USB Driver" or "Qualcomm/MTK USB Driver."

iQOO devices use the same underlying USB driver as vivo since they share the same hardware ecosystem and Funtouch OS base. There is no separate iQOO-specific driver — the vivo USB driver covers all iQOO models.

For Qualcomm-based vivo/iQOO devices (iQOO 9 Pro, 11 Pro, 12, 13, vivo X90 Pro, X100 Pro), the Qualcomm HS-USB QDLoader driver (available from Qualcomm or as part of the vivo driver package) is needed for Fastboot/EDL mode access in addition to the standard vivo USB driver.

Enabling Developer Options in Funtouch OS

Funtouch OS hides the Build Number in a non-standard location compared to stock Android. The exact path varies by OS version:

Funtouch OS 12 and later (Android 12+):

1. Go to Settings > More Settings > About Device.
2. Tap Version Info.
3. Tap Build Number seven times. A PIN or password prompt may appear if screen lock is set.
4. Developer Options appears under Settings > More Settings > Developer Options.

Funtouch OS 11 and earlier (Android 11):

1. Go to Settings > About Phone.
2. Tap Build Number seven times.
3. Developer Options appears under Settings > More Settings > Developer Options.

OriginOS (China variants): OriginOS has Developer Options at Settings > My Device > Version Info > OS Version. Tap OS Version seven times. The Developer Options location is Settings > System Management > Developer Mode.

Enabling USB Debugging

Once Developer Options is unlocked, navigate to it and toggle USB Debugging on. Connect the phone to the PC with a USB cable. A notification appears in the Android shade — tap it and ensure File Transfer (MTP) is selected. Then, an ADB authorization dialog appears on the phone screen. Tap Always allow from this computer.

Verify the connection on the PC:

adb devices

The expected output lists the device serial number with status device. If the status reads unauthorized, the phone's authorization dialog was not accepted — disconnect, reconnect, and tap the authorization prompt on the phone.

Installing the Vivo USB Driver on Windows

If adb devices returns nothing or shows the device with an error, the driver is not installed correctly. Steps for manual installation:

1. Download the vivo USB driver ZIP or installer from vivo's support site for your region.
2. If it is an installer EXE, run it with administrator rights and follow the wizard. Restart Windows when prompted.
3. If it is a ZIP with INF files, extract to a local folder such as C:\VivoDriver.
4. Connect the phone in File Transfer mode.
5. Open Device Manager (devmgmt.msc). Look for vivo Mobile Device, Android Device, or an unknown device under Other Devices with a warning icon.
6. Right-click the problematic entry and select Update Driver > Browse my computer for drivers.
7. Point to C:\VivoDriver with Include subfolders checked. Click Next.
8. Accept the publisher prompt.

After driver installation, disconnect and reconnect the phone. Run adb devices again to confirm the connection.

MediaTek vs. Qualcomm Driver Differences

Vivo and iQOO sell models with both MediaTek Dimensity and Qualcomm Snapdragon chipsets, and the Fastboot driver handling differs between them.

MediaTek-based devices (e.g., vivo Y55, iQOO Z5, Z7, Z9 Turbo using Dimensity 6020, 8200, 9300): In Fastboot mode, these devices often require the MediaTek VCOM driver rather than a standard Fastboot driver. The device may appear as a COM port rather than a USB device in Device Manager when in Fastboot/Download mode. The vivo PC Suite driver bundle typically includes this VCOM driver. Without it, fastboot devices returns nothing even though the phone is connected.

Qualcomm-based devices (e.g., iQOO 9 Pro, 11 Pro, 12 Pro, 13, vivo X90 Pro, X100 Ultra using Snapdragon 8 Gen 1/2/3/Elite): These use standard Qualcomm Fastboot and EDL protocols. fastboot devices works with the standard vivo USB driver once Fastboot mode is reached. EDL (emergency download) mode requires the Qualcomm HS-USB QDLoader 9008 driver.

To identify your chipset:

adb shell getprop ro.hardware
adb shell getprop ro.board.platform

A response like mt6877 or mt6983 indicates MediaTek. A response like taro, kalama, or sun indicates Qualcomm Snapdragon 8 Gen 1, Gen 2, or Gen 3/Elite respectively.

Fastboot Mode on Vivo and iQOO

Vivo and iQOO bootloaders are locked by default and vivo does not offer an official bootloader unlock program for most markets outside China. On global (international) vivo/iQOO devices, bootloader unlock is not officially supported and there is no publicly documented unlock command. Fastboot mode can still be entered for other diagnostic purposes:

1. Power off the device completely.
2. Hold Volume Down + Power simultaneously until the Fastboot screen appears. On some iQOO models, it is Volume Up + Power.

Verify Fastboot detection:

fastboot devices

On Qualcomm models, this should list the device. On MediaTek models with the VCOM driver, the device may appear in Device Manager as a COM port and fastboot devices may return nothing — this is expected behavior for MTK Fastboot over the SP Flash Tool protocol rather than standard Fastboot.

Verifying Full ADB Functionality

After driver installation and ADB authorization, confirm full command access:

adb shell getprop ro.product.model
adb shell getprop ro.build.version.release
adb shell getprop ro.product.cpu.abi

These return the device model, Android version, and CPU architecture (e.g., arm64-v8a for 64-bit). Successful responses confirm ADB is fully operational for sideloading APKs, pulling logs, and using developer tools.