I'm Kris! I hope my topic is in a good section.
I am asking you guys for help in this difficult hackintosh problem.
For a very long time I tried to solve it myself but I have no idea how I can solve this problem.
Description of the problem
My problem is that I do not have access to any apple service. I am unable to log into the App Store using my Apple ID. I am unable to log into iCloud account in system preferences. iMessage and Facetime also do not work. Messages that I get when I try to log in: "An error occurred during activation. Try again"
in iMessage: "An error occurred during activation. Try again"
in App Store: "This device or computer can not be verified. Contact the support department for help"
in Face Time: "There was an error during activation. Try again"
In summary, I am unable to log in to any apple network service.
Motherboard: Acer MG43M
Processor: Intel(R) Core(TM)2 Duo CPU E7600 3.06GHz
Graphic card: Gigabyte GeForce 9600GT 515MB
Wi-fi: TP-LINK TL-WN881ND
Ethernet: (not supported)
Audio: (rather, it is not needed here)
My config.plist: https://drive.google.com/drive/folders/1vlYJC329sz6yuTwFr-k0fOs3rfhKeI6l
I have 5 disks including four SSDS and a 4TB HDD configured in a CoreStorage (Fusion drive) volume.
I have Filevault enabled also.
When I turn on my hackintosh, I am presented with the Filevault screen to select my user, enter my password and continue to decrypt and boot macOS. This works around 80% of the time with no issues at all.
Sometimes with seemingly no identifiable pattern, after I enter my password it just hangs on the Filevault screen with the loading bar and does not progress. There is no disk activity either. After a while of the hanging, it will just display the prohibitory sign against a black background.
I have to force shut the hackintosh off with the power button and try to boot again. Usually after I do this, it will boot the second time.
I'm currently running Sierra 10.12.6 but this has also happened when I tried 10.13 too.
Clover is fully up to date as of today (r4380).
Does anyone know why this might occur?
The only thing I have picked up on is the drives change disk identifiers and move themselves around (eg. /dev/disk1) during different boot ups so maybe it's getting confused when trying to decrypt and boot as a corestorage volume. I have no idea how to prevent this from happening either.
Any help or suggestion would really be appreciated.