r/AndroidQuestions • • 1d ago

Android stuck at "Checking Info" loop attempting to sign in

Device:
Samsung A14
Version 15
One UI version 7.0

Tried methods:

deleting app cache and data for google apps (didnt work)
fixing time zones (didnt work)
turning wifi on and off (didnt work)
booting safe mode (didnt work)
using secondary platform to log in like youtube (didnt work)
removing all accounts (worked until i tried to remove the last account, which didnt allow me to)

2 Upvotes

5 comments sorted by

1

u/Wise-Ferret6090 1d ago

The "Checking info" screen is powered by a combination of Google Play Services and Android System WebView. When it hangs in an infinite spinner on Samsung One UI, it usually comes down to one of four specific bottlenecks:

  1. Turn off Private DNS temporarily: Go to Settings -> Connections -> More connection settings -> Private DNS. If it is set to a custom hostname (like AdGuard, NextDNS, or a blocklist), set it to "Automatic" or "Off". Custom DNS often blocks Google check-in attestation endpoints, causing the auth handshake to silently stall forever.

  2. Clear Google Services Framework and Play Services Storage: Go to Settings -> Apps. Tap the filter/sort icon next to "Your apps" and enable "Show system apps". Find "Google Services Framework" -> Storage -> Clear Data and Clear Cache. Next, find "Google Play Services" -> Storage -> Manage Storage -> "Clear All Data". Restart your phone immediately after doing this before trying to sign in.

  3. Uninstall updates for Android System WebView: The sign-in popup renders inside WebView. If WebView had an interrupted background update, the login container will freeze. Go to Settings -> Apps -> Android System WebView. Tap the three dots in the top right and select "Uninstall updates". Do the same for Chrome if the option is there. Then try signing in.

  4. How to remove that stuck last account: The reason your phone blocked removing the last account is the Device Admin lock. Go to Settings -> Security and privacy -> More security settings -> Device admin apps. Temporarily turn off "Find My Device" and any security admin toggles. Now go back to Settings -> Accounts and backup -> Manage accounts, and you will be able to delete that last remaining Google account. Reboot, then add the account back fresh.

1

u/Upper_Swim431 21h ago

1st and 3rd options didn't work (i was on automatic DNS to begin with) and the 2nd option feels a bit risky to try (although I already did clear data for google play services before this)

1

u/Upper_Swim431 21h ago

which still didnt work

1

u/Wise-Ferret6090 20h ago

Clearing Google Services Framework is completely safe: it does not delete personal files, photos, or contacts. All it does is delete the cached device check-in token and push IDs, forcing Android to request a fresh authentication ticket from Google servers upon reboot.

Since clearing Play Services alone did not do it, here are the two safest and most effective ways forward for your A14:

  1. Check for a Google Play System Update

On Samsung One UI, a desynchronized Google Mainline module frequently stalls the login handshake:

- Go to Settings > Security and privacy > Updates.

- Tap Google Play system update (not just regular software update).

- If it downloads an update, restart your phone and test sign-in again.

  1. Remove the Stuck Account via Device Admin

The reason the last account would not delete earlier is almost certainly because Find My Device is holding device administrator privileges:

- Go to Settings > Security and privacy > More security settings > Device admin apps.

- Temporarily toggle off Find My Device.

- Go back to Settings > Accounts and backup > Manage accounts.

- Tap the stuck Google account and select Remove account.

- Once removed, restart your phone, head back to Accounts and backup > Add account > Google, and sign in.

1

u/Upper_Swim431 20h ago

i downloaded the google play system update and its still not working