Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
  • Like
Reactions: Flint Ironstag
I have a quick and dirty guide on how to patch the BootROM your self here: https://forums.macrumors.com/thread...issing-microcode.2121072/page-2#post-26111525

however if your (understandably so) uncomfortable with patching the BootROM yourself, feel free to Dump your BootROM and PM it to me, ill patch in updated Nehalem and Westmere Microcodes and send it back to you where you just flash it onto your MP5,1 :)

OK. So

1) I am with the 0087.B00 firmware. I should use the 0085.B00 firmware for microcode patching, and flash that to replace my current 0087.B00 firmware, isn't it?

2) I've already

a) Open the 0085.B00 with this Hex editor (https://itunes.apple.com/hk/app/ihex-hex-editor/id909566003?l=en&mt=12)
b) search the old microcode
c) replace all matched block by the new microcode
d) save it to a new file

This is how I did it.
Screen Shot 2018-06-07 at 17.05.15.jpg

The new ROM is attached, can you double check if my own ROM image is correctly edited?

(Just in case some other users NOT closely following this topic, please do NOT download this ROM to use. It may brick your Mac. And the serial number won't match your Mac as well)

3) If the patched file is correct, then I only need to use the ROMTool to flash it. Correct?
I never use ROMTool to flash anything. My plan is

a) rename the new ROM image file to MP51_0087_01B_LOCKED.fd
b) Open ROMTool, choose "Flash System ROM"
c) follow the onscreen instruction (if any) to finish the flash.

Million thanks in advance.
 

Attachments

  • 0085.B00_ws30.bin.zip
    1.7 MB · Views: 308
  • Like
Reactions: LightBulbFun
yep everything checks out fine on my end :) (you dont have to re-name the ROM for ROMTool BTW)

Awesome guide btw :) (much better then what I quickly knocked up LOL I completely forgot that find and replace was thing...)
 
yep everything checks out fine on my end :) (you dont have to re-name the ROM for ROMTool BTW)

Awesome guide btw :) (much better then what I quickly knocked up LOL I completely forgot that find and replace was thing...)


Not sure what I’ve done wrong.

1) Open ROMTool
2) it says put the Mac in firmware flashing mode. So I did that.
3) after flashing LED and long beep boot to desktop
4) Open ROMTool again
5) pick the modded bin file
6) flashed
7) reboot

And all I have is this soild white screen now regardless which CPU I insert
EE5947F0-2D55-41B0-84DF-8FD518E7B44C.jpeg


Then go black after few more seconds, and self shutdown in about a minute.
Any idea how to recover?


Update 1: I can perform PRAM reset, but nil help. (this is good sign)

And after PRAM reset, no more white screen, but pure black screen then self shutdown.


Update 2: it seems I kill my Mac (this looks like a bad sign, but eventually because my Mac is 100% good)

Due to the firmware is successfully updated. I cannot get my Mac into firmware restoratation mode.


Update 3: False alarm

After ROM flashing. It automatically revert to boot from bay 1 HDD (same as after PRAM reset). And coincidentally which is a HDD that installed Clover before, but removed.

May be due to the improper uninstallation. The HDD stuck at boot, than self shutdown.

After I pull that HDD out. And insert a known good Yosemite HDD in bay 1, my mac boot to desktop again.
 
Last edited:
Not sure what I’ve done wrong.

1) Open ROMTool
2) it says put the Mac in firmware flashing mode. So I did that.
3) after flashing LED and long beep boot to desktop
4) Open ROMTool again
5) pick the modded bin file
6) flashed
7) reboot

And all I have is this soild white screen now regardless which CPU I insert
View attachment 765164

Then go black after few more seconds, and self shutdown in about a minute.

Any idea how to recover?

Update 1: I can perform PRAM reset, but nil help.

thats very odd, :confused: this is exactly why im quite reluctant when someone says "I have thing your looking to experiment with let me test for you" as I dont want to brick someone else's machine, with this 5,1 Microcode thing I had tested it extensively on my MacPro5,1 and 3 Mac Pro 5,1s that @Surrat own

your BootROM size did not change and your microcodes are in the right place, I wonder if somehow the hex editor it self corrupted something? I use Hex fiend my self.

