Sidebar Sidebar
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

bookemdano said:
I guess we're still in search of the culprit here.
Click to expand...

Try mounting your EFI partition. In the past, I've had problems with firmware updates because the partition was corrupted and couldn't be mounted.
 
cdf said:
Try mounting your EFI partition. In the past, I've had problems with firmware updates because the partition was corrupted and couldn't be mounted.
Click to expand...

Mounted fine for me just now. Inside EFI > APPLE > FIRMWARE are EfiUpdaterApp2.efi and MP51.fd, both with a modified date of 5/14/19 @ 4:21pm

So I don't think the partition is corrupted. Plus, there appear to be a bunch of us affected by this. I would guess (although I don't know) that corruption of the EFI partition is pretty rare.
 
  • Like
Reactions: cdf
bookemdano said:
I'm curious what 10.14.2 has in regards to 32bit app compatibility that later versions of 10.14 don't? I haven't noticed any difference in running my 32bit apps under any version of Mojave (other than the warning that they need to be updated, but that's been present since 10.14.0).
Click to expand...
Toast Titanium 14 would crash almost instantly in 10.14.4 but worked fine on 10.14.2. I'll get back to you if it works again on 10.14.5 later. I'm pretty sure that the crash was a bug and not an intended incompatibility. Newer versions of Toast do work but still throw up a warning, including the supposedly 64-bit Toast 17.
 
Enricote said:
I can confirm. My upgrading proccess from 140.0.0.0 to 144.0.0.0 with a Samsung NVMe 970 EVO 1Tb was successfully done after cloning (via Carbon Copy Cloner) my system from NVMe to one internal SSD. I downloaded the fullinstaller 10.14.5 from Apple. I followed instructions from installer.
Click to expand...

I am in the same boat (Boot?). Going from 140 to 144.
My boot drive is a 1TB NVME Samsung like yours. My clone backup however is an internal SATA 1TB HDD. I also have an internal 10.13.6 SSD (too small now to become a clone for my NVME drive).
I could copy the full 10.14.5 installer either to the internal HDD or SSD to perform the BootROM upgrade like you did. I guess it doesn't matter since the installer is booting from itself and not the OS that it happens to be sharing the drive with. the internal SSD only has about 40GB space available if that makes a difference.

I downloaded the Combo update to then perform the actual system 10.14.3 to 10.14.5 update.

Thoughts?
 
mavots said:
I am in the same boat (Boot?). Going from 140 to 144.
My boot drive is a 1TB NVME Samsung like yours. My clone backup however is an internal SATA 1TB HDD. I also have an internal 10.13.6 SSD (too small now to become a clone for my NVME drive).
I could copy the full 10.14.5 installer either to the internal HDD or SSD to perform the BootROM upgrade like you did. I guess it doesn't matter since the installer is booting from itself and not the OS that it happens to be sharing the drive with. the internal SSD only has about 40GB space available if that makes a difference.

I downloaded the Combo update to then perform the actual system 10.14.3 to 10.14.5 update.

Thoughts?
Click to expand...

If you have a clone of your Mojave drive on a SATA HDD why not just use that?
 
No rdaso
bookemdano said:
If you have a clone of your Mojave drive on a SATA HDD why not just use that?
Click to expand...

No reason not to. I thought someone wrote to use SSD (Maybe assumed APFS instead of HFS+, not that I can see why that would make any difference for the installer)

Did you restart from the internal hdd Mojave clone first and then run the installer?
Will I be able to "see" anything happening with the RX580 (or just follow the noises, lights and drive tray opening/closing)?
 
mavots said:
No rdaso


No reason not to. I thought someone wrote to use SSD (Maybe assumed APFS instead of HFS+, not that I can see why that would make any difference for the installer)

Did you restart from the internal hdd Mojave clone first and then run the installer?
Will I be able to "see" anything happening with the RX580 (or just follow the noises, lights and drive tray opening/closing)?
Click to expand...

SSD or HDD doesn't matter--just needs to be SATA as opposed to in a PCIe slot.

And yes, you'll want to change the startup disk to the SATA drive, boot from it and run the full 10.14.5 installer from there. You won't see anything on the screen when initiating the firmware upgrade, but yes you'll see/hear the normal signs... flashing power light, long beep, superdrive open, superdrive close, etc.
 
I upgraded from 141.0.0.0.0. I already was on 10.14.5, so I ran the full installer just for the firmware part.
It seemed to take a long time both to get the process going and for the whole thing to complete.
1. I keep the power button depressed well past the flashing light until I hear a beep. Took quite a while.
2. It then trundled for a long time. I knew things were happening when it finally opened both of my CD drives. But it stayed on a black screen forever.
 
