Ducky One 2 Mini PCB Not Working

[Boolaahh]

Hey all, new to this community so sorry if I am posting with incorrect etiquette for any reason (if I am please let me know!). But recently I got some cream switches that I lubed with 205g0 and filmed with kebo films. I desoldered my one 2 mini and soldered on the new switches. However, the entire keyboard doesn't work at all.

After desoldering the board, I tried to test the pcb by plugging it in and shorting the connections with tweezers before I put anything back in. And even at this point nothing seemed to work. None of the pads I connected with tweezers worked at all. But since I had to leave (my friends house) I ended up soldering everything back in before I left anyways.

Now I am assuming its the desoldering that ruined something on the pcb but I am at a loss as to what that might be. Is there a pad I destroyed? If so would it do enough damage to make it so that nothing works on the pcb? The only indication of life on the pcb is that when I plug it in the caps lock and number 2 key light up like they used to when you plug in the keyboard, then nothing. After that, pressing anything doesn't work. Currently I am just using a replacement keyboard but does anyone have any idea what the possible cause of this issue might be? I can see if I am able to post a picture later of the pcb after soldering everything.

I desoldered using a normal 40W soldering iron I picked up from the store that worked fine when I did the same kinda mod to my old corsair as a test bench. On the corsair (tested on corsair before I did anything to the ducky), everything went fine and the new switches worked fine. But on my ducky, nothing works now. Again I apologize if it is kind of a wall of text and the format isn't the best.

[suicidal_orange]

A polite and detailed question, nothing wrong with that

In theory it would only take about 12 lifted pads to kill all the keys, but in practice if you did a whole other board with no problems I see no way you were that unlucky this time.

Can we clarify 'not working' please?  What happens when you plug it in - does the computer see a keyboard (weird) or come up with an error (possible ESD damaged controller) or nothing (USB socket data connection damaged)?  Does the Caps Lock LED work if you toggle it on another board?

[Boolaahh]

When I plug it in, the computer does not make the windows notification sound that it usually does when you plug in something like a mouse or keyboard, the caps lock key also doesn't light up if I use a different keyboard to press caps. The only thing that it does when plugged in, after a moment, is flash the caps lock and the number 2 key twice and then nothing after that. So possibly the USB socket is damaged? Also just to clarify, the corsair that I tested first I only did about 12 switches, 4 in each row and they all worked without an issue.

[suicidal_orange]

Hmm, two flashes.  One would be it reacting to power then waiting for something but the second suggests it's not that.

Not sure it will work but you could try 'updating' the firmware.

[Boolaahh]

I have tried, it does not respond to the updater. The updater doesn't detect there is a ducky keyboard plugged in.

[suicidal_orange]

What about resetting it, apparently that's done by holding left and right Windows keys.

[Boolaahh]

I reset the board and that seems to have reset to profile 1 and the standard rgb mode. So now all the lights are lighting up but still none of the keys are working themselves. I tried on a keyboard tester and no luck on any keys, just seems that the board has reset to the default rgb wave color profile but it did work, so the win keys did function, just nothing usable on windows. Now when I plug it in, caps lock and the number 1 (not 2) flashes once and then the rgb wave starts, so I guess the 2 lighting up before was my main color profile with rgb off. Thanks for the help so far, I'm heading into work but will definitely be looking at this post while I am there to see what else I can try when I get home.

[Boolaahh]

Ah quick update, ended up fixing the issue and the board now works

[suicidal_orange]

That's great, how did you fix it?  Will help the next person with the same problem

[Boolaahh]

I did a bunch of things to test out what the problem might be.

Basically me and my buddy tried to use his linux machine to determine if the keyboard is having trouble communicating with the OS which is what I suspected, we realized that when we plug it in, there is no change in the controllers that were connected. We tried a bunch of things like updating firmware and stuff to try and fix it. But what ended up working was changing DIP Switch 3 to ON which defines a vendor ID for the board. Once we did that, windows detected the ducky board and installed drivers and we were able to install proper firmware and it worked!