macOS 10.14 Mojave on Unsupported Macs Thread

[BookEmDanno]

If you use that file your PrefPanes error will disappear and the "input devices customization" will 100% work again. It's the same identical CoreBrightness file you could obtain if you patch it yourself from your machine. I suggest only this time use that file, at the next Mojave beta 6 for sure they will update it and so then you will try the cbpatcher yourself.
[doublepost=1533136778][/doublepost]

Still no dice. Ran the steps, didn't get any codesigning errors, rebooted twice and I am still having the same Preference Panes issues. Thanks.

 

[TimothyR734]

Try only replacing essential graphics drivers to get the system to function and see if you can get transparency working.

I tried booting without the legacy video patch endless reboot

 

[jackluke]

Still no dice. Ran the steps, didn't get any codesigning errors, rebooted twice and I am still having the same Preference Panes issues. Thanks.

Even there are code-signing errors they are not noticeable, but there could be.
If you haven't tried yet, please try using this file it will 100% work: DOWNLOAD Night Shift Mojave beta 5 patched
You have to copy it manually through Finder folders, replacing the existing one you have, then reboot and I guarantee you will fix all your issues.

This has been done through the dosdude1 cbpatcher, and Olivia88 discovered that will fix Mouse/Keyboard/Trackpad issues too.

EDIT:
Be sure to rename that file in "CoreBrightness" because if you have downloaded others in past on your machine it will be automatically renamed by Safari with auto-zip-decompressing into wrong name "CoreBrightness-1" or "CoreBrightness-2" and so on.
The name of file must be ONLY "CoreBrightness" so rename it before copying.

 

[0403979]

I finally installed Mojave beta 5 on my MacBook7,1’s main SSD after having to decrypt it and then reinstall because of a failed night shift patch.
[doublepost=1533139923][/doublepost]I’m using dark mode with Reduce Transparency.

 

[BookEmDanno]

Even there are code-signing errors they are not noticeable, but there could be.
If you haven't tried yet, please try using this file it will 100% work: DOWNLOAD Night Shift Mojave beta 5 patched
You have to copy it manually through Finder folders, replacing the existing one you have, then reboot and I guarantee you will fix all your issues.

This has been done through the dosdude1 cbpatcher, and Olivia88 discovered that will fix Mouse/Keyboard/Trackpad issues too.

EDIT:
Be sure to rename that file in "CoreBrightness" because if you have downloaded others in past on your machine it will be automatically renamed by Safari with auto-zip-decompressing into wrong name "CoreBrightness-1" or "CoreBrightness-2" and so on.
The name of file must be ONLY "CoreBrightness" so rename it before copying.

That worked! ~Mahalo~(Thanks) @jackluke.

 

[0403979]

@dosdude1 I sent you a private message a bit ago and thought that it would be better if you answered my question here so others can use some of the information as well. Here’s the message:

Hello dosdude1,
I was just wondering how exactly your macOS Mojave Patcher works? I noticed that the installer usb file system structure was different than a regular macOS Mojave usb installer made with the command line. I also noticed that not all regular utilities are included in the patched installer. Would you mind letting me know a bit about how you made this patcher?

 

[jackluke]

@dosdude1 I sent you a private message a bit ago and thought that it would be better if you answered my question here so others can use some of the information as well. Here’s the message:

When a developer release his software, unless explicitly declared that it is released as open-source, he is not obliged to disclose how he developed the software.
[doublepost=1533144025][/doublepost]

That worked! ~Mahalo~(Thanks) @jackluke.

I used the cbpatcher of dosdude1, that is perfectly working on my machines but unluckily on some machine seems give some issues, but I would say don't depending from the patcher itself but some incompatibility due to different Xcode Command Line Tools versions installed on different machines.

EDIT:
Anyway @dosdude1 , I am going to contradict myself, but as you seen the Mojave beta 5 CoreBrightness is 718 KB, after your cbpatcher it becomes 727 KB, it was been so also for Mojave beta 4.
Making a foresee, I don't think they will make big changes, so I guess there would be less issues if you include a CoreBrightness already patched into your Mojave Patcher or maybe release the cbpatcher in the form of a shell script.

The merit is absolutely yours, you did it first for Mojave, as far I know pikeralpha abandoned it since High Sierra 10.13.2

 

[Badruzeus]

If you use that file your PrefPanes error will disappear and the "input devices customization" will 100% work again. It's the same identical CoreBrightness file you could obtain if you patch it yourself from your machine. I suggest only this time use that file, at the next Mojave beta 6 for sure they will update it and so then you will try the cbpatcher yourself.
[doublepost=1533136778][/doublepost]

Maybe you are right, the SkyLight.framework could be the main responsible of the greyed menu bar in "light mode".

I've checked the console app during switching from "dark mode" to "light mode" I read this message:
WindowServer (Skylight) invalid surface "number" for window "number"

Replacing the entire HS SkyLight.framework will stuck on Mojave verbose mode due to many console crashes incompatibility.

Instead inspecting SkyLight from Mojave, I tried replacing just some elements inside the HS Skylight.framework and it partially boot in Mojave but only to black screen with mouse cursor.

Using an entire HS Skylight a mandatory element for Mojave required to boot ONLY until a stage2 black screen is:

(THIS FILE MUST BE FROM MOJAVE otherwise you get console crashes on verbose mode)
/S/L/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer

All the others seems replaceable BUT this won't work, if you try it will bring you after stage2 to a black cursor screen, this is just informative to show that a future booting using a previous Skylight framework could be possible with proper patching.

Yeah, as @parrotgeek has ever said.. it' s not ez figuring out issue with WindowServer...

 

[pkouame]

Hi pkouname, any solution for update from dev b4 to b5?
Thanks

So far not. I’ve gone as far as logging the full xml during a system update from dp4. Am peeling through it but nothing jumps out at me. The software update patch should still work. I’m sure others are working on this too.

 

[ASentientBot]

@ASentientBot , even after another beta wave, your Legacy Nvidia Tesla patch and C2D fix still rock!!!

* my legacy nVidia Tesla patch and our C2D fix

From a manual patched Macbook7,1 just needed to replace: telemetry.plugin, IOUSB***, AppleHDA.

Mojave beta 5 is amazing, safari 12 almost perfect, to me it looks like a GM candidate.

In my experience, only IOUSBHostFamily.kext and IOUSBFamily.kext need to be replaced. We don't want to replace unnecessary files.

I don't think the transparency issues are due to .car files. It's due to the graphics drivers.

I'm going to try booting with the graphics patches removed and see if the transparency issues are still present. This might shed some light on it (though to be honest, I really don't care about the transparency issues).

Edit: fixed something with the quotes.

 

[0403979]

* my legacy nVidia Tesla patch and our C2D fix



In my experience, only IOUSBHostFamily.kext and IOUSBFamily.kext need to be replaced. We don't want to replace unnecessary files.

I don't think the transparency issues are due to .car files. It's due to the graphics drivers.

I'm going to try booting with the graphics patches removed and see if the transparency issues are still present. This might shed some light on it (though to be honest, I really don't care about the transparency issues).

Edit: fixed something with the quotes.

I do because I like transparency and the issues occur in dark mode as well just much less prominent. If there is a way to fix them then I want to use it.

 

[jackluke]

* my legacy nVidia Tesla patch and our C2D fix

In my experience, only IOUSBHostFamily.kext and IOUSBFamily.kext need to be replaced. We don't want to replace unnecessary files.

I don't think the transparency issues are due to .car files. It's due to the graphics drivers.

I'm going to try booting with the graphics patches removed and see if the transparency issues are still present. This might shed some light on it (though to be honest, I really don't care about the transparency issues).

Edit: fixed something with the quotes.

Glad you're back!
Please, you have found the C2D culprit with a clever method between more than two hundred thousand files leaving only 46 among which I found a culprit, the credit is most yours, apart this if I (and many many others) have QE/CI on Legacy Nvidia Tesla is only thanks to you, without QE/CI Mojave would be totally unusable.

Anyway I need all the 5 IOUSB*** from HS because on a supported Mac I get a KP using only the required two where I don't get any KP on MB7,1 since I use the same external SSD with Mojave on both.

I also prefer the "dark mode", so that about "light mode" was just an experiment.

If anything do some yours experiment and give a try to the infamous "light mode" translucent Finder menu bar.

 

[0403979]

Glad you're back!
Please, you have found the C2D culprit with a clever method between more than two hundred thousand files leaving only 46 among which I found a culprit, the credit is most yours, apart this if I (and many many others) have QE/CI on Legacy Nvidia Tesla is only thanks to you, without QE/CI Mojave would be totally unusable.

