btcrecover
btcrecover copied to clipboard
Can't Crack Old Wallet Spending Pin Android
Okay so my original backup of my wallet is dated 2017-02-27 although I think I made this back-up some time in February 2017 because at the time I just bought my first Bitcoin (I know form my transaction records on my exchange account). So I assume that date is when I downloaded the app, which I did do fairly early before purchasing my first Bitcoin.
I bought a small amount of BTC and sent it from my exchange wallet to the wallet on my phone. When I tried to send it out of my android wallet it told me I needed to input a spending pin. I didn't even know I had set one. Then I made a backup of the wallet and wiped the app, only to forget my backup key. (all happened around February time)
Fortunately, yesterday I remembered that backup key. I updated the app and restored the wallet on my phone (synchronized from like 16 months). The spending key is still there so I went on Google and found btcrecover. I made another backup, with another password and ran that through btcrecover for the spending pin.
I ran btcrecover to search for 1-6 digits (%1,6d in the tokenlist file). Password possibilities where exhausted and I doubt I set a PIN of more than 6 digits. The whole process took about 2 hours 20 min. Now I'm halfway running a 7 digit recovery (10 hours spent) but nothing so far. However I read something about less key stretching depending on your app version or something... Also p=4096 (I don't know what that means) while others' have their p=65536.
Now my question is, is it just that my PIN is definitely not 1-6 digits or is there some other factor preventing this whole PIN recovery process from being effective?
Your help would be really appreciated. Thanks in advance.
I guess by now you are through with the 7 digit recovery and I hope you have found your pin. I just created a new issue #169 . Please check if you can assist in anyway because you seem to have gotten it right. Thanks!
Unfortunately, I haven't yet. Cleared all 7 digit combinations and no pin. It might be 8 because on the app, once you type 8 digits the password is described as 'strong'. So I might have been taunted into making 8 digits. But the problem I'm stuck with is that it counts the combinations, then freezes at 22 300 000. The total amount of combinations it should reach is 100 000 000 000 combinations.
@moglimax you need to run the script with:
--no-eta --no-dupchecks
then it won't get killed for whatever resource ran out counting.
@elkiwi hey man. thanks for the tip. I totally forgot about this thread and I actually never tried your suggestion yet. I'm going to try it and I'll get back to you. Thanks.