- Joined
- Jun 13, 2014
- Messages
- 56
- Motherboard
- Dell G3 3579
- CPU
- i5-8300H
- Graphics
- UHD 630/GTX 1050
- Mac
-
- Mobile Phone
-
I have a perfectly working sierra 10.12.6 setup on my 3537. I've read through and gone with the steps mentioned in "Common problems in 10.13.x" thread, stopped VESA drivers from loading by injecting properties. Finally I've checked and updated kexts and clover patches.
To avoid APFS conversion, I use the terminal command for direct upgrade mentioned in RehabMan's "Avoid APFS conversion..." thread which reboots me into clover and gives an additional option to boot the installer. Once I boot from this option (using -v), the verbose screen shows a lot of lines starting with "com.apple.xpc.launchd[1].." with most of them ending with "Service exited with abnormal code". These lines take a lot of time of the booting.
Finally once the verbose screen gets over, I get stuck at the apple logo screen with an empty progress bar and an infinitely spinning beach ball stuck in a corner, not movable by mouse. This particular screen appears right after the verbose screen ends, making it harder to troubleshoot the issue.
The (first) attached picture shows the verbose screen state right before it changes to the stuck apple logo screen (second picture)
All problem reporting files have been attached.
To avoid APFS conversion, I use the terminal command for direct upgrade mentioned in RehabMan's "Avoid APFS conversion..." thread which reboots me into clover and gives an additional option to boot the installer. Once I boot from this option (using -v), the verbose screen shows a lot of lines starting with "com.apple.xpc.launchd[1].." with most of them ending with "Service exited with abnormal code". These lines take a lot of time of the booting.
Finally once the verbose screen gets over, I get stuck at the apple logo screen with an empty progress bar and an infinitely spinning beach ball stuck in a corner, not movable by mouse. This particular screen appears right after the verbose screen ends, making it harder to troubleshoot the issue.
The (first) attached picture shows the verbose screen state right before it changes to the stuck apple logo screen (second picture)
All problem reporting files have been attached.