1. Desktop app installation & driver setup
Requirements
- Windows 11, 10, 8 or 7 (64-bit)
- A data-capable USB cable (not charge-only)
- An authorised Android device, charged above 50%
- An FRPB licence for paid operations
- 1
Download the official FRPB-Recovery-V2-Setup-2.0.0.exe installer (v2.0.0) from the FRPB download page or the GitHub v2.0.0 release asset.
- 2
Verify the downloaded file name and size match the published release before running it, so a mirror copy can be ruled out.
- 3
Run the installer on a Windows 10 or Windows 11 64-bit PC and complete the setup wizard.
- 4
Open FRPB and let the one-click driver installer detect and install the correct Samsung, Google, MediaTek or Qualcomm USB driver.
- 5
Enable Developer Options and USB debugging on the Android device, then approve the RSA fingerprint prompt when it appears.
- 6
Connect the device with a data-capable USB cable — not a charge-only cable — and confirm FRPB lists the device and its detected mode.
USB driver setup
FRPB ships a one-click OEM driver installer. When a device is not detected, open the driver panel inside FRPB and let it install the matching driver for the brand you are servicing — Samsung, Google Pixel, OnePlus, Xiaomi, MediaTek or Qualcomm. If Windows still binds a generic driver, open Device Manager, uninstall the device entry (including the driver software), reconnect the phone and re-run the FRPB driver installer.
Keep the phone on a rear-panel USB port of a desktop PC where possible. Front-panel ports, unpowered hubs and USB-C docks are the most common cause of a device dropping out mid-operation.
2. Bootloader unlock safety & backup precautions
Unlocking the bootloader wipes all userdata. It also destroys the storage encryption keys and voids most manufacturer warranties. There is no undo — back up first.
A bootloader unlock removes the verified-boot restriction that stops unsigned code from starting. That is what makes custom recovery, root and ROM flashing possible — and it is also why every serious vendor requires an explicit OEM unlocking opt-in followed by a full data wipe.
Pre-unlock checklist
Confirm ownership and authorisation
Only unlock devices you own or are authorised to service. A locked, carrier-locked or policy-locked unit will be refused by the bootloader itself.
Take a full backup first
Copy photos, chats, call logs and any app data to a PC or cloud account. Unlocking wipes userdata and destroys the storage encryption keys — a partial backup is not recoverable afterwards.
Record the device state
Note the model number, build number, Android version and the current OEM unlocking toggle state before you start, so a failed unlock can be diagnosed against a known baseline.
Charge the battery and stabilise the cable
Use a charged battery (above 50%) and a short, data-capable cable in a rear-panel USB port. Interrupted fastboot sessions are the leading cause of self-inflicted soft bricks.
Remove screen locks and accounts you control
Disable the PIN/pattern and remove the Google account you can still access before unlocking. This avoids an FRP re-lock on the first boot after the wipe.
Accept the warranty and integrity trade-offs
Unlocking voids most manufacturer warranties and typically trips Play Integrity / SafetyNet, which can break banking, streaming and some games on that device.
Backup precautions
- Copy photos, video, documents and downloads to a PC folder you can verify — do not rely on a single cloud sync completing.
- Export WhatsApp / Telegram chats and media from inside the app before the wipe, not after.
- Note the Google account on the device. If it cannot be removed before the unlock, Factory Reset Protection will re-lock the phone on first boot.
- Record any app-specific two-factor authenticators, since re-enrolling after a wipe needs recovery codes you must already hold.
- Keep the stock firmware package for the exact model and build number ready, so a failed unlock can be restored rather than left in fastboot.
For the full command reference and brand-specific behaviour, read the Android bootloader unlock 2026 guide and the fastboot unlocking guide.
3. FRP bypass & flashing usage guides
FRP bypass workflow
Factory Reset Protection is the Google account lock Android applies after a factory reset. FRPB removes it only for an authorised owner, over a verified USB session.
- 1
Register or sign in to your FRPB licence in the desktop app so the operation is logged to your account.
- 2
Connect the device and let FRPB auto-detect the chipset and the available mode — Download, Recovery, EDL/BROM or fastboot.
- 3
Select the FRP bypass operation and follow the on-screen step for the detected chipset and Android version.
- 4
Keep the cable connected until FRPB reports completion, then reboot the device and verify the setup wizard completes without an account prompt.
Flashing & flash reset
Flashing restores known-good firmware. FRPB matches the firmware package to the exact model and build before writing, and verifies the partition images first, so a mismatched package is rejected instead of half-flashed.
- Confirm the model number, region code and build number match the firmware package exactly.
- Charge the battery above 50% and never disconnect mid-write — a partial flash is how devices become soft bricks.
- Use the flash reset option when the device cannot boot but the bootloader is still reachable; use EDL/BROM recovery only when no normal mode is available.
- Keep the generated log — it contains the exact sequence needed to diagnose any failure.
Android Bootloader Unlock 2026
Safe one-click fastboot OEM unlocking, OEM unlocking flag checks and unlock-state verification.
Bootloader unlock guideFastboot Unlocking Guide
Every fastboot unlock command, driver fix, slot check and 'fastboot devices not showing' remedy.
Fastboot guideFRP Bypass Tool
Remove Factory Reset Protection on an authorised device across Qualcomm, MediaTek and Exynos.
FRP bypass workflowFlash Reset Tool
Restore stock firmware and recover a device from a soft brick without a manual Odin session.
Flashing guide4. Troubleshooting steps
Device not detected
Swap to a data-capable cable and a rear USB port, re-run the FRPB driver installer, enable USB debugging and accept the RSA prompt. Uninstall any generic composite driver Windows bound automatically, then reconnect.
OEM unlocking toggle is greyed out
The unit is carrier-locked or policy-locked, or the device has not been connected to the internet since the last reset. FRPB refuses to continue in this state — it is a bootloader restriction, not a tool error.
Operation fails at 30–60%
Almost always a cable, hub or power problem. Use a short known-good cable on a rear port, charge the phone above 50%, close other USB-consuming tools and retry the identical operation.
Fastboot shows no devices
The phone is in the wrong mode or the fastboot driver is not bound. Re-enter the bootloader, reinstall the driver, and confirm with a fastboot devices scan before starting the unlock.
Device boots to a bootloop after flashing
Boot into recovery, wipe cache, and if the loop persists re-flash the stock package for the exact model and build. Never re-lock the bootloader while the firmware is mismatched.
Licence not recognised
Sign in again in the desktop app and confirm the licence is bound to this machine. If the key still fails, contact support at support@frpb.in with your order ID — never share the key publicly.
Disclaimer: FRPB is a device recovery utility intended strictly for authorized device owners and certified repair technicians. Users must own or have legal authorization for the devices they service. Use of FRPB to bypass security protections on unauthorized devices is strictly prohibited.