CustodyStress
ArchiveSeed phrase unavailable › Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00834

Mycelium on Encrypted Samsung Galaxy Note 4: 0.1 BTC Inaccessible, 6 Password Attempts Remaining

Blocked

Seed phrase could not be located — without it, wallet recovery was not possible.

Case description

The owner stored 0.1 BTC in a Mycelium wallet installed on a Samsung Galaxy Note 4 at a time when Bitcoin's price was materially lower. The device's screen fractured, rendering daily use impractical, so the owner purchased a replacement and set the Note 4 aside without extracting the private key or recording the wallet's seed phrase. No backup of any kind was created or stored separately.

Years passed. As Bitcoin appreciated significantly, the owner returned to the damaged device intending to recover the funds. The phone remained powered on and partially functional despite the screen damage, and the owner could still operate it through remaining tactile controls. However, the device was encrypted at the operating system level.

The owner did not remember the device unlock passphrase and attempted multiple guesses. This triggered a critical limitation in Android's security architecture: encrypted storage permits only a finite number of failed password attempts before triggering an automatic factory reset that irreversibly destroys all data. The owner exhausted most available attempts and reported having approximately 6 guesses remaining before permanent data loss.

Mycelium, as a mobile software wallet, offered no independent recovery path without either the correct device unlock passphrase or a pre-recorded seed phrase. The wallet file existed only on the encrypted device. Unlike hardware wallets or properly architected custody systems, this configuration created an absolute single point of failure that could not be circumvented by technical means once the unlock passphrase was forgotten.

The case illustrates a delayed recognition of custodial discipline. The window for recovery—recording the seed phrase at wallet creation—had closed years prior.

Custody context
Stress conditionSeed phrase unavailable
Custody systemSoftware wallet
OutcomeBlocked
DocumentationPartial
Structural dependencies observed
Single Person KnowledgePassphrase DependencyDevice Specific AccessUndocumented procedure
What this illustrates
Only one person knew how the setup worked — and that person wasn't available. A software wallet stores keys on the device — whether a phone or computer. When the device is lost or the application is uninstalled, access depends entirely on whether a seed phrase was recorded and stored independently. Seed phrase loss is structurally irreversible. Unlike a forgotten password, there is no reset mechanism and no authority that can restore access. The seed phrase is the wallet. The wallet needed a passphrase that nobody could produce. A blocked outcome in this archive means that no path to authorized access was found under the conditions documented.
Why this matters

Why seed phrase loss is structurally irreversible

Seed phrase unavailability is the most decisive failure mode in the archive. Unlike most custody failures — where a workaround, a legal process, or a recovery service offers some path — seed phrase loss eliminates all alternatives. The seed phrase is the master key. There is no institutional backup, no reset process, and no authority that can reconstruct it.

The Bitcoin network was designed this way deliberately. No centralized party holds a copy of private keys. No court order can compel a blockchain to release funds. This design protects against seizure, censorship, and institutional failure. It also means that the holder bears the entire burden of preserving the one credential that cannot be replaced.

Observed cases in this archive show three primary paths to seed phrase loss: the phrase was never recorded at setup (the holder assumed they would remember it or relied on the device alone), the recording was destroyed (fire, flood, degraded paper), and the recording was misplaced or its location forgotten. Each of these is a documentation failure that occurred before any custody stress event.

The distinction between seed loss and passphrase loss matters: seed phrase loss is typically irreversible because the seed phrase is the foundation of everything else. Passphrase loss sometimes allows professional recovery attempts. Nothing recovers a missing seed.

How this category of failure is typically preventable

Seed phrase preservation requires three things: recording at setup, storing the record in a durable and discoverable location, and verifying the record is correct before the original device is relied upon. Cases in this archive that resulted in permanent loss almost universally involved at least one of these steps being skipped.

