Bricked Sub37 with 1.1 update

Starting from 1.03. Windows updater recognized the Phatty, gave instructions to switch to firmware mode, Sub 37 read FIRMWARE UPDATE and the counter ticked to 100%.

At 100%, it paused, then said “update failed”.

Then Windows said “USB device failed - this is a malfunctioning USB device”.

Now the Phatty reads “Flash Erased - Ready for Code”.

Trying to re-run the update does nothing…

Help!

From another thread ..

Hi guys,

Andy from the Moog Tech Lab here!!!

If you encounter any problems installing the new FW update, please contact us directly. My email is andy@moogmusic.com and my number is 1-828-251-0090 ext 221

You can also reach out to my technicians:

Nick Montoya ext.217 nick@moogmusic.com

Nate Marino ext.204 natemarino@moogmusic.com

Thanks,
Andy Hughes
Service Department Manager
Moog Music, Inc.Control_Voltage

Also, make sure you’re NOT using a USB hub as that causes known issues. You want to go straight from the Sub37 to your computer.

I encountered this problem too. It freaked me out. I ran the installer three more times and it finally worked. No change to the system or components. USB has always been plugged directly into my Mac. Don’t know why it happened and why it finally worked, I’m just thrilled my Sub isn’t dead.

Now I just need documentation for the new features.

An updated manual is included in the download and also available separately from the download tab on the Moog website: http://www.moogmusic.com/products/phattys/sub-37#downloads-tab

Same problem with my Sub 37 :open_mouth: :open_mouth: :open_mouth:
Don’t seem to work, I restarted the procedure three times but still saying: “flash erased waiting for code”…
Can you help me?

Contact Andy from Moog Tech Lab (see post above)…

Thanks!

This happened to me from 1.07 to 1.1 but I rolled back manually to 1.07 then manually did the update to 1.1, it scared the crap out of me because I thought it was permanently bricked but resorting to totally manual update and not auto update program worked for me.

just as an addition when it bricked it was left in the state to receive the 2nd update file of the four files.

To be clear, “bricked” means that a device’s booting software has also been corrupted such that there is no way to install firmware until the boot software has been fixed.

A device is not “bricked” simply because a particular computer/USB interface/SysEx app/transmission setting is currently not working.

It simply means that one of the above things needs to be different.

I writing this because we collectively have a tendency to post alarming headlines for things that often have a simple fix.

And those headlines will exist long after the simple problem has been solved.

That being said, squidfood, did you get your problem solved yet?

I experience a similar issue. The auto update erase the firmware but when I turned the power back on (with pitchwheel all the way up). It would act like it was installing the new firmware but almost immediately return with “device not found”. It found the device fine to erase the firmware. It’s not connected to a hub. Running Windows 7. I tried at least have dozen times. BTW, the instructions don’t really say when to release the pinch bend.

I was terrified. Fortunately, I was able to use the manual method at this point to get it updated. Otherwise, I was getting in the car and heading to Asheville!

If I had time to troubleshoot it with a tech, I would have but I never really know when I’ll have free time and it’s usually odd hours. When I have free time, I’d rather be playing.

All that being said, once the new OS was installed, it’s a beauty

Did you make sure the FINE PITCH was turned all the way down? That must be true in conjunction with the PITCH WHEEL all the way up when rebooting into the installer.

Ok, at least I’m not the only one :blush:

Hello!

First Post!
I had the same issues with the Windows install, took about 8 tries to get it to update. Here’s what worked for me:

  1. Disconnected all other USB devices.
  2. Restarted my Laptop.
  3. Connected the Sub 37 directly into the laptop (no hubs).
  4. Started installer.
    5.After the 2nd try, it finally worked.

I also tried a different USB cable, not sure if it helped, but I was in panic mode.

Good luck!

I sent an email to Moog, still waiting.
BTW, when Sub 37 is ready to update, (after turning filter cutoff and fine tune all the way down) is it right that midi button is red?

Hi there,

Andy from Moog Tech Support here!!!

Please contact us directly:

andy@moogmusic.com or (828)-251-0090 xt. 221, 217, or 214

We will be happy to help you get this sorted.

Thanks,
Andy Hughes
Service Department Manager
Moog Music, Inc.

Still waiting an answer, Andy…

I send an email over a month ago and got no reply Andy… not impressed.

I use “bricked” very specifically, because I’ve tried three computers and none of them recognize the Sub37… “unknown USB device”. So no - with no connection, no way to fix. I’d call that bricked.