Without this EFI partition, the Mac would not boot any more. Recently, a friend got his EFI boot partition overwritten, whereas his main Mac boot partition had remained intact. I wonder if it still may contain additional support for Macs whose boot ROMs can't be updated, such as adding support to boot from APFS volumes, perhaps. Meaning there's no need to create a bootoable EFI partition at all. This suggests that neiter files need to be present at boot time at all, at least on recent Macs. This resulted in a new EFI folder being created in the EFI partition with the same Firmware.scap file. I also did a test where I renamed the top 'EFI' folder to 'EFI-OFF' and rebooted a MacBook Air 2015.

So, if the particular Mac had already installed the particular file into its Flash ROM once, it won't be needed any more and can be removed from the EFI partition. This answer suggests that the files in the FIRMWARE folder are not loaded when booting the system but are rather just used to flash the ROM.

Is EfiUpdaterApp2.efi needed to run the firmware, or is that only a leftover from an older firmware update process and can be removed?Ĭan I create a universal EFI boot partition, containing the firmware for any Mac model, so that I can put that onto an external disk and boot practically any Mac from it for which I've included its. fd file (which may be optional) then goes into the FIRMWARE folder? scap file matching the Mac model and rename that to Firmware.scap, whereas a model-matching. Which files do I take from the macOS Installer, and where do I place them in the EFI volume? E.g, do I use the. The EFI partition requires particular values in the GPT.Īn EFI partition is a FAT32 volume with a folder structure like this: EFI How does one create a working EFI partition from those? called EFIPayloads) with EFI firmware files named MP61_0116_B17_LOCKED.scap, MBP114_0172_B09_LOCKED.fd or similarly. Any macOS installer contains a folder (e.g.

Efi system partion for mac with frisk