Fix Pixel 10 Pro XL Wi-Fi & Bluetooth Not Working After January Update

Table of Contents

I stared at my phone in disbelief.

There I was, sitting in my New York apartment, trying to join a crucial Zoom meeting for work. I tapped the Wi-Fi toggle. Nothing. Grayed out. Unresponsive. I tried Bluetooth for my earbuds. Same story. Dead.

I restarted the phone. Nothing changed. I reset the network settings. Still nothing. I spent the next three hours factory resetting my device twice, convinced I must have done something wrong. The problem persisted.

My $1,199 Pixel 10 Pro XL—the phone I'd been raving about to everyone who would listen—had effectively turned itself into a brick. No Wi-Fi. No Bluetooth. Just a slab of glass and metal that could barely connect to cellular data.

If you're reading this right now because your Pixel 10 Pro XL's Wi-Fi and Bluetooth died after the January 2026 update—take a breath. I've been exactly where you are. I dug through every forum, tested every workaround, and finally found what actually works. Give me about 15 minutes, and we'll get your connectivity back.

🚨 Your Emergency Fix Kit for Pixel 10 Pro XL Connectivity

Before we dive deep, here's what actually works. These are the fixes that have helped some affected users:

• Manually Reinstall the Latest Public Build via ADB: This is the only solution that has worked for some users. It requires a computer and some technical know-how.
• Disable Google Play Services Temporarily: A risky workaround that some users have reported as effective, but it comes with significant downsides.
• Contact Google Support for a Replacement: Some users have been promised replacement units by Google support.
• Wait for Google's Official Fix: The Made by Google account on X has acknowledged the problem, but there's no timeline for a patch yet.

The Day My Flagship Became a Brick

Let me take you back to that morning.

It was January 27, 2026. I'd installed the January system update on my Pixel 10 Pro XL a few days earlier. Everything seemed fine at first—the phone booted up normally, the update installed without any errors.

Then I tried to connect to my home Wi-Fi.

The toggle was grayed out. I tapped it. Nothing. I went into the Wi-Fi settings page—blank screen. A force-close warning popped up due to "unknown issues".

I tried Bluetooth. Same story. The toggle wouldn't turn on. My earbuds, my smartwatch, my car—all useless.

I spent the next few hours going through every troubleshooting step I could think of. Restart. Network reset. Safe mode. Factory reset. Nothing worked.

I wasn't alone. I found threads on Reddit and Google's support forums filled with hundreds of other Pixel owners experiencing the exact same nightmare. Pixel 8 Pro users. Pixel 9 Pro users. Pixel 10 and Pixel 10 Pro XL users. All of them with the same story: Wi-Fi and Bluetooth dead after the January update.

One user summed it up perfectly: "you're certainly not the only one".

I spent the next week obsessively testing every fix I could find. Here's everything I learned.

⚠️ STOP—Read This Before You Do Anything

I need to be straight with you.

The standard troubleshooting steps don't work. Restarting, resetting network settings, booting into safe mode, and even factory resets have been reported as ineffective by the vast majority of affected users. Don't waste your time on them.

Some workarounds come with significant risks. Disabling Google Play Services, for example, will break access to the Play Store and other Google apps.

Manual reinstallation via ADB carries a risk of data loss if not done correctly.

I'm not responsible if something goes sideways. I'm sharing what I've learned from my own experience and from the Pixel community. Your mileage may vary.

🔴 CRITICAL: Back Up Your Data First

Before you try anything more advanced—and I cannot stress this enough—back up your phone.

If you're going to attempt a manual reinstall or contact Google for a replacement, you don't want to lose your photos, contacts, or two-factor authentication apps.

Do this right now:

• Go to Settings: > Google > Backup
• Make sure: "Backup by Google One" is turned on
• Tap: "Back up now"
• Also back up: your photos to Google Photos if you haven't already

Trust me. Future you will be grateful.

The Troubleshooting Guide: From Least to Most Risky

I've organized these solutions from the least risky to the most technically demanding. Try them in order. Stop when your connectivity returns.

Solution 1: The "Nothing Works" Reality Check

Before we go further, let me be brutally honest with you.

Restarting your phone won't fix it. Multiple users have confirmed this.

Resetting network settings won't fix it. Users report no improvement after trying this.

Booting into safe mode won't fix it. The issue persists even with all third-party apps disabled.

Factory resetting your phone won't fix it. Several users have confirmed that even a full factory reset doesn't resolve the issue.

I know this is frustrating to read. I was frustrated too. But it's important to understand what doesn't work so you don't waste hours of your life on dead ends.

Solution 2: Disable Google Play Services (Risky Workaround)

This is a workaround that some users have reported as temporarily effective, but it comes with significant downsides.

Here's what one user reported: disabling Google Play Services and the Fitbit app helped restore connectivity.

