Sure, PM sent. Btw, I always send two images, one standard image exactly like Apple and another one with EnableGopv1_4 already injected.
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
Sure, PM sent. Btw, I always send two images, one standard image exactly like Apple and another one with EnableGopv1_4 already injected.
Hi Alex,
I need help with my bootrom 144. My 2010 5.1 mac pro works very well but MacSchrauber’s tool detects crc errrors e give me the message that the firmware is inconsistent. all the other values are ok. i have an XfX Rx580 not flashed and work nice. i'd like to enable Gop but but i have fear to brick my Mac Pro flashing gop with these crc errors.
Can you help me with reconstuction?
Thanks.
Vito From italy
I need help with my bootrom 144. My 2010 5.1 mac pro works very well but MacSchrauber’s tool detects crc errrors e give me the message that the firmware is inconsistent. all the other values are ok. i have an XfX Rx580 not flashed and work nice. i'd like to enable Gop but but i have fear to brick my Mac Pro flashing gop with these crc errors.
Can you help me with reconstuction?
Thanks.
Vito From italy
Sure, PM sent with instructions/files required/service fee/turnaround time.
I have a Mac pro that's been upgraded from 4,1 to 5,1 - I'm currently running Mojave with open core (Martin Lo 0.7.3.1) I'm wanting to upgrade to Monterey. I got open core 0.9.8. upon checking I see that my boot rom is 9144.0.7.3.1 - do I need a reconstructed Boot Rom? I read that this could help as the 4,1 to 5,1 upgrade was done a while ago. thanks
9144.x.x.x.x and 9999.x.x.x.x are spoofed BootROM release versions, to avoid unwanted firmware upgrades from newer Macs (2019 Mac Pro or iMac Pro are spoofed to run macOS releases after Mojave). Since the spoofed/fake version is being displayed, you should boot native and see the real version.
All cross-flashed early-2009s greatly improve firmware wise with the BootROM reconstruction service, being then equivalent to a mid-2012, especially since the early-2009 incompatible NVRAM volume is repaired and upgraded.
Hi everyone, new to the rumours and interesded in this tread. In short, recenty acquired Mac Pro 4,1 and trying to update firmware to 144 curent one is MP41.0081.B08. Netkas is not working tried and no luck with Jensd's. Read here there is reconstruction method, can someone help with it? Thanks
PM sent with instructions/files required/service fee/turnaround time.
Thanks Alex, will need some time to get all photos and other requirements, but not sure can do:
6. Do a BootRom dump
Also, where to upload folder here on the Forum or send it directly to you?
See the instructions I've sent you by PM, everything needed is there, follow the steps to dump the BootROM image.
Compress the folder with the pictures/SystemInfoReport/BootROM image dump and upload it/attach to the PM thread.
Seems you didn't noticed the un-upgradeable MP41.0081.B08 firmware of factory refurbished early-2009s - he even wrote that Netkas cross-flashing method didn't work.
Adding yet another testimonial for the thoughtful / thorough work of @tsialex who reconstructed my crusty, vintage 5,1 bootrom. I reached out once I saw alarmingly low levels of remaining space after injecting enableGOP successfully. Was a fairly straight forward process, esp using his well organized instructions, worth following to the letter. Was glad to have had a spare SDD with generic install of High Sierra for bay 1 rather than rely on PCI NVMe with Mojave. I feel much better about finally getting set up with OC and Monterey knowing my bootrom is healthy. Easily worth the money and was with me every step. Glad I did it. Alex is the man.
@tsialex I have a Mac Pro 2010 with 2x3.33GHz CPU and 16GB RAM. After running Macschrauber ROM Dump I got 2 errors (see screenshots) related to a Windows Certificate and a Second Header Broken. It appears I have plenty of room in my ROM ~42K. Before I proceed enabling GOP, should I proceed further?
Attachments
Nope, your BootROM image is already corrupt. Try a NVRAM reset, if stays as is, you'll need to repair it.
Use A63 version of UEFITool, not UEFIExtract.
Your BootROM image had an interesting failure mode, the primary VSS store header was the one that became corrupted - usually is the secondary VSS store header.
Since you have 8 x 16GB DIMMs and runs Sonoma, the constant need of the garbage collection process for sure have some responsability here. Everything over pressure breaks sooner or later.
Anyway, repair/clean-up/upgrade done sucessfully!
Hey guys, just wanted to get to the correct thread for BootRom Reconstruction and give a big thanks publically to @tsialex! To me, Bro is a genius! LOL!!😂 He did both of my upgraded Mac Pro 5,1's with chip and firmware updates BootROM Reconstruction and I also had him add "Enable GOP" because I needed multiple displays to continue using with Mountain Lion OS for some tasks in my recording studio. I had him also get my GPU Bios set to work with NVIDIA GTX-680 cards that I purchased used on Facebook Marketplace and eBay and he got me right. Also, somebody direct me to a thread about "Cloning" OPLP hard drives because I found a way to do it fast "Offline" at least with my Monterey rig. Also, I appreciate the connections here on MacRumors.com!
Hello, I owned a 4,1 machine for a bit over 10 years. I also have a metal capable rx480 flashed with EFI compatible firmware. Early on I did the 4,1 -> 5,1 hack and my bootROM has been upgraded to 144.0.0.0.0 however, I booted windows 10 in EFI mode before it was widely known the issues this causes. My machine is still booting os 10.14 but I hope to get a reconstruction service. Alexandre, could you send me a PM?