Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

Upgrader

macrumors 6502
Nov 23, 2014
359
53
I'm running Mojave 10.14.6 and BootROM 138.0.0.0

I need to upgrade my boot drive to an EVO plus NVMe on a Kyro cooler.

Is it possible for me to upgrade the BootROM to 140.0.0.0 now I've already gone to Mojave?

Thanks.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
I'm running Mojave 10.14.6 and BootROM 138.0.0.0

I need to upgrade my boot drive to an EVO plus NVMe on a Kyro cooler.

Is it possible for me to upgrade the BootROM to 140.0.0.0 now I've already gone to Mojave?

Thanks.
Nope, it's to 144.0.0.0.0 or nothing.

 

cageytiger

macrumors newbie
Jun 18, 2016
28
3
I'm trying to upgrade from 140.0.0.0 to 144.0.0.0.

I used a fresh install of 10.14.6 in bay 1, did the hold the button til flashing bong, I got a bootscreen and a progress bar but the progress bar has got to 100% and stopped. It does look a lot like a normal boot progress bar, if I remember correctly the firmware progress bar was different?

I'm scared to touch anything now incase it's still updating firmware, but it's been about 20 minutes at 100%.

Anyone else have this problem or have any ideas?

Cheers!
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
I'm trying to upgrade from 140.0.0.0 to 144.0.0.0.

I used a fresh install of 10.14.6 in bay 1, did the hold the button til flashing bong, I got a bootscreen and a progress bar but the progress bar has got to 100% and stopped. It does look a lot like a normal boot progress bar, if I remember correctly the firmware progress bar was different?

I'm scared to touch anything now incase it's still updating firmware, but it's been about 20 minutes at 100%.

Anyone else have this problem or have any ideas?

Cheers!
Something is definitively wrong, last BootROM upgrade that had a progress bar was MP51.0089.B00, since the requirement change from an AppleOEM/flashed GPU to a METAL GPU with 138.0.0.0.0 is just a grey screen and it takes just a minute or two.
 
  • Like
Reactions: Eschers

cageytiger

macrumors newbie
Jun 18, 2016
28
3
Something is definitively wrong, last BootROM upgrade that had a progress bar was MP51.0089.B00, since the requirement change from an AppleOEM/flashed GPU to a METAL GPU with 138.0.0.0.0 is just a grey screen and it takes just a minute or two.
Yeah just powered off and it rebooted fine without the power button hold.

Am I doing something wrong here? The Mojave install is direct from App Store etc, nothing else installed except GTX 680 flashed.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Yeah just powered off and it rebooted fine without the power button hold.

Am I doing something wrong here? The Mojave install is direct from App Store etc, nothing else installed except GTX 680 flashed.
There are several pitfalls with Mac Pro firmware upgrades, fully read the first post:

 

cageytiger

macrumors newbie
Jun 18, 2016
28
3
There are several pitfalls with Mac Pro firmware upgrades, fully read the first post:


Thanks Alex, all good now, I'd read on another post it didn't need to be through High Sierra, but booting that and running Mojave installer fixed it.

This is off topic but I noticed something earlier, I know you're really active on here and it might help someone. The black screen on boot problem with Windows EFI (I think it's GPU related?) can be bypassed if you boot from a Windows install DVD and let it time out on the 'press any key to boot from DVD/CD' prompt. You need to release the C key immediately as soon as the disk spins up or boots into the DVD, but it works. Not sure if this is a known 'fix'.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Thanks Alex, all good now, I'd read on another post it didn't need to be through High Sierra, but booting that and running Mojave installer fixed it.

This is off topic but I noticed something earlier, I know you're really active on here and it might help someone. The black screen on boot problem with Windows EFI (I think it's GPU related?) can be bypassed if you boot from a Windows install DVD and let it time out on the 'press any key to boot from DVD/CD' prompt. You need to release the C key immediately as soon as the disk spins up or boots into the DVD, but it works. Not sure if this is a known 'fix'.
Windows burned to a DVD is CSM, not UEFI. I'm not understanding what you are trying to show, you are using the Windows installer DVD as a bootstrap for something?
 

KevinClark

macrumors 6502
Feb 28, 2019
349
42
Hi guys I’m worried with a macpro2010 single core x5690 i tried to update from high Sierra to Mojave from usb stick and put my rx 580 Mac after turn off the Mac it refuse to restart now the front led is flashing and no more boot on the os is possible can someone help me please thanks
 

Attachments

  • 30E23449-41CD-49DB-95B3-AB6EE3B66715.jpeg
    30E23449-41CD-49DB-95B3-AB6EE3B66715.jpeg
    1.1 MB · Views: 118
  • BFCEAF3A-03ED-4FCA-9073-3E11CAB7F7FA.jpeg
    BFCEAF3A-03ED-4FCA-9073-3E11CAB7F7FA.jpeg
    651.7 KB · Views: 106

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Hi guys I’m worried with a macpro2010 single core x5690 i tried to update from high Sierra to Mojave from usb stick and put my rx 580 Mac after turn off the Mac it refuse to restart now the front led is flashing and no more boot on the os is possible can someone help me please thanks
Repeating myself from three posts above:

There are several pitfalls with Mac Pro firmware upgrades, fully read the first post:


You will understand what you are doing wrong after reading it, your first photo already shows it.
 
Last edited:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
How to un Brick the Mac ?
If it's really bricked, see your options at the end of the first post I linked. The "What to do if during the upgrade process your Mac Pro bricked:" part of the post.

Be aware that you shouldn't have tried to upgrade MP51.0084.B00 to Mojave 144.0.0.0.0. Apple warns this clearly, you have to upgrade first to MP51.0089.B00, only then you do the 144.0.0.0.0 firmware upgrade.
 

