Closed whosnorman closed 1 year ago
Also I should've opened this in the cli repo. Figured it out, was trying to push a bundled .hex that included a bootloader using the bootloader instead of dfu. Wound up pushing an unbundled .hex using the bootloader instead!
Heyo, just got a hacker solokey that was at version "3.1.2 unlocked" and was able to run
solo1 key update
to get it to version "4.1.5 unlocked".However when I try to upload custom firmware with
solo1 program bootloader teal-led-all.hex
it results in two CTAP errors. I've also tried putting it into bootloader mode manually by holding down the button while plugging in. Both ways result in the same errors when trying to push custom firmware.I'm running:
I've also tried running it with fido2==0.9.1 and the current production solo1 and I get the same errors.
Error logs:
I've tried programming custom firmware and regular firmware to two different hacker solokeys and a hacker somu and always get NOT_ALLOWED once they're in bootloader mode.