![]() Seems you didn't understood, the BootROM reconstruction process is exactly to repair the mess and the final result is identical of the MacPro mid-2012 release 0x0d made in late 2013 right before the production moved to MacPro6,1, except that the original System Serial Number and other hardware identifications (HWC/SON/MLB/BD) are kept as saved from the factory. I excitedly swapped the board that evening. I picked up a used backplane and while I was there, grabbed a second optical drive for fun. I found a local guy who does a great job recycling Apple stuff. Hopefully, this helps someone else who sees all the lights come on at once instead of as each check is passed like they are supposed to. Now, they come on one by one after the tone. So just because EFI Done and GPU OK are lit, does not necessarily mean that. Now that the system is working, they work their way to the on state. When I had a non-working state, all the lights were on at the same time immediately after power up. Perhaps the most important thing I have now noticed is exactly how the firmware status lights work. Use spray isopropyl alcohol and compressed air to really get between pins and under chips. It finished the updates it was doing when the machine died, which worried me for a second before I remembered that. I put in my OpenCore Monterrey disk and all is well. Now I have my serial number back and can use iCloud, etc. So I used ROMTool to burn the image of the chip I removed to the new chip. This board is the one I put a new chip on with MP51.fd burned using a programmer. I tested a few things, dumped that ROM just in case, and then put the original one back in. Booted right away with the second mainboard. ![]() I blew off the remaining IPA with air.īoom, back in business. I had a can of compressed IPA and cleaned and brushed the front of the tray well, focusing on the chip's pins. Given the rest of the board was so clean, I had missed this earlier. It looked like there was enough crud that some of the pins could be shorted. There is a large chip on that edge that is mostly under the cpu cooler. While examining the tray, I noticed some slight corrosion and a thin layer of dust that had seen a light layer of condensation at some point on the machine front side of the board. I haven't had this machine long, nor used it much yet, and the inside of this one was really quite clean so I had not super scrutinized each board. If I had hosed two backplanes, I wasn't about to wreck a third without proving my tray was OK. I decided to take a close look at the cpu tray, since that was the only common thing at that point. I decided that it must not be backplane related. Unplugged and waited a day and a half, same thing. I unplugged everything and tried again in the morning. The machine now would not boot, with the same behavior I had with the original backplane. That boot was about 10% of the Mojave bar and then stopped. I turned on the machine and after a few seconds got the tone and thought I was home free. It's also beneficial to those who wish to learn and practice handling this type of tool.Click to expand.Well, I have my machine working again. What's more, you'll be able to export any of your work quickly after you're finished. You'll have a basic user interface that easy to understand and navigate, making your job a lot easier. Easily change your UEFI firmwareįor those who find making UEFI changes tiresome and somewhat complicated, UEFITool will serve as an excellent solution for you. If you wish to seek other developers' feedback on the changes, you may also share it publicly. After you have the necessary changes, you have the option to either save your BIOS images and UEFI firmware settings to your Windows device or an external USB drive as the last step. Images, such as BIN, BIO, ROM, CAP, WPH, FD, and EFI are some of the image types you can experiment with using this tool.Īs long as you know what you're doing, you can add and delete components as you see appropriate. UEFITool displays the data in an easy-to-read manner. Of course, before you can make any changes, you'll need to comprehend what you're looking at. The user-friendly UEFITool interface is the first component that makes UEFI-changing simple for you.Įverything is well laid out in windows where you can get all of the information you need to get you started. You'll just import files as images and make changes before exporting them again. The goal of UEFITool is to make the process easier by providing the best techniques for interpreting and changing settings without causing any harm. Working with BIOS settings may be challenging, especially if you're not familiar with the procedure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |