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.
MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
No end user should bother with this. If the re-issued has a need to be installed over the deprecated, Software Update does that automatically.
Re-issues happen when something is wrong with the previous release. Apple does that from time to time and since they don't publicly post release notes about what changed, usually users never know and system administrators have to compare the re-issued with the previous release to know what was modified.
I usually talk about because system administrators need to use the most current releases when using MDM/Reposado/etc.
Correction: 18F203 is a new build exclusive for 2018 & 2019 15" MacBook Pro
Apple released a new full installer of 10.14.5 for the 2018 & 2019 15" MacBook Pro (Mac-937A206F2EE63C01, Mac-1E7E29AD0135F9BC). The new build is 18F203 while the general one is 18F132.
New MacBook Pro Supplemental Update and BridgeOSUpdateCustomer were released too. Seems the re-issue is T2 related. Support Article for macOS Mojave 10.14.5 Supplemental Update for MacBook Pro
Apple released a new full installer of 10.14.5 for the 2018 & 2019 15" MacBook Pro (Mac-937A206F2EE63C01, Mac-1E7E29AD0135F9BC). The new build is 18F203 while the general one is 18F132.
New MacBook Pro Supplemental Update and BridgeOSUpdateCustomer were released too. Seems the re-issue is T2 related. Support Article for macOS Mojave 10.14.5 Supplemental Update for MacBook Pro
Last edited:
One thing I just noticed on the Mac Pro in my signature, my monitor connected via displayport now appears in sound output devices in the menu bar after the 144.0.0.0.0 firmware. I never really used monitor speakers anyway, but I don't remember it ever being there. I did try it out of curiosity, and it does actually work too. 
One thing I just noticed on the Mac Pro in my signature, my monitor connected via displayport now appears in sound output devices in the menu bar after the 144.0.0.0.0 firmware. I never really used monitor speakers anyway, but I don't remember it ever being there. I did try it out of curiosity, and it does actually work too.
I'm pretty sure it was actually the 10.14.4 (the one released 25 March) macOS update that finally fixed that issue, not the bootrom. Here is a thread about it: https://forums.macrumors.com/threads/psa-display-port-audio-now-working-in-mojave-10-14-4.2175184/
Hey everyone, I've read through almost all the pages and wasn't able to track this down. I followed the instructions on how to update it to no success. I have a 4,1 -> 5,1 running Mojave on a SM961 PCIe SSD. Works great with Metal GPUs GTX760. I never had a problem updating the firmware, however when I tried upgrading to boot rom 144.0.0.0.0, I'm not able to have success. I'm on boot rom 140.0.0.0.0 trying to upgrade to 144.0.0.0.0.
I downloaded the full-installer (I'm assuming it's full?) via the App Store and click on the "Install Mac OS Mojave". It then says it needs to update the firmware. It shuts down, then I hold the power button until the lights flash and I hear the loud tone. Since my gpu is not efi, I'm not able to see what if anything going on, but when I hold down the bottom it appears to look like it's doing something. Just stays at this screen, doesn't restart, shut down nothing. Tried a spare machine and same outcome, so wasn't sure if anyone else experienced this.
Anything "new" that needs to be done? Thanks
EDIT: It appears that you cannot update the firmware from a NVMe ssd, and that an internal sata is what is recommended. Any way to use the NVMe to update it? or just proceed with how others have done it?
I downloaded the full-installer (I'm assuming it's full?) via the App Store and click on the "Install Mac OS Mojave". It then says it needs to update the firmware. It shuts down, then I hold the power button until the lights flash and I hear the loud tone. Since my gpu is not efi, I'm not able to see what if anything going on, but when I hold down the bottom it appears to look like it's doing something. Just stays at this screen, doesn't restart, shut down nothing. Tried a spare machine and same outcome, so wasn't sure if anyone else experienced this.
Anything "new" that needs to be done? Thanks
EDIT: It appears that you cannot update the firmware from a NVMe ssd, and that an internal sata is what is recommended. Any way to use the NVMe to update it? or just proceed with how others have done it?
Last edited:
Most people have been upgrading BootROMs directly from NVMe PCIe drives since 140.0.0.0.0, but seems that some people are having trouble with the 140.0.0.0.0 to 144.0.0.0.0 upgrade. You can always try from a SATA drive installed in one of the southbridge ports and see if makes difference for your config or not.
This doesn’t affect everyone for some reason. I’ve done nearly all of my firmware updates directly from an NVMe SSD.
Strange question. He has never suggested that you SHOULDN’T upgrade to v144 that I’m aware of.
Can you show me a link where it has been discouraged?
If you meant v142 however, that one will brick your machine if you have a w3xxx processor. Go back and review the posts and read this thread. Seems you have skipped a lot of essential reading if you want to understand.
Page 1 ... post 1 !
Maybe I missed something
It seems you don’t understand.
144.0.0.0.0 =
142.0.0.0.0 =
IL
Last edited:
As mentioned by crjackson2134, the description in post #1 says not to install 142fw (which was only beta).
144 fw is no problem.
144 fw is no problem.
Read the first post, Mac Pro has it's own manual way to upgrade firmware.
HDMI/DP audio is un-related to BootROM.
Weird. Any rhyme or reason why it works for some and not others?
What's the best way to go about updating it if the nvme drive isn't working? Would a full installer on a USB drive work? Or should I suck it up and just install it on a sata drive?
This happens to just some people and never happened to me or other people that are capable of investigating it.
Don't use USB drives to upgrade firmware.
Until a better solution is devised, just use a SATA drive installed on the southbridge SATA ports.
People that have this problem made a dedicated thread: Updating my MacPro 5.1 from 140.0.0.0.0 to 144.0.0.0.0 does not work
I still think it has something to do with jumping directly from 140.0.0.0.0 to 144.0.0.0.0. Seems that almost everyone having this problem (including myself) skipped the 141.0.0.0.0 bootrom that was released with 10.14.4.
You will have to suck it up and install onto a SATA drive if you want to install 144.0.0.0.0
I upgraded from 140.0.0.0.0 to 144.0.0.0.0 with my backup backplane this week without any problem from a 970 Pro + Wings PX1. It's something else of the BootROM version itself that is causing this.
Did you used the NVMe EFI module from MP6,1? I found that the injection with dosdude tools is different from what Apple or UEFITool did. BootROMs that had the injection show the NVMe EFI module two times.
[doublepost=1558896838][/doublepost]
No, I've never injected anything--only ever used stock bootroms (never even beta versions). I wonder though if the reason you are successful could have anything to do with having rebuilt your own bootrom with the newest base version. Mine is still the super old Base_17. I think I saw that many (all?) of us having problems with NVMe firmware updates are on 4,1->5,1's. Maybe unrelated--just a guess.
I don't think that we know enough about what is causing this to make a hypothesis. Anyone dumped the problematic 140.0.0.0.0?