Forgot password from Google account, bought a used smartphone linked to someone else's data, or encountered FRP blocking (Factory Reset Protection) after a reset? Flashing Android firmware without being tied to a Google account is a risky task, but it can be done. In this article, we will look at legal and non-obvious ways to bypass restrictions, from official tools to custom firmware.

It is important to understand: Google actively blocks FRP bypass on new versions of Android (starting from 11+), so methods for Samsung Galaxy S22 and Pixel 7 will differ from solutions for Redmi Note 8 2019 year. We will focus on universal approaches, but some steps will require adaptation to a specific model.

We warn you right away: bypassing FRP may violate the terms of use of the device. If the smartphone is not yours, return it to the owner. If this is your device, but you have forgotten your account details, first try to restore access through Google service.

Why Android requires a Google account after flashing

Mechanism Factory Reset Protection (FRP) appeared Android 5.1 Lollipop as a security measure. Its goal is to prevent the use of stolen devices. After resetting the settings or firmware, the system requests the data of the last linked Google account, even if you installed a clean version of Android.

FRP is triggered in three cases:

  • 🔄 Reset to factory settings through the recovery menu (Recovery Mode).
  • 📱 Firmware via Fastboot/ODIN without first shutting down FRP.
  • 🔓 Deleting a Google account manually through settings (on some devices).

Manufacturers like Samsung i Xiaomi add their own layers of protection. For example, Galaxy may require entering PIN code. SIM cards, and Redmi - binding to Mi AccountThis complicates universal solutions.

📊 For what purpose do you want to flash Android without a Google account?
I bought a used phone with FRP
Forgot my account details
I want to install custom firmware
Other

Preparing for firmware: what needs to be done BEFORE resetting

If you still have access to the device, follow these steps to avoid problems with FRP:

Delete Google account in Settings → Accounts

Disable Find device (Settings → Google → Security)

Back up your data (photos, contacts, SMS)

Remember or write down the IMEI of the device (*#06#)

-->

On devices Samsung additionally disable Reactivation Lock in the security settings. On Xiaomi - unlock Mi Account (if linked).

If access to the device has already been lost, proceed to bypass methods. But remember: Flashing through unofficial tools can lead to loss of warranty and unstable system operation.

Method 1: Bypass FRP via Fastboot (for an unlocked bootloader)

This method is suitable for devices with unlocked bootloader (bootloader). If you have never officially unlocked it (for example, through fastboot oem unlock), the method will not work.

You will need:

  • 💻 A computer with Windows/Linux installed drivers ADB/Fastboot.
  • 🔌 Cable USB Type-C (original, no damage).
  • 📦 Firmware for your model (official or custom).

Steps:

  1. Turn off the phone and press combination to enter Fastboot Mode (usually Power + Volume Down).
  2. Connect the device to the PC and check the connection with the command: 
    fastboot devices

    If the device is not detected, install the drivers manually.

  3. Unlock the bootloader (if not already unlocked): 
    fastboot flashing unlock

    On some devices (Pixel, OnePlus) you will need confirmation on the phone screen.

  4. Flash the modified boot.img without FRP check or install custom recovery (TWRP): 
    fastboot flash boot patched_boot.img
  5. Reboot the device. At the setup stage, skip linking the account.
💡

On devices Xiaomi after unlocking the bootloader you will have to wait 72-168 hours (depending on the model) before flashing the firmware. This is a company limitation and cannot be circumvented.

⚠️ Attention: On new devices (Android 12+) Google has closed many loopholes in Fastboot. If FRP remains active after flashing, try the method with ADB (see next section).

Method 2: Using ADB to remove FRP (without unlocking the bootloader)

This method works on some devices with Android 9–11where vulnerabilities remained during the setup process. You do not need an unlocked bootloader, but you will need access to ADB in Setup Wizard.

Instructions:

  1. During the initial setup, connect the phone to the PC and open Command Prompt.
  2. Check the connection: 
    adb devices

    If the device does not apparently, install the drivers Google USB Driver.

  3. Run the ADB shell: 
    adb shell
  4. Delete the files responsible for FRP: 
    rm /data/system/gesture.key

    rm /data/system/locksettings.db
    

    rm /data/system/locksettings.db-wal
    

    rm /data/system/locksettings.db-shm

  5. Reboot the device: 
    reboot

After reboot, go through the setup again - the Google account request should disappear. If not, try alternative commands:

adb shell am start -n com.google.android.gsf.login/

adb shell am start -n com.google.android.gsf.login.LoginActivity

Why this method stopped working on new Android

Starting with Android 12Google has tightened its control over ADB in setup mode. Now, access to the shell requires an unlocked bootloader or confirmation on the device, which makes bypassing FRP via ADB almost impossible without prior preparation.

Method 3: Flashing custom software (TWRP + Magisk)

If the official methods do not work, the option remains with installation custom recovery (TWRP) and modified firmware. This is the riskiest path: you can lose the warranty, encounter unstable operation, or even brick- destroy the device (turn it into a “brick”).

Procedure:

  1. Download TWRP for your model from the official website twrp.me.
  2. Install it via Fastboot: 
    fastboot flash recovery twrp-3.7.0_9-0-redfin.img

    (replace the file name with the current one).

  3. Boot into TWRP (usually Power + Volume Up).
  4. Make a backup copy of the partition data (in case of errors).
  5. Flash a ZIP file with a patch to bypass FRP (for example, FRP_Bypass.zip from trusted sources).
  6. Install Magisk for root access (optional, but will help in future settings).

After reboot FRP must be disabled. However, please note:

  • ⚠️ On some devices (Samsung Exynos, MediaTek) TWRP may not work correctly.
  • 🔧 Custom firmware often deprives the device of certification Google Play Protect.
  • 📱 Banking applications (SberBank Online, Tinkoff) may refuse to work on rooted devices.
💡

Custom firmware is the last chance to bypass FRP, but they are only suitable for experienced users. For most tasks, it is better to use official methods or contact a service center.

Not all methods work on all devices. Below is a brief overview of compatibility:

Brand/Model Fastboot ADB TWRP Notes
Google Pixel 4–7 ✅ (with unlock. bootloader) ❌ (on Android 12+) ✅ Requires official unlocking via fastboot flashing unlock.
Samsung Galaxy S20–S23 ❌ ⚠️ (only on Android 10) ❌ (due to Knox) It is better to use Odin with a patch FRP Reset.
Xiaomi Redmi Note 10–12 ✅ ✅ (on MIUI 12–13) ✅ Requires waiting 72+ hours after unlocking the bootloader.
OnePlus 8–11 ✅ ❌ ✅ Firmware via MSM Tool resets FRP.
Realme/Narzo 30–50 ⚠️ (partially) ✅ (on Realme UI 2.0) ✅ Use Realme Flash Tool for official firmware.

⚠️ Attention: Manufacturers regularly update protection. If your model is not listed or the method did not work, check the latest information on forums like XDA Developers or 4PDA.

What to do if nothing helps

If all of the above methods did not work, you have three options left:

  1. Contact the service center:

    Official centers (Samsung Service, Xiaomi Authorized) can remove FRP by documents for the device (receipt, warranty card). Cost - from 500 to 2000 rubles.

  2. Buy paid software to bypass FRP:

    apps like FRP Hijacker or SamFw Tool promise bypass for 10–30 dollars. Risk: many of them contain malicious code or do not work on new firmware.

  3. Use a device without Google services:

    Install firmware without GApps (for example, LineageOS without Google) or use alternative services (MicroG, FDroid). Minus: there will be no Play Market, Gmail other Google applications.

If the smartphone was purchased second-hand, try contacting the previous owner. In some cases (for example, on Samsung), you can delete an account remotely via Find My Mobileif the previous owner agrees to help.

FAQ: Frequently asked questions about bypassing FRP

Is it possible to bypass FRP without a computer?

On older devices (Android 8–9), tricks with Wi-Fi settings or emergency calls sometimes help. For example:

  1. During the setup stage, connect to Wi-Fi.
  2. Go back and click "Emergency call".
  3. Dial ##4636## and try to open the settings.

On new Androids (11+) these methods do not work - you need a PC.

Why did the FRP remain after flashing via Odin?

Odin it only flashes system partitions, without affecting /datawhere the FRP data is stored. To completely reset the protection, you need to:

  1. B Odin select option Nand Erase All (if available).
  2. Or after flashing go to Recovery Mode and do Wipe Data/Factory Reset.

On Samsung s Exynos sometimes flashing a combination helps files AP + BL + CP + CSC (not Home_CSC!).

How to check if the bootloader is unlocked?

Turn off the phone and hold down the buttons to enter Fastboot Mode. If you see the message Device State: Unlocked , the bootloader is unlocked. If Locked - you will need an official unlock.

On Xiaomi the status can be checked in Developer Options (Mi Unlock Status).

Will Google Pay work after bypassing FRP?

If you used custom firmware or root access Google Pay will refuse to work due to a violation SafetyNetSolutions:

  • Install Magisk and module Universal SafetyNet Fix.
  • Use alternatives: Samsung Pay, Mir Pay or virtual cards.
Is it possible to return the official firmware after bypassing the FRP?

Yes, but with reservations:

  • On Pixel i OnePlus you can flash the official image via Fastboot.
  • On Samsung required Odin with the flag Re-Partition (risk of data loss!).
  • On Xiaomi after returning to the official firmware it can return FRP, if it was not disabled initially.

Before flashing the firmware, make a backup copy in TWRP!