Make sure the disk is at least 16gb. Try another one too
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
Not sure what you missed or doing wrong. Just did the same procedures ~ (1) installed mojave final release using dosdude1's patch app (2) made sure my mac was under developer or public beta (3) updated via System Preferences | Software Update (4) and did the OTA update. Wasn't necessary to re-patch.
Let me qualify this. My update did NOT work with my MBP 2009, but DID work on MBAir 2011. Both are mojave unsupported macs. Good luck.
I guess if you had one you could give a great contribute, here is a quick list, just CMD+F for "Radeon HD 5" and "Radeon HD 6": https://support.apple.com/en-us/HT202823
depends if you prefer a desktop or laptop, however with those indicted GPUs the cheapest you can find nowadays are:
Mac Pro (Mid 2010)
Mac mini (Mid 2011) only the model with AMD Radeon HD 6630 (not with IntelHD3000)
MacBook Pro (15-inch, Early 2011) available only with i7 cpu
iMac (21-inch, Mid 2010) only the model with i3 cpu at 3,2GHz and ATI Radeon HD 5670
all the iMacs 2011 contain an "ATI/AMD Radeon HD 6xxx"
edit:
Anyway me too, I don't own any mac with ATI/AMD GPU, so can't do my usual non-clever tests.
Last edited:
Just for the record - anyone else having problems with 'Mail/Bundles' folder? If I create on a fresh install an empty folder called 'Bundles' for MailPlugins. The GUI won't start anymore. And yes, really an empty folder - not an unsupported plugin.
On my unsupported Mac mini 2011 all seems fine. But something strange has happened on my supported MBP 2015. On that machine ~/Library/Mail is now owned by root and I can't see inside, even with sudo and even though its permissions show as 777. The plugins show up in `Prefs > General > Manage Plug-ins… `, but I can't delete those that don't work under Mojave. I know this is not a thread for Macs that are officially supported, but still it shows that strange things can happen. Since installing Mojave the MBP has developed a few other glitches that do not appear on the Mac mini, which runs more or less identical apps.
I used intel dev emulator. Ran it globally in the terminal. Was able to the AMD using kextload or kextutil. No crashes. Tried restarting the window server. No luck. Obviously when they are loaded is the issue. I was able to verify that they were loaded. Just going from memory here. To do this I moved the ssee4.2 out of my system so u could boot with the AMD card.
If Intel’s dev emulator can be loaded at boot a startup script could load the kexts.
Hey everyone! First of all great work on the patcher 
My MacBook 8,1 just received a new Bluetooth legacy update via Patch updater and after installing it, the Bluetooth that was working fine, just can’t connect with my headphone anymore. It confirms the connection but after some seconds it disconnects and the sound don’t go to to it all. Any way to revert to the old Bluetooth patch or something like that?
Thank you!
My MacBook 8,1 just received a new Bluetooth legacy update via Patch updater and after installing it, the Bluetooth that was working fine, just can’t connect with my headphone anymore. It confirms the connection but after some seconds it disconnects and the sound don’t go to to it all. Any way to revert to the old Bluetooth patch or something like that?
Thank you!
Y
Yes, just replace Bluetooth kexts from the ones on the original USB patch installerHey everyone! First of all great work on the patcher
My MacBook 8,1 just received a new Bluetooth legacy update via Patch updater and after installing it, the Bluetooth that was working fine, just can’t connect with my headphone anymore. It confirms the connection but after some seconds it disconnects and the sound don’t go to to it all. Any way to revert to the old Bluetooth patch or something like that?
Thank you!
@dosdude1
I installed mojave on my MBP 8,2 with your patcher.
Everything works finde but I can't adjust the screen brightness, the MB doesn't sleep if I close it and going into sleep-mode wakes the MB immediately up but the screen stays off.
I disabled the ATI in single-user-mode and installed your patch-program under Mojave again.
Is there any solution?
I installed mojave on my MBP 8,2 with your patcher.
Everything works finde but I can't adjust the screen brightness, the MB doesn't sleep if I close it and going into sleep-mode wakes the MB immediately up but the screen stays off.
I disabled the ATI in single-user-mode and installed your patch-program under Mojave again.
Is there any solution?
Is there any tutorial how to do this here?
You need these kext "IOBluetoothFamily.kext" and "IOBluetoothHIDDriver.kext" get them from /System/Library/Extensions/ inside the USB macOS Installer, then replace the ones inside your Mojave /S/L/E/ after you have to launch Terminal and fix permissions:
sudo chmod -R 755 /S*/L*/E*
sudo chown -R 0:0 /S*/L*/E*
sudo kextcache -i /
sudo reboot
edit:
Even if getting them from the USB macOS Installer could work, they result smaller in size, then incomplete, so better take them from a clean Mojave Installation or late HighSierra.
Last edited:
Lately, I have had a problem with my WiFi, on and off. Whenever I stop using my MBP4,1 (late 2008, 17"), and it goes into sleep for about 2 to 3 hours, the WiFi has to be restarted before it will work again. The problem has been there since (I think) High Sierra 10.13.6. I (tried to) search the forum for similar reports, but I didn't find any - or perhaps I didn't use the correct search parameters. Has anyone reported such a problem? It is intermittent, and only happens if it has been asleep (but not switched off) for a long period. Once the Wi-Fi is restarted, everything is fine - it HAS to be restarted, because if not, despite showing connectivity, it will not accept the password, and so needs a restart (not a reboot). It is not a big problem, as I just make sure I use the MBP every hour or so. The card is the Broadcom BCM 94322 and had not given any problems before. Anyone had a similar glitch?
Those who wish to use Wi-Fi on their patched macOS Mojave installers, please read the above post.
Anyone have the issue when switching back from dark mode to light mode that the menu bars stay dark?
Hi, I have the same machine, so I can tell you this method works great. Dosdude1's gpu disabler did the same thing you described to my machine, but this method allowed it to have the GPU power management and backlight control again. Be aware that this disables the AMD GPU, so there will be no external monitor support and all of the graphical anomalies (such as the gray menu bar in light mode) will be present with the Intel HD 3000. My machine does have full acceleration and is still able to play x265 1080p video with no dropped frames, but don't expect to be playing any video games with the Intel HD 3000 as your main GPU.
This guide assumes you still have the AMDRadeonX3000.kext in the default /System/Library/Extensions/ location. If it is not there, you need to move it back before starting this procedure. I did not create this method, but I have been using it since Sierra (when my GPU died for the second time) with no problems.
Here is the guide, pasted in full from my post almost 200 pages ago:
"#####__ The Guide __#####
This guide assumes that you run a stock system. Problem just occured. That means:
This guide assumes that all kexts are still in their default location /System/Library/Extensions.
Having all AMD-kexts there except one is beneficial for 'proper' operation.
To get some display acceleration back it will be necessary to force the machine to not boot into discrete graphics (dGPU) but directly into integrated graphics (iGPU). This will give you back your laptop – but you will lose some features: e.g. the ability to drive an external display. Thunderbolt data connections should work.
The initial procedure:
– To start from a clean slate: reset SMC and PRAM/NVRAM:
shutdown, unplug everything except power, now hold
<leftShift>+<Ctrl>+<Opt>+<Power>
release at the same time;
– Now power on again and hold
<Cmd>+<Opt>+<p>+<r>
at the same time until you hear the startup chime two times.
– Boot into Recovery by holding
<Cmd>+<r>+<s>
– Disable SIP:
csrutil disable
– disable dGPU on boot
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
– enable verbose boot mode:
nvram boot-args="-v"
– reboot into single user-mode by holding
<Cmd>+<s>
on boot
– mount root partition writeable
/sbin/mount -uw /
– make a kext-backup directory
mkdir -p /System/Library/Extensions-off
– only move ONE offending kext out of the way:
mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/
– let the system update its kextcache:
touch /System/Library/Extensions/
– wait for the kextcache process to finish
then
reboot
Reboot normally:
you will have an accelerated iGPU display.
But the system doesn't know how to power-management the failed AMD-chip.
For that you have to either manaully load the kext after boot by:
sudo kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
Automate this with the following LoginHook:
sudo mkdir -p /Library/LoginHook
sudo nano /Library/LoginHook/LoadX3000.sh
with the following content:
#!/bin/bash
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
exit 0
then make it executable and active:
sudo chmod a+x /Library/LoginHook/LoadX3000.sh
sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHook/LoadX3000.sh
Preventive measures for future use
There are two further caveats to know: This is reversible when the SMC/PRAM/NVRAM is reset. If that happens the GPU-power-pref nvram can/has to be set again to force the use of the iGPU from boot-time.
Since this can happen quite easily (and is often erroneously recommended way too many times than it is actually useful), you should probably prepare for such a scenario and create a simple script to greatly speed up the process and also make entering the necessary variable much less error prone:
sudo nano /force-iGPU-boot.sh
– Enter the following content to this file:
#/bin/sh
sudo nvram boot-args="-v"
sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
exit 0
– Now make that executable:
sudo chmod a+x /force-iGPU-boot.sh
In the future, when the SMC/PRAM/NVRAM gets reset to default values it is now possible to boot into SingleUser with:
<Cmd>+<s>
– And after mounting your boot-volume read-write to execute just:
sh /force-iGPU-boot.sh
This setup has now one kext in a place Apple's installers do not expect. That is why in this guide SIP has not been reenabled. If an update that contains changes to the AMD drivers is about to take place it is advisable to move back the AMDRadeonX3000.kext to its default location before the update process. Otherwise the updater writes at least another kext of a different version to its default location or at worst you end up with an undefined state of partially non-matching drivers.
After any system update the folder /System/Library/Extensions has to be checked for the offending kext. Its presence there will lead to e.g. a boot hang on Yosemite and Sierra, an overheating boot-loop in High Sierra.
Further: this laptop is overheating, no matter what you do. The cooling system is inadequate and the huge number of failing AMD chips are just proof of that.
To prolong the life of this now hacked machine it is advisable to abstain from really heavy lifting over prolonged stretches of time. Strictly follow the usual recommendations for laptops: use on hard surfaces, keep the fans and fins inside it clean. Using any fancontrol software with relatively aggressive settings should also help: like smcFanControl, MacsFanControl, or TGPro (the latter both commercial).
This is fairly complete and what I do recommend to everyone asking me.
Nevertheless. We're not done here, yet. Improvements are welcome. Share them!"
The best thing you can do to disable the dGPU on these systems is outlined in my post here. This is a permanent solution, and doesn't rely on NVRAM variables that could get erased, and doesn't require deleting any kexts from Mac OS.
That's true, but I don't have the nerve to try a modification that requires precise soldering. The method I posted doesn't actually delete any kexts and is fully reversible. A combination of using your legacy video card patch in the patcher and that manual method has actually been a better experience for me in Mojave than any previous OS because updates don't replace the AMDRadeonX3000.kext. I just didn't re-run the Legacy Video Card Patch when updating from the beta to the final build.
Is there a reason you can't do as I suggested and load the SSE4.2 emulator and the kexts in single user mode? That would solve the timing issue, at least for testing. Then a startup script could be made to do that, if it works.
To those who use Mojave on APFS file system, I have managed to "fix" the APFS Recovery Volume to make it bootable with CMD+R and mainly with USB input devices responsive, working wifi and everything else, just follow next steps, boot from a Mojave APFS Volume, launch Terminal and type:
diskutil apfs list
{locate your "APFS Recovery Volume" diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]}
diskutil mount diskXs3
open /Volumes/Recovery
landing on Finder, double tap on the "random-numbers-letters" folder, once inside rename these files:
prelinkedkernel into prelinkedkernelbackup
immutablekernel into immutablekernelbackup
PlatformSupport.plist into PlatformSupportbackup
Don't close Finder yet, once you renamed those 3 files, press CMD+N, then from this new Finder Window press CMD+SHIFT+G (or use "Go to Folder"): /System/Library/PrelinkedKernels/
while inside this path copy the file prelinkedkernel into the previous Finder Window, exactly were you renamed those 3 files, lastly rename this fresh copied file from prelinkedkernel to immutablekernel
Now you have a working APFS Recovery Volume.
edit:
On APFS scheme the "APFS Recovery Volume" is always on the 3rd (hidden) partition.
diskutil apfs list
{locate your "APFS Recovery Volume" diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]}
diskutil mount diskXs3
open /Volumes/Recovery
landing on Finder, double tap on the "random-numbers-letters" folder, once inside rename these files:
prelinkedkernel into prelinkedkernelbackup
immutablekernel into immutablekernelbackup
PlatformSupport.plist into PlatformSupportbackup
Don't close Finder yet, once you renamed those 3 files, press CMD+N, then from this new Finder Window press CMD+SHIFT+G (or use "Go to Folder"): /System/Library/PrelinkedKernels/
while inside this path copy the file prelinkedkernel into the previous Finder Window, exactly were you renamed those 3 files, lastly rename this fresh copied file from prelinkedkernel to immutablekernel
Now you have a working APFS Recovery Volume.
edit:
On APFS scheme the "APFS Recovery Volume" is always on the 3rd (hidden) partition.
Last edited:
pkouame is working on a definitive solution, meanwhile you can either use reduce transparency in system preferences, or use my interim solution.
is to use combination keys to enter and exit the dark mode.
when it exits the dark mode, it applies the reduction of transparency in the light mode menus, when it turns on the dark mode, it removes the transparency reduction.
The detail of this workaround is that you need to restart any application that is open for it to be applied.
ModoEscuro (DarkMode)
@dosdude1
last bluetooth patch kill bluetooth on my Mac mini Server (Mid 2011)
AT this time, no way recovering IOBuletooth ext from USB install disk
last bluetooth patch kill bluetooth on my Mac mini Server (Mid 2011)
AT this time, no way recovering IOBuletooth ext from USB install disk
This has been fixed, just install the latest update to the patch.