Hey! If your mobile phone is stuck on the agreement screen (Terms & Conditions / Privacy Policy / “I Agree”), we can do a safe diagnosis without jumping to risky resets.

This problem usually falls into a few categories, and the “right” next step depends on which one you’re in:

• Network validation issue: the terms page needs internet to load/confirm acceptance, but Wi-Fi is connected with no real access (captive portal, filtering, DNS/security app, weak signal). People describe this as “the Accept button does nothing” or it spins forever.
• Time / certificates mismatch: incorrect date/time can break secure connections, so the agreement page won’t verify even though the screen looks normal.
• Touch / display scaling / accessibility conflict: the button is there but taps don’t register, or the “Agree” checkbox is off-screen due to display size, zoom, or an accessibility feature during setup.
• Setup wizard bug: after an update or after a reset, the setup app (Setup Wizard / One UI setup / iOS Setup Assistant) can loop back to the same agreement page.
• Account / device policy blocks: on some work or school phones, MDM/management steps can look like a normal agreement screen but it’s actually waiting for enrollment or account verification.

Quick questions so we don’t guess:
1) Is this Android or iPhone? (And brand/model if Android: Samsung, Pixel, Motorola, Xiaomi…)
2) Are you in first-time setup after turning it on/resetting, or is it popping up inside Settings (like iCloud terms)?
3) What exactly happens when you tap Agree / Accept / Next: nothing at all, a spinner, or it jumps back to the same screen?
4) Are you on Wi-Fi or mobile data, and does the network require a sign-in page (hotel/school/public Wi-Fi)?

Got it — Samsung setup wizard stuck on terms and conditions after a reset is frustrating, but “Next does nothing” often means the phone isn’t successfully completing a background check (internet validation, date/time, or the setup app is hung).

Before we do anything big, I want to separate two look-alike situations:

A) The phone is ignoring taps (touch/zoom/accessibility issue): you tap Next and there’s zero visual response, like the button isn’t clickable.
B) The phone responds but doesn’t complete (network/setup bug): you tap Next and maybe you see a tiny flash/spinner, but it returns to the same screen or just sits there.

When you tap Next, do you see any small change at all (button highlight, spinner, brief “loading”)? Also: can you scroll the terms smoothly, and do other buttons on that page respond normally?

Perfect — that points away from a broken touchscreen and toward a verification problem during setup.

Here are the safest “no-regret” checks (they don’t erase anything and don’t require hidden tools). I’ll explain what each check tells us, because the goal is a clear diagnosis, not random button-mashing.

Safe check #1: “Is the phone truly online?”
During setup, some phones show Wi-Fi as connected even if the connection is limited (router filtering, DNS issues, weak signal). If you can, tell me: is the Wi-Fi signal strong, and are you close to the router? If the page has a “back” option, does it show the Wi-Fi network name as connected?

Safe check #2: “Does a different internet path behave differently?”
The quickest way to confirm a network validation issue is a simple comparison: the same screen on a different network (like a phone hotspot). If it behaves differently, that’s a strong clue it’s not the Galaxy itself but the internet path (router settings, DNS, filtering).

Safe check #3: Date & time sanity
If the device time is wildly wrong after a reset, secure connections can fail and the privacy policy / EULA acceptance won’t finalize. Some setup flows let you view the time in a corner or in a date/time step earlier in setup. Do you remember seeing an incorrect date/time earlier?

That detail matters: during initial setup you can have multiple agreements layered together (Samsung terms, Google services terms, privacy policy, diagnostics/analytics). Sometimes the setup wizard won’t proceed unless a specific required checkbox is accepted — and the confusing part is that the required one might be off-screen or collapsed under “More.”

I’m going to keep this safe and non-invasive: I won’t tell you “toggle everything” because that’s not good troubleshooting. Instead, we’re looking for a clue like:

• Is there any checkbox that looks required (often marked “Required” or doesn’t have an optional label)?
• Is there a small link like “View details”, “More,” or a scroll area where an additional consent appears at the very bottom?
• Does the Next button stay greyed out sometimes, or is it active but still doesn’t move on?

Also, one more important question (because you mentioned a factory reset): was this Galaxy previously signed into your Google account, and did you remove that account before resetting? I’m not asking for credentials — just whether the phone used to belong to you. This helps rule out certain account protection screens that can look like “agreement” steps.

