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
Just to clear up a couple things that I didn't see answered:
Edit: Looking at this Hackintosh stuff seems potentially useful, though. For example, WhateverGreen apparently includes patches for AMD GPUs. Has anybody looked into this? (I don't even really know the current state of Mojave on these cards, I don't have one. Maybe someone more knowledgeable can look?)
Also, interestingly, a BaseSystem (used in install disk, recovery partition) does not contain the required extensions to build a prelinkedkernel. If you try to use kextcache from there, you'll get errors. If you replace that volume's /S*/L*/E* from a full install, though, it'll succeed. But then it seems to corrupt something else (never figured that out) and the system won't boot. Moral of the story: build prelinkedkernels on full installed systems, not BaseSystems. (When I was first patching Mojave for my system, I figured out on my own, a crazy complex way of making a patched install disk like @dosdude1's patcher does. It involved rebuilding the prelinkedkernel and replacing OSInstall.mpkg from HS, deleting PlatformSupport.plist and using createinstallmedia. It was not fun. When I found this thread and learned of things such as -no_compat_check and running the patched package directly... life got a lot easier.)
Sorry for the super long post.
This will not enable Metal on unsupported hardware, it's a (outdated) kext for OpenGL acceleration and some other fixes. Since my patch already fixes nVidia Tesla acceleration, this is not necessary.
Edit: Looking at this Hackintosh stuff seems potentially useful, though. For example, WhateverGreen apparently includes patches for AMD GPUs. Has anybody looked into this? (I don't even really know the current state of Mojave on these cards, I don't have one. Maybe someone more knowledgeable can look?)
Correct me if I'm wrong, but prelinkedkernel is not hardware-specific. I have some experience rebuilding it for install disks/recovery partitions. It contains all loadable kexts in the system.
Also, interestingly, a BaseSystem (used in install disk, recovery partition) does not contain the required extensions to build a prelinkedkernel. If you try to use kextcache from there, you'll get errors. If you replace that volume's /S*/L*/E* from a full install, though, it'll succeed. But then it seems to corrupt something else (never figured that out) and the system won't boot. Moral of the story: build prelinkedkernels on full installed systems, not BaseSystems. (When I was first patching Mojave for my system, I figured out on my own, a crazy complex way of making a patched install disk like @dosdude1's patcher does. It involved rebuilding the prelinkedkernel and replacing OSInstall.mpkg from HS, deleting PlatformSupport.plist and using createinstallmedia. It was not fun. When I found this thread and learned of things such as -no_compat_check and running the patched package directly... life got a lot easier.)
For the install image, we don't need graphical acceleration, sound, wifi, etc. The only thing I can see being an issue, is USB. Does LegacyUSBInjector mess up USB on new systems? (I have not tested it, still using my old method of replacing IOUSBHostFamily.kext since it works just fine.) I don't imagine it does, so a single prelinkedkernel is probably possible. Is it not?
Sorry for the super long post.
you. An use Automator, Applescript, cron Apple calendar or a native app xcode, startup script, shell script, a combination, pick your poison. An app with settings is best, just takes a little longer to make. Night owl ain’t bad. AppleScript also has a script menu available in prefs. Automator has a good bit of options, but I am leaning towards an menuet app
[doublepost=1538198105][/doublepost]
I have an AMD card 7000 series
Just realized I was pressing the wrong thing to get to my time machine backup. Pressed option and now It comes up. Phew!
Same Mac 3,1 and same GPU but VLC 3.0.2 plays videos perfectly here.
It should be, but dosdude’s file has has issues on my device and when I made the file myself it didn’t so idk.
For what it's worth, that's not what my DLMeta.plist has. I got:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>DownloadKey</key>
<string>041-08708</string>
</dict>
</plist>
Last edited:
This is a glitch, it seems to have gotten some CloudFlare code. I'll have to update the tool to access those files outside of CloudFlare, as I recently had to implement it on my domain.
hello I used APFS rom patcher and now my MacBook does not boot anymore I reset smc and vram without result Help me please
Your machine is bricked and you’ll need to replace the EFI chip or your motherboard.
One doubt,
I have a thing that bothers me. Since El Capitan my login screen has the colors inverted. Then, when logged, all is fine. No problems. Why this happens and how to fix it? Thnx in advance.
I have a thing that bothers me. Since El Capitan my login screen has the colors inverted. Then, when logged, all is fine. No problems. Why this happens and how to fix it? Thnx in advance.
So now, should I assume I can unlock the APFS encrypted (FileValut2) with the 1.2.2 created Boot USB Installer? or I will need to test it?
That's the focus point, one method whom will work for sure is booting from your current macOS opening security & privacy prefpane you should de-encrypt before upgrade, it will take many many hours depending of the amount of your datas.
I don't think that using a custom prelinkedkernel could override a FileVault2 encryption on-the-fly, especially on a "patched" USB Mojave Installer, maybe it could from a "non-patched" USB Mojave Installer but that requires a supported mac of course, as chasing its tail.
Last edited:
Yea, had been dealing with decrypt FileVault2 for a day or 2 before getting the current one installed
If you replace the prelinkedkernel file then it should unlock in the usb.
I see, thank you. will try it after my mac completed FileVault2 encryption
Last edited:
I think is better compiling all in Apple script, you can check the dark mode status
tell application "System Events"
tell appearance preferences
set dark mode to not dark mode
set scuro to get dark mode
if scuro then
do shell script "
defaults write com.apple.universalaccess reduceTransparency -bool true;
killall Spotlight;
killall Finder;
defaults write com.apple.universalaccess reduceTransparency -bool false;
killall Dock;
killall Finder;
killall NotificationCenter;
defaults write com.apple.universalaccess reduceTransparency -bool true;
killall Spotlight;
defaults write com.apple.universalaccess reduceTransparency -bool false;
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO;"
else
do shell script "
defaults write com.apple.universalaccess reduceTransparency -bool false;
killall Finder;
killall Dock;
killall NotificationCenter;
defaults write com.apple.universalaccess reduceTransparency -bool true;
killall Finder;
killall Spotlight;
defaults write com.apple.universalaccess reduceTransparency -bool false;
killall Finder;
killall Dock;
killall NotificationCenter;
defaults write com.apple.universalaccess reduceTransparency -bool true;
killall Finder;
killall Spotlight;"
end if
end tell
end tell
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 mode
to 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.
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!