[Solved] Freezing at Apple Logo after post-install and shutdown after sleep

[pepperoni]

I was able to successfully get through Sierra installation with my hardware and boot into the desktop. However, after running running multibeast setup, and modifying suggested parameters in config post-install I cannot boot. Here's what I've done so far.

• Edited config.plist with to change the Crf value to 0x67, added FakeCPUID of 0x0506E3
• Replaced this driver https://github.com/MegaCookie/Lenov...FI/CLOVER/drivers64UEFI/OsxAptioFixDrv-64.efi
• Installed ALC892 and ethernet using multibeast

Restarting worked just fine and I was able to get into the desktop. Then, the computer went to sleep. I couldn't wake from it, so had to do a hard shut down. Now, I haven't been able to get back into the desktop since not being able to wake from sleep.

Here's two screenshots. Sometimes I get one, sometimes I get the other.

Any idea what I can do to troubleshoot this issue without being able to access the desktop?

 

[TheAquired]

when the pluses appear, is there nothing after them? Normally when the pluses appear, the system starts to actually boot (in my hack).

The error alloc type 2 can be potentially fixed by adding test2.efi to the EFI drivers folder with OSxAptioFixDRV-64 and then updating your bios to the latest version (fixed it for me)

its strange that even when the EFI succesfully starts (the pluses) it freezes after that. Could be an unrelated issue.


I would suggest adding test2.efi to the EFI drivers folder by plugging your drive into another machine and just opening the folder up. See if it helps?

 

[pepperoni]

when the pluses appear, is there nothing after them? Normally when the pluses appear, the system starts to actually boot (in my hack).

Absolutely nothing. Hard drive stops working and it just hangs there.

I would suggest adding test2.efi to the EFI drivers folder by plugging your drive into another machine and just opening the folder up. See if it helps?

Where do I find test2.efi? Can't seem to find it by searching and it's not in Clover Configurator.

 

[AM0207xx]

I was able to successfully get through Sierra installation with my hardware and boot into the desktop. However, after running running multibeast setup, and modifying suggested parameters in config post-install I cannot boot. Here's what I've done so far.

• Edited config.plist with to change the Crf value to 0x67, added FakeCPUID of 0x0506E3
• Replaced this driver https://github.com/MegaCookie/Lenov...FI/CLOVER/drivers64UEFI/OsxAptioFixDrv-64.efi
• Installed ALC892 and ethernet using multibeast

Restarting worked just fine and I was able to get into the desktop. Then, the computer went to sleep. I couldn't wake from it, so had to do a hard shut down. Now, I haven't been able to get back into the desktop since not being able to wake from sleep.

Here's two screenshots. Sometimes I get one, sometimes I get the other.

Any idea what I can do to troubleshoot this issue without being able to access the desktop?

Have you used a Fake CPUID, because KabyLake isn´t natively supported by mac OS at the moment...

 

[pepperoni]

Have you used a Fake CPUID, because KabyLake isn´t natively supported by mac OS at the moment...

Yes, I was able to install successfully with the FakeCPUID. Also able to boot successfully. It wasn't until after installing the multibeast updates that it started failing

 

[AM0207xx]

Yes, I was able to install successfully with the FakeCPUID. Also able to boot successfully. It wasn't until after installing the multibeast updates that it started failing

I don´t know, but maybe it has something to do with your SMBIOS...
Some time ago I got the same error, because I used the wrong SMBIOS.

 

[pepperoni]

Okay. I managed to get everything working now by just wiping everything and starting from scratch. Not sure what weirdness I hit, but things are working now.

 

[Geode1010]

I have the exact MOBO and CPU with the same issue. What did you do to solve it?