Contribute
Register

Can't boot after 10.12.3 Update

Status
Not open for further replies.
ben9923

ben9923

Joined
Apr 21, 2016
Messages
1,005
Motherboard
ASUS X556UA-Clover
CPU
i5-6200U
Graphics
HD 520,1366x768
Mobile Phone
  1. iOS
Hi everyone, @RehabMan ,
After every update so far was smooth, without any problem, I felt safer to update right away.
I saw only positive feedback about that update, so I've downloaded the update from the Mac App Store...

When booting, I get a 'No Entry' sign.
I notice a strange thing when booting verbose, didn't see it before.
Tried to boot with my config-backup, and with my DSDT Patch-free DOK, but without success.
The message photo is attached, something about ACPI.
The "Method parse/execution..." message only occurs when I was booting with my DOK (no patched acpi)

I might should say that my AppleIntelLpss...+AppleHPM+Some Others are deleted (Didn't cause any problem in the last updates, but said it anyway..) Beacause of VoodooI2C.

I can still boot to Windows if it matters.
I am using SATA-100-series-unsupported.kext

What can I do?
Thanks!
 

Attachments

  • IMG_9307.JPG
    IMG_9307.JPG
    3 MB · Views: 201
ben9923 said:
Hi everyone, @RehabMan ,
After every update so far was smooth, without any problem, I felt safer to update right away.
I saw only positive feedback about that update, so I've downloaded the update from the Mac App Store...

When booting, I get a 'No Entry' sign.
I notice a strange thing when booting verbose, didn't see it before.
Tried to boot with my config-backup, and with my DSDT Patch-free DOK, but without success.
The message photo is attached, something about ACPI.
The "Method parse/execution..." message only occurs when I was booting with my DOK (no patched acpi)

I might should say that my AppleIntelLpss...+AppleHPM+Some Others are deleted (Didn't cause any problem in the last updates, but said it anyway..) Beacause of VoodooI2C.

I can still boot to Windows if it matters.
I am using SATA-100-series-unsupported.kext

What can I do?
Thanks!
Click to expand...

You updated from what version?

Attach EFI/Clover folder as ZIP (omit 'themes' folder).
 
RehabMan said:
Must provide current files.
Click to expand...
I can't boot the OS so I can't get them :(
There is no difference between the current files to the linked ones. Only that small thing that can't be related, since I tested without it.
 
ben9923 said:
I can't boot the OS so I can't get them :(
There is no difference between the current files to the linked ones. Only that small thing that can't be related, since I tested without it.
Click to expand...

Boot using a USB prepared according to the guide.
Or boot the OS X/macOS installer from USB and collect the files with Terminal.
Or remove the HDD/SSD and connect to working computer.

Unfortunately, it is not possible to provide advice without details on what exactly you're doing.
 
RehabMan said:
Boot using a USB prepared according to the guide.
Or boot the OS X/macOS installer from USB and collect the files with Terminal.
Or remove the HDD/SSD and connect to working computer.

Unfortunately, it is not possible to provide advice without details on what exactly you're doing.
Click to expand...
What kind of details? Tried to boot with safe mode, without injected kexts, it didn't help.
The problem started after the update, system was working well without any problem.

I don't know why it's nescessary, these are exactly the same files. No change except EDID inject. I have a config-backup there which doesn't have the EDID inject, and I tried to boot with it too.

RehabMan said:
Boot using a USB prepared according to the guide.
Click to expand...
I do that. Only change is the MBP2016 SMBIOS. The rest is exactly by the guide.
This is a 10.12.2 USB.
Still the same error while booting, so it's not a config.plist problem...
 

Attachments

  • CLOVER.zip
    2.2 MB · Views: 79
ben9923 said:
Attached CLOVER folder (from Windows), without 'themes' :)

Actually created that USB a week ago ;)
Click to expand...

Your ACPI configuration is wrong.
As per ACPI patching guide, DropOem must be set true when you have patched SSDTs in ACPI/patched.
You have it set false.

Also, you should have only "essential" kexts in EFI/Clover/kexts/Other.
AppleALC.kext is not essential.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top