Unbelievable.
Another great Mojave bug Apple still haven't fixed is that if you have a SATA RAID 0 array then you can't erase a USB flash drive using disk utility without it crashing.
Mojave does have some pretty nasty bugs in it right now.
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
Another great Mojave bug Apple still haven't fixed is that if you have a SATA RAID 0 array then you can't erase a USB flash drive using disk utility without it crashing.
Mojave does have some pretty nasty bugs in it right now.
The small 22.8 MB Mojave installer app (downloaded via Mac App Store) worked to update firmware to 140.0.0.0.0 on my authentic MacPro5,1 with GTX 1080 FE installed, running 10.13.6 Build 17G65. Firmware update basically worked as all previous have, but no need for EFI GPU to be installed. System SSD is formatted HFS+ and is a SATA SSD connected via PCIe adapter. CD/DVD drive ejected as usual, but the wait until TONE after blinking power light did take slightly longer than usual/previous.
Overall was a bit more panic on my end, non-sensibly wondering if the rest of Mojave was going to be installed without my desire at this time... but had full bootable clones to turn to if anything went wrong. Figured was worth the shot since I'm one of the "lucky" ones that received this smaller file link to download via App Store.
For anyone else who uses this smaller download in the future, you do need to authenticate a Mojave Helper to install the firmware update.
Overall was a bit more panic on my end, non-sensibly wondering if the rest of Mojave was going to be installed without my desire at this time... but had full bootable clones to turn to if anything went wrong. Figured was worth the shot since I'm one of the "lucky" ones that received this smaller file link to download via App Store.
For anyone else who uses this smaller download in the future, you do need to authenticate a Mojave Helper to install the firmware update.
I cannot update my boot rom to 140.0.0.0 as both the full 10.14.1 installer and RecoveryHDMeta.pkg refuse to install on my 4,1->5,1 complaining about no metal card found and FileVault on. I have the sapphire pulse rx580 and FileVault is 100% off. I suspect there might be a bug with those packages as my cMP updated to 10.14.1 just fine using System Preferences -> Software update, without the boot rom update that is
Legend!!! you are so helpful and knowledgeable. Thanks for everything you do. God bless
tsialex the king 
thanks for your amazing support just update to 140.0.0.0 will get a Samsung 970 Pro, have a question about that, how can I do a clean install on the 970 Pro as Boot Device, when I have no Bootscreen ?
thanks for your amazing support just update to 140.0.0.0 will get a Samsung 970 Pro, have a question about that, how can I do a clean install on the 970 Pro as Boot Device, when I have no Bootscreen ?
From macOS, Use two disks, when you open the installer, you select the empty one.tsialex the king
From USB, if you have a RX-580, createinstallmedia 10.14.1 installer works with it.
thank you very much, will post updates soon, need to get the Samsung 970 Pro
My Geekbench Results
Mojave 10.14.1 >>> 140.0.0.0
Mojave 10.14 >>> 138.0.0.0
High Sierra 10.13.6 >>> MP51.0089.B00
Have 8GB of Ram and S-ATA Disk at the moment and Quadro K600 installed
Last edited:
Mac Pro 4,1 ---> 5,1 with gtx680 successfully upgraded to 10.14.1 with 140.0.0.0
Just ran the full 10.4.1 Mojave installer downloaded from the App Store. It took 40 minutes after the firmware flash.
It was easy peasy from 138.0.0.0 that tsialex helped me with. For some reason I had to reboot twice to get the flash to work, and I didn't get a progress bar; but my DVD drive did open up and then close when it was finished, although it seems hairy when you don't get to see the thermometer.
As promised, it did have the NVMe driver rolled in as it immediately rebooted to the PCIe 970 Pro I had installed, and I'm now at 140.0.0.0.
What's strange is I applied the update to a 13-inch 2015 rMBP and got 180.0.0.0 as the revision also?! Guess this is the new format
It was easy peasy from 138.0.0.0 that tsialex helped me with. For some reason I had to reboot twice to get the flash to work, and I didn't get a progress bar; but my DVD drive did open up and then close when it was finished, although it seems hairy when you don't get to see the thermometer.
As promised, it did have the NVMe driver rolled in as it immediately rebooted to the PCIe 970 Pro I had installed, and I'm now at 140.0.0.0.
What's strange is I applied the update to a 13-inch 2015 rMBP and got 180.0.0.0 as the revision also?! Guess this is the new format
Just a coincidence, every Mac has a different revision, MP6,1 is on 127.0.0.0.0, my rMBP 251.0.0.0.0.
Thank you. Upgrade complete. I went from 10.13.6 with the .0089 firmware to 10.14.1 with the 140.0.0.0 firmware. I had to do one extra reboot and an SMC reset to get bluetooth to work again. It was all dashed out on my menu bar, but after the reboot everything works just fine (except for my PCI fan which wants to run fast after the RX580 upgrade.... alas... another thing to patch). Now, to buy one of those Angelbird cards (or something) and an NVME stick just for fun.
@tsialex
Great thread, great people in this forum and extraordinary help I just have gotten from this guy getting my cMP4,1-5,1 machines corrupted firmware fixed!
He helped in every step where things were unclear and was very patient, and finally he got all the stuff removed and double checked from my side that everything will work just fine!
BIG THANKS!
+100
Great thread, great people in this forum and extraordinary help I just have gotten from this guy getting my cMP4,1-5,1 machines corrupted firmware fixed!
He helped in every step where things were unclear and was very patient, and finally he got all the stuff removed and double checked from my side that everything will work just fine!
BIG THANKS!
+100
This is wild. There was an update to Mountain Lion today too. I had an old "Install OS X Mountain Lion" file on an internal Mac Pro hard drive (Mountain Lion is not installed anywhere on my disks) and suddenly today an update for it appeared in the App Store Updates list. I didn't even know it would search the non-boot drives but it did. I pressed the Update button and it downloaded and replaced the install file with a newer version.
@tsialex Interesting... I went to Software Update and it provided a 6GB update, which did the firmware upgrade at the end of the process... then after the firmware upgrade was completed, I checked again "Software Update" and it provided me with a 3+GB update, that I run and the upgrade to 10.14.1 completed.
Everything happened automatically... I did not use the Mac App Store manually to download Mojave 10.14.1!
Everything happened automatically... I did not use the Mac App Store manually to download Mojave 10.14.1!
Firmware update problem -
I installed 10.14.1 over the 10.14.1 beta by downloading the full installer from the Mac App Store. Started the 140 firmware upgrade (had 138). I waited for power off, and held the power button until I had flashing LED and then released the power button. I heard the long beep a couple seconds later. The DVD tray never opened. Then it rebooted back into Mojave like normal without updating the firmware or anything else. Still 138.
I repeated the process and this time held the power button until I saw the flashing LED AND heard the long beep. This time the firmware updated and then Mojave 10.14.1 update proceeded normally. I binwalked the BootRom and two XML files appeared. Previously the 138 bootrom was clean with no XML files.
Is this trouble?
I installed 10.14.1 over the 10.14.1 beta by downloading the full installer from the Mac App Store. Started the 140 firmware upgrade (had 138). I waited for power off, and held the power button until I had flashing LED and then released the power button. I heard the long beep a couple seconds later. The DVD tray never opened. Then it rebooted back into Mojave like normal without updating the firmware or anything else. Still 138.
I repeated the process and this time held the power button until I saw the flashing LED AND heard the long beep. This time the firmware updated and then Mojave 10.14.1 update proceeded normally. I binwalked the BootRom and two XML files appeared. Previously the 138 bootrom was clean with no XML files.
Is this trouble?
Your xml files are for documenting purposes after upgrade and they will disappear later just like they did on mine. So you don't have Windows, do you?
How will they disappear? On another firmware upgrade? Or do you mean in normal use after some cold boots?
Yes, I have Win10 legacy-BIOS and previously I had Win10 UEFI boot. Neither have produced any "certificates".
I got a problem. I just tried to boot to Win10 using the Startup Disk Preference Pane and got a message that the Bless tool was unable to set the current disk. I also tried using my normal bless script to boot to Win10 and it didn't work. I've got SIP-nvram turned off, so that isn't the problem.
Didn't we see this problem around here a month ago? I'm drawing a blank (3 am).
Apple started to send the 6GB update to people still with 18A389, so they did:
18A389 -> 18A391 (6GB)
18A391 -> 18B75
[doublepost=1540981873][/doublepost]
Sent you a PM.
Hi,
I tested both the delta update AND a clean install by downloading it from my second MacPro still with high Sierra (it won't let you download it if you're running Mojave) and none of them offer to install 140.0.0.0.
I even downgraded my BootRom to pre-mojave build (89.something) and the full installer brought me back to 138.0.0.0.
I tested both the delta update AND a clean install by downloading it from my second MacPro still with high Sierra (it won't let you download it if you're running Mojave) and none of them offer to install 140.0.0.0.
I even downgraded my BootRom to pre-mojave build (89.something) and the full installer brought me back to 138.0.0.0.