Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Hi @tsialex
Could you PM me for BootROM reconstructing service?
My MP5,1 is still booting but after posts about getting OpenCore, i found my BootROM are having strange Dumps.
I'm new in OpenCore and don't want to brick my precious one.
 
Hi @tsialex
Could you PM me for BootROM reconstructing service?
My MP5,1 is still booting but after posts about getting OpenCore, i found my BootROM are having strange Dumps.
I'm new in OpenCore and don't want to brick my precious one.
Sure, PM sent. Since you have been dumping the BootROM image send me the oldest one and then dump again following the instructions. Also, I'm curious to see what you call strange dumps.
 
Sure, PM sent. Since you have been dumping the BootROM image send me the oldest one and then dump again following the instructions. Also, I'm curious to see what you call strange dumps.

@tsialex Please PM me... I would like to use your services to upgrade 2x 5,1's
 
  • Like
Reactions: tsialex
Unfortunately not, MacPro3,1 BootROM is a FWB (TSOP-32pins) flash memory. It's a lot more expensive and difficult to source flash memory and a lot more complicated to de-solder/solder.

Programming also require a real flash memory programmer, like a TL-866II + TSOP adapter.



Never saw a MacPro3,1 bricked because flash memory failure, so, I doubt it. The FWB flash memory was the best flash memory for the technology of the time, while MacPro4,1/5,1 moved to a first generation SPI flash memory that didn't stood the passage of the time.



No, it's right below the AirPort Extreme/BT module.



Yes, there is also a small SPI nearby for the NVRAM.
Well I dumped my 3,1 bootrom and it had approx 34000 free space with several 'invalid' entries after booting mojave without opencore. I did a 4x pram reset and dumped again and now showing 64000 free with one or two invalid entries so I am assuming garbage collection is working.

Saved that one for backup ;)

To confirm, 3,1 bootrom only has one vss storage area, correct?
 
Yes, thats correct.

In my opinion it is not so prone for corruption, there was no crossflashing as the 4.1 to 5.1-conversions. But anyway: You can still brick the machine.
 
  • Like
Reactions: freqrider
I did a 4x pram reset and dumped again and now showing 64000 free
If you implement Emulated NVRAM via OpenCore, it will basically freeze your NVRAM in that state as Hardware NVRAM Read/Write would effectively stop and instead go into RAM and/or Hard Disk. Only active when booting via OpenCore for now but sure you can imagine the benefit in terms of otherwise unavoidable NVRAM wear and tear. Also mitigates against the large, potential bricking, NVRAM hit that happens when running updates.

You can read up on how to implement this in the OpenCore Manual for a DIY setup.
MyBootMgr has an option to set this up if using that.
 
  • Like
Reactions: freqrider and JedNZ
uefitool.jpg


@tsialex:
Do you know something of the meaning of the marked entries tsth, tsty, tstc?
 
MacPro3,1 BootROM is a FWB (TSOP-32pins) flash memory. It's a lot more expensive and difficult to source flash memory and a lot more complicated to de-solder/solder.

Yes, there is also a small SPI nearby for the NVRAM.

I have been wondering where the Mac Pro 3,1 stores the firmware for the Intel Management Engine (if it exists at all.) I suspected it might be on a separate SPI flash chip, but could not find one from low-res photos of the logic board.
 
I have been wondering where the Mac Pro 3,1 stores the firmware for the Intel Management Engine (if it exists at all.) I suspected it might be on a separate SPI flash chip, but could not find one from low-res photos of the logic board.
No Intel ME with Mac Pros 3,1/4,1/5,1.
 
Hello,

I'm new to the forum. I'm trying to figure out couple things. Is it possible to refresh the BootRom 144.0.0.0.0? Is it possible to downgrade and upgrade again?
 
Hello,

I'm new to the forum. I'm trying to figure out couple things. Is it possible to refresh the BootRom 144.0.0.0.0? Is it possible to downgrade and upgrade again?
Apple firmware tools only allow upgrades, so the answer is no, but with a reconstructed BootROM image I also send the intermediate files that you can reconstruct yourself any previous EFI version and flash.
 
Apple firmware tools only allow upgrades, so the answer is no, but with a reconstructed BootROM image I also send the intermediate files that you can reconstruct yourself any previous EFI version and flash.
What about Pigsyn’s MacProFirwareToolUpgrade? It has option to downgrade, but to 2009. Which probably will be to far since I have 6-core processors. Is it correct? Can you provide me more details about your service?
 
