Limited Unicode Characters

[MBHD-Woes]

I am attempting to create a token list to run and produce the same results as these posts from bitcointalk https://bitcointalk.org/index.php?topic=5307795.0 (Key parts of the conversation down below).

When using the %U token it says it is supposed to use all 65,535 Unicode characters.
%U - a single Unicode character (All Unicode characters up to 65,535)

There may be something simple I am missing but testing with just the %U token in the tokens file stops at about 162 entries on my linux system and does not complete the --listpass command. On my windows system it runs the same thing runs way further, but encounters an error of the following after 55297 entries:

Interupted after generating 55297 passwords
Traceback (most recent call last):
File "C:.......\btcrecover-master\btcrecover.py", line 39, in
(password_found, not_found_msg) = btcrpass.main()
File "C:...........\btcrecover-master\btcrecover\btcrpass.py", line 8809, in main
print(password[0])
UnicodeEncodeError: 'utf-8' codec can't encode character '\ud800' in position 0: surrogates not allowed

This is a Multibit HD version 0.5.1 wallet I am going to be working with. I believe it has the password bug with the UTF16 BE issue. I know what the original password is supposed to be, but if like in the description below any characters became ༀ, Ā, ƀ ∀ etc etc I would like to have it attempt replacing characters of any type. Any guidance is apprectiated.

---

[Re: The MASSIVE Negligence of Multibit - Corrupt Wallets]
Just out of curiosity... how did you find the "working" password? Did you have a bruteforce script running that was trying all sorts of unicode characters in addition to the standard aA-zZ0-9 + "specials"? Huh

Or were the unicode characters "accented" characters like you'd find in french and other european languages? like à etc?

---

[Re: The MASSIVE Negligence of Multibit - Corrupt Wallets]
I did run bruteforce scripts several times at the beginning as it was a quick and easy way to get started.
Then, based on my friend's guesses of potential passwords he could have used, I tried many variations using dedicated machines with GPUs.
The unicode characters were not the kind you can find on any keyboard in any language. A real pain in the nose.
We had to be very creative coming up with new ideas for variations because of that. The positive aspect is that all these rules are coded now and I can run them anytime. The recovery potential is much higher when the owner has a basic idea of the password(s) he could have used at the time.

[MBHD-Woes]

So I am reading on issue 22 of the Gurnec version of this script and found in their comments mention of some makefile?

gurnec#22
"I have used the makefile file to add Unicode support. But when I run the btcrecoveru.py file I still get errors because the character ï is not recognized. below is the snipper of the CMD."

Does the equivalent of this step exist in this version? I cannot seem to locate it if it does.