Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

bookemdano

macrumors 65816
Jul 29, 2011
1,424
805
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?

I dumped it prior to the 144.0.0.0.0 upgrade. I can send it to you on Tuesday when I am back at work.
 
Comment

fatespawn

macrumors regular
Feb 22, 2009
195
93
Chicagoish
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 have the Kryo m.2 PCIe adapter running a 970Pro NVME drive. I went directly from 140 to 144 without a problem.
 
Comment

bookemdano

macrumors 65816
Jul 29, 2011
1,424
805
Comment

hasseye

macrumors newbie
May 25, 2019
5
0
Yeah, sounds like it's not a straightforward cause. Is yours an authentic 5,1 or was it a 4,1 flashed to 5,1?

Anyway, let's try to consolidate this discussion to the dedicated thread for it so people don't have to hunt around for data points and info: https://forums.macrumors.com/thread...0-0-0-0-to-144-0-0-0-0-does-not-work.2182219/

Just wanted to thank everyone. I used a SATA drive and all worked out well the first time on both computer's. I am using a 4,1 to 5,1 so maybe that does have something to do with it?
 
Comment

Pressure

macrumors 601
May 30, 2006
4,276
501
Denmark
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 had no issues going from 140 to 144. I downloaded the full installer from the AppStore and upgraded the firmware that way.
 
  • Like
Reactions: crjackson2134
Comment

tsialex

macrumors G3
Original poster
Jun 13, 2016
9,416
10,146
Apologies alex, but what do you mean by 10.15 blocking mp5.1, have I missed some news?

10.15 won't support MP5,1 anymore, support starts with MP6,1

Screen Shot 2019-06-03 at 16.49.20.png
 
Comment

hasseye

macrumors newbie
May 25, 2019
5
0
I'm a little surprised ours don't support it. I guess I can see why Apple wouldn't want to officially support us given they finally have a new Mac Pro out, but as long as we have metal cards, I'm not sure what is stopping us from installing it. 2012 Macbookpros etc and 2012 iMacs are all compatible, what does there's have that we don't?

I wouldn't be surprised if "unofficially" we're able to install it. Although we won't get anymore firmware upgrades, but I appreciate Apple for still upgrading our firmware so far.
 
Comment

bsbeamer

macrumors 601
Sep 19, 2012
4,029
2,136
I'm a little surprised ours don't support it. I guess I can see why Apple wouldn't want to officially support us given they finally have a new Mac Pro out, but as long as we have metal cards, I'm not sure what is stopping us from installing it. 2012 Macbookpros etc and 2012 iMacs are all compatible, what does there's have that we don't?

I wouldn't be surprised if "unofficially" we're able to install it. Although we won't get anymore firmware upgrades, but I appreciate Apple for still upgrading our firmware so far.

BLAME INTEL. The lack of microcode updates for all MP5,1 issued CPUs for the recent vulnerabilities are likely the main reason 10.15 will officially be unsupported.
 
Comment

hasseye

macrumors newbie
May 25, 2019
5
0
BLAME INTEL. The lack of microcode updates for all MP5,1 issued CPUs for the recent vulnerabilities are likely the main reason 10.15 will officially be unsupported.
Great great point. Why would Apple want to support something that has security vulnerabilities. Apple would then need to spend time trying to patch Intel's problems. For them, there's no reason to do so.

For us Mac Pro 5,1 fans, hold out hope. I believe we'll be able to install it unofficially, as everything I've read and saw if it supports Mojave it supports Catalina.
 
Comment

tsialex

macrumors G3
Original poster
Jun 13, 2016
9,416
10,146
Great great point. Why would Apple want to support something that has security vulnerabilities. Apple would then need to spend time trying to patch Intel's problems. For them, there's no reason to do so.

For us Mac Pro 5,1 fans, hold out hope. I believe we'll be able to install it unofficially, as everything I've read and saw if it supports Mojave it supports Catalina.
MP5,1: Catalina Developer Preview works, more or less…
 
Comment

tsialex

macrumors G3
Original poster
Jun 13, 2016
9,416
10,146
10.14.6 DP2 released, downloading it now. Build is 18G48f.

Screen Shot 2019-06-11 at 14.02.58.png
[doublepost=1560273955][/doublepost]10.14.6 DP2 EFI Version table for non BridgeOS Macs:

(All Macs that have Mojave support had firmware upgrades, except MP5,1)


Some Macs BootROM versions are now two versions over, btw.
Mac:EFI version:
IM13,1286.0.0.0.0
IM14,1138.0.0.0.0
IM14,2138.0.0.0.0
IM14,3138.0.0.0.0
IM14,4198.0.0.0.0
IM15,1229.0.0.0.0
IM16,1228.0.0.0.0
IM16,2228.0.0.0.0
IM17,1168.0.0.0.0
IM18,1173.0.0.0.0
IM18,3173.0.0.0.0
IM19,1220.270.076.0.0
MB10,1176.0.0.0.0
MB8,1182.0.0.0.0
MB9,1182.0.0.0.0
MBA5,1258.0.0.0.0
MBA6,1116.0.0.0.0
MBA7,1187.0.0.0.0
MBP10,1256.0.0.0.0
MBP10,2279.0.0.0.0
MBP11,1155.0.0.0.0
MBP11,2155.0.0.0.0
MBP11,4193.0.0.0.0
MBP12,1185.0.0.0.0
MBP13,1234.0.0.0.0
MBP13,2257.0.0.0.0
MBP13,3257.0.0.0.0
MBP14,1196.0.0.0.0
MBP14,2196.0.0.0.0
MBP14,3196.0.0.0.0
MBP9,1227.0.0.0.0
MM6,1279.0.0.0.0
MM7,1243.0.0.0.0
MP5,1144.0.0.0.0
MP6,1131.0.0.0.0

Code:
$IBIOSI$ MP61.88Z.F000.B00.1905251553
Copyright (c) 2005-2019 Apple Inc.  All rights reserved.
Apple ROM Version
  Model:        MP61
  EFI Version:  131.0.0.0.0
  Built by:     root@saumon
  Date:         Sat May 25 15:53:29 PDT 2019
  Revision:     131 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, Release
  Compiler:     Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)
 
Last edited:
Comment

trifero

macrumors 68000
May 21, 2009
1,527
1,134
Comment

tsialex

macrumors G3
Original poster
Jun 13, 2016
9,416
10,146
Second useless* info of the day:

If you have a bricked backplane, restored MP51.fd to it and then you run BlankBoardSerializer, the only thing added is the SSN, all other hardwareIDs will be blank.

Screen Shot 2019-06-14 at 08.31.54.png

Screen Shot 2019-06-14 at 08.32.19.png


blank.0.jpg
blank.1.jpg
blank.2.jpg
blank.3.jpg
blank.4.jpg
blank.5.jpg
blank.6.jpg
blank.7.jpg


*Btw, it's not useless info per se, but it's an useless application of BBS. You still need to do a reconstruction of your hardwareIDs.
 
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.