How to Fix Wi-Fi or Bluetooth That Will Not Turn On

The six-step fix order that resolves most Wi-Fi and Bluetooth failures on Android. Save the factory reset for last; hardware replacement is rare.

Short answer: Work the fixes from gentle to drastic. Toggle airplane mode, restart, reset network settings, then clear the Wi-Fi or Bluetooth cache. That short ladder clears about 90 percent of cases. A Play services update or a Safe Mode boot catches most of the rest, and only a failure that survives a full factory reset points to hardware.

RADIO WON’T WAKE UP

When the toggle says on but the radio stays dead

The switch slides over, the icon lights up, and nothing connects. Almost always that is software, not a broken chip. Here is the order to work through it.

THE CAUSE

A stuck service

A crashed system service or a corrupt config file makes the toggle a UI lie.

THE FIX

Gentle first

Airplane toggle, restart, network reset, and a cache wipe clear most cases.

THE LAST RESORT

Rarely hardware

If a factory reset cannot fix it, the radio or its antenna is the problem.

You tap the Wi-Fi tile and it slides to on. The icon lights up. And then nothing happens, no networks appear, or it flips itself back off a second later. Bluetooth does the same trick: the switch animates across, but no device will pair. The toggle is telling you one thing while the radio underneath is doing another.

Four things usually cause it. A system service that quietly crashed, a corrupt network-state file, a firmware hiccup after a half-finished update, or, rarely, a genuine hardware fault. Most people fix this inside the first three steps below, so resist the urge to jump straight to a factory reset. Work the list in order and stop the moment the radio comes back. If your radio does switch on but the connection is patchy or limited, that is a different problem covered in the editors’ guide to fixing limited connectivity on Android.

Try these first, in order

If you only have two minutes, run down this quick list. Each one is gentle, none of them wipes your data, and any of the first three resolves most cases on its own.

Line illustration of a hand tapping a phone Wi-Fi toggle while the radio icon stays inactive.
  • Toggle airplane mode: turn it on, wait about 15 seconds, then turn it off. This power-cycles every radio at once and fixes more cases than any other single move.
  • Restart the phone: a full reboot clears a stuck Wi-Fi or Bluetooth system service that a toggle alone cannot.
  • Reset network settings: this rebuilds the network-state files that most often go bad. It does forget your saved networks and pairings, so have your Wi-Fi password handy.
  • Clear the cache (not the data): wipe the cache for the Wi-Fi or Bluetooth system app to clear a corrupt temporary file without losing any settings.
  • Update and reboot to Safe Mode: refresh Google Play services and check for a system update, then boot into Safe Mode to rule out a misbehaving third-party app.

Why this happens at all

It helps to picture the radio as a chain rather than a single switch. At the bottom sits the kernel driver that talks to the actual Wi-Fi or Bluetooth chip. Above that runs a system service that manages connections. Above that is the toggle you see in Quick Settings, and off to the side are the small config files that remember your networks and paired devices. The switch you tap is only the top link.

Break any link in that chain and the toggle keeps animating while nothing connects. A service can crash and fail to restart. A config file can get corrupted, often after an update that did not finish cleanly. An over-the-air update can leave the firmware in a half-applied state. Each of those is fixable in software, which is why the steps below go in the order they do. For Bluetooth specifically, Google’s first-party advice follows the same path, and you can cross-check it against Android’s own Bluetooth troubleshooting steps.

A real hardware fault is the exception. On a phone under four years old it is uncommon, and even on a well-worn device that is three or more years old it still accounts for a small share of cases, usually under five percent. When hardware is the culprit, it is more often a damaged antenna connection after a drop than the radio chip itself simply dying.

Where the chain can breakWhat goes wrong
The system serviceCrashes and fails to restart, so the toggle does nothing
A network-state fileGets corrupted, often after an update that did not finish
FirmwareLeft half-applied by an interrupted over-the-air update
The radio or antennaPhysically damaged, the rare hardware case

The full six-step fix order

Here is the same ladder in more detail, from the lightest touch to the heaviest. The exact menu names shift a little between stock Android, Samsung One UI, and other skins, so if a path does not match, open Settings and search for the keyword in bold.

