
You type the right password, the spinner turns, and then the same error comes back. The account works fine on another device, but the phone refuses to sign in. When google account sign-in error on android blocks Gmail, the Play Store, and sync all at once, the phone feels cut off from everything that matters.
The good news is that the account itself is usually fine. Sign-in errors on Android most often come from a wrong date and time, an outdated Google service, a stale account record on the phone, or a network that blocks the sign-in check. This guide works through those causes in order, from the simplest check to the deeper fixes. Never share your password or any verification code with anyone, and use only the official Google account recovery pages if you need to reset a password — no app or website can unlock an account for you.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Check Your Internet Connection and Try Again
- Fix 2: Check the Date and Time Settings
- Fix 3: Restart the Phone
- Fix 4: Try Signing In Through the Browser to Test the Account
- Fix 5: Update Google Play Services and the Google App
- Fix 6: Clear the Cache for Google Play Services
- Fix 7: Check Storage Space and Turn Sync Back On
- Fix 8: Remove and Re-add the Google Account
- Fix 9: Check 2-Step Verification and Use Official Account Recovery
- Fix 10: Check App Permissions and Battery Restrictions for Google Apps
- Fix 11: Reset the Network Settings
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
Signing in is a handshake between the phone and the account service. The phone proves who you are, the service checks the proof, and both sides must agree on the time, the connection, and the account details. When any part of that handshake fails, the phone shows a generic error that hides the real cause. These are the reasons the handshake fails most often.
1. The Date and Time on the Phone Are Wrong
Sign-in security depends on the clock. The phone and the server exchange time-stamped tokens, and if the phone clock is minutes or hours out, the server rejects the proof as expired or not yet valid. A phone set to the wrong time zone, or with automatic time turned off after travel, fails sign-in even with the correct password. This cause is invisible in the error message, which never mentions the clock.
2. The Internet Connection Blocks the Sign-In Check
The sign-in check needs a stable connection to the account servers. A weak Wi-Fi signal, a captive portal that needs a login first, or a network that blocks certain services can all interrupt the check halfway. The phone shows a sign-in error when the real problem is that the request never completed. Public Wi-Fi and workplace networks are the usual suspects, because they filter traffic in ways a home network does not.
3. Google Play Services Is Outdated or Its Data Is Stale
Google Play Services is the background service that handles sign-in, sync, and account checks for most Google apps. When it is outdated, it can fail a security check that newer versions pass. When its stored data is stale or corrupted, it can send an old account token that the server rejects. Either way, the error appears in Gmail or the Play Store, while the real fault sits in the background service neither app mentions by name.
4. The Account Record on the Phone Is Damaged
The phone keeps a local record of the signed-in account, including tokens that prove the sign-in is still valid. If that record is damaged by a failed update, a restore from a backup, or a storage problem, the phone keeps presenting proof the server no longer accepts. The account itself is untouched — only the phone copy of the record is broken. Removing and re-adding the account, as in Fix 8, rebuilds that record from scratch.
5. Two-Step Verification Is Waiting for a Step That Never Arrives
When 2-Step Verification is on, sign-in needs a second proof after the password, such as a prompt on another device or a code. If the prompt goes to a device that is off, or the code goes to a number that changed, the sign-in stalls and the phone reports a generic error. The password was correct. The second step simply never completed, and the error message does not say which step is missing.
6. Storage, Sync, or Battery Settings Are Starving the Sign-In Service
A phone with almost no free storage cannot save the new account tokens that sign-in creates. A sync setting turned off can block the account check that follows sign-in. A battery restriction can stop the background service before it finishes. Each of these looks like an account problem, but each is a phone setting quietly cutting off the service that sign-in depends on. The error message mentions none of them, which is why google account sign-in error on android survives so many password retries.
Quick Checks
Two minutes before the deep fixes.
- Check the clock — is the date, time, and time zone correct on the phone?
- Open a web page in the browser — does the internet work, or is the connection itself the problem?
- Try mobile data instead of Wi-Fi — does google account sign-in error on android disappear on the other connection?
- Check whether the account signs in on another device or in a computer browser.
- Look at free storage — is less than 1 GB free on the phone?
- Think about when it started — did the error begin after an update, a restore, or a password change?
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| Error on Wi-Fi only, fine on mobile data | Network blocking the sign-in check | Fix 1 |
| Error after travel or a time change | Wrong date and time settings | Fix 2 |
| Error in every Google app at once | Stale background service | Fix 3 |
| Error on the phone, fine in the browser | Phone account record damaged | Fix 4 |
| Error after a long time without updates | Outdated Play Services | Fix 5 |
| Error returns after every retry | Corrupted service cache | Fix 6 |
| Error with almost no storage free | No room to save sign-in tokens | Fix 7 |
| Error with a prompt that never arrives | Second verification step missing | Fix 9 |
Fix 1: Check Your Internet Connection and Try Again
Start with the connection, because a failed sign-in check looks exactly like a wrong password. If the request never reaches the server, no password can fix it. A quick connection test separates a network problem from an account problem in under a minute.

- Open the browser and load a web page to confirm the internet works at all.
- If the page fails, turn Wi-Fi off and try mobile data instead.
- If mobile data works, the Wi-Fi network is the problem — restart the router or stay on mobile data for sign-in.
- If you are on public Wi-Fi, open the browser and complete any login page the network shows.
- Turn off any VPN, then try signing in again — a VPN can route the check through a blocked server.
- Move closer to the router if the Wi-Fi signal is weak, and try once more.
- If sign-in works on the other connection, the account is fine — fix the network, not the password.
A captive portal is the sneakiest version of this problem. The phone shows a Wi-Fi connection, but every request is redirected to a login page until you accept the terms. Sign-in fails silently because the account request never leaves the portal. The browser test catches it, because the portal page appears instead of the web page you asked for. Once the portal is completed, sign-in usually works immediately. If the connection is solid and the error persists, the clock is the next suspect, and Fix 2 takes one minute.
Fix 2: Check the Date and Time Settings
A wrong clock breaks sign-in security in a way no error message explains. The phone and the server must agree on the time, and automatic time keeps them in step. This fix is short, safe, and fixes more sign-in errors than any other single setting.
- Open Settings, then System, then Date and time.
- Turn on Set time automatically if it is off.
- Turn on Set time zone automatically if it is off.
- Check that the displayed date and time now match the real date and time.
- If automatic time shows the wrong time, turn it off, set the time by hand, and try signing in.
- Restart the phone after changing the clock so every service picks up the new time.
- Try signing in again and note whether the error has changed or disappeared.
Manual time is the trap here. A phone set by hand drifts over weeks, and a drift of even a few minutes can fail a security token. Travel makes it worse: a phone carried across time zones with automatic time off keeps the old zone and fails checks that depend on the local time. Automatic time and automatic time zone together prevent both problems. If the phone is a work device managed by an employer, the time settings may be locked — in that case, ask the IT team to check the clock policy rather than fighting the setting yourself.
Fix 3: Restart the Phone
A restart clears stuck background services and gives the sign-in process a clean start. Google Play Services and the account service both restart fresh, and a temporary glitch that blocked the handshake disappears with them.
- Hold the power button and tap Restart, or power off and power on if no restart option shows.
- Wait for the phone to fully start and connect to Wi-Fi or mobile data.
- Open Gmail or the Play Store and try signing in again.
- If the error persists, restart once more after completing Fix 2, so the clock fix and the restart work together.
- Check for a notification asking you to re-enter the account password after the restart.
- If a notification appears, tap it and follow the sign-in prompt from the notification itself.
- Note the exact error message if it returns — the wording helps narrow the cause in later fixes.
A restart is simple, but it is not a waste of time. Background services can wedge in a failed state and keep failing every retry with the same stale token. Nothing short of a restart clears that state. Do not confuse a restart with a reset: a restart keeps every app, photo, and setting, while a reset wipes the phone. This guide never asks for a factory reset. If the error survives a restart with the correct clock and a good connection, the next step is to test whether the account itself is the problem, and Fix 4 does that without touching the phone account at all.
Fix 4: Try Signing In Through the Browser to Test the Account
The browser test answers the most important question in this whole guide: is the account fine and the phone at fault, or is the account itself locked? Signing in through the browser bypasses the phone account record entirely, so the result points clearly in one direction.