Anyway I need all the 5 IOUSB*** from HS because on a supported Mac I get a KP using only the required two where I don't get any KP on MB7,1 since I use the same external SSD with Mojave on both.

I also prefer the "dark mode", so that about "light mode" was just an experiment.

If anything do some yours experiment and give a try to the infamous "light mode" translucent Finder menu bar.

There are still glitches in dark mode discovered and probably a couple undiscovered.

 

[ASentientBot]

Glad you're back!
Please, you have found the C2D culprit with a clever method between more than two hundred thousand files leaving only 46 among which I found a culprit, the credit is most yours, apart this if I (and many many others) have QE/CI on Legacy Nvidia Tesla is only thanks to you, without QE/CI Mojave would be totally unusable.

Anyway I need all the 5 IOUSB*** from HS because on a supported Mac I get a KP using only the required two where I don't get any KP on MB7,1 since I use the same external SSD with Mojave on both.

I also prefer the "dark mode", so that about "light mode" was just an experiment.

If anything do some yours experiment and give a try to the infamous "light mode" translucent Finder menu bar.

Oops, I missed your point about IOUSB*.kext replacements causing KP on a supported Mac. I don't have a supported Mac so I wasn't aware of that. It's cool that you're keeping your patched system functional on both supported and unsupported systems

I can try to understand the transparency glitches but don't get your hopes up. It's a lot easier to trace a KP than a tiny graphics glitch.

 

[tn-xyz]

Here are my tests results:

Preliminary NOTE: Replacing all the CAR files from HS will stuck at boot on Mojave.


THIS IS NOT A FIX but a LITTLE STEP forward I guess:

- Into /S*/L*/CoreServices/SystemAppearance.bundle/Contents/Resources/
there are respectively:

20 .CAR files in High Sierra 10.13.6
25 .CAR files in Mojave beta (the 5 more are needed for the dark mode)

I noticed that replacing only SystemAppearance.car from HS will fix some Finder greyed windows/folders but will NOT fix the greyed Menu bar!
(A BIT EVEN BETTER if you use IOAccelerator from Mojave beta 1)

Instead if you want to achieve a similar HighSierra Look Style you will need to replace all these:
SystemAppearance.car
Assets.car
VibrantLightAppearance.car
GraphiteAppearance.car


But I repeat this Will NOT fix the Finder greyed menu bar, but instead should give some missing transparencies in Mojave "light mode".

Even if you replace from HS (leaving the others Mojave .CAR untouched):
/S*/L*/CoreServices/SystemAppearance.bundle/Contents/MacOS/SystemAppearance
it will still work.

Maybe another mixing-combination of .CAR files could achieve the Menu Bar transparency, for now I cannot test further.

EDIT:
Before trying any attempt do a backup/copy of yours stock/untouched SystemAppearance.bundle

EDIT2:
IT seems that you can replace ALL the .CAR files from HS and Mojave will still Boot EXCEPT THESE:
Accessibility***.CAR
They Must be from Mojave Untouched, all the others are REPLACEABLE, even dark mode will still work with lets say an High Sierra Theme style.

wow, thank you for your hard work.
i'm curious to see where this will lead us.

 

[0403979]

Oops, I missed your point about IOUSB*.kext replacements causing KP on a supported Mac. I don't have a supported Mac so I wasn't aware of that. It's cool that you're keeping your patched system functional on both supported and unsupported systems

I can try to understand the transparency glitches but don't get your hopes up. It's a lot easier to trace a KP than a tiny graphics glitch.

I will forever appreciate your tracement of them both.

 

[TimothyR734]

I wonder if there is a way to modify dirextX 11-12 and directx shader to work in macOS both were required in windows 7 for transparency

 

[jackluke]

wow, thank you for your hard work.
i'm curious to see where this will lead us.

Lets call it another kind of workaround for Mojave "light mode" instead using "increase contrast/Reduce Transparency", cause even in menu bar the highlighted elements seems more readable.

Moreover if you replaced the main .CAR files from your High Sierra, in Mojave opening Finder and enabling from "View" tab "Show Path Bar" you will notice a little translucency working even in the Finder. While in Safari 12 and Notification Center I would say the translucency is almost perfect in "light mode".

edit:
I have attempt also in doing a hybrid/reducetransparency, I mean aiming the "reduce transparency" only to the Finder menu bar, keeping the dock translucent, but I can't find exactly which "Accessibility" console feature disable the transparency, probably it's a plist pointing to some other unix exec.

 

[tn-xyz]

