MP 1,1-5,1 MacPro5,1: What you have to do to upgrade to Mojave (10.13/10.14 BootROM upgrades instructions thread)

[GreyT-Drumming]

Please read the first post of the thread…
[automerge]1584550326[/automerge]

This has nothing to do here, for NVMe compatibility, check the first post of the thread:

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

Good advise, and I did, look at it again. And after printing it out I followed the 'prescription', I found the Mojave dowload place via the link to 'app store'. after some waiting and goofing around holding many different keycombos the macpro booted and asked me to install Mojave. well just out of curiosity I first checked the bootrom version and Herureka it was now 144.0.0.0.0. and just to make sure YES the blade was now a bootable drive, so I chose to install Mojave on the blade, while High Sierra still resided on the SSD sata drive.

Next I was asked if I wanted to copy settings? YES it took some time but then the new Mojave installation had copied all from my actual High Sierra Timemachine disk, and I was set to go, all software installed as before, and loading much faster.

I only have one blade in a simple PCIe card, but this summer I intend to go for the Amfeltec Squid board and make a raid on it too. then I will only use the sata drives for timemachine and databackup.
One of the benefits of getting the newest bootrom is that now my dropbox can reside on the blade too.

The one thing not totally in place is the graphic card. I have an NVIDIA card which is great, but drivers are for high Sierra, so it runs in native apple mode, which is ok but not that flexible, so I will get a Sapphire Pulse Radeon RX 580 8GB card soon.

So thank you to all those whose input have inspired me, and maybe my findings will inspire others too.
Palle

 

[ktfelker]

Hey tsialex,
This thread was super helpful in helping get my 5,1 to load Mojave - the DVI Only output on my RX580 was the saving grace - who knew?
Anyway, wondered if i could get your opinion: I upgraded to Mojave, and now i can not run Messages. Is it possible to fix, or will i have to go back to High Sierra ( i can not run Catalina because i use Avid Media Composer). And if i do go back to High Sierra, will this problem persist because i flashed the Boot Rom up to 14.0.0?
THANKS!

 

[kohlson]

After a series of updates - 4,1-> 5,1; firmware upgrades; firmware cleanup/up - Messages stopped working on my cMP. I tried quitting and logging out and re-installing. Old messages were there, but new messages could neither be sent nor received. Not the worst - my phone is right there - but still.
While I have upgraded the OS a couple of times, nothing seemed to work. But recently I did both an SMC and NVRAM reset. Lo and behold - it works again. So give these a try before reverting. I'm on 10.14.6.

Also, you're fine with a "later" firmware than the OS.

 

[tsialex]

Hey tsialex,
This thread was super helpful in helping get my 5,1 to load Mojave - the DVI Only output on my RX580 was the saving grace - who knew?
Anyway, wondered if i could get your opinion: I upgraded to Mojave, and now i can not run Messages. Is it possible to fix, or will i have to go back to High Sierra ( i can not run Catalina because i use Avid Media Composer). And if i do go back to High Sierra, will this problem persist because i flashed the Boot Rom up to 14.0.0?
THANKS!

Some Macs don't work with Messages after Sierra because the BootROM are missing hardwareIDs. Usually it's a problem related to replacement backplanes that are not correctly serialised.

If it's the case, only a BootROM reconstruction will solve this problem. Upgrading or downgrading the BootROM don't correct this, only re-inserting the missing hardwareIDs.

 

[ktfelker]

Jesus... How do i do this? Is it as simple as flasing the boot rom with an older version? Guess not - how about going back to High Sierra? can i ?

 

[tsialex]

Jesus... How do i do this? Is it as simple as flasing the boot rom with an older version? Guess not - how about going back to High Sierra? can i ?

I don't understand your question, since I already told you that upgrading, downgrading is not allowed anymore, the BootROM won't solve the problem at all.

Sierra version of Messages usually works fine with missing hardwareIDs, with High Sierra working with some cases and Mojave don't work at all.

Reconstruction is a complex process and it's a last resort only, since involves lot's of my time and your effort to gather all the needed info.

 

[ktfelker]

Got it, right, my apologies... i asked the wrong question. My main question is, and i think you've answered it, that if i re-install High Sierra, will it work again. And i think you're saying most likely it will ... and no, i don't want to get involved in all that id number stuff, that's out of my league.
Thanks for all your help!!!! You've been a godsend!

 

[tsialex]

Got it, right, my apologies... i asked the wrong question. My main question is, and i think you've answered it, that if i re-install High Sierra, will it work again. And i think you're saying most likely it will ... and no, i don't want to get involved in all that id number stuff, that's out of my league.
Thanks for all your help!!!! You've been a godsend!