- Open the browser on the phone and go to the Google sign-in page.
- Enter the same email address and password that fail in the app.
- If the browser signs in, the account and password are correct — continue with the phone fixes below.
- If the browser also fails, read the exact message — it usually explains the account problem more clearly than the app error.
- If the browser asks for a verification step, complete it and note which method it used.
- If the browser says the account is locked or needs recovery, use official account recovery as in Fix 9.
- Do not change the password yet unless the browser clearly says the password is wrong.
A successful browser sign-in is genuinely good news. It proves the password, the account, and the second verification step all work, and it narrows the fault to the phone record or the background service. That is exactly the territory Fixes 5 to 8 cover. A failed browser sign-in is also useful, because it stops you wasting time on phone settings when the account needs attention first. Never enter your password on a page reached from a text message or email link claiming the account is locked — open the browser yourself and type the address, or use the official recovery pages linked at the end of this guide.
Fix 5: Update Google Play Services and the Google App
Google Play Services handles the sign-in handshake for most Google apps, and an outdated version can fail checks that current versions pass. The Google app itself also carries sign-in code that improves with updates. Both update through the Play Store, but Play Services hides in a less obvious place.
- Open the Play Store, tap the profile icon, then Manage apps and device.
- Tap Update all, and wait for every pending update to finish.
- Search the Play Store for Google Play Services and open its page.
- If an Update button shows, tap it and wait for the update to complete.
- Search for the Google app and update it too if an update is offered.
- Restart the phone after the updates so the new versions load cleanly.
- Try signing in again and check whether the error has cleared.
Play Services updates sometimes arrive silently in the background, and sometimes they wait for weeks when automatic updates are off. Do not assume it is current — open its store page and look. If the Play Store itself refuses to open because sign-in fails, update through Settings instead: open Settings, then Apps, then Google Play Services, and check the app details for a version and update prompt. For store errors that block updates entirely, our guide to Google Play Store server error fix covers the store side.
Fix 6: Clear the Cache for Google Play Services
A corrupted cache in the background service can keep presenting a stale sign-in token that the server rejects. Clearing the cache removes the stale data without touching the account, the apps, or any personal files. It is safe, and it is the fix most often skipped because the service is invisible.
- Open Settings, then Apps, then See all apps.
- Find Google Play Services in the list and tap it.
- Tap Storage and cache, then tap Clear cache. Do not tap Clear storage yet.
- Go back and find the Google app, then clear its cache the same way.
- Restart the phone so the services start with a clean cache.
- Try signing in again and watch whether the error changes.
- If the error persists, repeat the cache clear for Google Play Store as well, then restart once more.
Clearing the cache is not the same as clearing storage. Cache holds temporary files that rebuild themselves. Storage holds account data and settings, and clearing it signs apps out and resets their state. Stay with the cache for this fix. If a guide elsewhere tells you to clear storage for Play Services, treat it as a last resort and expect to re-enter account details afterwards. The cache clear in this fix is the gentle version, and it resolves the stale-token problem in most cases without any sign-out side effects.
Fix 7: Check Storage Space and Turn Sync Back On
Sign-in creates new tokens and account data that must be saved on the phone. A phone with almost no free storage cannot save them, so sign-in fails at the last step even though the password check passed. A sync setting turned off can also block the account check that follows sign-in.

