[Solved] Pro 3 SE is bricked since updating?

mjaestewart · « **on:** November 13, 2020, 04:06:02 PM »

Hi Everyone! Looking for some help on this brand new Pro 3 I just received today.

After receiving the Pro 3 I started to play and instantly noticed crackling noises coming out of my monitors which did not seem normal. After a quick google search I discovered others having similar issues and instantly knew I needed to update the OS from 1.0.0 to 1.1.0.

I followed the instructions (using a MacBook Pro) and instantly noticed that the screen went black. After 30+ minutes I knew something did not seem right so I restarted the Pro 3. The screen is still black. Attached is a picture of what this "brick'd" device looks like when it's powered on.

Is there any other known method I can use to start this device in a different mode to load v1.1.0 update?

I've been trying to reach out to Sequential Support but have yet to get any response. As having this new beauty sit here in death mode on a Friday night where the weekend is completely open is depressing. Any help would be appreciated!

composerjk · « **Reply #1 on:** November 13, 2020, 06:28:16 PM »

First suggestion: try sending the Core and Panel updates, again. Ideally, when the update is happening you should see something on the display.

Note that there are two updates: the Core OS and the display Panel. Send one at a time and power cycle between each.

If those don't work, you can try the steps I mentioned in the following post to get into bootloader mode and try sending again. Note, as I mention there, this has not been verified by Sequential folk.
https://forum.sequential.com/index.php/topic,4550.msg45765.html#msg45765

In your case, from the image, it looks like the synth has booted up. The display does have a screensaver blank option during normal operation, but usually pressing keys/buttons brings it back on. I'm assuming you've also tried pressing various buttons/slider and see no changes for the lights connected to those buttons/slider?

Good luck!

mjaestewart · « **Reply #2 on:** November 13, 2020, 06:38:10 PM »

Quote from: composerjk on November 13, 2020, 06:28:16 PM

First suggestion: try sending the Core and Panel updates, again. Ideally, when the update is happening you should see something on the display.

Note that there are two updates: the Core OS and the display Panel. Send one at a time and power cycle between each.

If those don't work, you can try the steps I mentioned in the following post to get into bootloader mode and try sending again. Note, as I mention there, this has not been verified by Sequential folk.
https://forum.sequential.com/index.php/topic,4550.msg45765.html#msg45765

In your case, from the image, it looks like the synth has booted up. The display does have a screensaver blank option during normal operation, but usually pressing keys/buttons brings it back on. I'm assuming you've also tried pressing various buttons/sliders and see no changes for the lights connected to those buttons/sliders?

Good luck!

Thanks for the response! I definitely followed your advice from the previous post. I do get a flashing indicator on "0" when in this apparent, but unverified, bootloader mode. I went out to the store and bought a "mio" USB type A to 5 pin Midi cable to send this update via midi to the device. Is this what you meant when you said to send the update file via 5-pin midi?

Also, I have tried using both a Mac and a Windows computer to send the update file without any kind of luck. I've been trying for hours at this point. The only other thing I do not see happening is that the slider is NOT lighting up when sending this update file to the Pro 3.

Here is how I am sending the update file:

1. USB Type-A Midi Out on Computer --> 5-Pin Midi In on Pro 3

Amy other suggestions?

composerjk · « **Reply #3 on:** November 13, 2020, 06:52:09 PM »

Quote from: mjaestewart on November 13, 2020, 06:38:10 PM

Thanks for the response! I definitely followed your advice from the previous post. I do get a flashing indicator on "0" when in this apparent, but unverified, bootloader mode. I went out to the store and bought a "mio" USB type A to 5 pin Midi cable to send this update via midi to the device. Is this what you meant when you said to send the update file via 5-pin midi?

For the bootloader mode, it might only work over the 5-pin MIDI port.

In your case, I'd have tried without the bootloader mode. If you're connecting over USB, ideally, the Pro 3 will be listed as a MIDI device (whether via SysEx Librarian and the sendmidi/receivemidi command-line tools). If it's not, then it might mean only the bootloader option is possible (again, just guessing). So, I'd power up the Pro 3 SE, connect the USB cable, select the Pro 3 in SysEx Librarian, and send one of the .syx files. Then, repeat with the other file. And, if that fails, try the MIDI cable.