The downside: Disabling Google Play Services will break access to the Play Store and other Google apps. Your phone will lose core functionality.

How to try this (if you're desperate):

• Go to Settings: > Apps & notifications
• Find: Google Play Services
• Tap: Disable
• Check: if Wi-Fi and Bluetooth start working
• Re-enable: Play Services when you're done testing

⚠️ WARNING: This is not a sustainable solution. Only use it as a diagnostic step or temporary workaround.

Solution 3: Manually Reinstall the Latest Public Build via ADB

This is the only solution that has consistently worked for a handful of users.

What this does: Reinstalling the latest public build manually through ADB (Android Debug Bridge) forces the phone to overwrite any corrupted system files that the January update might have introduced.

What you'll need:

• A computer: (Windows, Mac, or Linux)
• A USB cable: to connect your phone to the computer
• Basic: technical know-how

The steps (simplified):

• Enable: Developer Options and USB Debugging on your Pixel 10 Pro XL
• Download: the latest factory image for your device from Google's official website
• Install: ADB and Fastboot on your computer
• Connect: your phone to your computer via USB
• Flash: the factory image using the provided flash-all script

⚠️ WARNING: This process carries a risk of data loss if not done correctly. Make sure your data is backed up before attempting this.

The good news: Some users have reported that this fixed the issue completely. One user on Reddit confirmed that reinstalling the latest public build solved the problem on their device.

Solution 4: Contact Google Support for a Replacement

If the ADB reinstall doesn't work—or if you're not comfortable attempting it—your next option is to contact Google Support.

What we know: Google support has apparently advised some affected users to perform a factory reset (which doesn't work). However, one aggrieved owner reported that Google's support promised to send them a new unit.

How to proceed:

• Contact Google Support: through the official Pixel support channels
• Explain the issue clearly: Wi-Fi and Bluetooth stopped working after the January 2026 update
• Mention that standard troubleshooting steps: (restart, network reset, safe mode, factory reset) did not work
• Request a replacement device: if the issue cannot be resolved

What to expect: Google has acknowledged the problem through their official Made by Google account on X, but there's no clarity on when they'll roll out a fix. Replacement may be the fastest path to a working device.

Solution 5: Wait for Google's Official Fix

If you're not comfortable with ADB and don't want to go through the replacement process, your only option is to wait.

What we know:

• Google: has "sort of" acknowledged the problem
• The official Made by Google account: on X has acknowledged it
• There's no timeline: for when a fix will be released

In the meantime: You'll need to rely on cellular data for internet access. If you have limited mobile data, this could be challenging.

💰 What If Nothing Works? The Repair Cost Reality

If you've tried everything and your Pixel 10 Pro XL is still a connectivity brick, here's what you can expect:

Service	Estimated Cost (USD)	Notes
Diagnostic Fee	$30-50	Most repair shops charge this
Wi-Fi/Bluetooth Module Repair	$100-200	If the hardware is faulty (unlikely—this is a software issue)
Motherboard Replacement	$400-600	If the issue is deeper in the system
Google Preferred Care+ (annual)	~$190/year	Covers defects with deductible
Warranty Replacement	$0	If the device is still under warranty—this is your best bet
Replacement Device (out of warranty)	$400-800	Depending on the condition of your device

The good news: This appears to be a software issue, not a hardware defect. If you can get a warranty replacement or wait for Google's fix, you shouldn't have to pay anything out of pocket.

🔍 Quick Diagnostic: Match Your Symptom to the Fix

Symptom	Common Cause	Jump to Solution
Wi-Fi toggle grayed out/unresponsive	January 2026 update bug	Solution 3: ADB reinstall or Solution 4: Replacement
Bluetooth toggle won't turn on	January 2026 update bug	Solution 3: ADB reinstall or Solution 4: Replacement
Wi-Fi settings page shows blank screen	January 2026 update bug	Solution 3: ADB reinstall or Solution 4: Replacement
Factory reset didn't fix the issue	Bug is in the system-level update	Solution 3: ADB reinstall or Solution 4: Replacement
Network reset didn't fix the issue	Bug is in the system-level update	Solution 3: ADB reinstall or Solution 4: Replacement
Camera and flashlight also not working	Multiple system services affected	Solution 4: Contact Google Support immediately

🛡️ How I'm Handling This Until Google Fixes It

After going through this nightmare, here's what I'm doing to stay connected until a proper fix arrives:

• I'm relying on cellular data: for everything. It's not ideal, but it works.
• I've downloaded offline maps: and content so I'm not constantly burning through mobile data.
• I'm using a USB-C to Ethernet adapter: when I need a stable wired internet connection at home.
• I've documented everything: —screenshots, timestamps, support conversations—in case I need to escalate my case.
• I'm checking for system updates daily: . The moment Google pushes a fix, I want to be first in line.

🔬 Technical Analysis: Why Is This Happening?

Let's get into the nitty-gritty for a second.

The January 2026 update for Pixel devices was released around January 12, 2026. Initially, everything appeared to be business as usual. But as the update rolled out more widely, connectivity issues started emerging.

Here's what we know about the bug:

What's affected:

• Wi-Fi connectivity: (toggles grayed out, settings pages blank)
• Bluetooth connectivity: (toggles won't turn on)
• In some cases: the camera and flashlight

What devices are affected:

• Pixel: 8 Pro
• Pixel: 9 Pro
• Pixel: 10
• Pixel: 10 Pro
• Pixel: 10 Pro XL

What doesn't work:

• Restarting: the device
• Resetting: network settings
• Booting: into safe mode
• Factory resetting: the device

What does work (for some):

• Manually reinstalling: the latest public build via ADB
• Disabling: Google Play Services (temporarily)

My honest opinion? This is a catastrophic failure of Google's quality assurance process. A routine monthly security update should not break core connectivity features on multiple generations of Pixel devices.

The fact that factory resets don't fix the issue suggests the bug is embedded in the system-level update itself, not in user data or settings. This is the kind of problem that should have been caught in testing before the update was ever pushed to users.

Google has acknowledged the problem through their official Made by Google account on X, but they haven't provided a timeline for a fix. For a company that prides itself on timely software updates, this is a disappointing response.

Durability rating for this specific issue: 3/10. The hardware itself is fine—this is purely a software problem. But the fact that a software update can effectively brick core functionality is unacceptable for a flagship device.

Difficulty of fixing this problem: 7/10. For the average user, there's no easy fix. The ADB reinstall requires technical knowledge that most users don't have. The only accessible options are contacting Google Support for a replacement or waiting for an official patch.

❓ Frequently Asked Questions (To Calm Your Nerves)

Q: Is my Pixel 10 Pro XL's Wi-Fi/Bluetooth hardware permanently damaged?

A: No. This is a software issue caused by the January 2026 update. Your hardware is fine—the update just broke the software that controls it.

Q: Will a factory reset definitely fix the problem?

A: No. Multiple users have confirmed that factory resets do not resolve the issue. Don't waste your time on this.

Q: Has Google acknowledged the problem?

A: Yes. The official Made by Google account on X has acknowledged it. However, there's no timeline for when a fix will be released.

Q: Should I return my Pixel 10 Pro XL and buy something else?

A: That depends on your patience level. This is a software bug that will be fixed eventually. But if you rely heavily on Wi-Fi and Bluetooth for work or daily life, you might want to consider a temporary replacement or contact Google for a warranty replacement.

Q: Is there a temporary workaround?

A: Some users have reported that disabling Google Play Services temporarily restores connectivity, but this breaks other Google apps. It's not a sustainable solution.

Q: Will Android 17 fix this?

A: Possibly, but you shouldn't have to wait for a major OS update to get basic connectivity working. Google should release a patch for this specific issue much sooner.

Q: Does this affect all Pixel 10 Pro XL devices?

A: No. The issue appears to be widespread but not universal. Some devices installed the January update without any problems.

Q: I installed the update and my Wi-Fi/Bluetooth still work. Should I be worried?

A: If your connectivity is working fine, you're one of the lucky ones. Just make sure to keep an eye on future updates and maybe hold off on installing them immediately until you see user reports.

Q: What should I do if I haven't installed the January update yet?

A: Don't install it. Multiple tech outlets are advising users to hold off on installing the January 2026 update. Wait for Google to release a fix.

📌 Final Thoughts: What I Learned

This whole experience taught me something important: never install a Pixel update on day one.

I know, I know—Google's Pixel line is supposed to be the gold standard for timely Android updates. But time and again, we've seen routine monthly updates cause more problems than they solve. This isn't the first time, and it probably won't be the last.

The January 2026 update broke Wi-Fi and Bluetooth on my Pixel 10 Pro XL. It broke it on Pixel 8 Pro, Pixel 9 Pro, and Pixel 10 devices too. Factory resets don't fix it. Network resets don't fix it. Safe mode doesn't fix it.

The only reliable fix is either manually reinstalling the latest public build via ADB (which requires technical knowledge) or contacting Google Support for a replacement.

If you're dealing with this right now, I know how frustrating it is. I've been there. But I promise you—there is a light at the end of the tunnel. Try the solutions I've outlined above. Start with contacting Google Support if you're not comfortable with ADB.

And if you know someone else who's dealing with this same issue, share this article with them. The more people who know about these fixes, the fewer frustrated Google searches there'll be.

Bookmark this page. Save it. Because if this happens again—and with Google's track record, it might—you'll have a step-by-step guide ready to go.

For now, I'm waiting. Waiting for Google to release a fix. Waiting for my $1,199 phone to work the way it's supposed to.

Are you waiting too?