MediaTek preloader and BROM: the EDL of the other half of the market
Most of the guides on this site cover Qualcomm hardware, because that is what I have spent the most time on. But a large share of budget phones in Pakistan run MediaTek, and if you only know the Qualcomm way of working you will be lost the first time one lands on your bench.
The good news is that the concepts transfer almost exactly. MediaTek does the same things with different names.
Preloader and BROM
MediaTek devices have two low-level modes rather than one, and the difference matters.
The preloader is the normal one. It runs from storage, initialises the hardware, and accepts flashing commands. If the preloader is intact, most work happens here.
BROM — boot ROM — is the emergency mode, and it is the true equivalent of Qualcomm EDL. It lives in the chip itself and survives any amount of damage to storage. A device with a wiped preloader can still be reached in BROM.
The notorious part: on many MediaTek devices the port appears for only a second or two when you connect the cable, then disappears. People plug in, see nothing, and conclude the device is dead. The tool has to already be waiting and listening before you connect.
The scatter file
Where Qualcomm uses rawprogram0.xml, MediaTek uses a scatter file — a plain text file describing the partition layout: names, start addresses, sizes.
It is readable, which makes it as useful a verification tool as its Qualcomm counterpart. Open the scatter file from a firmware package, compare the partition names and sizes against what you expect for your device, and you have answered the compatibility question before flashing anything. The same principle as checking a Qualcomm package.
The Download Agent
The DA file plays the role the firehose loader plays on Qualcomm: it is sent to the device first, runs in RAM, and turns the device into something that accepts a flash. Like the firehose file, it is chipset-specific.
And like Sahara errors on Qualcomm, DA-stage failures are usually about the connection or the DA version rather than your firmware — which means the same diagnostic habit applies. Prove the connection before you blame the files.
Where MediaTek differs in practice
- Timing sensitivity. BROM's brief window makes MediaTek work feel fiddlier. Start the tool first, then connect.
- Preloader recovery. A device with a broken preloader can often still be reached in BROM, which gives you a second chance Qualcomm's single emergency mode does not structure the same way.
- Format options. MediaTek tools typically offer format modes that differ in how much they erase. The aggressive options can take NVRAM with them, which is where IMEI disappears after a MediaTek flash.
- Secure boot on newer chips. Older MT65xx parts are very open. Newer ones implement authentication that blocks unsigned DA files entirely — the same direction of travel as everything else in modern Android.
Frequently asked questions
- Which mode should I aim for, preloader or BROM?
- Preloader if the device still reaches it, because it is less fiddly. BROM when the preloader is damaged or unreachable.
- Why does the port vanish immediately?
- That is BROM behaving normally. Have the tool running and waiting before you connect the cable.
- Can I use a scatter file from a similar model?
- The same caution applies as with Qualcomm packages — compare the layout first. See which parts genuinely carry variant-specific data.
- My MediaTek phone lost IMEI after flashing.
- Most likely a format option that took NVRAM with it. The IMEI guide covers what legitimately restores it.
- Is MediaTek easier or harder than Qualcomm?
- Older MediaTek is generally easier. Newer secure-boot parts can be harder than the Qualcomm equivalent.
Working on a MediaTek device and not sure which mode you are in? Tell me the chipset and what your PC shows. Preloader and BROM look different in Device Manager.