As for the lights not lighting up when attempting with bootloader mode, that sounds like it not working. I believe I recall those lights lighting up during the load process. NOTE: that's only for using the bootloader mode. During a normal OS load, those lights do not light up; only updates happen via the display.

Of course, your best bet is support, if it doesn't work. But, if they haven't responded, yet, there probably won't be a response until Monday.

mjaestewart · « **Reply #4 on:** November 13, 2020, 08:28:20 PM »

Quote from: composerjk on November 13, 2020, 06:52:09 PM

Quote from: mjaestewart on November 13, 2020, 06:38:10 PM
Thanks for the response! I definitely followed your advice from the previous post. I do get a flashing indicator on "0" when in this apparent, but unverified, bootloader mode. I went out to the store and bought a "mio" USB type A to 5 pin Midi cable to send this update via midi to the device. Is this what you meant when you said to send the update file via 5-pin midi?

For the bootloader mode, it might only work over the 5-pin MIDI port.

In your case, I'd have tried without the bootloader mode. If you're connecting over USB, ideally, the Pro 3 will be listed as a MIDI device (whether via SysEx Librarian and the sendmidi/receivemidi command-line tools). If it's not, then it might mean only the bootloader option is possible (again, just guessing). So, I'd power up the Pro 3 SE, connect the USB cable, select the Pro 3 in SysEx Librarian, and send one of the .syx files. Then, repeat with the other file. And, if that fails, try the MIDI cable.

As for the lights not lighting up when attempting with bootloader mode, that sounds like it not working. I believe I recall those lights lighting up during the load process. NOTE: that's only for using the bootloader mode. During a normal OS load, those lights do not light up; only updates happen via the display.

Of course, your best bet is support, if it doesn't work. But, if they haven't responded, yet, there probably won't be a response until Monday.

I've tried everything. I guess there's not much I can do except wait for Monday. It's unfortunate that this occurred on a brand new unit. I really hope that the Pro 3 line is a stable synth. I'm quite nervous holding onto something that will only cause me issues in the future, especially at the price point I paid for the Special Edition.

I really do appreciate all of your help on this.

composerjk · « **Reply #5 on:** November 13, 2020, 10:53:12 PM »

What I can say is that the Pro 3 is a favorite and a fun synth to play and create sounds. My sympathies for having to wait to play yours.

mjaestewart · « **Reply #6 on:** November 14, 2020, 05:46:46 PM »

Quote from: composerjk on November 13, 2020, 10:53:12 PM

What I can say is that the Pro 3 is a favorite and a fun synth to play and create sounds. My sympathies for having to wait to play yours.

So I think I figured it out!!! Senior Engineer by profession but certainly can be unintelligent at times. And yesterday was one of those days.

Here's what I did wrong:
1. MIDI IN on the mio USB cable --> Pro 3 MIDI IN (DOh!!!! Very wrong!!!!)

The correct way:
1. USB Type-A to 5-Pin MIDI was the correct cable indeed (used a mio brand that I picked up at a local music store)
2. Press Transpose UP and DOWN on start to boot into bootloader mode (Indeed is correct for bootloader)
3. MIDI OUT on the mio USB cable --> Pro 3 MIDI IN (SEE ATTACHED IMAGE)
4. Pushed the sysx CORE v1.1.0 to Pro3 and instantly saw the slider lights illuminate (SEE ATTACHED IMAGE)
5. Powered Off after sysx CORE v1.0.0 finished loading
6. Powered back on into bootloader mode holding in Transpose UP and DOWN
7. Pushed the sysx PANEL v1.1.0 to Pro3 and instantly saw the slider lights illuminate (SEE ATTACHED IMAGE)
8. Powered Off after sysx PANEL v1.0.0 finished loading
9. Voila!! System is now functional and v1.1.0 is now displayed in Global (SEE ATTACHED IMAGE)

Glad I can finally start using this synth! Thought I'd provide an update since someone else may find this thread useful.

composerjk · « **Reply #7 on:** November 14, 2020, 09:13:31 PM »

In that case, you might have been fine just loading the Core and Panel OS SysEx files without starting up the bootloader mode. That mode would only be needed when the synth is not responding at all.

Glad to hear the Pro 3 SE is working, again.

chysn · « **Reply #8 on:** March 01, 2021, 07:30:44 PM »

