I have 'bricked' my MicroFreak

[Rufus The Dog]

I downloaded the latest firmware first and then went through the firmware update procedure - seemingly without issue. When I power cycled my MF all I then got was the sign-on screen (MICRO FREAK etc in square outline) and nothing else - dead as a brick.

A member of the FB MF group let me know how to reset the MF to put it in to update mode - I could not find that referenced anywhere else - hold shift arp and oct/mod down then power up. The utility button lights up.

Starting MIDI Control Centre finds the MF but claims firmware revision is 0.0.0 - start update procedure and it fails with usual pop up error message and Utility button no longer lit and MIDI control centre can no long connect to MF.

I have tried various combinations of what gets turned on first, when connected etc. to no avail - I still have an impressive brick.

I have raised a ticket with Arturia but it is the weekend so I do not expect a response until Monday at the earliest.

Running on a MacBook Pro too old to update past El Capitan (10.11.6) - I do have a windows 10 machine available if anyone thinks that will help.

Any thoughts of what I could try next? 

Thanks

[CC4]

Bummer. Did you try these steps?
https://www.arturia.com/faq/installation/firmware-reset-and-detection-of-a-midi-device

[tnunnery]

I have the same exact issue. The steps in the FAQ did not have any impact. Help!

[Rufus The Dog]

Bummer. Did you try these steps?
https://www.arturia.com/faq/installation/firmware-reset-and-detection-of-a-midi-device

Thanks for the tip... still bricked though, sadly. I expect Arturia will point me at this first when they respond, hopefully, tomorrow.

[Edouard_Arturia]

Hello.

I saw a user posting that he faced the same issue.
He resolved it by updating from Windows instead of MacOS.
Once updated, the unit could be detected again on his macbook.

I hope this can help !

[tnunnery]

Updating using a Windows 7 machine worked for me.

[Rufus The Dog]

Hello.

I saw a user posting that he faced the same issue.
He resolved it by updating from Windows instead of MacOS.
Once updated, the unit could be detected again on his macbook.

I hope this can help !

Thanks for the tip - that is, in fact, exactly how I solved the issue