Farebot incompatible with recent mfocGUI keyfiles about farebot HOT 2 CLOSED

I guess the file you are referring to is a file prefixed by a 'T' (i.e. Taxxxxxxxx.dump). If you get all the keys, this file will be renamed and the success/failure indications will be removed from the file by mfocGUI.

Farebot wants to read everything on the card so you'll need keys for all of the 40 sectors (not 100% true, but just bare with me here), so of course Farebot expects all the keys to be present in the key file and not just 'some of them'.

If this is not the case, please enlighten me, because I'm not aware of any newer version than v29.

from farebot.

It's been a long time since I experimented and I don't have access to a reader now to check. I remember never getting a successful read using mfocGUI (KVM guest) so reverted to the linux commandline, which is an even bigger mess, because it doesn't output the key-file at all. I had to create the file "manually" by parsing the mfoc logs...

from farebot.