Android Setup Keeps Stopping? Fix It Fast

You unboxed the phone, plugged in the charger, and expected a few welcome screens. Instead the setup screen threw up a red box saying Android Setup keeps stopping. The wizard closes itself, the phone restarts, and the same box comes back. You are stuck on the same screen with a new phone you have not even finished setting up.

The same thing happens after a factory reset. You wipe the phone to fix something else, the welcome screens start, and then Android Setup falls over. This is not the crash you get when a running app dies mid task. The setup app itself is failing, and it sits in the way of every step that comes after it.

What you see	What it means	Go to
The error appears on a brand new phone, still in the box	The setup app shipped broken on this handset	Disable the app, then check your warranty
The error appears after a factory reset	Setup data was left in a bad state by the reset	Disable the app, then clear its cache later
The error appears after a system update	An interrupted update left a broken file behind	Restart twice, then update the phone
The error returns every time you retry	The fault is in the build, not in one bad attempt	Recovery menu, then the maker

If none of these four rows describe your case, the fault may not be setup at all. A reader who thinks the red box is an app crash needs our guide to apps that keep stopping instead.

Why the setup screen falls over

Three causes sit behind this error, and only two of them live on the phone.

• Corrupt or failed setup data. The setup app keeps its state on the phone. A reset, an update or a power cut can leave that state half written, so the app cannot read it back. This is the cause you can test yourself, because clearing the app's storage rebuilds it from scratch.
• A broken file left by an interrupted update or restore. The phone was cut off, or the restore failed halfway, and a file the setup app needs is now wrong. A restart clears what is only held in memory, but a broken file on storage survives it.
• A fault in the maker's own build. The setup app that shipped on the handset has a bug in it. Nothing you do on the phone fixes that. Only a new build from the maker does.

You can tell the first cause from the others by one move. If clearing the setup app's storage fixes it, the fault was in its data. If the error survives a cache wipe, a second restart and a new update, the fault is in the build.

Fix one: turn the setup app off from the error screen

This is the fastest way past the error. WikiHow's page on this error calls it the quickest, most common fix. I read that page on 1 November 2026. The taps are short because the error box carries a shortcut for you.

1. Tap App info on the error screen.
2. Tap Force stop, then confirm by tapping Force stop again.
3. Tap Disable, then confirm by tapping Disable again.
4. Carry on with setup. The wizard moves past the box.

Galaxy owners had already found this route in 2019, before the guide this site leans on. A reader on Reddit's Galaxy S10 thread, 13 March 2019, wrote that they disabled Android Setup and got past it. Another poster in the same thread said the App info route was the only way through for them.

One caveat comes with the fix, so read it before you tap Disable. One poster in the same thread reported that a backup would not restore once the app was switched off. Disabling only stops that one app from running, and Google says a disabled app can be added back to your phone later.

Fix two: restart the phone, and then restart it again

The restart is the cheapest thing on this page, so it comes before the cache and the recovery menu. Hold the side button, then choose Restart. Do not choose Power off, because a phone that powers off and comes back can carry a fault that a restart would have cleared.

If the error is still there after the first restart, do a second one. WikiHow makes the point that a second restart is often the one that works, after the first restart has already been done.

If the screen is frozen and will not respond to the side button, force restart it from the buttons. On a Galaxy, hold Volume Down and the Side or Power button together until the device turns off and turns back on. The screen goes black and the logo comes back. A force restart does not erase anything on the phone, and our guide to a phone stuck on the boot screen walks the same hold. I read Samsung's force restart page on 1 November 2026.

Fix three: clear the cache and the storage of the setup app

This one runs after setup is finished, because the Settings app has to be open before you can reach it. The path is the one WikiHow gives for the storage screen, and the same path works on every phone I have walked it on.

1. Open Settings, then tap Apps or Apps and notifications.
2. Tap the three-dot menu at the top of the list, then tap Show system apps. Android Setup is a system app, so it stays hidden until you switch this on.
3. Tap Android Setup to open its app info screen.
4. Tap Storage and cache.
5. Tap Clear cache, then tap Clear storage and confirm.

Read that last step for what it is. Clear storage removes the setup app's saved state, which means it forgets the setup choices it had stored. Do this only after setup is finished, because you will be wiping what the wizard already did.

Fix four: update the phone once setup is done

Once the phone is running, check for a system update and install it. WikiHow puts this last in its order and gives the path as Settings > System > System update. A maker's own build can carry the fix for the fault that stopped you. This step is worth taking even when setup went through cleanly.

If setup never finished, check for the update through your maker's own app instead. Some makers ship their updater outside Settings, and the name of the app differs from one brand to the next.

Fix five: recovery mode and a cache wipe

