Bitcoin Forum
May 05, 2024, 06:10:14 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Got my recovery seed for android bitcoin wallet, but electron cash says 0 BCH  (Read 1079 times)
username_number (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 17, 2017, 10:29:52 PM
Last edit: November 17, 2017, 10:44:34 PM by username_number
 #1

I had coins in the android wallet (schildbatch) during the time of the fork. I moved the coins and extracted the recovery seed phrase for the wallet using the python script (decrypt_bitcoinj_seed.pyw). the result stated:

Quote
14 non-deterministic keys found. 1 extra mnemonics found. Your mnemonic backup does not back up your entire wallet.

The script produced a 12 word list.

When I entered the 12 word seed phrase in Coinomi the app said there were unrecognized words so I tried in electron cash and I just get an empty wallet with a 0BCH balance.

I tried to use the mnemonic decoder (bip39-standalone.html) with BIP32 deviation path of m/0'/0 and m/0'/1 but none of the addresses that appear are addresses displayed on my phone in the "my receiving addresses". Why am I getting a list of addresses and keys that do not match my phone?

I can't sweep my BCH until I can figure out what's going wrong. Angry Thanks in advance.
1714932614
Hero Member
*
Offline Offline

Posts: 1714932614

View Profile Personal Message (Offline)

Ignore
1714932614
Reply with quote  #2

1714932614
Report to moderator
1714932614
Hero Member
*
Offline Offline

Posts: 1714932614

View Profile Personal Message (Offline)

Ignore
1714932614
Reply with quote  #2

1714932614
Report to moderator
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714932614
Hero Member
*
Offline Offline

Posts: 1714932614

View Profile Personal Message (Offline)

Ignore
1714932614
Reply with quote  #2

1714932614
Report to moderator
1714932614
Hero Member
*
Offline Offline

Posts: 1714932614

View Profile Personal Message (Offline)

Ignore
1714932614
Reply with quote  #2

1714932614
Report to moderator
1714932614
Hero Member
*
Offline Offline

Posts: 1714932614

View Profile Personal Message (Offline)

Ignore
1714932614
Reply with quote  #2

1714932614
Report to moderator
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
November 18, 2017, 12:45:52 AM
 #2

The text you have quoted is probably the reason. The coins are probably on the private keys of the non hierarchical deterministic part. You'll have to use different software to get out what you want (as the wallet file is linked to bitcoin possibly try there to get the keys but I wouldn't be certain on that).
HCP
Legendary
*
Offline Offline

Activity: 2086
Merit: 4316

<insert witty quote here>


View Profile
November 18, 2017, 01:18:03 AM
 #3

I've honestly not seen that message from decrypt_bitcoinj_seed before... but it sounds like your BTC might have been on imported keys? and NOT on addresses that were generated from the HD wallet seed mnemonic? Huh

It should be possible to dump the wallet file out, but it would require some Python hacking... I have a version of decrypt_bitcoinj_seed which just dumps the decrypted/parsed wallet data to a text file... it may or may not have encrypted keys in it tho... which requires more work Wink


As for why your addresses on the phone are different from the BIP39 tool... I can only theorise that the addresses you are seeing are not being generated from your seed phrase? Huh Those are definitely the correct derivation paths... I've just tested it with my phone.

█████████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████
█████████████████████████
.
BC.GAME
▄▄░░░▄▀▀▄████████
▄▄▄
██████████████
█████░░▄▄▄▄████████
▄▄▄▄▄▄▄▄▄██▄██████▄▄▄▄████
▄███▄█▄▄██████████▄████▄████
███████████████████████████▀███
▀████▄██▄██▄░░░░▄████████████
▀▀▀█████▄▄▄███████████▀██
███████████████████▀██
███████████████████▄██
▄███████████████████▄██
█████████████████████▀██
██████████████████████▄
.
..CASINO....SPORTS....RACING..
█░░░░░░█░░░░░░█
▀███▀░░▀███▀░░▀███▀
▀░▀░░░░▀░▀░░░░▀░▀
░░░░░░░░░░░░
▀██████████
░░░░░███░░░░
░░█░░░███▄█░░░
░░██▌░░███░▀░░██▌
░█░██░░███░░░█░██
░█▀▀▀█▌░███░░█▀▀▀█▌
▄█▄░░░██▄███▄█▄░░▄██▄
▄███▄
░░░░▀██▄▀


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
username_number (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 24, 2017, 07:10:14 PM
 #4

I've honestly not seen that message from decrypt_bitcoinj_seed before... but it sounds like your BTC might have been on imported keys? and NOT on addresses that were generated from the HD wallet seed mnemonic? Huh

It should be possible to dump the wallet file out, but it would require some Python hacking... I have a version of decrypt_bitcoinj_seed which just dumps the decrypted/parsed wallet data to a text file... it may or may not have encrypted keys in it tho... which requires more work Wink


As for why your addresses on the phone are different from the BIP39 tool... I can only theorise that the addresses you are seeing are not being generated from your seed phrase? Huh Those are definitely the correct derivation paths... I've just tested it with my phone.

Do you have a copy of the script I could try on this wallet? There were no imported keys for this wallet.
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
November 24, 2017, 07:55:31 PM
 #5

I've honestly not seen that message from decrypt_bitcoinj_seed before... but it sounds like your BTC might have been on imported keys? and NOT on addresses that were generated from the HD wallet seed mnemonic? Huh

It should be possible to dump the wallet file out, but it would require some Python hacking... I have a version of decrypt_bitcoinj_seed which just dumps the decrypted/parsed wallet data to a text file... it may or may not have encrypted keys in it tho... which requires more work Wink


As for why your addresses on the phone are different from the BIP39 tool... I can only theorise that the addresses you are seeing are not being generated from your seed phrase? Huh Those are definitely the correct derivation paths... I've just tested it with my phone.

Do you have a copy of the script I could try on this wallet? There were no imported keys for this wallet.

Not that I have tried it ever but if a wallet file can be decrypted by a bitcoinj wallet decrypter, you might have luck using a version of bitcoinj. That being said, if HCP has their script, it'll probably function better.
HCP
Legendary
*
Offline Offline

Activity: 2086
Merit: 4316

<insert witty quote here>


View Profile
November 24, 2017, 11:22:12 PM
 #6

Do you have a copy of the script I could try on this wallet? There were no imported keys for this wallet.
You can try using this: https://pastebin.com/rEmF1F1r

Just save it as a .pyw file and put it in the same location as the decrypt_bitcoinj_seed.pyw script... then double it and run it like you did with decrypt_bitcoinj_seed... After it completes, you should get a "parsed_wallet.txt" file generated in the same directory.

If you open it, you should see all your encrypted keys etc:
Code:
key {
  type: DETERMINISTIC_MNEMONIC
  creation_timestamp: 1510100577000
  encrypted_data {
    initialisation_vector: "\033C\\\327\.......................4\372#"
    encrypted_private_key: "ib\313\365\...................0O\266*?\026"
  }
  encrypted_deterministic_seed {
    initialisation_vector: "lC\205\...........37\223"
    encrypted_private_key: ".Kd\3.............4p\307"
  }
}
key {
  type: DETERMINISTIC_KEY
  public_key: "\003^\0028$z..................................024z\006"
  creation_timestamp: 1510100577000
  encrypted_data {
    initialisation_vector: "\3101..................................0\346"
    encrypted_private_key: "N;\227..................................40\307h"
  }
  deterministic_key {
    chain_code: "\236\016e..................................22K\304"
  }
}

I'm guessing, you'll find some "Keys", that have a type that are NOT "DETERMINISTIC_KEY"s....


Also, right at the end of the file you should see the encryption type and parameter used which will be required if you want to attempt to decrypt the keys:
Code:
encryption_type: ENCRYPTED_SCRYPT_AES
encryption_parameters {
  salt: "\301..................25"
  n: 65536
}

█████████████████████████
████▐██▄█████████████████
████▐██████▄▄▄███████████
████▐████▄█████▄▄████████
████▐█████▀▀▀▀▀███▄██████
████▐███▀████████████████
████▐█████████▄█████▌████
████▐██▌█████▀██████▌████
████▐██████████▀████▌████
█████▀███▄█████▄███▀█████
███████▀█████████▀███████
██████████▀███▀██████████
█████████████████████████
.
BC.GAME
▄▄░░░▄▀▀▄████████
▄▄▄
██████████████
█████░░▄▄▄▄████████
▄▄▄▄▄▄▄▄▄██▄██████▄▄▄▄████
▄███▄█▄▄██████████▄████▄████
███████████████████████████▀███
▀████▄██▄██▄░░░░▄████████████
▀▀▀█████▄▄▄███████████▀██
███████████████████▀██
███████████████████▄██
▄███████████████████▄██
█████████████████████▀██
██████████████████████▄
.
..CASINO....SPORTS....RACING..
█░░░░░░█░░░░░░█
▀███▀░░▀███▀░░▀███▀
▀░▀░░░░▀░▀░░░░▀░▀
░░░░░░░░░░░░
▀██████████
░░░░░███░░░░
░░█░░░███▄█░░░
░░██▌░░███░▀░░██▌
░█░██░░███░░░█░██
░█▀▀▀█▌░███░░█▀▀▀█▌
▄█▄░░░██▄███▄█▄░░▄██▄
▄███▄
░░░░▀██▄▀


▄▄████▄▄
▄███▀▀███▄
██████████
▀███▄░▄██▀
▄▄████▄▄░▀█▀▄██▀▄▄████▄▄
▄███▀▀▀████▄▄██▀▄███▀▀███▄
███████▄▄▀▀████▄▄▀▀███████
▀███▄▄███▀░░░▀▀████▄▄▄███▀
▀▀████▀▀████████▀▀████▀▀
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!