Not sure about the APFS app as I have never seen this. The solution I outlined removes the software APFS efi partition that causes the scrolling text during boot up. If you have a native APFS Rom then you do not need the APFS patch.
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
I also have an iMac8,1 that has been patched to run under Mojave. WiFi did not work in the first two or three versions of the patcher, but has been stable for several months now.
WiFi information from the System Report is given below.
Software Versions:
CoreWLAN: 13.0 ((null))
CoreWLANKit: 13.0 ((null))
Menu Extra: 13.0 ((null))
System Information: 12.0 (1355)
IO80211 Family: 11.1 (1110.26)
Diagnostics: 1.0 (910)
AirPort Utility: Not Installed
Interfaces:
en3:
Card Type: AirPort Extreme (0x14E4, 0x8C)
Firmware Version: Broadcom BCM43xx 1.0 (5.10.131.36.16)
MAC Address: 00:1f:5b:c2:e0:2f
Locale: ETSI
Country Code: CH
Supported PHY Modes: 802.11 a/b/g/n
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140
Wake On Wireless: Supported
Status: Connected
The airport card is identical, but firmware version is given generically as BCM43xx.
Did you run the macOS Post Install? Have you tried re-running Patch Updater than can be found under Applications/Utilities? Did you use version 1.3.0 of the Patcher?
Hi! Thanks for your answer! To be honest, I bought a used SSD on which the owner already installed the mojave patch for me.. so I am not sure.. how can I update? Can I update via an usb flash drive?
To make this clear: The system report you posted is from your IMac8.1? And your airport is 0x14E4, 0x8C, so one which is stated not to work on the Sierra patch (dosdudes homepage:http://dosdude1.com/sierrapatch.html)
However he did not patch it on Sierra but on a later patch of Mojave? So we have the same card and it can definitely be made working? great news
To make this clear: The system report you posted is from your IMac8.1? And your airport is 0x14E4, 0x8C, so one which is stated not to work on the Sierra patch (dosdudes homepage:http://dosdude1.com/sierrapatch.html)
However he did not patch it on Sierra but on a later patch of Mojave? So we have the same card and it can definitely be made working? great news
Installing with a USB stick and Dosdude1's patcher has always worked for me. OTA updates, without a USB stick, sometimes work but often fail.Hi! Thanks for your answer! To be honest, I bought a used SSD on which the owner already installed the mojave patch for me.. so I am not sure.. how can I update? Can I update via an usb flash drive?
To make this clear: The system report you posted is from your IMac8.1? And your airport is 0x14E4, 0x8C, so one which is stated not to work on the Sierra patch (dosdudes homepage:http://dosdude1.com/sierrapatch.html)
However he did not patch it on Sierra but on a later patch of Mojave? So we have the same card and it can definitely be made working? great news
I did not install Sierra on the iMac8,1. The first unsupported release was Mojave. The early versions of the Patcher required a supported Mac to download the app. This has now been addressed and you can download the latest release of Mojave as described in http://dosdude1.com/mojave/.
Hopefully, all those using the dosdude patches have received this email? "Receipt for your donation to <obfuscation>@gmail.com" If not - GET WITH IT!
A 'supported' machine is north of $300 US.
A 'supported' machine is north of $300 US.
Last edited:
Hey iMac-Oldschool,
again Thanks for your help! I am going to follow your tips and next step is to reinstall Mojave with the newest Versions of tool and mojave. However I am new to this can please answer me the following Question concerning your last post:
You said the Airport Card is identical. Do you mean our Cards are identical? If yes, how do you see this, I'm not even sure we one min is.
I just said when go to the terminal and type what the dude said in this post I find out that is says IOName "pci14e4,4328"
and according to this link in Google I find that this Name hints at the device: BCM4321
So do we both have that one? So mine must function in Mojave?
again Thanks for your help! I am going to follow your tips and next step is to reinstall Mojave with the newest Versions of tool and mojave. However I am new to this can please answer me the following Question concerning your last post:
You said the Airport Card is identical. Do you mean our Cards are identical? If yes, how do you see this, I'm not even sure we one min is.
I just said when go to the terminal and type what the dude said in this post I find out that is says IOName "pci14e4,4328"
and according to this link in Google I find that this Name hints at the device: BCM4321
So do we both have that one? So mine must function in Mojave?
Hi guys, I've had my MBP4,1 15-inch fixed (the old 17-inch monster was binned, cracked screen etc... pity). Long story short - it was Slot 1 that was bad, and once the 2 Gb RAM in it was taken out, the laptop booted fine. (Guy here in Accra charged me an arm and a leg to KNOW what to fix, but I am not complaining - much). It now has only 4Gb RAM on the second slot, but it works. I used @dosdude1's 1.3.3 patcher, and apart from making sure the date was correct, everything was OK. I do have a second Catalina-capable laptop (MBP9,1) and that is running Catalina, so I'm OK. But I am glad to be back here, running Mojave on the MBP4,1. So, why am I writing? Because I want to 'push the envelope' so to speak, to see if I should try to make the laptop run Catalina. I've been lurking on both fora for some time now. My laptops don't do any serious work, so it's just for the 'yes it CAN' feeling, as I run MXLinux and Windows 10 in VirtualBox on the MBP9,1.. Is 4Gb RAM sufficient on an MBP4,1 to run Catalina? I know about all the caveats... just asking. Thanks guys.
Last edited:
Got a little problem booting the Patcher (macOS Mojave Patcher 1.3.3) on a bootscreen-less Kepler GPU on Mac Pro 3.1
Got no picture from the USB installer. The installed System (10.14.6.04 18G95) will give a picture when the driver is loaded. It is alive, capslock lit when pressed, shutdown keyboard shortcut switches machine off.
USB installer works with an efi GPU, a Kepler, too (GTX680 with bootscreen)
So now, what's the difference between booting the usb patcher with 18G95 and booting the installed 18G95.
Recovery (after patching platformsupport.plist) gives no picture with bootscreen-less Kepler also.
Tried two Kepler GPUs (nvidia quadros).
Zapped nvram 4 times in a row.
Copied NvidiaGK100 kext from installed system (this with picture) to the USB Patcher System. No difference.
scratching head... and asking for some help...
or does the usb installer needs a GPU with bootscreen ?
Edit: some kind of o/t but Catalina Patcher USB Installer gives a Picture with the same Kepler GPU. So 2nd: Whats the difference loading GPU kext between Catalina and Mojave patcher for Kepler ?
Got no picture from the USB installer. The installed System (10.14.6.04 18G95) will give a picture when the driver is loaded. It is alive, capslock lit when pressed, shutdown keyboard shortcut switches machine off.
USB installer works with an efi GPU, a Kepler, too (GTX680 with bootscreen)
So now, what's the difference between booting the usb patcher with 18G95 and booting the installed 18G95.
Recovery (after patching platformsupport.plist) gives no picture with bootscreen-less Kepler also.
Tried two Kepler GPUs (nvidia quadros).
Zapped nvram 4 times in a row.
Copied NvidiaGK100 kext from installed system (this with picture) to the USB Patcher System. No difference.
scratching head... and asking for some help...
or does the usb installer needs a GPU with bootscreen ?
Edit: some kind of o/t but Catalina Patcher USB Installer gives a Picture with the same Kepler GPU. So 2nd: Whats the difference loading GPU kext between Catalina and Mojave patcher for Kepler ?
Last edited:
With 4GB of RAM your memory pressure will be in the "yellow zone" most of the time. If you can live with it than it is OK.
Hi Guys, I got this update popup earlier today, will it be okay to update or will this one screw up my Mac Pro 3.1 ?
macOS Mojave 10.14.6 Supplemental Update –– Restart Required
This update contains bug fixes that improve the stability, performance and security of your Mac, and is recommended for all users.
This update:
For more detailed information about this update, please visit: https://support.apple.com/kb/HT209149
For detailed information about the security content of this update, please visit: https://support.apple.com/kb/HT201222
macOS Mojave 10.14.6 Supplemental Update –– Restart Required
This update contains bug fixes that improve the stability, performance and security of your Mac, and is recommended for all users.
This update:
- Resolves an issue that may cause certain Mac notebooks to shut down during sleep
- Fixes an issue that may degrade performance when working with very large files
- Addresses an issue that may prevent Pages, Keynote, Numbers, iMovie and GarageBand from updating
For more detailed information about this update, please visit: https://support.apple.com/kb/HT209149
For detailed information about the security content of this update, please visit: https://support.apple.com/kb/HT201222
The best approach is to download the 10.14.6.04 full installer which contains the second supplemental update and use that to make a new patched usb installer with Mojave Patcher 1.3.3.
I successfully installed Mojave with the latest patcher on a Mac Pro 3,1 and was able to boot into it...once. All future attempts to boot into it again quickly stalled with a gray screen and Apple logo (no progress bar) until I reinstalled, at which point it again worked exactly once. I've now done this about 5 times, first with 10.14.4 and most recently with 10.14.6, but needing to spend almost an hour reinstalling the OS every time I need to restart the machine is getting tedious. Just the post-install isn't sufficient, I need to completely reinstall the OS (and then run the post-install) to regain the ability to boot into it one more time.
Has anybody else encountered this, and does anyone have a solution for it? I haven't switched to APFS yet, but have fully disabled auto software updates in System Preferences
Has anybody else encountered this, and does anyone have a solution for it? I haven't switched to APFS yet, but have fully disabled auto software updates in System Preferences
I tried the OTA update and it mostly went OK, but my MBP 6,2 refused to recognise the external display. Trying the full installer method now.
EDIT: before trying the full installer again, I zapped the PRAM (cmd-opt-P-R) and then did a Safe Boot (Hold down shift from the chime until the Apple appears). All back to normal now. Must have been a corrupted cache somewhere.
Last edited:
Yesterday night my early 2009 iMac running Mojave wanted to install an update and I allowed it, not knowing about potential boot problems. After the update my Mac did not boot anymore: it booted about 50%, then the Apple logo showed a very subtle colour change to a slightly lighter shade of grey, then the screen went black and a warning text in multiple languages appeared.
I was able to fix it by building a new USB stick with a patched Mojave version (a non-patched Mojave version does not work and shows the 'prohibited' icon after boot). After booting from the USB containing the patched Mojave version I ran a TimeMachine restore and was quickly back in business.
Only after all this I became aware of the fact that these problems are related to the version of the patcher. It may be a dumb question and it may be asked and answered before (although I was not able to find it in this forum) so here goes: how can I update Dosdude's patcher? Is it just a matter of downloading the latest version of it? How can I check the version I currently have?
I was able to fix it by building a new USB stick with a patched Mojave version (a non-patched Mojave version does not work and shows the 'prohibited' icon after boot). After booting from the USB containing the patched Mojave version I ran a TimeMachine restore and was quickly back in business.
Only after all this I became aware of the fact that these problems are related to the version of the patcher. It may be a dumb question and it may be asked and answered before (although I was not able to find it in this forum) so here goes: how can I update Dosdude's patcher? Is it just a matter of downloading the latest version of it? How can I check the version I currently have?
If you check your download folder it will show you your patcher file and the code number dmg, underneath it, ie: the latest is 1.3.3 dmg
I understand and the patcher that I now used has version 1.3.3. But when dosdude writes this on his site "If you update to 10.14.4 or later, and HAVE NOT updated your installer volume with version 1.3.0 or later of Mojave Patcher, you WILL NOT be able to get your system to boot after updating!" does he then mean that you need to have installed your OS using a patcher of version 1.3.0 or higher? Or is it just the patch utility running in Mojave that needs to be updated?
I believe the instructions are pretty clear, you pretty much answered your own question. If you can't boot Mojave how can you possibly use the "patch utility running in Mojave"?
If you know what you are doing it is actually very easy to boot to Mojave desktop without acceleration. Using a patcher is a better way though.
I made my patcher on a MacBook Pro already running Mojave I did download the latest version of Mojave with the update in, I have since installed it on my Mac Pro 3.1 that had Mojave on without the update, it took about 30 mins or so and then I rebooted and ran the patch updater as per instructions and everything is running smoothly and it tells me I am fully updated, it didn't overwrite Mojave as it left all my apps and files intact, even though I did do a Time Machine backup just in case. Hope this helps and good luck.
So this is a dumb question but, how can I know that this patcher is safe? I've followed dosdude's work for years, since before the patchers even, so it's not really a not trusting him thing. I'm just super careful with stuff like this because who knows what could be going onto the system with patched OS stuff like this. I've looked through the patcher's contents and it looks to be just the kexts and such, so it's probably fine, but I still wonder. Is there any way to verify the security of it?
Shoot, he is always around these threads or his youtube. Just ask him.
You can go by the fact that Apple did not shut down the whole patcher thing. That's because the patcher does not introduce the security holes into the system. If anything, Apple is probably more interested in more people running the latest macOS for a better overall security for all. We just run it with a reduced functionality on our unsupported Macs.
P.S. I have heard that jailbreaking of the iOS comes at the cost of introducing security holes into the system.
Hello there. I installed Mojave 10.14.3 on mid 2011 MacBook Air using patcher by DosDude. System booted successfully only after post-installation patches, but after them I see EFI shell (verbose mode?) every time and instead of standard login screen I see plane white one with all users (according to my current settings the login screen must automatically show my profile). I tried to delete all boot arguments using following command: sudo nvram boot-args="" , but
it always boot up with EFI shell and logs. How do I turn off the shell and always use "graphic" boot?
it always boot up with EFI shell and logs. How do I turn off the shell and always use "graphic" boot?
Post #17199.
Make sure that you already applied appropriate firmware updates to support APFS(if you had High Sierra installed on APFS previously, you should be good).