Help recovering Bitcoin from old Json wallet? (blockchain info android wallet)

[jimgittum]

I found an old wallet I had on an android tablet from 2014 - it is in a JSON format and I do have the password for it.

This was using the old Blockchain.Info android app from around 2014 I believe.  I tried sending coins out from the app on the tablet but it seems to never broadcast to the blockchain.  Probably because it's a 6 year old app with outdated code.  I can't update the app because I no longer have access to the e-mail address from back in 2014 and I am afraid if I re-download the app with another e-mail it will delete my wallet. 

So I used the backup feature to backup the wallet in JSON format.

So what can I do with this JSON file?  I see blockchain.com let's you import them, but my worry is I no longer have access to my old e-mail from 2014 and I am not sure if I had an e-mail tied to the wallet.  I don't remember if those old Blockchain wallets are tied to e-mail addresses/logins or if its just a standalone phone wallet.

So my worry is if I try to recover on Blockchain.com - it will trigger some kind of 2FA from the wallet and my funds will be locked or something.

Any ideas on how to proceed with this?

[1714943860]

1714943860

[1714943860]

1714943860

[NotATether]

Since it's a JSON file you can transfer it to your computer and inspect it in a text editor to see what keys there are. Maybe there is a JSON key for the private keys or seed phrase.

If you have Python, which all Mac and Linux systems have, you can make it read the JSON file and print the keys so we can see them, like this:

Code:

import json

with open('json-file.json') as f:
    j = json.load(f)
    for key in j.keys():
        print(key)  # change to   print key    if you have Python 2 like Mac has it.

Knowing which keys are in the wallet will help us give you better advice without revealing any of the sensitive information inside the wallet.

[OmegaStarScream]

Have you tried running their decryption tool? This should work: https://github.com/blockchain/my-wallet-backup-decryption-tool/releases

Download the my-wallet-backup-decrypt-win64.zip (if you're on windows) go offline, unzip it, and then run the executable file.

Once you manage to get the private keys, install Electrum and sweep them there.

If the above solution doesn't work for you, and you're willing to pay a 20% fee, you can reach out to WalletRecoveryServices. It shouldn't be difficult for them to recover the wallet since you already know the password.

[The Cryptovator]

Here is the guide on how to decrypt your JSON file, [GUIDE] Offline Access to Blockchain Wallet (Exporting Keys). Hope it would help you to recover your funds. Just follow what is suggested by @OmegaStarScream and use the above guide. Make sure again you have multiple copies of your JSON file to avoid any harm.

By the way, I am wondering if you have a JSON file and password then why you need email verification for login? Are you sure your wallet is encrypted with the password or are you talking about a login password? Login password and encrypted password aren't the same. But you may try it. If you recover your wallet by seed phrase then a new wallet id will create with your old funds, so the same thing should happen with the JSON file as well. Since you backed up your file, at least you may try login via JSON file.

Warning! Don't fall into a scam if someone PM you to recover your wallet. Since you have access to your wallet file, so just stay calm and discuss here publicly. Don't hand over your wallet file to any scammers. Your fund is recoverable by the way.

[bitmover]

So what can I do with this JSON file?  I see blockchain.com let's you import them, but my worry is I no longer have access to my old e-mail from 2014 and I am not sure if I had an e-mail tied to the wallet.  I don't remember if those old Blockchain wallets are tied to e-mail addresses/logins or if its just a standalone phone wallet.

Maybe a faster and easier approach to NotATether suggestion, is to just open the json file in a text editor.

You can just open the .json with any TXT editor (such as notepad) and look inside it. Try to find private keys, keys, etc....

You can make a copy and rename the file to .txt. It will open in any text editor or even in your firefox/chrome browser.

[nc50lc]

Maybe a faster and easier approach to NotATether suggestion, is to just open the json file in a text editor.

It's no use, the contents are human-readable but the payload that contains the keys is encrypted.
The backup file provided by old blockchain.info is actually "wallet.aes.json" with "aes" indicating that the payload is encrypted.

@jimgittum if you were to use the suggested "decryption tool" either the offline (recommended) or the html version,
be informed that the private key will be exported in plain BASE58 format without a checksum, flag or network bytes.
That format isn't supported by almost all wallets and should be encoded into WIF (Wallet Import Format) first before it can be imported to Electrum.
Find a tool that can convert it.

The forked brainwallet tool (guthub repo link) has a converter tool but it'll only convert it uncompressed WIF,
Although you can get the compressed version in the Generator tab when used it as input.
Here's how to convert using that tool (use an Air-Gap PC same as the decryption tool):

• Download (and audit) the source code, extract it, launch the HTML file using your browser.
• In the tool, go to 'Convert' tab, tick "Base58" in 'Source Encoding', tick "Hex" in 'Convert To'; then paste your base58 prv key.
• Copy the hex encoded private key, then go to 'Generator' tab, in 'Get Address From', tick "Secret Exponent"; then paste the copied hex prvKey in 'Secret Exponent'.
• In 'Point  Conversion', see which option will produce the correct address ('Compressed' or 'Uncompressed').
• To view the WIF private key, Click "Toggle Key".

If it's quite new, you can also try to import each of your HD wallets' "xprv" (extended private key) from "View JSON" after decrypting the wallet.
In Electrum, import it in new wallet option: "Standard->Use a master key".