MP 1,1-5,1 4,1->5,1 Firmware Update and early OS Compatibility

[GoJohnGo]

I'm considering flashing my 4,1 to a 5,1 and am curious if the firmware updates (currently at MP41.0081.B07) affect early OS compatibility. For example, Everymac.com states my early 2009 originally shipped with 10.5.6. If I flash it to a 5,1, does that mean the earliest version it will work with is what the 5,1 originally shipped with (10.6.4)?

Does the same apply for subsequent firmware updates? If not, do the firmware updates still work with an OS earlier than the one they were released with? I'm curious whether I could update to the latest (144.0.0.0.0) then boot 10.5.6 from an NVMe drive. No real need, but I just get nostalgic sometimes and want to play in a colorful jelly bean interface for a while.

Lastly, if for some reason I want to revert to MP41.0081.B07 after running an update, is it possible?

 

[tsialex]

I'm considering flashing my 4,1 to a 5,1 and am curious if the firmware updates (currently at MP41.0081.B07) affect early OS compatibility. For example, Everymac.com states my early 2009 originally shipped with 10.5.6. If I flash it to a 5,1, does that mean the earliest version it will work with is what the 5,1 originally shipped with (10.6.4)?

Correct.

Does the same apply for subsequent firmware updates?

No.

If not, do the firmware updates still work with an OS earlier than the one they were released with?

Yes.

Read the first post of the thread below:

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

I'm curious whether I could update to the latest (144.0.0.0.0) then boot 10.5.6 from an NVMe drive.

NVMe support starts with Sierra for 4096 bytes/sector NVMe blades and High Sierra for 512 bytes/sector.

Read the first post of the thread below:

PCIe SSDs - NVMe & AHCI

