Updating my MacPro 5.1 from 140.0.0.0.0 to 144.0.0.0.0 does not work

The Spirit

macrumors member
Original poster
Jun 23, 2010
60
12
Germany
HI.
I have a MacPro 5.1 (see details in my sig).
I am on Bootrom 140.0.0.0.0. But upgrading to a newer Bootrom does not work anymore.
Tried to press the button until the chime comes up -> does not work
Tried to press the button until the led blinks -> does not work
Tried to press the button 10s longer after the led blinks -> does not work
The screens stays black. If i press the power button after 30min, the MacPro shuts down.
What can i try to update my bootrom?
Thanks for your help.
Andreas
 

h9826790

macrumors G5
Apr 3, 2014
14,400
6,951
Hong Kong
You didn't tell us how you run the OS installer. From internal drive? From NVMe? From USB installer?

Tried NVRAM reset yet?
 

The Spirit

macrumors member
Original poster
Jun 23, 2010
60
12
Germany
i downloaded the full installer onto my nvme drive (bootdrive) and did the installation from there.
i did not reset the nvram yet. will try to do this.
 

h9826790

macrumors G5
Apr 3, 2014
14,400
6,951
Hong Kong
i downloaded the full installer onto my nvme drive (bootdrive) and did the installation from there.
i did not reset the nvram yet. will try to do this.
If NVRAM reset (4 chimes) doesn't work, try to run the installer from an INTERNAL SATA drive.
 

The Spirit

macrumors member
Original poster
Jun 23, 2010
60
12
Germany
do i just need to copy the installer from my nvme boot drive to an internal sata and start the installer from there?
seems to easy
 

MIKX

macrumors 68000
Dec 16, 2004
1,775
650
Aussie in Japan
The Spirit

Things to consider. Mojave will only update to an APFS formatted drive.

I upgraded from 140.0.0.0.0 to bootrom 144.0.0.0.0 Mojave plus 10.14.5 to an APFS formatted spare SSD drive + my metal supported Sapphire Dual-X HD 7970.

The above setup allowed the bootrom upgrade to proceed.

==========================================

I then used Carbon Copy Cloner to clone " 10.14.5 " my Samsung M.2 NVMe which is HFS formatted. Everything works.

I'm presuming that you already had Mojave 10.14.4 installed to an APFS drive and that your HD 7870 GPU is " metal supported" and that you were booted from that drive.

The " full" Mojave 10.14.5 installer is 6.04gb. Was your's the same size ?

==================================

Before I ever do a "full & final" install of any Mac OS I archive ALL ( combo & full ) installers to an external drive for any future installations.

Good Luck.

PS : HIS make nice cards ! I absolutely loved my HIS 7950 = best cooling solution !
 

ironmanny1

macrumors newbie
Oct 28, 2018
14
5
I have an NVME 960 Evo M.2 installed on my Mac Pro 4,1 -> 5,1. I was not able to update to 144.0.0.0.0 from 140.0.0.0.0 with the NVME drive. I cloned Mojave to the internal SSD drive, booted off it and was able to update successfully.
 
  • Like
Reactions: MIKX

MIKX

macrumors 68000
Dec 16, 2004
1,775
650
Aussie in Japan
Congrats !

I highly recommend that you make a "signature" ( mine is at the bottom of this post ) so that people will quickly understand your cMP setup.
Go to your Macrumors profile page and look for "signature". tell us everything relevant about your cMP
 
  • Like
Reactions: ironmanny1

jscipione

macrumors 6502
Mar 27, 2017
278
148
I'm in the same boat as OP trying to update to 144.0.0.0.0 from 140.0.0.0.0 using a USB stick 10.14.5 installer. I install the shutdown helper from the installer and power down, then hold the power button until the LEDs starts flashing rapidly, then I get a tone then a bong, and then no boot screen with my RX 580 installed so I can't see what's going on next. I waited overnight and nothing happened, just a black screen. I am installing onto an NVMe boot disk on a real 5,1 running 10.14.2. I will try putting the HD 5770 back in next and see if that helps determine what is going on.
 

bookemdano

macrumors 65816
Jul 29, 2011
1,381
762
I posted in the other bootrom thread that I had the same experience. Seems there is an issue for many (if not all) users trying to jump from 140.0.0.0.0 to 144.0.0.0.0 with an NVMe drive.

I think most reports from users who were able to install 144.0.0.0.0 from an NVMe boot drive were previously on 141.0.0.0.0.

In any case, to echo the other poster here I had zero problems doing the upgrade once I put in my old SATA Mojave drive into one of the internal bays. So that appears to be the solution here.
 

Enricote

macrumors member
Oct 7, 2018
42
24
Madrid, Spain
I posted in the other bootrom thread that I had the same experience. Seems there is an issue for many (if not all) users trying to jump from 140.0.0.0.0 to 144.0.0.0.0 with an NVMe drive.

I think most reports from users who were able to install 144.0.0.0.0 from an NVMe boot drive were previously on 141.0.0.0.0.

