macOS 10.14 Mojave on Unsupported Macs Thread

[Badruzeus]

Sadly, I have to report, that 10.14.4 is not a daily driver at all. You can goof around with it and beta-test it for the sake of knowledge, but fore serious work you need 10.14.3. So, I was forced to return to 10.14.3, very sad indeed. In my testings 10.14.4 will crash unexpectedly at least once a day. I do not use any of the iOS apps and have no Siri. If one would change appearance elements like "Reduced Transparency" the OS would crash, than it will settle until the next change and crash. Then there are third party programs, which have implemented portions of the new API, which are broken in 10.14.4, but work perfectly fine in 10.14.3. An example for this is Enpass. The support for Mojave's White/Dark themes was implemented as of version 6.0 ( the latest). So that version works outstanding in 10.14.3, but under 10.14.4 it will just open and display a black/white square window depending on the selected theme. So certain programs are rendered by this totally useless. Although at a first glance poucame's 1.4.1 Hybrid mode would seem to work, one can notice some elements having changed appearance and it does not look as pleasing to the eyes and practical for work as with 10.14.3. Given the above, once released, I think none of us will be using 10.15 as a daily driver. By then changes will be so drastic, that no tinkering, nor replacement with older components will manage to rescue the day. We have reached the final station for our old macs. Maybe we should concentrate on making 10.14.3 being able to appear to programs as if of a higher version. In the long run it will be necessary to avoid OS-version restrictions imposed by third party programs. I think in 10.14.3 the support for all features pertinent to Mojave is excellent, this will assure compatibility with future third party apps.

That's what I'm thinking about, even if System runs well with full (non-vanilla) gfx accel but yeah; new API from 3rd party apps will be complicated due to missing some dependencies, binary missmatch, etc.. as Apple either have invited those devs to migrate from OpenGL to Metal. I don't believe that ppl are just running OS only w/o Graphics apps, Office, etc. My last trial was running recent Oracle VirtualBox but having issue with 3D Acceleration though my 10.14.x system are QE/CI enabled for sure (could be bug with the app, or my vanilla Fermi gfx provided by Apple is not supported, who know?)

 

[Project Alice]

Will be interesting to see what the author of MacTracker replies, have contacted him.
With the MCP79 chipset its no surprise, but what took me by surprise is that I only found 6GB as max. RAM in all specs (lowendmac, MacTracker, OWC, ...). If its common knowledge, why don't they correct that entry?

It's too old for anyone besides us to care.

 

[avz]

Anybody have an idea on what these errors might mean?

objc[560]: Class asn1Token is implemented in both /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x12beb8038) and /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128312628). One of the two will be used. Which one is undefined.
objc[560]: Class asn1SetToken is implemented in both /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x12beb8010) and /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128312650). One of the two will be used. Which one is undefined.
objc[560]: Class asn1SequenceToken is implemented in both /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x12beb7fe8) and /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128312678). One of the two will be used. Which one is undefined.
objc[560]: Class asn1IntegerToken is implemented in both /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x12beb7f70) and /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x1283126a0). One of the two will be used. Which one is undefined.
objc[560]: Class asn1OSToken is implemented in both /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x12beb7f98) and /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x1283126c8). One of the two will be used. Which one is undefined.
objc[560]: Class ISPurchaseReceipt is implemented in both /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x12beb7f48) and /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128312a38). One of the two will be used. Which one is undefined.
objc[560]: Class asn1ReceiptToken is implemented in both /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore (0x12beb7fc0) and /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128314ce8). One of the two will be used. Which one is undefined.
objc[560]: Class AAFollowUpController is implemented in both /System/Library/PrivateFrameworks/AppleAccount.framework/Versions/A/AppleAccount (0x127fa2368) and /System/Library/PrivateFrameworks/AOSAccounts.framework/Versions/A/AOSAccounts (0x110b82ef0). One of the two will be used. Which one is undefined.
objc[560]: Class AMSupportURLConnectionDelegate is implemented in both /System/Library/PrivateFrameworks/EmbeddedOSInstall.framework/Versions/A/EmbeddedOSInstall (0x12f8cec58) and /System/Library/PrivateFrameworks/OSPersonalization.framework/Versions/A/OSPersonalization (0x12f731088). One of the two will be used. Which one is undefined.
objc[560]: Class PKFileDownload is implemented in both /System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/PackageKit (0x12e30c498) and /System/Library/PrivateFrameworks/PassKitCore.framework/Versions/A/PassKitCore (0x11c1ac510). One of the two will be used. Which one is undefined.
objc[560]: Class SSRequest is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830f1a8) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a2d90). One of the two will be used. Which one is undefined.
objc[560]: Class SSOperationProgress is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830ef78) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a3150). One of the two will be used. Which one is undefined.
objc[560]: Class SSDownloadMetadata is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830ec58) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a35b0). One of the two will be used. Which one is undefined.
objc[560]: Class SSDownloadAsset is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830ef28) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a3650). One of the two will be used. Which one is undefined.
objc[560]: Class SSDownloadPhase is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830ee88) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a36a0). One of the two will be used. Which one is undefined.
objc[560]: Class SSDownloadStatus is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830ee38) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a3718). One of the two will be used. Which one is undefined.
objc[560]: Class SSDownloadManifestResponse is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830f158) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a3740). One of the two will be used. Which one is undefined.
objc[560]: Class SSPurchase is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830f518) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a2890). One of the two will be used. Which one is undefined.
objc[560]: Class SSPurchaseResponse is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128313398) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a28b8). One of the two will be used. Which one is undefined.
objc[560]: Class SSDownload is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x12830ebb8) and /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFoundation (0x12e9a2840). One of the two will be used. Which one is undefined.
objc[560]: Class SSRestoreContentItem is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128311a48) and /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/CommerceKit (0x12ea6c060). One of the two will be used. Which one is undefined.
objc[560]: Class SSURLRequestProperties is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128310918) and /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/CommerceKit (0x12ea6c510). One of the two will be used. Which one is undefined.
objc[560]: Class SSMutableURLRequestProperties is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128310940) and /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/CommerceKit (0x12ea6c538). One of the two will be used. Which one is undefined.
objc[560]: Class SSRemoteNotification is implemented in both /System/Library/PrivateFrameworks/StoreServices.framework/Versions/A/StoreServices (0x128310f58) and /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/CommerceKit (0x12ea6c790). One of the two will be used. Which one is undefined.
objc[560]: Class SLWebTokenHandlerController is implemented in both /System/Library/Frameworks/Social.framework/Versions/A/Social (0x12be4c1c0) and /System/Library/PrivateFrameworks/SocialServices.framework/Versions/A/SocialServices (0x12bdd0fe8). One of the two will be used. Which one is undefined.

 

[Larsvonhier]

It's too old for anyone besides us to care.

Haha. That attitude would make all historians and archeologists obsolete. ;-)
Oh, wait - we are the h&a´s!
[doublepost=1554186063][/doublepost]

That's what I'm thinking about, even if System runs well with full (non-vanilla) gfx accel but yeah; new API from 3rd party apps will be complicated due to missing some dependencies, binary missmatch, etc.. as Apple either have invited those devs to migrate from OpenGL to Metal. I don't believe that ppl are just running OS only w/o Graphics apps, Office, etc. My last trial was running recent Oracle VirtualBox but having issue with 3D Acceleration though my 10.14.x system are QE/CI enabled for sure (could be bug with the app, or my vanilla Fermi gfx provided by Apple is not supported, who know?)

My experience in running 10.14.4 on various machines* without tinkering with the transparencies is on the contrary: Very useful, very stable and I had no crashes at all (just on a dual GPU machine I have to use the GT instead of M).
And there are many of us who are happy to have a minimum set of modern apps for daily tasks:
Mail, iTunes, Browsers, iWork or M$Office, some photo viewers...
So my advice would be stop modding the frameworks for optics alone (transparencies) and use the machines a while in that state to see if they really crash as hell on 10.14.4. Mine don´t.

*currently on MacBook 5,2 - MacBook Air 4,1 11" - MacBook Pro 5,2 - MacBook 4,1 - MacBook 7,x and 6,x 13"- MacBook Air 2,1 - MacBook Pro 4,1 17"

 

[Vitamincbu]

Im thinking about buying a cheap iMac 2011 with Radeon GPU.
It is still running High Sierra and the Mojave patcher is not workin, because of die Radeon GPU.

Will it be possible to get the GPU working in the future or is it absolutely impossible to get this working at some time ?

 

[avz]

Hi,
I haven't been able to get 10.14.4 running on my Macbook5,1 (2008 unibody Macbook), but it looks like some people have had success. (When I install 10.14.4, it doesn't recognise the display and keyboard, hence I get no backlight and it thinks the screen is an external display.) Can anyone share a recipe for successfully installing 10.14.4. on a Macbook5,1 (not MacbookPro5,1)?

