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.

lazerdisk

macrumors newbie
Apr 26, 2020
4
2
I updated my original post. The rest of the process remains unchanged, though. I booted into recovery mode from a Time Machine drive, and from there I was able to update the firmware.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
I updated my original post. The rest of the process remains unchanged, though. I booted into recovery mode from a Time Machine drive, and from there I was able to update the firmware.
Still wrong.

Catalina Recovery partition don't have any MP5,1 firmwares. If what you are telling have any sense, it's a Mojave Recovery partition.

For a person that criticise the complexity of the thread in your first post ever on MacRumors, you make a real mess.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Apple released 10.15.5 DP3, build is 19F72f. Downloading it now, very slowly, seems it's not propagated to CDNs down here yet.
 
  • Like
Reactions: crjackson2134

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Firmware updates for BridgeOS Macs, but nothing for non-BridgeOS Macs, same firmwares from February 27.

Checking MP7.1 firmware now.

1037.120.79 - 10.15.5 DP3 (19F72f) - 20200429 - 17.16.15274.5.3

Code:
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2004232004
  Model:        MP71
  EFI Version:  1037.120.79.0.0
  Built by:     tangstad@pdb172
  Date:         Thu Apr 23 20:04:19 2020
  Revision:     1037.120.79 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
  UUID:         2377FE0D-73DC-34E3-9D50-0EA81B2D981B
  UUID:         B1365F68-CE27-3509-837E-0EB2BCE21381
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2004232004
  Model:        MP71
  EFI Version:  1037.120.79.0.0
  Built by:     tangstad@pdb172
  Date:         Thu Apr 23 20:04:19 2020
  Revision:     1037.120.79 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
$IBIOSI$    MP71.88Z.F000.B00.2004232004
Copyright (c) 2005-2020 Apple Inc.  All rights reserved
 
Last edited:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
AFAIK, this is the first time an EFI firmware is signed by tangstad@pdb172. Don't mean anything, I just noticed that.

Code:
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2004232004
  Model:        MP71
  EFI Version:  1037.120.79.0.0
  Built by:     tangstad@pdb172
  Date:         Thu Apr 23 20:04:19 2020
  Revision:     1037.120.79 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
$IBIOSI$    MP71.88Z.F000.B00.2004232004
Copyright (c) 2005-2020 Apple Inc.  All rights reserved
 

bsbeamer

macrumors 601
Sep 19, 2012
4,313
2,713
AFAIK, this is the first time an EFI firmware is signed by tangstad@pdb172. Don't mean anything, I just noticed that.

Same Tangstad?
Screen Shot 2020-04-29 at 4.07.28 PM.png
 
  • Like
Reactions: handheldgames

kings79

macrumors regular
Sep 16, 2015
227
105
This thread still going? How are you guys? What are you talking about these days? ✌
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
BridgeOS is pretty much all the talk going on here now ?
I'm always checking every still supported Mac. I use a script to get all EFI versions for non-BridgeOS Macs and generate the table, but the first one I visually inspect is always MP6,1.

Focus changed to BridgeOS on the thread just because it's what Apple is relentlessly updating at the moment, sometimes with weekly new EFI releases.
 
  • Like
Reactions: JedNZ

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Two hours searching and some minutes editing this table, now every EFI released is linked to the Apple Support article or the announcement post here, first post already updated:

- Mac Pro 5,1 firmware releases, from the oldest EFI update to the newest:

BootROM VersionReleased with:Type:Note:
MP51.007F.B03Mac Pro EFI Firmware Update 1.5General releaseFirst public released Mac Pro 5,1 firmware update, microcodes vulnerable to Spectre and Meltdown
MP51.0083.B0010.13 DP5BetaBeta APFS support, microcodes vulnerable to Spectre and Meltdown
MP51.0084.B0010.13 DP6 and 10.13.0General releaseInitial APFS support, microcodes vulnerable to Spectre and Meltdown
MP51.0085.B0010.13.4 and Mojave DP1 to DP3General releaseAPFS support, microcodes vulnerable to Spectre and Meltdown
MP51.0087.B0010.13.5General releaseMissing microcodes and bricks the Mac Pro if you boot UEFI installed Windows 10
MP51.0089.B0010.13.6General releaseSpectre/Meltdown mitigated microcodes on the April 2 Microcode Update Guidance.
138.0.0.0.010.14 DP7 and 10.14.0General release5GT/s support for every PCIe 2.0 card
139.0.0.0.010.14.1 DP1Betaminor updates and corrections
140.0.0.0.0 10.14.1 DP3 and 10.14.1 to 10.14.4General releaseNative NVMe boot support, several minor updates and corrections
141.0.0.0.010.14.4 DP2Betaminor updates and corrections
142.0.0.0.010.14.4 DP4 and 10.14.5 DP1BetaUpdated APFSJumpStart EFI module - W3xxx Xeon bricker.

