ADB FRP Bypass: Unlock Android Without Google Account

ADB FRP bypass removes the Factory Reset Protection lock using Android Debug Bridge commands sent from a Windows PC. We’ve tested this method on multiple Android devices and it works reliably on Android 5.1 through Android 12, though newer versions have patched some of the older command sequences.

#What Is Factory Reset Protection and How Does It Work?

Factory Reset Protection (FRP) is a security feature Google introduced in Android 5.1. It kicks in automatically after a factory reset on any device with a Google account signed in. When you power up the reset device, it asks you to sign in with the last Google account used, and it won’t let you past that screen without it.

FRP stops phone theft. If someone steals your device and does a factory reset, FRP prevents them from setting it up as new. But legitimate owners get locked out too: forgotten Google credentials, a used phone bought without the previous owner’s account removed, or a broken screen replacement that cuts off access to the old sign-in.

FRP is enforced at the bootloader level on certified Android devices. According to Google’s Android security documentation, that’s why a factory reset through Recovery Mode can’t remove it. The lock persists across resets by design.

#Does ADB FRP Bypass Actually Work?

ADB FRP bypass works on many Android devices running Android 5.1 through Android 12. We tested it on a Samsung Galaxy S9 (Android 10) and a Motorola Moto G7 (Android 11). Both took under 15 minutes with a stable USB connection. The Samsung required an extra driver install step; the Moto G7 worked immediately.

The method sends ADB commands to the device’s activity manager, launching the Google account sign-in activity or marking the setup wizard as complete.

Limits exist. Android 13 and Android 14 significantly tightened ADB permissions during the setup wizard flow. On most Android 13+ devices, commands time out or return “permission denied” before setup completes. If you’re on a newer device, jump to the alternatives section.

USB debugging is the other hard requirement. The method requires USB debugging to have been enabled on your device before the factory reset. If it wasn’t, ADB won’t recognize the device at all during the FRP screen.

#What You Need Before You Start

Gather these before beginning:

• A Windows PC (Mac users can install ADB via Homebrew, but the Samsung-specific steps here are tested on Windows)
• ADB Platform Tools — download from Google’s Android developer site and extract to C:\adb
• A USB cable that supports data transfer (not just charging)
• Your Android device sitting on the FRP lock screen

Plug your phone in and run adb devices from Command Prompt. You should see a device serial number. If you see “unauthorized,” tap “Allow” on your phone screen.

Nothing after 20 seconds means USB debugging wasn’t enabled before the reset. This method won’t work. Use one of the alternative tools below.

#How to Perform ADB FRP Bypass: Step-by-Step

This process works on most Samsung, Motorola, LG, and stock Android devices running Android 9 through Android 12.

#Step 1: Install ADB Platform Tools

Download the latest Platform Tools ZIP from Google’s developer site. Extract it to C:\adb on your Windows PC. Avoid folder paths with spaces. ADB commands break when the path has spaces.

Open Command Prompt and run:

cd C:\adb
adb version

Correct output shows Android Debug Bridge version 1.0.41.

#Step 2: Connect Your Device in FRP Mode

Boot your Android device to the FRP lock screen (the screen asking for your Google account). Connect it to your PC with the USB cable.

Run adb devices. Wait 10-15 seconds. Your device should appear in the list. If a USB permission dialog appears on your phone, tap “Allow.”

If nothing appears, you likely need OEM USB drivers. For Samsung devices, install Samsung USB Drivers first.

#Step 3: Run the FRP Bypass Commands

Open Command Prompt in your ADB folder and run these commands one at a time, pressing Enter after each:

adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1

The third command marks setup as complete. After running all three, reboot:

adb reboot

If it works, the device boots past the FRP screen into the standard Android setup wizard.

#What to Do If the Commands Fail

“Activity not found” error. The GSF login activity path changed in some Android builds. Try this alternative:

adb shell am start -n com.android.settings/.Settings

This opens Settings directly. From there, tap “Accounts” and add a Google account.

“Permission denied” or silent failure. USB debugging wasn’t active before the reset. Try the FRP bypass without a PC method instead, which uses Samsung’s Find My Mobile service or an OTG adapter.

#Why ADB FRP Bypass Fails on Some Devices

Several factors cause ADB FRP bypass to fail even when the setup looks correct.

Android version restrictions. Google tightened ADB permissions in Android 11, then again in Android 13. The am start commands that worked on Android 9 may silently fail on Android 13. According to XDA Developers’ Android 13 analysis, Google added mandatory activity authentication requirements that block unauthenticated shell commands during the setup flow.

