USB Success Narrows the Problem but Does Not Test Bluetooth
If Nano X works by USB but not over Bluetooth in Ledger Live, keep the functioning wired route as evidence while investigating the wireless conditions separately. The current app is Ledger Wallet. A successful desktop USB session can show that the hardware completes that task; it does not prove the phone app has permission or a valid Bluetooth association.
Begin by identifying the same intended operation on each host. Comparing a desktop portfolio view with a phone pairing scan tests different capabilities and cannot support a simple transport conclusion.
Confirm the Wireless Host Is Supported
The dedicated desktop app uses USB rather than the mobile Bluetooth pairing workflow. Use a compatible phone and actual Nano X for wireless testing. Nano S Plus instructions are not interchangeable, because that model has no Bluetooth.
Review Ledger’s Nano X Bluetooth guidance and the phone’s current app requirements. Keep the hardware charged and unlocked and enable its radio. USB may supply power that is absent when testing wirelessly, so record the actual device state rather than assuming it remained identical.
Check app discovery permission on the phone and close another phone’s active session. System Bluetooth working for headphones does not establish this application is authorized to discover and use Nano X.
Compare the First Failed Wireless Stage
If no device appears, focus on readiness, permission, proximity, and a possible abbreviated label. If Nano X appears but code confirmation fails, inspect both displays and cancel disagreement. If pairing completes but the app task fails, record that narrower session or component error.
Use an intended device-management or address-verification action after connection. Public balances can remain visible without live hardware access and are an insufficient test. Do not send a transaction merely because it offers a convenient Bluetooth button.
Repair Pairing State Without Discarding the Wired Baseline
For an unusable retained relationship, follow the coordinated app, phone, and Nano X pairing cleanup in the official guide. Read Reset pairings under Control Center, Settings, Security, distinguishing it from Reset device.
Reconnect through the app and complete a matching code exchange when requested. If the wired route still works but wireless fails, report both controlled results with versions and hardware state. Do not reset wallet keys to make the wireless test look like first use.
Keep Firmware Eligibility Separate
The current Nano X product specification identifies installed Ledger OS 2.4.1 or later as the condition for Bluetooth OS updates; older versions require a supported wired desktop or Android update route. That threshold is not a statement of the latest release.
It also does not mean every Bluetooth failure calls for another firmware installation. Read the actual required operation and current instructions. Let any already progressing OS installation finish before changing transports or hosts, and use model-specific continuation for a failed state.
Try the same intended operation over each supported connection rather than comparing unrelated screens. Reading an old portfolio over Bluetooth and completing a hardware action over USB would otherwise produce misleading evidence about what works.
Transport Questions
Can I Use the Working USB Route Meanwhile?
Use it for supported tasks on a suitable host while investigating wireless access. Reconnecting the same configured hardware does not require copying recovery words into either interface.
Does USB Success Guarantee Account Matching on the Phone?
No. Add or synchronize the intended supported accounts separately and compare chains and public identities. Pairing and local account organization are different tasks.
What Should Remain Unchanged During Diagnosis?
Preserve the wallet configuration and offline backup. Record one transport change at a time, and exclude secrets from screenshots, support reports, or any phone pairing form.