Finish the Nano X Update Before Testing Bluetooth
If Nano X stops appearing over Bluetooth after firmware maintenance, first establish that the Ledger OS update completed and the device is in its normal usable state. The app is now Ledger Wallet, previously called Ledger Live. A progressing installation is not the moment for pairing resets, cable experiments, or app-data removal.
If the hardware instead shows an explicit Update or Bootloader failure state, use Nano X-specific continuation guidance. Ordinary Bluetooth advice is not a substitute for completing or recovering that hardware operation.
Restart Only at the Documented Post-Update Point
Ledger’s current Bluetooth help describes restarting the device after relevant Ledger OS maintenance before pairing again. Apply that advice after the update’s supported completion, not while an indicator is actively advancing.
Power Nano X back on, unlock it, and inspect its Bluetooth state. Keep the intended phone nearby with the app visible. End another phone’s active session and check the mobile app’s relevant discovery permission.
Note whether the default device name is abbreviated after the update. A shortened label can explain why a user overlooks the right result in a scan. It does not justify accepting an unknown device or mismatched pairing codes.
Keep Update Eligibility Separate From Reconnection
The current Nano X specifications state that Bluetooth OS updates require an already installed Ledger OS 2.4.1 or later; older versions need a supported wired desktop or Android route first. That is an eligibility threshold, not the newest release number.
Successful wireless transactions do not establish every firmware route, and a post-update pairing failure does not automatically mean the OS must be installed again. Read the current model and release instructions for the operation actually required.
Test the Existing Association
Start the intended Nano X connection inside the mobile app and observe discovery, selection, and device confirmation separately. A valid existing association may reconnect without a new code. A saved phone entry can also remain even though the app cannot complete its session.
Use a device-dependent management or address-verification action to judge communication. Previously loaded balances are public account information and can stay visible without a live Nano X connection.
If a new code comparison appears, inspect both displays fully. Cancel disagreement or an unsolicited request. Do not approve merely because the device label resembles the pre-update name.
Rebuild Pairing State if the Normal Attempt Fails
Follow the official Nano X branch to clear stale app and phone records and use the hardware’s Reset pairings command where directed. Its button menu uses Control Center, Settings, Security. Do not choose Reset device or attempt to restore a seed as a radio repair.
Pair again through the app, then repeat the intended device action once. If it succeeds but account history remains old, investigate synchronization separately. Pairing cleanup cannot restore an unavailable blockchain explorer.
For example, a completed update followed by an empty scan differs from a device still showing installation progress. Capture the exact hardware screen before deciding which troubleshooting branch applies; timing alone cannot distinguish them.
Post-Firmware Questions
Should I Install the Same OS Repeatedly Until Bluetooth Appears?
No. Verify the completed device state and troubleshoot the communication layer. Another firmware attempt should have a current documented purpose, not serve as an indiscriminate scan reset.
What Should I Report if It Still Cannot Be Found?
Provide the installed OS information, host app and phone versions, hardware state, and the first failed pairing stage. Do not include recovery words or PINs.
Can App Deletion Be Done During the Update?
Do not remove or clear the host while a device installation progresses. Preserve its supported session and resolve explicit hardware failure under the model’s instructions first.