My understanding is that you have to leave SIP off because it breaks the ability of the patched software from loading because it won't be signed anymore. Nature of the beast.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
My understanding is that you have to leave SIP off because it breaks the ability of the patched software from loading because it won't be signed anymore. Nature of the beast.
Got a couple of notes on the 3 items listed above.
Running a MacBook Pro 5,2 -> these remedies would work on other models too!
This is not a full fix by all means, but for some dudes having issues with the light mode, you could "fix" this following the instructions listed here, which will get the Dock, Finder and menu bar into Dark mode. This is better than the weird parking grey menu.
Launch Terminal (located in /Applications/Utilities) and enter the following command:
sudo defaults write -g NSRequiresAquaSystemAppearance -bool Yes
Then logout or restart. Switch to Light mode. Only the "weird darkish mode" will be changed by black mode.
-> This is an excerpt from :
https://www.tekrevue.com/tip/only-dark-menu-bar-dock-mojave/
Mainly, whoever wants a Light Mode can have it working 99%, only the dock and top bar will be blank, but not “weird darkish grey”.
I currently prefer this modeto fully white or black and is better than the weird one.
I think this was sorted with the macOS Mojave Patcher 1.2.2, but in any case the above can be preferable to some users.
I got that model.
It works OK for me. You might want to do a PRAM/NVRAM reset if the track pad is not detected at all.
Proof:
The following patch would apply to any machine with issues with the iSight camera... if you also have installed Virtual Box (currently 5.2.18 but I presume all versions will break iSight).
I noticed that after a clean install the builtin isight camera didi work ok, but stopped after a while. Looking around I found that uninstalling VirtualBox does bring the camera back to life!
How to get both working ? Well, it looks VirtualBox has a kext that breaks the camera.
Found a way to partially disable that kext, but keeping the camera and Virtualbox working at the same time. This unobtrusibe and clean touch/fix will get broken if you install a newer version of Virtualbox and you'd have to do the changes to the file again.
See highlighted the commented lines on the Virtual Box file, then restart your machine and enjoy the Camera and VirtualBox.
File to patch:
"/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh"
Look for the section below
ConsoleMessage "Loading ${VBOXUSB}.kext"
Enter comments to the kextload section.:
#if ! kextload -d "/Library/Application Support/VirtualBox/${VBOXDRV}.kext" "/Library/Application Support/VirtualBox/${VBOXUSB}.kext"; then
# ConsoleMessage "Error: Failed to load /Library/Application Support/VirtualBox/${VBOXUSB}.kext"
# VBOX_RC=1
#fi
Hope this helps somebody out there
Perhaps dosdude1 could update his main documentation with some notes re this fixes if found helpful or relevant. i.e. iSight "hit & miss" will definitely not work if VirtualBox installed.
Thanks for this development, it has renewed my MBP 5,2 and works much better with 10.14 vs the last "supported" 10.11 !!!
Hope this helps somebody out there!
Just updated VBOX from 5.2.18 to 5.2.22 and the same issue happens as the patched file gets overwritten.
Same suggested patch above solves the issue and FaceTime and Camera work again after the edit and restart the computer.
I have an external monitor connected to my MacBook Pro 13' late 2011 when I boot my Mac up the display does not activate (stay dark), I have to unplug then plug the display cable so it works.
(it wasn't doing that in High Sierra it was opening with the log screen as the Mac screen)
I wonder if someone can help me regarding this, or if someone having the same issue.
Thanks!
(it wasn't doing that in High Sierra it was opening with the log screen as the Mac screen)
I wonder if someone can help me regarding this, or if someone having the same issue.
Thanks
!
ah cool, thanks for the tip. and glad to hear others have it working. I'll give ONYX a shot.
(I would have tried re-installing iTunes, but Apple has not yet released a stand-alone iTune installer for Mojave, just has the previous version available or download.
I'm using the same card in a Mac Pro 3.1. It actually won't work in Mojave. But you can do something. Read more here ...
To remove NightShift patch and get rid of "keyboard, trackpad, and mouse preference panes issues" you have to use the untouched framework from a clean Mojave installation from this path: /System/Library/PrivateFrameworks/CoreBrightness.framework
just copy and replace manually from Finder, as far I know frameworks don't need permissions fixing, they only must be ad-hoc signed, and taking them from a clean installation are already correctly signed, while if they are patched, disabling SIP they will be accepted even with an invalid signature. So they will work anyway.
Last edited:
Any chance the Brightness (F1 and F2) buttons functionality can be reactivated in the next DosDude Mojave patcher?
Honestly it is the only patched Mojave anomaly on my Early 2008 17" Core 2 Duo 2.6Ghz MacBook Pro besides the WiFi card being unsupported (supported card coming from eBay for $10). Mojave Patcher is absolutely brilliant !!!
Honestly it is the only patched Mojave anomaly on my Early 2008 17" Core 2 Duo 2.6Ghz MacBook Pro besides the WiFi card being unsupported (supported card coming from eBay for $10). Mojave Patcher is absolutely brilliant !!!
Perhaps it's something else. I have a MBP4,1 also, from early 2008, and F1/F2 both function properly.
Files with .tbd extension
For those using patched frameworks (such as CoreBrightness, CoreUI, HIToolbox ...) anyone know the purpose of the copy files that has extension .tbd, such as CoreBrightness.tbd?
Thanks.
For those using patched frameworks (such as CoreBrightness, CoreUI, HIToolbox ...) anyone know the purpose of the copy files that has extension .tbd, such as CoreBrightness.tbd?
Thanks.
These files are for Apple validation, I usually delete them when I apply manually, but if it works for you, do not touch them.
They are explained very well here: https://fileinfo.com/extension/tbd
Just read the Mac related one, in few words this file.tbd is definitely not needed when using a binary compiled file (unix executable), but only during the developing time.
Is it possible to use transparency ... in Mojave for the AMD 5870 ?
I know that the GPUs isn't metal compatible, but perhaps there is a chance to use the "normal" desktops effects?
I know that the GPUs isn't metal compatible, but perhaps there is a chance to use the "normal" desktops effects?
I have... TWICE
Upon Startup the brightness dims to ~ 50%... and tapping the F1 "dim" or F2 "brighten" keys don't change the brightness even though the brightness pop up appears.
Any other ideas?
Thanks! Thats' what I'm using now... but it doesn't restore the functionality of the F1 "dim" and the F2 "brighten" keys even though the brightness pop up appears.
Would installing DyingLight restore these brightness keys? https://computeco.de/DyingLight.html
No, that is for 2011 15"/17" machines that have had their dedicated GPU permanently disabled via hardware. Which 4,1 do you have, a 15" or 17" model?
17" Early 2008 Core 2 Duo 2.6Ghz MacBook Pro (model A1261) 6GB RAM 1TB SSD running Mojave 10.14.1 via DosDude's Mojave Patcher
Yeah, that one has a CCFL backlight, which seem to have weird control issues under Mojave. I'm trying to figure out a solution currently.
Awesome! Thanks for all your AMAZING work. The backlighting is a minor inconvenience easily worked around with the free Brightness Slider app https://ActProductions.net/free-apps/brightness-slider
Thank You.
[doublepost=1543381309][/doublepost]
Thank You. I believe I am using your patched CoreBrightness. So I appreciate it.
Thank you – I had no idea that was the cause of that problem on my computer. Is there any chance to update the patch to correct that problem and keep nightshift working?
Edit: replaced the CoreBrightness.framework file on my computer with one from a machine with an original High Sierra installation (right now I'm using High Sierra on an unsupported computer). The Night Shift option disappeared, as expected, but the problems with the Control Panel remain... sigh.
Last edited:
Hm, the term "impossible" seems to have degraded somewhat since the big bang ;-)
I´ll note the full path next time the msg pops up here on my machines (I saw it only twice so far on my 12 MacBooks and 1 iMac)...