A Samsung that is not a Samsung platform
Samsung's budget and mid-range lines increasingly use MediaTek SoCs. The A15 is one of them, which means the Odin/Download-mode advice written for Galaxy flagships does not apply.
The tell is the USB vendor ID when the device enumerates in preloader: 0E8D is MediaTek. A Samsung semiconductor part would present differently.
Why the key combination differs
Download mode on an Exynos or Snapdragon Galaxy uses Volume Down + Power. BROM on a MediaTek Galaxy uses Volume Up + Volume Down with the device powered off.
Using the Download-mode combination on a MediaTek device simply boots the phone, which then lands on the FRP screen and looks like the method failed. It is the wrong entry sequence, not a failed unlock.
The BROM procedure
With the phone off and both volume keys held, connecting the cable puts the chipset into Boot ROM before Samsung firmware loads. FRPB then performs the DA handshake, formats the FRP partitions, and reboots.
The console streams each phase. If the handshake never answers, re-check key timing before suspecting the tool.
If you only have a Bluetooth COM port showing
FRPB deliberately ignores Bluetooth and virtual COM ports — a headset on COM3 will never be treated as your phone. If the detector reports nothing, the phone genuinely is not enumerating.
That points at the cable, the port, or the driver. Work through those three before trying anything else.
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 Galaxy A15 off completely.
- 2Hold Volume Up + Volume Down together.
- 3Connect the USB cable while holding both keys.
- 4Wait for the MediaTek USB Port to appear in Windows.
- 5Confirm FRPB reports BROM / Preloader.
- 6Run FRP Bypass and accept the disclaimer.
- 7Allow the format sequence and automatic 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.