When your Fitbit shows Error 1001 alongside “Data not cleared, sync & try again,” the watch’s storage and your Fitbit account have fallen out of sync during a factory reset or firmware wipe. Most often, this happens when a tracker is reset with its buttons before being removed from your phone’s Bluetooth menu and app—and you can clear it by unpairing everything in the right order and finishing setup on the charger.
Quick Answer: How to Fix Fitbit Error 1001 and “Data Not Cleared”
Put your Fitbit on its charger, open the Fitbit (or Google Health) app, and remove the device from your account if it still appears. Next, forget the Fitbit in your phone’s Bluetooth settings, restart your phone, reopen the app, and tap Add Device while the tracker stays plugged in.
Device & Signal Snapshot
- Affected Models: Fitbit Versa, Sense, Charge, Luxe, and legacy smartwatches
- Trigger: Button-initiated factory reset before unpairing, interrupted firmware install, or mismatched phone Bluetooth bond
- Data Risk: Any stats already synced to your Fitbit/Google account remain saved; unsynced activity or sleep logs still trapped on the watch before the failed reset cannot be recovered
What Is Actually Happening?
Fitbit smartwatches store user ownership tokens and operating system files separately from your cloud account. When you hold the physical buttons to force a factory reset without first removing the watch inside the Fitbit app, the watch wipes only part of its memory—or hits an incomplete reset state (Error 1001)—while your phone still holds onto the old encrypted Bluetooth pairing key.
Because the phone and watch disagree on who owns the connection, the Fitbit refuses to boot to a normal clock face. It stays locked on the “Data not cleared, sync & try again” screen until the app finishes a clean setup handshake and pushes a working OS package over Bluetooth or Wi-Fi.
What to Do: Break the Reset Loop in the Right Order
Order matters here. Simply tapping “try again” or holding the watch button for 10 seconds rarely breaks Error 1001 if stale Bluetooth keys remain on your phone.
Step 1: Remove the Old Connection Everywhere
- Place your Fitbit on its powered charging cable and leave it plugged in throughout this process.
- Open the Fitbit (or Google Health) app on your phone, tap the Devices icon (top left), and select your tracker.
- Scroll down and tap Remove This Fitbit (or Unpair). (If this is a brand-new or already-removed watch that does not appear in the app, skip to the next step.)
- Force-close the Fitbit app completely.
- Open your phone’s Settings > Bluetooth, find every entry for your Fitbit model, and tap Forget This Device (or Unpair).
- Check any other phone, tablet, or secondary device nearby that ever synced with this Fitbit and forget it from Bluetooth there as well.
Step 2: Reset Your Phone’s Bluetooth Session
- Turn Bluetooth OFF on your phone.
- Restart your phone completely so background Bluetooth services clear out stale cache tokens.
- Turn Bluetooth ON again—and do not pair the Fitbit directly from your phone’s Bluetooth menu. Always let the Fitbit app initiate the pairing.
Step 3: Run Fresh Setup While Charging
- Open the Fitbit app (make sure Wi-Fi or strong cellular data is on, and temporarily pause any VPN).
- Tap Devices > + Add Device and select your Fitbit model.
- Keep the Fitbit sitting on its charger right next to your phone.
- When the app locates the watch—even if the watch screen still shows the “Data not cleared” message or a red icon—continue through the prompts to accept the 4-digit pairing code and install any prompted firmware update.
What to Check If That Doesn’t Work
The Watch Won’t Connect or Fails Halfway Through Setup
If the Fitbit app scans endlessly or drops the connection before finishing the reset:
- Reinstall the Fitbit app: Delete the app from your phone, restart your phone, download a fresh copy from the App Store or Google Play, and sign back in. This clears corrupted local setup caches.
- Force a 10-second charger restart: Keep the Fitbit plugged in, press and hold the side button (or dual side touch sensors, depending on model) for about 10 seconds until it vibrates or flashes the logo, then immediately run + Add Device in the app.
- Verify account migration: If syncing broke right after switching logins, check Fitbit “Syncing Unavailable” – The 2026 Google Account Migration Fix.
- Fix Android/Fast Pair stalls: On newer Versa or Sense watches failing the initial handshake, follow Fitbit Versa 4 “Fast Pair” Failing: Troubleshooting Bluetooth Handshakes.
The Error Switches to a Red X or Stuck Logo
If clearing Error 1001 shifts your screen to a static Red X or freezes on the startup icon:
- For a persistent loop specifically on “Data not cleared,” review How to Clear the “Data Not Cleared, Sync & Try Again” Fitbit Loop.
- If a red warning icon appears during the firmware push, follow How to Fix the “Red X” on Your Fitbit Luxe Screen.
- If the device freezes indefinitely on the boot icon, see Why Your Fitbit Charge 6/Sense 2 is Stuck on the “Smile” Logo.
You can also browse Fitbit Legacy Error Codes & OS Sync Failures for related screen messages.
When It’s Actually a Hardware Problem
Contact Fitbit Customer Support—or return the device to the retailer if it arrived sealed out of the box with Error 1001—when:
- Two-phone test fails: You unpair everywhere, reinstall the app, and try setting up the watch on a second smartphone while plugged into power, yet the watch either never broadcasts a Bluetooth signal or flashes a Red X immediately after every 4-digit pairing code.
- Infinite boot crash: Instead of staying on the setup prompt, the watch reboots back to the Fitbit logo every few seconds on the charger and shuts off completely the moment you unplug it.
Never try to fix “Data not cleared” by pairing through your phone’s Bluetooth settings—always wipe the old Bluetooth listing first, leave the watch on its charger, and let the Fitbit app push the fresh setup and firmware link.