macOS 10.14 Mojave on Unsupported Macs Thread

[bbfc]

Cool. I you have time, elaborate a little on your installation or upgrade experience. It may help @peanutismint and @MelkorMorgoth . Thanks.

I just downloaded the Mojave Patcher and installed it as per the instructions. I’ve done it a few times. I did have an issue with a previous beta that @dosdude1 helped with.

https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-498#post-27153871

 

[webg3]

@pkouame I know you're focused on the differences between .3 / .4 ./. 5 and that made some discoveries , can you check also with 10.14.2? Thank you.
[doublepost=1555518849][/doublepost]Will you upgrade your Flat Patch?

 

[kral84]

1.) can i format my 2011 to apfs via recovery or must is use the apfs rom patcher???

2.) i have an GTX 860m must i set Legacy Video Card Patch or not?

 

[flygbuss]

1.) can i format my 2011 to apfs via recovery or must is use the apfs rom patcher???

Your MBP natively supports apfs so there is no need for the rom patcher.

 

[jackluke]

2.) i have an GTX 860m must i set Legacy Video Card Patch or not?

I guess not, just use the "nvidia web driver" if you don't achieve gpu acceleration.
[doublepost=1555521253][/doublepost]

@dosdude1 @ASentientBot @jackluke @pkouame.
For my early 2011 MBP 8.1 13" with Intel3000 I have absolutely same story as @peanutismint.
After updating to 10.14.4 from .3 using @dosdude1's patcher 1.3.0 I have no system transparency, Siri wave, Chess and a couple side apps that use OpenGL rendering such as Jump Desktop etc.
I've even tried fresh install .4 on new unused before ssd no luck with above problem. Now I'll going to try to up for .5b2 with @ASentientBot finding of .3 CoreDisplay.framework, and if it fail I'd to go back for .3.

updating to .5 beta2 will bring a better OpenGL experience overall, without those previous .4 side effects, and at 99% you will have "transparencies" and acceleration this time.

Simple route: update via OTA, apply dosdude1's post install patches for your machine, adding in addition an manual replacement of CoreDisplay.framework , that's all.

Forgot to mention, to those who have had unusual OpenGL not detected, another attempt try to delete from SLE the NDRVShim.kext .

Even if worked with or without it, I don't use it on any of my machines.

 

[MelkorMorgoth]

So... I've updated to .5b2 OTA, then patched with 1.3.0 + .3 CoreDisplay. And I have everything working again!

 

[pkouame]

@pkouame I know you're focused on the differences between .3 / .4 ./. 5 and that made some discoveries , can you check also with 10.14.2? Thank you.
[doublepost=1555518849][/doublepost]Will you upgrade your Flat Patch?

Yes, I'll have "flat" (AppKit) patches available for .4 and .3 sometime this weekend (or before). I'll keep you posted.

 

[jackluke]

@pkouame about your useful recent analysis:

1. CoreDisplay .3 only has a 64 code (no 32 bit support)
2. CoreDisplay .5b+ (and probably .4) has both a 32 and 64 bit

I can confirm that CoreDisplay .4 does have both x86 32 and 64 bit support and using 10144CoreDisplay.framework.zip still bring OpenGL acceleration in combination with .3 OpenGL and GPUSupport.

So I guess it doesn't strictly depend from a 64 code.

Anyway am a bit worried for this .5 beta3 delay.

edit:
From my non-clever analysis also .3 CoreDisplay does contain both x86 architectures, probably you analyzed only a CoreDisplay taken from a BaseSystem.dmg and that's only 64 bit.
But all the frameworks and kext from a BaseSystem are 64 bit only I guess, I call them incomplete, while taking them from a Core.pkg will contain both architectures.

 

[bbfc]

So... I've updated to .5b2 OTA, then patched with 1.3.0 + .3 CoreDisplay. And I have everything working again!

View attachment 832665

I’d love to do that but I wouldn’t know where to start. I’ll wait for @dosdude1 to update the patcher.

 

[pkouame]

@pkouame about your useful recent analysis:

1. CoreDisplay .3 only has a 64 code (no 32 bit support)
2. CoreDisplay .5b+ (and probably .4) has both a 32 and 64 bit

I can confirm that CoreDisplay .4 does have both x86 32 and 64 bit support and using 10144CoreDisplay.framework.zip still bring OpenGL acceleration in combination with .3 OpenGL and GPUSupport.

So I guess it doesn't strictly depend from a 64 code.

Anyway am a bit worried for this .5 beta3 delay.

Not to worry, they're probably late trying to find more ways to trip us up ...
[doublepost=1555534685][/doublepost]

@pkouame about your useful recent analysis:

1. CoreDisplay .3 only has a 64 code (no 32 bit support)
2. CoreDisplay .5b+ (and probably .4) has both a 32 and 64 bit

I can confirm that CoreDisplay .4 does have both x86 32 and 64 bit support and using 10144CoreDisplay.framework.zip still bring OpenGL acceleration in combination with .3 OpenGL and GPUSupport.

So I guess it doesn't strictly depend from a 64 code.

Anyway am a bit worried for this .5 beta3 delay.

edit:
From my non-clever analysis also .3 CoreDisplay does contain both x86 architectures, probably you analyzed only a CoreDisplay taken from a BaseSystem.dmg and that's only 64 bit.
But all the frameworks and kext from a BaseSystem are 64 bit only I guess, I call them incomplete, while taking them from a Core.pkg will contain both architectures.

Yes and Phew! That makes better sense, I did recover a .3 CoreDisplay from an install - just forgot. It's hard keeping track of this.

More on CoreDisplay...

Here's a (incomplete) list of .4 and .5+ frameworks and things that depend on "new" CoreDisplay functionality (VirtualDisplay handling) It may not be complete, but it is significant. Arguably a lot of stuff Apple is actively revamping in .4, .5+ and 10.15.

An obvious conclusion is that any .4/.5 App and or framework leveraging this new functionality will now fail (silently or crash) with the .3 CoreDisplay retro-grade. Probably the reason why News is crashing so "hard" now ...

/System/Library/Frameworks//CoreGraphics.framework/CoreGraphics
/System/Library/Frameworks//CoreMediaIO.framework/Resources/iOSScreenCapture.plugin/Contents/MacOS/iOSScreenCapture
/System/Library/Frameworks//CoreMediaIO.framework/Resources/iOSScreenCapture.plugin/Contents/Resources/iOSScreenCaptureAssistant
/System/Library/Frameworks//MediaToolbox.framework/MediaToolbox
/System/Library/Frameworks//IOKit.framework/IOKit
/System/Library/PrivateFrameworks/AirPlayReceiver.framework/Versions/A/AirPlayReceiver
/System/Library/PrivateFrameworks/AirPlaySender.framework/Versions/A/AirPlaySender
/System/Library/PrivateFrameworks/JavaScriptAppleEvents.framework/Resources/BridgeSupportCache/IOKit.plist

Later...

 

[TimothyR734]

I bought a 500GB Hdd tried installing 10,14,2 but it won't boot tried making a High Sierra patcher and get this bs I am getting frustrated about to throw my iPhone se MacBook and iMac in my creek in the back yard and go back to easy hacker access windows so my of my info can be stolen

 

[SpyderSoldier]

Not to worry, they're probably late trying to find more ways to trip us up ...
[doublepost=1555534685][/doublepost]
Yes and Phew! That makes better sense, I did recover a .3 CoreDisplay from an install - just forgot. It's hard keeping track of this.

More on CoreDisplay...

Here's a (incomplete) list of .4 and .5+ frameworks and things that depend on "new" CoreDisplay functionality (VirtualDisplay handling) It may not be complete, but it is significant. Arguably a lot of stuff Apple is actively revamping in .4, .5+ and 10.15.

