Losing a wallet file is frightening, but the outcome depends almost entirely on one question: do you still have the recovery phrase (seed) that the file was derived from? In most ProKey-related cases the answer is a decisive yes — and that single fact turns a potential disaster into a 20-minute restore.
This guide walks through what a ProKey backup file actually contains, the recovery routes for every realistic scenario, and the offline tools (btcrecover, HashCat, Pywallet, BIP39 utilities) that professionals use. If you are brand new to this topic, the fundamentals are covered in our Crypto Wallet Recovery Guide, which explains BIP39/BIP32 in plain English before you touch any tool.
What Was Actually Inside Your ProKey File?
Before running any recovery software, be clear about what you lost.
| What you lost | Does it hold spendable keys? | Recoverable without it? |
|---|---|---|
| An exported backup/JSON or xpub file | No — these are public-key material | Yes, from your seed phrase |
| A wallet sync/configuration file | No | Yes, from your seed phrase |
| An encrypted wallet file (wallet.dat, keystore JSON) | Yes | Only with the file + password |
| The seed phrase itself | It was the key | Only through partial-memory recovery |
ProKey devices followed the BIP39 standard with a 24-word seed, and standard BIP44 derivation paths (m/44'/0'/0' for Bitcoin, m/44'/60'/0'/0/0 for Ethereum). Because it was standards-compliant, any reputable BIP39-compatible wallet can rebuild your balances — the hardware brand no longer needs to exist.
Key insight: the seed phrase is the wallet. The file was only a convenient copy of it.
Step 1 — Freeze the Situation (Do This First)
- Stop using the affected computer or drive. Deleted files overwrite fast; a forensic undelete is only possible before new writes occur.
- Do not reinstall, format, or "clean up" anything.
- Do not type your seed phrase into any website, chat support, browser extension, or email form — ever. Legitimate recovery never requires it.
- Inventory everything you have: handwritten seed, partial seed, photo of seed, password manager entry, PIN, encrypted backup, email attachment, cloud backup, old phone, old laptop, hardware device itself.
- Work offline from here on. Air-gap the machine you use for recovery where possible.
Scenario A: You Have the Seed Phrase (Most Common Case)
This is the easy path, and it applies to almost every "ProKey file lost" situation.

Restore into a compatible wallet
- Bitcoin: Electrum, Sparrow, BlueWallet, or a hardware wallet with BIP39 import.
- Ethereum / ERC-20: MetaMask ("Import using Secret Recovery Phrase"), MyEtherWallet, Rabby.
- Verify first, offline: use an offline copy of the Ian Coleman BIP39 tool on a machine that has never seen the internet, to confirm the address matches the one you remember.
Check the derivation path if balances look empty
An empty wallet after a correct restore almost always means the wrong derivation path, not a wrong seed. Try, in order:
m/44'/0'/0'(Bitcoin legacy addresses)m/49'/0'/0'(Bitcoin SegWit-compatible, addresses starting with3)m/84'/0'/0'(Native SegWit,bc1)m/44'/60'/0'/0/0(Ethereum / MetaMask default)
Also check account index 0 through 20 — sometimes funds sit in a later account or change address.
If the seed is 12 words and you typed 24 (or vice versa), stop and recheck the word count before assuming the worst.
Scenario B: No Seed, But You Still Have the Wallet File
Here the file itself is the asset, and the obstacle is usually the password that encrypts it.
Step 1 — Preserve an untouched copy
Copy the original file to a working directory and never modify the original. Keep a checksum.
Step 2 — Identify the file type
- Bitcoin Core
wallet.dat— binary Berkeley DB format. - Ethereum keystore JSON (MetaMask / MyEtherWallet / geth) — JSON with
cryptofields. - Electrum wallet file — plain text with an
xprvif unencrypted, or ciphertext if password-protected. - MultiBit / other legacy formats — handled by Pywallet and similar parsers.

Step 3 — Recover the password offline
- btcrecover — the workhorse for
wallet.dat, Electrum, and many other formats. It supports token lists, character sets, typo simulation, and multi-wallet batch attempts. - HashCat — GPU-accelerated cracking for keystore JSON and similar hashes. Recover the hash first, then run a targeted mask or a wordlist with rule mutations.
- Pywallet — useful for inspecting, dumping keys from, or repairing legacy
wallet.datfiles.
Practical crack strategy that actually works:
- Build a personal wordlist from things you would plausibly have used (names, dates, pets, keyboard patterns, old passwords).
- Add mutations: capitalized first letter, trailing
!,123, year suffixes, doubled words. - Only then move to masks or broader dictionaries — GPU time is precious and personal lists crack far faster.
Run everything on an offline machine. Neither btcrecover nor HashCat needs internet access.
Scenario C: Missing Seed and Missing File
Recovery is still sometimes possible if the loss is partial rather than total.
Partial seed phrase recovery
- Write down every word you are confident about, and the positions you are sure of.
- Use the BIP39 wordlist (2048 words) and the built-in checksum to eliminate impossible combinations.
- Tools such as btcrecover's seed-recovery features, Seed Savior, or a short custom Python script with the BIP39 wordlist can iterate unknown positions.
- Order matters. If you know all 24 words but not the order, that is still an enormous search space — but known-position constraints plus checksum validation shrink it dramatically.
File undelete
- Stop all writes to the drive immediately.
- Use a read-only forensic tool (e.g., a bootable Linux USB with PhotoRec/TestDisk) and image the drive before analysis.
- Recover to a different drive, never back onto the source.
Realistic expectations
- 12 unknown words out of 12 on mainnet: not feasible.
- 4–5 unknown words with known positions: feasible with a scripted offline search.

- Encrypted file + forgotten password + no partial hint: usually not feasible; treat it as a cold-storage loss.
Common Mistakes That Destroy Recoveries
- Pasting a seed phrase into a "recovery service" website. This is the single most common cause of permanent theft.
- Assuming a lost file means lost coins. If the seed exists, nothing is lost.
- Restoring, seeing a zero balance, and giving up. Check derivation paths and account indexes first.
- Continuing to use the drive after deletion. Every write reduces the odds of undelete.
- Trusting paid "wallet recovery" services without escrow or proof of capability. Most are either incompetent or predatory.
- Storing the seed digitally in screenshots, cloud notes, or email. That converts a physical-security problem into a data-breach problem.
Prevention: Make This the Last Time
- Steel backup plates for the seed phrase protect against fire and water.
- Two geographically separate copies — never both in the same room.
- SLIP-39 or Shamir-style sharding splits a seed into shares so no single location holds the whole secret.
- Test your backup once. Restore into an empty wallet and confirm the addresses match before you need it.
- Keep an encrypted
wallet.dat/ keystore copy in a separate offline location from the password. - Record the derivation path and word count alongside your backup — future-you will thank present-you.
Summary
| Situation | Best move |
|---|---|
| Seed phrase available, file gone | Restore into Electrum / MetaMask or a hardware wallet; verify derivation path |
| File available, password forgotten | Offline btcrecover or HashCat with a personalized wordlist |
| Seed partially remembered | BIP39 wordlist + checksum-constrained offline search |
| File deleted from a drive | Stop writes, image the drive, undelete to a separate disk |
| Nothing at all | Focus on prevention for future wallets |
A lost ProKey file is rarely the end of the story. In the overwhelming majority of cases the seed phrase — not the file — is what controls the funds, and a careful, offline, standards-based restore brings everything back. Work slowly, keep the machine disconnected, and take a few minutes to understand the Crypto Wallet Recovery Guide concepts before running any tool. Caution and patience recover more wallets than raw computing power ever will.