In any case, to echo the other poster here I had zero problems doing the upgrade once I put in my old SATA Mojave drive into one of the internal bays. So that appears to be the solution here.
I can confirm. My upgrading proccess from 140.0.0.0 to 144.0.0.0 with a Samsung NVMe 970 EVO 1Tb was successfully done after cloning (via Carbon Copy Cloner) my system from NVMe to one internal SATA SSD. I downloaded the fullinstaller 10.14.5 from Apple. I followed instructions from installer.
 
Last edited:
  • Like
Reactions: roobarb!

MIKX

macrumors 68000
Dec 16, 2004
1,775
650
Aussie in Japan
My usual routine for Mojave.

1. Installed the first release to a SPARE SSD formatted to APFS in an internal SATA bay.
This SSD became my ": Mojave Home SSD " for all OS & bootrom upgrades.

2. I then use Carbon Copy Cloner to clone from the " Mojave Home " SSD TO my M.2 Samsung 970 EVO formatted as HFS+

3. IMPORTANT : Now I Always download the FULL ( 6gb+ ) installer which includes bootrom upgrades using dosdude1's "macOS Mojave Patcher tool " = dosdude1.com/mojave/
Using the "Tools dropdown menu.
macOS Mojave Patcher Tool.jpg


Make sure that you have the LATEST version of dosdue1's patcher though.

The App store download ( correct me if I'm wrong ) doesn't include bootrom upgrades.
===========================================
The downloaded FULL 6gb + installer MUST be started from Applications !
===========================================

This regimen ensures I'm always ' hassle free ' up to date.

NOTE 1. : It really does help if you have an EFI'd HD 7950 or HD 7970 or R9 280X
NOTE 2. : Seeing that M.2 PCIe blades are seen as "external" by MacOS it seems to me
safer to install Mojave to an APFS formatted in an internal SATA bay.
 
Last edited:

MIKX

macrumors 68000
Dec 16, 2004
1,775
650
Aussie in Japan
crjackson

Thanks for that info. Filed.

Seeing that the next release might be the final for Mojave I'll stick with dosdude1's patcher ... :) . . it just works for me.
 
Last edited:

slamjack

macrumors member
Jul 22, 2011
63
12
Moscow
My upgrading proccess from 140.0.0.0 to 144.0.0.0 with a Samsung NVMe 970 EVO 1Tb was successfully done after cloning (via Carbon Copy Cloner) my system from NVMe to one internal SSD. I downloaded the fullinstaller 10.14.5 from Apple. I followed instructions from installer.
I can confirm this. I was able to update firmware only from Carbon Cloner copy on internal HDD (sata). Firmware updating process didn't start from my PCI-E Kingston HyperX predator.
 
  • Like
Reactions: roobarb!

The Spirit

macrumors member
Original poster
Jun 23, 2010
60
12
Germany
i managed to upgrade my bootrom.
i cloned my nvme boot drive to a internal sata hdd. from there i booted and was able to do the upgrade of the bootrom wihtout any problems.
after that i booted again from my nmve ssd
 

jscipione

macrumors 6502
Mar 27, 2017
278
148
Same here. I copied my NVMe ssd to an ahci ssd, then I was able to perform the firmware update to 144.0.0.0. It seems that there is a problem initiating the firmware update from an NVMe boot drive.
 

bookemdano

macrumors 65816
Jul 29, 2011
1,381
762
Same here. I copied my NVMe ssd to an ahci ssd, then I was able to perform the firmware update to 144.0.0.0. It seems that there is a problem initiating the firmware update from an NVMe boot drive.
What firmware were you on before 144? I think the data points so far suggest that this is only an issue for folks who skipped firmware 141.0.0.0.0 (and if so, now we know something Apple likely tweaked/fixed in that firmware).
 
  • Like
Reactions: crjackson2134

jscipione

macrumors 6502
Mar 27, 2017
278
148
What firmware were you on before 144? I think the data points so far suggest that this is only an issue for folks who skipped firmware 141.0.0.0.0 (and if so, now we know something Apple likely tweaked/fixed in that firmware).
I was on 141.0.0.0.0 before, I had upgraded to macOS 10.14.4 before going back to 10.14.2 for 32-bit app compat. So I don't think the problem is limited to 140.0.0.0.0.
 
  • Like
Reactions: bookemdano

bookemdano

macrumors 65816
Jul 29, 2011
1,381
762
I was on 141.0.0.0.0 before, I had upgraded to macOS 10.14.4 before going back to 10.14.2 for 32-bit app compat. So I don't think the problem is limited to 140.0.0.0.0.
Great info, thanks. We've had a bunch of reports from folks on NVMe drives who were able to upgrade from 141.0.0.0.0 to 144.0.0.0.0 just fine, so I guess we're still in search of the culprit here.

Edit: I'm curious what 10.14.2 has in regards to 32bit app compatibility that later versions of 10.14 don't? I haven't noticed any difference in running my 32bit apps under any version of Mojave (other than the warning that they need to be updated, but that's been present since 10.14.0).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.