macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

What about my other question ? "I still install the 5 IOUSBKexts and your patched CoreBrightness after each update. Is it still usefull to do it after the recent update of @dosdude1 Patcher ? "

I guess no, even if the 5 IOUSBKexts were needed for me to use the same external USB Mojave both on supported and unsupported mac, replacing only 2-3 IOUSBKexts caused Kpanic on the supported mac, I mean a supported mac can run quietly a patched Mojave.

And I still think in manual patching replacing all the 5 IOUSBKexts is still a good practice to enforce the iSight cam and any other third party USB device compatibility/detection.

About CoreBrightness I don't remember exactly but after Mojave beta 4, always the same file still work, but re-patching the new one with pikeralpha method or dosdude1's tool is better.

 

[peanutismint]

Question for @dosdude1: Following your advice to get 10.14.4 working after update on my 2011 MBP. When I run the 'install.sh' tool you provided, I get the following error in Termina:

cp: cannot overwrite directory
​

Any idea why this happens? I'm guessing it's not fixing my graphics acceleration issues because although Mojave now boots again, graphics rendering is choppy with no transparency/shadows etc....?

Anyone got any advice?
[doublepost=1553807347][/doublepost]

Just for an FYI, I went back to 10.14.4...

I kinda need graphics acceleration to run the simulators...one other thing when shutting down, 10.14.5beta takes nearly twice as long to shut down once you get to the swirling gears of doom.

10.14.4 much snappier, better response...I don't always need to be on the very edge of cutting.

Question - how did you (or how can you) roll back to a previous version of macOS? Would you need a Time Machine backup to do this?

 

[dosdude1]

Question for @dosdude1: Following your advice to get 10.14.4 working after update on my 2011 MBP. When I run the 'install.sh' tool you provided, I get the following error in Termina:

cp: cannot overwrite directory
​

Any idea why this happens? I'm guessing it's not fixing my graphics acceleration issues because although Mojave now boots again, graphics rendering is choppy with no transparency/shadows etc....?

Anyone got any advice?
[doublepost=1553807347][/doublepost]


Question - how did you (or how can you) roll back to a previous version of macOS? Would you need a Time Machine backup to do this?

The "cannot overwrite directory" error is normal. You need to make sure you re-apply the legacy video card patch after applying that script.

 

[videotape74]

Can someone please explain exactly what I have to do to get 10.14.4 running on my MBP 5, 4?

Every time I try with the @dosdude1 Mojave Patcher, it seems to install, I reboot and then do the post install patches but then I just get a grey screen and then it boots back into the USB installer. I had no problems with 10.14.3 but I’ve tried 10.14.4 as a fresh install and a update via System Preferences.

Any help would be greatly appreciated, thanks!

Anyone got any ideas? I'm dying here! Haha

 

[peanutismint]

The "cannot overwrite directory" error is normal. You need to make sure you re-apply the legacy video card patch after applying that script.

