Click to view our Accessibility Statement or contact us with accessibility-related questions
Showing 1 of 1864 conversations about:
weston990
51
Dec 23, 2016
bookmark_border
Apparently my fully assembled Whitefox is having some really weird issues. Keyboard keeps resetting itself then windows doesn't actually detect it or something and I can't type ... no clue what's happening there or if i'm just hitting some macro I don't know of by accident.
Also I have the stabilizer issue that was mentioned a while ago in a update we all received. My R2 Left Shift is sticking sometimes, and when it doesn't stick it just feels god awful to touch. Unlike every other stabilized key on the board ... I don't even know if I'm getting the replacement plate from the manufacturing issues but that would mean I just paid over 200 to fix a problem that shouldn't have existed in the first place. Not entirely disappointed, but wtf am I supposed to do ...
Just a guess, but on a personal build I used costar stabilizers, unless they're lubed they tend to stick more often and feel like shit. These two stabilizers on the left shift, are not lubed at all, but the other stabilized keys are. I can probably lube them but that means I have to buy some. Small input on what is probably just another classic Massdrop QC problem.
Edit: To attempt to address the issue with the keyboard randomly not being detected by windows, I checked the Device Manager and it's showing as Unknown USB Device (Device Descriptor Request Failed). It's now in a unflashable state even after hitting the flash button on the pcb. Zadig is showing that there isn't even a Driver for the usb and fails to install one saying "Resource already exists". I'm at a loss with wtf I'm supposed to do with this broken ass keyboard. And no support is coming from anywhere ...
Edit 2: After plugging and unpluging, I can get it into it's original state, but then randomly windows will again shows it's a unknown usb device. Even after getting the driver to install on Zadig, the Kiibohd DFU Flasher returns a code 74 and doesn't flash anything.
Edit 3: By some miracle I got the driver installed and the layout flashed that I was wanting. But it still hasn't solved this fucking issue with the Usb Unknown shit. I took the case apart and checked the pcb, it's totally fine from everything I can see. Plug it in, no case on, can't get Windows to recognize it. Put the case on, plug it in, it's recognized, then I move the board and BOOM windows no longer recognizes it. It may be a physical thing on the pcb ?? Maybe a bad usb port ?? I tried 2.0 and 3.0 both giving the same results ...
Edit 4: I'm definitely suspecting a "static shock" death somehow, as the board will sometimes be recognized totally fine, but the second I jiggle or move it then it becomes a USB Unknown Device essentially just shutting down. I've been issued a return label to receive a new board, great ... hope no one else has to deal with this shit.
Dec 23, 2016
rrajarajan
18
Oct 23, 2018
bookmark_border
weston990Any luck with this. I had my whitefox working for a few month and I might have goofed up the firmware update a few months ago (I forget the details). Now it is not recognized by Windows and I keep getting the Device Driver Request Failed issue with windows and zadig. I uninstalled the driver etc., but no luck yet in having windows recognized it to reflash the layout.
Oct 23, 2018
weston990
51
Oct 23, 2018
bookmark_border
rrajarajanThat sounds like an unrelated issue to what I was having, sorry. Mine was a hardware malfunction that I eventually got a full refund for from Massdrop.
It does sound like you just need to reflash a different firmware though, maybe start with the stock QMK firmware for the board and work from there.
Oct 23, 2018
rrajarajan
18
Oct 23, 2018
bookmark_border
weston990Unrelated issue - looks like. I am unable to flash the default Whitefox FW and that's my current (big) problem. When I double click the reset button I see the red/orange led inside, but windows doesn't recognize it (with the device driver request failed). And a Zadig install of the driver in this case doesn't help. The keyboard (in flash mode) show up in windows with a USB vendor ID 0x0000 and Prod ID 0x0002 which doesn't seem right. Maybe the bootloader on the keyboard itself is malfunctioning - and I am stumped!
Oct 23, 2018
weston990
51
Oct 23, 2018
bookmark_border
rrajarajanOh jeez yea I'm not entirely sure, any flashing I've done has been from a Unix system to avoid driver issues in Windows. Uh maybe @matt3o can help you out.
Oct 23, 2018
rrajarajan
18
Oct 23, 2018
bookmark_border
weston990I just posted a separate message under the main discussion.
Oct 23, 2018
View Full Discussion
Related Products