Google Pixel stuck on agreement screen — safe step-by-step help

Hey! If your Google Pixel is stuck on the agreement screen during setup (Terms of Service / Privacy / “Additional legal terms”), we can usually narrow down whether it’s a loading problem, a tap/scroll requirement, or a network/time validation issue — without doing anything risky.

First, I want to understand what “stuck” looks like on your Pixel, because the safest next step depends on the exact behavior:
• The Accept button is missing or greyed out
• You can tap Accept, but nothing happens (or it spins and returns to the same page)
• The page won’t load (blank, endless “loading…”)
• You can’t scroll to the bottom so it never enables Accept

Quick questions — answer in any order:
1) Pixel model (Pixel 6/7/8/9 etc.) and whether this is after a factory reset or brand-new setup.
2) Do you see Wi-Fi connected (and does it actually have internet)?
3) What exactly happens when you try to accept — does the button respond at all?

Got it — “Accept button responds but doesn’t advance” is different from “Accept is greyed out.” On Pixels, the agreement screen often needs to contact Google services in the background. So you can be connected to Wi-Fi but still have a blocked connection (DNS/VPN/router issue) and it looks like the setup is frozen.

People search this a bunch under slightly different phrases, so I’ll keep the checks broad and practical:
• Pixel stuck on agreement screen
• Google Pixel can’t accept terms and conditions
• Pixel setup stuck on privacy policy

First diagnostic question (because it changes everything): does your Wi-Fi ever show “Connected, no internet” on other devices, or did you recently change router settings (new ISP box, Pi-hole, parental controls, custom DNS, VPN)?

That’s a strong hint the phone is trying to reach something but the connection isn’t consistently clean. During setup, even small hiccups can cause a “tap Accept → nothing happens” loop.

Let’s do the safest checks first — these don’t erase data and don’t change security settings in a sketchy way:

Step 1: Confirm real internet, not just Wi-Fi signal.
If you can, try a different connection for 2 minutes (mobile hotspot from another phone is perfect). This is purely diagnostic: if the agreement screen instantly advances on a hotspot, the Pixel probably isn’t the problem — the network is.

Step 2: Confirm date/time isn’t off.
A wrong date/time can break secure connections (and setup screens depend on those). You don’t need to “fix” anything yet — just check if it looks normal for your location.

Step 3: Watch for a hidden “scroll to enable” rule.
Some agreement pages don’t activate properly until you scroll through the content. If you’re stuck at the same page, try scrolling all the way down once and see if the button behavior changes.

Quick check: is the date/time shown on the setup screen correct (even roughly), and do you have access to a hotspot to test?

Spinner then “returns to same screen” usually means one of two things:
• It can’t complete the background request (network/DNS/service reachability), or
• Something is blocking taps/UI flow (rare, but overlays/accessibility can interfere).

Since you’re still in setup after a reset, we won’t mess with advanced app settings. Instead, I’d run a quick “yes/no” filter with minimal actions:

1) Hotspot test: Connect to a hotspot and try Accept once. If it progresses, you’ve basically proven the router/network is the trigger.
2) Airplane Mode toggle: If hotspot isn’t available, briefly toggling Airplane Mode (then back) can reset the network stack. It’s reversible and doesn’t wipe anything.
3) SIM/eSIM presence: Are you setting up with a SIM inserted? Sometimes the phone tries to validate via mobile network and Wi-Fi at the same time. Not always an issue — but good to know.

Also, if you’ve seen other “setup flow” weirdness before, there’s a related guide some people find helpful for understanding confusing screens: Android phone consent screen confusing – simple fix (it’s more about reading what the screen is asking, not bypassing anything).

Do you have a SIM in it right now, and can you try hotspot just once to see if the behavior changes?

That’s one of the clearest diagnostic results you can get — nice job testing it. If the agreement screen works on a hotspot, the Pixel hardware and the setup wizard UI are probably fine. The issue is most likely that your home network intermittently blocks or breaks whatever the setup needs (DNS filtering, router security feature, captive portal behavior, or unstable internet handshake).

So the “safe next step” is not a reset. It’s narrowing what about the network makes setup hang. A few common patterns (you can answer without changing anything yet):
• Is your home Wi-Fi using a content filter / “safe browsing” / family controls?
• Any custom DNS (AdGuard DNS, NextDNS, Pi-hole, “private DNS” on the router)?
• Does the router show a login page (captive portal) sometimes, like hotel Wi-Fi style?

Even if you don’t know, you can still do the setup on a hotspot, then later fix Wi-Fi normally after you’re on the home screen. If you run into “stuck downloads” later, the same root cause can show up as slow Play Store installs. (Related reading if you hit a different “black screen” symptom later: Android phone camera shows black screen – easy help for seniors.)

Quick question: is this your own router at home, or a managed network (school/work/apartment) where you can’t change settings?

Yes — using a hotspot to get through setup is a common low-risk workaround when the agreement screen hangs on a specific Wi-Fi network. It doesn’t “damage” the phone or lock anything in. The main caution is just data usage (setup can download updates).

And you don’t have to touch router settings today. You can treat the router as the suspect and come back to it later if you notice other signs (apps stuck “pending,” Play Store not loading, or “connected but no internet”).

To keep this focused and safe, here are the checks that matter most after you get past the agreement screen:
• Can the phone sign in and sync (Google account adds successfully, backup restore can start).
• Do updates download normally on your home Wi-Fi vs hotspot (that comparison tells you if the router is still blocking).
• Is date/time set automatically (wrong time can cause weird “can’t sign in” behavior).

If you later want a simple “compare networks” approach for Android connectivity, this can be a helpful reference conceptually: Android phone charging very slowly – what to do next (different topic, but it shows the same idea of isolating the real cause instead of guessing).

One more detail: when you were on your home Wi-Fi, did you ever see a small pop-up asking to “sign in to network” (like a portal), or was it silent?

That’s a sensible plan. And you’re not “guessing” — you already ran the best test: same phone, different network, different result.

If you want to keep notes (helps if you ever talk to ISP support), the story is:
• Pixel setup stuck on agreement/terms screen on home Wi-Fi
• Works immediately on hotspot
That points to network filtering, DNS behavior, or security features on the router/ISP side.

One last safety check while you’re still in setup: if the phone offers an update during setup, make sure it has a stable connection and decent battery. Updates during setup can take longer than expected, and people sometimes think “it’s stuck again” when it’s actually downloading in the background.

If you later see another “setup flow” notification that says something like “finish setting up your Pixel,” that’s normal — it’s not the same as being stuck. And if you ever hit a different setup message, like “setup cannot be restarted,” this related guide covers the logic (different problem, same setup family): Android phone consent screen confusing – simple fix.

Want to tell me whether the phone is restoring apps/settings now, or are you doing a clean setup?

Perfect. The agreement screen is one of those places where “looks like a phone bug” is often actually “the network won’t complete a background check.” You did the safest thing: isolate the variable and confirm it’s network-specific.

If anything else pops up during setup (sign-in loops, downloads stuck pending, or a screen that won’t load), the most useful detail to share is always: does it happen on both Wi-Fi and hotspot? That single comparison prevents a ton of trial-and-error.