Thank you!

This is how I did it.
I already had 10.14.3 installed, so I just downloaded 10.14.4 through the Software Update.
Booted in Single User mode(CMD+S) and renamed the GeForceTeslaGLDriver.bundle.
Rebooted in Mojave 10.14.4 and applied 10.14.4accel patch.
Renamed GeForceTeslaGLDriver.bundle to its original name.
Rebooted with full graphic acceleration.
I don't remember if I had to redo the Night Shift, but I always do it manually as per pikeralpha guide.
Manually replaced Siri framework.
Done.

 

[jklas]

I guess you have mixed the dosdude1's Post Install, with 10.14.4accel patch and with my IntelHD3000 kexts, then boot again with CMD+S and try these:

mount -uw /
rm -R /System/Library/Extensions/AMDRadeonX3000.kext
chown -R 0:0 /System/Library/Extensions/
chmod -R 755 /System/Library/Extensions/
kextcache -i /
reboot

if after that you still can't reach the desktop then boot with CMD+S and:
mount -uw /
rm -R /System/Library/Extensions/AppleIntelHD3000GraphicsGLDriver.bundle
reboot

Hey jackluke my friend,
I did what you said with my old unsupported MBP 13" 2010.
I put my SSD from my MBP 8,2 which does not boot. and then I tried to fix everything with cmd + s but it didnt worked out. I boots but just like 75% and then reboots again... .
I dont have those files AMDRadeonX3000.kext and the AplleInten.....bundle while trying to remove them.
What should I do now?! :/

EDIT: I put the SSD after the single user mode commands back into my MBP 8,2 15" but it still does not show me any screen or anything on the display.
My other MBP is a 7,1 13". I put the Post install patch but it didnt allow me to boot normal into MacOS not even with shift boot on. So actually I really dont know how to fix that issue?! :/

 

[jackluke]

Hey jackluke my friend,
I did what you said with my old unsupported MBP 13" 2010.
I put my SSD from my MBP 8,2 which does not boot. and then I tried to fix everything with cmd + s but it didnt worked out. I boots but just like 75% and then reboots again... .
I dont have those files AMDRadeonX3000.kext and the AplleInten.....bundle while trying to remove them.
What should I do now?! :/

EDIT: I put the SSD after the single user mode commands back into my MBP 8,2 15" but it still does not show me any screen or anything on the display.
My other MBP is a 7,1 13". I put the Post install patch but it didnt allow me to boot normal into MacOS not even with shift boot on. So actually I really dont know how to fix that issue?! :/

For MBP 13" 2010 you need two more steps, booting with CMD+S type :

mount -uw /
rm -R /System/Library/Extensions/GeForceTeslaGLDriver.bundle
rm -R /System/Library/UserEventPlugins/com.apple.telemetry.plugin
exit

edit:
About "repairing" MBP 8,2 15" search for "MuxHat" by dosdude1 , maybe is an easy way tool to disable your AMD faulty video card instead of de-solder the R8911 resistor.

 

[kellydavid]

This is how I did it.
I already had 10.14.3 installed, so I just downloaded 10.14.4 through the Software Update.
Booted in Single User mode(CMD+S) and renamed the GeForceTeslaGLDriver.bundle.
Rebooted in Mojave 10.14.4 and applied 10.14.4accel patch.
Renamed GeForceTeslaGLDriver.bundle to its original name.
Rebooted with full graphic acceleration.
I don't remember if I had to redo the Night Shift, but I always do it manually as per pikeralpha guide.
Manually replaced Siri framework.
Done.

Thanks.
Just to confirm... running 10.14.3, you downloaded and installed the 10.14.4 software update and THEN rebooted in single-user mode and renamed the GeForceTeslaGLDriver.bundle and then rebooted into 10.14.4 and applied the accel patch, etc?

Did you have any problems with the Macbook5,1 keyboard not being recognised and hence no "adjust keyboard brightness in low light" option in System Preferences->Keyboard?

Thanks again.

 

[puremind2000]

Do you still have the right Apple Installer dmg for 10.14.3?

Yep, I kept a copy and patched with dosdude1's version 1.2.3 (just in case)

No KPs again. Will Stay in 10.14.3 for a while. Definitely something wrong with 10.14.4 or the patching.

 

