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.
Just wanted to post, I had 2 Mac Pro's rom reconstruction service by tsialex and both are working great . He was very thorough with what he did and explains in detail. I was able to purchase new chips on line, flash them with the reconstructed ROM files and solder them on the boards. Thanks tsialex
 
  • Like
Reactions: basslik and tsialex
Hi! I've sent you a PM with instructions/files required/service fee/turnaround time.
I have your kit you made for me 3 years ago. I am experiencing Mac Pro 4,1→5,1, NVRAM variables won’t persist, boot device not retained down grading from sequoia to Sonoma. Down to 1 disk running native Mojave and keyboard plus mouse connected. Can’t get to a clean apple state to install Sonoma/open core. Will the kit clean this out go to the replacement back plane?
 
I have your kit you made for me 3 years ago. I am experiencing Mac Pro 4,1→5,1, NVRAM variables won’t persist, boot device not retained down grading from sequoia to Sonoma. Down to 1 disk running native Mojave and keyboard plus mouse connected. Can’t get to a clean apple state to install Sonoma/open core. Will the kit clean this out go to the replacement back plane?

No, you can’t use the reconstructed image from one Mac Pro to another. This is cloning and will be detected and could have all sort of problems with your iCloud.

There is a correct procedure from Apple to “mate” it. Send me a dump from the replacement and I’ll take a look. Also necessary a photo of the MLB label.
 
No, you can’t use the reconstructed image from one Mac Pro to another. This is cloning and will be detected and could have all sort of problems with your iCloud.

There is a correct procedure from Apple to “mate” it. Send me a dump from the replacement and I’ll take a look. Also necessary a photo of the MLB label.
I think I just needed to dump the ROM and apply the one you made for me. I got a message ?DirectHW.kext cannot be loaded. The operation cannot proceed." Is there something I am missing?
 
I think I just needed to dump the ROM and apply the one you made for me.

To the replacement backplane? Don't do it, this will make a fake clone and you will have problems with iCloud and any software that requires serialization down the road.

I got a message ?DirectHW.kext cannot be loaded. The operation cannot proceed." Is there something I am missing?

Use AppCleaner to fully remove ROMTool, then reinstall it.
 
To the replacement backplane? Don't do it, this will make a fake clone and you will have problems with iCloud and any software that requires serialization down the road.



Use AppCleaner to fully remove ROMTool, then reinstall it.
No for the original backplane that you created the boot kit for. Replacing the backplane is last resort if the original backplane cannot be repaired with refreshed BootRom
 
  • Like
Reactions: tsialex
No for the original backplane that you created the boot kit for. Replacing the backplane is last resort if the original backplane cannot be repaired with refreshed BootRom
Well I replaced the backplane. Can I ask you to prepare an updated Boot Rom so I can get back to work? There were other issues with the other board. Current boot rom on the replacement board is

Boot ROM Version: MP51.0084.B00

I will gladly compensate you for your time.
 
Well I replaced the backplane. Can I ask you to prepare an updated Boot Rom so I can get back to work? There were other issues with the other board. Current boot rom on the replacement board is

Boot ROM Version: MP51.0084.B00

I will gladly compensate you for your time.

Sure, please check your PMs.
 
Hi there! (first post!) I've recently started working on my newly acquired Mac Pro (2009) and would love to see if you could help me with a reconstructed boot rom with EnableGop? I'm just getting my battery on the machine replaced and installing mojave for a proper dump for you (as I'm running opencore legacy patcher at the moment on monterey).

Are you still offering this service? Please let me know.
 
Last edited:
Hi there! (first post!) I've recently started working on my newly acquired Mac Pro (2009) and would love to see if you could help me with a reconstructed boot rom with EnableGop? I'm just getting my battery on the machine replaced and installing mojave for a proper dump for you (as I'm running opencore legacy patcher at the moment on monterey).

Are you still offering this service? Please let me know.

I've sent you a PM with instructions/files required/service fee/turnaround time.
 
  • Love
Reactions: animatedbreak
Hello everyone, Im working on a personal project attempting to get a normal X58 motherboard to run on a UEFI Bios. I know the macpro 5,1 has an EFI firmware, just wondering if anyone had a fully unlocked EFI firmware ROM on the newest version (144.0.0.0.0 with NVME support) so i could potentially mod it for use on a conventional X58 motherboard and get UEFI Windows functional. I know I have to change the bios chip to 4MB from 2MB. Thanks.
 
Hello everyone, Im working on a personal project attempting to get a normal X58 motherboard to run on a UEFI Bios. I know the macpro 5,1 has an EFI firmware, just wondering if anyone had a fully unlocked EFI firmware ROM on the newest version (144.0.0.0.0 with NVME support) so i could potentially mod it for use on a conventional X58 motherboard and get UEFI Windows functional. I know I have to change the bios chip to 4MB from 2MB. Thanks.

You can get it yourself from the Mojave installer, MP51.fd is a standard binary image:

Code:
/Applications/Install macOS Mojave.app/Contents/Resources/Firmware/MP51.fd

Btw, is a lot easier to start from another X58 board that supports UEFI than trying to make MacPro5,1 BootROM run on a PC motherboard, SPI size is the least of your problems. MacPro5,1 is too tied to the SMC, which doesn't exist on the PC side.
 
  • Like
Reactions: skeptech
You can get it yourself from the Mojave installer, MP51.fd is a standard binary image:

Code:
Install\ macOS\ Mojave.app/Contents/Resources/Firmware/MP51.fd

Btw, is a lot easier to start from another X58 board that supports UEFI than trying to make MacPro5,1 BootROM run on a PC motherboard, SPI size is the least of your problems.
Dont currently own a mac, so thats my current issue, although i could throw together a hackintosh easily. The problem is no x58 UEFI motherboards exist. The closest thing was a mish mash core i 1st gen with a core i 2nd gen P67 chipset and UEFI bios. Other systems back then did have UEFI bios, so it doesnt make sense that no single x58 motherboard had UEFI as an option. Gigabyte did have some hacky "EFI" bios, but it was not full UEFI. I think the mac firmware is the closest potential candidate. Some x58 motherboard DID have a 4MB bios chip, but i dont know which ones. Thanks
 
You are forgetting that MacPro5,1 is not UEFI also - EFI 1.10.

MacPro5,1 predates UEFI spec by 5 years, does not have SecureBoot and the BootROM NVRAM volume is easily corrupted by Windows SecureBoot signing of the BootROM. UEFI Windows is only stable with a lot of backstage work by OpenCore.
I'm aware that they're not a 1:1 solution, but having NVME bootable from bios is a large step in the right direction.
 
Dont currently own a mac, so thats my current issue, although i could throw together a hackintosh easily. The problem is no x58 UEFI motherboards exist. The closest thing was a mish mash core i 1st gen with a core i 2nd gen P67 chipset and UEFI bios. Other systems back then did have UEFI bios, so it doesnt make sense that no single x58 motherboard had UEFI as an option. Gigabyte did have some hacky "EFI" bios, but it was not full UEFI. I think the mac firmware is the closest potential candidate. Some x58 motherboard DID have a 4MB bios chip, but i dont know which ones. Thanks

You are forgetting that MacPro5,1 is not UEFI also - EFI 1.10.

MacPro5,1 predates UEFI spec by 5 years, does not have SecureBoot and the BootROM NVRAM volume is easily corrupted by Windows SecureBoot signing of the BootROM.

UEFI Windows is only stable with a MacPro5,1 with a lot of backstage work by OpenCore.
 
I'm aware that they're not a 1:1 solution, but having NVME bootable from bios is a large step in the right direction.

If you are starting from this, you gonna have a lot of surprises.

Get a Chinese X58 (it existed 5 years ago) or current selling X79 UEFI firmware and modify it to run on your own board.

Macs are not PCs, won't even work with PC GPUs, zero BIOS menus/configuration since there is no BIOS at all, and etc.
 
Hi @tsialex,
I have a genuine MacPro5,1 (2010) with BootROM 144.0.0.0.0. I have problems installing newer macOS with OCLP; the installer repeatedly fails with MobileSoftwareUpdateErrorDomain Code=53 – Splat global ticket failed to verify.

Macschrauber's Rom Dump reports:

  • Length of 2nd VSS Store is wrong (FF FF FF FF)
  • VSS2 (Formatted) (VSS2 header problem)
  • one unnamed VALID variable
  • only 12110 bytes free of 65464
  • CRC32 checksums OK

NVRAM variables can be written, but do not persist after reboot.
I have the original 4 MB firmware dump.

What to do? 🙂
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.