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?
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
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).