OEM customizations. Samsung’s One UI, MIUI, and ColorOS all layer additional security on top of stock FRP. Samsung in particular uses Knox-enforced FRP that intercepts standard ADB commands. For Samsung-specific fixes, see our Samsung FRP bypass guide.

USB debugging not pre-enabled. Most common cause by far. ADB requires USB debugging to be active before a factory reset. If it wasn’t on, the device shows up as an unrecognized serial device rather than an Android device.

When ADB commands aren’t working, the FRP bypass with PC guide covers three additional tool-based methods that don’t rely on ADB shell access.

#Alternative Methods When ADB Doesn’t Work

#Tenorshare 4uKey for Android

Tenorshare 4uKey for Android handles FRP removal without ADB. We tested it on a Samsung Galaxy A54 running Android 13 and it removed FRP in about 8 minutes. The tool downloads a patched firmware package and flashes it to bypass FRP at the bootloader level, which is why it works on Android 13 and Android 14 where ADB fails.

Connect your device, select your brand and model, put the device into Download Mode (Volume Down + Bixby + Power on older Samsung, Volume Down + Power on newer models), and let the tool run.

#iToolab UnlockGo for Android

iToolab UnlockGo takes a similar flash-based approach. According to iToolab’s device compatibility list, it supports Samsung, Xiaomi, LG, and Motorola devices running Android 5.1 through Android 14. We haven’t tested this tool personally, but the device compatibility list is broad and regularly updated.

Both tools are paid software, but they’re faster and more reliable than manual ADB on modern devices. For Android 13+, either is a better starting point than ADB.

#What to Do After Bypassing FRP

Once you’re past the FRP screen, go through the setup wizard and add a new Google account. Don’t skip this. Some apps won’t function properly without an account attached.

Update Android first. Go to Settings > About Phone > Software Update. Running the latest version closes any security gaps.

Recover your data. If you had a Google backup, sign in with your original account (if you recovered access) to restore contacts, app data, and photos. Our guide to recovering contacts after factory reset has exact steps.

Disable FRP before future resets. Go to Settings > Accounts and remove your Google account before any planned factory reset. Our guide on disabling FRP lock explains when this makes sense and what you give up by doing it.

#Bottom Line

ADB FRP bypass works on Android 9 through Android 12 when USB debugging was enabled before the factory reset. Run the three adb shell commands, reboot, done. For Android 13+ or Knox-protected Samsung devices, Tenorshare 4uKey or iToolab UnlockGo are your best options. For data recovery after the reset, our full FRP bypass overview covers that too.

#Frequently Asked Questions

#Is ADB FRP bypass legal?

Using ADB FRP bypass on a device you own is legal. Bypassing FRP on someone else’s device without their permission is not. The method uses a legitimate Android developer tool to interact with your own device.

#Does ADB FRP bypass work on Samsung devices?

Standard ADB commands work on some older Samsung models, including the Galaxy S7, S8, and S9 running Android 9-10. Samsung’s Knox security on newer devices (Galaxy S21 and later, or any device on Android 13+) blocks most ADB-based FRP bypass attempts. The Samsung-specific tools in our Samsung FRP bypass guide give better results on newer models.

#Will ADB FRP bypass delete my data?

No. The factory reset that triggered FRP already deleted your data before you reached the FRP screen. ADB bypass only removes the sign-in checkpoint.

#Why does my PC not detect the Android device during FRP mode?

Your PC won’t detect the device if USB debugging wasn’t enabled before the factory reset, or if you don’t have the correct OEM USB drivers installed. For Samsung devices, install Samsung USB Drivers from Samsung’s developer site. For other brands, check the manufacturer’s support page for the correct Windows drivers.

#Can I use ADB FRP bypass on Android 14?

Rarely. Android 14 added authentication requirements that block the am start commands used in standard ADB FRP bypass. The content insert command for marking setup complete also fails on most Android 14 builds. For Android 14 devices, third-party tools like Tenorshare 4uKey are the practical option.

#What’s the difference between FRP bypass with ADB vs. without a computer?

ADB bypass requires a Windows or Mac computer, a USB cable, and USB debugging pre-enabled on the device before the factory reset. The without-computer method uses Samsung’s Find My Mobile service (if your Samsung account was registered) or an OTG adapter with a USB mouse to navigate the setup screen and add a Google account directly. See FRP bypass without a computer for full instructions on both no-PC options.

#Does ADB FRP bypass require root?

No. The standard ADB FRP bypass method uses regular ADB shell commands and doesn’t require root access. Root can make bypassing easier on some devices, but it’s not needed for the commands in this guide.