Thanks — “active button, required checked, no error” usually points to either:

1) Setup wizard is waiting for a background response (internet/cert/time), but it’s failing silently, or
2) The setup app is stuck (a temporary hang in the onboarding flow).

Here’s a simple explanation of what’s happening under the hood (so this doesn’t feel mysterious): when you tap Agree, the phone may need to fetch the latest terms text, confirm region/device identifiers, and sometimes verify Google Play services components. If any part can’t reach the server securely, the UI can just sit there.

Two safe observation questions (no changes required):
• Is there a tiny text at the bottom like “Checking…”, “Loading,” or a spinning indicator after you tap Next?
• If you leave it for a minute on that screen, does it ever jump forward on its own, or is it completely frozen in the same state?

And a practical comparison test that’s still safe: do you have another phone you can use as a hotspot just for one minute? If the agreement screen proceeds on hotspot but not on home Wi-Fi, we’ve basically confirmed the root category without doing anything destructive.

It’s a common pattern — and the symptoms you described don’t sound like a “bricked” device (a bricked phone usually won’t boot, won’t charge normally, or crashes/restarts constantly). A phone that reliably reaches setup and responds to taps is generally alive; it’s the setup flow that’s blocked.

Think of it like a web page inside the setup wizard: if that page can’t complete a step (network validation, agreement submission, component check), it can feel like you’re stuck on the agreement screen loop even though nothing is physically wrong.

Also, since you mentioned this is for your mom: if the device is going to be used by someone else, we want to be careful not to create account lockouts by trying random “shortcuts.” So the safest plan is: identify whether the blocker is internet path, time/region, or setup wizard hang — in that order.

One more detail that helps: is this Galaxy connected to SIM right now (even an inactive SIM), or is it Wi-Fi only? Sometimes setup behaves differently with no SIM present (especially if it’s trying to determine region/carrier settings).

Similar “shape,” different details. On iPhone you’ll see things like iCloud Terms and Conditions or the iOS Setup Assistant terms page, and the blocker is often still one of the same categories: network validation, Apple ID/iCloud verification, or a software mismatch. The feeling is the same: “I tap Agree and it won’t complete.”

On Android/Samsung, “no SIM” can be totally fine, but it’s useful because it changes what the setup wizard tries to auto-detect. That’s why I like the hotspot comparison test — it isolates the most common silent blocker quickly.

If you want a simple explanation you can remember, here’s the rule-of-thumb:

If the button responds but nothing advances, it’s usually a background check not completing (internet/time/software component).
If the button doesn’t respond, it’s more often touch/scaling/accessibility or the UI layer itself.

When you’re ready, tell me one thing you can confirm (any one is enough to choose the next safe step):
• Does the same screen behave differently on a hotspot?
• Does adding a SIM (even temporarily) change anything about the setup flow?
• Does the setup wizard show a software update prompt anywhere earlier (even if you skipped it)?

Smart question. When a phone is stuck on the terms / agreement screen, the biggest mistakes are the ones that add new variables or increase the chance of an account lockout.

Safe “avoid” list (simple, practical):
• Don’t install random “setup bypass” or “FRP bypass” tools. They create security risks and can complicate legitimate recovery.
• Don’t repeat factory resets back-to-back out of frustration. If an account or policy is involved, repeated resets can make the situation harder (and wastes time).
• Don’t change a bunch of hidden options at once. One change at a time is how you learn what the blocker is.

What’s safe to do:
• Try one alternate network path (hotspot) and observe what changes.
• If there’s a step to confirm date/time/region during setup, just verify it looks sane.
• If you notice display size/zoom, keep it default during setup so buttons/checkboxes don’t get pushed off-screen.

If you report back whether hotspot changes the behavior, we can pinpoint the category and choose the next safest move without guessing.

Exactly — if it proceeds on hotspot, the phone is basically telling us: “I can complete the agreement step when my internet path is clean.” That often points to router-level filtering, DNS/security settings, or a Wi-Fi connection that’s “connected but restricted.”

If it behaves the same on hotspot and Wi-Fi, then we pivot to other likely buckets (time/region mismatch, setup wizard hang, or a device/account policy step). Either way, you’ll have a clear direction — not a doorway-style list of random fixes.

When you run the test, note one tiny detail: does it get stuck on Samsung terms, Google services terms, or a generic “agreement” page? That helps narrow which component is failing.