macOS 10.14 Mojave on Unsupported Macs Thread

[dosdude1]

There is actually a difference between the two EFIScriptMain files. I assume I can just include the one from the post install tool resources since that one is normally used to replace the one in the preference pane after it's copied? I assume it's the newer one then. @dosdude1

Yes, just use the one from the Post Install tool resources.

 

[Larsvonhier]

OMG...suddenly can't boot up my mb4,1 after power off the machine from 10.7.5...

very bad timing... the machine should live to see Mojave ;-)

 

[0403979]

Yes, just use the one from the Post Install tool resources.

Thank you for your help. I’ll send you the files and the code snippet to install the patch so you can look over it.

 

[antony34]

Finally it successful installed 10.14.3 into MB 4,1 just fast checked some feature are not working...it will work again tomorrow...coz 4am right now....lol

Trackpad can’t configure (known issue)
Wi-Fi not working (but Bluetooth seems working, have not yet check)
Other things are underchecking

 

[avz]

Up-to-date!

 

[hvds]

System: MBP5,2 17", SSD with APFS, APFS ROM patch applied.

System running well with 10.14.5b2.

Thanks to RogueB for the instructions, and worth repeating what he said: All credit, and thanks, to @dosdude1, @jackluke, @ASentientBot, @pkouame and many others (in no particular order) for their amazing work and perseverance!

