Google Pixel Setup Stuck on Welcome Screen? How to Fix It

Hey! If your Google Pixel setup is stuck on the Welcome screen (or it keeps looping between “Welcome,” “Just a sec…,” “Checking for updates,” or a never-ending loading circle), we can narrow down what’s blocking it without jumping straight to a reset.

Pixel setup failures usually fall into a few buckets that look identical on-screen:
• Network problems (Wi-Fi sign-in/captive portal, weak DNS, router filtering, “connected but no internet”).
• Google account verification (sign-in hangs, 2-step prompts not loading, time/date mismatch).
• Carrier/SIM activation (SIM/eSIM trying to activate mid-setup, or “no service” delays).
• Setup wizard glitch (transfer step stalls, update check stalls, setup app freezes).

Tell me whatever you remember (order doesn’t matter):
1) Which Pixel model and is it brand new or after a factory reset?
2) Where exactly does it hang — on “Welcome,” after you tap Start, during Wi-Fi, during Google sign-in, or while “Checking for updates”?
3) Are you using a SIM/eSIM already, and are you trying to copy data from an old phone?

Thanks — “connects to Wi-Fi, then stuck on Checking for updates” is a common setup-loop pattern. The good news is: it’s often an environment issue (network/portal/router) or a setup-transfer step getting jammed, not anything “broken” with the phone.

I’ll keep this in safe checks only — no wipe instructions, no “guaranteed fix,” just a way to isolate the cause.

First, two quick clarifiers (different angle than usual):
• Are you on home Wi-Fi, school/work Wi-Fi, or a hotspot? Networks with sign-in pages can silently block setup even when the phone says “Connected.”
• Do you see a clock/time on any screen? If the date/time is wrong (rare on new phones, but possible), Google sign-in and update checks can hang.

And one more: did you insert a SIM already, or are you setting it up without a SIM?

Great detail: SIM inserted + update check hanging can sometimes mean the setup wizard is bouncing between carrier activation and Google services while the network path isn’t “clean” enough (even if other devices feel fine).

Here’s a safe way to decide whether waiting helps or whether you’re stuck in a loop:
• If it hasn’t progressed at all in ~10–15 minutes (no next screen, no new prompt), it’s usually stuck, not “slow.”
• A simple restart is a normal diagnostic step if the setup screen is frozen. It doesn’t commit you to anything drastic.

Before we restart though, I want to isolate the top two culprits with minimal changes:
1) Try a different internet path — even briefly. A phone hotspot (from another device) is ideal for testing because it bypasses router DNS/filtering quirks.
2) Temporarily remove the SIM just for the test-run. This tells us if the setup wizard is getting delayed by activation checks. (You can put it back later.)

Quick question: do you see any message like “can’t connect,” “something went wrong,” or is it purely a spinner with no error?

Yep — removing the SIM here is not “a fix,” it’s just a clean test: if the Pixel gets past the Welcome/setup loop without the SIM, we’ve learned the stall is likely activation-related rather than the phone being defective.

Another thing that can make setup look frozen: the data transfer step. Sometimes “copy apps/settings” or “restoring backup” causes the setup wizard to hang and it looks like it’s stuck on Welcome or updates because it keeps retrying in the background.

So when you re-try setup (especially on hotspot), note whether it behaves differently if you choose “set up as new” versus transferring. You don’t have to commit to that choice right now — it’s just a way to isolate what’s triggering the loop.

Also, if the phone becomes unresponsive during setup (touches don’t register, screens don’t change), that’s closer to a “device froze” scenario than a setup logic issue. In that case, a basic restart is normal. (Unrelated example: if you ever run into a general freeze after setup, this is the generic Pixel guidance path.)

Side note while we’re here: if you later hit a confusing “permissions/consent” page during setup or first-run apps, that’s a different issue track — this guide is related: Android phone consent screen confusing – simple fix.

That’s a big clue — you changed two variables that matter (network path + SIM), and behavior changed. So we’re not dealing with a random “dead phone,” we’re dealing with a setup blocker that shifts depending on conditions.

On the Google account part: yes, recent account changes can affect setup, especially if there’s a verification step that isn’t loading properly yet (2-step prompt, security confirmation, or a “Verify it’s you” step that’s waiting in the background). I’m not going to ask you to bypass anything — just to identify whether sign-in is the bottleneck.

A few diagnostic questions (answer any that apply):
• Are you using 2-Step Verification? (prompt on old phone, authenticator, SMS, etc.)
• Do you have access to that old phone right now to approve a prompt if it appears?
• After entering the password, does it ever show a “Verify it’s you” screen or is it only a spinner?

Another angle: when setup stalls right after account sign-in, sometimes it’s actually stalling on a background download/update step. On brand new devices, the setup wizard can be sensitive to weak connectivity, so hotspot helps — but we still want to watch for a prompt that never appears.

If you later notice the phone charging very slowly while you’re doing setup (which can cause throttling), that’s another separate path: Android phone charging very slowly – what to do next.

Perfect — that tells me what to watch for. If you have 2-step and you’re not seeing a prompt, setup can appear “stuck” even though it’s waiting for verification in the background.

Since we’re keeping it safe and not doing drastic actions, here are the next checks I’d do in a real support situation, in this exact order (because you already proved hotspot helps):
• Power + stability: plug the Pixel into a charger while trying again. Low-ish battery plus setup downloads can cause slowdowns. Warm is normal during first-time setup and app updates, but keeping it charging helps stability.
• Prompt visibility: keep the old phone unlocked and on Wi-Fi/cellular so a “Google prompt” can actually pop up. Also check if a code method is offered (without changing security settings).
• “Stuck vs slow” test: if it spins for more than ~10–15 minutes with zero change, treat it as stuck and do a simple restart (still non-destructive).
• SIM re-introduction later: since removing SIM changed behavior, don’t add the SIM back until you’re past Google sign-in. Then add it and let activation happen after setup is complete.

None of this is a “magic fix.” It’s just clean isolation so you know whether you’re fighting Wi-Fi/router, carrier activation, or account verification.

If later, after setup, you run into performance weirdness like an SD card slowing a phone down (on devices that support external storage), that’s unrelated but common: Android phone SD card slow – how to fix safely.

Totally reasonable questions.

About restarting: if the setup wizard is frozen/spinning with no progress, a restart is a standard diagnostic move. It doesn’t “brick” the device by itself. The only thing it changes is you may have to re-enter a couple of steps (Wi-Fi, account). That’s why we use it as a test: does the behavior repeat at the exact same point, or does it move forward when conditions are cleaner (hotspot, no SIM, charger connected)?

About transferring data: transfer is great when it works, but for diagnosing a setup loop, it’s one more moving part. If the goal is “get through setup reliably,” the clean diagnostic approach is to get past Welcome + Google sign-in first on the simplest path, then handle transfers/restore once the phone is stable. You’re not “giving up,” you’re just isolating variables.

If you want one practical way to keep this from feeling endless: write down the exact screen where it stalls (Welcome, Wi-Fi, Checking for updates, Google sign-in, “Just a sec…”). That single detail is what separates a network issue from an account verification issue from a setup app freeze.

And if, while doing all this, the Pixel starts acting like it’s fully frozen (buttons unresponsive, screen doesn’t change), that’s the “device froze” category rather than “setup logic,” and the general restart guidance applies. Also keep it charged to reduce slowdowns during first-run updates.

If you tell me: (1) hotspot vs home Wi-Fi behavior, (2) SIM in vs SIM out behavior, and (3) whether any 2-step prompt appears — we can usually identify the blocker without jumping to last-resort steps.