This is a general info thread for blade SSDs that can be used in the Mac Pro. This is a WikiPost so anyone with the proper credentials may edit it. NVMe SSDs can be used as a boot drive in the MP5,1 and MP6,1 with the latest firmware installed (beginning with version 140.0.0.0.0 for MP5,1 and...

forums.macrumors.com

No real need, but I just get nostalgic sometimes and want to play in a colorful jelly bean interface for a while.

Not possible, NVMe disks are completely ignored before Sierra/HighSierra.

Lastly, if for some reason I want to revert to MP41.0081.B07 after running an update, is it possible?

If you dump the BootROM image before with ROMTool, yes.

Index of /apps/

ROMTool zip file password is "rom".

 

[GoJohnGo]

Thanks for such a detailed answer; I appreciate it.

 

[machinist68]

Hi all, happy to be here & hope this is the right thread. Having issue updating firmware to 5,1. Have read most of the relevant posts & sites pertaining to patchers, firmware tools, opencore, GPU's etc. on the interweb over the last month or so. Joining the forum is a new experience for me in an effort to solve this issue & only one other person I've found in the last 3 weeks of searching (no one answered his question) has the same problem.

I have disabled SIP & double checked the "status" of SIP, re-seated memory, used a different SSD, allowed all software to install in system security applet, using wired internet, allowed all connections through firewall, toggled firewall on & off, tried both versions of the firmware update tool (netkas & ifixit), mounted firmware before using tool in same directory & so on.

When running the firmware tool, the option buttons for upgrade to 2010 or re-loading 4,1 firmware are greyed out. After approximately 15 seconds, a message appears just above the initial firmware message & reads: "This tool requires access to the internet, please connect to the internet & try again". As you may guess, I am connected to the internet using the onboard Nic.

Crucial DDR3
GT 120
Clean install 10.11.6

 

[tsialex]

Look, maybe I'm biased, but why go this route?

You can get your BootROM image fully cleaned, all modules upgraded to the most recent releases and reconstructed to 144.0.0.0.0 professionally instead of butchering it with the cross-flashing process.

Even if you have to do it on the cheap, save a BootROM image dump before the cross-flashing process, so you have a BootROM image dump unmodified for a reconstruction later on.

 

[machinist68]

Look, maybe I'm biased, but why go this route?

You can get your BootROM image fully cleaned, all modules upgraded to the most recent releases and reconstructed to 144.0.0.0.0 professionally instead of butchering it with the cross-flashing process.

Even if you have to do it on the cheap, save a BootROM image dump before the cross-flashing process, so you have a BootROM image dump unmodified for a reconstruction later on.

Thanks for the quick response & suggestions, allow me to elaborate on what my objective is with this machine. I'm interested in getting this machine updated to 5,1 firmware by whatever means is appropriate for stability & longevity.

I do not intend to use OpenCore.

I have purchased a matched pair of de-lidded X5675s, a couple of metal supported GPU's, & a 64GB memory kit. I also own a 2010 MP 5,1 single CPU that has been upgraded to 6-core 3.3Ghz & running 10.13 (my Protools/Logic rig). I want to take my 4,1 to where I'm at with my 2010 box using official hardware & software & eventually take it to Mojave with one of the GPU's I purchased, hopefully with the help of folks like you on this forum.

Just found your BootROM thread.... looks like another 239 pages of reading material =0

Would you be willing to elaborate on whether I'm on the right track? Also, where or who would be able to do the work you mentioned in regards to upgrading modules & getting the BootROM squared away so I can price that out?

Thank you for your time,

machinist68

 

[tsialex]

Thanks for the quick response & suggestions, allow me to elaborate on what my objective is with this machine. I'm interested in getting this machine updated to 5,1 firmware by whatever means is appropriate for stability & longevity.

Ok.

I do not intend to use OpenCore.

I have purchased a matched pair of de-lidded X5675s, a couple of metal supported GPU's, & a 64GB memory kit. I also own a 2010 MP 5,1 single CPU that has been upgraded to 6-core 3.3Ghz & running 10.13 (my Protools/Logic rig). I want to take my 4,1 to where I'm at with my 2010 box using official hardware & software & eventually take it to Mojave with one of the GPU's I purchased, hopefully with the help of folks like you on this forum.

Just found your BootROM thread.... looks like another 239 pages of reading material =0

Would you be willing to elaborate on whether I'm on the right track?

Not by cross-flashing an early-2009 BootROM image to MP5,1.

The BootROM is an image that contains hundreds of components, most of them EFI related, cross-flashing process mix and match several major MP4,1 that are not EFI related with the MP5,1 EFI, like the NVRAM and BootBlock - this will get you a brick in the long run.

If you just want to use a MacPro for some time and get rid of it, no doubt cross-flash it, but if you want it working like a real mid-2012 Mac Pro and have the BootROM working for years like you wrote, don't do it and invest on a reconstruction.

Also, where or who would be able to do the work you mentioned in regards to upgrading modules & getting the BootROM squared away so I can price that out?

Thank you for your time,

machinist68

I've sent you a PM.

 

[Kobura85]

Ok.



Not by cross-flashing an early-2009 BootROM image to MP5,1.

The BootROM is an image that contains hundreds of components, most of them EFI related, cross-flashing process mix and match several major MP4,1 that are not EFI related with the MP5,1 EFI, like the NVRAM and BootBlock - this will get you a brick in the long run.

If you just want to use a MacPro for some time and get rid of it, no doubt cross-flash it, but if you want it working like a real mid-2012 Mac Pro and have the BootROM working for years like you wrote, don't do it and invest on a reconstruction.



I've sent you a PM.Hey, curious about getting an A1418 2017 iMac's EFI chip loaded with a new firmware. I see in 2018 you did a similar job where you had the chips (EFI & SPI) chips removed in some sort of process to get it loaded with something to crack past the firmware lock....Was wondering if you could send me a PM? I can send you all the dets there...

 

[tsialex]

@Kobura85

Long time ago I decided that removing any type of firmware/MDM/iCloud activation locks is something that I wouldn't do. Sorry, but I don't accept this type of job request.