Unprogrammed key?

[noteknix]

I have 2 Solo-A keys both do not work. The first key was from the original kickstarter and was working, then seemed to stop. The latter only arrived today and as with the first one, Windows simply sees it as STM32Bootloader.

Try using it as 2FA with Google, not detected, try using DiceKeys on a Mac, no device detected. The original key did still go into program mode with the button pressed on insertion, that's now stopped, so it's possible I've bricked it or changed it to a Secure version, either way, Win11 just says STM32 Bootloader in device manager with either key inserted. The newer key does nothing when inserted with the button depressed or otherwise. Solo Python is installed and detects neither key when using solo ls, just says ::SOLOS. Wink doesn't work either.

[noteknix]

With a bit of research, I now have signs of life in both keys. Plug in and I get a pulsing green LED, press the button, blue, but that's my lot. Solo ls gives me 205937A0324B: Solo 4.1.5 so I seem to have firmware? But insert the key with the button pressed I still get a pulsing green LED and any solo command says no DFU found. Suggestions?

[jolo1581]

Maybe you should try to Update your solo.

[noteknix]

Yes, now returns the USB device ID and Fido2 device. Which puts me sort of back to square 1, but at least both now have a steady green LED.

…

On 29 Dec 2021, at 18:36, Jan A. ***@***.***> wrote: Did you use solo phython? Plug in solo and type solo ls This should list all connected solo. — Reply to this email directly, view it on GitHub <#592 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXAS35754M26MRMAEXJHU3TUTNILNANCNFSM5KTF7YGA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.

[jolo1581]

Maybe a Win 11 problem?
Do you have any other system to test the keys?

Win 10 or Linux?

[noteknix]

Mac, Win10, Win11 and Linux. :-) The Mac with Solo installed also displays the same results. Might be time to try on Linux.

…

On 29 Dec 2021, at 18:46, Jan A. ***@***.***> wrote: Maybe a Win 11 problem? Do you have any other system to test the keys? Win 10 or Linux? — Reply to this email directly, view it on GitHub <#592 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXAS354LDHEMOVDM7DL3BRLUTNJO5ANCNFSM5KTF7YGA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.

[noteknix]

More work and I have a pair of working keys, except neither are recognised by the Solokeys app. Solo version says both are Hacker firmware, so I assume I should be able to use Dicekeys?

[msiqx9]

So far I have had to programme 2 blank keys and they both appear as "Hacker" in the Solokeys Windows app even though I used the regular secure firmware. Both work fine...