<< Solved >> Won't boot after EFI restore (1070, i7-6700K, z170x G7)

Hi,

The other day I FINALLY got my rig (running Sierra) to work with my new Phoenix Gainward 1070 graphics card, and it has been running smoothly since that - except it wouldn't stay shut down. I was fiddling with clover settings to make that work, but gave up after a while, and now I am only able to boot system from the boot disk I made following this guide. I have tried restoring EFI (by deleting the old EFI folder and copying from my system's EFI-Backups folder), but it just reboots after Apple logo. I'm not entirely sure if I should use the EFI backup made days ago, or the first one today (before enabling FixShutdown)?

I have enabled CSM in BIOS since I'm running a Display Port monitor and a HDMI monitor simultaneously (I've disconnected the DP one for troubleshooting purposes, though), and am using the profile "Other OS". Else I think I followed the guide pretty precisely. I've attached a picture of the verbose log and the config.plist, I don't know if anything else is needed?

Thanks for reading!

Bump.

As per forum rules, please update your profile with your CPU, motherboard, and GPU info.

Your config.plist is almost completely blank.

Ok I thought that was what the signature was for, is it correct now?

Ok, as I stated, I'm not entirely sure if I should use the EFI backup made days ago, or the first one on the 17th (before enabling FixShutdown and updated Clover that broke the build)? I have the following EFI backups to choose from:

GerrigMAX said:

Ok I thought that was what the signature was for, is it correct now?

Ok, as I stated, I'm not entirely sure if I should use the EFI backup made days ago, or the first one today (before enabling FixShutdown and updated Clover that broke the build)? I have the following EFI backups to choose from:
View attachment 394462

Click to expand...

Yes. Profile is correct now.

It looks like you updated to Clover r4895 on March 14th. So you should be able to use anything before that or just open up your config.plist and disable FixShutdown.

pastrychef said:

Yes. Profile is correct now.

It looks like you updated to Clover r4895 on March 14th. So you should be able to use anything before that or just open up your config.plist and disable FixShutdown.

Click to expand...

OK that makes sense. But If I copy the backup named "2019-03-14-01h08" to the EFI partition (which doesn't have FixShutdown enabled), it won't boot, and just displays "+++++++++++++++++++++++++++++++" with verbose output.

Config.plist and picture is attached.

I have disconnected my primary monitor (Display Port) for troubleshooting purposes, so that only my HDMI monitor is connected.

I still have CSM enabled in BIOS, with profile "Other OS".

GerrigMAX said:

OK that makes sense. But If I copy the backup named "2019-03-14-01h08" to the EFI partition (which doesn't have FixShutdown enabled), it won't boot, and just displays "+++++++++++++++++++++++++++++++" with verbose output.

Config.plist and picture is attached.

I have disconnected my primary monitor (Display Port) for troubleshooting purposes, so that only my HDMI monitor is connected.

I still have CSM enabled in BIOS, with profile "Other OS".

Click to expand...

Try changing OsxAptioFix2Drv-64.efi to AptioMemoryFix-64.efi in /EFI/CLOVER/drivers64UEFI/.

You can also try with CSM disabled.

pastrychef said:

Try changing OsxAptioFix2Drv-64.efi to AptioMemoryFix-64.efi in /EFI/CLOVER/drivers64UEFI/.

You can also try with CSM disabled.

Click to expand...

You're the best! Booted up beautifully However, OsxAptioFix2Drv-64.efi was not installed to that folder, so I just installed AptioMemoryFix-64.efi without changing anything else - should I try with OsxAptioFix2Drv-64.efi instead/also?

Thank you very much for your help!

GerrigMAX said:

You're the best! Booted up beautifully However, OsxAptioFix2Drv-64.efi was not installed to that folder, so I just installed AptioMemoryFix-64.efi without changing anything else - should I try with OsxAptioFix2Drv-64.efi instead/also?

Thank you very much for your help!

Click to expand...

No, don't bother with OsxAptioFix2Drv-64.efi. AptioMemoryFix-64.efi is much, much better. They can not be used together. It's either/or, never both together.

pastrychef said:

No, don't bother with OsxAptioFix2Drv-64.efi. AptioMemoryFix-64.efi is much, much better. They can not be used together. It's either/or, never both together.

Click to expand...

Ok thanks for clarifying! Not to take advantage of your kindness, but do you happen to know of any other "this driver is better than that" examples in regard to sound production via a thunderbolt sound card? Both in regard to cpu effiency and sound fidelity/latency and such?