I can take a look at your BootROM image. I'll send the instructions via PM on how to dump it correctly and other things that are needed to validate your BootROM, get everything as instructed and I'll get back to you.
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
He analyzed a log file. Never thought about someone throwing a log file to the test firmware part of the script. Maybe I do some probing before, just in case.
@tsialex - I installed a MATT card (taking that route rather than soldering) and flashed my reconstructed ROM. All is working well.
I am assuming that I still should (to be careful) reflash with my reconstructed ROM periodically. Prior to installing the MATT card I was on a 90 day reflash cycle. My plan is to do that same with the MATT card installed. Thoughts?
I am assuming that I still should (to be careful) reflash with my reconstructed ROM periodically. Prior to installing the MATT card I was on a 90 day reflash cycle. My plan is to do that same with the MATT card installed. Thoughts?
Nice!
MATT card being installed don't change the fact that the MacPro5,1 NVRAM design/size is insufficient for modern macOS requirements.
@tsialex - thanks for the confirmation on reflashing.
Installing the MATT card was very easy and now I have protection against SPI failure. As another note to protect my iCloud accounts I disabled wifi until I flashed my reconstructed ROM to the MATT card and verified "About This Mac" showed my serial number.
I will say "Thank you" again for all your advice and time on this forum as well as your reconstruction services.
@tsialex yes. I did have a microscope available and was able to read that it was a Macronix 25L3205D (it was so faint I couldn't read it any other way). At about the same time cmizapper responded to my email with the same information.
Several times I had to wet the laser etched chip markings to read it when it's faint. Glad that worked out.
Can't it be replaced with MX25L6406E? That's the one in MP6,1 and its size is basically double.
Physically, sure. Logically, only half will be addressed.
Not comparable/related in anyway and not possible without the source code of the full EFI. This is not a possibility.
This is from efiflasher generic codebase, but not all work with MacPro5,1. The MacPro5,1 supported SPI flashes are:
- SST 25VF032B
- Macronix MX25L3205A or MX25L3205D
- Macronix MX25L3206E
While not listed inside efiflasher, there are one more Macronix SPI flash model that can be used, several people used it, MX25L3208E.
I have checked with UEFITool and 2nd VSS store is nowhere to be found. It wasn't there even before the first update, it definitely needs a reconstruction.
It is not updated to 144.0.0.0.0 yet. Should I go ahead with the update or we can go directly to reconstruction?
The only way to get a pristine BootROM image again is via reconstruction (clean-up/upgrade to the most recent components/reconstruction), see the PM I've sent you.
@tsialex Happy New Year!
I have a mid 2012 tower - and I think I may have buggered up the BootROM by trying to install Windows 11 multiple times - failed, but manage to install after almost giving up. Never knew about the X509 certificates. I
I am running Catalina with the DosDude1 patch - 144.0.0.0.0. (done it the High-Sierra/Mojave process) withe GTX 680 2GB GPU.
The start up seems sluggish - when the Win11 disk is connected (which I have removed now - only the MacOS connected), I get the Blue screen and the system is corrupted, MacOS starts up okay, but slightly slow. Also the Recovery partition is not showing up as well (did use to show up in the past). I also had Windows 10 installed on another disk, which has been removed.
Could you please send the instructions to check my BootROM correctly and safely to see if there are any issues? I want to run only MacOS - got a separate machine for Windows. Cheers.
Sure, check your PM. From what you wrote above, you gonna need the reconstruction service ASAP. Multiple Windows SecureBoot combos (dbs/PKs/X509s) => failed garbage collection => brick.
@tsialex Mind sharing those instructions with me as well? When setting up my 5,1 I inadvertently somehow briefly ended up with Windows 10 UEFI installed from a DVD before realizing this and reinstalling in Legacy mode. Went through a few boots so would like to check to make sure my Bootrom is okay or if I need to reconstruct it.
I've sent the instructions via PM on how to dump it correctly and other things that are needed to validate your BootROM, get everything exactly as instructed and I'll get back to you.