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.

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Today a user here sent me a dump of a brick to investigate.

Code:
DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
24972         0x618C          CRC32 polynomial table, little endian
35787         0x8BCB          mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
243907        0x3B8C3         BIOS version: MP51.88Z.F000.B00.1904121248
524288        0x80000         UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
549260        0x8618C         CRC32 polynomial table, little endian
560075        0x88BCB         mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
768195        0xBB8C3         BIOS version: MP51.88Z.F000.B00.1904121248
1048576       0x100000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1064960       0x104000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1065216       0x104100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1077504       0x107100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1085696       0x109100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1114112       0x110000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1130496       0x114000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1130752       0x114100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1143040       0x117100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1151232       0x119100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1179648       0x120000        UEFI PI Firmware Volume, volume size: 196608, header size: 1, revision: 0, Variable Storage, GUID: FFF12B8D-7696-4C8B-85A9-2747075B4F50
1179688       0x120028        NVRAM start of the 1st VSS stream
1179766       0x120076        NVRAM MemoryConfig type: (j)
1181061       0x120585        NVRAM MemoryConfig type: (i)
1183153       0x120DB1        NVRAM MemoryConfig type: (g)
1185201       0x1215B1        NVRAM MemoryConfig type: (h)
1187249       0x121DB1        NVRAM MemoryConfig type: (i)
1189341       0x1225DD        NVRAM MemoryConfig type: (g)
1191389       0x122DDD        NVRAM MemoryConfig type: (h)
1193437       0x1235DD        NVRAM MemoryConfig type: (i)
1195529       0x123E09        NVRAM MemoryConfig type: (g)
1197577       0x124609        NVRAM MemoryConfig type: (h)
1199625       0x124E09        NVRAM MemoryConfig type: (i)
1201717       0x125635        NVRAM MemoryConfig type: (g)
1203765       0x125E35        NVRAM MemoryConfig type: (h)
1205813       0x126635        NVRAM MemoryConfig type: (i)
1207905       0x126E61        NVRAM MemoryConfig type: (g)
1209953       0x127661        NVRAM MemoryConfig type: (h)
1212001       0x127E61        NVRAM MemoryConfig type: (i)
1214093       0x12868D        NVRAM MemoryConfig type: (g)
1216141       0x128E8D        NVRAM MemoryConfig type: (h)
1218189       0x12968D        NVRAM MemoryConfig type: (i)
1220281       0x129EB9        NVRAM MemoryConfig type: (g)
1222329       0x12A6B9        NVRAM MemoryConfig type: (h)
1224377       0x12AEB9        NVRAM MemoryConfig type: (i)
1226469       0x12B6E5        NVRAM MemoryConfig type: (g)
1228517       0x12BEE5        NVRAM MemoryConfig type: (h)
1230565       0x12C6E5        NVRAM MemoryConfig type: (i)
1245255       0x130047        NVRAM start of the 2nd VSS stream
1245302       0x130076        NVRAM MemoryConfig type: (j)
1246597       0x130585        NVRAM MemoryConfig type: (i)
1248689       0x130DB1        NVRAM MemoryConfig type: (g)
1343511       0x148017        bzip2 compressed data, block size = 100k
1345189       0x1486A5        HardwareID Base_xx: 20
1345198       0x1486AE        HardwareID 11-digits SSN: redactedEUE
1345215       0x1486BF        HardwareID 3-digit HWC model: EUE
1376256       0x150000        UEFI PI Firmware Volume, volume size: 2686976, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1416827       0x159E7B        BIOS version: MP51.88Z.F000.B00.1904121248
1614976       0x18A480        Apple NVMe EFI Module
4063232       0x3E0000        UEFI PI Firmware Volume, volume size: 65536, header size: 1, revision: 0, GUID: E3B980A9-5FE3-48E5-929B-2798385A9027
4128768       0x3F0000        UEFI PI Firmware Volume, volume size: 65536, header size: 0, revision: 0, Apple Boot Volume, GUID: 04ADEEAD-61FF-4D31-BAB6-64F8BF901F5A
4128867       0x3F0063        BootBlock version: AAPLEFI1.88Z.0005.I00.1006041028
4194000       0x3FFED0        HardwareID MLB/LBSN: redactedBH9A, BuildDate: redacted

The interesting thing, there are 29 MemoryConfig entries and no SecureBoot certificates/PKs/dbs at all, just severe fragmentation.

Why I'm showing this? My theory that you can brick a Mac Pro just with the fragmentation of the NVRAM over time, see the multiple MemoryConfig entries accumulating, seems to be confirmed.

