LG phone setup lost after restart — simple explanation with safe diagnostic checks

Hey! If your LG phone looks like it “lost setup after a restart” (showing the welcome/setup wizard again, asking for Google sign-in, or acting like a new phone), we can sort out what happened with safe checks first.

Quick reassurance + why this matters: sometimes it’s a real reset, but other times it’s a launcher/home screen crash, a different user profile (Guest / Secondary user), or the phone booting into a “fresh” state because something couldn’t load correctly.

Before you tap through anything, answer any of these (in any order):
1) What exactly do you see? “Let’s go / Welcome,” language selection, Wi-Fi setup, Google login, or something like “Finish setting up your device”?
2) Are your apps still there? Do you recognize your wallpaper, icons, photos, or notifications?
3) What LG model (G/V/Velvet/Stylo/K series) and did this happen after an update or after a low battery shutdown?

I get why that’s alarming. The “Let’s go” setup wizard can appear in a few scenarios — only one of them is a full reset.

Let’s do a quick “is it truly wiped?” check without committing to anything:
• Pull down the notification shade (swipe from the top). Do you see any old notifications (messages, app alerts) or is it totally blank like a brand-new device?
• Tap the power button once to lock, then unlock — does it ask for your usual PIN/pattern, or does it behave like there’s no lock set?
• Check the status bar: do you see your carrier name/SIM signal as usual?

Also: do you remember what happened right before the restart — low battery, overheating, phone got stuck and you forced a restart, or an Android update prompt?

Battery-to-0 events can cause weird boot states, especially if the phone shut down mid-process (updates, file writes, encryption checks). It still doesn’t automatically mean “factory reset,” but we should treat this as a careful triage moment.

Here are the main “buckets” we’re testing for — simple explanation, no scary steps:
• Setup wizard overlay: Android thinks setup didn’t finish, but your user data may still exist behind it.
• Wrong user/profile: The phone can boot into a Guest/secondary profile that looks empty.
• User data didn’t mount: Storage/encryption issue where the system boots but can’t load your profile (often after abrupt power loss).
• Actual reset: Less common without you confirming prompts, but we’ll look for evidence either way.

Quick question that often separates these: do you ever remember enabling Guest mode or multiple users? Some people swipe down quick settings and tap a user icon by accident.

And when you see the setup wizard, is there an option like “Skip,” “Not now,” or “Use existing account,” or is it forcing Wi-Fi and Google sign-in immediately?

That caution is smart. I’m not going to tell you “just sign in and it’ll be fine.” The safe approach is to gather a couple more clues first so you know what state the phone is in.

Two non-destructive checks that help a lot on LG/Android:
1) Storage behavior clue: If you can get to any screen showing “About phone” or “Emergency information,” sometimes you can see whether the device reports normal internal storage size. If it looks wildly wrong (like tiny storage or errors), that points toward a “data not loading” situation, not a normal setup flow.
2) Google account clue: If the phone was previously protected (screen lock + Google account), after a genuine reset it often requires the previous Google account to proceed. If you see prompts about verifying the account that was previously on the device, that’s a different signal than a basic “sign in to continue.”

Also, since this happened after a near-dead battery, it’s worth checking whether the phone has been acting unstable lately — random restarts or weird charging. If yes, keep this for later: Android phone battery not charging – easy help for seniors.

One more question: do you still see your phone name in Bluetooth lists on another device, or any previously paired devices? Sometimes those persist even when the user profile doesn’t load.

Seeing “Verify your account” with part of the previously used Gmail is important context. It can happen after a true reset, but it can also appear when the phone thinks setup must be completed and it’s trying to validate the protected profile state.

Rather than assuming, here’s the practical evidence checklist I use (safe, no “fix promises”):
• Does it ask for the same Google account that was on the phone? That suggests the phone remembers prior ownership (good for security, confusing for users).
• Are there any signs of your old data at all? For example, your carrier name is there, but are your photos visible anywhere, or is the gallery empty if you can reach it?
• Did you have an SD card? If photos were stored externally, they might still exist even if the phone is in a setup state.

One safe move (not a full solution) is to slow down and avoid repeated restarts while it’s in this state. If you’ve been restarting a lot, it can make troubleshooting harder because you lose “what changed” clues.

If your concern is “will signing in overwrite anything,” the main risk is moving forward without confirming what data exists locally vs in backup. If you ever set up Google backup, it may restore some things later — but we should treat it like a diagnostic question, not a guarantee. Related (for later): Android phone consent screen confusing – simple fix.

That’s totally understandable — most people would try the same thing. At this point, the safest “what next” is to clarify whether you’re facing a setup wizard loop versus a completed reset — and to protect anything that might still be on the device.

Here are safe checks that don’t require you to “fix” it on the spot:
• Look for wording differences: “Set up as new” / “Copy apps & data” / “Restore” options suggest the device is behaving like a fresh setup. “Verify your account” suggests the phone is tying setup to the previous owner account.
• Check if the phone shows the same device name (often visible on Wi-Fi Direct/Bluetooth screens) — if it kept its custom name, it can imply the device wasn’t fully wiped, but it’s not definitive.
• Watch for storage errors: any warnings about storage, encryption, or “can’t access data” are big clues.

If you previously had performance issues (phone lagging, storage almost full), that can sometimes lead to strange states after a hard shutdown. If that sounds familiar, this might help later: Android phone SD card slow – how to fix safely (even without an SD card, the “storage pressure” concept is similar).

One question: did you ever see messages like “System UI isn’t responding,” freezing, or apps crashing in the days before this?

Given the slowdown + near-full storage + “System UI not responding” before the battery crash, it’s reasonable to suspect a software/storage stability problem that turned into a setup/verification loop after the shutdown.

The safest approach (no “guaranteed fix,” just good logic) is:
1) Don’t rush through setup screens blindly. Read each screen for “restore,” “copy data,” or “verify previous account” wording and take a photo if you can — it helps you avoid wrong turns.
2) Use the account you recognize. If it’s asking to verify the account that was previously on the phone, that’s a security step; it also tells us the device still has a memory of prior ownership.
3) Once you regain access, prioritize evidence. Check whether your apps, photos, and downloads are present before changing big settings. If you get back in and it’s unstable, you can also do a short Safe Mode test (diagnostic only) to see if third-party apps contributed to the instability.

If you end up back in Android normally but feel like your home screen “reset” (icons/wallpaper changed) rather than your data being wiped, that’s often a launcher/profile symptom — not the same thing as data loss. If you see black screens or freezing during this process, this related guide can help you describe symptoms clearly: Android phone camera shows black screen – easy help for seniors.

Bottom line: we’re aiming to identify whether this is a real reset, a profile that didn’t load, or a setup wizard loop — and the “verify account” prompt + pre-crash instability are the strongest clues you’ve shared so far.