This BootROM version was never released outside betas.
144.0.0.0.010.14.5 DP4 and 10.14.5General releaselot's of corrections, booting improvements, works with W3xxx Xeons.

This is the current BootROM release
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Apple just released 10.15.5 DP4 (19F83c). Checking it know

Apple released a new EFICheck AllowListAll, so non-BridgeOS Macs probably got updates.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
MP7,1:

1037.120.82 - 10.15.5 DP4 (19F83c) - 20200507 - 17.16.15284.5.2

Code:
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2005050349
  Model:        MP71
  EFI Version:  1037.120.82.0.0
  Built by:     _securitya@pdb172
  Date:         Tue May  5 03:49:21 2020
  Revision:     1037.120.82 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
  UUID:         2377FE0D-73DC-34E3-9D50-0EA81B2D981B
  UUID:         B1365F68-CE27-3509-837E-0EB2BCE21381
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2005050349
  Model:        MP71
  EFI Version:  1037.120.82.0.0
  Built by:     _securitya@pdb172
  Date:         Tue May  5 03:49:21 2020
  Revision:     1037.120.82 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
IBIOSI$    MP71.88Z.F000.B00.2005050349
Copyright (c) 2005-2020 Apple Inc.  All rights reserved

MP6,1:

Code:
$IBIOSI$    MP61.88Z.F000.B00.2004121755
Copyright (c) 2005-2020 Apple Inc.  All rights reserved
Apple ROM Version
  Model:        MP61
  EFI Version:  136.0.0.0.0
  Built by:     root@saumon
  Date:         Sun Apr 12 17:55:07 PDT 2020
  Revision:     136 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, Release
  Compiler:     Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)
 
Last edited:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
10.15.5 DP4 (19F83c) EFI firmware list for non-BridgeOS Macs:

All Catalina supported non-BridgeOS Macs got EFI firmware updates, several Macs got the version bumped two releases over the previous updates.

Mac:EFI version:
IM13,1291.0.0.0.0
IM14,1143.0.0.0.0
IM14,2143.0.0.0.0
IM14,3143.0.0.0.0
IM14,4203.0.0.0.0
IM15,1234.0.0.0.0
IM16,1234.0.0.0.0
IM16,2234.0.0.0.0
IM17,1178.0.0.0.0
IM18,1183.0.0.0.0
IM18,3183.0.0.0.0
IM19,11037.120.79.0.0
MB10,1187.0.0.0.0
MB8,1189.0.0.0.0
MB9,1192.0.0.0.0
MBA5,1263.0.0.0.0
MBA6,1121.0.0.0.0
MBA7,1194.0.0.0.0
MBP10,1261.0.0.0.0
MBP10,2284.0.0.0.0
MBP11,1160.0.0.0.0
MBP11,2160.0.0.0.0
MBP11,4198.0.0.0.0
MBP12,1191.0.0.0.0
MBP13,1245.0.0.0.0
MBP13,2267.0.0.0.0
MBP13,3267.0.0.0.0
MBP14,1207.0.0.0.0
MBP14,2207.0.0.0.0
MBP14,3207.0.0.0.0
MBP9,1232.0.0.0.0
MM6,1284.0.0.0.0
MM7,1248.0.0.0.0
MP6,1136.0.0.0.0
 
Last edited:

magicpeasant

macrumors newbie
May 8, 2020
3
0
@tsialex - great work and info you've provided to the community over the last couple of years - outstanding!
I have a couple of questions though that I can't seem to find answers to in this thread anywhere:
1) Regarding Windows 10 installing/injecting SecureBoot certificates - are there any real life implications to this if you're only running Windows on your cMP 5,1 - ie no macOS, no dual boot required?
2) Does the NVMe boot capability provided by 144.0.0.0.0 for the cMP 5,1 extend to Windows 10 as well, again with Window 10 being the only install OS in the 5,1?
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
@tsialex - great work and info you've provided to the community over the last couple of years - outstanding!
I have a couple of questions though that I can't seem to find answers to in this thread anywhere:
1) Regarding Windows 10 installing/injecting SecureBoot certificates - are there any real life implications to this if you're only running Windows on your cMP 5,1 - ie no macOS, no dual boot required?
CSM/legacy Windows installs don't require or support SecureBoot. It's a requirement only for UEFI Windows 8.1/10 installs.

If you just use UEFI Windows 10 on your Mac Pro, that don't change the effects inside the NVRAM, same fragmentation problems happens. BootROM/EFI firmware runs before anything.

2) Does the NVMe boot capability provided by 144.0.0.0.0 for the cMP 5,1 extend to Windows 10 as well, again with Window 10 being the only install OS in the 5,1?
NVMe boot is only supported by Windows 10 UEFI installs, CSM/legacy don't have NVMe boot support at all. Using your Mac Pro as a Windows only PC don't change this fact in any way.

Mac Pro EFI is version 1.10 from 2010, while Windows 10 requires PCs that support UEFI 2.3.1c spec from 2012. Windows 10 just happens to work with Apple EFI 1.10, but you have to overcome it's problems when running with an old and unsupported EFI revision.

The only way to make Windows 10 UEFI more or less secure to use with a Mac Pro 5,1 is to use OpenCore NVRAM protection. I'd advise you to dump and clean up/reconstruct your BootROM, then use OpenCore to protect it - anything else will make you a brick down the road.
 

magicpeasant

macrumors newbie
May 8, 2020
3
0
CSM/legacy Windows installs don't require or support SecureBoot. It's a requirement only for UEFI Windows 8.1/10 installs.

If you just use UEFI Windows 10 on your Mac Pro, that don't change the effects inside the NVRAM, same fragmentation problems happens. BootROM/EFI firmware runs before anything.


NVMe boot is only supported by Windows 10 UEFI installs, CSM/legacy don't have NVMe boot support at all. Using your Mac Pro as a Windows only PC don't change this fact in any way.

Mac Pro EFI is version 1.10 from 2010, while Windows 10 requires PCs that support UEFI 2.3.1c spec from 2012. Windows 10 just happens to work with Apple EFI 1.10, but you have to overcome it's problems when running with an old and unsupported EFI revision.

The only way to make Windows 10 UEFI more or less secure to use with a Mac Pro 5,1 is to use OpenCore NVRAM protection. I'd advise you to dump and clean up/reconstruct your BootROM, then use OpenCore to protect it - anything else will make you a brick down the road.
Ugh - I was afraid you say something like that ;-(
I no longer have a macOS compatible GPU to use in my cMP (I’m running a GeForce RTX 2070) so no way to run macOS (and thus no UEFITool) to reconstruct my bootrom :-(
I’m going to be installing a PCie-based NVMe drive soon, for use as a Win 10 boot drive (currently using a SATA SSD) - assuming the Mac Pro doesn’t brick during the process, I can disable Secure Boot after install to mitigate any future potential bootrom bricking issues...
thanks heaps for your response mate - very much appreciated.
Regards,
P.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Ugh - I was afraid you say something like that ;-(
I no longer have a macOS compatible GPU to use in my cMP (I’m running a GeForce RTX 2070) so no way to run macOS (and thus no UEFITool) to reconstruct my bootrom :-(
I’m going to be installing a PCie-based NVMe drive soon, for use as a Win 10 boot drive (currently using a SATA SSD) - assuming the Mac Pro doesn’t brick during the process, I can disable Secure Boot after install to mitigate any future potential bootrom bricking issues...
thanks heaps for your response mate - very much appreciated.
Regards,
P.
Since you will change to a NVMe boot drive and UEFI installed Windows, you will have to workaround the Mac Pro EFI limitations with OpenCore BEFORE installing Windows, not after, enabling NVRAM protection. If you enable after, the damage is already done.

Any Apple OEM GPU will work for this, Apple GT120 is inexpensive and works fine up to 10.13.6.
 
  • Like
Reactions: foliovision

magicpeasant

macrumors newbie
May 8, 2020
3
0
Since you will change to a NVMe boot drive and UEFI installed Windows, you will have to workaround the Mac Pro EFI limitations with OpenCore BEFORE installing Windows, not after, enabling NVRAM protection. If you enable after, the damage is already done.

Any Apple OEM GPU will work for this, Apple GT120 is inexpensive and works fine up to 10.13.6.
Sage advice, which I'll follow. Now to call in a favour and borrow back that HD 5770 I gave away...
Thanks again for your advice and help, Sir.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Hey tsialex, do you know if UEFI Windows pollutes the NVRAM with SecureBoot certificates on the 6,1?
It's worse and better with a MP6,1.

Worse because there are more NVRAM stores inside the late 2013 Mac Pro NVRAM volume, so a binwalk of a MP6,1 seems a nightmare of multiple certificates.

Better because the MP6,1 SPI flash is 64Mbit, so the space that SecureBoot take with a MP5,1 is not so much a problem with a MP6,1.
 
  • Like
Reactions: startergo
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.