Why these three OEMs share one guide
Vivo, OPPO and Realme are all BBK-affiliated or BBK-adjacent manufacturers with broadly common firmware foundations. Their FRP implementations across MediaTek and Qualcomm models behave the same way: the lock is enforced at the account-verify step, and the reachable clearing routes are the chipset-level ones.
That means one documented procedure covers a large share of the handsets on a technician's bench. Where a specific model differs, it is almost always the chipset — not the OEM — deciding the route.
Choosing the route: MediaTek vs Qualcomm
Dimensity and Helio models are MediaTek and enter BROM or Preloader mode. Snapdragon models are Qualcomm and enter EDL (9008). The key combination is frequently the same, but what FRPB does afterwards and what the console reports are different.
FRPB detects the interface itself and tells you which one it found. You should always see the detected transport before any write begins.
Entering BROM or EDL mode
Timing matters more than anything else. The buttons must be held as power is applied via the cable — releasing early boots the phone normally and the whole sequence has to be repeated.
If the device was on, power it off first and verify the screen is genuinely black. On Qualcomm models that resist 9008 entry, an EDL or deep-flash cable can help by holding the data lines correctly at power-up.
- 1Power off fully — confirm the screen is black.
- 2Hold Volume Up + Volume Down together.
- 3Plug the cable in while holding both buttons.
- 4Keep holding for 5–10 seconds until the interface appears.
- 5Confirm in FRPB that BROM or EDL 9008 was detected.
ColourOS / Funtouch / Realme UI specifics
The Android skin names differ — ColorOS, Funtouch OS, Realme UI — but none of them expose a settings path from the FRP screen that can disable the lock. The OEM skins add features above Android; FRP is enforced by the framework and the account service underneath.
This is why skin-specific tutorials that promise a settings-based bypass are almost always republished content from a pre-Android-11 era. The reliable path is below the OS, which is what this guide documents.
Troubleshooting failed attempts
If the console reports that no device was found, the driver did not bind or the cable dropped the link. Install the matching VCOM or HS-USB driver from the FRPB Driver Center, plug directly into a rear-panel USB port, and retry.
A device that enters the mode but then disappears mid-write is nearly always a power or cable problem. Charge it above 30% and replace the cable before repeating the operation.
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.