MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0

[MIKX]

Thanks for that info Alex.

So . . . no booting from USB 3 yet .. . but the number of bootrom upgrades in Mojave suggests more to come.
Perhaps .. . .

I DO feel sorry for anyone whose cMP got bricked . . . . will replacing the W3xxx cpus with originals or X cpus fix that problem ?

 

[tsialex]

Thanks for that info Alex.

So . . . no booting from USB 3 yet .. . but the number of bootrom upgrades in Mojave suggests more to come.
Perhaps .. . .

I DO feel sorry for anyone whose cMP got bricked . . . . will replacing the W3xxx cpus with originals or X cpus fix that problem ?

W3xxx are the original Xeons for any single CPU Mac Pro.

Xeons X5xxx/E5xxx and, almost sure, L5xxx will boot with 142.0.0.0.0.

 

[MIKX]

W3xxx are the original Xeons for any single CPU Mac Pro.

Yes, I saw that. How much liability does Apple have for bricked cMPs ?

 

[tsialex]

Yes, I saw that. How much liability does Apple have for bricked cMPs ?

I bet nothing, it's a beta BootROM that shouldn't be installed by anyone out of the Seed channel. Or anyone that have some good sense.

 

[bsbeamer]

Beta SHOULD be for discovering issues like this before public release, preventing an issue widespread that bricks OEM style machines. Read the fine print of any beta testing program and it’s basically a waiver of responsibility.

 

[MIKX]

Yes, agreed . .. Betas are scary, risky.

I wonder if any official Apple Mojave 10.14.4 developers suffered getting bricked too . . surely some have W3xxx 5,1's

 

[tsialex]

Yes, agreed . .. Betas are scary, risky.

I wonder if any official Apple Mojave 10.14.4 developers suffered getting bricked too . . surely some have W3xxx 5,1's

Quoting myself:

Mac Pro up to 5,1 don't upgrade firmware with updates, only with full installs.

142.0.0.0.0 it's a beta bootROM that you only can get if you are a developer that have access to the Seed channel.

No end user can install it inadvertently.

Apple didn't release a full installer for 10.14.4 DPs yet.

 

[bsbeamer]

If anything it’s a clearer indication the folks developing these FW updates are using more top of the line or upgraded machines and possibly never discovered on their own internal testing. Prior speculation they added previous update features as part of development for 7,1. Who knows. We’ll see at least a 143 and maybe even a 144 before public release.

 

[tsialex]

If anything it’s a clearer indication the folks developing these FW updates are using more top of the line or upgraded machines and possibly never discovered on their own internal testing. Prior speculation they added previous update features as part of development for 7,1. Who knows. We’ll see at least a 143 and maybe even a 144 before public release.

Seems plausible, at the same time weird. Not one Mac Pro with a W3690? All duals?

 

[bsbeamer]

Agree it’s strange, but also could be necessary if testing high quantity of RAM/utilization in OS. If it was true traditional testing, stock configs would always be referenced... but that sort of broke with the Metal GPU requirement.

 

[Macschrauber]

My personal machine is with W3670, just built another Mac Pro with W3680 - wouldn't be amused to get them bricked by a firmware update if I am not in this tech theme.

Hope that Apple fixes this bug soon enough.

We should spam Apple with bug reports !

https://www.apple.com/feedback/mac-pro.html

 

[circlecreek]

Hi tsialex,

My macpro5,1 is now bricked since mid-February 2019 refusing to go further than 60-70% of the boot process. Nothing helped, neither Reset SMC, nor Safe mode, nor Reset PRAM/NVRAM. It was installed with Mojave and working perfectly in Dark mode with an NVidia K5000 for Mac.
I suspect that I have now inherited an automatic firmware upgrade to an invalid version.

May I ask you if you know how to:
- Identify the system information from single-user mode (bootROM version, firmware, etc...)
- Get the previous 140.0.0.0.0 released with 10.14.1
- Re-apply the previous 140.0.0.0.0 from single-user mode (thought that I could mount an additional USB-key then)