Step 1, airplane mode. Swipe down, tap the airplane icon, wait roughly 15 seconds, then tap it off again. This forces every radio to power down and come back fresh, which clears a surprising number of stuck connections in one move.

Step 2, restart. A proper reboot, not just locking the screen, clears a system service that has hung. If the toggle was greyed out or refusing to respond, this is often the step that brings it back.

Step 3, reset network settings. On stock Android, go to Settings, System, Reset options, then Reset Wi-Fi, mobile and Bluetooth. On Samsung the path is Settings, General management, Reset, then Reset network settings. This clears saved networks and pairings, so you will re-enter your Wi-Fi password afterward. Android Authority has a clear, device-by-device walkthrough for resetting network settings if your menu looks different.

Step 4, clear the cache. Open Settings, Apps, See all apps, then tap the three-dot menu and choose Show system. Find the Wi-Fi or Bluetooth entry, open Storage, and tap Clear cache. Do not tap Clear data, which would wipe your settings. Repeat for whichever radio is misbehaving.

Step 5, update. Open the Play Store, tap your profile, then Settings, About, and check the Google Play services version to nudge an update. Then go to Settings, System, System update to make sure no half-installed OTA is sitting in the way.

Step 6, Safe Mode. Safe Mode starts the phone with third-party apps disabled, so if the radio works there, an installed app is the troublemaker. On a modern Pixel or Samsung, press and hold the power button (or power plus volume up), then press and hold the on-screen Power off button until the Reboot to safe mode prompt appears and tap OK. On older Pixels, the 5a and earlier, the legacy method of holding volume down while the phone boots still applies. Google documents the current sequence in its Pixel guide to rebooting into Safe Mode.

Save it for last
A factory reset is overkill for almost everyone

It is tempting to wipe the phone and start over, but a factory reset erases everything and rarely fixes anything the steps above did not. Treat it as the final software move before you suspect hardware, never as an early shortcut.

Symptom to fix, at a glance

If you would rather match the exact behaviour you are seeing to a fix, start here, then drop into the matching step above.

SymptomFirst fix to try
Toggle flips back off on its ownAirplane-mode cycle, then restart
Toggle is greyed out or unresponsiveRestart, then clear the system app cache
Wi-Fi connects but has no internetReset network settings, or forget and re-add the network
Bluetooth will not pair with anythingRestart, then clear the Bluetooth cache
Nothing works after an updateCheck for a pending system update, then reset network settings
Still dead after a factory resetSuspect hardware, visit a repair shop or service center

Common questions

QuestionShort answer
Wi-Fi is on but will not connectCorrupt config, reset network settings or re-add the network
Is it the router or the phone?Test a hotspot, if that works the router is to blame
How do I know it is hardware?Only after a factory reset still leaves the radio dead

Wi-Fi turns on but will not connect to anything. That is usually a corrupt network config rather than a dead radio. Reset network settings, or forget the specific network and add it again from scratch.

How do I know if it is the router, not the phone? Try connecting to a different network, such as a friend’s phone hotspot. If that works, the problem is your router or modem, and a quick power-cycle of the router often sorts it.

How can I tell if it is actually hardware? If the radio stays dead through every step here, including a factory reset, the odds tip toward hardware. The more common physical fault is a damaged antenna trace after a drop, not the radio chip giving out, and both are jobs for a repair shop rather than a settings menu.

The bottom line

A radio that will not turn on looks alarming, but it is almost always software, and the fix is almost always quick. Respect the order: gentle resets first, deeper interventions only if those fail. The airplane toggle, a restart, and a network reset clear most cases without touching your data, and plenty of people never get past step two.

Save the factory reset and the repair shop for the genuine last resorts they are. Run the ladder in order, stop as soon as the radio wakes up, and you will spend a couple of minutes on a problem that can feel like a dead phone.

How we put this together
Tested across three current phones

We reproduced these failures on a Pixel 8a, a Galaxy S24, and a Motorola G Stylus by force-stopping the radio’s system service and corrupting its config, then worked each fix back. The OEM-specific menu paths were checked against Google’s and Samsung’s official support documentation, which is also where the Safe Mode and network-reset steps above are sourced.