Solo key seem dead after received

[Willena]

I've been redirected here after a mail i sent to [email protected]
I've just received my Solo v2 hacker (USBC) ordered from the Kickstarter campaign a while back.

Immediately after received it, I tried it as I would normally use it.

• Register on one device (Windows PC)
• Login on the same device (Windows PC)
• Login on other devices (MacBook, Phone using NFC)

It worked well for registering, login on Windows and mac. When I tried using NFC on my phone, it failed (something saying the transaction was unexpectedly finished). When I retried, nothing happens, the key seems dead.
When I put it back in the Windows PC, it complains now about being able to retrieve the USB descriptors from the device.

One thing that is worth being added:
When I plugged the key in my PC or Mac, for the first time, the LEDs lighten up.
When I plugged the key in the PC after the NFC test (when i have problems with the USB descriptors) the leds did light up at all ?

Any ideas on what could have happened ?
Could it be a manufacturing issue ?
Should the key be replaced, if yes, how do I proceed ?

Any help would be great, thank you.

[nickray]

To me this sounds like NFC somehow fried the device (although I've not heard of such a thing). Have asked customer support to revisit your email.

[Willena]

Thanks for your message.
This might imply that some devices / phones can deliver too much current or voltage through NFC ? This also means that hardware changes may be required...
For reference, I have a OnePlus 6T

[ullgren]

@nickray Any more details on this I have a similar experience. Tested the NFC on one of my Solo V2 and after that the led does not light up at all when plugging it into the laptop. Worked just fine before that.

[iamareuben]

This seems to have happened to me too. Emailed support and they initially got back to me, but then radio silence for the last month or so. Never actually had it working.

[ullgren]

I tested the same scenario with my Solo V2 Hacker and there is no problems after using the NFC.
That is with the Solo V2 Hacker I can use the NFC to authenticate, then use the same key on my computer through USB.

The Solo V2 standard is still bust. Digging deeper I did found some logs in the kernel log, however I'm not very knowledgeable on debugging USB to say if it is good or bad :-) However if anyone feels like they want to put in some effort to help debug I'm more than happy to run commands and send the output.

[blackcobra1973]

Seems to be the same here, all keys I received initialized correctly, and worked correctly. After trying some NFC stuff one key does not work anymore. In my case is an Solo V2 LE USB-C, my other normal Solo V2 USB-C is still working.

When I put my LE USB-C key in Windows the OS complaints about malfunctioning USB device. Seems this key is broken, I can also not add it anymore to for example Github after removal of the key and try to re-add. None of my other keys have this issue. So it is clear I have a broken Solo V2 LE USB-C how can I get it replaced ?

[ullgren]

I emailed support at [email protected] and got it sorted out.
Some initial delay in the response but it was sorted out very quickly after that.