- Open Settings, then Storage, and check how much free space remains.
- If less than 1 GB is free, delete videos or large files you no longer need, or move photos to a backup.
- Empty the trash in the photos app if deleted items are still taking space.
- Open Settings, then Accounts, then tap the Google account.
- Tap Account sync and check that sync is turned on for the main services.
- If sync was off, turn it on, then tap the menu and choose Sync now.
- Try signing in again and check whether the account now completes the handshake.
Storage pressure causes strange, unrelated-looking failures, and sign-in is one of them. The phone needs room not only for the token but for the temporary files the sign-in process creates along the way. Freeing a comfortable margin — several hundred megabytes at least — removes the doubt. Sync deserves the same attention: an account with sync disabled can sign in and then stall on the first sync check, which the phone reports as a sign-in failure. For sync that keeps stopping after sign-in succeeds, our guide to Google account sync keeps stopping covers that problem in full, and it is the right next read once you are signed in again.
Fix 8: Remove and Re-add the Google Account
When the local account record is damaged, no amount of retrying repairs it. Removing the account deletes the broken record from the phone, and re-adding it builds a fresh record with new tokens. The account itself, and everything stored with it online, stays untouched.
- Open Settings, then Accounts, then tap the Google account that fails to sign in.
- Tap Remove account and confirm. Read the warning — local copies of synced data are removed from the phone, not from the account.
- Restart the phone after removing the account.
- Open Settings, then Accounts, then Add account, and choose Google.
- Enter the email address and password, and complete any verification step that appears.
- Wait for the initial sync to finish before opening Gmail or the Play Store.
- Open Gmail and confirm new mail arrives, which proves the fresh record works.
The warning on removal worries many people, so read it carefully. Removing the account from the phone removes the local copy of synced contacts, calendar entries, and mail stored on the device. The online copies in the account remain safe, and they sync back down when the account is re-added. Photos and files stored only on the phone are not part of the account record and are not removed. If the re-add fails with the same error, the cause is deeper — the network, the clock, or the account itself — so revisit Fixes 1, 2, and 4 before trying anything more drastic. Never use a third-party tool that claims to remove or bypass the account lock: those tools are a common route to malware and stolen credentials.
Fix 9: Check 2-Step Verification and Use Official Account Recovery
When the second verification step never arrives, sign-in stalls no matter how correct the password is. The fix is to check which verification methods the account has, and to use only the official recovery pages if the account needs unlocking. No shortcut exists, and anyone offering one is not to be trusted.
- On another device or a computer browser, sign in to the Google account and open the security settings.
- Check which 2-Step Verification methods are listed — prompts, authenticator codes, or backup codes.
- Confirm the phone number on file is current, and that prompts go to a device you still own.
- Generate fresh backup codes and store them somewhere safe, away from the phone.
- If the phone sign-in asks for a code, use the authenticator app or a backup code — never share the code with anyone who asks for it.
- If the account is locked, use the official account recovery page from the browser, following its questions honestly.
- After recovery succeeds, sign in on the phone again and complete the verification step it requests.
Verification codes are the keys to the account. Google will never ask for a code by phone, text, or email, and neither will any legitimate helper. Anyone asking for a code, a password, or remote access to “fix” the account is attempting to steal it. The official recovery process asks questions only the account owner can answer, and it may take time — that delay is a security feature, not a fault. If recovery fails, keep trying with as much accurate information as possible, and do not pay any service that promises to recover the account faster. Those services cannot bypass the official process.
Fix 10: Check App Permissions and Battery Restrictions for Google Apps
Android battery and permission settings can starve the background service that sign-in needs. A restricted app cannot run in the background long enough to finish the handshake, and a missing permission can block a step the service needs. Checking both takes a few minutes and removes a quiet cause.

