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.
Updating my MacPro 5.1 from 140.0.0.0.0 to 144.0.0.0.0 does not work
- Thread starter The Spirit
- Start date
- Sort by reaction score
I use High Sierra 10.13.6 with APFS from an internal Sata drive and run "Install Mac OS Mojave" to get to 144.0.0.0 - just to get the firmware, Mojave installation is not necessary.
With GTX680 and other Kepler GPUs, with and without bootscreen. Also I used AMD HD7 / R9 GPUs.
What is NOT working is running from a bootable USB Installer, and of course not with patched DosDude Installation.
With GTX680 and other Kepler GPUs, with and without bootscreen. Also I used AMD HD7 / R9 GPUs.
What is NOT working is running from a bootable USB Installer, and of course not with patched DosDude Installation.
This is a major problem with your install. You might have better luck in those dedicated threads.
Clean install High Sierra onto a spare/blank SATA SSD or SATA HDD. Then download Mojave installer and try again. This is the only known workaround. USB installer does NOT work for firmware updates the majority of the time. Believe some have tricked it, but it's not reliable.
There are lot's of motives that can make a MP4,1>5,1 or MP5,1 firmware update unsuccessful, most if not all of them are already in the first post of the thread:
MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)
MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)
Right. That's what I wrote.
And that helped with updating the firmware to 144? Or did that just help you to install Mojave, but you're still at 140?
Right - that claims it won't work with a GTX, right? Yet, two people up here claimed that it would work with a GTX 680 regardless, and that's what I was trying to clarify: Were they talking BS or what's their secret?
Other than having a GTX 680 installed, I've ruled out all other possibilities listed in the first post as problematic.
I do not have an original graphics card, so I am looking for other ways to fool the installer into doing its work even though it believes that I have a Metal-incapable card installed.
So, you're the 3rd person now that claims the upgrade to 144 should work with my setup (booting into 10.13.6 from an internal drive, running the Mojave installer, with GTX680 as the graphics card). How did this work for you? Did you run the Mojave Installer, and when it says it has to first upgrade the firmware, and after you clicked the (>) button and entered your admin pw, did it then automatically shut down (mine doesn't)? Or did you do it in a different way?
Last edited:
And that helped with updating the firmware to 144? Or did that just help you to install Mojave, but you're still at 140?
NO, I did the firmware update successfully the first time i ran the installer from an hfs+ , THEN when i restarted it would not proceed because it said the 680gtx video was not supported so then i booted off a dosdude installer usb and ran the patched installer but did not need to do any other patches of course.
You mentioned in a prior post that you installed the RX 580 and the update still failed. Was this the only card installed in the system at that point?
What drives did you have installed in the system when you were booted from your fresh install of 10.13.6? And what is the format of the drive that is booting 10.13.6—HFS+ or APFS?
I had this issue....(I have Mac Pro 2009, flashed to 5,1 with a single 6 core 3.46 processor, Radeon RX580 GPU with High Sierra) couldn't get beyond the 140.0.0.0 Boot Rom. I kept trying the upgrade installer for Mojave and I would get the message that it needed to install a firmware update. I'd restart, hold down the button until the chime had finished (maybe 5-10 sec past) and eventually it would just restart as usual...no upgrade.
I noodled around here in these threads for a bit and then decided to remove all the HD's from my machine (2 SATA HD's I use for image storage), leaving only one SSD with the OS on it, and then I reset the NVRAM three times...and that worked. I'm not super technical but hopefully this helps someone.
As always appreciate all the great info here (especially tsialex).
Alan.
I noodled around here in these threads for a bit and then decided to remove all the HD's from my machine (2 SATA HD's I use for image storage), leaving only one SSD with the OS on it, and then I reset the NVRAM three times...and that worked. I'm not super technical but hopefully this helps someone.
As always appreciate all the great info here (especially tsialex).
Alan.