Read the Device Before Starting Another Installation
If a Ledger device locks during app installation in Ledger Live, inspect the hardware screen and host status before clicking Install again. The host application is currently Ledger Wallet. A request waiting for unlock, an app already installed, and a device still performing work require different next steps.
Keep any progressing Ledger OS installation powered and connected. Coin-app management and firmware installation are separate operations; advice suitable for an idle locked session must not interrupt an advancing OS update.
Unlock Through the Device’s Own Controls
If the hardware is genuinely on its ordinary locked or PIN screen, enter the known correct PIN there. Do not type it into the companion application, a support chat, or a repair webpage. Stop if you are uncertain rather than making repeated guesses that could trigger the device’s protection.
Follow the screen requested by the active management flow after unlocking. The official Nano navigation guide distinguishes the dashboard from an open blockchain app and device settings. Use matching touchscreen guidance for other models.
Check Whether Installation Actually Completed
Once normal access returns, inspect the device’s own app list and the current My Ledger inventory. The host may have lost the session after completion, so its last progress display alone is not conclusive. Do not queue another copy simply because the final confirmation was missed.
| Observed state | Next check |
|---|---|
| Ordinary PIN screen | Unlock on hardware using the known PIN. |
| App already present | Verify the installed inventory and intended operation. |
| Advancing OS installation | Preserve its host, power, and connection. |
For example, if Solana now appears on the hardware and the refreshed inventory shows it installed, test the intended supported Solana account action rather than reinstalling it repeatedly. If it is absent and the previous request failed, retain the exact error before resuming through the supported install control.
Re-establish the Management Session Deliberately
Ensure the host is current and genuine, the appropriate data connection is available, and other wallet clients are not competing for the device. On desktop, use USB; mobile transport depends on model and platform. A reliable power supply is not a substitute for a working data path.
Ledger’s secure management reference documents unlock and secure-connection interactions for installing apps. Read the expected prompt and complete only the management request you initiated. It should not be replaced by an unexplained payment or contract approval.
If a later error names storage or compatibility, address that stated condition. Repeated unlocking does not increase hardware capacity or make an app compatible with an unsupported device OS. Use Ledger’s app-update explanation when the required version is unavailable.
Investigate Repeated Locking Without Removing Protection
Note whether the device locks before the request begins, during an idle wait, or after a connection drop. Record the model, OS version, power arrangement, and host error. Review the model’s documented auto-lock settings only if they are relevant to the observed timing.
Do not permanently disable the hardware’s normal protection just to avoid looking at the screen. Keep the device attended during authorized maintenance and respond to expected prompts. If it repeatedly locks unexpectedly while work is active, stop the repeated install attempts and request official guidance.
Is Auto-Lock the Same as a Factory Reset?
No. A normal lock protects access and can be released using the correct device PIN. Initial setup or recovery screens are different states and should not be treated as an ordinary unlock prompt.
Did Locking Delete My Crypto?
An ordinary lock does not itself move blockchain assets. App installation concerns software used by the signer. Verify the actual account or transaction separately if another symptom exists.
Can I Send My PIN to Support for Testing?
No. Describe the screen and timing without the PIN value. Recovery phrases, private keys, and photos of backups must remain outside the diagnostic record.