You might also have a look at Dosdude1's page:
dosdude1's Personal Web Server - Resources
dosdude1.com
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
Thanks a lot. I have done everything that he says on his webpage concerning my laptop, 8,2 on Mojave concerning sleep, etc. Nothing works. If the machine sleeps, I must force restart, nothing else works.
Can I use a Mojave Time Machine backup made on an unsupported device to move the installation onto a new supported MacBook, without any problems?
Upgrade to a new MacBook.
Upgrade to a new MacBook.
You should only restore user files and settings and avoid any system files (the old system has been patched and will not work properly on the new supported system) and check apps in advance, see below.
In case you are crossing the 64bit boarder using Catalina or later I would strongly recommend to avoid restoring applications, some of them may simply do not work any longer. Just migrate your user data in and install applications from the scratch.
Without any problems? This is the land of unsupported, i.e. self supported macs.
Hi together.
Because I was missing the Bootrom Update (and my iMac10,1 supports HightSierra natively) and I didn't know how to install it without an OS (I had already erased the SSD for a clean install) I had to install Mojave as MacOS journaled and couldn't use APFS. So I will have a backdraw:
"Using APFS is REQUIRED in Mojave in order to receive system updates via the normal Software Update method. If you choose to continue using macOS Extended (Journaled) as your filesystem type, you will NOT receive System Updates via System Preferences."
I will seemingly need to update manually instead of letting it happen automatically. But how do I do it manually? (in sys. preferences it proposes for me to install BigSur.. which obviously wont work..)
Best,
Because I was missing the Bootrom Update (and my iMac10,1 supports HightSierra natively) and I didn't know how to install it without an OS (I had already erased the SSD for a clean install) I had to install Mojave as MacOS journaled and couldn't use APFS. So I will have a backdraw:
"Using APFS is REQUIRED in Mojave in order to receive system updates via the normal Software Update method. If you choose to continue using macOS Extended (Journaled) as your filesystem type, you will NOT receive System Updates via System Preferences."
I will seemingly need to update manually instead of letting it happen automatically. But how do I do it manually? (in sys. preferences it proposes for me to install BigSur.. which obviously wont work..)
Best,
You need to install High Sierra and all updates. Within one of these updates the firmware update will be applied. You have to install onto your internal disk.
You may just download the dosdude1 High Sierra patcher and use this tool only to download and create an unpatched High Sierra USB installer (this is only one way to get the installer, there are several other options, searching the net is much more effective than posting here).
I once had the Mac updated to the latest update possible so it should have been on it already. Didnt work anyways.
I thought it has to do with the fact that the HDD, where Sierra and the update was on, was exchanged to an SSD. So how would the Computer know this High Sierra Bootromupdate was ever installed? Does it install to any other Hardware besides the HDD? Because even if I used the same HDD.. Before I install the new unsupported Mojave, I have to format it to APFS.. which also erased any info.. How would that Computer know the update was ever installed?
Anyhow. This is not my question anymore. It is now extended journaled an thats ok. I just need to know how to get the firmware security update which are still to come to Mojave. Since without APFS they wont update automatically. How do I do it mannually?
There are macOS tools able to read the firmware version. Running the updates these tools are used, the firmware updates are staged to the internal EFI and on the next reboot it should run and apply the updates. This does not work in any case and on the first attempt, just retry. You may check the EFI partitions for an APPLE folder containing the firmware.scap files for updates. I could update all my iMac11,x and iMac12,x systems.
Your machine will not get any firmware updates from Mojave, it was never supported to run with Mojave. Why should apple bundle software for unsupported macs into macOS updates?
You need to go back to High Sierra, or the latest supported macOS version in general to get the firmware updates and APFS support.
Last edited:
It is installed to the so called "boot ROM". The "boot ROM" is a small flash memory on the main board - something like a very small SSD.
The boot ROM contents is what is loaded and executed immediately after powering up. The software stored in the boot ROM will then try to find something bootable on some attached drive or might even try to connect to the internet for recovery.
Well someone once told me Mojave doesn't get any real updates anymore (since there are newer MacOSs) but machines that dont run newer versions than Mojave are not yet obsolete and still get security updates. I think that is what they mean with the quote of Dosdude on his homepage, I requote:
"Using APFS is REQUIRED in Mojave in order to receive system updates via the normal Software Update method. If you choose to continue using macOS Extended (Journaled) as your filesystem type, you will NOT receive System Updates via System Preferences."
ahh thanks now I get it.
I revived my MacBook Air mid 2011 running High Sierra and DOSDude's Mojave. Both are running well.
I would love to turn SIP back on. As a developer, i have KEXT signing privileges from Apple. I can only use it for our products for distribution but could sign other things for personal use.
Is there a list of patched KEXTs and Frameworks from DosDude? It would save time to get the system straight.
I would love to turn SIP back on. As a developer, i have KEXT signing privileges from Apple. I can only use it for our products for distribution but could sign other things for personal use.
Is there a list of patched KEXTs and Frameworks from DosDude? It would save time to get the system straight.
You can get the source code for the Catalina patcher. The Mojave and High Sierra patchers are probably similar.
You can download all the patches and examine them manually.
Each patch usually has two versions. One in the Objective C code (patcher) and one as a bash script (downloads).
But some patches only exist in one of those.
Code:
#=========================================================================================
# Download source code
git clone https://github.com/dosdude1/macos-catalina-patcher.git
#=========================================================================================
# Download patches
for theos in highsierra mojave catalina; do
curl -s "http://dosdude1.com/${theos}/patchupdates/updates.plist" > ${theos}updates.plist
[[ -d ${theos}updatepatches ]] || mkdir ${theos}updatepatches
for theurl in $(plutil -p ${theos}updates.plist | sed -nE '/^ +"patchURL" => "(.*)"$/s//\1/p'); do
echo $theurl
thezip="${theurl##*/}"
thefile="${thezip%.zip}"
[[ -d $thefile ]] || mkdir "${theos}updatepatches/$thefile"
curl -s "$theurl" > "${theos}updatepatches/$thefile/$thezip"
open "${theos}updatepatches/$thefile/$thezip"
done
done
#=========================================================================================
# Currently installed updates:
bbedit /Library/Application\ Support/macOS\ Mojave\ Patcher/installedPatches.plist
bbedit /Library/Application\ Support/High\ Sierra\ Patcher/installedPatches.plist
bbedit /Library/Application\ Support/macOS\ Catalina\ Patcher/installedPatches.plist
This is an interesting idea. As far as I know frameworks are straight from Apple and should not need any extra signatures.
You might be able to see unsigned kexts when manually rebuilding prelinked kernel:
sudo kextcache -system-prelinked-kernel
Mojave is definitely and completely out of support - no further updates to be expected, although exceptionally some extraorbitantly critical hot fix might occur.
It is not quite clear to me what your question is. As previously pointed out, Mojave is not receiving further updates as of now. Depending on your system, you can install High Sierra to get the firmware update required to run on APFS. DOSDude's installer also has an EFI driver that allows running APFS on older systems. But if you can use High Sierra to install the firmware update, it's a better solution.
Duh - should have thought of that. Thanks!
--> worked my way through and was able to patch a couple of KEXTs and their plugins, mainly LegacyUSBInjector and AppleHDA. I parked the SIPManager and rebuilt the kext cache. After double-checking the PlatformSupport.plist I did an NVRAM reset (clearing SIP disabled and boot-args) and was able to boot fine with everything intact.
==> must have missed an audio component. No sound - AppleHDA. Will have to find the responsible piece not loading. Meanwhile SIP is back off. I wonder whether the High Sierra version works.
Last edited:
AppleHDA kext is straight from the High Sierra as far as I know.
Not true i get updates for Mojave every few weeks still. Just run SilentKnight and install whats available √
Security Updates is EXACTLY what SilentKnight updates amongst other things √
Please enlighten us which security updates have been silently published only available using this tool within the last 5 months since July, 21st - this was the day Apple released the last Mojave security update. Government, big universities , companies have phased out macOS Mojave support. Just search the net.
Catalina got in September another security update…
EDIT: Mojave got no in September or later.
Last edited:
October 25th, to be correct (19H1519). More to come for another year, probably.
Have you tried this command to restore audio?:
sudo kill -9 `ps ax|grep 'coreaudio[a-z]' | awk '{print $1}'`