Ledger Error 0x5515: Locked Device Signing Interruption Fix
Ledger error 0x5515 is the proprietary BOLOS status word for "Device Locked". This occurs when a web3 application attempts to communicate with a Ledger whose screen saver has activated or whose PIN has not been entered. Hardware wallets immediately lock down communication channels when locked to prevent unauthorized access. Simply unlock the device with your PIN and re-open the coin applet. Adjust the auto-lock setting to keep the session active.
# Root Cause & Technical Architecture
Under the Ledger BOLOS security architecture, the Secure Element enforces an immediate communication barrier when the device is locked. Status word `0x5515` is returned whenever a host application initiates a command that requires user interaction while the OS is in the locked state. This frequently happens when users prepare complex transactions in a browser, leaving the Ledger idle long enough for its auto-lock timer to engage.
# 4-Step Actionable Diagnostic Protocol
Step-by-Step ResolutionUnlock Device with PIN Code
Press the buttons or tap the screen to wake the Ledger, enter your PIN, and verify that the home screen or coin app is visible.
Re-Open the Specific Blockchain Application
After unlocking, ensure you open the appropriate coin applet (e.g. Ethereum or Solana) until the screen displays "Application is ready".
Adjust Auto-Lock Timeout Setting
Navigate to Settings > Security > Auto-lock on your Ledger device and select a longer duration (e.g. 5 or 10 minutes) to avoid premature locks.
Click Retry in the Web3 Wallet Interface
Once the device is unlocked and the coin app is open, click the "Retry" button on MetaMask or Rabby to re-send the signing prompt.
# Diagnostic Verification Code / Command
textBOLOS Kernel State Check:
Condition: Screen Saver Active (PIN Required)
Host Event: dApp calls eth_sendTransaction -> Browser issues APDU
Device Response:
SW1 = 0x55
SW2 = 0x15
Decoded Status: ERROR_DEVICE_LOCKED
Resolution: Enter PIN -> Re-launch applet -> Retry commandLaunch Derivation Path Inspector
Execute client-side cryptographic simulation and parameter checks safely in your browser via native WebCrypto without sending private keys or mnemonics over the wire.
Read Full Investigation & Recovery Workflow
Explore complete architectural diagrams, edge-case failure trees, and detailed post-mortem analysis in our verified deep guide.
# Related Diagnostic Codes in Hardware & BIP-39
Related Hex StatusesLedger Stax 24-Words Invalid, Seed Phrase Typo & Wrong Word
Fix Ledger Stax 24-words invalid error and seed phrase typos. Resolve E-Ink capacitive touch entry slips, SHA-256 checksum failure, and Recovery Check.
Ledger Nano X 24-Words Invalid, Seed Phrase Wrong Word & Typo
Fix Ledger Nano X 24-words invalid and wrong word errors. Troubleshoot dual-button debounce skips, BIP-39 stem swaps, and Recovery Check validation.
Ledger Nano S Plus (S+) 24-Words Typo & Seed Phrase Wrong Word
Fix Ledger Nano S Plus 24-words typo and wrong word alerts. Resolve 2048-wordlist prefix autocomplete traps, button misses, and checksum verification.
# Frequently Asked Questions
FAQ SchemaWhy does MetaMask show error 0x5515 repeatedly?
Your Ledger is locking itself before MetaMask finishes sending the transaction. Unlock the device and adjust your auto-lock timer in device settings.
Can I disable the PIN requirement on Ledger?
No. Hardware wallet security requires a PIN to decrypt the Secure Element storage. Disabling the PIN is not supported by BOLOS.
Does error 0x5515 mean my transaction was rejected?
No. The transaction was never sent to the device for signing because the device was locked. No gas was consumed and no transaction was broadcast.