Ok, so it´s that. Many years ago that I don´t try a BT keyboard for that. Only USB. Failed so many times...
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
Ok, I'll post in this thread since I do not want to pollute the other thread with a problem that belongs here.
My situation is the following:
A few days ago my system (cMP 5,1) was running OpenCore 0.7.2 (martin's package), Big Sur 11.2.3 on PCIe NVMe, Mojave on internal SSD and Windows 10 on internal SSD (as far as I know it was installed in Legacy mode).
On Monday I decided to update Big Sur on my NVMe to 11.5.2 but I forgot to set the emulate flag in the OpenCore config.plist
This caused an unsuccessful install of 11.5.2 (of-course) an the Mac was stuck in a boot cycle where after rebooting it kept displaying the following message:
After this I booted back into Mojave, wiped the NVMe and Installed Catalina instead (this time setting the emulate flag in the config.plist like I should have done the first time around). All went fine and Catalina is running fine. But I noticed I lost my Windows 10 entry in the OpenCore bootpicker screen. The only entries left are Catalina and Mojave.
I am however able to adress the Windows 10 SSD using Parallels to load it as a 'BootCamp' partition. Everything there is running as it should and I checked again if it was running in Legacy mode and it was.
Now, when logged into Catalina (on the NVMe) and after waking up from sleep, the computer fails to wake up and reboots and gives me the same warning message displayed in the picture above.
Someone hinted me that my bootROM might be affected (I never booted into Windows without OpenCore and as far as I know, Windows always ran in Legacy mode not UEFI).
So I checked my bootROM in system information and saw this:
Now, I know from the las time I updated/flashed the ROM back in 2019 that the Boot ROM should be version 144.0.0.0.0 and not what is displayed here.
So what might be going on here, what likely happened? And can I simply re-flash again to version 144.0.0.0.0 ?
My situation is the following:
A few days ago my system (cMP 5,1) was running OpenCore 0.7.2 (martin's package), Big Sur 11.2.3 on PCIe NVMe, Mojave on internal SSD and Windows 10 on internal SSD (as far as I know it was installed in Legacy mode).
On Monday I decided to update Big Sur on my NVMe to 11.5.2 but I forgot to set the emulate flag in the OpenCore config.plist
This caused an unsuccessful install of 11.5.2 (of-course) an the Mac was stuck in a boot cycle where after rebooting it kept displaying the following message:
After this I booted back into Mojave, wiped the NVMe and Installed Catalina instead (this time setting the emulate flag in the config.plist like I should have done the first time around). All went fine and Catalina is running fine. But I noticed I lost my Windows 10 entry in the OpenCore bootpicker screen. The only entries left are Catalina and Mojave.
I am however able to adress the Windows 10 SSD using Parallels to load it as a 'BootCamp' partition. Everything there is running as it should and I checked again if it was running in Legacy mode and it was.
Now, when logged into Catalina (on the NVMe) and after waking up from sleep, the computer fails to wake up and reboots and gives me the same warning message displayed in the picture above.
Someone hinted me that my bootROM might be affected (I never booted into Windows without OpenCore and as far as I know, Windows always ran in Legacy mode not UEFI).
So I checked my bootROM in system information and saw this:
Now, I know from the las time I updated/flashed the ROM back in 2019 that the Boot ROM should be version 144.0.0.0.0 and not what is displayed here.
So what might be going on here, what likely happened? And can I simply re-flash again to version 144.0.0.0.0 ?
Nothing here, it's just spoofing from OC, to block unwanted updates from iMacPro or MacPro7,1.
You could have several other problems, but the EFI release is not one.
Ok, a small update.. I removed OpenCore 0.7.2 from the EFI of my boot drive and rebooted (into Mojave obviosly). This time System Information shows the correct Boot ROM version:
So now I know the Boot ROM is still as it should be. That still leaves me with the wonder why the Windows drive won't whow up in the bootpicker when OpenCore is loaded and why I'm getting the reboot with the warning message afterwards when waking up from sleep when in Catalina.
So now I know the Boot ROM is still as it should be. That still leaves me with the wonder why the Windows drive won't whow up in the bootpicker when OpenCore is loaded and why I'm getting the reboot with the warning message afterwards when waking up from sleep when in Catalina.
OpenCore is not compatible with BootCamp/CSM/BIOS Windows installs, only works chain loading from another loader.
KPs when waking from sleep are usually RTC battery related, or your NVRAM volume could be corrupted - usually the first overtime will cause the later one - check your VSS stores.
Thanks for replying. That's strange.. it worked fine before with OpenCore (Martin's package). What are VSS stores and how do I check them?
You are mistaken, unless you chain loaded with MyBootMgr or rEFIndPlus, it never ever worked. OpenCore explicitly warns about the compatibility only with UEFI Windows installs from the get go.
If you previously had a Mac EFI flashed GPU, you could also bypass OC and load the CSM/BIOS/BootCamp Windows directly.
VSS stores are the main and secondary areas of variable storage inside the NVRAM volume, a component of the BootROM.
Start checking with this post below:
OpenCore on the Mac Pro
Thank you @tsialex as always! Your knowledge overwhelms me! I have fixed my problem just reflashing BootROM using the reconstructed one that you made it for me. Now everything is ok again
forums.macrumors.com
Yes.
Just from looking at the number of invalid entries inside the main VSS store and the pristine secondary one, I already know that you have a failed garbage collection and will need a BootROM reconstruction.
Check your Mac Pro BR2032 RTC battery voltage with a voltmeter right now - a brick is the most probable outcome if you continue like this and will happen soon with all these invalid entries.
Sure, but you need to replace it with a real BR2032 and not a CR2032 one that have a chemistry formulation not appropriated for the high temperatures near the GPU heatsink.
Btw, replacing the RTC battery will only solve the crashes that happened because of the RTC time related counters being stuck when sleeping. The damage to the SPI flash memory NAND cells overuse after the garbage collection failed (plus the 9/11/12 years of previous usage) and the KPs being saved inside the main VSS store will only be solved with a SPI flash replacement (you can replace the SPI flash on the cheap if you can desolder/solder a 8-pin SMD chip or buy a MATT card) and a BootROM reconstruction.
Ok, that's it then. I am screwed. Because I am not able to do that (the battery replacement I can do ofcourse). Damn.
You have two options at this point:
- If you can have some downtime with your Mac Pro:
- Buy a BR2032 from DigiKey/Mouser/Farnel/Richelt/etc, replace the RTC battery
- Do a BootROM reconstruction, I'll send you a PM, flash it back
- When the SPI flash memory fails, could happen tomorrow or six months from now, you buy a Mac Pro MATT card, install it, then flash your own Mac Pro BootROM reconstructed image to it, problem solved.
- If you can't have any downtime with your Mac Pro:
- Buy a BR2032 from DigiKey/Mouser/Farnel/Richelt/etc, replace the RTC battery
- Do a BootROM reconstruction, I'll send you a PM, flash it back
- Buy a Mac Pro MATT card from cmizapper, install it, flash your own Mac Pro BootROM reconstructed image to it, problem solved with zero downtime.
I told you this was the right place for your probem. @tsialex is one of the most skilled guy in this stuff I have seen in my life. And been using macs since 1988. I really advice you to obtain a ROM reconstruction from him. We are a lot that we have it, and it´s almost mandatory. I reflash from time to ime.
@tsialex , is it possible that I read from you same time ago about the MATT card , some about not as good as a proper bootrom?
Last edited:
I can echo this, Alex reconstructed my messed up BootROM very recently, and I feel quite relieved that I got it done before anything went wrong. I can't recommend his excellent and detailed service enough!
Thanks for all the tip guys. This is exactly what I did. Alex has been very helpful, professional and consice in getting my problem fixed.
MATT cards are not a plug and play solution as cmizapper documentation let you think it is, it's a solid hardware and well designed, but the BootROM image that cmizapper flashes to it is a clone of a mid-2010 Mac Pro with SSN GJ0340TXH2N, while it will let you boot right after installed, Apple will block the Mac Pro from accessing iCloud/Messages/FaceTime since it's a widely used clone. You need to flash the Mac Pro own firmware to the MATT card.
Read this post for more details:
Mac OS 11.3 has broken support for older Mac Pros
I'm glad to answer, but this is a very old topic that I've written extensively about all pros and cons, use the search for MATT written by me, you will find more than you ever want to read about this. SPI flash has a limited life, if your Mac Pro has being in use continuously, it's probably...
forums.macrumors.com
Thanks, Alexandre. All clear now.MATT cards are not a plug and play solution as cmizapper documentation let you think it is, it's a solid hardware and well designed, but the BootROM image that cmizapper flashes to it is a clone of a mid-2010 Mac Pro with SSN GJ0340TXH2N, while it will let you boot right after installed, Apple will block the Mac Pro from accessing iCloud/Messages/FaceTime since it's a widely used clone. You need to flash the Mac Pro own firmware to the MATT card.
Read this post for more details:
Mac OS 11.3 has broken support for older Mac Pros
I'm glad to answer, but this is a very old topic that I've written extensively about all pros and cons, use the search for MATT written by me, you will find more than you ever want to read about this. SPI flash has a limited life, if your Mac Pro has being in use continuously, it's probably...
hi, i just want to flash my 5,1 rom from MP51.007F.B03 to latest, and i want to stay with high sierra using my new nvme card, how do i do it, I have an 5770 card. is it worth dumping my existing rom ? thanks
A METAL GPU is a requirement for the upgrade process, the workaround is a BootROM reconstruction (but it's a firmware engineer job).
If you can borrow a METAL GPU, the whole process is explained here:
MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)
Please fully read this first post, you will probably find that you have one or more problems described into the various notes below. Mojave will only install if you have upgraded your BootROM to the current release and your Mac Pro have a Metal capable GPU*. If you are trying to install Mojave...
forums.macrumors.com
For a BootROM reconstruction, see your PM.