What BROM is, and why it matters
The Boot ROM is a small, immutable first-stage loader burned into the MediaTek SoC at manufacture. It runs before any firmware, before the bootloader, and before Android — it is what loads everything else.
Because it cannot be patched by a software update, and because it must be reachable to let a factory flash an otherwise-dead board, it remains open. That is the property every BROM-based FRP method depends on.
No test point needed
Some MediaTek service procedures require shorting pads on the mainboard to force BROM. That is for devices with disabled key entry or a corrupt preloader.
For a normal FRP-locked handset the key combination is sufficient. Try it before considering disassembly — opening a phone risks the seal and any remaining warranty for no benefit on most units.
The DA handshake
BROM itself only knows how to load a Download Agent — a small signed program that gives the host richer partition access. FRPB performs that handshake and then drives the DA.
If the handshake does not answer, the phone is not in BROM. That is a cable, key-timing or driver problem, not a tool limitation, and FRPB reports it as such instead of proceeding.
Why the console shows raw output
FRPB streams every command and the device's every response. That is deliberate: when a partition format is refused, the refusal carries the reason, and hiding it behind a spinner would make the failure undiagnosable.
Read the last few lines before any failure. In practice the cause is nearly always visible there.
Step-by-step procedure
Follow the sequence below in order. Each step is also published as structured HowTo data, so search results can surface it as a step-by-step list.
- 1Power the MediaTek device off completely.
- 2Hold Volume Up + Volume Down together.
- 3Connect the USB cable while holding both keys.
- 4Hold for 5-10 seconds until Windows reports a MediaTek USB Port.
- 5Confirm FRPB detects BROM / Preloader.
- 6Run FRP Bypass and accept the disclaimer.
- 7Let the DA injection and partition format complete, then reboot.
Safety, legality and when to stop
FRPB is intended strictly for authorised device owners and licensed repair professionals. You must own the device or hold explicit written permission from its owner. Using an FRP bypass tool on hardware you do not own may defeat an anti-theft control and can be illegal in your jurisdiction.
Stop and reassess if the device reports a bootloader state you did not expect, if the model or chipset FRPB detects does not match the handset in front of you, or if the operation halts mid-way. A mismatched firmware package is the single most common cause of a hard brick — abandoning an operation is always cheaper than recovering from one.