Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Just a heads up, on a MacBook7,1 (MacBook Mid 2010) with a macOS Mojave Patcher v1.3.0 and installing Apple's own OTA 10.14.4 update, then patching from USB, it boots to a black screen when the login page should be there.

Installing a fresh full macOS 10.14.4 from said USB and patching it, does work correctly. No black screen. After the first login the Patch Updater will see that it needs to re-patch 3 patches (like night mode).

Works for me.
 
@dosdude1 with MacPro 3,1 I see issues with graphics with 10.14.4 ...OneDrive dropdown menu does not show, Photos images if edited with plugin disappeared when the plugin open....
 
@dosdude1, patch updater is offering to install USBOHCI Support patch in MacBook Pro 6,2, that breaks FaceTime camera (black rectangle). can you fix it please?

Hi LuisN,

I have the same mbp6,2. When i try to boot in safe boot (with shift key) i get a prohibitory sign.
Do you have same issue ?
Thanks for your attention.
 
Hi LuisN,

I have the same mbp6,2. When i try to boot in safe boot (with shift key) i get a prohibitory sign.
Do you have same issue ?
Thanks for your attention.
Yes, I guess it's because it bypasses the com.apple.Boot.plist file in /Lybrary/Preferences and therefore the "-no_compat_check" parameter but I'm just guessing. Maybe someone else can give you a better explanation
 
  • Like
Reactions: ASentientBot
Is there anyway to take screenshots in the installer itself? I have used Parallels Desktop but I don't want to purchase a license for it. I noticed that @dosdude1 did this for his tutorial. Can you explain the process to me please?
 
Thanks a lot dude. Im very grateful. Thanks for your efforts. Im waiting for the solution. Have a nice day!
Installed 10.14.4 on my MBP5,2 this morning, resulting in frequent restarts as Thevivian and others have reported.
Assuming it is to do with graphics I changed the GPU mode after the last restart, to use the NVIDIA GeForce 9600M GT (in system settings/energy->higher performance).
No more restarts, but running only since 2hrs so far, so this could well be just luck. I thought I'd still post it as a hint. Many thanks dosdude1!

(MBP5,2 17", 10.14.4 on an external SSD with APFS, APFS ROM patch applied. Installed with patcher 1.3.0 over 10.14.3, then applying all proposed postinstall patches but APFS, then all proposed patch updater patches: Nightshift, Siri, iSight.)

Bildschirmfoto 2019-03-30 um 14.35.15.png


EDIT: after some 7hrs of smooth daily work with the 9600M GT GPU I switched back to 9400M to see what happens. Switching requires only logout/login to take effekt. I did not observe kernel panics within 15min after switching. I then rebooted and soon got several KPs (about 10min mtbf).
Now again using the 9600M GT, smooth running so far even after rebooting.
EDIT2: after a while of running with the 9600M GT, I switched to 9400M with logout/login, without rebooting. Still no KPs after 30min... and 11hrs.
EDIT3: now observed KPs in 9400M mode under graphics load from Quicktime player. Stable only with 9600M GT.
 
Last edited:
Yes, I guess it's because it bypasses the com.apple.Boot.plist file in /Lybrary/Preferences and therefore the "-no_compat_check" parameter but I'm just guessing. Maybe someone else can give you a better explanation

Thanks for your prompt response. Might not be the problem the "-no_compat_check", as my MacPro3,1 with 10.14.4 upgraded couple days ago, is booting in "safe boot" with no problem.

Any solution to this ?

@dosdude1 have you faced such issue ?

Macbook Pro (6,2) 15" Mid 2010 i7 2.66ghz, Samsung 860 EVO SSD
 
Last edited:
About my experiment, discovering that using the previous "GPUWrangler.framework" lets Mojave 10.14.5 beta1 booting (even w/o 10.14.4accelpatch), digging its dependancies, I found that the "AppleGPUWrangler.kext" is contained inside the "Plugins" folder of /S/L/E/AppleGraphicsControl.kext

I suspect that this could be one of the reasons why OpenGL Acceleration failed loading from 10.14.5 beta 1, I've already tried to replace it with 10.14.3 one but I get "omitting errors" from the prelinkedkernel building, so unusable, I'm trying to figure it out.
 

Attachments

  • AppleGraphicsControl kext plugins.png
    AppleGraphicsControl kext plugins.png
    30.7 KB · Views: 180
Last edited:
Thank's!! Do you use a specific version of colin's installer?
Well, to install 10.14.3 I used version 1.2.3 patcher after updating OTA, and to update to 10.14.4 I did it OTA and used patcher 1.3.0 afterwards.
To roll it all back I just did a restore from my Carbon Copy Cloner backup disk.

Cheers :)