To start, cloned stable 10.14.3 to an external SSD (with CCC). 9600M GT GPU selected all the time.
- installed 10.14.4 over this with dosdude's patcher 1.3.0, applied post-install patches, no extra patch updater patches proposed
- updated to 10.14.5b2 OTA, applied 1.3.0 post-install patches again (and rebuilt caches)
- in single-user mode moved .4 CoreDisplay.framework to /System/Library/Frameworks (before, /sbin/mount -uw /). Used the framework attached to post #14339
- booted fine. Rebuilt caches with sudo kextcache -system-caches; sudo kextcache -system-prelinked-kernel (wasn't sure if needed)

The SSD with 10.14.5b2 is now on SATA and being used as my standard system. Fingers still crossed...

Experience so far:
- stable running for a day using the 9600M GT GPU.
- then switched to 9400M, went well for several hours then a KP in Mail. Was difficult to switch back to 9600M GT because of frequent KPs, but eventually succeeded and running fine again with 9600M GT.
- started to use Safari at this point which had caused KPs in 10.14.4. Fine so far for a few hours, so this is better in 10.14.5b2.

After some running I'll retry everything with the .3 CoreDisplay.framework, to see how 9400M behaves then. Apart from having a stable-enough beta system the thrill of experimenting is also valuable.

Thanks again!View attachment 833340

MBP5,2 still on 10.14.5b2, to test 9400M while using .3 CoreDisplay.framework.

System running with 9600M GT.
In single user mode replaced the .4 CoreDisplay.framework in /System/Library/Frameworks with the .3 one.
Rebooted, in Terminal sudo kextcache -system-caches and -system-prelinked-kernel (maybe unnecessarily), rebooted again.
Running fine, then switched to 9400M (see remarks below), rebooted.
Still running fine with 9400M after a while, trying to push it into a KP...

BTW no problems with backlight control etc with either .3 or .4 CoreDisplay.framework.

Remarks on switching GPU:
- although About This Mac and Systen Setting indicate the GPU switching was done, my feeling is that it takes permanent effect, i.e. for next reboot, only after an ordinary shutdown.
- I guess the GPU setting is stored in NVRAM or elsewhere on the main board. Indication is that resetting the NVRAM brings the system into 9400M mode always. And even running from a different disk to switch to 9600M GT mode (had to do that in 10.14.4 from a 10.14.3 disk, otherwise KPs happened too soon to switch) made the switch effective for the next boot from the standard disk.
- one more observation with 9400M during booting: the "white" phase with the progress bar doesn't show, instead after some time or even only after pushing power briefly, the "black" phase starts and boot proceeds OK. Was like this already in 10.14.4, but OK in 10.14.3. That indicates that something is strange with 9400M in 10.14.4 and .5b2 at least during boot, for MBP5,2.

Still no KP with 9400M and .3 CoreDisplay.framework. I'll report if one happens.

EDIT: KP happened as expected - and desired: can proceed to 10.14.5 PB3 now. Switched to 9600M GT for this.

 

[jackluke]

MBP5,2 still on 10.14.5b2, to test 9400M while using .3 CoreDisplay.framework.

System running with 9600M GT.
In single user mode replaced the .4 CoreDisplay.framework in /System/Library/Frameworks with the .3 one.
Rebooted, in Terminal sudo kextcache -system-caches and -system-prelinked-kernel (maybe unnecessarily), rebooted again.
Running fine, then switched to 9400M (see remarks below), rebooted.
Still running fine with 9400M after a while, trying to push it into a KP...

BTW no problems with backlight control etc with either .3 or .4 CoreDisplay.framework.

Remarks on switching GPU:
- although About This Mac and Systen Setting indicate the GPU switching was done, my feeling is that it takes permanent effect, i.e. for next reboot, only after an ordinary shutdown.
- I guess the GPU setting is stored in NVRAM or elsewhere on the main board. Indication is that resetting the NVRAM brings the system into 9400M mode always. And even running from a different disk to switch to 9600M GT mode (had to do that in 10.14.4 from a 10.14.3 disk, otherwise KPs happened too soon to switch) made the switch effective for the next boot from the standard disk.
- one more observation with 9400M during booting: the "white" phase with the progress bar doesn't show, instead after some time or even only after pushing power briefly, the "black" phase starts and boot proceeds OK. Was like this already in 10.14.4, but OK in 10.14.3. That indicates that something is strange with 9400M in 10.14.4 and .5b2 at least during boot, for MBP5,2.

Still no KP with 9400M and .3 CoreDisplay.framework. I'll report if one happens.

EDIT: KP happened as expected - and desired: can proceed to 10.14.5 PB3 now. Switched to 9600M GT for this.

I guess GPU Switching for dualGPUs machine should occur immediately if you used the gfxCardStatus.app , if this doesn't happen it means that only GPUs kexts are loaded but the AGC Mux control is not properly loaded.

I noticed on my dualGPUs machine (manual patched) that a new kext symbol was omitted from linking with the new .5 beta 3 Mojave kernel, and it is related with AppleMCCSControl.kext, moreover I got since .5 beta 1 other unresolved symbol on AppleGraphicsDevicePolicy and AppleMuxControl that are Plugins of the main AppleGraphicsControl.kext .

If you want to try I fixed in this way and now everything work as expected: Mojave .5 beta 3 DualGPUs Mux Switching

Even if with dosdude1 and ASentientBot patches legacy OpenGL acceleration worked without these "MUX" replacement, I noticed that without a correct GPU Switching I had random KP, higher cpu/gpu temperatures, a broken sleep function and a missing Brightness control, or only the HUD without the backlight.

So for my dualGPUs machine this apparently pointless .4 set replacements, was indeed essential.

Moreover I don't know if this .4 replacements are useful to support the News.app too, but News.app on my three machines is working fine with acceleration.

 

[pkouame]

MBP5,2 still on 10.14.5b2, to test 9400M while using .3 CoreDisplay.framework.

System running with 9600M GT.
In single user mode replaced the .4 CoreDisplay.framework in /System/Library/Frameworks with the .3 one.
Rebooted, in Terminal sudo kextcache -system-caches and -system-prelinked-kernel (maybe unnecessarily), rebooted again.
Running fine, then switched to 9400M (see remarks below), rebooted.
Still running fine with 9400M after a while, trying to push it into a KP...

BTW no problems with backlight control etc with either .3 or .4 CoreDisplay.framework.

Remarks on switching GPU:
- although About This Mac and Systen Setting indicate the GPU switching was done, my feeling is that it takes permanent effect, i.e. for next reboot, only after an ordinary shutdown.
- I guess the GPU setting is stored in NVRAM or elsewhere on the main board. Indication is that resetting the NVRAM brings the system into 9400M mode always. And even running from a different disk to switch to 9600M GT mode (had to do that in 10.14.4 from a 10.14.3 disk, otherwise KPs happened too soon to switch) made the switch effective for the next boot from the standard disk.
- one more observation with 9400M during booting: the "white" phase with the progress bar doesn't show, instead after some time or even only after pushing power briefly, the "black" phase starts and boot proceeds OK. Was like this already in 10.14.4, but OK in 10.14.3. That indicates that something is strange with 9400M in 10.14.4 and .5b2 at least during boot, for MBP5,2.

Still no KP with 9400M and .3 CoreDisplay.framework. I'll report if one happens.

EDIT: KP happened as expected - and desired: can proceed to 10.14.5 PB3 now. Switched to 9600M GT for this.

Cool. Yes, the gpu switching is not real-time - one needs to restart for it to take effect. I don't know about gfxCardStatus.app , maybe it enables dynamic switching.

So far, my experience with .5b3 is similar.
[doublepost=1556056972][/doublepost]

I guess GPU Switching for dualGPUs machine should occur immediately if you used the gfxCardStatus.app , if this doesn't happen it means that only GPUs kexts are loaded but the AGC Mux control is not properly loaded.

I noticed on my dualGPUs machine (manual patched) that a new kext symbol was omitted from linking with the new .5 beta 3 Mojave kernel, and it is related with AppleMCCSControl.kext, moreover I got since .5 beta 1 other unresolved symbol on AppleGraphicsDevicePolicy and AppleMuxControl that are Plugins of the main AppleGraphicsControl.kext .

If you want to try I fixed in this way and now everything work as expected: Mojave .5 beta 3 DualGPUs Mux Switching

Even if with dosdude1 and ASentientBot patches legacy OpenGL acceleration worked without these "MUX" replacement, I noticed that without a correct GPU Switching I had random KP, higher cpu/gpu temperatures, a broken sleep function and a missing Brightness control, or only the HUD without the backlight.

So for my dualGPUs machine this apparently pointless .4 set replacements, was indeed essential.

Moreover I don't know if this .4 replacements are useful to support the News.app too, but News.app on my three machines is working fine with acceleration.

Still wondering why your News app does not show "News+" in .5b3? It's been part of News since .4.

 

[bbfc]

Successful update to 10.14.5 DP3 using previous methods.

 

[MrZupp]

Installed 10.14.3 after a series of unsuccessful attempts, and I think that this is the best version for me, despite the fact that I still don't have the ability to change graphic cards or the brightness, since I installed it I had no KP whatsoever, so if anyone knows any patches that can be applied, hit me up
[doublepost=1556059548][/doublepost]

MBP5,2 still on 10.14.5b2, to test 9400M while using .3 CoreDisplay.framework.

System running with 9600M GT.
In single user mode replaced the .4 CoreDisplay.framework in /System/Library/Frameworks with the .3 one.
Rebooted, in Terminal sudo kextcache -system-caches and -system-prelinked-kernel (maybe unnecessarily), rebooted again.
Running fine, then switched to 9400M (see remarks below), rebooted.
Still running fine with 9400M after a while, trying to push it into a KP...

BTW no problems with backlight control etc with either .3 or .4 CoreDisplay.framework.

Remarks on switching GPU:
- although About This Mac and Systen Setting indicate the GPU switching was done, my feeling is that it takes permanent effect, i.e. for next reboot, only after an ordinary shutdown.
- I guess the GPU setting is stored in NVRAM or elsewhere on the main board. Indication is that resetting the NVRAM brings the system into 9400M mode always. And even running from a different disk to switch to 9600M GT mode (had to do that in 10.14.4 from a 10.14.3 disk, otherwise KPs happened too soon to switch) made the switch effective for the next boot from the standard disk.
- one more observation with 9400M during booting: the "white" phase with the progress bar doesn't show, instead after some time or even only after pushing power briefly, the "black" phase starts and boot proceeds OK. Was like this already in 10.14.4, but OK in 10.14.3. That indicates that something is strange with 9400M in 10.14.4 and .5b2 at least during boot, for MBP5,2.

Still no KP with 9400M and .3 CoreDisplay.framework. I'll report if one happens.

EDIT: KP happened as expected - and desired: can proceed to 10.14.5 PB3 now. Switched to 9600M GT for this.

How did you switch to the 9600M?

 

[MTBnBeer]

I've been running 10.14.3 flawlessly for over a month on my very similar MBP 17"(Early2008):Core2Duo 2.6GHz|6GB RAM|512GB SSD|Nvidia 8600M GT 512 MB (MacBookPro4,1). DosDude1 provided a patch which fixed the backlighting on my MBP, but I'm not sure if:

1. DosDude now includes the backlight fix as a post install patch
2. this will work on your similar (but not exactly the same) MBP

Here is the link to my confirmation it worked on my MBP

https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-448#post-26930004

YMMV

 

[pkouame]

Installed 10.14.3 after a series of unsuccessful attempts, and I think that this is the best version for me, despite the fact that I still don't have the ability to change graphic cards or the brightness, since I installed it I had no KP whatsoever, so if anyone knows any patches that can be applied, hit me up
[doublepost=1556059548][/doublepost]
How did you switch to the 9600M?

Energy Saver or a utility like gfxCardStatus

 

[MrZupp]

Energy Saver or a utility like gfxCardStatus

https://ibb.co/s9tdTS5 That's what it's showing me after I logged out 4 times
Also, when waking up from sleep, there's no backlight, despite the fact that the macbook is on, even on 10.14.3

Edit: the backlight turns on for a split second when I force shut down the macbook using the power button

 

[pkouame]

https://ibb.co/s9tdTS5 That's what it's showing me after I logged out 4 times
Also, when waking up from sleep, there's no backlight, despite the fact that the macbook is on, even on 10.14.3

Edit: the backlight turns on for a split second when I force shut down the macbook using the power button

Try restarting - logging out didn't always work for me either. Not sure why. You may also want to try @jackluke 's gfxCardStatus app for more sophisticated handling of your gpus.

I know this may not help, but for me .4 was extremely unstable with sleep, backlight etc. Until I decided to start from scratch: wipe my disk - install a base .4 (from a stick I save for the occasion) - post install etc and OTA update back to the level I prefer (now .5b3) This seems to be the cure all for most if not all of my unstable conditions. Then again, I do a lot of experimenting on my box.

 

[jackluke]

Cool. Yes, the gpu switching is not real-time - one needs to restart for it to take effect. I don't know about gfxCardStatus.app , maybe it enables dynamic switching.

So far, my experience with .5b3 is similar.
[doublepost=1556056972][/doublepost]

Still wondering why your News app does not show "News+" in .5b3? It's been part of News since .4.

The .5 beta 3 News.app version that I'm using is 4.3 , but a little detail is that I haven't logged in News.app with my Apple ID (maybe this is the reason why don't crash?) , I use it just without Apple ID, but searching in app can find and read many free newspaper, and every article opened is an hyperlink to a wider safari page.

However yours dualGPUs Nvidia Tesla is a different machine, as I told with Arrandale, Sandy Bridge, or apfs native machine with a more recent hardware is easier to make things to work (as backlighting control).

Anyway don't know, maybe replacing those .4 set-kext, I can use News.app quietly with acceleration also on MacBook7,1 (Nvidia 320m) without any app crashing.

To those located in Europe and want to launch News.app simply open Terminal and type:
cd /App*/News.app/C*/M*/
./News

 

[pkouame]

The .5 beta 3 News.app version that I'm using is 4.3 , but a little detail is that I haven't logged in News.app with my Apple ID (maybe this is the reason why don't crash?) , I use it just without Apple ID, but searching in app can find and read many free newspaper, and every article opened is an hyperlink to a wider safari page.

On 10.14.4 it is 4.2. So I logged out of iCloud - reopened News - News+ is still a Channel offering a Free Trial. I don't think this is tied to our Apple IDs

 

[jackluke]

On 10.14.4 it is 4.2. So I logged out of iCloud - reopened News - News+ is still a Channel offering a Free Trial. I don't think this is tied to our Apple IDs

I had News+ on .5 beta 1 and crashed with acceleration (Yes I still have a .5 beta 1 copy and ASentientBot CoreDisplay does accelerate also .5 beta 1 ), after updated to .5 beta 2 News+ pane disappeared but the News.app crashed with acceleration , on .5 beta 3 doesn't crash more with acceleration. Can't explain.

If I launch News.app from Terminal the only debug message I get is related to:

/System/iOSSupport/System/Library/PrivateFrameworks/NewsUI.framework

and nothing else.

 

[pkouame]

I had News+ on .5 beta 1 and crashed with acceleration (Yes I still have a .5 beta 1 copy and ASentientBot CoreDisplay does accelerate also .5 beta 1 ), after updated to .5 beta 2 News+ pane disappeared but the News.app crashed with acceleration , on .5 beta 3 doesn't crash more with acceleration. Can't explain.

If I launch News.app from Terminal the only debug message I get is related to:

/System/iOSSupport/System/Library/PrivateFrameworks/NewsUI.framework

and nothing else.

Yes weird - at no point during my upgrade cycle .5b1 -> .5b3 did I ever "lose" News+. And I don't think anyone's reported losing it either. Just that it crashes. I don't see how the way you are patching your machine affects this, but who knows...

 

[webg3]

While you are arguing about News and News+, in my region it does not work, I do not miss it.

When I start the same via Terminal with the command: "open -a news.app" it opens, but most news is not available and when it is, in English only.
It is very limited for Brazil.
[doublepost=1556068750][/doublepost]My workaround is still working.
Who wants to use, is here:

[doublepost=1556068850][/doublepost]

 

[alphascorp]

From normal boot I sometimes encounter also issues to build a correct kextcache on the target drive, instead is much better when I do that from single user mode directly on the target drive.

Moreover I have also issues when I want to clone some OSX installation into other external drives especially handling with APFS containers, instead doing that from a Recovery Environment works like a charm.

I finally managed to update to 10.14.5 Beta 3.

1- I redid a clone of my system 10.14.4 SSD
2- I updated this clone (external SSD) to 10.14.5 Beta 3 with Pacifist.
3- I replaced "CoreDisplay"
4- I re-applied the patches with "macOS Post Install.app" 1.3.0 and force rebuild cache
5- After the correct boot (this time) I re-installed the patches with "Patch Updater.app"

EVERYTHING works fine, I have the Siri waveform, Chess 3.16 and Flurry screensaver

 

[hvds]

Energy Saver or a utility like gfxCardStatus

Yes in my case, energy saver, then logout/login. That seems to do the switch, because when doing that towards 9400M weirdness starts then. - An orderly shutdown seems to additionally make the gpu choice permanent so it survives the next (non-orderly) reboot.
[doublepost=1556082611][/doublepost]

I guess GPU Switching for dualGPUs machine should occur immediately if you used the gfxCardStatus.app , if this doesn't happen it means that only GPUs kexts are loaded but the AGC Mux control is not properly loaded.

I noticed on my dualGPUs machine (manual patched) that a new kext symbol was omitted from linking with the new .5 beta 3 Mojave kernel, and it is related with AppleMCCSControl.kext, moreover I got since .5 beta 1 other unresolved symbol on AppleGraphicsDevicePolicy and AppleMuxControl that are Plugins of the main AppleGraphicsControl.kext .

If you want to try I fixed in this way and now everything work as expected: Mojave .5 beta 3 DualGPUs Mux Switching

Even if with dosdude1 and ASentientBot patches legacy OpenGL acceleration worked without these "MUX" replacement, I noticed that without a correct GPU Switching I had random KP, higher cpu/gpu temperatures, a broken sleep function and a missing Brightness control, or only the HUD without the backlight.

So for my dualGPUs machine this apparently pointless .4 set replacements, was indeed essential.

Moreover I don't know if this .4 replacements are useful to support the News.app too, but News.app on my three machines is working fine with acceleration.

Thank you jackluke. I‘ll experiment a bit more and try your recipe from post #14572, and also gfxCardStatus.
If I remember correctly the GPU switching on my MBP5,2 was always like this: power settings+logout/login lets it take effect, orderly shutdown then saves the setting across next reboot. Only difference with 10.14.4, .5b2 being that 9400M doesn‘t work properly there.
I‘ll try your recipe later today and report back.

 

[FarmerBob]

You have graphics acceleration?

"No."

"Don't have sleep either and Apple-Tab no longer works." Not sure when i lost it, but my 7,1 will no longer sleep. Things are getting really laggy, like "STOPPED". Think I'm gonna wipe and go back to Sierra. I have been running my MacPro 3,1 on it and it's as if it were made for it.

We'll see . . .

 

[0403979]

Thank you for your help. I’ll send you the files and the code snippet to install the patch so you can look over it.

I've now added the APFS patch by @dosdude1 to macOS Patcher. Thanks a lot to dosdude1 for allowing me to include this patch.

Release notes for macOS Patcher 2.1:

• Add APFS patch for older Macs
• Fix issue with restore tool and APFS patch

macOS Patcher 2.1 can be downloaded here.

 

[antony34]

I've now added the APFS patch by @dosdude1 to macOS Patcher. For now it's only on the dev branch and no zips have been uploaded. If you want to try it out you can download it from here. Thanks a lot to dosdude1 for allowing me to include this patch.

Release notes for macOS Patcher 2.1:

• Add APFS patch for older Macs
• Fix issue with restore tool and APFS patch

Thank you very much for your update!

Let me try it as I have not get WiFi work on MB4,1.

 

[pkouame]

While you are arguing about News and News+, in my region it does not work, I do not miss it.

When I start the same via Terminal with the command: "open -a news.app" it opens, but most news is not available and when it is, in English only.
It is very limited for Brazil.
[doublepost=1556068750][/doublepost]My workaround is still working.
Who wants to use, is here:

View attachment 833544
[doublepost=1556068850][/doublepost]View attachment 833546

It's not News or News+ per se that concerns us. It's the fact that one or our "Marzipan" based apps is not working correctly and Apple is doing a lot along those lines (remember News+ was a big announcement last month) , more apps like this will pop-up in 10.15.