[avz]

Thanks.
Just to confirm... running 10.14.3, you downloaded and installed the 10.14.4 software update and THEN rebooted in single-user mode and renamed the GeForceTeslaGLDriver.bundle and then rebooted into 10.14.4 and applied the accel patch, etc?

Did you have any problems with the Macbook5,1 keyboard not being recognised and hence no "adjust keyboard brightness in low light" option in System Preferences->Keyboard?

Thanks again.

Yes, I put the steps in chronological order, you can't mix them around.

I don't have the keyboard backlight, so I'm not able to test it, but my Apple Wireless Keyboard and internal keyboard are recognised and both working very well.
I would strongly recommend you to manually patch the Night Shift(as per pikeralpha) as it deals with CoreBrightness.framework and can easily break System Preferences Panes(as I learned the hard way in 10.13.6). For whatever reason(don't ask me why) the "one size fit all unsupported Macs" patch does not always work in case of CoreBrightness.framework.

 

[jklas]

For MBP 13" 2010 you need two more steps, booting with CMD+S type :

mount -uw /
rm -R /System/Library/Extensions/GeForceTeslaGLDriver.bundle
rm -R /System/Library/UserEventPlugins/com.apple.telemetry.plugin
exit

edit:
About "repairing" MBP 8,2 15" search for "MuxHat" by dosdude1 , maybe is an easy way tool to disable your AMD faulty video card instead of de-solder the R8911 resistor.

So I gonna put my MBp 8,2 SSD into my MBP 13" and then type those things that you mentioned. Then I could boot normally the SSD with Mojave right?
And after this I need to do what?
Put those. AMD3000.kext files into extensions? Or run that Programm that you mentioned before?

 

[jackluke]

So I gonna put my MBp 8,2 SSD into my MBP 13" and then type those things that you mentioned. Then I could boot normally the SSD with Mojave right?
And after this I need to do what?
Put those. AMD3000.kext files into extensions? Or run that Programm that you mentioned before?

Yes, put again the ssd inside the MBP 13" and do those steps from CMD+S, after from booted Mojave apply the dosdude1's 10.14.4accel patch, then re-apply the Post-Install patches for your machine to get Video Acceleration and transparencies.

The AMD3000 kext and IntelHD3000 were required only for your MBP 8,2 .

 

[jklas]

Yes, put again the ssd inside the MBP 13" and do those steps from CMD+S, after from booted Mojave apply the dosdude1's 10.14.4accel patch, then re-apply the Post-Install patches for your machine to get Video Acceleration and transparencies.

The AMD3000 kext and IntelHD3000 were required only for your MBP 8,2 .

Well but I want to use my MBP 8,2 again.
Well it does not allow me to use the Mojave on my MBP 13". I cannot start the cmd + s on my MBP 13".
Only running the USB-Installer with 1.3.0 version shows me something. I did the Post install with the model that I actually was going to run MBP 8,2 and shutdown the MBP 13" to put my SSD back to my MBP 8,2. But it didnt start properly...at my MBP 8,2 :/

So I put the SSD back into my MBP 13" and ran the Post-Installer for the recommended 7,1 MBP and now I can use the SSD on my MBP 13".
So what should I do now? put the kext files back? or what?
I just run normally Mojave on my MBp 13" now. But I didnt restart yet to see if I can use the cmd+s mode :/

 

[jackluke]

Well but I want to use my MBP 8,2 again.
Well it does not allow me to use the Mojave on my MBP 13". I cannot start the cmd + s on my MBP 13".
Only running the USB-Installer with 1.3.0 version shows me something. I did the Post install with the model that I actually was going to run MBP 8,2 and shutdown the MBP 13" to put my SSD back to my MBP 8,2. But it didnt start properly...at my MBP 8,2 :/

So I put the SSD back into my MBP 13" and ran the Post-Installer for the recommended 7,1 MBP and now I can use the SSD on my MBP 13".
So what should I do now? put the kext files back? or what?
I just run normally Mojave on my MBp 13" now. But I didnt restart yet to see if I can use the cmd+s mode :/

About the MBP 8,2 wasn't been the Post-Install the cause why you power-on to black screen, instead your AMD/ATI GPU has become faulty, it was in the air, known issue, so to fix it definitely you should "repair" it de-solder with hot air the resistor R8911 I guess.

If are located in the same country of dosdude1 he can fix it for sure: https://forums.macrumors.com/thread...ook-pro-dedicated-gpu-gmux-ic-bypass.2134019/

About Mojave patched on MBP 13" if you see the Dock and the Notification Center transparencies then you have to do nothing more.

edit:
The main fact why Mojave, when you swapped the SSD from MBP 8,2 to MBP 7,1 , hasn't worked immediately is essentially because MBP 8,2 has an i7 cpu and dual GPUs (AMD ATI and IntelHD3000), MBP 7,1 has Core2Duo CPU and single Nvidia GPU.

 

[jklas]

About the MBP 8,2 wasn't been the Post-Install the cause why you power-on to black screen, instead your AMD/ATI GPU has become faulty, it was in the air, known issue, so to fix it definitely you should "repair" it de-solder with hot air the resistor R8911 I guess.

If are located in the same country of dosdude1 he can fix it for sure: https://forums.macrumors.com/thread...ook-pro-dedicated-gpu-gmux-ic-bypass.2134019/

About Mojave patched on MBP 13" if you see the Dock and the Notification Center transparencies then you have to do nothing more.

edit:
The main fact why Mojave, when you swapped the SSD from MBP 8,2 to MBP 7,1 , hasn't worked immediately is essentially because MBP 8,2 has an i7 cpu and dual GPUs (AMD ATI and IntelHD3000), MBP 7,1 has Core2Duo CPU and single Nvidia GPU.

Okay I am kinda confused.
I live in germany by the way.

And well I just tried to run the accel script via terminal, which said again those cannot override... even doing it with sudo. So I guess it didnt worked properly.
Also I reinstalled the legacy Video Patcher. Which worked and I rebooted on my MBP 13" 7,1.
But actually I want to use the Mojave SSD with it on my MBP 8,2 15". Which is a 8,2 model.
So how should I proceed now? do the single user mode as next at the MBP 13" or run the post installer with settings for the 8,2 Model? Or should I install something else?
By the way I cannot see everything transparent, so should I install something else now? Like the tool that you posted once?

thanks in advance and sorry for annoying you with my questions and so on.. :/

 

[jackluke]

Okay I am kinda confused.
I live in germany by the way.

And well I just tried to run the accel script via terminal, which said again those cannot override... even doing it with sudo. So I guess it didnt worked properly.
Also I reinstalled the legacy Video Patcher. Which worked and I rebooted on my MBP 13" 7,1.
But actually I want to use the Mojave SSD with it on my MBP 8,2 15". Which is a 8,2 model.
So how should I proceed now? do the single user mode as next at the MBP 13" or run the post installer with settings for the 8,2 Model? Or should I install something else?
By the way I cannot see everything transparent, so should I install something else now? Like the tool that you posted once?

thanks in advance and sorry for annoying you with my questions and so on.. :/

Then to see things transparent on your MBP 13" 2010, and having an overall faster UI experience, follow this steps:

- Download this archive from dosdude1
- Go in that folder from Finder
- copy "GPUSupport.framework" from "10.14.4accel folder" and paste it in this path /System/Library/PrivateFrameworks/ when you are overwriting and system message asks for: "Do NOT Merge" but instead "Replace All"
- copy "OpenGL.framework" from "10.14.4accel folder" and paste it in this path /System/Library/Frameworks/ when you are overwriting and system message asks for "Do NOT Merge" but instead "Replace All"

reboot and you will finally have Video Acceleration.

 

[jklas]

Then to see things transparent on your MBP 13" 2010, and having an overall faster UI experience, follow this steps:

- Download this archive from dosdude1
- Go in that folder from Finder
- copy "GPUSupport.framework" from "10.14.4accel folder" and paste it in this path /System/Library/PrivateFrameworks/ when you are overwriting and system message asks for: "Do NOT Merge" but instead "Replace All"
- copy "OpenGL.framework" from "10.14.4accel folder" and paste it in this path /System/Library/Frameworks/ when you are overwriting and system message asks for "Do NOT Merge" but instead "Replace All"

reboot and you will finally have Video Acceleration.

Okay, but then I can put it back into my MBp 8,2? And it should start normally??

 

[jackluke]

Okay, but then I can put it back into my MBp 8,2? And it should start normally??

Yes, but I guess to pass the black screen with your MBP 8,2 you need a little repair internally the logic board.
[doublepost=1554203992][/doublepost]@Larsvonhier , just to report, but your SiriUI.framework patch doesn't seem to work more on 10.14.5 beta1, while instead work exactly on 10.14.4 final build.

 

[Larsvonhier]

Yep, I kept a copy and patched with dosdude1's version 1.2.3 (just in case)

No KPs again. Will Stay in 10.14.3 for a while. Definitely something wrong with 10.14.4 or the patching.

Nope. See #13779.
[doublepost=1554204244][/doublepost]

Yes, but I guess to pass the black screen with your MBP 8,2 you need a little repair internally the logic board.
[doublepost=1554203992][/doublepost]@Larsvonhier , just to report, but your SiriUI.framework patch doesn't seem to work more on 10.14.5 beta1, while instead work exactly on 10.14.4 final build.

Yes, thanks, I noticed it also. Will have to do a further test flight on my MB4,1 (stranded there without GPU accel for the rest of time anyway, so I can also stay there if the rest works - meaning Siri also being fixed).

 

[jklas]

Yes, but I guess to pass the black screen with your MBP 8,2 you need a little repair internally the logic board.
[doublepost=1554203992][/doublepost]@Larsvonhier , just to report, but your SiriUI.framework patch doesn't seem to work more on 10.14.5 beta1, while instead work exactly on 10.14.4 final build.

Okay, but well it started once normally and as I said kinda skipped cause of my reboot routine.. .
And actually it doenst make any sens that it does not work anymore the display... .
Since the same "misstake" happend with the post installscript, after I used it at my MBP 13" 7,1. But I canceled the thingy and then it restarted normally with Mojave... .
So should I use the post installscript with the MBp 8,2 settings just to be sure? and start it once with single user mode to do those things that you mentioned, or can I just use my MBp 8,2 with the order of the part that you gave me as advice?

 

[jackluke]

Okay, but well it started once normally and as I said kinda skipped cause of my reboot routine.. .
And actually it doenst make any sens that it does not work anymore the display... .
Since the same "misstake" happend with the post installscript, after I used it at my MBP 13" 7,1. But I canceled the thingy and then it restarted normally with Mojave... .
So should I use the post installscript with the MBp 8,2 settings just to be sure? and start it once with single user mode to do those things that you mentioned, or can I just use my MBp 8,2 with the order of the part that you gave me as advice?

I guess it's not the display but the faulty AMD ATI Video Card that can't let you pass the power-on EFI CHECKS, so it stucks on black screen turned off LCD with sleep white led staying on solid.

 

[avz]

Thanks.
Just to confirm... running 10.14.3, you downloaded and installed the 10.14.4 software update and THEN rebooted in single-user mode and renamed the GeForceTeslaGLDriver.bundle and then rebooted into 10.14.4 and applied the accel patch, etc?

Did you have any problems with the Macbook5,1 keyboard not being recognised and hence no "adjust keyboard brightness in low light" option in System Preferences->Keyboard?

Thanks again.

Sorry, I forgot another step, after the update it is a good idea to boot into the installer(1.2.3 will do) and re-apply the patches with force cache rebuild. It is only logical as an update usually breaks the patches which causes boot loops with no regard to what you did in a Single User Mode. Cheers.

 

[jklas]

I guess it's not the display but the faulty AMD ATI Video Card that can't let you pass the power-on EFI CHECKS, so it stucks on black screen turned off LCD with sleep white led staying on solid.

hmm okay, but it is the first time that this happend like this!
also is there no other possibility to fix that except by doing something at the logic board?

actually the thing really never happend before. and then the MBP just wanted to reboot and then the display just went dark, like no soul into it anymore... . I know that this is pretty random now, but to be honest, it did the same with the white LED on my MBP 13" 7,1. But I could cancel it. Maybe it has something to do with the update procedure by myside or anything else. Its kinda sad that it came like this and maybe someone can help me out.

 

[jackluke]

hmm okay, but it is the first time that this happend like this!
also is there no other possibility to fix that except by doing something at the logic board?

actually the thing really never happend before. and then the MBP just wanted to reboot and then the display just went dark, like no soul into it anymore... . I know that this is pretty random now, but to be honest, it did the same with the white LED on my MBP 13" 7,1. But I could cancel it. Maybe it has something to do with the update procedure by myside or anything else. Its kinda sad that it came like this and maybe someone can help me out.

Try to plug the MBP 8,2 with Magsafe charger and from a power-off state (no white sleep led) hold down until the Magsafe led will change from orange to green, then release and re-try to power on :

Left Shift+Control+Option+Power button