Thank you for your advice.
Best regards

20190304: 10.14.4 DP4 - 142.0.0.0.0

DON'T FLASH 142.0.0.0.0 IF YOU HAVE A W3xxx XEON!
ONLY WORKS WITH X5xxx/E5xxx/L5xxx XEONS.​

With todays 10.14.4 DP4, Apple released MP5,1 BootROM 142.0.0.0.0:

• Build date is 20190214
• BootBlock version is APLEFI1.88Z.0005.I00.1902142048
• CRC32 is 64e8f5ea.
• same microcodes as 138.0.0.0.0
• same NVMe EFI module as 140.0.0.0.0

$IBIOSI$ MP51.88Z.F000.B00.1902142049
‰Apple ROM Version
  Model:        MP51
  EFI Version:  142.0.0.0.0
  Date:         Thu Feb 14 20:43:08 2019
  Build Type:   Release

View attachment 824556

20190204: 10.14.4 DP2 - 141.0.0.0.0

With todays 10.14.4 DP2, Apple released MP5,1 BootROM 141.0.0.0.0:

View attachment 819923

• Build date is 20181219
• CRC32 is 58ee7535.
• same microcodes as 138.0.0.0.0
• same NVMe module as 140.0.0.0.0

$IBIOSI$ MP51.88Z.F000.B00.1812191621
‰Apple ROM Version
  Model:        MP51
  EFI Version:  141.0.0.0.0
  Date:         Wed Dec 19 16:15:33 2018
  Build Type:   Release

20181030: 140.0.0.0.0 released with 10.14.1

Today Apple released 10.14.1 final, it's the same 140.0.0.0.0 BootROM released with 10.14.1 DP3.
(10.14.2 and 10.14.3 still have the same 140.0.0.0.0 BootROM)

The new Mac Pro BootROM with NVMe boot support is now released for everyone, but remember that Mac Pro 5,1 don't install firmwares automatically with updates like every other Mac.

$IBIOSI$ MP51.88Z.F000.B00.1809191555
Apple ROM Version
  Model:        MP51
  EFI Version:  140.0.0.0.0
  Date:         Wed Sep 19 15:49:52 2018
  Build Type:   Release

You have three ways to install 140.0.0.0.0 (updated to 10.14.3):

• install 10.14.3 from scratch into another drive,
• download and open Mac App Store full installer for 10.14.3 (~6GB download), the installer will ask you to perform the upgrade,
• manually trigger the install with 10.14.3 RecoveryHDMetaDmg.pkg. Instructions in this post, use the current RecoveryHDMetaDmg.pkg (~450MB download).

Note 1:

You can't use the createinstallmedia pen drive to upgrade the firmware, you have to do it from macOS.

Note 2:

If you have a Metal supported GPU and you open the full Mac App Store installer and the installer tells you that your GPU don't have Metal, please report this bug to Apple. It's a bug with the detection of Metal support that the macOS installer has with some HD 79xx and RX-580 GPUs.

Please report to it to Apple: Submitting Bugs and Feedback

Note 3:

If you can't install 140.0.0.0.0 because of the Metal detection bug with some HD 79xx and RX-580 GPUs, boot 10.13.6 and run the full Mac App Store 10.14.2 installer from there. Worked for most people.

140.0.0.0.0 and previous macOS releases note:

Since a lot of people ask this question: firmware 140.0.0.0.0 can boot even 10.6.8, but only if your GPU has drivers for it. With RX-4xx/RX-5xx, you are limited to 10.12.6/10.13/10.14, per example.

NVMe and previous macOS support:

Apple started supporting NVMe protocol with Sierra, but only for blades with 4 Kbytes per sector. This seems counterintuitive since 512 Kbytes per sector are older, but Apple only supported their own NVMe drives and those are 4 Kbytes per sector. With High Sierra, Apple supports both 4 Kbytes and 512 bytes per sector blades.