This is the fix for the phone that never reaches setup at all. It needs the recovery menu, and the buttons that open it differ from one brand to the next. Search your model name plus recovery mode, then follow your maker's own steps. A button combo copied from a forum can open the wrong menu on your phone.

Samsung's UK support page shows how much the hold varies. A phone with a physical Home button, such as the S6 or S7, takes Volume Up, Home and Power together. A phone with no Home button but a separate Power button, such as the S8 or S9, takes Volume Up, Bixby and Power. A phone with neither, such as the Note 10, Fold or Z Flip, takes Volume Up and Side. Let go when the phone vibrates and the logo appears.

Google's Pixel help page gives the same kind of split. A Pixel 6 or later takes Volume Down and Power together for up to 30 seconds. Earlier Pixels take Volume Up and Power. You can then choose Recovery Mode from the menu with the volume keys and confirm with Power. I read Google's Pixel recovery guidance on 1 November 2026.

Inside recovery, choose the option that wipes the cache only. Samsung's page names it Wipe cache partition and the menu asks you to confirm with Yes, then Reboot device. Read the difference carefully before you pick, because the menu sits next to a far heavier option. A cache wipe clears temporary system files and leaves your photos, your chats and your installed apps alone. A factory reset erases everything on the phone.

One warning before you touch that menu. Google's reset page says a factory reset erases all your data. It asks you to know your Google Account username and password first, plus your screen lock. It also asks you to charge the phone to at least 70%. Google also says a reset can take up to an hour, and that you should try the other solutions first. Back up before you reset anything, and confirm the backup by opening it. I read Google's factory reset guidance on 1 November 2026.

When to stop and call the maker

There are four honest reasons to stop fixing and contact the people who sold you the phone.

• The error survives every fix on this page. You disabled the app, restarted twice, cleared the cache and storage, updated the phone and wiped the cache partition. If the box is still there, the fault is not on the handset's storage.
• The error comes back after every reset. A reset that cannot clear a fault means the fault is in the build the maker shipped. Only a new build from them will do it.
• You hit account sign-in problems after the fix. Setup can finish and leave you unable to sign in. Google's own guidance sends you to the maker when the account side of the phone is the problem.
• The phone was bought faulty and is still in warranty. A brand new handset that dies on its own welcome screens is a warranty case, not a troubleshooting case.

Google's reset page is blunt about the order of things. It recommends trying other solutions first, and it tells you to check your manufacturer's support site for instructions that match your device. Bring your maker the model name and the exact wording of the error box, because that is what they will ask for.

The same fix on four different brands

The fix is the same everywhere, but the menu names are not. Here is where each brand puts the pieces.

Pixel. The error screen carries its own App info button, so you do not need Settings at all. Once setup is finished, open Settings > Apps > See all apps, tap the three-dot menu, choose Show system apps, then tap Android Setup and Storage. The recovery hold is Volume Down plus Power on a Pixel 6 or later, and Volume Up plus Power on the older models.

Galaxy. The error screen carries the App info button there too. The later path is Settings > Apps, then the three-dot menu, Show system apps, then Android Setup and Storage. Samsung's own page notes that on older devices the recovery hold includes a physical Home button, so search your model before you hold anything.

Xiaomi. Xiaomi's support page gives the route as Settings > Applications > Application management, then the three menu points and Show all applications. From there you reach the app menu, tap Force Stop, then Disable. The same page says disabling is safe when Xiaomi allows it. It also warns that removing system apps can be dangerous. MIUI blocks you from uninstalling the ones it treats as essential. I read Xiaomi's MIUI support page on 1 November 2026.

Tecno and HiOS. This site tests on a Tecno Spark 40 running HiOS on Android 15, and HiOS moves these menus between versions. On that phone I use the Settings search box when a menu name is not where I expect it. Open Settings, tap the search bar at the top, and type Android Setup. The app info screen opens from the search result, and Force stop and Disable sit where they sit on other phones.

On any brand, the rule is the same. If a name in this guide does not appear on your phone, use the Settings search box. Type the setting name you are looking for. That search works on HiOS, on stock Android and on the maker's own skins, and it beats any menu tree copied from another phone.

What to do next

Do the disable fix first, because it is four taps and it moves you past the box today. Carry on with setup, then update the phone once you are in. If the error returns every time you retry, go to the recovery menu and wipe the cache only, never the data.

A third retry of the same setup screen will not work. A factory reset on a phone whose fault is in the build will not work either. A setup tool from a site you do not know will not help, because nothing on this page needs installing.

The wider map of Android faults sits in our Android problems and fixes guide. If you are convinced the red box is not setup but a running app failing, read why apps keep stopping instead.