QU-24 crush after update

Forums Forums Qu Forums Qu troubleshooting QU-24 crush after update

Tagged: , ,

This topic contains 2 replies, has 2 voices, and was last updated by Profile photo of lasolitude lasolitude 6 years, 4 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #53434
    Profile photo of lasolitude

    Hi guys!

    Hope you may help.

    There is a problem with my QU-24. After updating the firmware from QU-24 V1.73 to QU-24 1.82, occassionally I have installed the wrong firmware assigned for QU-Pac V1.82 (16-channels). Don’t ask me how, but I did it. Then the story begins..

    I wanted to backup QU-Pac V1.82 to QU-24 V1.73 version, but the mixer couldn’t find the file of firmware on USB key. Then in order to make it possible for mixer to find the file of update, I just renamed QU-24 V1.73.quu file on my USB to Q-Pac V1.73.quu. The process of installation started and it end up with fail after reboot.

    Now the console is just not reacting, buttons are not working. When I turn it on, the display shows the start screen of device and not loading anything, it’s not working actually.

    Is there any way to solve this problem, to make a backup maybe or hard restart (btw the standard way of hard reset is not working too). Not any button react. Please help!!

    Profile photo of DavidCo

    Hi lasolitude, try this:

    After removing all QUU files from your key, put a fresh copy of the Qu24 firmware image back on. Turn off your Qu24. Put your key into the USB-A slot. Hold the USB (above preamp) and HPF in buttons down as you power up. This should invoke the bootloader to look for a new firmware image on a USB key and force an update.

    EDIT: I *strongly* recommend that users refrain from renaming QUU files. While the codebase is mostly common, there are distinctly separate builds for each product in the range.

    Hope this helps,


    Profile photo of lasolitude

    Hello DavidCo!

    Thank you for the reply.

    Unfortunately it didn’t work either. Finally, I’ve just passed the console to the service centre. Hope they will find a solution.

    Certainly, I will never do the same mistake again.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.