Ledger Error 0x6e00: CLA_NOT_SUPPORTED Class Mismatch Fix
Ledger status word 0x6e00 indicates "CLA_NOT_SUPPORTED" (Class Not Supported). This error occurs when the Class byte (`CLA`) in an incoming APDU packet does not match the protocol class expected by the Ledger operating system. The most common cause is attempting to communicate with a Ledger while it is sitting on the home screen or locked with a PIN, where the host sends application-specific commands that BOLOS rejects.
# Root Cause & Technical Architecture
The first byte of every APDU frame is the Class byte (`CLA`), defining the instruction category. For Ledger apps, Ethereum uses `0xE0`, Bitcoin uses `0xE0` or `0xF0`, and BOLOS OS commands use `0xB0`. If a web3 client transmits an Ethereum payload (`CLA = 0xE0`) while the device is in the BOLOS dashboard (which only accepts `0xB0`), the device returns `0x6e00`. It also occurs when connecting through outdated bridge wrappers that send generic ISO classes (`0x00`).
# 4-Step Actionable Diagnostic Protocol
Step-by-Step ResolutionUnlock Ledger and Open Required Coin Applet
Ensure the device is unlocked and the target application (e.g. Ethereum) is actively open on the screen before initiating any wallet connection in the browser.
Terminate Background Ledger Live Processes
Close Ledger Live completely. Ledger Live continuously polls the device using OS-level `CLA 0xB0` commands, colliding with browser WebHID sessions.
Verify Browser WebHID Permissions
Navigate to chrome://settings/content/hidDevices in Chrome/Brave and remove stale Ledger permissions, then re-authorize the device on the dApp page.
Check Extension Transport Protocol Mode
In MetaMask or Rabby settings, toggle the hardware connection transport from "Ledger Live" to "WebHID" to avoid legacy bridge framing discrepancies.
# Diagnostic Verification Code / Command
textLedger CLA Byte Protocol Mapping:
0xB0: BOLOS Operating System / Hardware Dashboard
0xE0: Ethereum / EVM Standard Application
0xD0: Solana Standard Application
0xF0: Bitcoin / UTXO Applet
Error Scenario:
Host Sends: [CLA: 0xE0, INS: 0x02] (Get Eth Address)
Device State: Dashboard (Only responds to CLA: 0xB0)
Device Returns: [SW1: 0x6E, SW2: 0x00] -> CLA_NOT_SUPPORTEDLaunch 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 SchemaWhat does 0x6e00 mean in plain English?
It means the Ledger received a command meant for a specific coin app, but the device is currently on the home screen or running a different app.
How do I resolve 0x6e00 on Solana with Phantom?
Open the Solana app on your Ledger before opening Phantom or clicking connect, and verify that blind signing is enabled in the Solana app settings.
Why does closing Ledger Live fix 0x6e00?
Ledger Live communicates with the device dashboard using different class bytes. If it holds an open USB handle, browser requests fail with 0x6e00.