cageytiger

macrumors newbie
Jun 18, 2016
28
3
Windows burned to a DVD is CSM, not UEFI. I'm not understanding what you are trying to show, you are using the Windows installer DVD as a bootstrap for something?
Yes it's probably irrelevant in most cases - but whatever the problem is with Win10 resulting in black screen/no display can be temporarily 'fixed' by letting the installer timeout, to be able to quickly boot in to Windows that is otherwise inaccessible.

I'm now Opencore'd etc, but it was really useful to me as I needed to boot into Windows to flash a GTX680, to in turn be able to run the Mojave installer to update firmware. I was 'stuck' previously due to the Metal requirement and not being able to flash the card.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
I didn’t understand what you said
For you to un-brick the Mac Pro, you have the three options below:

What to do if during the upgrade process your Mac Pro bricked:

If during the upgrade process you bricked the BootROM, you have three options:

  1. Buy a replacement backplane on eBay and replace the backplane yourself, cheapest option if you can't solder SMD. Remember that you need a 2009 backplane if you have an early-2009 Mac Pro. If you have a mid-2010 or mid-2012 you can use either 2010 or 2012 backplanes. Don't mix early-2009 backplanes with mid-2010/mid-2012 CPU trays, or vice-versa - either scenario is a SMC firmware version mismatch and all your fans will run at maximum RPM, full time and without any software control.
  2. Buy a Mac Pro MATT card and use it as a replacement SPI flash, this is not recommended since all MATT cards are clones and won't work for iCloud/iMessage/FaceTime. A replacement backplane is usually cheaper.
  3. Desolder, reprogram and solder back the SPI flash, chip U8700 on the backplane. It's not possible to read or write to the SPI flash memory while it's soldered on the MP5,1 backplane. A cheap SPI flash programmer like ch341a will work for read/write the BootROM after the SPI flash memory is desoldered from the backplane. Start reading here, read all my posts on the subject from there. I strongly recommend that you replace your original SPI flash memory with a brand new one, don't solder it back to the backplane, it will fail soon since SPI flash memories have limited lifetime (manufacture rated for just 100.000 erase/write cycles) when used as NVRAM for a Mac Pro. Again, most hard bricks are caused by the failure of the SPI flash, it's a US$ 2 component easily available, MXIC MX25L3206E, just replace it! Btw, yes, you can use a MXIC MX25L3206E as a modern replacement for the two older models SST25VF032B and MXIC MX25L3205D used on early-2009 and mid-2010 respectively, Apple did it for mid-2012 Mac Pros.

    Mojave has the generic MP51.fd firmware image inside the full installer, it's enough for boot your Mac Pro again but not for iCloud/iMessage/FaceTime login.

    Code:
    Install\ macOS\ Mojave/Install\ macOS\ Mojave.app/Contents/Resources/Firmware/MP51.fd
 
Last edited:

redbandit0

macrumors newbie
Nov 10, 2020
4
0
I currently have Bootloader version MP51.0089.B00. I am running a 5,1 cMP mid-2010, 2 x 2.66 GHz 6-Core Intel Xeon. If I updated my Bootloader to 144.0.0.0.0, will older OSes still load? After reading the first post and it's links and doing a search here, I wasn't sure.

Right now my main OS is El Capitain, but also have High Sierra (10.13.6) and Sierra (10.12.4) on different Partitions/HDDs. Looking to update to Mojave, but that Sierra drive has some legacy software I need that OS version for (but working on getting it updated to 10.13.3 - but having a hard time finding that version - apparently the software I need works buggy on 10.13.6).

I have a Sapphire Radeon Pulse RX580 to install as an upgrade to my current GPU, which is an ATI Radeon HD 5870. I plan to use Opencore to get a boot screen picker again.

I'd be OK to lose the El Capitain OS and make the High Sierra or even Mojave my main OS, but I still need the Sierra one occasionally, or at least 10.13.3 if I can find that.
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I currently have Bootloader version MP51.0089.B00. I am running a 5,1 cMP mid-2010, 2 x 2.66 GHz 6-Core Intel Xeon. If I updated my Bootloader to 144.0.0.0.0, will older OSes still load? After reading the first post and it's links and doing a search here, I wasn't sure.
BootROM is not Boot loader.

And your question has been answered many times. If you can't find it by the search function, the answer is YES.

Even there is no driver for RX580 in El Capitan. But you can still use it via OpenCore. However, that won't be a nice experience if you use that as your primary.

For RX580, I personally recommend you use Mojave as the primary OS.
 
  • Like
Reactions: crjackson2134

redbandit0

macrumors newbie
Nov 10, 2020
4
0
BootROM is not Boot loader.

And your question has been answered many times. If you can't find it by the search function, the answer is YES.

Even there is no driver for RX580 in El Capitan. But you can still use it via OpenCore. However, that won't be a nice experience if you use that as your primary.

For RX580, I personally recommend you use Mojave as the primary OS.
My mistake on the terminology. Thank you for the answer. I was sure it had been answered before, but couldn't find it, perhaps my search terms weren't ideal.

Yes, if I can get the RX580 working, I don't need El Cap anymore, but Sierra is my concern.
Thank you again!
 

Koka016

macrumors regular
Aug 30, 2020
101
12
Serbia
Is it possible that 144.0.0.0.0 blocked CPU upgrade for 4.1 Mac pro? (some micro codes misssing? )
There is too much unsuccessful threads these days?
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Is it possible that 144.0.0.0.0 blocked CPU upgrade for 4.1 Mac pro? (some micro codes misssing? )
There is too much unsuccessful threads these days?
You problem is not BootROM related at all.

Start inspecting the CPU socket pins.
 
  • Like
Reactions: crjackson2134
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.