haralds said:
I upgraded from 141.0.0.0.0. I already was on 10.14.5, so I ran the full installer just for the firmware part.
It seemed to take a long time both to get the process going and for the whole thing to complete.
1. I keep the power button depressed well past the flashing light until I hear a beep. Took quite a while.
2. It then trundled for a long time. I knew things were happening when it finally opened both of my CD drives. But it stayed on a black screen forever.
Click to expand...

Yes, it seemed to take longer on mine too. It was pretty noticeable, but not alarming.
 
I had a two-fold issue; I'm on 10.13.6 and had installed Ubuntu as a triple-boot at some point in the past. The firmware update from 140.0.0.0.0 to 144.0.0.0.0 when run from NVME would continually trigger a boot to GRUB, not the EFI updater. After mounting each EFI partition I could find and deleting the BOOT or UBUNTU directories contained within, each attempt to update the firmware would simply reload macOS.

I installed 10.13.6 on an internal drive and ran the full Mojave installer from there. Firmware update worked first time.

Able to flash 144.0.0.0.0 via NVMe?: No
Actual cMP Model: 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive: Samsung 970 Pro 1 TB
NVMe in PCIe Slot: 2 (High Point SSD7101A-1, Position 1)
 
Last edited:
The good news about this issue is that it seems easy enough to solve, so long as someone still has a SATA drive around to use. I haven't seen any reports yet from anyone who was unsuccessful in flashing 144 from SATA.

But in terms of trying to figure out the cause, maybe we should try to report config/results in a consistent way in order to better spot a potential pattern. Here is what I think is potentially relevant info to provide:

Able to flash 144.0.0.0.0 via NVMe?: NO
Actual cMP Model: 4,1 > 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive: WD Black 500GB WDS500G2X0C
PCIe adapter model and PCIe Slot#: Kyro M.2 Evo Slot 4

If anyone thinks there is other configuration info that would be helpful to report please suggest it and I'll edit my post.
 
Last edited:
Able to flash 144.0.0.0.0 via NVMe?: NO
Actual cMP Model: 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive: Crucial P1 500GB
NVMe in PCIe Slot: 4 (Aqua Computer kryoM.2)
 
Last edited:
  • Like
Reactions: bookemdano
Able to flash 144.0.0.0.0 via NVMe?: Yes
Actual cMP Model: 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive: Samsung 970 Pro 500GB
NVMe in PCIe Slot: 1 (High Point SSD7101A-1, Position 1)

Able to flash 144.0.0.0.0 via NVMe?: Yes
Actual cMP Model: 5,1
Previous Bootrom: 141.0.0.0.0
NVMe Drive: Samsung 970 Pro 500GB
NVMe in PCIe Slot: 1 (High Point SSD7101A-1 Position 1)

Able to flash 144.0.0.0.0 via NVMe?: Yes
Actual cMP Model: 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive: Adlink S70 1TB
NVMe in PCIe Slot: 1 (High Point SSD7101A-1 Position 2)

Able to flash 144.0.0.0.0 via NVMe?: Yes
Actual cMP Model: 5,1
Previous Bootrom: 141.0.0.0.0
NVMe Drive: Adlink S70 1TB
NVMe in PCIe Slot: (High Point SSD7101A-1 Position 2)
 
  • Like
Reactions: bookemdano
I assume 144.0.0.0 is the firmware installed by the osx 10.14.5 full installer ? And it has to be run from a disk in one of the drive bays not the pcie slot ?

I looked through a lot of the posts but could not find what if any changes/advantages this new firmware update brings ....could someone please tell me ? thanks
 
macguru9999 said:
I assume 144.0.0.0 is the firmware installed by the osx 10.14.5 full installer ? And it has to be run from a disk in one of the drive bays not the pcie slot ?

I looked through a lot of the posts but could not find what if any changes/advantages this new firmware update brings ....could someone please tell me ? thanks
Click to expand...


Look at the post right before yours. Yes, some people have to use an SATA drive to do the update, but many people don’t.

Regarding changes, please use the search function.
https://forums.macrumors.com/thread...yper-threading.2132317/page-134#post-27322642
 
Success!
Updated BootROM 140 >>> 144. Used an internal (SATA) SSD boot drive with the full installer. Disconnected all other attached internal drives and external enclosures. No issues. Then restarted with normal NVME/PCIe boot drive and updated OS with Combo 10.14.5 installer.
 
  • Like
