Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I thought so. There is no official Bootcamp drivers for Windows 10 on Mac Pro 5.1
There isn't installers for Mac Pro firmwares. Please read the first post of the stickie thread to know what you have to do:
MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)
Please fully read this first post, you will probably find that you have one or more problems described into the various notes below. Mojave will only install if you have upgraded your BootROM to the current release and your Mac Pro have a Metal capable GPU*. If you are trying to install Mojave...
forums.macrumors.com
BTW, this is linked on the post that you quoted…
Don´t you feel sometimes frustrated?There isn't installers for Mac Pro firmwares. Please read the first post of the stickie thread to know what you have to do:
MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)
Please fully read this first post, you will probably find that you have one or more problems described into the various notes below. Mojave will only install if you have upgraded your BootROM to the current release and your Mac Pro have a Metal capable GPU*. If you are trying to install Mojave...
BTW, this is linked on the post that you quoted…
Yes, but when this type of question arises (most of the time from people googling) I follow the link and add the stickie thread to it with giant letters, for the next person to see it immediately.
We don´t deserve you. Thanks for all your hard work.
Ahh i see. Do you know whether or not I would be able to reinstall windows using something like OpenCore?
Really, no idea. I
No experience with OpenCore. So sorry. I use Windows 7, two displays in a Mac 3,1. Wiorks like a charm. In my Mac Pro 5,1 I´m not able to boot Windows at all. I think my IOcrest card doesn´t allow.
@tsialex as you've evolved your theory regarding 5,1 NVRAM corruption - relating it to entries from the first store invading the second one as old entries stop being erased - have you had any further thoughts/insights/or seen any cases in the wild since the above post regarding the risk of MP6,1's suffering from NVRAM corruption due to similar reasons?
Since it's newer and Apple doubled the size of the MP6,1 SPI flash memory, with more NVRAM stores, it's very rare at this point in time to see late-2013 Mac Pro bricks, but dumps people sent me show the same process happening over time.
Late 2013 Mac Pro have another problem that will make it die like flies some point in the future, you can't flash it easily like with a MP5,1 since MP6,1 don't have Firmware Programming Mode and an end user can't easily flash a reconstructed SPI image, you have to physically access the flash memory to program it - this is a security feature implemented by Apple against permanent implants.
I think I already written about it before, a binwalk of a MP6,1 dump that have BootCamp Windows 10 is crazy frightening when you see it, there are several SecureBoot certificates all over the NVRAM of the stores.
I already developed the reconstruction process for MP6,1, it's a little more complex than for a MP5,1. @CodeJingle asked me back in the day, but I never really tested it since I don't own one - still crazy expensive on this side of the globe.
Please note that binwalk is a framework, it will only show things that it has signatures for detection and is barely useful for MP5,1 firmwares since the framework knows nothing about Mac Pro firmwares.
It's not very useful at all if you don't know how to correctly use it and interpret the data.
This is a standard binwalk of a 2010 Mac Pro that has UEFI Windows 10:
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
1187566 0x121EEE Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1253102 0x131EEE Certificate in DER format (x509 v3), header length: 4, sequence length: 986
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-64F8BF901F5AThis is the exactly same binwalk report, but with my own diagnostic tools signatures:
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: (i)
1181814 0x120876 NVRAM MemoryConfig type: (j)
1186748 0x121BBC NVRAM SIP state, type: (w)
1187566 0x121EEE Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1190681 0x122B19 NVRAM MemoryConfig type: (g)
1192729 0x123319 NVRAM MemoryConfig type: (h)
1245255 0x130047 NVRAM start of the 2nd VSS stream
1245302 0x130076 NVRAM MemoryConfig type: (i)
1247350 0x130876 NVRAM MemoryConfig type: (j)
1252284 0x131BBC NVRAM SIP state, type: (w)
1253102 0x131EEE Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1256217 0x132B19 NVRAM MemoryConfig type: (g)
1343511 0x148017 bzip2 compressed data, block size = 100k
1345181 0x14869D HardwareID Base_xx: 21
1345190 0x1486A6 HardwareID 11-digits SSN: redactedEUH
1345207 0x1486B7 HardwareID 3-digit HWC model: EUH
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.1904121247
4194000 0x3FFED0 HardwareID MLB/LBSN: redactedBH9, BuildDate: redacted
The 6,1 got a BootROM update. Version 423.0.0.0.0. (This was in the first 11.0.1 build. The release candidate has firmware version 425.0.0.0.0.)
It includes a revised startup chime. It sounds similar, but not exactly the same. See if you can hear the difference. Remove .txt from the file names to play.
It includes a revised startup chime. It sounds similar, but not exactly the same. See if you can hear the difference. Remove .txt from the file names to play.
Last edited:
Please if someone can help on the issue ... I have cmp 4.1 flashed to 5.1. After that i did try to instal high sierra. Went outside during install screen, and when I come back I had only black screen. On, off and all other solutions did not help, no signal no chime. So i took the Chip out and flash it with MP51.007F.03B. When i return chip back to logic board i have chime and picture (hdd is out). Then i turn it off and turn it back one and same problem as before ( no chime no video). Than i did all procedures again, reflash it, return chip to board ... 1st time on have chime and picture, restart and its dead again. Thanks in advance.
Did you installed a brand new SPI flash? A ~11 year heavily used one is probably dead already.
Hi, and thanks for fast reaponse. It’s the old one. But the logical thinking is, if the SPI is dead I would not be able to erase it and rewrite it again (just the opinion, correct me if iam wrong). And i did 2 times and every time when i solder it back it would work only for the 1st time turn on. Could this bold one truly be the issue, LOL and thank you man.
Attachments
Last edited:
One thing is using a slow SPI flash programmer using a safe programming algorithm, another totally different one is the backplane writing NVRAM data at the fastest supported SPI frequency. Never install an original SPI flash memory back, you can buy a brand new MX25L3206E from a reputable reseller for less than $2 + shipping.
Use 144.0.0.0.0 MP51.fd from the 10.14.6 Mojave full installer, not an ancient BootROM. Btw, you won't login to iCloud/iMessage/FaceTime with the generic upgrade image, no hardwareIDs on it at all.
No, it's a requirement, without hardwareIDs your Mac Pro login is rejected on any Apple service that requires hardware identification. You have to be sure that the problematic backplane is working perfectly before the reconstruction.
Ok got it. I already flash it and solder it back to motherboard and as said this is what i got (pls see the picture) so I am thinking board is ok. Can i continue to install osx. And afterwards you can help me with rebuilding bootrom for my mac. I read it somewhere that it takes you up to an hour so i want to be grateful for your efforts and time.(After I fully test the board and all the other components).
Attachments
Just sharing an excerpt of a totally boring NVRAM volume that really caught my eye today, a completely new BootBlock version!
I really wasn't expect to see that BootBlock version AAPLEFI1.88Z.0004.I00.0908061259.
Code:
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
240027 0x3A99B BIOS version: MP41.88Z.0081.B07.0910130729
764315 0xBA99B BIOS version: MP41.88Z.0081.B07.0910130729
1179688 0x120028 NVRAM start of the 1st VSS stream
1183321 0x120E59 NVRAM MemoryConfig type: (i)
1185687 0x121797 NVRAM SIP state, type: (w)
1186304 0x121A00 NVRAM MemoryConfig type: (g)
1188352 0x122200 NVRAM MemoryConfig type: (h)
1190400 0x122A00 NVRAM MemoryConfig type: (i)
1345189 0x1486A5 HardwareID Base_xx: 20
1345198 0x1486AE HardwareID 11-digits SSN: redactedE1C
1345215 0x1486BF HardwareID 3-digit HWC model: E1C
1416499 0x159D33 BIOS version: MP41.88Z.0081.B07.0910130729
4128867 0x3F0063 BootBlock version: AAPLEFI1.88Z.0004.I00.0908061259I really wasn't expect to see that BootBlock version AAPLEFI1.88Z.0004.I00.0908061259.
Nothing practical, it's more a historical curiosity to see the BootROM evolution than anything else. 11 years later and we are slowly finding BootROMs releases that we never new that existed before in the wild.Cool, but what does that mean more exactly?
The BootBlock is not changed when you upgrade the firmware version via Apple efiflasher, so it's the best way to track the original firmware version that was installed back in the factory and why we now know that existed so much more BootROM releases than what Apple ever published on the support site.
This is the updated table of MP4,1 and MP5,1 BootROMs, some releases are not complete and for the incomplete ones like MP51.007F.B01 and MP51.007F.B02 we have the data from a table inside efiflasher while the rest are from dumps.
EFI Release vs BIOS Version vs BootBlock Version Reference Table:
| EFI Release: | BIOS Version: | BootBlock Version: |
|---|---|---|
| MP41.0081.B04 | MP41.88Z.0081.B04.0903051113 | AAPLEFI1.88Z.0004.I00.0901121311 |
| MP41.0081.B?? | MP41.88Z.0081.B?? | AAPLEFI1.88Z.0004.I00.0908061259 |
| MP41.0081.B07 | MP41.88Z.0081.B07.0910130729 | AAPLEFI1.88Z.0004.I00.0910130728 |
| MP41.0081.B08 | MP41.88Z.0081.B08.1001221313 | AAPLEFI1.88Z.0004.I00.1001221311 |
| MP51.007F.B00 | MP51.88Z.007F.B00.1008031144 | AAPLEFI1.88Z.0005.I00.1006041028 |
| MP51.007F.B?? | MP51.88Z.007F.B?? | AAPLEFI1.88Z.0005.I00.1007141219 |
| MP51.007F.B01 | MP51.88Z.007F.B01.1008231310 | AAPLEFI1.88Z.0005.I00.? |
| MP51.007F.B02 | MP51.88Z.007F.B02.1009221128 | AAPLEFI1.88Z.0005.I00.? |
| MP51.007F.B03 | MP51.88Z.007F.B03.1010071432 | AAPLEFI1.88Z.0005.I00.1010071430 |
| MP51.0083.B00 | MP51.88Z.0083.B00.1707271620 | AAPLEFI1.88Z.0005.I00.1707271617 |
| MP51.0084.B00 | MP51.88Z.0084.B00.1708080528 | AAPLEFI1.88Z.0005.I00.1708080525 |
| MP51.0085.B00 | MP51.88Z.0085.B00.1802021746 | AAPLEFI1.88Z.0005.I00.1802021742 |
| MP51.0087.B00 | MP51.88Z.0087.B00.1804181525 | AAPLEFI1.88Z.0005.I00.1804181521 |
| MP51.0089.B00 | MP51.88Z.0089.B00.1806081708 | AAPLEFI1.88Z.0005.I00.1806081704 |
| 138.0.0.0.0 | MP51.88Z.F000.B00.1807300628 | AAPLEFI1.88Z.0005.I00.1807300627 |
| 139.0.0.0.0 | MP51.88Z.F000.B00.1808171030 | AAPLEFI1.88Z.0005.I00.1808171029 |
| 140.0.0.0.0 | MP51.88Z.F000.B00.1809191555 | AAPLEFI1.88Z.0005.I00.1809191554 |
| 141.0.0.0.0 | MP51.88Z.F000.B00.1812191621 | AAPLEFI1.88Z.0005.I00.1812191620 |
| 142.0.0.0.0 | MP51.88Z.F000.B00.1902142049 | AAPLEFI1.88Z.0005.I00.1902142048 |
| 144.0.0.0.0 | MP51.88Z.F000.B00.1904121248 | AAPLEFI1.88Z.0005.I00.1904121247 |
Last edited: