This along with the custom screenshot that has been triggered for each Full Installer High Sierra update on a MP5,1; it becomes quite clear that this is the intended and only method for a Mac Pro 5,1 to receive a firmware update. Apple never intended for the 5,1 to still be inservice. The iMac Pro, 2018 MacBook Pro with Touch Bar (MacBookPro15,1 and 15,2), 2018 Mac mini and 2018 MacBook Air all use a different mechanism for firmware updates, managed by their T2 chips. They also appear unable to run eficheck. Download the EFI Firmware update from Apple, unpack the package (e.g. With unpkg) and locate the Firmware in the correspoding app. Or you use the existing app in /Applications/Utilities if you happen to have it already. As I needed to reflash a Unibody MacBook 5,1 (Late ’08), I downloaded the package for it (MB51.007D.003 (EFI 1.3)), unpkged. Logger Pro 3.16.2. Logger Pro 3.16.2 is the latest update to our award-winning data-collection software. The update is free for any version of Logger Pro 3. New Features of Logger Pro 3.16.2. Released March 5, 2021. Updated support for Qubit sensors. Improved FFT performance for large data sets. Improved Windows video playback.
Are you a fan of corporate conspiracy theories? If so, listen up, because I've got a great one for you. On Friday, reports started surfacing that suggested the EFI Firmware Update 1.5 was behind a 'blank screen' issue that was rendering MacBook Pros inoperable. As usual, Apple hasn't acknowledged the problem, and the EFI 1.5 firmware hasn't been (officially) confirmed as the cause. Rather coincidentally, though, Apple released the MacBook Pro EFI Firmware Update 1.5.1 yesterday in place of the 1.5 firmware.
We're not entirely sure if the 1.5.1 update fixes the specific bug. The description of the firmware update is particularly terse, saying only that the new firmware 'fixes several issues to improve the stability' of MacBook Pros. I suppose blank screens and wake-from-sleep issues do count as stability problems, though, and the fact that the 1.5 firmware is nowhere to be found suggests that something got fixed.
The version numbers for the 1.5 and 1.5.1 firmwares are the same. This, plus the timing of the release, leads me to guess is that the 1.5.1 update does indeed fix whatever issue (perhaps an installation issue) that was causing the problem for some people. Now, does anyone feel like taking one for the team, trying out the new firmware, and letting us know if it breaks anything?
Update (yes, already): We've received several reader reports that this update does fix the blank screen issue for them.