does the machine chime? Have you tried stripping the Mac Pro back to bare essentials? this looks like the same issue this guy had https://forums.macrumors.com/threads/mp51-0084-b00-rom-dump-request.2119496/page-11#post-26112132

did you try the Dual CPU tray?

try pulling the Mac Pros PRAM battery to properly reset everything and try resetting the SMC

finally if all else fails

try running the Mac Pro Firmware Recovery CD image and see if that kicks the machine into gear

https://support.apple.com/kb/dl1320?locale=en_US
[doublepost=1528367968][/doublepost]
Not sure what I’ve done wrong.

After I pull that HDD out. And insert a known good Yosemite HDD in bay 1, my mac boot to desktop again.


oh sweet thank F*ck I was sh*tting my self there thinking i had broken someone else computer :eek:

so does your microcode Report back 30 for Westmere or 28 for Nehalem? :D
 
Last edited:
thats very odd, :confused: this is exactly why im quite reluctant when someone says "I have thing your looking to experiment with let me test for you" as I dont want to brick someone else's machine, with this 5,1 Microcode thing I had tested it extensively on my MacPro5,1 and 3 Mac Pro 5,1s that @Surrat own

your BootROM size did not change and your microcodes are in the right place, I wonder if somehow the hex editor it self corrupted something? I use Hex fiend my self.

does the machine chime? Have you tried stripping the Mac Pro back to bare essentials? this looks like the same issue this guy had https://forums.macrumors.com/threads/mp51-0084-b00-rom-dump-request.2119496/page-11#post-26112132

did you try the Dual CPU tray?

try pulling the Mac Pros PRAM battery to properly reset everything and try resetting the SMC

finally if all else fails

try running the Mac Pro Firmware Recovery CD image and see if that kicks the machine into gear

https://support.apple.com/kb/dl1320?locale=en_US

Sorry for my false alarm. That “failure post” is updated”

The Mac can boot with both CPU tray.
 
  • Like
Reactions: LightBulbFun
oh sweet thank F*ck I was sh*tting my self there thinking i had broken someone else computer :eek:

Please don’t worry on this. It’s my own 100% responsibility if I brick my Mac. I am the one who willing the put my Mac to test. And I appreciate you share all your knowledge here. Please don’t feel bad (even if I really brick it).
[doublepost=1528368351][/doublepost]Doing some follow up actions now. e.g. reselect the correct boot drive. Swapping back the HDD. Re-enable Nvidia web driver. And disable SIP etc.

Will report the microcode version once in about 5-10 minutes.

Eventually it's actually a big success, microcode version 30 on a W3690.
Screen Shot 2018-06-07 at 18.49.24.png


I should pull out all unrelated hard drive before this test, it's my own fault, I am very very sorry for creating the unnecessary panic. But I will still keep that post there. Just let the other know what can happen. And how to recover.
 
Last edited:
Awesome glad the microcode worked in the end :)

also glad that it works with the W3690, suck it intel :D

and now people have nice guide they can follow if they wish to patch their own BootROM :)

BTW if your MP has windows on it it would be interesting to see what this tool reports https://www.grc.com/inspectre.htm .
 
Something smells fishy to me.

The fact Apple hasn't determined what GPUs are technically usable... Even so the older cards like the 680 ATI 7 series are old cards and there are no official metal supported cards from Apple. Let alone cards that are even close to being supported by programs with GPU acceleration.

CC minimum requirements are:
ATI: R9 and above
Nvidia: GTX 760 and above

Although yes you can use them, supported and officially supported are two entirely different things.

So are Apple just going to support unsupported cards that dont have Apple EFIs for no boot screens and just leave it at that? Like it has been for years? If this is the case its not really an Apple supported product? Very confusing this announcement.

In classic apple fashion there will probably be no official documentation and as the machines are way out of support why would they?

Its like saying yes its supported, but not with your card... so technically its not supported. With no official cards how are you supposed to have confidence that drivers will be up to date and work correctly? As a Pro you cant really sit back and hope... no point waiting on a whim.

