Contribute
Register

System doesn't boot after installation.

Status
Not open for further replies.
The Config is always deleted When I reopen it. Now it showed this message.
 

Attachments

  • Screen Shot 2018-01-18 at 01.20.06.png
    Screen Shot 2018-01-18 at 01.20.06.png
    44.1 KB · Views: 97
Okay, so now it won't boot anymore. It's stuck here ... Aargh It's nuts. I'ma go to bed for now and continue trying tomorrow.
Thanks so much for now cmd!!
 

Attachments

  • IMG_20180118_013023.jpg
    IMG_20180118_013023.jpg
    5 MB · Views: 81
The Config is always deleted When I reopen it. Now it showed this message.
Click "OK" to dismiss this.
You know you have consciously and willingly editing this config.plist and overwriting old file and replacing with this edited file the previous one that was causing you boot problem; you are not doing this by accidentally clicking!:)
 
Okay, so now it won't boot anymore. It's stuck here ... Aargh It's nuts. I'ma go to bed for now and continue trying tomorrow.
Thanks so much for now cmd!!
  • I think something went wrong in your CLOVER editing .
    • Usually missing kexts in "Other".
      • I had uploaded image of "Other" showing needed kexts
  • Another reason is ENABLED SIP instead of DISABLED SIP (CsrActiveConfig=0x67 in config.plist_Rt Variables) [See image]
  • Occasionally it can be seen if ACPI has too may unneeded Fixes
 

Attachments

  • Error in Clover kexts or Rt Varaiables .png
    Error in Clover kexts or Rt Varaiables .png
    1.2 MB · Views: 72
  • Rt Variables CsrActiveConfig.png
    Rt Variables CsrActiveConfig.png
    124 KB · Views: 82
  • 1.CLOVER:kexts:Other.png
    1.CLOVER:kexts:Other.png
    24.1 KB · Views: 77
Okay, so now it won't boot anymore. It's stuck here ... Aargh It's nuts.
This error is typically the result of too many unnecessary fixes in config.plist/ACPI/DSDT/Fixes.
Remove all of them (or set false), then enable only those you actually need.
 
This error is typically the result of too many unnecessary fixes in config.plist/ACPI/DSDT/Fixes.
Remove all of them (or set false), then enable only those you actually need.
The point you made is already in my response as the last item and also on the edited Verbose Boot Error screen posted at #14
OP has not come back after that post.
In my opinion, the only way OP can get back to Desktop to try and re-edit CLOVER is by temporarily editing to remove or add some of the things through CBM Screen>Options and submenu items.
If OP has included essential kexts in CLOVER/Other , there is a god chance, he will be able to boot by editing at CBM screen
 
Okay I'm kinda helpless here. I tried different boot flags, but it keeps giving me the same errors.

Any Idea what I could try?
Thanks
 

Attachments

  • IMG_20180124_125422.jpg
    IMG_20180124_125422.jpg
    7.9 MB · Views: 79
Okay I'm kinda helpless here. I tried different boot flags, but it keeps giving me the same errors.

Any Idea what I could try?
Thanks
Upload your CLOVER as a compressed file.
 
Status
Not open for further replies.
Back
Top