Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacBook Pro 13 2017 Mac OS 12.4 (Monterey) doesn't find CoreDisplay #381

Open
AndreyLalin opened this issue Jun 2, 2022 · 2 comments
Open

Comments

@AndreyLalin
Copy link

I've seen this issue for quite a while, but still couldn't figure out how to fix this on Mac OS Monterey:

Can't open /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: No such file or directory.
touch: /System/Library/Extensions: Read-only file system
Re-signing /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
/System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: No such file or directory
Closing...

Also tried to run with md5:

(base) lalin@MacBook-Pro ~ % /Users/lalin/Desktop/CoreDisplay-patcher.command md5
md5: /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: No such file or directory
error: /Library/Developer/CommandLineTools/usr/bin/otool-classic: can't open file: /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay (No such file or directory)
---- BEGINNING MD5 HASH SUMS ---- version: 12.4 build:21F79

error: /Library/Developer/CommandLineTools/usr/bin/otool-classic: can't open file: /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay (No such file or directory)
otool CoreDisplay: d41d8cd98f00b204e9800998ecf8427e
otool CoreDisplay.bak: NO FILE (this is okay)
md5: /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: No such file or directory
CoreDisplay:
CoreDisplay.bak: NO FILE (this is okay)

---- ENDING MD5 HASH SUMS -------

It just doesn't find the required Folder

Does anyone know how to fix this issue?

@moosethegoose2213
Copy link

In macOS Big Sur and newer, binaries (including CoreDisplay) are no longer on-disk - but rather are within the dyld cache. This means that the only way to obtain CoreDisplay in order to patch it would be to download a full macOS installer, extract the Ramdisk, and pull CoreDisplay from there. On top of that, in order to modify files on the system volume, you now need to handle snapshot extractions. This effectively makes automating these patches in macOS 11+ impossible (specifically the lack of binaries being on-disk - snapshotting is very easy to implement), as you have no binary available to the end user.

@augustelemoine
Copy link

Thank you for the explaination.
Would it be any help about snapshot extractions and a way to put Coredisplay at the right place so that the patch could run correctly ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants