An Oura Ring Gen 4 firmware update freezing at 99% before showing a “Something went wrong” error indicates a failure during the final Bluetooth Low Energy (BLE) handshake or cryptographic checksum verification. At 99%, the binary payload has fully transferred from your phone to the ring’s flash memory. The process fails because the ring cannot reboot into its new firmware partition or the phone fails to confirm the installation before the BLE connection times out.
Quick Answer
Place the Oura Ring on its powered charging dock, force-close the Oura app, toggle Bluetooth off and on, and restart the update. At 99%, the ring verifies data integrity and executes a soft reset; keeping the ring docked ensures steady voltage, preventing low-power state resets and Bluetooth packet drops during the final installation handshake.
Device & Signal Snapshot
| Diagnostic Field | Technical Detail |
|---|---|
| Affected Device | Oura Ring Gen 4 (also applies to Gen 3) |
| Failure Point | 99% Progress Mark (Post-Transfer / Flashing & Verification Phase) |
| Error String | “Something went wrong” / “Update timed out” / “Connection lost” |
| Communication Protocol | Bluetooth Low Energy (BLE) Secure Attribute Protocol (ATT) / Nordic DFU |
| Data / Hardware Risk | Minimal; dual-bank flash memory prevents permanent bricking by defaulting to the previous bootloader |
What Is Actually Happening?
Oura firmware updates use an Over-the-Air Device Firmware Update (OTA DFU) pipeline managed by Nordic Semiconductor microcontrollers. The update executes in three distinct stages:
[ Stage 1: 0% – 90% ] ──> Data Transfer (Phone transmits binary chunks via BLE)
[ Stage 2: 90% – 98% ] ──> Flash Writing (Binary writes to secondary memory bank)
[ Stage 3: 99% – 100% ] ──> Checksum Verification, Boot Swap & Final Handshake
Dual-Bank Flash Memory
┌───────────────────────────────────┬───────────────────────────────────┐
│ Primary Active Bank │ Secondary Staging Bank │
│ (Currently Running Firmware) │ (Incoming 99% Payload) │
└─────────────────┬─────────────────┴─────────────────┬─────────────────┘
│ │
│ CRC Checksum │
└─────────────── < ─────────────────┘
Match: Swap & Boot New OS
Mismatch / Timeout: Abort & Revert
When the progress bar reaches 99%, data transmission is complete. At this precise point:
- CRC Checksum Verification: The ring’s bootloader runs a Cyclic Redundancy Check (CRC) to confirm that no data packets were corrupted during the BLE transfer.
- Bank Swap & Soft Reboot: The microcontroller swaps the active memory pointer from the old firmware bank to the new one and executes a rapid internal soft reset.
- The BLE Re-Connection Handshake: Once rebooted, the ring advertises a new firmware signature over BLE. The Oura app must discover this new broadcast within a strict timeout window (typically 30–45 seconds) to flip the UI to 100% “Update Complete.”
If the ring’s battery voltage dips during the write cycle, or if the phone’s operating system delays the BLE reconnection, the app aborts the process, reports “Something went wrong,” and reverts to the existing firmware.
How to Tell Which Problem You Have
Determine why your update is failing at 99% by checking the hardware and LED behavior:
- Pattern A: BLE Handshake Timeout (Most Common)
- Symptom: The progress bar stays at 99% for 60 seconds, displays “Something went wrong,” and the charger LED pulses steady white.
- Meaning: The ring successfully updated internally, but the phone’s Bluetooth stack failed to reconnect and verify the new OS version within the timeout window.
- Pattern B: Voltage Drop / Charger Sleep Mode
- Symptom: The update fails instantly when reaching 99%, and the charger LED turns off or blinks red.
- Meaning: The ring attempted high-draw flash writing while running on low battery, or the charger entered a USB power-saving sleep state.
- Diagnostic Check: For charger-specific light codes.
- Pattern C: Corrupted BLE Bonding Cache
- Symptom: The update fails at 99%, and the app displays a perpetual “Connecting to ring…” or “Searching for ring…” status afterward.
- Meaning: The phone’s OS Bluetooth cache is attempting to communicate with the old firmware profile.
What to Do: Step-by-Step Resolution
Follow these sequential fixes to clear the communication block and finish the update:
Step 1: Dock Ring on Wall Power ──> Ensure stable voltage (Avoid PC USB ports)
│
▼
Step 2: Clear BLE Cache ──> Toggle Bluetooth & force-close companion app
│
▼
Step 3: Keep Screen Active ──> Prevent OS background power throttling
1. Enforce Proper Charger Placement
Do not run firmware updates while wearing the ring. Place the Oura Ring Gen 4 on its dedicated charging dock connected to a standard 5V wall adapter rather than a low-power laptop USB port. Ensure the sensor bumps align directly with the dock’s indentation. For physical placement troubleshooting.
2. Clear the Bluetooth State and Force-Restart
- Close the Oura app completely (swipe up from the app switcher).
- Go to your phone’s Settings $\rightarrow$ Bluetooth.
- Toggle Bluetooth OFF, wait 10 seconds, and turn it back ON.
- Reopen the Oura app, keep the phone within 12 inches of the charging dock, and re-initiate the firmware update.
3. Disable Background App Throttling
Keep the Oura app open on your screen during the entire 99% phase. Mobile operating systems (especially iOS and aggressive Android battery managers) can throttle background BLE polling right as the app tries to capture the reboot handshake.
What to Check If That Doesn’t Work
If the update continues to fail at 99% across multiple attempts:
1. Perform a Hardware Soft Reset
A soft reset restarts the ring’s microcontroller without erasing your historical data or membership status:
- Place the ring on the charger.
- Tap the charger firmly against a flat, solid surface (like a wooden table) 4 to 6 times within 3 seconds.
- Observe the charger LED: it will flash momentarily to indicate the onboard microcontroller has restarted.
- For detailed mechanics on this physical sequence.
2. Clear OS Bluetooth Bonding
If the phone refuses to capture the post-update handshake, reset the cryptographic pairing keys:
- Go to your phone’s Bluetooth settings and select Forget This Device for your Oura Ring.
- Clear the Bluetooth system cache if using Android. For complete steps.
- For general BLE security handshakes across wearable platforms.
- Re-pair the ring through the Oura app and restart the update.
When It’s Actually a Hardware Problem
A firmware update freeze at 99% rarely indicates permanent hardware failure due to the dual-bank memory protection. However, hardware escalation is necessary if you observe:
- A Solid Red LED on the Charger Dock: A solid red light indicates a battery voltage hardware fault or sensor circuit failure that prevents flash writing.
- Total BLE Loss Post-Update: The ring fails to broadcast Bluetooth signals entirely even after being left on a powered dock for 30 minutes. If the app cannot find the ring at all.
A 99% firmware failure is a communication timeout during the final reboot verification, not a bricked ring. Keep the ring docked to steady wall power, restart your phone’s Bluetooth stack, and keep the app active on screen so the installation handshake can complete.