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

MP 1,1-5,1 Can't update from 4,1 to 5,1

leonardobertaso

leonardobertaso

macrumors newbie
Original poster
May 21, 2024
5
0
Hi, I am having the same problem with two Macs with the same configuration when upgrading from 4.1 to 5.1.

Configuration:
Mac Pro 2009 4.1 - MP41.0081.B07
2x 2.6 Xeon
32 GB DDR3 1333 (working at 1066)
1TB SATA ssd

I am following this guide here: https://thehouseofmoth.com/turning-a-2009-41-mac-pro-into-a-2010-2012-51-mac-pro-2021-edition/

The problem is that, with both machines, everything appears to be regular but on reboot, after the sound and flashing of the Front Led, the Macs reboot regularly by booting Mac OS.

I tried to have a look here on the forum but still could not solve the problem.
 
For years dozens of people have been reporting that the Netkas forum cross-flashing tool does not work anymore. Even the updated version on GitHub stopped working sometime around 2022.

The only way today is via BootROM reconstruction service.
 
  • Like
Reactions: leonardobertaso
I provide the BootROM reconstruction service since around 2019, did all the reverse engineering back in 2018, see the main BootROM thread.

I'll send a PM about it.
 
I'm currently trying to install the 5,1 firmware onto my 4,1. The issue is that, on 10.11.6, the program itself runs successfully, but the step for actually applying the update doesn't work, it just boots normally after the tone. The SuperDrive doesn't even open. On earlier versions, it errors out (5530)

The Mac is running B07 and has 3 drives, one on bay 1, another on bay 2, and another on the SATA connector under the optical drive

I suspect that the issue might be caused by the fact that I tried doing it accidentally before disabling SIP. Any solution to this?
 
Not what you wanna read, but the issue is that Netkas forum tool stopped working years ago, there are loads of posts here confirming this.

Btw, even when it worked back in the day, the tool did a very bad job, creating a hybrid of a MacPro4,1 (NVRAM volume) and MacPro5,1 (EFI firmware). The way to solve this once and for all is the BootROM reconstruction service.
 
Last edited:
tsialex said:
Not what you wanna read, but the issue is that Netkas forum tool stopped working years ago, there are loads of posts here confirming this.

Btw, even when it worked back in the day, the tool did a very bad job, creating an hybrid of a MacPro4,1 (NVRAM volume) and MacPro5,1 (EFI). The way to solve this once and for all is the BootROM reconstruction service.
Click to expand...
So what can I do at this point? I want to run an RX 580 on it and it seems that this EFI version is needed for it.
 
afastaudir8 said:
So what can I do at this point? I want to run an RX 580 on it and it seems that this EFI version is needed for it.
Click to expand...

Is not the EFI version itself that makes a RX 580 to work, but the drivers inside macOS. The first macOS release that have driver support for a RX 580 is Sierra 10.12.6, so, no go with El Capitan since there are zero support with it.

I'll send you a PM with all the info about the BootROM reconstruction service, files required, service fee and turnaround time.
 
tsialex said:
I provide the BootROM reconstruction service since around 2019, did all the reverse engineering back in 2018, see the main BootROM thread.

I'll send a PM about it.
Click to expand...
Hi, can you help me to upgrade my two 4.1 dual processor Mac Pro’s to 5.1?
 
Hello, I am attempting this same upgrade to 5,1 from 4,1. I am getting same error, just boots normally after restart. Do you have another solution? I was simply trying to upgrade to 5,1 in order to get a later version of MacOS. El Cap has so many issue with modern software like browsers in particular loading webpages incorrectly
 
Kianes said:
Hello, I am attempting this same upgrade to 5,1 from 4,1. I am getting same error, just boots normally after restart. Do you have another solution?
Click to expand...

Yes, the BootROM reconstruction service solves this once and for all. I've sent you a PM with all the info, required files, service fee and turnaround time.
 
hi guys :
i have mac pro 4.1 with boot rom b08
gt 120
16 giga ram
original hdd

i try to upgrade to 5.1 but fail ..

any one can help me ?
thank you
 
Well known issue, the crossflashing doesn't work anymore. Only way to overcome the problem is manual rebuilding (btw will also avoid some issues of the crossflashing) and flashing the bootrom.

forums.macrumors.com

Can't update from 4,1 to 5,1

Hi, I am having the same problem with two Macs with the same configuration when upgrading from 4.1 to 5.1. Configuration: Mac Pro 2009 4.1 - MP41.0081.B07 2x 2.6 Xeon 32 GB DDR3 1333 (working at 1066) 1TB SATA ssd I am following this guide here...
forums.macrumors.com forums.macrumors.com
forums.macrumors.com

Unable to flash MacPro5,1 firmware onto MacPro4,1 (Update doesn't apply)

I'm currently trying to install the 5,1 firmware onto my 4,1. The issue is that, on 10.11.6, the program itself runs successfully, but the step for actually applying the update doesn't work, it just boots normally after the tone. The SuperDrive doesn't even open. On earlier versions, it errors...
forums.macrumors.com forums.macrumors.com
 
Is it possible to upgrade an 4.1 to 5.1 use MacProEFIUpdate.dmg with the Macschrauber dumper and how?
Thank you!
 
Appler007 said:
Is it possible to upgrade an 4.1 to 5.1 use MacProEFIUpdate.dmg with the Macschrauber dumper and how?
Thank you!
Click to expand...

Nope, extremely bad idea.

If you do it, you will destroy all the factory serialization (SSN, HWC, SON, MLB SN, BD), ports configuration and calibration/fine tuning of sensors since the MP51_007F_03B_LOCKED.fd have nothing but 0xff where all this data were saved back in the production line. Never do it, no iCloud/Messages/FaceTime and any apps that require serialization for licensing purposes will not work anymore.

Running BBS after the damage is done, like some reddit posts suggest as a "solution", won't solve the problem, since an Apple blank replacement backplane already have all the configuration, calibration and serialization saved (HWC, SON, MLB SN, BD) inside the BootROM, except the SSN, while the backplane flashed with the MP51_007F_03B_LOCKED.fd or MP51.fd have absolutely nothing.

BBS was designed to work with an Apple blank board, where just the SSN is missing.
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back