Contribute
Register

[Solved] Near-instantaneous reboot after boot

Joined
Aug 30, 2015
Messages
10
Motherboard
Gigabyte GA-Z170X-UD3
CPU
Core i7 6700K / 4GHz
Graphics
Onboard or Gigabyte GTX-1080
I did something to my hackintosh to kill it deader than dead. I wish I could tell you exactly what, but I can't. I was trying to solve a "no audio after wake" issue, and I thought I had rebooted after whatever I had done most recently ... but maybe not. When I reboot now, the machine reboots *instantly* back to the boot loader -- it takes about one second from choosing the boot partition to rebooting. I grabbed a video and the last frame is attached.

crash-at-boot.jpg


What I've done to try to fix this:

I was able to boot into single user mode using the Clover USB stick, so I mounted the internal hard drive, and found that AppleIntelInfo.kext was in /S/L/E, so I removed it. But on reboot, I get the same error ... how is that possible?

I can't boot into Safe mode, and even more disconcerting, my cloned backup won't boot either, though it did so this weekend.

Can anyone recommend any other fixes to try before I nuke the thing and start all over?

thanks!
 
Joined
Feb 13, 2012
Messages
1,515
Motherboard
Gigabyte Z370M D3H
CPU
i3-8350K
Graphics
RX 560
Mac
iMac, Mac mini
Classic Mac
eMac, iBook
Mobile Phone
iOS
I did something to my hackintosh to kill it deader than dead. I wish I could tell you exactly what, but I can't. I was trying to solve a "no audio after wake" issue, and I thought I had rebooted after whatever I had done most recently ... but maybe not. When I reboot now, the machine reboots *instantly* back to the boot loader -- it takes about one second from choosing the boot partition to rebooting. I grabbed a video and the last frame is attached.

View attachment 250551

What I've done to try to fix this:

I was able to boot into single user mode using the Clover USB stick, so I mounted the internal hard drive, and found that AppleIntelInfo.kext was in /S/L/E, so I removed it. But on reboot, I get the same error ... how is that possible?

I can't boot into Safe mode, and even more disconcerting, my cloned backup won't boot either, though it did so this weekend.

Can anyone recommend any other fixes to try before I nuke the thing and start all over?

thanks!
Hi there :)

First thing I'd do, since you can boot the UniBeast stick okay - (you've probably gone this route before because I guess you've used Bash to remove that kext, but ...) - is choose External (i.e the UniBeast stick) as the boot drive from the Clover screen. Once the Installer comes up don't go any further but go to the Tools menu and select DiskUtil, then use it to check the disk IDs for your normal boot drive and your UniBeast stick. Write them down and exit DiskUtil. Then choose Terminal and use that to mount the EFI partitions of your both drives, keeping careful watch on which is which.

Then check the EFI/CLOVER/kexts/Other folders and see what is in each. Your choice what to do here - I would probably remove/move any un-needed kexts on the failing drive for now. I'd then rename the drive's config.plist to config.old or similar and then copy the UniBeast one into its place. And see if the system would boot again.

If not, more of the same, checking what's in each EFI main-drive folder etc, replacing and changing until a boot happens either with the UniBeast stick or on it's own.

As you say, that or rebuild from scratch. :rolleyes:
 
Joined
Aug 30, 2015
Messages
10
Motherboard
Gigabyte GA-Z170X-UD3
CPU
Core i7 6700K / 4GHz
Graphics
Onboard or Gigabyte GTX-1080
Hi there :)

Then check the EFI/CLOVER/kexts/Other folders and see what is in each.
Oh jeez - thanks! I had totally forgotten that kexts could live there, too. Found and disabled two, and the machine rebooted. Yes!!

Thanks again; that saved a few hours of aggravation!
 
Joined
Feb 13, 2012
Messages
1,515
Motherboard
Gigabyte Z370M D3H
CPU
i3-8350K
Graphics
RX 560
Mac
iMac, Mac mini
Classic Mac
eMac, iBook
Mobile Phone
iOS
Oh jeez - thanks! I had totally forgotten that kexts could live there, too. Found and disabled two, and the machine rebooted. Yes!!

Thanks again; that saved a few hours of aggravation!
Good news! :)

Glad you got it sorted.
 
Top