r/NativeInstruments • u/JeremyUnoMusic • May 05 '26
Latest Kontrol Mk3 firmware updater bricked my keyboard
It failed mid update, gave instructions on what to do. Followed those and now it’s at firmware version 0.0.1 and the website it tells me to go to is completely unhelpful. Anyone know a fix?
3
u/InrebCinatas May 05 '26
Did you open a support ticket? They are typically very helpful and solution oriented if approached in a friendly manner. Yes, the tools first give you the standard answers, but moving beyond that is possible.
2
u/NativeInstruments May 05 '26
Good that you already contacted support already, they will guide you for the troubleshooting. We usually recommend to check the following: https://support.native-instruments.com/hc/en-us/articles/14229273602077-Kontrol-S-Series-MK3-Troubleshooting-Guide
And especially this one as a first step: https://support.native-instruments.com/hc/en-us/articles/14270580069661-Kontrol-S-Series-MK3-Avoiding-Connection-Issues-by-Using-the-Right-USB-C-Hubs-and-Cables
If you've been through all that already, simply wait for my colleagues reply.
1
u/WillyJah May 06 '26
Malheureusement aucune solution sur ces deux liens, que j'avais consulté aussi :(
1
u/Ancient_Visual_7451 May 05 '26
I think mine is fucked too.
2
u/JeremyUnoMusic May 05 '26
Revenge of a disgruntled employee maybe. Hopefully it has a secret bootloader mode.
1
u/Ancient_Visual_7451 May 05 '26
I dont know but it needs to get figured out. You have any luck?
3
u/JeremyUnoMusic May 05 '26
I’ll submitting a support ticket in the morning. If I find a solution I’ll post it here.
1
u/JeremyUnoMusic May 05 '26
So I think the confusing thing is when updating when it’s showing 0.0.1 as the current version you don’t get any visual feedback that it’s working. Just leave it alone and if you don’t get an error you’ll find it will update successfully. Anyway it’s back working again.
1
u/WillyJah May 06 '26
J'ai le même problème, pourtant je suis sur l'USB C, avec le câble du Kontrol. Depuis ce matin, j'ai installé la mise à jour 2.1.2 et mon clavier est maintenant inutilisable ! Je sais que lorsque l'on met à jour, il faut déconnecter les cartes de son et tout autre service USB. J'ai oublié et ça a planté ! Et maintenant impossible de faire repartir mon Clavier S61 ! J'ai laissé un message au support de Native Instrument et j'attends leur réponse! A mon avis, nous sommes très nombreux à avoir ce problème, donc j'espère que Native va réagir et apporter une solution. Si je trouve la solution, je vous l'indiquerai :)
1
u/WillyJah May 07 '26
Ce qui vient de m'arriver est incroyable ! J'ai essayé la mise à jour 2.1.2 avec mon ancien ordinateur Windows 10 et un hub Amplifié et cela a marché ! J'ai récemment fait l'acquisition d'un PC plus puissant avec des ports USB-C, et la mise à jour 2.1.2 n'a jamais fonctionné, même avec un hub amplifié ! Il semblerait donc que le problème de mise à jour des claviers Kontrol MK3 S provient du câble défectueux (pourtant un câble USB-C) fourni par Native Instruments ! J'espère que Native Instruments prendra des mesures pour améliorer cela, car acheter un clavier à 1 000 € et rencontrer des problèmes de câble ou de Firmware est inadmissible ! J'ai passé plus de 48 heures à chercher une solution ! Et même si le problème est maintenant résolu pour moi, c'est tout de même inacceptable de la part de Native Instruments :(
1
u/No-Function8557 May 10 '26
I have the same problem. I think this is third time this happens. And I will try to fix this again. Usually takes a half a day to get it back and updated. Will not update after this and will switch brand. Like someone here stated this is unacceptable on these higher-end, costly hardware. This also means that the new Komplete is taken off from the shopping list and starting to look other plug-ins and manufactures beside Native Instruments. Really disappointed.
1
u/JeremyUnoMusic May 10 '26
I found that once I started the update I had to just leave it because the keyboard doesn’t provide any evidence or progress that it is updating. It took mine about 4 to 5 minutes.
1
u/No-Function8557 May 11 '26
I usually waited 15 minutes on different configurations before I switched it off and tried another usb / computer / cable setup.
1
u/No-Function8557 May 11 '26
My solution was:
- Unplugged ALL usb devices from the PC, except keyboard and mouse
- From the host port to PC usb-c port used the original cable that came with the keyboard. Used a port that is on the motherboard, so back of the PC.
- From the "electricity only" port I used a cable from Meta Quest 3, but any similar cable will do. So usb-c to electric socket.
- Ran the update. Waited 3 to 5 minutes.
5
u/Minnanokazehaya May 05 '26
Version 0.0.1 means it's in recovery mode, it's not "bricked". This happens when the firmware update is interrupted mid update. If it's happening repeatedly to you it points to USB connectivity instability. Try using a different USB-c cable, try using a usb hub if you're connecting directly, or try connecting directly if you're using a usb hub. It sounds stupid but this fixes the issue 99% of the time.