- Open Settings, then Apps, then See all apps, and find Google Play Services.
- Tap Battery and set it to Unrestricted or Not optimised, depending on the phone.
- Tap Permissions and make sure the permissions the service requests are granted.
- Repeat the battery and permission check for the Google app and Google Play Store.
- Turn off any data saver or background data restriction for these apps if one is set.
- Check whether a device-care or cleaner app is force-stopping Google apps, and exclude them if so.
- Restart the phone and try signing in again.
Battery optimisation is helpful for most apps, but the sign-in service is not most apps. It must run in the background, hold a network connection, and finish a multi-step exchange with the server. An aggressive battery saver that kills it halfway produces exactly the generic error this guide addresses. The unrestricted setting uses slightly more battery, but it removes the doubt, and it can be revisited once sign-in works. For mail that still misbehaves after sign-in is fixed, our guides to Gmail app not syncing new messages and Chrome keeps logging me out cover the app-specific side.
Fix 11: Reset the Network Settings
Resetting the network settings clears saved Wi-Fi networks, Bluetooth pairings, and mobile data settings back to defaults. It catches stale network settings that hide from the other fixes, including a saved Wi-Fi setup that quietly blocks the sign-in check.
- Open Settings, then System, then Reset options.
- Tap Reset Wi-Fi, mobile and Bluetooth, or Reset network settings on some phones.
- Read the warning and confirm — photos, apps, and files are not affected.
- Restart the phone after the reset completes.
- Reconnect to Wi-Fi with the password, and re-pair any Bluetooth devices.
- Check the date and time once more, as in Fix 2, before attempting sign-in.
- Try signing in again and confirm the account completes the handshake.
Have the Wi-Fi password ready before starting, because every saved network is removed. Bluetooth pairings go too, so earbuds and speakers need pairing again. If google account sign-in error on android survives a network reset, a fresh account record, and a passing browser test, the fault is likely on the account side or with the network provider. Contact the network provider about blocked services, or work through official account recovery once more with the full history of what was tried. Do not factory reset the phone for a sign-in error — the fixes in this guide cover every phone-side cause, and a reset wipes the device without touching an account-side lock.
What to Avoid
- Do not share your password or any verification code with anyone — no legitimate helper ever asks for them.
- Do not use apps or services that claim to unlock or bypass a Google account — they steal credentials or install malware.
- Do not keep retrying the same password dozens of times — repeated failures can trigger a temporary lock that delays the real fix.
- Do not clear storage for Google Play Services as a first step — start with the cache, as in Fix 6.
- Do not change the password from a link in a text message or email — open the browser yourself and use the official pages.
- Do not factory reset the phone for a sign-in error — it wipes the device and cannot fix an account-side lock.
- Do not turn off 2-Step Verification to make sign-in easier — it protects the account, and the fix is to repair the verification method, not remove it.
Frequently Asked Questions
Why does the correct password keep failing on the phone but work in the browser?
Because the phone and the browser use different paths to prove the sign-in. The phone relies on a local account record, the clock, and background services, and any of those can fail while the password itself is correct. A passing browser test proves the account is fine. Work through the clock, cache, and account-record fixes in this guide to repair the phone side.
Will removing the account delete my emails and photos?
No. Removing the account from the phone deletes only the local copies of synced data. The emails, contacts, calendar entries, and photos stored with the account online stay safe and sync back when the account is re-added. Files stored only on the phone are not part of the account record. Fix 8 explains the warning in full.
How do I know whether the problem is the account or the phone?
Sign in through the browser, as in Fix 4. If the browser signs in, the account is healthy and the phone is at fault. If the browser fails with the same details, the account needs attention first, through official recovery. The browser test is the fastest way to aim the rest of the fixes in the right direction.
What should I do if the verification prompt never arrives?
Check that prompts go to a device you still own and that is switched on, and check the verification methods in the account security settings from another device. Use an authenticator code or a backup code if one is available. If no method works, use official account recovery. Never accept a code from someone else, and never share your own code.
Can a VPN cause a sign-in error?
Yes. A VPN routes the sign-in check through a remote server, which can trigger a security challenge or route the request through a blocked location. Turn the VPN off and try signing in again. If it works, the VPN is the cause — try a different server, or sign in without the VPN and turn it back on afterwards.
Should I clear storage for Google Play Services?
Only as a last resort, and with the expectation that apps will sign out and need their details again. Clearing the cache, as in Fix 6, is the safe first step and fixes the stale-token problem in most cases. Clearing storage is a bigger hammer that resets the service state, and it should only follow the gentler fixes in this guide.
Conclusion
When google account sign-in error on android locks the phone out of every Google service, the account is usually fine and the phone handshake is at fault. Check the connection and the clock first, test the account in the browser, then repair the background service and the account record. Finish by opening Gmail and confirming new mail arrives — a fresh inbox is the only proof that counts. Set it, test it, and sign in with confidence, keeping passwords and codes private throughout.