Its all well and good for the tinkerers that like having a modular machine... but for people actually using these for day to day work its not acceptable. It is wrong that people are still using the cMP these day to day 9 years later but what other choice do people have? The Trashcan isnt a decent alternative and in most aspects doesn't have much more horse power. The iMac Pro is a completely different product and not comparable, with the amount of problems they have had with this parts bin special that just one more reason not to buy one. Let alone the lack of actual support.

I cant see Apple all of a sudden releasing Apple spec cards and I cant see them removing the EFI constraint for boot screens either.

Although tbh the only machine that this actually has any issue with boot screens these days is the Mac pro all the others are non up-gradable and will always use the built in GPU for boot.

Its all a bit of a white wash. It feels like Apple is saying the 5,1 mac pro is supported and everyone is super happy... yet it feels like they might pull the plug when it comes to launch.

They may have made progress with the 2019 MP by the time Mojave is released and think... you know what this is a waste of our time and resources to get it working correctly... how many people are honestly working on 9 year old machines...

Well lots of us but we are insignificant compared to the rest of the apple line up.

Or am I looking at this all wrong?
 
Awesome glad the microcode worked in the end :)

also glad that it works with the W3690, suck it intel :D

and now people have nice guide they can follow if they wish to patch their own BootROM :)

BTW if your MP has windows on it it would be interesting to see what this tool reports https://www.grc.com/inspectre.htm .

Can’t boot to Windows 10 now. “Unsupported processor” for both upgraded / original tray.
604A9D85-86F2-4A58-B43E-49FFA002A0B8.jpeg


Windows try to repair it, then failed in few seconds, restart, and the same error happen again....... until force shutdown.
 
Last edited:
They may have made progress with the 2019 MP by the time Mojave is released and think... you know what this is a waste of our time and resources to get it working correctly... how many people are honestly working on 9 year old machines...

Well lots of us but we are insignificant compared to the rest of the apple line up.

Or am I looking at this all wrong?
Inside Apple, the discussion and conclusion about whether the cMP thing is a waste of time and resources will have already happened BEFORE the Mojave reveal, not after...
 
  • Like
Reactions: mbosse
Can’t boot to Windows 10 now. “Unsupported processor” for both upgraded / original tray.

Windows try to repair it, then failed in few seconds, restart, and the same error happen again....... until force shutdown.

interesting how is windows installed via EFI or BIOS?

with my MP5,1 I have windows 10 installed via EFI mode

and with a microcode patched BootROM windows 10 will just reboot the machine a few seconds after displaying the windows logo

when I flash back the stock BootROM windows 10 boots fine, however before all of this I had booted windows 10 on 0087 with no Microcode and I noticed windows 10 itself was loading Microcode version 15, so I was wondering if with the patched BootROM windows 10 was trying to load an older microcode then what was already there and falling over itself, it looks like this is not the case as I dont think you have run windows 10 on 0087 have you? (does raise the question does the windows 10 installer still boot with the patched BR?)
 
interesting how is windows installed via EFI or BIOS?

with my MP5,1 I have windows 10 installed via EFI mode

and with a microcode patched BootROM windows 10 will just reboot the machine a few seconds after displaying the windows logo

when I flash back the stock BootROM windows 10 boots fine, however before all of this I had booted windows 10 on 0087 with no Microcode and I noticed windows 10 itself was loading Microcode version 15, so I was wondering if with the patched BootROM windows 10 was trying to load an older microcode then what was already there and falling over itself, it looks like this is not the case as I dont think you have run windows 10 on 0087 have you? (does raise the question does the windows 10 installer still boot with the patched BR?)

My Windows 10 is the legacy installation. Will try an EFI installation after dinner.

And it can boot with both unmodded 0085 and 0087 firmware
 
  • Like
Reactions: LightBulbFun
Inside Apple, the discussion and conclusion about whether the cMP thing is a waste of time and resources will have already happened BEFORE the Mojave reveal, not after...

It has happened before... 06 Mac Pro had Mountain Lion support on announcement and was dropped at launch. Obviously you can update it but not officially.
 
  • Like
Reactions: frou
Apple says No

I say Yes :D

(I had a quick look at the GPU drivers everything pre-metal has been purged, interesting NVIDIA fermi drivers are still there so does Fermi actually support metal? i Remember that being a bit debated "back in the day" no NVIDIA drivers newer then kepler tho sadly)

