Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

andrewkhoo

macrumors newbie
Oct 7, 2020
10
1
While it's easy to confirm if your Mac Pro firmware have SecureBoot certificates inside the NVRAM volume, just run binwalk with your BootROM image dump and see if the output show any X.509 certificates inside, SecureBoot is just a red-herring.

The real problem is the NVRAM data/variables/entries not being erased anymore and the NVRAM volume part of the BootROM self destructing over the years. SecureBoot just makes this process much faster since the certificates/DBs/PKs occupy so much valuable space inside the NVRAM volume.

I've sent you a PM with instructions.
Hi Alexandre, thank you for the reply! hopefully you can repair that old lady of mine.
 

andrewkhoo

macrumors newbie
Oct 7, 2020
10
1
While it's easy to confirm if your Mac Pro firmware have SecureBoot certificates inside the NVRAM volume, just run binwalk with your BootROM image dump and see if the output show any X.509 certificates inside, SecureBoot is just a red-herring.

The real problem is the NVRAM data/variables/entries not being erased anymore and the NVRAM volume part of the BootROM self destructing over the years. SecureBoot just makes this process much faster since the certificates/DBs/PKs occupy so much valuable space inside the NVRAM volume.

I've sent you a PM with instructions.
much appreciated for your help, thank you tsialex! god knows what might happen if we didn't manage to connect here. I'm so grateful that you took the time to explain the steps in detail and, it works, even for a low-tech person like me.
 
  • Like
Reactions: tsialex

dksoutha

macrumors member
Mar 5, 2012
35
1
Just seeking clarification: I suppose that since my 4,1 is flashed to 5,1 I must follow the 5,1 directions for reconstructing my NVRAM?
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,005
13,238
Who would bet that one more EFI release would be found and dumped after all these years? Better yet, one earlier than all others!

Yes, thanks to @Edge, now we have the dump and the data for MP41.0081.B03:

EFI Release vs BIOS Version vs BootBlock Version Reference Table:

EFI Release:BIOS Version:BootBlock Version:
MP41.0081.B03MP41.88Z.0081.B03.0902231259AAPLEFI1.88Z.0004.I00.0901121311 (this could be from an earlier BootROM)
MP41.0081.B04MP41.88Z.0081.B04.0903051113AAPLEFI1.88Z.0004.I00.0901121311 (this could be from an earlier BootROM)
MP41.0081.B??MP41.88Z.0081.B??AAPLEFI1.88Z.0004.I00.0908061259
MP41.0081.B07MP41.88Z.0081.B07.0910130729AAPLEFI1.88Z.0004.I00.0910130728
MP41.0081.B08MP41.88Z.0081.B08.1001221313AAPLEFI1.88Z.0004.I00.1001221311
MP51.007F.B00MP51.88Z.007F.B00.1008031144AAPLEFI1.88Z.0005.I00.1006041028
MP51.007F.B??MP51.88Z.007F.B??AAPLEFI1.88Z.0005.I00.1007141219
MP51.007F.B01MP51.88Z.007F.B01.1008231310AAPLEFI1.88Z.0005.I00.?
MP51.007F.B02MP51.88Z.007F.B02.1009221128AAPLEFI1.88Z.0005.I00.?
MP51.007F.B03MP51.88Z.007F.B03.1010071432AAPLEFI1.88Z.0005.I00.1010071430
MP51.0083.B00MP51.88Z.0083.B00.1707271620AAPLEFI1.88Z.0005.I00.1707271617
MP51.0084.B00MP51.88Z.0084.B00.1708080528AAPLEFI1.88Z.0005.I00.1708080525
MP51.0085.B00MP51.88Z.0085.B00.1802021746AAPLEFI1.88Z.0005.I00.1802021742
MP51.0087.B00MP51.88Z.0087.B00.1804181525AAPLEFI1.88Z.0005.I00.1804181521
MP51.0089.B00MP51.88Z.0089.B00.1806081708AAPLEFI1.88Z.0005.I00.1806081704
138.0.0.0.0MP51.88Z.F000.B00.1807300628AAPLEFI1.88Z.0005.I00.1807300627
139.0.0.0.0MP51.88Z.F000.B00.1808171030AAPLEFI1.88Z.0005.I00.1808171029
140.0.0.0.0MP51.88Z.F000.B00.1809191555AAPLEFI1.88Z.0005.I00.1809191554
141.0.0.0.0MP51.88Z.F000.B00.1812191621AAPLEFI1.88Z.0005.I00.1812191620
142.0.0.0.0MP51.88Z.F000.B00.1902142049AAPLEFI1.88Z.0005.I00.1902142048
144.0.0.0.0MP51.88Z.F000.B00.1904121248AAPLEFI1.88Z.0005.I00.1904121247

Also, this indicates that the BootBlock versions for MP41.0081.B03 and MP41.0081.B04 could be not correct and the Mac Pros were upgraded from a previous release - BootBlocks are never upgraded by efiflasher when the EFI is upgraded.

BootBlock version AAPLEFI1.88Z.0004.I00.0901121311 is probably from MP41.0081.B02 or something.
 
Last edited:

Edge

macrumors regular
Jul 28, 2005
128
24
Who would bet that one more EFI release would be found and dumped after all these years? Better yet, one earlier than all others!

Yes, thanks to @Edge, now we have the dump and the data for MP41.0081.B03:
Thanks @tsialex for reconstructing the ROM for this replacement machine. It only took me 14 months to send you the files once I had dumped it! After 12 years I hope it was worth the wait!
 

itiot

macrumors newbie
May 23, 2019
5
1
Thank you for this guide. i used to make the firmware files for 2 machines. and its working good!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.