Lets call it another kind of workaround for Mojave "light mode" instead using "increase contrast/Reduce Transparency", cause even in menu bar the highlighted elements seems more readable.

Moreover if you replaced the main .CAR files from your High Sierra, in Mojave opening Finder and enabling from "View" tab "Show Path Bar" you will notice a little translucency working even in the Finder. While in Safari 12 and Notification Center I would say the translucency is almost perfect in "light mode".

i suppose even the workaround might be very well acceptable for a majority of users on unsupported macs.
but since dark mode does nothing for me (imagine working and then opening a plain white page in safari; it's like eye cancer), i hope we get to the bottom of this issue.

 

[TimothyR734]

So far not. I’ve gone as far as logging the full xml during a system update from dp4. Am peeling through it but nothing jumps out at me. The software update patch should still work. I’m sure others are working on this too.

no luck on my end when I successfully updated to DB 5 it was on my internal HDD on my iMac 9,1 since my hdd in my iMac 8,1 went belly up (internal HDD) I had PB3 installed on the external usb I am using it now on my 9,1 I tried to update to DB5 no luck and with 3 versions of the Mojave Patcher no luck so maybe the only some machine can get beta 5 is on the internal hdd/ssd

 

[ASentientBot]

I wonder if there is a way to modify dirextX 11-12 and directx shader to work in macOS both were required in windows 7 for transparency

Nope. Bringing over anything from Windows to macOS will be borderline impossible as the two systems are totally different internally.

 

[jackluke]

Nope. Bringing over anything from Windows to macOS will be borderline impossible as the two systems are totally different internally.

I think TimothyR734 was referring to following a similar procedure adopted in Windows, or from Windows flashing the firmware of the GPU, but of course in unix environment is another story.

Anyway to those interested, these are the new 5 .CAR files used for "dark mode" in Mojave:

GraphiteDarkAquaAppearance
DarkAquaAppearance
AccessibilityGraphiteDarkAquaAppearance
AccessibilityDarkAquaAppearance
AccessibilitySystemAppearance

I've done a very weird experiment and it has partially worked, I've renamed the possibly .CAR files used for the "dark mode" into those used for "light mode" and viceversa, to cheat the system making believe that selecting the "dark mode" instead is a "light mode", cause GPU acceleration and translucency work fine in "dark mode", maybe the "light mode" renamed in "dark mode" can point better to OpenGL translucency, it's not simple, I've obtained an hybrid dark/light mode, but I have annoyance to the eyes, so for now I drop.

edit:
I need to understand/discover the terminal console command used in High Sierra (also present from El Capitan) when is enabled/disabled in System Preferences the "pre-darkmode" feature "Use dark menu bar and Dock".

edit2:
Found: sudo defaults write /Library/Preferences/.GlobalPreferences.plist _HIEnableThemeSwitchHotKey -bool true

 

[pkouame]

no luck on my end when I successfully updated to DB 5 it was on my internal HDD on my iMac 9,1 since my hdd in my iMac 8,1 went belly up (internal HDD) I had PB3 installed on the external usb I am using it now on my 9,1 I tried to update to DB5 no luck and with 3 versions of the Mojave Patcher no luck so maybe the only some machine can get beta 5 is on the internal hdd/ssd

Interesting tidbit. There are some volume checks in Apple's xml script. My attempts have purely been on internal HD.

Nope. Bringing over anything from Windows to macOS will be borderline impossible as the two systems are totally different internally.

Yes - that's what metal shaders are for.

 

[TimothyR734]

Interesting tidbit. There are some volume checks in Apple's xml script. My attempts have purely been on internal HD.

Yes - that's what metal shaders are for.

with beta 2 I had the same issue cold install on a external usb hdd that's why I tried on my internal hdd in my iMac 9.1 it installed no issues and I haven't done a clean install since all done by the software update and here is another interesting tidbit on my external usb hdd which has Mojave beta 3 had a update in the App Store for safari technology preview version 62 rebooted back into my internal hdd Mojave beta5 checked the App Store all apps updated but safari technology is version 61 weird

 

[Sevenfeet]

My Mac Mini 4,1 is now running Mojave PB4. I first tried just installing over the previous version (PB2) since my Mac Mini was nominally serving in a production capacity (Roon music endpoint) but it didn't work. Upon boot and doing the post-install patch, it would get through most of the boot and either reboot or kernel panic and reboot. Doing a clean install worked nicely.