How did you do it?
installed via a supported mac?
 
My Windows 10 is the legacy installation. Will try an EFI installation after dinner.

And it can boot with both unmodded 0085 and 0087 firmware

I can install Windows 10 EFI mode via a disc. Still going through the initial driver installation. Will run the Spectre test later.
 
  • Like
Reactions: LightBulbFun
Something smells fishy to me.

The fact Apple hasn't determined what GPUs are technically usable...

My thoughts exactly. My first impulse is to race out and grab a metal-capable GPU for my 5,1 before used prices go through the roof. HOWEVER, given the pause on support for 5,1, I am hesitant that it will be so simple as to throw in any old metal-cap GPU... I'm going to wait for the chips to fall before putting any more money into my six-year old box (loaded as it is).

As a Pro you cant really sit back and hope...

Tinkering with drivers and firmware updates on a production machine is risky business for sure! Pro apps won't require 10.14 for a long while. So unless you are a game dev, I see no reason to rush on this.
 
However small, there is still a chance we will see new model official PCIe GPUs from AMD and/or NVIDIA built for Mac at some point before Mojave is released. That could be part of the hold up for official recommendations.

IF the mMP/7,1 has or supports standard PCIe slots (as most here hope it does) both AMD and NVIDIA will (likely) want to get their cards onto the latest Pro Mac machines, or at least offer them as upgrades. This can be done two ways: through installing PC cards and dealing with the residual issues, or made for Mac cards. The approach method and technical requirement ultimately comes down to how Apple is handling EFI in the next generation of MacPro (or the next box/cube/hub being called MacPro). The resulting implications for the 5,1 (and upgraded 4,1) are basically dependent on how the 7,1 is paving the path.

Since eGPU is now an official thing for Mac, and the RX580 (plus some other AMD) is officially supported by the OS, manufacturers are (at worst) prepping to get cards installed in external enclosures that are compatible with Mac to meet market demands. AMD is officially supported this way and I'm sure NVIDIA would like to be before they get shutout of the next generation of Mac completely.

NVIDIA is not releasing the next GPU platform (11XX cards) for awhile. Making the 10XX series (or at least 1080) work well with NVIDIA drivers, or making a Mac version of the GTX 1080 MIGHT be something they're considering. Again, all depends on if the 7,1 has PCIe slots and if the GTX 1080 will still be the top of the line GeForce card at that time the 7,1 comes to market.

