Home / Guides

Drivers and connection modes: EDL, BROM, preloader and fastboot

Updated 2026-11-04 · Русская версия

Most failed flashing and FRP jobs come down to one thing: the PC does not see the phone in the right mode because the driver or mode is wrong. Understanding the modes and their drivers fixes the majority of "device not detected" problems.

The main connection modes

EDL / 9008 (Qualcomm)

EDL is an emergency download mode where the Qualcomm chip accepts low-level commands. The PC must have the HS-USB 9008 driver. On newer models, raw EDL is locked and an authorized connection is required. Enter it via a supported command or a test point, depending on the model.

BROM and preloader (MediaTek)

MediaTek has two low-level entries. BROM (boot ROM) is the deepest, used when the preloader is damaged or for low-level work; preloader is the normal entry for flashing. Both need the MediaTek VCOM / preloader driver so Windows assigns the right COM port.

Download Mode (Samsung)

Samsung uses Download Mode (Odin mode) for flashing and many service flows. Enter it with the model's button combination and install the Samsung USB driver so the device appears correctly.

Fastboot

Fastboot is a bootloader-level mode for commands like unlocking or flashing partitions. It needs the Android/Google USB driver and the platform tools, and the device must be in fastboot, not normal boot.

Which driver for which mode

• Qualcomm EDL - HS-USB 9008 driver;
• MediaTek BROM/preloader - MediaTek VCOM driver;
• Samsung Download Mode - Samsung USB driver;
• Fastboot - Android/Google USB driver.

Why detection fails

Cable and port

A charge-only cable or a flaky front-panel USB 3.0 port causes most intermittent drops. Use a short, verified data cable in a rear USB 2.0 port directly on the motherboard for the most stable connection during flashing.

A reliable setup routine

1. Install all the drivers you may need before the job.
2. Add the tool folder to antivirus exclusions.
3. Use a rear USB 2.0 port and a verified cable.
4. Enter the correct mode for the platform.
5. Confirm detection with Read Info before the real operation.

Bottom line

Match the mode to the platform - EDL/9008 for Qualcomm, BROM/preloader for MediaTek, Download Mode for Samsung, fastboot for bootloader work - install that mode's driver, and use a verified cable in a rear USB 2.0 port. That alone resolves most detection failures.

Install drivers before you need them

The worst time to hunt for a driver is mid-job with a customer waiting. Set up a bench once with all the common drivers - Qualcomm 9008, MediaTek VCOM, Samsung USB and the Android fastboot driver - so any phone in any mode is detected immediately. This single habit removes most delays.

Diagnosing by swapping one thing at a time

1. Try a different verified data cable first.
2. Move to a rear USB 2.0 port directly on the motherboard.
3. Reinstall the driver for the exact mode you need.
4. Re-enter the mode and confirm with read-info.
5. Only then change the tool or method.

Avoiding driver conflicts

Multiple old driver versions can fight over the same COM port and cause a device to appear and vanish. When detection is unstable, remove stale drivers and reinstall the current one cleanly, then reconnect. A single correct driver per mode is more reliable than a pile of leftovers.

Quick reference

Test point and button combinations

Some modes are entered by software command, others by hardware: a test point shorts two pads to force EDL on a locked Qualcomm phone, while Samsung Download Mode uses a button combination. Learn the correct entry for the specific model, and only use test points carefully to avoid damaging the board.

A stable bench pays off

A bench with the right drivers pre-installed, a known-good short cable and a dedicated rear USB 2.0 port turns most jobs into routine work. The time you invest once in a clean setup is repaid every time a phone is detected on the first try instead of the fifth.

FAQ

Related guides

• Cable and USB port for flashing
• Preloader vs BROM