An FRP lock (Factory Reset Protection) is a built-in Android protection that ties a device to the Google account that was last signed in on it and to its screen lock, so after any reset performed outside the Settings menu the phone asks for that account again. The device boots, then stops at the setup screen with a message such as “This device was reset”, and setup cannot be completed without signing in with the previous account. That is why handling a locked device starts with diagnosis and proof of ownership, not with plugging in a cable and trying tools at random.

What is FRP lock on Android and why does it appear?

FRP stands for Factory Reset Protection: a system-level guard that links the device to the previous Google account and to the screen lock. It activates automatically as soon as a Google account is added and a PIN, pattern or password is set, and there is no on/off switch for it in Settings. The supported way to remove it is to delete the Google account before resetting the phone (Asurion).

The feature is present on Android 5.1 and later. The verification key is kept in secure storage and survives a factory reset, which is why the lock does not disappear simply because the data was wiped (CPU Academy).

Wording differs by brand: Samsung, Pixel, Xiaomi and others show broadly similar text such as “This device was reset — sign in with your Google account”, and some models add a line with part of the address (g•••@gmail.com) to remind the customer which account is required.

The point many technicians get wrong: an FRP-locked phone is not faulty and not necessarily stolen, but it is also not a device you start working on just because it is asking for an account.

Authorised vs unauthorised factory reset

When a customer resets the phone from inside Settings while signed in to their own account, the system treats the reset as authorised and does not ask for the account on the next boot.

A reset from Recovery Mode, or a data wipe with an external tool, leaves the verification key in secure storage and the account is requested at boot (Asurion).

In the shop it looks like this: the customer who did not remove their account before formatting comes back with a phone stuck on the setup screen, and many of them no longer remember the old password or have access to the old recovery number.

The system does not block the reset; it blocks completing setup afterwards. Put that sentence on the job sheet and explain it before you start — it prevents half of the arguments you would otherwise have.

Diagnosing the case before you touch the device

Before connecting any cable, read the on-screen message word for word and write it on the job sheet. The difference between a Google account lock after factory reset, a manufacturer account lock and a network lock decides the whole path, and getting it wrong wastes time on a route that does not fit the case.

  • Read the screen: is it asking for an email address? A manufacturer account password? A network unlock code?
  • Check the IMEI (emergency dialler, the back of the device or the box) and match it to the document the customer brought.
  • Record model, Android version and build number — they decide which tools and firmware apply.
  • Ask short questions: who bought the phone? Is there a family member's account on it? Has anyone else already tried a reset or a repair?
What the screen showsLock typeWhat it meansNext step
“This device was reset” and it asks for a Google emailFRP lockUnauthorised reset with a previous Google accountVerify ownership, then customer sign-in or the supported route
Asks for a PIN or pattern at boot but the system works afterwardsScreen lockDevice is intact and the data is still thereVerify ownership, then a screen-lock solution that avoids an unnecessary wipe
Asks for Samsung account or manufacturer account credentialsManufacturer account lockProtection tied to the brand account, not to GoogleAccount recovery or an authorised service centre
“Network unlock PIN” or the SIM is rejectedNetwork/operator lockDevice is restricted to one carrierRefer to the carrier, or a documented network unlock that fits your market

Proof of ownership: what a shop can realistically accept

One simple rule protects the business: no work starts until the person in front of you is tied to this specific device. That is not paperwork for its own sake — it is the line between a professional shop and one that takes in anything that walks through the door.

Proof that works in practice includes an original invoice showing the IMEI or serial number, a carrier account record, the customer signing in to their own account in the shop, or a manufacturer account record (CPU Academy). One clear document that matches the device is enough.

  1. Ask for the document and match the IMEI to the device in front of the customer.
  2. Fill in a job sheet with name, phone number, IMEI, fault description and the exact procedure requested.
  3. Add a data clause: what can be backed up, what may be lost, and the limits of your liability.
  4. Get the customer's signature and hand over a printed intake receipt — thermal printing makes this a quick step at the counter (thermal printing guide for repair shops).
  5. If ownership cannot be shown: stop, write the reason for refusal on the job sheet, and return the device as it came in.

The same steps protect the relationship with the customer. When someone sees that the shop asks about the IMEI and a document because it is protecting their device, they accept the request instead of feeling suspected.

The safe professional path: customer sign-in first, then the right tools

