Contribute
Register

<< Solved >> Attempting to install Mojave, system freezes after first reboot

Status
Not open for further replies.

nobodynose

Moderator
Joined
Sep 29, 2012
Messages
3,914
Motherboard
ASRock Z370M Pro4
CPU
i7-8700
Graphics
RX 560
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
  4. Mac mini
Classic Mac
  1. iBook
  2. iMac
  3. Quadra
Mobile Phone
  1. Android
  2. iOS
I'm attempting to build my second Mojave system, and the PC consistently freezes/locks up when I attempt to boot to the newly installed SSD (still starting the boot from a Unibeast USB installer). There's no mouse cursor, the progress bar never moves, and the system appears completely unresponsive. I've built about a dozen Hackintoshes over the years, and I've never had as much trouble as I've had with Mojave.

Hardware info listed as "New Mojave installation (currently working on)" in my Build Signature. Attached is my EFI folder (from the Unibeast USB stick) and a photo of the screen where it locks up.

I've tried various combinations of AptioMemoryFix UEFI drivers, etc., but nothing seems to work. I'm really stumped!
 

Attachments

  • EFI.zip
    2.3 MB · Views: 63
  • Mojave_Install_Locked_Up.jpg
    Mojave_Install_Locked_Up.jpg
    524 KB · Views: 62
Previously we would have used XHCI-200-Series_Injector.kext on a Z370 board rather than XHCI-300-Series_Injector.kext but now both have been superseded by XHCI-unsupported.kext - (Click download repository).

Lilu.kext, WhateverGreen.kext, USBInjectAll.kext and even FakeSMC.kext look old and probably should be updated.
 
Last edited:
In addition to the input from P1LGRIM:
  • It seems you're at Stage 2 of installation (see Installation Overview section here for a list of steps).
  • If so, the system will either (a) suddenly reboot within 1 minute of starting Stage 2, or (b) freeze within 1 minute.
  • We can therefore reboot the machine ourselves, boot from USB, and select "Boot macOS Install from Mojave" to continue the installation.
 
In addition to the input from P1LGRIM:
  • It seems you're at Stage 2 of installation (see Installation Overview section here for a list of steps).
  • If so, the system will either (a) suddenly reboot within 1 minute of starting Stage 2, or (b) freeze within 1 minute.
  • We can therefore reboot the machine ourselves, boot from USB, and select "Boot macOS Install from Mojave" to continue the installation.

Actually, this happens right after I reboot from USB and select "Boot macOS Install from Mojave".
 
Previously we would have used XHCI-200-Series_Injector.kext on a Z370 board rather than XHCI-300-Series_Injector.kext but now both have been superseded by XHCI-unsupported.kext - (Click download repository).

Lilu.kext, WhateverGreen.kext, USBInjectAll.kext and even FakeSMC.kext look old and probably should be updated.

I searched everywhere for a download link for XHCI-unsupported.kext, but couldn't find it - thank you! I'll try that along with updating the other ones you mentioned.
 
FWIW, I had a terrible time with freezes/reboots -- including right at the beginning of the progress bar after the first reboot. I think I eventually fixed it by using current versions of Lilu, WhateverGreen, and IntelMausiEthernet, plus changing the SMBIOS and using a working ig-platform-id. In my case I got it to work with Macmini8,1 though iMac18,1 may be fine too. I didn't have luck with the default iMac14,x. I used ig-platform-id 0x3E9B0007 for an i7-8700. That got me DisplayPort output but not HDMI; I didn't troubleshoot HDMI since my monitor supported both. I've ended up with a boot USB very customized to the system in question, but it works.
 
Attached is a modified EFI folder to try. Some of the changes include:
  • slide=0 in Boot arguments. If you encounter Randomseed or Couldn't Allocate Runtime Area error messages, simply remove this argument.
  • Latest versions of Lilu and WhateverGreen.
  • Additional ACPI patches.
No guarantee this will work (since I don't have an Asrock Z370), but it might get you a step closer. I've seen a handful of EFI folders from other 370-based motherboards and they tend to be filled with fairy dust. ;)
 

Attachments

  • EFI-nobodynose.zip
    2.2 MB · Views: 48
Attached is a modified EFI folder to try. Some of the changes include:
  • slide=0 in Boot arguments. If you encounter Randomseed or Couldn't Allocate Runtime Area error messages, simply remove this argument.
  • Latest versions of Lilu and WhateverGreen.
  • Additional ACPI patches.
No guarantee this will work (since I don't have an Asrock Z370), but it might get you a step closer. I've seen a handful of EFI folders from other 370-based motherboards and they tend to be filled with fairy dust. ;)

I already tried slide=0 and updating to the latest versions of those kexts, it didn't help. I'll take a look at the ACPI patches in the EFI folder you attached. For the record, the system I'm currently working on isn't the ASRock Z370, it's a Gigabyte Z370M-DS3H.
 
I already tried slide=0 and updating to the latest versions of those kexts, it didn't help. I'll take a look at the ACPI patches in the EFI folder you attached. For the record, the system I'm currently working on isn't the ASRock Z370, it's a Gigabyte Z370M-DS3H.
Forum member @Djb726 has a similar (not identical) motherboard and has uploaded his EFI folder here. It's a very skeletal config.plist, but it does allow the system to boot. You might want to try that EFI -- but, of course, please change the SMBIOS serial numbers.
 
OK nobodynose, I looked at the original posted EFI dir and I see you're a step ahead of me. Maybe just set inject Intel to true? If that doesn't do it, you could try setting ig-platform-id the old way, which is how I have it in my working build.
 
Status
Not open for further replies.
Back
Top