OS X Installer Boot Fail - Error loading kernel cache

[DakotaSamuel]

Thank you for the reply. I will try your first two suggestions later tonight.
I haven't wiped my HDD clean because I am trying to triple boot my laptop (Windows, Ubuntu, MacOS). Do you think the mess on the hard drive is causing problems?
I do have a spare copy of Windows, so I could start fresh and reinstall Windows and Ubuntu after wiping clean and installing MacOS if that would help.

 

[RehabMan]

Thank you for the reply. I will try your first two suggestions later tonight.

Good plan.

I haven't wiped my HDD clean because I am trying to triple boot my laptop (Windows, Ubuntu, MacOS). Do you think the mess on the hard drive is causing problems?

It might, but those problems will typically happen later in the process.

I do have a spare copy of Windows,

Of course.... Windows 10 can be easily downloaded with Microsoft provided software.

so I could start fresh and reinstall Windows and Ubuntu after wiping clean and installing MacOS if that would help.

If you have a second HDD you can install, maybe put your existing one aside while you experiment with macOS.

 

[DakotaSamuel]

I swapped in a spare hard drive and wiped it, so I will use that now. The USB drive I am using is 8GB usb2.0.

I tried the installer with OsxAptioFixDrv-64.efi on all USB ports. Sadly no changes from earlier (End RandomSeed, then plus signs).

I then tried all USB ports with AptioMemoryFix.efi instead of OsxAptioFixDrv-64.efi. This gave the kernel cache error again. PR files attached.

I assume that since using OsxAptioFixDrv-64.efi gets farther it is the correct one to use?

 

[RehabMan]

I swapped in a spare hard drive and wiped it, so I will use that now. The USB drive I am using is 8GB usb2.0.

I tried the installer with OsxAptioFixDrv-64.efi on all USB ports. Sadly no changes from earlier (End RandomSeed, then plus signs).

I then tried all USB ports with AptioMemoryFix.efi instead of OsxAptioFixDrv-64.efi. This gave the kernel cache error again. PR files attached.

I assume that since using OsxAptioFixDrv-64.efi gets farther it is the correct one to use?

You can also try OsxAptioFix2Drv-64.efi as well as Clover legacy (use sourceforge Clover legacy boot files).

 

[DakotaSamuel]

OsxAptioFix2Drv-64.efi: Gave me kernel cache error on all usb ports.

Clover legacy: Used the sourceforge Clover EFI bootloader (v2.4k r4630). Some of the settings were a little different then those on your guide, so I am not sure if they were correct.
When I booted into Clover, there were no boot options. I read that this could be caused by missing HFSPlus.efi so I added it to drivers64UEFI and the "macOS install" option appeared. That doesn't make any sense though since (from the guide):

Note: For Clover legacy, HFSPlus.efi is built-in (Clover legacy loads no drivers from drivers64UEFI anyway)

Does this mean I messed up when creating the USB and it is not using Clover legacy? I attached a screenshot of the installer settings.

 

[RehabMan]

OsxAptioFix2Drv-64.efi: Gave me kernel cache error on all usb ports.

Clover legacy: Used the sourceforge Clover EFI bootloader (v2.4k r4630). Some of the settings were a little different then those on your guide, so I am not sure if they were correct.
When I booted into Clover, there were no boot options. I read that this could be caused by missing HFSPlus.efi so I added it to drivers64UEFI and the "macOS install" option appeared. That doesn't make any sense though since (from the guide):


Does this mean I messed up when creating the USB and it is not using Clover legacy? I attached a screenshot of the installer settings.

drivers64UEFI is not used when using Clover legacy.
If adding things there makes a difference, you're not booting legacy (but instead are booting UEFI).
You can also tell by looking at misc/preboot.log.

 

[DakotaSamuel]

Yes. Probably a dumb question, but why is it not booting legacy? I don't see any legacy/uefi boot mode options in my bios and I followed the instructions in the guide for legacy (MBR and used the legacy settings).
Should I have not used the Sourceforge Clover EFI bootloader?

 

[RehabMan]

Yes. Probably a dumb question, but why is it not booting legacy? I don't see any legacy/uefi boot mode options in my bios and I followed the instructions in the guide for legacy (MBR and used the legacy settings).
Should I have not used the Sourceforge Clover EFI bootloader?

You will need to examine your BIOS options to see if there is a way to set UEFI boot disabled, or a way to set legacy boot as priority.

 

[DakotaSamuel]

You will need to examine your BIOS options to see if there is a way to set UEFI boot disabled, or a way to set legacy boot as priority.

There doesn't seem to be any way of doing that in my bios. I have secure boot disabled, and CSM enabled. There is no "Boot Mode" option or anything else relating to legacy boot that I can see.
I am attaching screenshots so maybe you could glance at my bios settings?

 

[RehabMan]

There doesn't seem to be any way of doing that in my bios. I have secure boot disabled, and CSM enabled. There is no "Boot Mode" option or anything else relating to legacy boot that I can see.
I am attaching screenshots so maybe you could glance at my bios settings?

If your BIOS provides no method for setting legacy boot as priority, you will not be able to boot legacy.
Because with a legacy Clover setup, both legacy and UEFI remain possibilities.

Unless you are successful removing all UEFI entries (use efibootmgr in Linux).