I'll investigate where/when exactly this happens now, I already have some insights about it.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Yesterday Apple released 10.15.5 DP5 (19F94a):

1037.120.87 - 10.15.5 DP5 (19F94a) - 20200520 - 17.16.15289.5.1
Code:
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2005132104
  Model:        MP71
  EFI Version:  1037.120.87.0.0
  Built by:     _securitya@pdb172
  Date:         Wed May 13 21:04:41 2020
  Revision:     1037.120.87 (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.2005132104
  Model:        MP71
  EFI Version:  1037.120.87.0.0
  Built by:     _securitya@pdb172
  Date:         Wed May 13 21:04:41 2020
  Revision:     1037.120.87 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
IBIOSI$    MP71.88Z.F000.B00.2005132104
Copyright (c) 2005-2020 Apple Inc.  All rights reserved

No new EFI firmware releases for non-BridgeOS Macs, still the same releases as 10.15.5 DP4:

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:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Apple just 10.15.5 (19F96) released, downloading it now.

macOS Catalina 10.15.5 Update

macOS Catalina 10.15.5 introduces battery health management in the Energy Saver settings for notebooks, an option to control automatic prominence of video tiles on Group FaceTime calls, and controls to fine-tune the built-in calibration of your Pro Display XDR. The update also improves the stability, reliability, and security of your Mac.

Battery Health Management
• Battery health management to help maximize battery lifespan for Mac notebooks
• Energy Saver preference pane now displays battery condition and recommends if the battery needs to be serviced
• Option to disable battery health management
For more information, please visit https://support.apple.com/kb/HT211094

FaceTime Prominence Preference
• Option to control automatic prominence on Group FaceTime calls so video tiles do not change size when a participant speaks

Calibration Fine-Tuning for Pro Display XDR
• Controls to fine-tune the built-in calibration of your Pro Display XDR by adjusting the white point and luminance for a precise match to your own display calibration target

This update also includes bug fixes and other improvements.
• Fixes an issue that may prevent Reminders from sending notifications for recurring reminders
• Addresses an issue that may prevent password entry on the login screen
• Fixes an issue where System Preferences would continue to show a notification badge even after installing an update
• Resolves an issue where the built-in camera may not be detected when trying to use it after using a video conferencing app
• Addresses an issue for Mac computers with the Apple T2 Security Chip where internal speakers may not appear as a sound output device in Sound preferences
• Fixes a stability issue with uploading and downloading media files from iCloud Photo Library while your Mac is asleep
• Resolves a stability issue when transferring large amounts of data to RAID volumes
• Fixes an issue where the Reduce Motion Accessibility preference did not reduce the speed of animations in a FaceTime group call

Some features may not be available for all regions, or on all Apple devices.
For more detailed information about this update, please visit: https://support.apple.com/kb/HT210642

For detailed information about the security content of this update, please visit: https://support.apple.com/kb/HT201222
[automerge]1590528073[/automerge]
Same EFI firmware releases from April 27 as 10.15.5 DP4, but new EFI firmwares for all Catalina supported Macs:

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:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Comparing with 10.15.5 DP5, MP7,1 didn't got a new EFI Firmware, just new BridgeOS:

MP7,1:

1037.120.87 - 10.15.5 (19F96) - 20200526 - 17.16.15290.0.0


Code:
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2005131954
  Model:        MP71
  EFI Version:  1037.120.87.0.0
  Built by:     _securitya@nonijuice
  Date:         Wed May 13 19:54:44 2020
  Revision:     1037.120.87 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
  UUID:         AE1298CF-67F2-3343-893D-13B9A579EBD7
  UUID:         65258576-FDEB-32EA-B2FF-5F29A91E084C
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2005131954
  Model:        MP71
  EFI Version:  1037.120.87.0.0
  Built by:     _securitya@nonijuice
  Date:         Wed May 13 19:54:44 2020
  Revision:     1037.120.87 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
$IBIOSI$    MP71.88Z.F000.B00.2005131954
Copyright (c) 2005-2020 Apple Inc.  All rights reserved
 

bsbeamer

macrumors 601
Sep 19, 2012
4,313
2,713
In case it's helpful:

System Version: macOS 10.15.5 (19F96)
Kernel Version: Darwin 19.5.0

Model Identifier: MacBookPro16,1
Boot ROM Version: 1037.120.87.0.0 (iBridge: 17.16.15290.0.0,0)

Model Name: Apple T2 Security Chip
Firmware Version: 17P5290

Chipset Model: AMD Radeon Pro 5500M
ROM Revision: 113-D3220E-190
VBIOS Version: 113-D32206U1-019
Option ROM Version: 113-D32206U1-019
EFI Driver Version: 01.01.190
 

KingCachapa

macrumors member
Feb 29, 2020
62
3
@tsialex and co., couple questions if you have the time (=

- When we check if a ROMTool export has been corrupted, opening the bin in TextEdit: it's usually all these crazy characters, and by searching "Secure", if we get a match, we should worry. Is there a guide or a thread dedicated to what happens / is recommended to do, if we *do* find a match examining the big ole' cMP's little dumps? Luckily I'm still safe, but just in case.

- Any point in running ROMTool on a modern MacBook Pro too? I did out of curiosity and tried to dump, but got an error. A day later, VirusBarrier Scanner gave me 2 alerts related to it (pic below) what do you think?

sjdgs.png
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
@tsialex and co., couple questions if you have the time (=

- When we check if a ROMTool export has been corrupted, opening the bin in TextEdit: it's usually all these crazy characters, and by searching "Secure", if we get a match, we should worry. Is there a guide or a thread dedicated to what happens / is recommended to do, if we *do* find a match examining the big ole' cMP's little dumps? Luckily I'm still safe, but just in case.
While it works, this is not the correct way. Install binwalk and use it to check.

There is no guide on the clean up, since there are several checksums and free space indicators that need to be set when you do any edits on the NVRAM volume. You can use the OpenCore NVRAM clean up if you have SecureBoot inside just one NVRAM store. If you already have two, you need a manual clean up.

- Any point in running ROMTool on a modern MacBook Pro too? I did out of curiosity and tried to dump, but got an error.
Macs released around 2013 are UEFI and support UEFI Windows installs. UEFI Windows is a problem only with EFI1.10 Macs and it's not a problem itself but a trigger for fragmentation, the real problem.

SecureBoot certificates/dbs/PKs trigger the fragmentation that corrupts the BootROM because it requires so much space inside the NVRAM volume.

A day later, VirusBarrier Scanner gave me 2 alerts related to it (pic below) what do you think?

View attachment 919308
Normal, any AV will mark directhw.kext as a false positive, in this case.
 

lukesturr

macrumors member
Jul 16, 2010
37
45
Texas
I got curious today and decided to dump my MacPro4,1->5,1 BootROM (144). It's currently running Mojave and UEFI Windows 10 with OpenCore. I've had this thing for 5 years now and I remember having a UEFI install of Windows in the past, but luckily I don't see any certs in the dump. I am concerned about the "XML document, version: "1.0"" line. @tsialex should I be worried and does anything else seem problematic? Thanks!

Code:
DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
24972         0x618C          CRC32 polynomial table, little endian
35787         0x8BCB          mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
524288        0x80000         UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
549260        0x8618C         CRC32 polynomial table, little endian
560075        0x88BCB         mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
1048576       0x100000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1064960       0x104000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1065216       0x104100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1077504       0x107100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1085696       0x109100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1114112       0x110000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1130496       0x114000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1130752       0x114100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1143040       0x117100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1151232       0x119100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1179648       0x120000        UEFI PI Firmware Volume, volume size: 196608, header size: 1, revision: 0, Variable Storage, GUID: FFF12B8D-7696-4C8B-85A9-2747075B4F50
1205261       0x12640D        XML document, version: "1.0"
1343538       0x148032        bzip2 compressed data, block size = 100k
1376256       0x150000        UEFI PI Firmware Volume, volume size: 2686976, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
4063232       0x3E0000        UEFI PI Firmware Volume, volume size: 65536, header size: 1, revision: 0, GUID: E3B980A9-5FE3-48E5-929B-2798385A9027
4128768       0x3F0000        UEFI PI Firmware Volume, volume size: 65536, header size: 0, revision: 0, Apple Boot Volume, GUID: 04ADEEAD-61FF-4D31-BAB6-64F8BF901F5A
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
I got curious today and decided to dump my MacPro4,1->5,1 BootROM (144). It's currently running Mojave and UEFI Windows 10 with OpenCore. I've had this thing for 5 years now and I remember having a UEFI install of Windows in the past, but luckily I don't see any certs in the dump. I am concerned about the "XML document, version: "1.0"" line. @tsialex should I be worried and does anything else seem problematic? Thanks!

Code:
DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
24972         0x618C          CRC32 polynomial table, little endian
35787         0x8BCB          mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
524288        0x80000         UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
549260        0x8618C         CRC32 polynomial table, little endian
560075        0x88BCB         mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
1048576       0x100000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1064960       0x104000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1065216       0x104100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1077504       0x107100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1085696       0x109100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1114112       0x110000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1130496       0x114000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1130752       0x114100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1143040       0x117100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1151232       0x119100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1179648       0x120000        UEFI PI Firmware Volume, volume size: 196608, header size: 1, revision: 0, Variable Storage, GUID: FFF12B8D-7696-4C8B-85A9-2747075B4F50
1205261       0x12640D        XML document, version: "1.0"
1343538       0x148032        bzip2 compressed data, block size = 100k
1376256       0x150000        UEFI PI Firmware Volume, volume size: 2686976, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
4063232       0x3E0000        UEFI PI Firmware Volume, volume size: 65536, header size: 1, revision: 0, GUID: E3B980A9-5FE3-48E5-929B-2798385A9027
4128768       0x3F0000        UEFI PI Firmware Volume, volume size: 65536, header size: 0, revision: 0, Apple Boot Volume, GUID: 04ADEEAD-61FF-4D31-BAB6-64F8BF901F5A
Normal, it's the IASInstallPhaseList.plist, a log that it's created every time you open Recovery or macOS installer to track Recovery/macOS installer completion.

The problem is to have more than one, when you have two or more, you have a fragmented NVRAM volume.
 
  • Like
Reactions: lukesturr

osxfr33k

macrumors regular
Jun 26, 2019
164
21
I apologize if this question has already been asked but I have a situation where I need to revert back to The original bootrom on a macpro5,1 from 144 to 007F. I have a second macro5,1 that still has original bootrom 007F. Can I use bootrom to dump that rom and use bootrom to flash that to the other macpro5,1 logic board or that won’t work and why?

The reason why I’m doing this is because the latest bootrom has an issue with a PCI express card that I’m using to connect to an instrument and that instrument requires an older bootrom. I believe one of the later bootrom’s adds features to the PCIe bus that this PCIe card must not like. That 2nd macpro5,1 logic board is bad and bought another one off ebay but it has the latest bootrom.

Does the bootrom have unique information on each logic board like a PC bios or would one bootrom work in different Macpro5,1 logic board bootrom?
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
I apologize if this question has already been asked but I have a situation where I need to revert back to The original bootrom on a macpro5,1 from 144 to 007F. I have a second macro5,1 that still has original bootrom 007F. Can I use bootrom to dump that rom and use bootrom to flash that to the other macpro5,1 logic board or that won’t work and why?

The reason why I’m doing this is because the latest bootrom has an issue with a PCI express card that I’m using to connect to an instrument and that instrument requires an older bootrom. I believe the bootrom adds features to the PCIe bus That this PCIe card must not like. That 2nd macpro5,1 logic board is bad and bought another one off ebay but it has the latest bootrom.

Does the bootrom have unique information on each logic board like a PC bios or would one bootrom work in different Macpro5,1 logic board bootrom?
Answered several times, search is your friend.

BootROMs are unique, you can't use a dump from one Mac to another. When you use a BootROM from one Mac Pro on another you are cloning it. Apple detect this clones, since the MACAddresses are not stored inside the BootROM, and blocks iCloud/FaceTime/Messages.

Mac BootROMs are a lot more complex than PC UEFI firmwares or BIOS, Apple saves much more unique serialising/tracking data inside than a PC.

If your theory about the way the PCIe slots are initialised since 138.0.0.0.0, is correct, install PCIe tools and downgrade the slot that your card is installed back to PCIe v1.0. Someone made a script for this some time ago on another thread.
 
  • Like
Reactions: osxfr33k

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Answered several times, search is your friend.

BootROMs are unique, you can't use a dump from one Mac to another. When you use a BootROM from one Mac Pro on another you are cloning it. Apple detect this clones, since the MACAddresses are not stored inside the BootROM, and blocks iCloud/FaceTime/Messages.

Mac BootROMs are a lot more complex than PC UEFI firmwares or BIOS, Apple saves much more unique serialising/tracking data inside than a PC.

If your theory about the way the PCIe slots are initialised since 138.0.0.0.0, is correct, install PCIe tools and downgrade the slot that your card is installed back to PCIe v1.0. Someone made a script for this some time ago on another thread.

thanks!
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
Apple released 10.15.6 DP2 (19G46c), for non-BridgeOS Macs, same EFI firmwares as 10.15.5 from April 27, no changes:

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:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
BridgeOS and EFI firmware updates for 2019 Mac Pro (J160):

1037.140.39 - 10.15.6 (19G46c) - 20200609 - 17.16.16045.5.1
Code:
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2006020623
  Model:        MP71
  EFI Version:  1037.140.39.0.0
  Built by:     _securitya@macncheese
  Date:         Tue Jun  2 06:23:36 2020
  Revision:     1037.140.39 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
  UUID:         889CF082-EAC1-33F7-BB00-D6D1C0A5DF36
  UUID:         98EC616F-9713-3EB9-B9A2-5A14AAB59204
Apple ROM Version
  BIOS ID:      MP71.88Z.F000.B00.2006020623
  Model:        MP71
  EFI Version:  1037.140.39.0.0
  Built by:     _securitya@macncheese
  Date:         Tue Jun  2 06:23:36 2020
  Revision:     1037.140.39 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1103.2.29.8
$IBIOSI$    MP71.88Z.F000.B00.2006020623
Copyright (c) 2005-2020 Apple Inc.  All rights reserved

2019 Mac Pro tracking table updated:

 

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Answered several times, search is your friend.

BootROMs are unique, you can't use a dump from one Mac to another. When you use a BootROM from one Mac Pro on another you are cloning it. Apple detect this clones, since the MACAddresses are not stored inside the BootROM, and blocks iCloud/FaceTime/Messages.

Mac BootROMs are a lot more complex than PC UEFI firmwares or BIOS, Apple saves much more unique serialising/tracking data inside than a PC.

If your theory about the way the PCIe slots are initialised since 138.0.0.0.0, is correct, install PCIe tools and downgrade the slot that your card is installed back to PCIe v1.0. Someone made a script for this some time ago on another thread.

still searching for this tool. I have confirmed the latest bootrom breaks this PCI express card. I actually have a macpro4,1 and replaced it with a 4,1 logic board and the eBay seller updated the bootrom to 144... I am still searching for this tool in desperation.
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,601
still searching for this tool. I have confirmed the latest bootrom breaks this PCI express card. I actually have a macpro4,1 and replaced it with a 4,1 logic board and the eBay seller updated the bootrom to 144... I am still searching for this tool in desperation.
Search for threads with setpci, you want the reverse of people usually want, set MP3,1 PCIe slots from the default PCIe v1.0 to v2.0, but it’s exactly the same process.

Screen Shot 2020-06-09 at 20.33.55.png


Anyway, you can always pay a firmware engineer with Mac Pro experience to reconstruct your BootROM image back to MP51.0089.B00, the last version without the PCIe v2.0 default.
 
Last edited:
  • Like
Reactions: osxfr33k

frenchfrys

macrumors newbie
Jun 14, 2020
2
0
Hi @tsialex

I was hoping you could check my BootRom that I have extracted for my MacPro5,1 - I think it has the Security Certificate on the NVRam? But to be honest I'm not 100% sure what I should be looking for, and If I do find it how to fix the problem?

I'm 99% sure I have installed windows using UEFI so wouldn't be surprised if the rom has the issue.

My goal is to install 144 without a Metal GPU and then run Windows 10 (legacy)

Thanks for your help!

Code:
DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
24972         0x618C          CRC32 polynomial table, little endian
35787         0x8BCB          mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
524288        0x80000         UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
549260        0x8618C         CRC32 polynomial table, little endian
560075        0x88BCB         mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
1048576       0x100000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1064960       0x104000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1065216       0x104100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-01-24, rev 0x001c, size 11264
1076480       0x106D00        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1084672       0x108D00        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-01-23, rev 0x001e, size 10240
1114112       0x110000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1130496       0x114000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1130752       0x114100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-01-24, rev 0x001c, size 11264
1142016       0x116D00        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1150208       0x118D00        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-01-23, rev 0x001e, size 10240
1179648       0x120000        UEFI PI Firmware Volume, volume size: 196608, header size: 1, revision: 0, Variable Storage, GUID: FFF12B8D-7696-4C8B-85A9-2747075B4F50
1202824       0x125A88        XML document, version: "1.0"
1343511       0x148017        bzip2 compressed data, block size = 100k
1376256       0x150000        UEFI PI Firmware Volume, volume size: 2686976, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
4063232       0x3E0000        UEFI PI Firmware Volume, volume size: 65536, header size: 1, revision: 0, GUID: E3B980A9-5FE3-48E5-929B-2798385A9027
4128768       0x3F0000        UEFI PI Firmware Volume, volume size: 65536, header size: 0, revision: 0, Apple Boot Volume, GUID: 04ADEEAD-61FF-4D31-BAB6-64F8BF901F5A
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.