I'm sure AMD and NVIDIA are keeping a close eye and (at least one) likely know where things with the 7,1 are heading. Beyond that, if you believe Apple is going to make desktop class GPUs on their own in the future, then none of this matters. You'll either buy into that system or you will not. I think that would result as part of a larger exit from the platform for many Professionals (if OpenCL/GL abandonment doesn't already).
 
  • Like
Reactions: mbosse
@LightBulbFun Sorry to be dense, I've reads your posts on the microcode, but still don't understand the reasons. Could you explain to me what the benefit is of editing it is?
 
However small, there is still a chance we will see new model official PCIe GPUs from AMD and/or NVIDIA built for Mac at some point before Mojave is released. That could be part of the hold up for official recommendations.

IF the mMP/7,1 has or supports standard PCIe slots (as most here hope it does) both AMD and NVIDIA will (likely) want to get their cards onto the latest Pro Mac machines, or at least offer them as upgrades. This can be done two ways: through installing PC cards and dealing with the residual issues, or made for Mac cards. The approach method and technical requirement ultimately comes down to how Apple is handling EFI in the next generation of MacPro (or the next box/cube/hub being called MacPro). The resulting implications for the 5,1 (and upgraded 4,1) are basically dependent on how the 7,1 is paving the path.

Since eGPU is now an official thing for Mac, and the RX580 (plus some other AMD) is officially supported by the OS, manufacturers are (at worst) prepping to get cards installed in external enclosures that are compatible with Mac to meet market demands. AMD is officially supported this way and I'm sure NVIDIA would like to be before they get shutout of the next generation of Mac completely.

NVIDIA is not releasing the next GPU platform (11XX cards) for awhile. Making the 10XX series (or at least 1080) work well with NVIDIA drivers, or making a Mac version of the GTX 1080 MIGHT be something they're considering. Again, all depends on if the 7,1 has PCIe slots and if the GTX 1080 will still be the top of the line GeForce card at that time the 7,1 comes to market.

I'm sure AMD and NVIDIA are keeping a close eye and (at least one) likely know where things with the 7,1 are heading. Beyond that, if you believe Apple is going to make desktop class GPUs on their own in the future, then none of this matters. You'll either buy into that system or you will not. I think that would result as part of a larger exit from the platform for many Professionals (if OpenCL/GL abandonment doesn't already).

Why, there are plenty of cards out now that should be fully supported, why bother with cards that dont exist concentrate on cards people can actually buy now!

TBH I dont think Nvidia or AMD care. The mac pro platform is minuscule and apple has made it difficult for them. Neither will be scrambling at all.

At the same time Apple hasnt had a proper pro machine for a decade, how many pros are still in the Apple camp that need a high end workstation? Honestly... its all nostalgia, too late. Apple really has done one over on itself.

I work for a large media corporation in the UK and they got rid of production macs 3 years ago for Dell workstations that are up-gradable, can have 6 drives with 2 NVME, twin CPU and graphics cards all internally. CC works better on the PC because they can be tailored to specific applications rather than having to deal with what apples deems necessary. High sierra was a bust on launch for all those customers which had quite a ripple through the community as most who upgraded had weeks of issues with compatibility.

This and the state of the Macbook Pro... pro customers have been given the bird.

Im sorry but I cant see more than 1% of mac users buying an EGPU they are beyond niche apart from the heaviest of users. The fact they perform at 90% of a PCI card and cost another £3-400 to buy an enclosure, it makes no financial sense at all. Even with an external GPU its for acceleration it doesn't need and EFI bootloader as the internal graphics cards deal with it.

It shows how much of a niche that this is, Apple hasnt got its own first party hardware and there are very very few options still although it was launched over a year ago.

The EGPU is a work around for a problem created by apple.

Apple is stripping the gaming community out of the mac too so there goes the small amount that game too.

The whole situation is just crazy, cant believe apple have let it get to this point and how long its taking them to come up with even the slightest turn around.
 
Theory - as I've heard tell, Apple has hundreds of 5,1s at HQ, and they're one of the standard machines anyone checks out to use when they want to do anything new, mainly because they're the most generic, flexible and quirkless mac Apple made. Brick the OS, just pull the sled, etc etc. My suspicion is there's a lot of "for Apple's internal convenience" in keeping the OS up to date on them. That, and they know there's going to be a lot of production houses that are "it's going to be a PC, and Windows for ever if we don't get a Mac Pro we want" waiting, and it's more important to them to keep those folks able to keep their software, especially Apple's "Pro" apps, up to date.
 
@LightBulbFun Sorry to be dense, I've reads your posts on the microcode, but still don't understand the reasons. Could you explain to me what the benefit is of editing it is?

microcode is a very small very low level piece of software that runs on a CPU and is used to interact with the CPU at a very low level, often fixing bugs improving performance or providing support for a specific CPU/architecture

in the Mac Pro 5,1s case im updating/patching in new microcode to a version that has patches against the spectre vulnerabilities/security flaws...

(another prime example of why one might want/need to patch in new microcode is when installing a Penryn based CPU to a PC motherboard, without microcode the CPU loses SSE4.1 VT-x and some other instruction sets needed to boot 64bit windows 8+ for example when installing LGA771 CPUs into a LGA775 motherboard most motherboards dont have 771 microcodes and as such Harpertown Xeons will be missing these instructions and not function properly being stuck at a 6x multiplier until you patch in 771 microcode then they work properly :) )
 
  • Like
Reactions: Supermacguy
@LightBulbFun do you know wich Firmware version it installs on our 5.1 Mac Pro? did you check?

View attachment 765191

Mojave contains MP51.0087.B00 I dont recommend you install that Firmware update currently

you can delete the FW update files from inside the installer by right clicking the installer.app, show package Contents /Contents/Resources/Firmware and deleting the files inside the "Firmware" folder and doing so will stop the installer from prompting you to update your FW.
 
  • Like
Reactions: lilins
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.