- Joined
- Mar 2, 2011
- Messages
- 316
- Motherboard
- GA-Z97X-Gaming 7
- CPU
- i7-4790K
- Graphics
- RX 580
- Mobile Phone
Imagine how confused I am mate. I get thrown different EFI, try this that so I try to keep up.To be honest I am a bit confused by the whole thing? As you've somehow gone back to square one?
If you've updated the EFI properly there's no reason why it should start blinking. Blinking usually means something in the bootloader is off - either the BootX64.efi, Opencore.efi etc is wrong or a driver is missing (like OpenShell.efi or OpenHFSPlus.efi). OR the config.plist is somehow corrupted. On all of the bootloader builds you have to ensure ALL the relevant files for the version involved to have to be updated to the same release date, which includes the usual OC kexts - Lilu, Whatevergreen, AppleALC, & VirtualSMC.
The best way to update the older EFI file is to copy that to another USB stick or drive, and then update it using manual methods or Opencore Configurator or similar like Hackintool. Personally I prefer Opencore Configurator - you just load up the old file using the latest version and simply re-save, add in your OC updates manually into the relevant folders and it is mostly done.
There is OCAT (Opencore Auxiliary Tool) but I would avoid using OCAT for now as I noticed it doesn't always update the kext files correctly even though its been specified by the user. Better to do a manual check of the folders to ensure the kexts have been updated.
Edhawk EFI gave blinking cursor but was 0.8.3 so more recent. I noticed it had a lot of dsdt patches that I used before with clover. I tried my system without them and it still ran ok so I went minimal in clover, only required kexts, drivers and proper config, no dsdt patches Or extra kexts.
Now the one you recommended works but is 0.6.5 or something. OpenCore Configurator even throws an error about the old version. Going trough with it might render the config file useless.