An obvious conclusion is that any .4/.5 App and or framework leveraging this new functionality will now fail (silently or crash) with the .3 CoreDisplay retro-grade. Probably the reason why News is crashing so "hard" now ...

/System/Library/Frameworks//CoreGraphics.framework/CoreGraphics
/System/Library/Frameworks//CoreMediaIO.framework/Resources/iOSScreenCapture.plugin/Contents/MacOS/iOSScreenCapture
/System/Library/Frameworks//CoreMediaIO.framework/Resources/iOSScreenCapture.plugin/Contents/Resources/iOSScreenCaptureAssistant
/System/Library/Frameworks//MediaToolbox.framework/MediaToolbox
/System/Library/Frameworks//IOKit.framework/IOKit
/System/Library/PrivateFrameworks/AirPlayReceiver.framework/Versions/A/AirPlayReceiver
/System/Library/PrivateFrameworks/AirPlaySender.framework/Versions/A/AirPlaySender
/System/Library/PrivateFrameworks/JavaScriptAppleEvents.framework/Resources/BridgeSupportCache/IOKit.plist

Later...

hey man just curious, is the public beta the same as the dev betas you talking about? cuz I don't wanna pay 100 for a new dev license just to use betas. lol

 

[Sedulous]

I bought a 500GB Hdd tried installing 10,14,2 but it won't boot tried making a High Sierra patcher and get this bs I am getting frustrated about to throw my iPhone se MacBook and iMac in my creek in the back yard and go back to easy hacker access windows so my of my info can be stolen

Probably something funny about the formatting of drive.

 

[TimothyR734]

yes there is something wrong with the patcher formatting I format my usb HFS extended journaled and the patcher formats it extended I tried booting into 10.14.2 I had a sliver left to the end of the first stage of the boot process watched the Amazing race it took 42 mins to get to the end waiting another 30 mins no black screen with the apple logo I am so mad I never had this issues when I installed 10.14.2 when it first came out did apple change something so when we installed it again it doesn't work
[doublepost=1555565680][/doublepost]I guess I will keep using my old and newer Mojave patchers and apply the post install patches from each 3 I have and force rebuilding my caches until it lets me in or my iMac catches fire

 

[Sedulous]

yes there is something wrong with the patcher formatting I format my usb HFS extended journaled and the patcher formats it extended I tried booting into 10.14.2 I had a sliver left to the end of the first stage of the boot process watched the Amazing race it took 42 mins to get to the end waiting another 30 mins no black screen with the apple logo I am so mad I never had this issues when I installed 10.14.2 when it first came out did apple change something so when we installed it again it doesn't work
[doublepost=1555565680][/doublepost]I guess I will keep using my old and newer Mojave patchers and apply the post install patches from each 3 I have and force rebuilding my caches until it lets me in or my iMac catches fire

In Disk Utility, try selecting View>Show All Devices. Maybe this will let you erase/format the entire volume.

 

[TimothyR734]

In Disk Utility, try selecting View>Show All Devices. Maybe this will let you erase/format the entire volume.

Since I couldn't make a HS patcher I re-downloaded macOS Mojave Patcher 1.2.3 download 10.14.4 created the patcher rebooted and installed the post install patches from it since the patches from 1.3.0 weren't working I got into my desktop finally

 

[avz]

I bought a 500GB Hdd tried installing 10,14,2 but it won't boot tried making a High Sierra patcher and get this bs I am getting frustrated about to throw my iPhone se MacBook and iMac in my creek in the back yard and go back to easy hacker access windows so my of my info can be stolen

It seems that the patcher renamed your target USB drive as OS X Base System. Have you tried naming your USB drive OS X Base System?

 

[noname007]

Yesterday I tried to update to 10.14.5beta2 via "Software update". After update I've installed patches from usb 10.14.4 and made software fix for AMD gpu. But when I launch my mac I have black screen with circle progress bar in the middle for a few seconds than it disappears and cursor appears for a second and then I see circle progress bar again and it goes like this again and again. How can I fix this? And how can I replace CoreDisplay.framework? The terminal on usb with 10.14.4 says that it's readonly.

mbp17 late 2011

 

[ASentientBot]

Yesterday I tried to update to 10.14.5beta2 via "Software update". After update I've installed patches from usb 10.14.4 and made software fix for AMD gpu. But when I launch my mac I have black screen with circle progress bar in the middle for a few seconds than it disappears and cursor appears for a second and then I see circle progress bar again and it goes like this again and again. How can I fix this? And how can I replace CoreDisplay.framework? The terminal on usb with 10.14.4 says that it's readonly.

mbp17 late 2011

Sounds like WindowServer is repeatedly crashing.

You should be able to boot from an up-to-date patcher USB and re-apply the graphics patch from there. If you still have a need to make things writable in single-user mode, type mount -uw / at the shell prompt. You can also temporarily disable acceleration by deleting the OpenGL kext for your GPU. This should let you reach the desktop and re-patch stuff more easily. Not sure which one for Intel (hey, @jackluke, do you remember? ) but for nVidia Tesla it's /S*/L*/E*/GeForceTeslaGLDriver.bundle.

Hope that helps you get back into your system.

 

[jackluke]

Sounds like WindowServer is repeatedly crashing.

You should be able to boot from an up-to-date patcher USB and re-apply the graphics patch from there. If you still have a need to make things writable in single-user mode, type mount -uw / at the shell prompt. You can also temporarily disable acceleration by deleting the OpenGL kext for your GPU. This should let you reach the desktop and re-patch stuff more easily. Not sure which one for Intel (hey, @jackluke, do you remember? ) but for nVidia Tesla it's /S*/L*/E*/GeForceTeslaGLDriver.bundle.

Hope that helps you get back into your system.

Of course, it was your earlier 10.14.4 beta workaround, and till today it seems that method does still allow to use the current OpenGL and GPUSupport framework if renouncing to the GL driver, so a good escape for 10.15 GUI just in case.

For IntelHD has a similar naming, this is it: AppleIntelHD3000GraphicsGLDriver.bundle

Totally agree, if the user succeed to replace CoreDisplay.framework from single user mode, then no other fix is need.

edit:
If I don't get wrong, when I updated to .5 beta2, without patching nothing, system booted straight to GUI desktop (in safe graphics mode), so technically only when using the legacy OpenGL acceleration the "three frameworks" replacement fixes are required.

 

[noname007]

Sounds like WindowServer is repeatedly crashing.

You should be able to boot from an up-to-date patcher USB and re-apply the graphics patch from there. If you still have a need to make things writable in single-user mode, type mount -uw / at the shell prompt. You can also temporarily disable acceleration by deleting the OpenGL kext for your GPU. This should let you reach the desktop and re-patch stuff more easily. Not sure which one for Intel (hey, @jackluke, do you remember? ) but for nVidia Tesla it's /S*/L*/E*/GeForceTeslaGLDriver.bundle.

Hope that helps you get back into your system.

I just reinstalled 10.14.4 for now, but still want to make telegram and onedrive to work again.
The Patcher version by this link http://dosdude1.com/mojave/#updates is 1.3.0 so it didn't change since my first 10.14.4 installation. Or am I missing something?

Have I missed something when I was updating to 10.14.5beta2?
I remember first screen was updating with apple logo and time countdown and the second screen was like the first one but instead of time countdown was circle progress bar and at some point I thought it hanged so I force restarted my mac (come to think of it now, it sounds bad) and just did all post update work except of CoreDisplay.framework replacing and got the situation I described previously.

If I update again and wait till the end of the second screen, then replace CoreDisplay.framework with the one from this post will it be enough? Or should I create a new usb with a new patcher? I believe my current one is 1.3.0.

 

[jackluke]

I just reinstalled 10.14.4 for now, but still want to make telegram and onedrive to work again.
The Patcher version by this link http://dosdude1.com/mojave/#updates is 1.3.0 so it didn't change since my first 10.14.4 installation. Or am I missing something?

Have I missed something when I was updating to 10.14.5beta2?
I remember first screen was updating with apple logo and time countdown and the second screen was like the first one but instead of time countdown was circle progress bar and at some point I thought it hanged so I force restarted my mac (come to think of it now, it sounds bad) and just did all post update work except of CoreDisplay.framework replacing and got the situation I described previously.

If I update again and wait till the end of the second screen, then replace CoreDisplay.framework with the one from this post will it be enough? Or should I create a new usb with a new patcher? I believe my current one is 1.3.0.

If you are currently on 10.14.5 beta2, that CoreDisplay replacement is enough to reach desktop and if you disabled correctly AMD GPU, you should get Video Acceleration too with no efforts.

If you are on 10.14.4 this build has telegram/onedrive UI OpenGL issues (flurry screensaver, chess game, and not only), so much better to update to .5 beta2 after new ASentientBot fix (essentially the CoreDisplay.framework).

If you are on 10.14.4 replacing CoreDisplay doesn't change nothing of your current APPs Graphic UserInterface issues.

CoreDisplay.framework is totally useful to fix all those OpenGL issues only from 10.14.5 beta and (hopefully) below.

BUT there is still a chance if you want to stay on 10.14.4 and continue use telegram and onedrive without those issues you described and it is to delete this:

/System/Library/Extentions/AppleIntelHD3000GraphicsGLDriver.bundle

After a couple of reboot, without GLDriver, all those APPs issues disappear, but you will have no more transparency and graphics acceleration.

 

[pkouame]

hey man just curious, is the public beta the same as the dev betas you talking about? cuz I don't wanna pay 100 for a new dev license just to use betas. lol

I OTA software update developer betas from Apple - then patch. I'm not aware of any "public" betas since these are just developer seeds.

 

[joelw135]

I have been reading this thread over and over and am I correct to say that over the air upgrade to10.14.5 doesn't work with the MacMini 3,1? My graphics card is the NVIDA GeForce 9400

 

[noname007]

If you are currently on 10.14.5 beta2, that CoreDisplay replacement is enough to reach desktop and if you disabled correctly AMD GPU, you should get Video Acceleration too with no efforts.

If you are on 10.14.4 this build has telegram/onedrive UI OpenGL issues (flurry screensaver, chess game, and not only), so much better to update to .5 beta2 after new ASentientBot fix (essentially the CoreDisplay.framework).

If you are on 10.14.4 replacing CoreDisplay doesn't change nothing of your current APPs Graphic UserInterface issues.

CoreDisplay.framework is totally useful to fix all those OpenGL issues only from 10.14.5 beta and (hopefully) below.

BUT there is still a chance if you want to stay on 10.14.4 and continue use telegram and onedrive without those issues you described and it is to delete this:

/System/Library/Extentions/AppleIntelHD3000GraphicsGLDriver.bundle

After a couple of reboot, without GLDriver, all those APPs issues disappear, but you will have no more transparency and graphics acceleration.

Second attempt to install 5beta2 was the same, it hanged on the same screen but it's probably because of my broken AMD gpu.
For some reason replacing CoreDisplay via terminal didn't work for me, but I was able to do it this time thanks to mount -uw / command. Maybe because I didn't delete original folder but renamed it to "CoreDisplay.framework1" and left on the same place.

So I renamed AppleIntelHD3000GraphicsGLDriver.bundle booted mac without acceleration, replaced CoreDisplay.framework, put back IntelHD bundle and next boot was with acceleration and fully functional onedrive and telegram.

Thank you for your help!