Since Apple started to up the security of Messages with each new release of macOS, missing hardwareIDs makes the authentication servers to reject the login.

Sierra version of Messages usually works fine, Sierra is obsolete since Catalina was released and don't get Security Updates anymore, but High Sierra is tightening the authentication process at each new Security Update, people that didn't had authentication problems back when High Sierra was released are having it now.

 

[ktfelker]

Interesting... I can't go to Catalina yet because i use Avid Media Composer, and Avid is badly broken in 10.15, but i wanted some of the functionality of Mojave.
Ultimately my question is : did the firmware update i did to load Mojave ruin my ability to run Messages if i go back to High Sierra? If I'm understanding you, that frimware update may not matter? Either way, i suppose i haver to try, which i am... It either works or it doesn't, and if no, then I'll just have to work around it.
Again, thank you so much for your help and knowledge.
Obrigado!

 

[tsialex]

Interesting... I can't go to Catalina yet because i use Avid Media Composer, and Avid is badly broken in 10.15, but i wanted some of the functionality of Mojave.
Ultimately my question is : did the firmware update i did to load Mojave ruin my ability to run Messages if i go back to High Sierra? If I'm understanding you, that frimware update may not matter? Either way, i suppose i haver to try, which i am... It either works or it doesn't, and if no, then I'll just have to work around it.
Again, thank you so much for your help and knowledge.
Obrigado!

Messages authentication problems are not EFI firmware related and I already explained to you that Apple is tightening the security validation, Macs that have missing hardware IDs that worked back when High Sierra was released don't work now with 10.13.6 + recent Security Updates. You can't change that, the authentication is remote, the only thing that you can do to solve this issue is to replace the whole backplane or contract someone capable to reconstruct your BootROM adding the missing info and correcting the several checksums, there's nothing else a user can do.

What is called a BootROM is in reality a big package that contains different things. A MP5,1 BootROM contains:

1. The EFI firmware - it's identical for all Macs that run the same version. It's what Apple upgrades when new firmware versions are released, like from 140.0.0.0.0 to 144.0.0.0.0.
2. The NVRAM volume - it's unique to each Mac and stores almost all hardwareIDs [ override version, hardware descriptor (base_XX), SSN, HWC, SON, Gaid ]. The NVRAM volume consists of five different parts, some are dynamic and some are immutable. The immutable part of the NVRAM is where most of the hardwareIDs are stored. Each part of the NVRAM is validated via checksums, an incorrect NVRAM volume cause weird things and can easily make a Mac un-bootable or behave unpredictable.
3. The BootBlock - it's the same for all Macs that run the same BootBlock version. While the BootBlock can be upgraded and Apple used several different versions of the BootBlock code during the MP5,1 production run, Apple don't ever upgrade it and the version installed during the backplane manufacture time will be there forever. When a BootROM reconstruction is done, the BootBlock code is updated to the current version.
4. The MLB sector, where the Mac Pro backplane (MainLogicBoard) serial number (not the SystemSerialNumber) and the build date are stored. MLB sector is unique for each Mac. The MLB sector is validated via checksums and wrong modifications would make your Mac un-bootable.

People usually refers to the whole BootROM as the EFI firmware, while the EFI firmware is the most important thing inside the BootROM, it's just part of it.

If you want to know more, use the search and find older posts where I explain this in every detail.

 

[ktfelker]

Thanks for all this. I might have bricked my 5,1 now since it wont boot or go into recovery. Didn't take my own advice to reformat and reinstall the operating system, then move over the files. Oh well...

Thanks for all your help

 

[tsialex]

Thanks for all this. I might have bricked my 5,1 now since it wont boot or go into recovery. Didn't take my own advice to reformat and reinstall the operating system, then move over the files. Oh well...

Thanks for all your help

Remove all disks from your Mac Pro, install an empty drive, connect a createinstallmedia USB key with macOS installer and then clear the NVRAM 3-times sequentially. Now your Mac Pro will boot from the USB createinstallmedia key and you can install macOS to the empty drive.

This process works with RX 580, if you are asking.

 

[ktfelker]

Thanks! I should have read this first, but all is not lost, i have an old drive with a functioning operating system. And booted up, though i did switch back to my old radeon - just in case - so I am up and working again, and can reformat and install the OS to the SSD. Pretty much like i did before. fingers crossed -
Thanks again!

 

[foonon]

Is there any reason to upgrade from 140.0.0.0.0 to 144.0.0.0.0 if I'm already running Mojave (10.14.6)?


~f

 

[Macschrauber]

run the full installer from High Sierra and you get the firmware update.

Always a good idea: Make a backup of your current firmware with DosDude's RomTool.

 

[foonon]

run the full installer from High Sierra and you get the firmware update.

Always a good idea: Make a backup of your current firmware with DosDude's RomTool.

Not my question...why would I *want* to do that? Is there a list of bugs that are fixed published somplace?

 

[tsialex]

Not my question...why would I *want* to do that? Is there a list of bugs that are fixed published somplace?

All the info about each updates are on the first post table.

Apple don't provide a public accessible changelog for firmwares releases, while detailed changelogs exist, it's only accessible internally.

 

[crjackson2134]

Is there any reason to upgrade from 140.0.0.0.0 to 144.0.0.0.0 if I'm already running Mojave (10.14.6)?


~f

If it's working well for you with no specific complaints or goals to satisfy, then there is no immediate need to change anything. I had a very specific issue related to booting, that went away after 144.0.0.0.0 was installed on my machine.

 

[foonon]

If it's working well for you with no specific complaints or goals to satisfy, then there is no immediate need to change anything. I had a very specific issue related to booting, that went away after 144.0.0.0.0 was installed on my machine.

I'm getting the prohibitory symbol when I boot sometimes (esp after the last two OS updates). I am still able to manually select the boot drive, so I'm not too bothered but it can be annoying.

Was your problem similar?

 

[crjackson2134]

I'm getting the prohibitory symbol when I boot sometimes (esp after the last two OS updates). I am still able to manually select the boot drive, so I'm not too bothered but it can be annoying.

Was your problem similar?

I had no pre-boot screens so I couldn't say for sure about that. I only knew that I randomly couldn't boot on initial try.

 

[cdiepenheim]

Hi all esp Tsialex,

Please need some help with a random rebooting MP 5,1 with a 580Rx see https://forums.macrumors.com/thread...-rx-580-random-restarts.2120481/post-28343803

I really don't know what to do anymore... cost me weeks... I am working now at my old Mini 2011

 

[tsialex]

Hi all esp Tsialex,

Please need some help with a random rebooting MP 5,1 with a 580Rx see https://forums.macrumors.com/thread...-rx-580-random-restarts.2120481/post-28343803

I really don't know what to do anymore... cost me weeks... I am working now at my old Mini 2011

Go back to the basics, test your GPU with a PC, then test it with another Mac Pro. Test another GPU, with similar power draw, with your Mac Pro.

144.0.0.0.0 EFI version has nothing to do with your restarts or everyone that have a RX 580 would have it too.

You problem is one of or more than one below:

• defective GPU,
• Mac Pro slot problem (check with another slot),
• Mac Pro defective PSU,
• Mac Pro backplane problem,
• unlike, but possible, defective power cables.

 

[cdiepenheim]

Go back to the basics, test your GPU with a PC, then test it with another Mac Pro. Test another GPU, with similar power draw, with your Mac Pro.

144.0.0.0.0 EFI version has nothing to do with your restarts or everyone that have a RX 580 would have it too.

You problem is one of or more than one below:

• defective GPU,
• Mac Pro slot problem (check with another slot),
• Mac Pro defective PSU,
• Mac Pro backplane problem,
• unlike, but possible, defective power cables.

hey Tsialex, well I am testing now with my older 7970 and sofa still no reboots, using same slot (I checked them all) can boot in Catalina too (Dosdude) and I testing it long now. boot at every boot part I have for checking if thats the reason. Ok these have diff cables then the 580 8GB Pulse.
I come back on it.

 

[wonderspark]

So, I've managed to somehow update to 10.13.6, and it looks like no issues, but I'm still on MP51.0085.B00

Is there any reason to go through the effort of updating the firmware to 0089? I've got a clone of my boot drive when it was still the most recent Yosemite, and I could just boot to that, then clone the High Sierra disk back to a Yosemite disk, and try again, couldn't I? Or just leave it be?

 

[tsialex]

So, I've managed to somehow update to 10.13.6, and it looks like no issues, but I'm still on MP51.0085.B00

Is there any reason to go through the effort of updating the firmware to 0089? I've got a clone of my boot drive when it was still the most recent Yosemite, and I could just boot to that, then clone the High Sierra disk back to a Yosemite disk, and try again, couldn't I? Or just leave it be?

MP51.0085.B00 is the third worst ever released Mac Pro firmware version. Riddled with APFS bugs and vulnerable to Spectre and Meltdown, it's only the third worst because the worst of all, 142.0.0.0, bricked W3xxx Xeons and the second worst, MP51.0087.B00, didn't even had Intel microcodes inside bricking people that had Windows UEFI installed. Don't use superseded firmware versions.

Follow the first post instructions on how to update to the current BootROM release, 144.0.0.0.0.