I'm bringing this thread back to life because I had an unsuccessful installation of Pro3 Beta 1.1.2.4.

I tried initiating bootloader mode, and then I sent the OS file via DIN MIDI. It appeared to read the file; the slider LEDs went upward as the file was sent. After the file was finished transmitting, the slider lights proceeded to turn off from the bottom up. Once this was done, the 0 Transpose light started flashing.

I wasn't sure if I should continue to wait, or what. There was never any obvious indication that it was "done." After some minutes, I cycled power, and I was back where I was after the update... a dead Pro 3.

Do you know how you know if the bootloader update succeeded or not?

Update I was able to get my instrument back online by using the bootloader mode to revert to 1.1.0.0 (thank you for the instructions, mjaestewart and composerjk). Now that I know I can do this, I'll try updating when the next beta or final OS comes out. After three attempts, I don't have much reason to think that 1.1.2.4 is going to work for me.

composerjk · « **Reply #9 on:** March 01, 2021, 10:45:48 PM »

From Bootloader mode, I believe what you saw is that indication it's done. The following is simply from observation:

OS .syx file loading: Slider lights turning on from bottom to top.
OS saving: Slider lights turning off from bottom to top.
Transpose 0 blinking again: done.

Typically, with the Pro 3, I'd do an OS update in normal running mode. Bootloader mode is only needed if things fail (which they seem to do with the beta 1.1.2.4 OS). In the normal mode, send the OS .syx file over the MIDI or USB (whichever you've selected for SysEx in Globals > MIDI). Then, you'll see updates on the display:

OS .syx file loading: Display shows percentage of file loaded so far.
OS saving: Display shows: Received OS successfully. Wait until save completes to power...
OS saved: Display shows: Finished saving. Power off...

fyi.

sockmonkey · « **Reply #10 on:** March 02, 2021, 12:01:31 AM »

Hi, I followed the instructions, updated via MIDI DIN and... bricked. The synth reported that the firmware arrived ok and told me to power cycle. But now my SE starts up with the sequencer lights 2 (red) & 6 (green) illuminated. They blink once and then stay on. I tried reloading the syx via bootloader mode without success. Any ideas? Thank you.

sockmonkey · « **Reply #11 on:** March 02, 2021, 12:11:38 AM »

I was able to downgrade to 1.1.0.0 in bootloader mode (whew), and I would be highly motivated to help troubleshoot this problem.

rb415 · « **Reply #12 on:** March 02, 2021, 03:12:05 AM »

1.1.2.4 bricked my SE too this morning. I updated using SysEx Librarian on a Mac, with a direct USB connection, and the Pro 3 screen reported a successful update. But on power cycling just the lights for sequencer steps 2 and 6 lit up, and the synth was otherwise dead. Then an anxious hour trying to restore 1.1.0 via the bootloader mode, which was not made easy by the fact that I don't own a conventional MIDI interface anymore (so I had to piggy back on to another USB synth, from its THRU to the Pro 3's IN). All working again now. I'll resolve to be a 'late adopter' next time...

chysn · « **Reply #13 on:** March 02, 2021, 05:04:20 AM »

The experiences relayed here mirror mine exactly. Fortunately I still have a MIDI interface box.

dvsmusic · « **Reply #14 on:** March 02, 2021, 05:29:32 AM »

I had the same experience on my Mac using SysEx Librarian and 5pin DIN MIDI. I was able to downgrade using boot loader mode. I was really looking forward to the fix for having to reboot after it sits idle for a while. Now I am just glad it boots up at all

. It's still my favorite mono synth, though.

W07 · « **Reply #15 on:** March 02, 2021, 05:31:02 AM »

Same here. Bricked Po3 when using either regular or bootloader mode. I think the sysexfile posted by sequential is just corrupted.

unease · « **Reply #16 on:** March 02, 2021, 06:16:59 AM »

So anyone actually had a successful update with this version??

erolok · « **Reply #17 on:** March 02, 2021, 07:32:24 AM »

The same here. But the bootloader mode back to 1.10 helped

chysn · « **Reply #18 on:** March 02, 2021, 07:34:12 AM »

We can all agree that Bootloader is the Pro 3's killer app.

Quatschmacher · « **Reply #19 on:** March 02, 2021, 08:00:49 AM »

I presume you’ve all reported this via a ticket to support so that they address it quickly.