LG phone stuck on agreement screen — simple explanation with safe setup checks

Hey! If your LG phone is stuck on the agreement screen (Terms & Conditions / privacy policy / “I agree”), we can troubleshoot it safely without jumping straight to “reset everything.”

First, I want to understand which “stuck” you mean, because it changes the logic:
• The checkbox won’t tick / buttons don’t respond
• You can tap “Agree,” but it spins and returns to the same page (setup wizard loop)
• It advances, then bounces back after Wi-Fi or Google sign-in
• The screen scrolls but “Next” stays greyed out

Tell me any details you can (in any order):
1) LG model (Velvet, G8/G7, V series, Stylo, K series) and Android version if you know it
2) Is this a new phone, after an update, or after a factory reset?
3) Are you on Wi-Fi, mobile data, or no connection during setup?

Thanks — that “checking info then returns” is the key phrase. It often means the Android setup wizard can’t complete a background step, so it loops back to the agreement page rather than showing an error.

Usually the root cause is one of these buckets:
• Network bucket: Wi-Fi is connected but blocked (captive portal, DNS issue), or connection drops mid-step.
• Services bucket: Google Play services / setup components are stuck loading, especially right after a reset.
• Account bucket: sign-in verification or device protection flow is waiting for something (and the UI looks like it’s just looping).

Before we try anything, a couple quick “environment” checks (because they’re low-risk and often solve the mystery):
• What Wi-Fi are you using? Home Wi-Fi, school/work Wi-Fi, hotspot?
• Does that network require a login page? (Some networks look connected but require you to accept terms in a browser.)
• Are date/time clearly correct? Bad date/time can break secure sign-in during setup.

That’s useful: “can’t proceed without Wi-Fi” suggests the setup flow is trying to reach Google/LG services and failing somewhere. The goal is to find out whether it’s the connection quality or a setup component hang.

A safe way to troubleshoot this (without giving you a full “do X and it’s fixed” recipe) is to do small comparisons and see which factor changes the behavior.

Quick comparison #1: switch the network
If you can, try a different internet source briefly — like a phone hotspot. This doesn’t “repair” anything, but it tells us if your router/DNS is the trigger. Setup flows can be surprisingly picky about DNS filtering, ad-blocking, or family-safety settings on the network.

Quick comparison #2: observe where it fails
When it goes back to the agreement screen, does it ever show a message like “Can’t connect,” “Something went wrong,” or does it just silently loop? And does it loop instantly or after ~10–30 seconds?

Good question — and it’s not about your Wi-Fi being “bad.” It’s more about whether something on the network path blocks a specific step.

A setup wizard may need to reach multiple services (Google sign-in endpoints, Play services checks, device provisioning). If your router has DNS filtering, “safe browsing,” an ad-blocker, or even a strict firewall profile, the phone can look connected yet still fail a required call — and the setup UI sometimes responds with a loop instead of a clear error.

Since we’re staying safe and non-destructive, here’s what I’d do next:
• Hotspot test (just once): If it progresses on a hotspot, we’ve proven it’s network-path related, not a broken phone.
• Router quick sanity: if you use Pi-hole/ad-block DNS, parental controls, or a “guest network,” switching to a plain guest network can be a clean test.

Another angle (different order of questions): did you reset because it was slow, or because you were locked out? And was this device previously signed in to a Google account you still have access to?

That hotspot result is huge — it means the “agreement screen loop” is very likely related to the home network path or something the phone can’t reach through it, not a random hardware failure.

And “Checking for updates” hanging during setup is another common setup-wizard pain point, especially right after a factory reset when Play services and system components are syncing in the background.

We won’t do anything risky here. Instead, think in terms of safe decisions:
• If hotspot gets you through setup, you can finish setup that way, then later troubleshoot the home Wi-Fi issue (DNS/filtering/router settings) when you’re back in Android normally.
• If updates hang for a long time, it can be because the connection is slow or because the device is waiting for background services. The safest approach is to watch for progress vs a true freeze (does it warm up and work, or does it bounce back repeatedly?).

Quick questions (not all at once):
1) Are you using any custom DNS on your home network? (ad-block DNS, “family filter,” VPN router)
2) When it says “Checking for updates,” can you skip it or is it a hard block?
3) Is the phone battery above ~30% during setup? Low battery can make setup behave oddly.

That lines up perfectly with what we’re seeing. An ad-block DNS can block a domain the setup wizard expects, and the UI sometimes responds with looping or “checking info” without a useful error.

About the “skip updates” concern: skipping during initial setup usually doesn’t “break” the phone, but I also get why you hesitated. From a safety standpoint, what matters is: get into the home screen first, then let updates run from normal settings when the UI is stable and you can see progress and error messages.

Here’s a non-pushy diagnostic approach that keeps control in your hands:
• Evidence you already collected: hotspot works, home Wi-Fi loops → likely DNS/filtering problem.
• Safest next test: temporarily try the home Wi-Fi with “plain DNS” (if you have a guest network without filters) and see if the agreement screen stops looping.
• If you can only use hotspot: finish setup with it, then later adjust DNS on the router or on the phone.

One more risk check: are you seeing any message about device protection or “this device was reset” asking for the previous Google account? (That’s normal security, but it changes which steps are appropriate.)

Makes sense. The safe path (without pretending there’s a single “magic fix”) is: use the connection that actually lets the setup wizard complete, then clean up the network settings afterward when you’re fully in Android.

In other words, treat the agreement loop as a setup connectivity problem until proven otherwise. You already proved a different network changes the outcome — that’s the strongest diagnostic evidence you can get without doing anything destructive.

While finishing setup, keep an eye on these “real freeze vs slow progress” signals:
• Does any screen change after a few minutes (even once), or does it bounce back repeatedly?
• Does it get hot (light warmth is normal; unusual heat is a stop sign)?
• Does it consistently fail on the same step (agreements, updates, sign-in), or is it random?

If it consistently fails only on your home Wi-Fi and not on hotspot, that points to DNS/filtering or router-level restrictions — not something you “fixed” by resetting again.