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

[tsialex]

Perhaps something was lost in translation here. I had two firmware updates to do, the first was to install High Sierra and the preceding FW Update (this may have been a Sierra FW update, if there's such a thing; the newest OS installed I believe was Yosemite). Are you saying the ATI 5770 cannot update to High Sierra?

This is clearly explained in the first post.

1. Any model of the AppleOEM GPUs is required for you to upgrade any of the earlier MacPro5,1 firmwares until you have MP51.0089.B00.
2. High Sierra supported METAL GPU is required when you have MP51.0089.B00. Also if you have any of the earlier Mojave firmwares (138.0.0.0.0 to 142.0.0.0.0), a High Sierra METAL supported GPU is required for you to update to the current 144.0.0.0.0.

 

[KingCornWallis]

This is clearly explained in the first post.

1. Any model of the AppleOEM GPUs is required for you to upgrade any of the earlier MacPro5,1 firmwares until you have MP51.0089.B00.
2. High Sierra supported METAL GPU is required when you have MP51.0089.B00. Also if you have any of the earlier Mojave firmwares (138.0.0.0.0 to 142.0.0.0.0), a High Sierra METAL supported GPU is required for you to update to the current 144.0.0.0.0.

Yes...your first post was quite clear. Perhaps mine wasn't: My ATI Radeon HD 5770 is indeed the stock Mac Edition with native Boot Screen support.

Nothing else was plugged into the computer, internally or externally, except an Apple Keyboard and a Microsoft USB Mouse/Keyboard combo. There should have been nothing preventing my FW update to get to MP51.0089.B00.

I also did not mention that once that previous FW update was installed, I plugged in a Vega 64 and tried to install Mojave/144.0.0.0.0 via USB unsuccessfully prior to doing it successfully inside macOS.

The only other variables are:

1. Newer Apple Wi-Fi/BT Card (stock bluetooth card removed as well)
2. No Disc Drive installed

If those don't sound like issues, then it is still unknown why the Shut Down button in FW Update prompt inside both macOS High Sierra AND Mojave USB installers did not work for me.

 

[tsialex]

Yes...your first post was quite clear. Perhaps mine wasn't: My ATI Radeon HD 5770 is indeed the stock Mac Edition with native Boot Screen support.

Nothing else was plugged into the computer, internally or externally, except an Apple Keyboard and a Microsoft USB Mouse/Keyboard combo. There should have been nothing preventing my FW update to get to MP51.0089.B00.

I also did not mention that once that previous FW update was installed, I plugged in a Vega 64 and tried to install Mojave/144.0.0.0.0 via USB unsuccessfully prior to doing it successfully inside macOS.

The only other variables are:

1. Newer Apple Wi-Fi/BT Card (stock bluetooth card removed as well)
2. No Disc Drive installed

If those don't sound like issues, then it is still unknown why the Shut Down button in FW Update prompt inside both macOS High Sierra AND Mojave USB installers did not work for me.

This is clearly stated on the first post here that does not work and is a waste of time:

- Upgrade firmware from USB note:

Firmware upgrade from USB is not possible unless you have the exact original factory config and if your Mac Pro is mid-2010 or mid-2012. Again, you can’t upgrade Mac Pro firmware from createinstallmedia USB-key.

Don’t waste your time trying, the USB installer asks to upgrade your BootROM, warns that it will do a shutdown for you to enter firmware upgrade mode, but never powers off your Mac Pro. Unfortunately, there are reported cases that shutting down manually bricked the BootROM.

Do it from High Sierra opening the Mojave Mac App Store full installer when you already have MP51.0089.B00 or if your Mac Pro have an earlier BootROM then MP51.0089.B00, from Sierra to High Sierra - see the set-by-step below.

Since you can't have an AppleOEM GPU with Mojave upgrades, installing a METAL GPU changes the factory config, you will never upgrade MP51.0089.B00 to 144.0.0.0.0 booted from a createinstallmedia USB installer of Mojave.

Apple made a ridiculous mistake here with the Mojave installer, probably because Mojave support with MacPro5,1 was an afterthought and the issue was never corrected. Another basic mistake was the Mojave installer not detecting a NVIDIA METAL GPUs when booted from Mojave createinstallmedia USB installer.

Also, with a cross-flashed early-2009 Mac Pro is not possible to upgrade the BootROM from a createinstallmedia USB installer of High Sierra.

 

[KingCornWallis]

"Firmware upgrade from USB is not possible unless you have the exact original factory config and if your Mac Pro is mid-2010 or mid-2012. I've only being successful in upgrading earlier firmwares to the High Sierra MP51.0089.B00, since you need a METAL GPU for Mojave, won't work."

So maybe this is it right here (Anything relating to Mojave is well understood); sorry if it was really there this whole time. If I read this right, it IS possible to upgrade firmware via USB createinstallmedia of High Sierra IF I have a Mid-2010 Mac Pro (not cross flashed) put back into it's stock hardware config? How can it tell what is stock; where is this info stored (outside of the label on the back; looking up SN results in multiple possible configs)...or does it do a database call? Would extra RAM or a larger hard drive (even if still OEM Apple) change this? Genuinely curious on the lack of oversight on Apple's part here...

 

[tsialex]

"Firmware upgrade from USB is not possible unless you have the exact original factory config and if your Mac Pro is mid-2010 or mid-2012. I've only being successful in upgrading earlier firmwares to the High Sierra MP51.0089.B00, since you need a METAL GPU for Mojave, won't work."

So maybe this is it right here (Anything relating to Mojave is well understood); sorry if it was really there this whole time. If I read this right, it IS possible to upgrade firmware via USB createinstallmedia of High Sierra IF I have a Mid-2010 Mac Pro (not cross flashed) put back into it's stock hardware config? How can it tell what is stock; where is this info stored (outside of the label on the back; looking up SN results in multiple possible configs)...or does it do a database call? Would extra RAM or a larger hard drive (even if still OEM Apple) change this? Genuinely curious on the lack of oversight on Apple's part here...

Look, you are trying to get to the bottom of something that simply does not work. Do not waste your time with this.

I'll edit the first post to make even more clear that this is a complete waste of time.

 

[dcouzin]

This newbie is a luddite.
I have a 2012 MacPro5,1. In two of its bays are drives with a variety of bootable volumes, OS 10.6.8 to 10.12.6. I have zero interest in Mohave, APFS, or NVMe storage. I have very small interest High Sierra. My current firmware is MP51.0084.B00. tsialex has semi-convinced me to take its microcodes' vulnerability to Spectre and Meltdown seriously even though my MacPro is online for less than 1 hour per week. He lists firmware MP51.0089.B00 as having "Spectre/Meltdown mitigated microcodes".

Fortunately Apple Store provided an OS 10.13.6 installer app including firmware MP51.0089.B00. The app opens in an OS 10.9.5 volume, and in later OS volumes, but strangely not in an OS 10.8.5 volume where it reports "it may be damaged or incomplete". When it opens it says that a firmware update is required. So this should update the firmware to MP51.0089.B00 whether or not I proceed to install OS 10.13.6 in one or another volume.

What are the risks in this process? If my GPU provides pre-boot support now, will it surely do so with that new firmware? tsialex notes that there is always a risk of a "failed flash" in all Mac/PC firmware upgrades. Does this failed flash generally spare the old firmware, or does it generally brick the computer? Probabilities please. Should the bricking risk be weighed against the risk of Spectre or Meltdown?

Thanks to all.

 

[earthcub]

I realize this is an ancient setup, but I've been running Sierra on my 5,1 forever. All my old Adobe software works and I don't want to give it up but I REALLY want to run BetterDisplay on my system to get crisper fonts and graphic details. In order to do so, I have to upgrade to Mojave. So, I got High Sierra running. I'm running BootRom 144.0.0.0.0. Got the security patches up to date so I could install the Nvidia Web Driver for my GTX 780. Everything runs great.

However, when I try to install Mojave, I get to the final system boot with the gray screen, Apple, and loading bar, and the system freezes. Now, there's a caveat. I can do the Mojave update if it's an update directly from a fresh install of High Sierra. If I try to update my fully loaded user/apps/system files version of High Sierra, I run into the boot problem. If I try to install Mojave and use Migration Assistant, I run into the same boot freeze. I can't figure out what the problem is.

I'm CCCing the High Sierra install to a SATA to do the Mojave update. I've tried doing the install from an HFS partition and from an APFS partition. When I first installed Sierra, I did RehabMan's nvme kexts to get my OS running on M.2. No problems with Sierra or High Sierra. Could this be a contributor? Is it the Nvidia card?

I don't know how to diagnose this any further and it doesn't work to try a recovery install because I'll run into the Metal GPU prohibition from the Mojave installer. I cannot safe boot; it just reboots the system. I want to keep my apps and system configuration. Any ideas? Anyone? Thank you.

 

[tsialex]

When I first installed Sierra, I did RehabMan's nvme kexts to get my OS running on M.2. No problems with Sierra or High Sierra. Could this be a contributor?

Yes, remove it.

Is it the Nvidia card?

Yes too, remove webdrivers before to the upgrade or do a clean install. Mojave do not support it.

Btw, paragraphs are really important, I almost did not read your wall of text.

 

[tsialex]

If I try to install Mojave and use Migration Assistant, I run into the same boot freeze. I can't figure out what the problem is.

Incompatible drivers can make TM restores to fail, do a new TM with the drivers removed.

 

[earthcub]

I checked out the hackrfamily kexts and they weren't transferred to the Mojave install with Migration Assistant so that's not the problem.

I forgot to mention that I tried with and without the Nvidia webdrivers and got the same result.

 

[tsialex]

I checked out the hackrfamily kexts and they weren't transferred to the Mojave install with Migration Assistant so that's not the problem.

I forgot to mention that I tried with and without the Nvidia webdrivers and got the same result.

Can you do a clean install successfully? Maybe you have other incompatibility issues or even a bad NVRAM volume inside your Mac Pro BootROM.

Enable verbose booting, usually helps a lot with grey screen freezes/crashes.

 

[earthcub]

I don't that the nvram volume is bad. Checked against symptoms and they don't apply.

I'm doing a clean install right now. I've done it before and it worked. The OS didn't boot after using Migration Assistant to transfer data from High Sierra install. So it may be what I'm choosing to transfer?

I looked at system.log from the last boot. There were quite a few entries to qmaster services trying to start that may have led to a kill 9. I haven't had that installed in ages. I removed anything I could find related to qmaster from my High Sierra system so I can try the Migration Assistant again.

I ran verbose mode on the startup. It would be nice if there were a way to save it but I don't see a way to do that. Also, do you know if there's a way to limit proceeding through startup by key entry like spacebar or enter key?

 

[tsialex]

I don't that the nvram volume is bad. Checked against symptoms and they don't apply.

Failing while installing macOS, is a sure signal of NVRAM volume problems, even more so if is failing while in the grey screen. Major cause of failure to install macOS back in Big Sur times.

Also, frequent KPs are a major cause of bricks, since the crash dump is saved inside the VSS store and can easily corrupt the NVRAM volume with MacPros before the MacPro7,1.

I ran verbose mode on the startup. It would be nice if there were a way to save it but I don't see a way to do that.

sudo nvram boot-args=“-v”

Also, do you know if there's a way to limit proceeding through startup by key entry like spacebar or enter key?

If you want to do a kernel messages/debug step by step, no it's not possible (unless remote debugging with a very complex procedure and requiring specialized hardware).

If what you want is to force the startup Manager to appear every boot, only works for GPUs that have pre-boot configuration support:

sudo nvram manufacturing-enter-picker=true

 

[Melbourne Park]

I am having issues when using migration assistant. When I use it, the system gets corrupted somehow. I only want to get my Safari passwords, but I cannot just import the Safari settings alone using Migration Assistant. If there is a way to do that using migration assistant, please tell me!

I know I can do so using Apple iCloud, but in order to get Safari's passwords etc., I need to enable duel Apple verification. I have had this issue before and I turned on duel authorisation, and then turned if off. But now Apple tells me if I turn it on, its on forever. I know its better security, but when I travel I like to log on at airports etc, and that doesn't allow duel authorisation. Duel is also slower and inconvenient as I think I need two Apple devices available at the one time.

 

[tsialex]

I am having issues when using migration assistant. When I use it, the system gets corrupted somehow. I only want to get my Safari passwords, but I cannot just import the Safari settings alone using Migration Assistant. If there is a way to do that using migration assistant, please tell me!

I'm almost sure that you posted here by accident since this is totally and completely off-topic for this thread, anyway, if you are restoring the TM booted from OC/OCLP, you need to remove the root patches.

If is really Mojave restoring a vanilla Mojave or earlier made TM, open a thread in the Mojave forum and ask for help there, more eyes.

I know I can do so using Apple iCloud, but in order to get Safari's passwords etc., I need to enable duel Apple verification. I have had this issue before and I turned on duel authorisation, and then turned if off. But now Apple tells me if I turn it on, its on forever. I know its better security, but when I travel I like to log on at airports etc, and that doesn't allow duel authorisation. Duel is also slower and inconvenient as I think I need two Apple devices available at the one time.

This is exactly why two-factor authentication was invented. I'm not even go further…

 

[earthcub]

Failing while installing macOS, is a sure signal of NVRAM volume problems, even more so if is failing while in the grey screen. Major cause of failure to install macOS back in Big Sur times.

Also, frequent KPs are a major cause of bricks, since the crash dump is saved inside the VSS store and can easily corrupt the NVRAM volume with MacPros before the MacPro7,1.

sudo nvram boot-args=“-v”

If you want to do a kernel messages/debug step by step, no it's not possible (unless remote debugging with a very complex procedure and requiring specialized hardware).

If what you want is to force the startup Manager to appear every boot, only works for GPUs that have pre-boot configuration support:

sudo nvram manufacturing-enter-picker=true

Thank you for hanging in there with me. I'm happy to say that your suggestions paid off and I was able to get Mojave going. It was definitely the HackrNVMeFamily.kext that I installed way back when. High Sierra was fine with it but Mojave said, "No way!"

Removing it was a pain. I started with Kext Wizard to determine whether it was truly installed or not. I had to clean it out of the /System/Library/Extensions/ from four different installs I've been tinkering with. I also had to boot into Recovery Mode and get to the terminal and use kextcache --clear-staging from /usr/sbin because my $PATH is screwed up from the OS not installing probably.

I got the clue that it was the HackrNMVeFamily.kext by using the verbose startup and filming it with my cell. It goes by so fast but with the video I was able to slow it down to see what the final error was that was causing the freeze.

I'm still not sure what to do about any NVRAM problems you thought might be occurring.

Also, I was able to get into Mojave and get Nvidia drivers uninstalled which greatly helped the second loading of the OS. However, I'm still having some performance issues that hopefully I'll be able to work out once I get the OS back on the NVMe.