A Phone Change Creates Two Different Jobs
If Nano X is still paired to an old phone, set up the new Ledger Live connection and assess the old phone’s remaining data separately. Ledger Wallet is the current app name. Removing Bluetooth does not remotely erase a portfolio, and moving an interface does not require moving blockchain funds.
Decide whether the old phone is available and trusted, unavailable or being prepared for disposal. That distinction matters for privacy even when the hardware connection to the new phone is the immediate goal.
Keep a Useful Reference From an Available Phone
If you still control it, privately note the intended chains and enough public history to recognize the accounts later. Finish its ordinary device session so it does not compete with the new phone. Do not export recovery words or place secrets into migration notes.
If Ledger OS installation is actively progressing through that phone, preserve the supported session instead of moving Nano X midway. A completed update or an explicit model-specific recovery procedure comes before ordinary handover.
Establish the New Phone Independently
Use Ledger’s official mobile links and check current compatibility. Choose the flow for an already configured Nano X. Unlock the hardware on its buttons and grant the phone app the relevant Bluetooth access.
Begin one app-led request. Keep both screens visible, identify the intended device and compare any pairing codes before confirming. Cancel disagreement or a request whose source is unclear. A familiar old device name is not sufficient evidence of the right exchange.
Handle an Obsolete Association Only When Required
If old relationship information prevents the new session, use the Nano X section of official pairing troubleshooting. Its Reset pairings command has a different scope from Reset device. Coordinate app and phone records where the procedure directs.
The old phone does not need to reveal wallet keys to permit the new interface. If it is unavailable, report that fact rather than treating possession of its local app password as a necessary hardware recovery credential.
Evaluate the Old Phone’s Remaining Information
A retired installation may still reveal addresses, labels or transaction history. Ledger’s extended public-key explanation helps show why viewing information deserves privacy even when it cannot itself sign payments.
Use the phone vendor’s supported security and disposal controls for a device you own. A Nano X pairing reset is not a remote phone wipe. Likewise, clearing a local app is not a guarantee that every earlier export or screenshot has disappeared.
If secrets were previously entered or photographed on the old phone, that is a distinct exposure question. A new Bluetooth association cannot make a copied backup private again. Preserve usable access and use official guidance for that separate incident.
Check the New Account View After Connection
Discover the intended supported accounts with the same hardware configuration or use an eligible documented sharing flow. Compare the actual chain and public history before copying old nicknames. Pairing completion does not itself recreate every local account entry.
For example, a new phone can communicate with Nano X while showing no portfolio accounts yet. Finish account addition rather than resetting working pairing or initializing another wallet.
Old-Phone Questions
Must the old phone remain nearby?
Do not rely on it as a source of signing keys. Follow the new phone’s supported connection flow with the configured Ledger. An active old session may instead be something to finish before testing.
Can the two phones show the same balance?
They can refer to the same public blockchain account. That does not duplicate assets or imply both have an active hardware session at once.
Does my hardware PIN belong in the new app?
No. Enter it using Nano X controls. App privacy credentials and phone unlock credentials are separate, and backup words stay outside both phone interfaces.
Comments are closed