Reactions: 0134168
Updated 140 to 144 on my native Mac Pro 5.1 Single

Booted a 2,5" SSD with High Sierra installation 13.6 and 14.5 full installer - plugged in an USB-SATA Adapter on front USB port.

Changed simply nothing (AHCI Samsung Blade, flashed GTX680, FL1100 USB 3 in PCIe slots)
 
Macschrauber said:
Updated 140 to 144 on my native Mac Pro 5.1 Single

Booted a 2,5" SSD with High Sierra installation 13.6 and 14.5 full installer - plugged in an USB-SATA Adapter on front USB port.

Changed simply nothing (AHCI Samsung Blade, flashed GTX680, FL1100 USB 3 in PCIe slots)
Click to expand...

Interesting--so you don't even have an NVMe drive? Then it seems we have to broaden this out to PCIe SSDs in general. Also interesting that you were able to do it via a USB>SATA bridge. When you did the fw update to 140.0.0.0.0 (and previous ones) were you using the Samsung blade? BTW is that the SSUBX?

Can you guys provide info in this format:

Able to flash 144.0.0.0.0 via NVMe?:
Actual cMP Model: 4,1 > 5,1 or 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive:
PCIe adapter model and PCIe Slot#:
 
Last edited:
Format really does not apply to me.

As I have stated in previous posts, I ran the 144.0.0.0.0 update from a (OS Installer, created with DiskMaker on a USB stick) plugged into an EtekCity Hub that was plugged into an Inateck USB 3 card plugged into PCIe slot 4. My Boot drive is a 970 Pro mounted on an I/O Crest card mounted in PCIe slot 2. Mac is a genuine 2010 5,1. Previous Boot ROM was 141.0.0.0.0.

Absolutely NO ISSUES!

Lou
 
Able to flash 144.0.0.0.0 via NVMe?:yes
Actual cMP Model: 4,1 > 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive: 512GB Samsung 970 Pro
NVMe in PCIe Slot: 2
 
Able to flash 144.0.0.0.0 via NVMe?:yes
Actual cMP Model: 4,1 > 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive: 512GB HP EX920
NVMe in PCIe Slot: 3
 
bookemdano said:
Can you guys provide info in this format:

Able to flash 144.0.0.0.0 via NVMe?:
Actual cMP Model: 4,1 > 5,1 or 5,1
Previous Bootrom: 140.0.0.0.0
NVMe Drive:
NVMe in PCIe Slot:
Click to expand...

Don't you think the NVMe carrier might be of some interest 1387914497.gif Some folks are listing it, some not.

Lou
 
  • Like
Reactions: crjackson2134
flowrider said:
Don't you think the NVMe carrier might be of some interestView attachment 839365 Some folks are listing it, some not.

Lou
Click to expand...

I didn't include it because there are already reports of differing results using the same PCIe adapter:

Highpoint 7101A:

NO
YES

Kyro M.2

NO (I too use this adapter and am also a NO)
YES

So I don't think that can be the culprit, unless we're looking at a combination of factors. But there's no harm in adding in that info.

So far I have not seen a NO from someone using a 970 Pro. EVO, yes (and other Samsung blades), but not Pro. Doesn't mean anything yet without more data points, but so far it's the only potential pattern I've noticed. Missed roobarb!'s edited post, who does have a 970 Pro and wasn't able to flash from it. So far, no pattern is apparent. Although, it seems he had a different issue going on with his EFI partition, so would like to see more results from folks with the 970 Pro to confirm.
 
Last edited:
mavots said:
Success!
Updated BootROM 140 >>> 144. Used an internal (SATA) SSD boot drive with the full installer. Disconnected all other attached internal drives and external enclosures. No issues. Then restarted with normal NVME/PCIe boot drive and updated OS with Combo 10.14.5 installer.
Click to expand...
Great!
 
haralds said:
I upgraded from 141.0.0.0.0. I already was on 10.14.5, so I ran the full installer just for the firmware part.
It seemed to take a long time both to get the process going and for the whole thing to complete.
1. I keep the power button depressed well past the flashing light until I hear a beep. Took quite a while.
2. It then trundled for a long time. I knew things were happening when it finally opened both of my CD drives. But it stayed on a black screen forever.
Click to expand...

It took about 1.25 Min. to update my Mac Pro from 142.0.0.0.0 to 144.0.0.0.0:
 
Last edited:
  • Like
Reactions: tsialex
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back