Your machine has a hardware problem, not every issue is bootrom related.
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 Guide: How to rebuild/update Mac Pro 4.1/5.1 bootrom with template files
- Thread starter Borowski
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
anyway thanks for your work and instructive it can be useful in some other occasion
Strange, but i can't see any argument why a formatted, empty nvram-area may cause unexpected shutdowns. That makes no sense at all.
Your backup is already reconstructed image? Did you also try the template(s) in first posting?
yes my image is rebuilt I tried with both file models I corrected the vss manually in the first case since I know how to do it I have already done it with my mac pro 5.1 mid 2010 with success without problems with the autostart your guide made me intrigued on how to validate cr32 and how to transfer sensitive data from one rom to another
In UEFITool NE A72 the developers added a hash-calculation of volumes/parts/sections: https://github.com/LongSoft/UEFITool/releases/tag/A72
This is helpful to calculate and edit the ZeroVector in the last volume directly in hexeditor instead inserting data to "Section_Raw_Volume_Top_File_Volume_Top_File.sct" and exchanging with UEFITool 0.28. All previous steps remain the same.
Anyway, the initial guide in the starting post is still valid and will work: Both methods will generate byte-identical rebuilds.
Read here (post #2): https://forums.macrumors.com/thread...te-files.2437082/?post=33417224#post-33417224
(For usage with older Windows operation systems, choose the win32-version).
This is helpful to calculate and edit the ZeroVector in the last volume directly in hexeditor instead inserting data to "Section_Raw_Volume_Top_File_Volume_Top_File.sct" and exchanging with UEFITool 0.28. All previous steps remain the same.
Anyway, the initial guide in the starting post is still valid and will work: Both methods will generate byte-identical rebuilds.
Read here (post #2): https://forums.macrumors.com/thread...te-files.2437082/?post=33417224#post-33417224
(For usage with older Windows operation systems, choose the win32-version).
@Borowski
I'm at correcting the checksums and in the Fsys- it accepts the suggested value no problem but in the Gaid- It will not accept the suggested value and keeps giving another suggested value I have tried like 5 times and I keep getting invalid.
973D32E1<>E1323D97 then it says
CRC32: BDBE5897h, invalid, should be BA186E26h
I'm at correcting the checksums and in the Fsys- it accepts the suggested value no problem but in the Gaid- It will not accept the suggested value and keeps giving another suggested value I have tried like 5 times and I keep getting invalid.
973D32E1<>E1323D97 then it says
CRC32: BDBE5897h, invalid, should be BA186E26h
Attachments
Last edited:
You inserted some parts at wrong positions or did insert (partly) instead of overwriting bytes:
- Offset 0x14a000h should begin with ff, but your screenshot shows 58 be bd
- UEFITool screenshots show wrong values for Base (Gaid), offset (Gaid), header address (Fsys), data address (Fsys).
