To complete the firmware update, wait for your Mac Pro to finish installing and shutdown. Hold down the power button until the power indicator light flashes, or you hear a long tone, then release the power button. A gray screen with an Apple logo and progress bar will appear while the update is taking place. When the update is complete your Mac Pro will startup normally.
Mac Pro EFI Firmware Update 1.5... This update is recommended for all Mac Pro (Mid 2010) models and addresses the following issues: - Resolves an issue that prevented the firmware password prompt from being displayed - Resolves an issue that prevented the Boot Picker from being presented if Ethernet is connected to a network without DHCPTo complete the firmware update, wait for your Mac Pro to finish installing and shutdown. Hold down the power button until the power indicator light flashes, or you hear a long tone, then release the power button. A gray screen with an Apple logo and progress bar will appear while the update is taking place. When the update is complete your Mac Pro will startup normally.
Mac Pro Efi Firmware Update 1.5 Download
Download File: https://3bromagatempdo.blogspot.com/?zx=2vGp36
I did this a couple of times. It looked like it was going to work but I did not get a firmware progress bar, it just booted normally. And I still have Boot ROM Version: MP41.0081.B07. The problem is the same as stated here:
As you may know, some Mac Pro models have been introduced that are identical or very nearly identical to the model that preceded them. Such is the case with the 2007 Mac Pro (MacPro2,1) and the 2010 Mac Pro (MacPro5,1). I decided to see if it was possible to come up with a way to update the firmware on the 2009 Mac Pro with the firmware from the 2010 Mac Pro. The hardware of these models is very close. The only thing that differs is the CPU socket mechanism on the dual CPU model, which uses Xeon CPUs with the IHS (Integrated Heat Spreader) removed, and the SMC firmware version. The CPU socket issue is transparent to the firmware, and the SMC firmware difference between 2009 and 2010 models is not an issue. As long as the SMC firmware version matches between the main board and the CPU board, everything works perfectly.
To explain how this was accomplished, let me first describe how the firmware update process works on a Mac. The firmware updater package, after checking that the Mac can use the update, places an EFI boot file named EFIUpdaterApp2.efi, which is very similar in structure to the standard boot file that starts a Mac on the system volume, in the /System/Library/Core Services/Firmware Updates folder, along with the actual firmware image. This boot file is then blessed in a special way, and the next time the Mac is booted from shutdown, with the power button held down for a few seconds, this special EFI program is run.
So how do we get the program to load the other firmware? It turns out that it is surprisingly easy. Inside the EfiUpdaterApp2.efi program are a list of firmware version strings from different releases of the 2010 Mac Pro, along with the CRC32 checksum of the firmware image file. If one of the firmware version strings is modified to what the 2009 Mac Pro model is, and the CRC32 checksum is changed to match the 2010 Mac Pro firmware image, and the firmware image filename is changed to the 2009 Mac Pro firmware image filename, then all is well.
I have tested this myself, on both 2009 and 2010 Mac Pro models. You can upgrade or downgrade at will. If you have a CPU in a 2010 Mac Pro that isn't supported in the 2009 Mac Pro, such as the Westmere 6-core Xeon, the system will not boot after the update until a compatible CPU is installed. I started off with just a few scripts and files in a folder to do this, but as a service to the community, I have written an installer program that does everything automatically. The program checks the Mac Pro model and will install the 2009 Mac Pro firmware or the 2010 Mac Pro firmware, whichever is appropriate. If you have a 2010 Mac Pro with a 6-core Xeon, the program will warn you, but still allow the firmware update. The download does not contain any firmware updater files or image files. The program creates a small RAM disk, downloads the needed files, copies all of the scripts to the RAM disk, and then runs the scripts. Everything is left on the RAM disk for you to look and and study, if needed.
Yep, I've had no problems going back to the 2009 EFI. It reverts to my original MP41.0081.B07 firmware, just something you need to be aware of in case you have one of those special refurb Mac Pros with the MP41.0081.B08 firmware.
It looks like you've covered almost all of the solutions. Did you rename the update to "EFI2010.dmg" and then mount it before running the firmware update tool? While using Mavericks of course, not El Capitan.
It is... Unless the Apple 5.1 firmware update is open on the desktop. A combination of issues led to all the trouble. I pulled the SSD hard drive running OS 10.11.3 from the PCI slot and booted 10.7.5 from a SATA hard drive. Disconnected from the 5770 GPU and connected to the old GT120. Loaded the 4.1-5.1 tool with Apple's 5.1 firmware update open on the desktop. That worked. At this point, I don't know why the GPU or PCI SSD would interfere but, all I know is that it only worked when they were out of the equation. I reset the pram and all is great. The 1333 ram shows as 1066 but, only because the new CPU isn't installed yet.
At this time Apple isn't showing any upgrade path for your machine. And given the list of what else Apple is dropping off in the way of software, it's unlikely Apple will issue a firmware patch for your machine.
3. If it wont update or the fans are running at full speed then you may have faulty motherboard components, ram, tray, backplane board, processors (have not seen processors this yet just badly installed or damaged cpu pins)
The updates require OS X 10.7.2 to install, and when downloaded and run will provide on-screen instructions for how to apply the updates. Be sure to follow the instructions exactly, and have your system plugged into a reliable power source when updating. It is not uncommon for computer systems to restart multiple times and show temporary black screens when firmware updates are being applied, so allow the system to go through its steps without interruption. An interrupted firmware update can render a system inoperable, requiring replacement of major system components.
When the update completes, the system should reboot to the log-in window or to the desktop, and if you check the boot ROM or SMC version in the system information utility you should see a version string of MB71.0039.B0E for the MacBook Pro, MM41.0042.B03 for the Mac Mini, and MB71.0039.B0E for the MacBook.
To use Lion Internet Recovery, once these updates are installed all you need to do is hold Command-R when starting up and the system will present a request to join a network if you do not have a local partition with the Lion Recovery tools on it. Once a network connection is established, the system will run some diagnostic tests and then download and run the Lion Recovery tools (they are about 200MB in size).
If you own a MacBook Pro or iMac system purchased in 2011, which does not have the capability to use Lion Internet Recovery, then you may need to update its firmware, which can be done by downloading and applying the update for these systems from Apple's Lion Internet Recovery firmware update Web page.
Updating the firmware on a Mac Pro isn't difficult, but it is possible to "miss" firmware upgrades. This guide is for anyone looking to get to the latest (and most likely last) firmware released for the Mac Pro 5,1s, without having to install Mojave 10.14.x, or if you already have installed Mojave, or are looking to install Mojave. My first try, my firmware was stuck at 138.0.0.0.0.x even when running Mojave 10.14.6. Updating the firmware adds key funcitonality to the Mac Pro 5,1s, most notably native NVMe m.2 boot support. To learn more about Firmware and the Mac Pro 5,1s, see the Firmware Upgrades section of my Mac Pro Upgrade Guide.
These aren't the only instructions on the web, as MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread) for firmware upgrading. However, this the method I've found most reliable for users who are having firmware troubles.
Note: some users are reporting they had to remove all PCIe cards sans their storage controller (SATA card) and GPU to install the firmware update. I did not. If you encounter issues, try removing additional PCIe cards.
Unfortunately, this is the biggest pain if you've already updated. You'll need a separate volume to boot into 10.13. Amazon and Newegg each have 120 GB SSDs for under $20 USD if you need a temporary drive to install macOS 10.13 on. (upside is you can buy a USB case and turn into a very fast USB 3.0 drive afterward or return it). You can get old versions of macOS via the Mac using DosDude1's installer if you can't access it. If you have no intention to upgrade to Mojave or already have it installed., don't worry. We won't be installing Mojave.
Fortunately, firmware flashing does not require updating in a particular order. I went from 138.0.0.0.0 to 144.0.0.0.0 without any problems. There's several avenues for this, including the Mac App store, but when I used the Mac App Store route, I didn't get the combined OS installer (The Mojave installer + all the updates to Mojave). The easiest way to obtain the final combined update for Mojave is to use Dosdude1's installer. Much like before, download the OS DosDude1's installer, even though we have supported hardware but with the patcher for 10.14.
Clarification: You do not need to use the DosDude1 installer, as you can grab the update via the App store or other sources but I found this easier. Apparently this link was posted this on MacRumors and a few posters didn't read the full instructions and suggested that I was advocating using DOSdude1 on the OS. I am not. The Mac Pro 4,1/5.1 does not need DOSDude1, so do not run the patcher on Mojave. The Patcher just happens to be extremely reliable about fetching the correct version, and skips the hassle of the App Store. 2ff7e9595c
Comments