Fix “This Device was Reset to Continue Sign in with a Google Account”

With Android devices, it is now a common issue experienced by many Android users to get this error: “This Device Was Reset To continue sign in with a Google account that was previously synced.” In this dedicated guide, I will explain how you get this error and what solutions there are to bypass the Google account screen.

This Device Was Reset. To Continue, sign in with a Google account that was previously Synced Samsung Galaxy S21

Verifying your account with your Google Account Samsung Galaxy S21 Android 12

As you can see in the above photo, a Samsung Galaxy S21 has the same error that will prevent you from setting up your phone and using it. It is now FRP-locked and cannot be used for any daily use to make calls, take photos, or use it for social media.

How is this error is triggered?

The error you see on your Android device screen has an FRP lock triggered by a wipe data factory reset through Android recovery. Android Factory Reset Protection (FRP) protects your device from unauthorized access in the event of being lost or stolen. Since most devices are locked with a pattern or PIN lock, new users try to wipe data factory reset it using Android recovery, which is the easiest option to hard reset a phone.

This hard reset triggers the FRP lock on your device. To use the phone, you need to use the pattern lock or sign in with a Google account that was previously synced on the device, hence you’re getting this error.

The majority of the users getting this error are those who bought their phones from eBay or the local market, not knowing that the previous owner had removed the Google account or default factory reset it from the phone settings (which is the right way to do it, if you’re planning to sell your phone in the future).

Bypass Google Account Verification after Factory Reset

To successfully bypass Google account verification after the reset, you need to do a lot of hard work and research. Because when Google introduced Factory Reset Protection with Android 5.1 back in 2014, the security was not as strong as it is today. Today, the latest and most stable version of Android is version 12 and Android 13 is in beta testing and will soon be released.

Also, Android security updates are released on a monthly basis, known as the security patch level. What they do is improve the security of FRP features. Let’s say you’re reading or watching a tutorial on how to bypass Google account verification for your specific phone model. You’ve read and followed the complete guide, but you find it’s not working for you, even though it shows the same model as yours.

So that is how Google security updates are working to keep your phone secure.

So what’s the best way to bypass Google account?

If it is your personal device and you’ve forgotten the Google account or password, then there is some chance to unlock your phone. You also get the option to draw a pattern lock that was previously used, so if you remember it, you’re lucky as it will unlock your phone within minutes. Then you have to follow the Google account recovery process if you remember the Google account.

Later, if you successfully reset your password through the recovery process, it can take up to 24-48 hours to get your password synced, so you need to wait for it.

In the second case, you don’t have many options. If it is not your personal phone and you bought it from someone, So, in that case, you need to follow a complicated process to find a working guide for your phone model.

I have written several FRP bypass guides for Samsung and other Android brands such as Google Pixel, ZTE, LG, Huawei, Oppo, and so on. These Android phone manufacturers have made several phone models, and they are releasing new models almost every month.

These phones also come with different Android versions and security features. The Galaxy S22 Ultra, for example, runs Android 14, while the Galaxy S9 should run Android 10. So there is no single bypass tool or method to remove a Google account.

Therefore, the Galaxy S22 may have a different bypass method than the Galaxy S9 because they are totally running different versions. The Google security patch level should have already fixed the method that was working in the Galaxy S9 Android 10 version.

Bypass Google Account Verification on Samsung Phones

To bypass the FRP lock on Samsung phones, you need a holistic approach to successfully unlocking your phone. As I said above, methods are different for all Android versions and devices, but one thing is common to get rid of Google lock: you need to access the Chrome browser on your locked device to download the unlock tools and remove the Google account.

Here are the common methods that can help you open Google Chrome on your phone and later download the required apps to get the work done.


Different methods are for different Android versions. Even the above methods can be used differently on the newer versions of Android. If you want to learn more about the above-mentioned method, If your device is running Android 12 or below then download FRP Bypass Apk 2023 which is a more effective way to get rid of Google account. If your device is running the latest Android 13 security and you’re tired of trying all the bypass methods without any luck then I would recommend you to use our paid frp unlocking for all Samsung phones and tablets to get it unlocked within 5 mins without wasting further time.

Share it with friends
Imran Aftab

Hello, I'm Imran Aftab, a tech enthusiast using Android, iOS, and Windows. Hardware expert for Gaming & Crypto mining rigs. I have been writing on tech since 2013, starting with ohguideme, then Androidcentral. I have written and published several guides and tutorials on how to root Android, flash custom ROM, recovery, and jailbreak iPhone, and have written several guides on how to bypass FRP. I also worked in a phone repair shop, so I have pretty good experience with mobile software and troubleshooting. So, all the guides you see here have been tested and confirmed to work.

Click Here to Leave a Comment Below 0 comments