The first route is always the fastest and cheapest: the customer signs in on the device at the counter, or recovers the account from another phone or a computer. Ask about an older email used on the device, a family member's account, or a former work account. If sign-in succeeds once, ask them to delete the account in Settings and then reset from inside the system, and the device leaves protection the supported way.

If the account is genuinely gone (deleted mailbox, dead number), the second route is flashing original firmware that matches the model and CSC exactly, using the manufacturer's own utilities: Odin for Samsung, MiFlash for Xiaomi, QFIL or EDL mode for Qualcomm devices (CPU Academy). Mismatched firmware does not remove the lock, and usually adds a boot or network fault on top of the original problem — on a Samsung FRP lock the CSC match is what decides whether the flash helps or hurts.

Professional tools — boxes, servers, FRP removal tools for repair shops, flashing utilities — are ordinary workshop equipment, like a soldering station or a programmer. The difference is not the tool but the procedure: a device with verified ownership, a signed job sheet, and a tool chosen to match the model and Android version. You can stock your bench from the GSM tools store at Warshati Plus (unlock tools, servers, software licences, wallet top-ups by local and international payment methods) according to the devices you actually take in.

There is a third route that matters just as much: referral. Any case involving a carrier lock, a theft report or an ownership dispute is not handled in the workshop — it goes to the carrier or an authorised service centre with proof of purchase. Samsung itself points customers stuck on the FRP screen to that route (Google Support).

One rule covers all of it: verify ownership first, refuse suspicious devices, and keep a record of what you did. A shop that works this way protects its reputation with customers and with local authorities in any market.

Protecting customer data while you deal with the lock

Some customers assume that removing FRP means getting their photos and files back. In reality a phone that reached the FRP screen has already been reset and holds no data. Explain that before the job, not after.

  • Back up whatever is reachable before any procedure, and state the limits of that backup on the job sheet.
  • Written warning that some routes end in data loss, especially if the phone has already been formatted once.
  • Document the outcome: technician notes, before-and-after screen photos, and the final state of the device.
  • A permanent record against the IMEI in your customer database, so the device history appears at the next visit next to the earlier receipt and notes.

This is where a repair-shop management system such as Warshati Plus saves real time: an intake receipt that carries the IMEI and device condition, technician notes attached to that device, and a customer record showing every previous visit — instead of searching paper books or chat threads. If you are still building your shop's procedures, our guide on running a mobile repair shop day to day sets out the order of these steps from intake to delivery.

Common mistakes that cost a shop time and reputation

  • Flashing firmware that does not match the CSC, then retrying with the same file several times. After two consecutive failures with correct firmware, stop: the problem is most likely hardware.
  • Changing device partitions with no written record, so later nobody can show what was done or by whom.
  • Handing a device back without documenting ownership, then a complaint or a theft report arrives a week later.
  • Forgetting to delete the Google account before selling or handing over a used phone — the lock returns for the new owner and the phone comes back to the shop.
  • Taking an FRP bypass route under time pressure without checking model and Android version first; the risks run from a bootloop to a device that will not activate at all.
  • Promising “unlock with no data loss” before seeing the device and knowing its Android version.

Preparing a device for sale or handover without the lock coming back

The correct way to remove the protection is to delete every Google account from the device before resetting it, then check that no manufacturer account lock is attached. Boot the phone after the reset all the way to the welcome screen before handover; if the account screen appears, the job is not finished.

Platform changes matter for the expectations you set. Android 15 closed several loopholes used during setup bypass by blocking new account creation, screen-lock changes and app installation in that state (Notebookcheck). The next update, announced at The Android Show: I/O Edition in May 2025 and reported as arriving later that year, goes further: the system demands a second factory reset and refuses to boot at all — calls included — when it detects an unauthorised reset, until the original credentials are entered (Notebookcheck).

What does that mean in practice? Set the expectation at intake: “We will try the supported route first, and if the account is gone the fix may involve a full reset.” That is better than a promise you cannot keep on a device running the newest Android, and better than leaving the phone on the bench for days with no clear answer.

Make proof of ownership a daily habit: an intake receipt with the IMEI, a signed data disclaimer, and technician notes on every device. If you want those steps in one place with the cashier, inventory and reports, start a free trial of Warshati Plus — it works fully offline and syncs between devices when the connection returns.