What about Pigsyn’s MacProFirwareToolUpgrade?

It's just a patch for MacEFIRom's Mac Pro 2009-2010 Firmware Tool, he just changed to the current Apple URLs.

It has option to downgrade, but to 2009.

AFAIK, the only way to downgrade via MacEFIROM's tool is when your BootROM have EFI MP51.007F.B03 installed, anything else fails.

Which probably will be to far since I have 6-core processors. Is it correct?

Westmere Xeons are not supported with MP4,1 EFI releases, so you won't have a working Mac Pro after downgrading.

Can you provide me more details about your service?

Sure, I'll send a PM.
 
Last edited:
What about Pigsyn’s MacProFirwareToolUpgrade? It has option to downgrade, but to 2009. Which probably will be to far since I have 6-core processors. Is it correct? Can you provide me more details about your service?

Completely useless, but I just confirmed that you can only downgrade back to a MP4,1 EFI if your BootROM is MP51.007F.B03.

Had to reconstruct MP51.007F.B03 with my test Mac Pro intermediate files and downgrade from 144.0.0.0.0 to the reconstructed MP51.007F.B03 image to finally be able to run MacEFIROM's tool downgrade procedure successfully.
 

Attachments

  • IMG_0388.JPG
    IMG_0388.JPG
    410.2 KB · Views: 89
  • Screen Shot 2023-01-08 at 04.47.32.png
    Screen Shot 2023-01-08 at 04.47.32.png
    103.1 KB · Views: 95
  • Like
Reactions: JedNZ
Hi Tsialex, I just dumped the bootrom on both of my flashed 4,1s and one of them is showing some serious signs of corruption. Can you PM me about your reconstruction services?
 
Hi Tsialex, I have a 4,1 Mac Pro flashed to 5,1 by previous owner. I upgraded from El Capitan to Mojave, changing the GPU to a metal one on High Sierra and now the cMP is at 144.0.0.0.0 boot ROM. I dumped system ROM with ROMTool and looked at content with UEFITool : VSS store 1 free space is at 32761, VSS store 2 is nowhere to be found and there are too many Invalid entries for my taste. It is better after a sudo nvram ResetNVRam=1 ( free space is 33889, second VSS store is there), but before I go further towards Big Sur or Monterey, I think it would be wise to reconstruct my bootrom.

This is a 2 x 3.46 GHz machine with 128 GB (8 x 16 GB) of ram.

In short, can you PM me about your reconstruction services ?
 
Hi Tsialex, I have a 4,1 Mac Pro flashed to 5,1 by previous owner. I upgraded from El Capitan to Mojave, changing the GPU to a metal one on High Sierra and now the cMP is at 144.0.0.0.0 boot ROM. I dumped system ROM with ROMTool and looked at content with UEFITool : VSS store 1 free space is at 32761, VSS store 2 is nowhere to be found and there are too many Invalid entries for my taste. It is better after a sudo nvram ResetNVRam=1 ( free space is 33889, second VSS store is there), but before I go further towards Big Sur or Monterey, I think it would be wise to reconstruct my bootrom.

This is a 2 x 3.46 GHz machine with 128 GB (8 x 16 GB) of ram.

In short, can you PM me about your reconstruction services ?
Invalid entries are the superseded entries marked for reclamation, so you always have some even after a ResetNVRam, your real problem is the cross-flashing process. PM sent.
 
  • Like
Reactions: marcpa
If you implement Emulated NVRAM via OpenCore, it will basically freeze your NVRAM in that state as Hardware NVRAM Read/Write would effectively stop and instead go into RAM and/or Hard Disk. Only active when booting via OpenCore for now but sure you can imagine the benefit in terms of otherwise unavoidable NVRAM wear and tear. Also mitigates against the large, potential bricking, NVRAM hit that happens when running updates.

You can read up on how to implement this in the OpenCore Manual for a DIY setup.
MyBootMgr has an option to set this up if using that.
I have write flash and update nvram set to false. Is this what you are teferring to or is there another setting?
 
Hey guys, hope you are all doing well. I wanted to ask if I can use Opencore bootloader to freeze my NVRAM so it doesn't get corrupted, but I want to use Mojave still, I don't want to use newer OS? Thanks.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.