Drop Alt Not Resetting Properly, cant rewrite firmware
I was just trying to write a new firmware to a custom purple colorscheme on my Drop Alt, and I can get to the phase where CMD is looking for the device, but after pressing Fn B or using a paperclip to reset the keyboard, it never turns back on. It goes to blinking yellow, then solid yellow, and gets stuck there. As far as I know this is using the default firmware that came with the board a few days ago.
If I unplug it from the USB cable and plug it back in, it goes back to normal, but the CMD eventually times out and says it could not find the device.
In all the videos I've watched, the keyboard comes right back up a few seconds after the reset. Even without the software to flash it running, the keyboard just blinks twice and gets stuck on the solid yellow light after the reset.
Why doesn't a keyboard this expensive have proper companion software to handle this kind of stuff? I can understand they wanted to engineer it so the keyboard held the user's data rather than a PC side software controller, but cant a keyboard like this also have a software suite to make the customizations and installation easier? Running around in CMD, powershell, and google for 2 hours doesn't seem very user friendly to me.
UPDATE: Response to inquiry from Drop staff:
"Thank you for your patience while I waited on a response back. I was informed It's the same device ID mismatch. We are working to release an updated mdloader to address this. If you are comfortable with some very basic coding, you can download the source code, make the edits, and recompile the binary. If not, you'll have to sit tight for an update."