#UEFITOOL 0.21.5 SERIAL#
#UEFITOOL 0.21.5 PATCH#
#UEFITOOL 0.21.5 PRO#
#UEFITOOL 0.21.5 CODE#

I downloaded the vanilla BIOS from Asus's website, versions 14 then I used UEFITool () to convert the. I did end up using the Pomona clips (I had ordered a different set of test clips, but what arrived didn't match what was shown on the product page it also was so chunky that I couldn't grab the Winbond chip, because there are some (mysterious) headers next to it that physically prevent the clip from attaching).

#UEFITOOL 0.21.5 CODE#

If you didn't add those identifiers, is it working ok? Maybe they are on protected memory blocks of the original chip and adding the new code from the CAP file doesn't disturb it?

#UEFITOOL 0.21.5 SERIAL#

I am curious to know if you used the Pomona clips to read a known good bios image into a BIN file, then wrote that to the bad chip? Or did you use a file from the downloaded CAP file? The latter would not have the MAC address, UUID and motherboard Serial No, which I understand can be added using the FD44Editor utility. I used an EEPROM programmer to copy the good BIOS image onto a replacement Winbond chip to replace the corrupted one. Hi, and congrats on recovering from a corrupted BIOS chip w/o an RMA! I just did that myself with the dual BIOS R5E.

If anyone is interested, I can put together a guide for resuscitating your BIOS using a BIOS programmer (won't fix non-BIOS problems, but if flashback isn't working, or if you bricked the BIOS, it should work).

I believe that this is the expected behavior for the EX900 due to its nature as a budget NVMe drive.ESATA problem was traced to dead drives. I did some basic disk throughput tests and found that, while the read speeds saturate the two PCIe lanes at 1500Mbps, the write speeds are less consistent, with spikes up to 1230Mbps but typical performance around 300Mbps. Hibernation seems to work properly, and the laptop seems to boot up and wake from sleep just a little faster than before. I wound up just backing up the original drive using Time Machine and then restoring the new drive from that backup, using Apple's GUI tool. The guide linked in the wiki uses dd to backup the whole drive, byte-by-byte, but I was unable to restore this image to my new drive using dd, asr, or Disk Utility. The only other issue I encountered was in moving my files from my old Apple SSD to this new one. Once I downloaded this older version from the GitHub releases page, the patching went perfectly, and I was able to write and verify this new bootrom to my Mac. I used UEFITool to modify this bootrom but found that I needed to use an older version (0.24) in order to be able to modify a bootrom rather than just extract the NVMe driver. I read the bootrom out three times, verifying consistency with the md5sum and diff tools. I tried using the CH341a from macOS but wound up using a Linux laptop when flashrom was unable to find it. View attachment 923212 View attachment 923213 (I later found out that, if I had desoldered the chip, it has the same spacing as the SOIC-8 and would have fit perfectly into the clip.) This meant that I couldn't use an SOIC-8 clip on it, but I was able to solder some 34AWG magnet wire onto the pins and get it recognized by a CH341a. This wound up being a little trickier, since my Mac doesn't have the J6100 connector installed for some reason, and its EFI chip is not an SOIC-8 chip like the 15' models have.

#UEFITOOL 0.21.5 PATCH#

I also opted to patch my bootrom (version 160.0.0.0) so that sleep would work with hibernatemode 25, following the guide in the wiki. Installing the pair went very simply, with the EX900's mounting notch perfectly aligning with the Mac's SSD standoff, as advertised. I'm using a 500GB HP EX900 drive with the short Sintech adapter, which came with tape pre-applied to the NVMe connector.

#UEFITOOL 0.21.5 PRO#

I've been working on upgrading my mid-2014 13' MacBook Pro (MacBookPro11,1) and thought I should share my success.

Uefitool 0.21.5