So, to use your NVMe drive you are limited to Sierra and newer macOS versions for drives with 4 Kbytes per sector and only to High Sierra and Mojave for NVMe drives with 512 bytes per sector.

Most blades on the market are 512 bytes per sector, all Samsung OEM and consumer blades are 512 bytes per sector and usually only NVMe drives made for the datacenter market are 4 Kbytes per sector with the exception of some rare Toshiba and Intel blades that are 4 Kbytes too.

20181008: 10.14.1 DP3 with 140.0.0.0.0

Apple released 10.14.1 DP3 and 140.0.0.0.0 Mac Pro BootROM.

• NVMe EFI module added and it's different than the one from MP61,
• PCIe drives still recognised as external,
• Same 29 & 31 microcodes from May,
• No boot screens for UEFI cards.

$IBIOSI$ MP51.88Z.F000.B00.1809191555
Apple ROM Version
  Model:        MP51
  EFI Version:  140.0.0.0.0
  Date:         Wed Sep 19 15:49:52 2018
  Build Type:   Release

NVMe EFI module already injected:

View attachment 793233



First post about 140.0.0.0.0 #1455. You can read posts #1554 and #1569 to know how to install 140.0.0.0.0 manually or just wait for the final release of 10.14.1.


20180925: 10.14.1 DP1 with 139.0.0.0.0

Apple released 10.14.1 DP1 and 139.0.0.0.0 Mac Pro BootROM.

• No boot screens for UEFI cards,
• no NVMe EFI module added,
• no FileVault2,
• same microcodes,
• still safe to insert the NVMe EFI module.

$IBIOSI$ MP51.88Z.F000.B00.1808171030
Apple ROM Version
  Model:        MP51
  EFI Version:  139.0.0.0.0
  Date:         Fri Aug 17 10:24:21 2018
  Build Type:   Release

First post about 139.0.0.0.0 #1242

20180813: 10.14 DP7 with 138.0.0.0.0

New BootROM 138.0.0.0.0 for Mac Pro 5,1 with updated microcodes (0x106A5 29 and 0x206C2 31), support for 5GT/s link speed on macOS/Windows without R17 mod, enabled HDMI audio on RX480 and new/improved firmware flasher on Mojave DP7/PB6 (18A365a) full installer.

Now seems you don't need a Mac EFI GPU to flash it, but the Mojave installer checks for a Metal supported one before upgrading the BootROM. @Squuiid confirmed flashing with a RX580, sadly without boot screens/boot selector.

Note 1:

Apple changed the versioning of the EFI from hex to decimal:

MP51.0084.B00 = 132.0.0.0.0
MP51.0085.B00 = 133.0.0.0.0
MP51.0087.B00 = 135.0.0.0.0
MP51.0089.B00 = 137.0.0.0.0


Note 2:

NVIDIA GPUs have a default mode of 2.5GT/s, only when in 3D use they go to 5GT/s, it's a power saving feature. Only eVGA GTX 680 Mac Edition and GPUs flashed with the same firmware show 5GT/s all the time into System Information.

Attention:

The new Firmware Flasher don't have the usual progress bar, just a grey screen on Mac EFI GPUs, or a black one with a PC GPU, and the usual DVD tray opening. Since the new flashing process don't have progress indicator/completion and seems to take longer to complete and shutdown the Mac Pro, you have to wait until the shutdown/restart.

View attachment 775772

Updated microcodes:

View attachment 775777

5GT/s link speed with a AMD HD 7870 without R17 mod:

View attachment 775822

BIOS version:

The complete BIOS version for 138.0.0.0.0 is MP51.88Z.F000.B00.1807300628

NVMe support:

Apple did not add the NVMe EFI module with 138.0.0.0.0, but the injection method is the same as was done with High Sierra - no changes.

What I have to do to upgrade the firmware:

If your Mac Pro have a BootROM earlier than MP51.0089.B00, to upgrade to 138.0.0.0.0 you will have to do:

1. Download the full Mac App Store installer for 10.13.6, open it and then do as the installer says to upgrade to MP51.0089.B00. After the firmware upgrade reboot, you can close the installer app.
2. Download the full Mac App Store installer for Mojave, the most recent one, open it and then do as the installer says to upgrade to 138.0.0.0.0. After the firmware upgrade reboot, you can close the installer app.

Mac Pro 5,1 recent firmware releases:

10.13 DP5 with MP51.0083.B00 with initial APFS support
10.13 DP6 with MP51.0084.B00 with APFS support
10.13.4 with MP51.085.B00 (Mojave DP1/DP2/PB1/DP3/PB2 too)
10.13.5 with MP51.087.B00 missing the Intel Xeon microcodes
10.13.6 with MP51.089.B00 updating to the Spectre mitigated microcodes on the April 2 Microcode Update Guidance.
10.14 DP7/PB6 with 138.0.0.0.0 with 5GT/s and new microcodes
10.14.1 DP1 with 139.0.0.0.0
10.14.1 DP3 with 140.0.0.0.0 with NVMe support
10.14.4 DP2 with 141.0.0.0.0
10.14.4 DP4 with 142.0.0.0.0 W3xxx Xeon "bricker"

 

[h9826790]

Hi tsialex,

My macpro5,1 is now bricked since mid-February 2019 refusing to go further than 60-70% of the boot process. Nothing helped, neither Reset SMC, nor Safe mode, nor Reset PRAM/NVRAM. It was installed with Mojave and working perfectly in Dark mode with an NVidia K5000 for Mac.
I suspect that I have now inherited an automatic firmware upgrade to an invalid version.

May I ask you if you know how to:
- Identify the system information from single-user mode (bootROM version, firmware, etc...)
- Get the previous 140.0.0.0.0 released with 10.14.1
- Re-apply the previous 140.0.0.0.0 from single-user mode (thought that I could mount an additional USB-key then)

Thank you for your advice.
Best regards

Sorry, but from your description, your cMP is NOT bricked.

It's just macOS issue, nothing firmware related. And there is NO auto firmware update on cMP (no matter you want it or not).

You may open another thread for seeking help. And at the mean time, try a clean install of macOS, or switching graphic card etc. But please keep that away from this thread now. It's not firmware related.

 

[LightBulbFun]

decided to take the risk and updated my MP4,1-5,1 to 142

pleased to report nothings been bricked, but I am running Dual X5677s so nothing was expected to get bricked

(once again 1 of the 2 Certs have vanished post update)

 

[circlecreek]

Thank you h9826790,

Unfortunately I can't perform a clean install of macOS because the progress bar doesn't even complete in safe mode, nor with a brand new hard-disc. There must be a way to identify my bootROM version from single-user mode.

I'll give it a try with another graphic card...

Thank you

 

[tsialex]

Thank you h9826790,

Unfortunately I can't perform a clean install of macOS because the progress bar doesn't even complete in safe mode, nor with a brand new hard-disc. There must be a way to identify my bootROM version from single-user mode.

I'll give it a try with another graphic card...

Thank you

Bricked Mac Pros don't even get the grey screen. You have another problem.

 

[flehman]

Hi tsialex,

My macpro5,1 is now bricked since mid-February 2019 refusing to go further than 60-70% of the boot process. Nothing helped, neither Reset SMC, nor Safe mode, nor Reset PRAM/NVRAM. It was installed with Mojave and working perfectly in Dark mode with an NVidia K5000 for Mac.
I suspect that I have now inherited an automatic firmware upgrade to an invalid version.

May I ask you if you know how to:
- Identify the system information from single-user mode (bootROM version, firmware, etc...)
- Get the previous 140.0.0.0.0 released with 10.14.1
- Re-apply the previous 140.0.0.0.0 from single-user mode (thought that I could mount an additional USB-key then)

Thank you for your advice.
Best regards