Read more: Seed Phrase Bitcoin Inheritance →
What happens if a Bitcoin seed phrase is lost?
Loss of the seed phrase with no backup means permanent loss of access to the Bitcoin. The seed phrase is the master key — it generates all private keys for that wallet. Without it, the wallet cannot be restored on any device. There is no central authority, no support process, and no technical substitute. This is structurally irreversible.
Can Bitcoin be recovered without a seed phrase?
Only in narrow circumstances. If the original device is intact with the correct PIN, the wallet may still be accessible through the device. Some wallets allow exporting private keys directly — but only while the wallet is operational. Once the device is lost or the wallet is inaccessible, the seed phrase is the only remaining recovery path. Without it, the Bitcoin is lost.
Is it possible to find a lost seed phrase?
Sometimes. If the holder wrote it down and the paper was misplaced rather than destroyed, it may still exist. Common locations include safes, safety deposit boxes, filing systems, and storage units. Professional searchers and estate specialists can assist in locating documents. If the seed was never written down, or the paper was destroyed, recovery is not possible.
Source
Publicly Reported
Most structurally similar case
Multibit Desktop Wallet: Bitcoin Inaccessible After Platform Closure and File Loss
Seed phrase unavailable · Software wallet Blocked
Related cases
Structural patterns in this case
Recovery attempted, access still blocked
157 cases involve seed phrase unavailable 455 cases involve software wallet View archive statistics →
This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case
← All cases
Framework references
Terms guide
Survived
Access remained possible under the reported conditions.
Constrained
Access remained possible, but only with delay, dependence, or significant difficulty.
Blocked
Access was not possible under the reported conditions.
Indeterminate
There was not enough information to determine the outcome.
Survivability
The degree to which a custody system maintains the possibility of authorized recovery under stress.
Archive inclusion criteria

This archive documents cases where a legitimate owner, heir, or authorized party encountered barriers accessing or recovering Bitcoin due to a failure in the custody arrangement. The central question for inclusion is: did the custody structure fail a legitimate access or recovery attempt?

A case must satisfy all three of the following to be included:

  1. Legitimate access attempt. The person attempting to access or recover the Bitcoin was the owner, a designated heir, an executor, a legal authority, or another party with a legitimate claim — not a thief, attacker, or unauthorized third party.
  2. Custody structure failure. The failure was caused by a property of the custody arrangement — missing credentials, structural dependencies, documentation gaps, knowledge concentration, legal barriers, or institutional constraints — not market conditions, individual-level fraud or theft, or protocol-level issues. Platform-level failures that block legitimate user access are in scope regardless of their cause.
  3. Documentable outcome or access constraint. The case must have a stated or inferable outcome: access blocked, access constrained, access delayed, or access eventually achieved through a recovery path. Cases with entirely unknown outcomes are included only where the structural failure is documented and the constraint is unambiguous.
  • Owner death or incapacity — Bitcoin held in self-custody that becomes inaccessible to heirs or designated parties because credentials, documentation, or operational knowledge were not transferred
  • Passphrase loss — BIP39 passphrase forgotten or unavailable, blocking access to a funded wallet even where the seed phrase is present
  • Seed phrase or wallet backup unavailable — no independent recovery path existed or the backup was destroyed, lost, or never created
  • Device loss without independent backup — hardware wallet, phone, or computer lost or destroyed with no recovery path outside the device
  • Documentation absent or ambiguous — heirs or executors cannot determine that Bitcoin exists, which wallet holds it, or how to access it
  • Knowledge concentration — only one person knew the procedure, passphrase, or access method; that person is dead, incapacitated, or unreachable
  • Multisig quorum failure — a threshold signature arrangement cannot be completed because signers are unavailable, uncooperative, incapacitated, or have lost their keys
  • Legal authority / access mismatch — a court order, probate ruling, or power of attorney establishes legal entitlement but provides no technical path to access
  • Institutional custody barrier — exchange or platform hacks, insolvency, regulatory seizure, or operational failure that caused a access constraint or failure for legitimate users, whether temporary, prolonged, or permanent. The failure of the custodian to remain available or solvent is itself the in-scope event.
  • Forced relocation or geographic constraint — physical access to a device or location required for recovery is blocked by displacement, border restrictions, or political circumstances
  • Coercion — the holder was compelled under threat to transfer Bitcoin or disclose credentials during an access event
  • Hidden asset discovery — heirs or executors locate a wallet or account but cannot access it due to missing credentials or operational knowledge
  • Market losses, investment losses, yield scheme losses, or Ponzi scheme losses
  • Hacks or theft targeting an individual's personal security (phishing, SIM swap, social engineering, malware) where the custody architecture itself did not fail
  • Unauthorized transfers where the holder's custody system was not the cause of the failure
  • Ordinary transaction mistakes — wrong-address sends, fee errors, mistaken amounts
  • Protocol-level failures — cryptographic vulnerabilities, consensus bugs, firmware integrity failures
  • Deliberate burns or tribute burns
  • Cases where the stated loss is unverifiable and no structural custody failure is described

Cases are drawn from public sources including forum posts, news reporting, court documents, academic research, and direct submissions. Each case is reviewed against the inclusion criteria above before publication. Source material is retained and available on request for documented cases.

The archive is observational and descriptive. It does not attempt to document all Bitcoin custody failures — only those meeting the criteria above with sufficient documentation to describe the structural failure and its outcome.