Hugh
 
  • Like
Reactions: K two
Yes, I guess it's because it bypasses the com.apple.Boot.plist file in /Lybrary/Preferences and therefore the "-no_compat_check" parameter but I'm just guessing. Maybe someone else can give you a better explanation
The problem is that as I update my tool, I will need to take new screenshots. I can't do that cause the trial runs out.
 
With 18E226 still get random KPs shortly after reboots mostly while in the Finder, Mini3,1 reboots without the chime and runs fine thereafter for a day or more, sleeps and generally behaves until a restart. Then, more than one KP. Ran as perfection on 10.14.3. All patches up to date, Video Accel working.

So far random KPs have not resulted in lost work.

Quandry.

p.s. That's Dark Reader in Firefox, save your eyes.
Screen Shot 2019-03-30 at 10.06.05 AM.png
 
I tried installing 10.14.5 but as after I logged in the screen went black and got a spinning circle so went back to 10.14.4 reapplied the the patches got a KP a few times then replace the openGL and GPUSupport framework the dosdude's accel and seems to be stable no crashes on my iMac 9,1
Given that my mbp 5,3 upgraded fine to .4 without the need for .3 frameworks, this all must be machine/gpu related. My experience was surprisingly smooth (and no KPs to date). I was expecting the worst with the accounts from this thread.
[doublepost=1553959793][/doublepost]
That's why I asked if you could fix the 10.14.3 binaries , since it is stable and trusted build for our unsupported mac, and the GPUSupport and OpenGL frameworks used for 10.14.4accel dosdude1 are directly taken from 10.14.3 but they are not suffice this time to bring OpenGL on 10.14.5 beta 1.
Many users get random KP with 10.14.4 , 10.14.3 binaries offsets for hybrid patch shouldn't have been changed so much from 10.14.2 .
Got it. I skipped .3, will have to find an old clean .3 distribution to develop hybrid and flat patches (CoreUI, HIToolbox and AppKit)
[doublepost=1553960007][/doublepost]
Well I've done deeply experiments about 10.14.5 beta 1 on Macbook 7,1 mid 2010 and I can affirm that to have a bootable 10.14.5 b1 even with the OpenGL driver prelinked into the kernel (but w/o Acceleration only Framebuffer) these are the requirements:

- Replacing from /S/L/Frameworks/ the OpenGL and OpenCL frameworks with those from 10.14.3 ;
- Replacing from /S/L/PrivateFrameworks/ the GPUSupport.framework (as the dosdude1's accel patch)
- Replacing from /S/L/PrivateFrameworks/ the GPUWrangler.framework with that from 10.14.3 ;

A weird fact is the "GPU Wrangler" should be used for externalGPU (feature for HighSierra or higher), but this updated framework prevents 10.14.5 beta1 booting.

I can assure that replacing only the GPUWrangler.framework any machine can pass the stage2 apple logo, without stucking on "busy timeout (60s)" or "IOconsoleusers lock screen" and with this replaced framework anyone can reach the loginwindow and use Mojave 10.14.5 beta1 with Framebuffer only, not so bad as I expected.

I advise also to use the "OpenCL.framework" from 10.14.3 for a better stability.

Anyway still can't get OpenGL Acceleration and transparencies. That's all for now.

edit:
For those who don't have the required framework (in my humble opinion) to pass always the loginUI from 10.14.5 , I attach it taken from an untouched 10.14.3 .

Even using only this GPUWrangler.framework without applying the dosdude1's 10.14.4accel patch, Mojave 10.14.5 will still boot correctly, but as I stated replacing OpenGL, OpenCL and GPUSupport is almost mandatory for overall stability, for example video web surfing from Safari.
Great work.
 
  • Like
Reactions: jackluke
With 18E226 still get random KPs shortly after reboots mostly while in the Finder, Mini3,1 reboots without the chime and runs fine thereafter for a day or more, sleeps and generally behaves until a restart. Then, more than one KP. Ran as perfection on 10.14.3. All patches up to date, Video Accel working.

So far random KPs have not resulted in lost work.

Quandry.

p.s. That's Dark Reader in Firefox, save your eyes.View attachment 829449
I love dark reader. Also, I see myself. Hello me.
Screenshot 2019-03-30 at 16.51.28.png
 
I can never get that working with macOS Installers. Much less a patched one.

Because from Virtualbox you need a bootloader for a EFI GUID HFS partition, you could try booting through Clover in Virtualbox maybe. I guess also that you should convert your USB installer into Installer.iso DVD image file. And I don't think you can take screenshot through virtual machine with transparencies, since there isn't video acceleration there. But you can take screenshot with transparencies directly from Mojave, of course.
[doublepost=1553966760][/doublepost]
Given that my mbp 5,3 upgraded fine to .4 without the need for .3 frameworks, this all must be machine/gpu related. My experience was surprisingly smooth (and no KPs to date). I was expecting the worst with the accounts from this thread.
[doublepost=1553959793][/doublepost]
Got it. I skipped .3, will have to find an old clean .3 distribution to develop hybrid and flat patches (CoreUI, HIToolbox and AppKit)
[doublepost=1553960007][/doublepost]
Great work.

Thank you, I can't focus much since I've installed 10.14.5 beta 1 on a spinning disk, and debug test is very slow, especially in rebuilding kextcache, I don't have spare ssd at the time to put this beta on.

I could provide you the clean "hybrid files" from 10.14.3 18D109, are suffice only the binaries? Or you need the entire frameworks ?
 
Last edited:
Because from Virtualbox you need a bootloader for a EFI GUID HFS partition, you could try booting through Clover in Virtualbox maybe. I guess also that you should convert your USB installer into Installer.iso DVD image file. And I don't think you can take screenshot through virtual machine with transparencies, since there isn't video acceleration there.
[doublepost=1553966760][/doublepost]

Thank you, I can't focus much since I've installed 10.14.5 beta 1 on a spinning disk, and debug test is very slow, I don't have spare ssd at the time to put this beta.

I could provide you the clean "hybrid files" from 10.14.3 18D109, are suffice only the binaries? Or you need the entire frameworks ?
I only need it for the installer screenshots. I’ve asked before but @dosdude1 didn’t respond on how he did it.
 
  • Like
Reactions: jackluke
I only need it for the installer screenshots. I’ve asked before but @dosdude1 didn’t respond on how he did it.

Then you could try to search and download a pre-prepared Mojave image for Virtualbox, that should include also the bootloader for EFI HFS Virtualbox. I did a test very earlier and it seems wasn't easy to get correctly booting APFS from Virtualbox, but maybe they fixed on the new version.
[doublepost=1553968554][/doublepost]
Thanks for your prompt response. Might not be the problem the "-no_compat_check", as my MacPro3,1 with 10.14.4 upgraded couple days ago, is booting in "safe boot" with no problem.

Any solution to this ?

@dosdude1 have you faced such issue ?

Macbook Pro (6,1) 15" Mid 2010 i7 2.66ghz, Samsung 860 EVO SSD

I'm testing the 10.14.5 beta1 but I guess this previous framework could even fix the 10.14.4 boot issues, could you try ?

GPUWrangler framework
 
Last edited:
Because from Virtualbox you need a bootloader for a EFI GUID HFS partition, you could try booting through Clover in Virtualbox maybe. I guess also that you should convert your USB installer into Installer.iso DVD image file. And I don't think you can take screenshot through virtual machine with transparencies, since there isn't video acceleration there. But you can take screenshot with transparencies directly from Mojave, of course.
[doublepost=1553966760][/doublepost]

Thank you, I can't focus much since I've installed 10.14.5 beta 1 on a spinning disk, and debug test is very slow, especially in rebuilding kextcache, I don't have spare ssd at the time to put this beta on.

I could provide you the clean "hybrid files" from 10.14.3 18D109, are suffice only the binaries? Or you need the entire frameworks ?
No problem. Debugging and testing is hard and time consuming (I know). When you have time, PM with just the binaries or on github. I don't have a .3 test box right now, so I may have to depend on others to test my hybrid patches.
 
  • Like
Reactions: jackluke
Thanks for your prompt response. Might not be the problem the "-no_compat_check", as my MacPro3,1 with 10.14.4 upgraded couple days ago, is booting in "safe boot" with no problem.

Any solution to this ?

@dosdude1 have you faced such issue ?

Macbook Pro (6,2) 15" Mid 2010 i7 2.66ghz, Samsung 860 EVO SSD

@jacklude

Your apfsrecoveryfix worked in my above MBP6,2
Now can enter at recovery :)
Thanks a lot for your hard work!

I still can not enter in safe boot (shift key) and i get the prohibitory sign :mad:

Any assistance is more than welcome.
 
Last edited:
  • Like
Reactions: jackluke
@jacklude

Your apfsrecoveryfix worked in my above MBP6,2
Now can enter at recovery :)
Thanks a lot for your hard work!

I still can not enter in safe boot (shift key) and i get the prohibitory sign :mad:

Any assistance is more than welcome.

from the APFS Recovery (CMD+R), open Terminal and type:

nvram boot-args="-no_compat_check -x"
reboot

This will enforce entering in safe mode, then to return normal mode you have to type later:
nvram boot-args="-no_compat_check"
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.