Thanks for the info (and everything else!). Glad to hear the 'error' is normal; I have re-applied the legacy patch (within your patcher tool, correct?) but I'm still not getting video acceleration after reboot. I read something about needing to use the latest updated version of your patcher tool but I don't know how I can update just the patcher tool on my USB stick without having to re-install the Mojave image as well (which I no longer have and don't have good enough internet to re-download...).

Or did you just mean the 'patch updater' tool needed to be updated to the latest version? Because I've done that already....

 

[Xristian]

Hi all! I accidentally updated to 10.14.4 without updating the patcher. ( I know, rookie move). Is my best recourse to reinstall Mojave using the original patched usb?

Edit: I have a MacBookPro8,1

 

[peanutismint]

Hi all! I accidentally updated to 10.14.4 without updating the patcher. ( I know, rookie move). Is my best recourse to reinstall Mojave using the original patched usb?

Hey mate, I made the same rookie move as you a few days ago Are you stuck without being able to boot now? I found this advice from a few posts back on this thread:

https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-531#post-27225066

 

[Sedulous]

It seems 10.14.4 is not stable on MacBookPro5,2 (DosDude1 reported similar issue). I would suggest remaining on 10.14.3 if you have this model.

 

[AlexyFoxy]

Rolled it back to 10.14.4 and retained graphics acceleration (transparency).

View attachment 828974

Anyone able to accomplish graphics acceleration on 10.14.5? If so can you please let me know the steps? I may have missed something from my original steps listed on my original post. Thanks.

and how you achieved it? you used Hybrid Mode Patchers?

 

[pkouame]

I guess @pkouame should be mentioned in the OP for his hybrid mode patch, editing HiToolBox, Appkit and CoreUI frameworks was not easy at all.

Thanks for the mention. A 10.14.4 compatible hybrid mode patch is under test. So far so good. I will publish this soon once the team can run it through its paces a bit (just like @TimothyR734 did).

I need to catch up with these posts, seems like a lot is happening on the OpenGL and graphics front. The offsets necessary to "hybrid" patch 10.14.4 changed, so new code is in CoreUI which I will start peeling through...

 

[16v]

Is there a nvidia ram patch like for the intel integrated gpu for higher memory use?
Mbp 5.4
Thx

 

[Jas-Singh685]

Thanks for the mention. A 10.14.4 compatible hybrid mode patch is under test. So far so good. I will publish this soon once the team can run it through its paces a bit (just like @TimothyR734 did).

I need to catch up with these posts, seems like a lot is happening on the OpenGL and graphics front. The offsets necessary to "hybrid" patch 10.14.4 changed, so new code is in CoreUI which I will start peeling through...

Just from updating to 10.14.4, I re-installed the hybrid patch over again and it worked perfectly like it did in 10.14.3. Is there a huge difference between the new patch?

Love the patch by the way! I couldn't imagine using Mojave without it!

 

[dosdude1]

Is there a nvidia ram patch like for the intel integrated gpu for higher memory use?
Mbp 5.4
Thx

No, the nVidia MCP chipsets do not have dynamically allocatable video memory. Therefore, they are limited to what they're set at, which is 256MB.

 

[johnsawyercjs]

Still wondering if anyone knows the answer to this: On a Macbook 5,2 running 10.14.4 using @dosdude1's Mojave Patcher, I have some transparency in Dark Mode, but not in Light Mode. Why would that be? And the amount of transparency I see in Dark Mode seems to vary--sometimes Notification Center is semi-transparent, and sometimes it's opaque, while pulldown menus vary in transparency.

 

[icevolt]

I’ve released an update that should fix these issues. A real cause hasn’t been identified and some things still seems to not work correctly but input devices should work now. Available from the releases page of my github.

CC: @Larsvonhier

Works now – great achievement dude! However performance seems to be decreased significantly now. First boot after installation took around 10 minutes (compared to 4 usually), even briefly prompted a crash report, which then closed itself automatically, so no data there – sorry! Oh yeah and Wifi doesn't work.
[doublepost=1553817761][/doublepost]Hey by the way – has anyone ever re-applied thermal paste to their older Macs' CPU, like 2012 and down? Mine (MB5,1) seems to be running unreasonably hot for mostly idling.

 

[pkouame]

Just from updating to 10.14.4, I re-installed the hybrid patch over again and it worked perfectly like it did in 10.14.3. Is there a huge difference between the new patch?

Love the patch by the way! I couldn't imagine using Mojave without it!

I'm glad it helps. As I've mentioned many times before (you can search for it in this long thread) , installing binaries (even my hybrid patched ones) from previous updates is fraught with many risks. Even though the CoreUI and HIToolbox patches are strictly data patches (pretty safe), updated frameworks usually come with updated code. Remember that all these frameworks are inter-dependent. That said, many have been running their systems with older patches successfully. Surprisingly few side effects in fact. But do so at your own risk.
I have a 10.14.4 compatible release of hybrid mode on the stove. It will be published within the week after testing.
Enjoy. Sounds like the 10.14.5 beta is a different beast so I will be analyzing the changes also...

 

[nekton1]

After an update from 10.14.2 to 10.14.4 GM using full USB installer I am seeing this message:

macos needs to repair your Library to run applications

I enter the required account password and see the same message over again and again

 

[DuncanGarp]

Ahh OK LOL. I just wanted to make sure people weren't confused.
[doublepost=1553759390][/doublepost]
Did you make sure to re-apply the legacy video card patch, or rename your GLBundle back after you applied the 10.14.4 acceleration patch?

I did both. Re-applied or re-installed all patches (not just legacy video) using your patch updater and renamed back the AppleIntelHD3000GraphicsGLDriver.bundle. Still no dice. Thanks for responding.

 

[Badruzeus]

Thanks, I´ll try replacing only the binary instead of whole framework contents.
The problem is text output with error/status messages like before under 10.14.4 without the accel-patch from dosdude1.

Interesting is with 10.14.5 I'm still able to reach Desktop using WindowServer binary from 10.13.6 with full gfx accel, at least.. on Fermi. You could also try rolling back this one from 10.14.4 / 10.14.3:

/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer

 

[DuncanGarp]

I can confirm that 10.14.5b1 needs more than the latest 10.14.4accel patch from @dosdude1.
Tried the (now familiar) routine to get acceleration running on my HD3000 GPU (macbook air 4,1), to no avail.
From the screen outputs it seems the window server crashes again (other tasks boot further, but you do not reach the finder/login).
I noticed that in /PrivateFrameworks/ there is a new/updated "HIDDisplays.framework". What puzzles me is that I do not have this on my 10.14.4 machines (framework not there), but in the 10.14.5b1 update some of the files in that bundle have older creation dates that match the installation time of the previous 10.14.4 (final).
Can others confirm existence or absence of this framework on both macOS versions? Thanks!
[doublepost=1553780994][/doublepost]
Re-run the patches for graphics (either with the 1.3.0 version of the patch installer from dosdude1 or with his patch updater tool and the option to re-install all patches).

I have 2 separate partitions on external SSD that has both 10.14.4 Final and 10.14.5 Dev Beta 1 on each. And I do see the HIDDisplays framework on the beta 1 but not on the other. Thanks for noticing it.

 

[jasoncarle]

I am having one small niggle of a problem that I am attempting to diagnose, perhaps someone here can tell me if it might be related to the fact I am running Mojave on an unsupported Mac.

My external Time Machine USB drive is refusing to automatically mount after a restart. If I open disk utility and mount it, it mounts right away. I would appreciate it if I didn't have to do that after every restart though.

First Aid found no errors with the drive either.

 

[RogueB]

It seems 10.14.4 is not stable on MacBookPro5,2 (DosDude1 reported similar issue). I would suggest remaining on 10.14.3 if you have this model.

MacBook Pro 5,2 (17 inch, 3.06, C2D, 8 GB RAM, APFS formatted Seagate Hybrid HD)

I am currently running 10.14.4 (master), without any evidence of instability; can you elaborate on the circumstances under which it becomes unstable (?)

Just for clarity:
I updated OTA to 10.14.4 (Master) from Beta6 -> rebooted -> got stuck at the white-cogwheel phase of the boot -> rebooted into Single User mode -> used terminal to apply dosduded1's patch 10.14.4accel -> rebooted to the USB patcher, and reapplied the standard patches for MacBook Pro 5,2 --> rebooted from USB stick with "force cash rebuilt" option selected, and "arrived" to the view of desktop and login window.

Note, that for a period of time, after logging in (or booting) the CPU is busy doing maintenance tasks (observe Activity Monitor to verify), which do "max out" CPU cycles (fans go near full speed). Once those tasks are completed, however, the machine returns to "idle" showing > 97% to > 98% of CPU available for use.

I did experience a kernel panic after the very first boot, while using Safari for a period of time, but had none while using FireFox developer edition. Oddly, that kernel panic disappeared after I downloaded Safari development edition; now both "safaris" are stable. Not sure if safari incident was coincidental or related. Henceforth, I had no kernel panics, or any other untoward activity.
Hope this is of help.

 

[swamprock]

I advise all MacBook4,1 users to wait until this issue is solved before attempting to use my tool.

I used your tool to create the installer, but followed the steps I outlined here to get USB and trackpad working- https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-537#post-27229227

 

[DuncanGarp]

@dosdude1,

Since it's been confirmed by some that 10.14.5 does not have graphics acceleration using your 10.14.4accel, perhaps you can develop and upgrade to 10.14.5accel? Many thanks as always.

I sorta have the same question too @dosdude1. Thanks.

 

[griftopia]

I had some trouble with my iMac9,1. I realized the kextcache was not building after apply the patches right after boot. So I also tried Force Rebuild. My issue was after loggin in, it would reboot.

So I did this few times. Reinstalled, Applied Patches, Build, Try Login, Force Rebuilt, Try...No difference

Finally seem to have fixed it. Just don't reboot after the first attempt to build caches after patching doesn't seem to work. Do a Force Rebuild right after whether every attempting logon. For some reason, if you let the MacOS boot after applying patches first time (and of course with caches not getting built), it is too late to try again later. You have to assume it's going to have trouble, and simply re-apply patches twice, and do Force Rebuild the second time before attempting logon.

Am a happy camper now. Still can't believe working with 10.14.4 on iMac9,1. :-D