Yes, on my MBP5,2 I also get the ad-hoc-signed messages, regarding CoreDisplay only.That is bizarre... I don't experience this on my system at all. Nothing has changed in the way that I build/sign the executables for quite a while. Is anyone else getting this issue too?
I already happens right after OTA and post-install patch with 1.3.0, including the legacy video card patch, see post #8203.
Then I replaced the CoreDisplay+CoreDisplayOriginal in
/System/Library/Frameworks/CoreDisplay.framework/Versions/A/
and SkyLight+SkyLightOriginal in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/
with the versions provided in your post #8213.
No change, the boot process still hangs at the same place.
Photos taken at the time when the boot stalls are attached (left and right part of screen). Looks the same when using safe mode.
Looks like a change in 10.15.4 causes this as it happens already with the versions used in patcher 1.3.0 ?
Attachments
Last edited: