Contribute
Register

MacOS stuck on Apple Logo, then restarts - Big Sur Laptop Hackintosh

@Night,

Okay, as the resident 10th gen guy I've had a look at your Comet Lake laptop build. It seems in addition to missing kexts you have a number of errors in your config.

Screenshot 2023-06-25 at 7.34.14 PM.png


I see you've forgotten to add essential kexts and ACPIs such as USBInjectAll, SMCBatteryManager & SMCLightSensor.kext to name a few. VoodooPS2Controller drivers for the mouse and keyboard do also require the VoodooI2CHID & VoodooI2C drivers to work properly in conjunction. The Intel WiFi and Bluetooth has been enabled via the Airportitlwm (Big Sur version) and IntelBluetooth kexts.

I've also removed some of the efi drivers which are conflicting and irrelevant to the base functions of the system. Your most important drivers are OpenRuntime.efi, OpenCanopy.efi & OpenHFSPlus.efi. I've also reordered the kexts into their expected positions, and disabled the Nvidia MX250 using -wegnoegpu in the boot-arg.
The SMBIOS has also been changed to MacbookPro16,2 which is an i7 Comet Lake chipset (correct for your setup).
Give it a try.
 

Attachments

  • EFI.zip
    25.8 MB · Views: 30
@Night,

Okay, as the resident 10th gen guy I've had a look at your Comet Lake laptop build. It seems in addition to missing kexts you have a number of errors in your config.

View attachment 568270

I see you've forgotten to add essential kexts and ACPIs such as USBInjectAll, SMCBatteryManager & SMCLightSensor.kext to name a few. VoodooPS2Controller drivers for the mouse and keyboard do also require the VoodooI2CHID & VoodooI2C drivers to work properly in conjunction. The Intel WiFi and Bluetooth has been enabled via the Airportitlwm (Big Sur version) and IntelBluetooth kexts.

I've also removed some of the efi drivers which are conflicting and irrelevant to the base functions of the system. Your most important drivers are OpenRuntime.efi, OpenCanopy.efi & OpenHFSPlus.efi. I've also reordered the kexts into their expected positions, and disabled the Nvidia MX250 using -wegnoegpu in the boot-arg.
The SMBIOS has also been changed to MacbookPro16,2 which is an i7 Comet Lake chipset (correct for your setup).
Give it a try.
I did not expect anyone to do such a kind thing, thank you very much, kind user!
 
@Middleman Unfortunately, the system still kernel panics at around the same time, and now my laptop keyboard doesn't work during the opencore efi stage. I booted from an external usb using the old efi folder I had, and i booted to the drive where I had your efi folder, and it still kernel panics. I'll try and boot using verbose mode, but it still auto-restarts on kernel panic. I've tried the tried and tested method, but my .plist file already has the debug=0x100 arguments, and it still auto-reboots! If it's not too much to ask, could you check what I'm doing wrong?

-Night
 
@Middleman Unfortunately, the system still kernel panics at around the same time, and now my laptop keyboard doesn't work during the opencore efi stage. I booted from an external usb using the old efi folder I had, and i booted to the drive where I had your efi folder, and it still kernel panics. I'll try and boot using verbose mode, but it still auto-restarts on kernel panic. I've tried the tried and tested method, but my .plist file already has the debug=0x100 arguments, and it still auto-reboots! If it's not too much to ask, could you check what I'm doing wrong?

-Night
Right. It might be remnants of your previous EFI you have to clear. So what you need to do is run the ResetNVRAM tool first - just highlight it and press Enter. If you don't see the tools menu, press space bar for it to appear. What ResetNVRAM will do is clear the cache of the bootloader, and once it is cleared you then reboot the new EFI and then run your OS selection.

If there are still issues, you may have to disable some of the kexts or ACPI files such as SSDT-UIAC and/or SSDT-RHUB. I know also that the XHCIPortlimit quirk need sto be enabled for Big Sur when used in conjunction with the USBInjectall.kext. Technically you do need a customised USB map kext file as you are relying on a generic USBInjectall kext. Check out Corpnewt's USBMap tool on Github or the USBToolbox tool (which can allow you to create a USB map kext from Windows).
 
As I have said, my laptop keyboard doesn't work. Is there any way I can fix that? @Middleman ? Also tyvm for the quick response.
 
As I have said, my laptop keyboard doesn't work. Is there any way I can fix that? @Middleman ? Also tyvm for the quick response.
as in your keyboard doesn't work at all, ie in windows? or just at the opencore picker menu?
 
as in your keyboard doesn't work at all, ie in windows? or just at the opencore picker menu?
Just in the opencore picker menu. I cannot pick in any option other than windows, and i cannot boot into verbose mode if I use an external USB to boot
 
Just in the opencore picker menu. I cannot pick in any option other than windows, and i cannot boot into verbose mode if I use an external USB to boot
verbose is already enabled in the config.plist

try a usb keyboard

also VoodooI2C should be setup for your own machine after you have setup macOS (as well as UIAC.aml)

again.. still no need for all those enabled Drivers

try disabling:
NvmExpressDxe.efi
OpenUsbKbDxe.efi
XhciDxe.efi
 
verbose is already enabled in the config.plist

try a usb keyboard

also VoodooI2C should be setup for your own machine after you have setup macOS (as well as UIAC.aml)

again.. still no need for all those enabled Drivers

try disabling:
NvmExpressDxe.efi
OpenUsbKbDxe.efi
XhciDxe.efi
@Feartech Even though verbose is already enabled, it boots to an apple logo! I really don't know what I'm doing wrong! I'll try with a USB keyboard, and I'll let you know in a few minutes
 
Back
Top