Right now, I decided to specify all of my keyboard characters with the token below:
%0,9[aAbBcCdDeEfFgGhHiIjJkKlLmMnNñÑoOpPqQrRsStTuUvVwWxXyYzZ0123456789ºª\!|"@·#$~%%€&¬/()=¿?'¡`+^*[´¨{}Çç,;.:-_ ]
Because I must not have more than 9 characters... but i got this error
Starting btcrecover 0.17.10 on Python 2.7.17 64-bit, 16-bit unicodes, 32-bit ints
btcrecover.py: notice: use --android-pin to recover the spending PIN of
a Bitcoin Wallet for Android/BlackBerry backup (instead of the backup password)
btcrecover.py: error: on line 1: invalid wildcard (%) syntax (use %% to escape a %)
i saved the file as utf-8 and included --utf8 on comand
Yes, you only specify %% when you a creating a "single" char token... when you're specifying chars in [...] format... you just use a single %. I've just tested it... and created the following token file:
%0,3[ab%]
And then tested using:
btcrecover.py --tokenlist myTokens.txt --listpass
It output:
a
b
%
aa
ab
a%
ba
bb
b%
%a
%b
%%
aaa
aab
aa%
aba
abb
ab%
a%a
a%b
a%%
baa
bab
ba%
bba
bbb
bb%
b%a
b%b
b%%
%aa
%ab
%a%
%ba
%bb
%b%
%%a
%%b
%%%
In addition to that... there is a weird character just before your final "]" which is actually what is causing your error... you need to delete that and the extra %... so your token file should looks something like this:
%0,9[aAbBcCdDeEfFgGhHiIjJkKlLmMnNñÑoOpPqQrRsStTuUvVwWxXyYzZ0123456789ºª\!|"@·#$~%€&¬/()=¿?'¡`+^*[´¨{}Çç,;.:-_]
The next problen will be when i would solved the error, it could take weeks, months, years¿? for %0,9 characters
it is crazy, i have read about doing it on amazon web services, although I have to research about it, I think it could be more complicated than download python and following tutorials...
What do you think?
Yes... a 9 character password, with that many special chars will take a LONG time to test... With 104 possible characters, it's something ridiculous like 1,423,311,812,421,484,500 possible combinations just for the 9 character passwords... then you have the 8 char passwords, 7 chars, 6 chars etc etc. All up, (with my bad maths) it is something like 1,437,130,373,707,129,900 combinations
If you can check
1,000,000,000 passwords/second... You would need: ~1437130373.73 seconds to check them all...
= ~23952172.9 minutes
= ~399202.9 hours
= ~16633.5 days
= ~45.6 years
You might be better off trying to exclude some characters which you're fairly sure you would not have used to reduce the total search space to a more reasonable amount.
You can also try and do it using Amazon Web Services, but the costs can get prohibitive... so unless you have a significant amount of money in this wallet, that might not be the most cost effective way of doing it. Again, talking to wallet recovery experts who already have the equipment and code setup and ready to go might be a better option.
