[Solved] Apple Logo boot loop after MultiBeast updates

[Nyak]

Thanks. Have attached a zip with some files to merge into your (real) EFI folder. Copy them into their corresponding locations.

What they are:

/efi/clover/kexts/other/ - FakeSMC and Ethernet kexts (needed when not present in cache e.g. Recovery Boot)

/efi/clover/config-safeboot.plist - Alternate configuration for safe boot, no unsigned kexts, no caches, inject always
/efi/clover/config-sip-enabled.plist - Alternate configuration for normal boot, no unsigned kexts, no caches, inject always
/efi/clover/config.plist - Your previous configuration with few changes (Drop DMAR, debug=0x100, detect fakeSMC for kext injection)

1. You should be able to boot into recovery with the default config.plist
2. You might be able to boot into safe boot with config-safeboot.plist but that would be too easy wouldn't it...

Hit 'o' for options at clover boot menu, see 'configurations'

Okay so I made it into Recovery with the default config file. Safe boot didn't work. What do I do now?

 

[vulgo]

Try and remove the kernel extensions you installed in /System/Library/Extensions through Multibeast:

In recovery open up the terminal app. Identify your macOS system partition

$ diskutil list

Example output:
AppleHFS Macintosh HD disk0s2

Now see if it is mounted

$ mount | grep /dev/disk0s2

Replacing /dev/disk0s2 with the real identifier from above. If you get no output, you need to mount the disk

$ diskutil mount /dev/disk0s2

Then again

$ mount | grep /dev/disk0s2

Example output showing the mount point:
/dev/disk0s2 on /Volumes/Macintosh HD (hfs, local, journaled)

Change working directory

$ cd /volumes/macintosh\ hd/system/library/extensions

Escaping any spaces in the path with backslashes

List directory contents, last modified last

$ ls -trla

Identify the kexts you installed/updated that might be preventing boot.

Become root (if necessary in installer environment?)

$ sudo su

To remove a kext: rm -R ./TheNameOfTheKext.kext

# rm -R ./AnotherKext.kext

When you are ready to try booting

# touch /system/library/extensions

And finally

# reboot now

 

[Nyak]

Try and remove the kernel extensions you installed in /System/Library/Extensions through Multibeast:

In recovery open up the terminal app. Identify your macOS system partition

$ diskutil list

Example output:
AppleHFS Macintosh HD disk0s2

Now see if it is mounted

$ mount | grep /dev/disk0s2

Replacing /dev/disk0s2 with the real identifier from above. If you get no output, you need to mount the disk

$ diskutil mount /dev/disk0s2

Then again

$ mount | grep /dev/disk0s2

Example output showing the mount point:
/dev/disk0s2 on /Volumes/Macintosh HD (hfs, local, journaled)

Change working directory

$ cd /volumes/macintosh\ hd/system/library/extensions

Escaping any spaces in the path with backslashes

List directory contents, last modified last

$ ls -trla

Identify the kexts you installed/updated that might be preventing boot.

Become root (if necessary in installer environment?)

$ sudo su

To remove a kext: rm -R ./TheNameOfTheKext.kext

# rm -R ./AnotherKext.kext

When you are ready to try booting

# touch /system/library/extensions

And finally

# reboot now

Okay so I listed the contents of the extensions folder, how do I figure out which kext is causing the problem?

 

[vulgo]

Okay so I listed the contents of the extensions folder, how do I figure out which kext is causing the problem?

Whatever you installed through Multibeast is safe to remove, including FakeSMC. Note what you delete if there are many extensions.

 

[Nyak]

Whatever you installed through Multibeast is safe to remove, including FakeSMC. Note what you delete if there are many extensions.

I removed the evOreboot.kext file and it works! Thank you so much for your patience and help.

Cheers!