that bug isn't really relevant. it's about a test lab setup.
that error happens when a firmware version was installed with key versions older than whatever the device saw most recently. so if the user installed some unofficial/incompatible firmware into the device that rolled the keys forward, and then tried to install older versions again, you'd prob hit that screen. if i'm reading the fwver=0x000a0002 correctly, something updated the key version to 10 which we haven't done on clapper (it's sitting at version 5 currently).
if i had to guess, they somehow booted a glimmer image (which uses the same root key, but has firmware version set to 10) on that clapper device which got it into this bad state. if that is the case, then i don't think any recovery image will help. you'd have to remove the write protect, manually reset the key versions, and then re-enable the write protect.
-mike