If you create a new thread to ask for help, one thing to do would be to open the case and report if any of the diagnostic lights are illuminated. Only way to get a new or “bad” bootrom is to download full OS X installer from the App Store or mess with developer previews or betas (which we should not do). Something else is going on if it is booting that far.

 

[tsialex]

MP5,1 and MP4,1>5,1 when bricked:

• powers on when you press the power button,
• Power LED keeps on,
• EFI DONE LED keeps off,
• nothing on the screen,
• no chime,
• no beep when you try to get into Firmware Programming Mode,
• no caps lock LED or anything else works.

[doublepost=1551965643][/doublepost]Bricked = No POST

 

[jhowarth]

You would think that Apple would have pulled the problematic beta boot ROM images on first reports of the bricking. Or at least put a huge warning up that it shouldn't be installed on single CPU MacPro units.

 

[tsialex]

You would think that Apple would have pulled the problematic beta boot ROM images on first reports of the bricking. Or at least put a huge warning up that it shouldn't be installed on single CPU MacPro units.

Cupertino updated Seed channel of SUS at least two times after I found what is causing the "bricks", but just to add other things. 10.14.4 DP4 still available.
[doublepost=1551968072][/doublepost]Btw, Apple didn't remove MP51.0087.B00 until 10.13.6 was released. I doubt that they will remove 142.0.0.0.0 that has a controlled release and can't be installed unless you intentionally install it.

 

[jhowarth]

Cupertino updated Seed channel of SUS at least two times after I found what is causing the "bricks", but just to add other things. 10.14.4 DP4 still available.
[doublepost=1551968072][/doublepost]Btw, Apple didn't remove MP51.0087.B00 until 10.13.6 was released. I doubt that they will remove 142.0.0.0.0 that has a controlled release and can't be installed unless you intentionally install it.

But MP51.0087.B00 didn't cause bricks so it isn't the same situation.

 

[tsialex]

But MP51.0087.B00 didn't cause bricks so it isn't the same situation.

No? Seems you missed how all this started…

I started researching this because my dual 2009, @h9826790, @Cecco and at least more three Mac Pros bricked with MP51.0087.B00.

One more thing, 142.0.0.0.0 are not real bricks and I always use "bricks" when referring to it. MP51.0087.B00 bricks are really dead and need SPI flash desolder/reprogramming/re-solder to boot again.
[doublepost=1551970811][/doublepost]You can say that 142.0.0.0.0, if ever released to the general public, will affect half or more of Mac Pros released and it's a lot more serious, but say that MP51.0087.B00 didn't caused bricks is just wrong.

 

[jhowarth]

No? Seems you missed how all this started…

I started researching this because my dual 2009, @h9826790, @Cecco and at least more three Mac Pros bricked with MP51.0087.B00.

One more thing, 142.0.0.0.0 are not real bricks and I always use "bricks" when referring to it. MP51.0087.B00 bricks are really dead and need SPI flash desolder/reprogramming/re-solder to boot again.

Requiring access to a dual CPU tray is effectively bricked for most users.

 

[tsialex]

Requiring access to a dual CPU tray is effectively bricked for most users.

Why you need a dual CPU tray? Just buy a $3,49 Xeon E5520 from eBay, install and get it going again.

Repeating my self again and again: end users shouldn't mess with beta BootROMs. I don't even tell where to get it.

Any way, this is a useless discussion, the only thing that anyone can do is report.

 

[LightBulbFun]

Why you need a dual CPU tray? Just buy a $3,49 Xeon E5520 from eBay, install and get it going again.

Repeating my self again and again: end users shouldn't mess with beta BootROMs. I don't even tell where to get it.

Any way, this is a useless discussion, the only thing that anyone can do is report.

on the report thing, shouldn't you be linking to https://bugreport.apple.com/web/ for bug reporting?

(on the CPU thing, iv always wanted to test one of those really low end Dual Core Nehalem Xeons in a Mac Pro just for the giggles of it, its funny how someone of them have "130W" TDPs )