MBox Pro (3rd gen) will not reset after firmware update.

[mrobertson1]

[MacBook Pro 15" (Early 2011), 2 GHz i7, 4GB running OS X 10.7.5]
[MBox Pro 3rd Gen, Pro Tools 10.1]
[There is an OWC Mercury Elite-Pro FireWire HDD between the MBox and MacBook Pro, so MBox (FireWire 400 to 800) --> HDD (800) --> MacBook Pro]

I installed drivers for my MBox Pro (to version 1.0.16), and the installation file included a firmware update (to version 1.0.3). After installing the drivers and restarting the computer, the firmware update started, but never finished. I left it for about 2 hours, and the progress bar never moved. I attempted to restart my computer after this period, and the MBox went dark and hasn't come back on since then. The MBox Pro Control Panel says there is no hardware connected, but in About This Mac...-->More info...-->System Report-->FireWire, it says there is an "Unknown Firewire Device" detected (Others have had problems with the internal power leads, but the fact that there is a device detected, and that it worked fine before the firmware update leads me to believe that this is not an issue).


I've tried reinstalling the drivers several times, with three different machines, including two Windows machines, but to no avail. I've searched the DUC, the knowledgebase and Google, but I've found no relevant information. Calling Avid support isn't an option for me right now as I cannot locate my registration card, and I want to delay paying for an ASC until I have exhausted all other options.
Can someone help?

[jryser]

I have asked them about a separate upload for that and am waiting to find out. I will post as soon as I hear something. My Mbox Pro is working well except the tuner is not working.


Sent from my iPhone using Tapatalk

[jryser]

What does your "about" panel say or can you even open it?


Sent from my iPhone using Tapatalk

[mrobertson1]

Originally Posted by jryser

What does your "about" panel say or can you even open it?


Sent from my iPhone using Tapatalk

I can open it, but when I do, there is no number listed next to "firmware version".

[davelok]

Hello gents... I ran into a similar problem last night... I upgraded my Mbox Pro (3rd gen) to latest firmware (1.1.2) - and now the Mbox is not recognized by the Mbox control panel or Pro Tools at all. The firmware version in the control panel is "blank" which seems weird. Now it seems I cannot use it at all and am stuck.. searching these forums for some clues...
thanks

[davelok]

well i was able to figure out my problem (so far anyways) - thought i'd post it if it might help others.
I had to first uninstall the 1.1.12 driver, then install the previous driver (1.0.16 - firmware 1.0.3) which now seems to work again after a reboot. My headphone outputs are working again and I don't hear the static noise. So far so good - just wish there was a readme or notice to not install 1.1.12...
thanks
dave

[Seth Thomas]

The MBox Pro 3 phantom power does not function now with update 1.1.2; and ML update today to 10.8.2.
Is there a way to reset the MBox Pro 3? The red light comes on, but the leds do not light; and, all 4 mics are dead.
Best,
Seth

[Beatsbyair]

I have the same issue. Mbox pro 3 is stuck in firmware update mode. Everytime I turn on the computer (brand new macbook pro 2012) it displays a message saying that mbox is updating firmware, and then my mbox is disconnected...I have to unplug and replug it for the computer to see it. Then when I go into midi setup, it has like 20 copies of the mbox in there. Probably one for each time the computer was turned on. I need a fix for this bad. I believe it's the root cause of a few other issues as well. This thing is only a couple weeks old and this problem is destroying my workflow and music making mojo.

[jryser]

I have sent my MBox in for repair. The issue is that upgrading firmware over several upgrades have caused a glitch. It seems the only way out is to ship it to Avid and have the repair done.


Sent from my iPhone using Tapatalk

[Shabbysheik]

Would love to hear how this went, jryser. Did you have to go through phone support? Cost? Time involved? And did it eventually solve the problem?