macOS 10.14 Mojave on Unsupported Macs Thread

[Hanemanma]

Hello! I am new to this and I have hit a snag. If the question has already been addressed please kindly point me the section of the thread.

The Issue:
When I attempt to create the USB boot media I get this message.

Failed Mounting failed. Please Check your MacOS Mojave Installer App then try again.

I have tried 3 USB thumb drives all above 16GB of space and various manufacturers. What step am I missing?

System Info:
Mac Mini 3,1 Intel Core 2 Duo 2.26Gz

 

[saudor]

Oh - I think you mean simply News. That works fine in .2. News+ is a new "applet" inside the News sidebar. Doesn't require a subscription (I don't have one) to see its "home' page.

ahh! that makes sense. Thanks for the clarification!

 

[franciscodavid]

Hi,

I'm running Mojave 10.14.4 on a Macbook5,1 (Late 2008) with the recommended patches. Some days ago, I started having no internal audio devices detected. Bluetooth headphones just worked fine. I have found that unloading & loading AppleHDA.kext recovered the internal audio devices and sound started to work again. However, I must reload this kext every time the system is restarted.

I hope this trick helps somebody:

sudo kextunload -v /System/Library/Extensions/AppleHDA.kext
sudo kextload -v /System/Library/Extensions/AppleHDA.kext

There is a funny thing, though. I could not load the kext without previously unloading it, which suggested the kext was previously loaded. So, I did some debug.

Loaded kext on start up:

kextstat -l | grep com.apple.driver.AppleHDA
  114    1 0xffffff7f824a7000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (282.54) 7C51B113-65CA-37EF-9736-754CA841344C <113 79 17 13 8 7 6 5 3 1>
  140    0 0xffffff7f82662000 0xb7000    0xb7000    com.apple.driver.AppleHDA (282.54) 7337AC93-3026-3BE5-93E5-70E677A74BE1 <139 114 113 108 79 17 7 6 5 3 1>

Loaded kext upon reload:

kextstat -l | grep com.apple.driver.AppleHDA
  114    1 0xffffff7f824a7000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (282.54) 7C51B113-65CA-37EF-9736-754CA841344C <113 79 17 13 8 7 6 5 3 1>
  160    0 0xffffff7f83743000 0xb7000    0xb7000    com.apple.driver.AppleHDA (281.52) 119A5EAE-5FD8-3CF3-A0CA-73EDDDC23DBE <139 114 113 108 79 17 7 6 5 3 1>
  161    0 0xffffff7f837fa000 0x2000     0x2000     com.apple.driver.AppleHDAHardwareConfigDriver (281.52) C9B1CF26-EB20-3D27-BE9E-6BD79F7F8C85 <5 3>

In conclusion, the kext loaded at startup is not the same version that the one present on the /S/L/E folder (which is the one the Patch Updater is patching). I upgraded to 10.14.4 from 10.14.3 using the Software Upgrade prefpane. I suspect the upgrade has modified the EFI partition and located there the new version, could that be possible?

Thank you.

--EDITED: PROBLEM SOLVED--

For the record, I'm using a RAID0 setting with helper boot partitions. Every time I have to apply the patches, I solve the issue by entering in single-user mode (Cmd+S at boot) and applying these commands:

/sbin/mount -uw /
kextcache -i /
reboot

 

[dosdude1]

Hi,

I'm running Mojave 10.14.4 on a Macbook5,1 (Late 2008) with the recommended patches. Some days ago, I started having no internal audio devices detected. Bluetooth headphones just worked fine. I have found that unloading & loading AppleHDA.kext recovered the internal audio devices and sound started to work again. However, I must reload this kext every time the system is restarted.

I hope this trick helps somebody:

sudo kextunload -v /System/Library/Extensions/AppleHDA.kext
sudo kextload -v /System/Library/Extensions/AppleHDA.kext

There is a funny thing, though. I could not load the kext without previously unloading it, which suggested the kext was previously loaded. So, I did some debug.

Loaded kext on start up:

kextstat -l | grep com.apple.driver.AppleHDA
  114    1 0xffffff7f824a7000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (282.54) 7C51B113-65CA-37EF-9736-754CA841344C <113 79 17 13 8 7 6 5 3 1>
  140    0 0xffffff7f82662000 0xb7000    0xb7000    com.apple.driver.AppleHDA (282.54) 7337AC93-3026-3BE5-93E5-70E677A74BE1 <139 114 113 108 79 17 7 6 5 3 1>

Loaded kext upon reload:

kextstat -l | grep com.apple.driver.AppleHDA
  114    1 0xffffff7f824a7000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (282.54) 7C51B113-65CA-37EF-9736-754CA841344C <113 79 17 13 8 7 6 5 3 1>
  160    0 0xffffff7f83743000 0xb7000    0xb7000    com.apple.driver.AppleHDA (281.52) 119A5EAE-5FD8-3CF3-A0CA-73EDDDC23DBE <139 114 113 108 79 17 7 6 5 3 1>
  161    0 0xffffff7f837fa000 0x2000     0x2000     com.apple.driver.AppleHDAHardwareConfigDriver (281.52) C9B1CF26-EB20-3D27-BE9E-6BD79F7F8C85 <5 3>

In conclusion, the kext loaded at startup is not the same version that the one present on the /S/L/E folder (which is the one the Patch Updater is patching). I upgraded to 10.14.4 from 10.14.3 using the Software Upgrade prefpane. I suspect the upgrade has modified the EFI partition and located there the new version, could that be possible?

Thank you.

Rebuild your kextcache. Either re-install the Legacy Audio Patch with Patch Updater, or just run the following in Terminal:

sudo kextcache -system-caches
sudo kextcache -system-prelinked-kernel

 

[adeuxx]

Hi folks, having an issue after installing Mojave on a freshly formatted APFS filesystem. After the install and reboot back into the USB to run the post install patcher then rebooting I’m just seeing a flashing image with a ?
I’ve tried booting back into the USB and running the patcher again, selecting to rebuild caches but still unable to boot to Mojave.
Can anybody assist please? Running a MacBookPro7,1. I used version 1.3.0 of the tool and downloaded Mojave through the tool too.
Cheers

 

[dendkmac]

have not touched the mac for a long time, migrated to Mojave on a MacBook Pro 5.3 from an old OS, well done with the Tools.

 

[SpyderSoldier]

Yes, it's all good anyway... I can only speak for myself: Mojave on my mbp 5,3 Mid-2009 runs better than HS, especially with the better APFS support. Hands down.

its suuuuuper slow on a MacBook Pro 8,2 tho. ngl

 

[hvds]

Hello! I am new to this and I have hit a snag. If the question has already been addressed please kindly point me the section of the thread.

The Issue:
When I attempt to create the USB boot media I get this message.

Failed Mounting failed. Please Check your MacOS Mojave Installer App then try again.

I have tried 3 USB thumb drives all above 16GB of space and various manufacturers. What step am I missing?

System Info:
Mac Mini 3,1 Intel Core 2 Duo 2.26Gz

I observe the same with the 10.14.2 installer app (version 14.2.2) which I retrieved from a time machine backup. The patcher (1.2.3 as well as 1.3.0) verifies the installer OK but then just before starting to write gives the above message.
No problems with the 10.14.4 installer app (version 14.4.08) which I still have from downloading with the patcher, nor with 10.14.3 (14.3.2) which I got from torrent, when writing to the same medium.

 

[siciov]

Finally !!!

The problem is
kernel_task” High CPU Usage Bug

A solution was found to the problem:
1) First, enable the display of hidden folders:
- Go to the "Terminal"
- We drive in 2 teams:
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder

2) Then we determine the computer model:
- Click "About this Mac"
- Next, click "More"
- Click on the "System Report"
Where the hardware is, find and remember the "Model ID". In my case, this is a MacBook6.1

3) Follow this path:
/ System / Library / Extensions
Select the IOPlatformPluginFamily.kext file, click the right button and select "Show package contents"

4) Go to Contents / PlugIns , then on the file ACPI_SMC_PlatformPlugin.kext also select "Show package contents"

5) Next, in Contents / Resources, find the file with the laptop model. As you remember: I had a MacBook 6.1. Delete this file! (If there is no necessary file, delete the nearest models)

6) Restart the computer. This procedure will probably have to be done after every Mac OS update.

To return the display of folders, as it was before, run the following command in the Terminal:
defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder

 

[hvds]

Thanks all of you for the assessment of 10.14.4 and the suggestions.

I use a MBP5,2 17", APFS ROM patch applied. 10.14.4 installed with dosdude's patcher on an external SSD with APFS, Patch Updater fixes installed.

1 - I followed the suggestion to delete the Safari settings. First I did: defaults read com.apple.Safari and was surprised by the amount of settings, then deleted them. Good riddance!
And afterwards: Safari works, doesn't provoke KPs anymore. Using it while writing this post. Just before the delete, I verified that Safari did still make KPs.

2 - Tried to switch from the Nvidia 9600M GT GPU, which I used the last days and now again, to the 9400M. Trying that from system settings + logout/login may have worked but resulted in a black screen, with display backlight on. Even with 10.14.3 it was like this. Then forced 9400M by resetting the NVRAM.
10.14.4 did KP soon after reboot in 9400M mode. After second boot I had enough time to switch to 9600M GT with system settings +logout/login, this time no black screen.
9400M related KPs were only experienced on MBP5,2 I think, not on 5,3.

With the cleaned Safari settings, and 9600M GT, 10.14.4 seems good as default for my work (SSD connected to SATA then). Will report observations of unnormal behaviour, and look forward to 10.14.5 and more...

EDIT: after two days of working with 10.4.4 I got a KP when starting Safari, and another one. I'll continue with .4 but refrain from Safari usage (removed it from the dock). Firefox is good enough for me. Curious to see what else may go wrong and keep me from working with .4 on my MBP5,2.

On my MBP5,2 with 10.4.4 got a KP while working in Numbers - not so good.
And a small point, the Photos app crashed when trying to edit a photo taken with an iPhone SE in Live mode. This works OK with 10.4.3.

 

[TimothyR734]

Rebuild your kextcache. Either re-install the Legacy Audio Patch with Patch Updater, or just run the following in Terminal:

sudo kextcache -system-caches
sudo kextcache -system-prelinked-kernel

When I try those terminal commands say not found , try safe mode a circle with a line through it even when trying to enable safe mode in terminal, tried installing 10.14.2 combo update it hangs, tried installing 10.14.4 it reboots to much I don't want to go back to High Sierra I wish I never updated to 10.14.4 when I had 10.14.3 I am about to take a sledge hammer to my iMac 9,1

 

[avz]

Hi folks, having an issue after installing Mojave on a freshly formatted APFS filesystem. After the install and reboot back into the USB to run the post install patcher then rebooting I’m just seeing a flashing image with a ?
I’ve tried booting back into the USB and running the patcher again, selecting to rebuild caches but still unable to boot to Mojave.
Can anybody assist please? Running a MacBookPro7,1. I used version 1.3.0 of the tool and downloaded Mojave through the tool too.
Cheers

Your machine should have native APFS support, but the firmware must be updated. Firmware update happens automatically when you install High Sierra. So it is not a good idea to go say from El Capitan to Mojave on the machine that has native APFS support.

 

[gosvamih]

Finally !!!

The problem is
kernel_task” High CPU Usage Bug


4) Go to Contents / PlugIns , then on the file ACPI_SMC_PlatformPlugin.kext also select "Show package contents"

ACPI_SMC_PlatformPlugin.kext - this is a kernel extensions for CPU SpeedStep. Remove Speed Step - I don't think this is a good idea



I have the MacBook6,1 and no any "kernel_task High CPU USAGE BUG"? I had a problem with Finder High CPU Load once, after some High Sierra minor update, and solved it easy to default finder settings
rm ~/Library/Preferences/com.apple.finder.plist

a big CPU load caused the speendump process sometimes. and sometimes another seems MRT process. I deleted that services.

 

[jackluke]

Both Hybrid and Flat mode patches work (without introducing side-effects that I know of) on all Mojave versions. So I don't anticipate development issues on 10.14.5.

10.14.4 introduced new code in CoreUI and changed the base offsets for the material patches, which brought me back to the drawing board as far as generating a scripted patcher. So for the moment I prefer to manually patch the dozen or so kCUIVariant entries that need it - which takes a little more time.

I'm not sure how many folks actually use "Flat" though. It isn't a complicated patch and can be (should be) scripted.
[doublepost=1554675654][/doublepost]
Oh - I think you mean simply News. That works fine in .2. News+ is a new "applet" inside the News sidebar. Doesn't require a subscription (I don't have one) to see its "home' page.

When using a Non-Metal GPU with only framebuffer (example on .5 beta1) isn't needed the Hybrid Patch since it is already a "without acceleration/transparency system".

However your 10.14.2 Hybrid patch still work with 10.14.4 "accelerated/transparency system".
I am using it.
[doublepost=1554715952][/doublepost]

ACPI_SMC_PlatformPlugin.kext - this is a kernel extensions for CPU SpeedStep. Remove Speed Step - I don't think this is a good idea

View attachment 830984View attachment 830990

I have the MacBook6,1 and no any "kernel_task High CPU USAGE BUG"? I had a problem with Finder High CPU Load once, after some High Sierra minor update, and solved it easy to default finder settings
rm ~/Library/Preferences/com.apple.finder.plist

a big CPU load caused the speendump process sometimes. and sometimes another seems MRT process. I deleted that services.
View attachment 830991

MRT is apple proprietary MalwareRemovalTool, I also got previously high %cpu and kernel_task on it, I fixed replacing the yara.framework inside the /S/L/Privateframeworks from a clean 10.14.4 , yara is the MRT.app engine: /System/Library/CoreServices/MRT.app

 

[hvds]

What is this talk about 10.14.3 vs 10.14.4? I of course downloaded what ever the patcher got out out of the Apple server yesterday so it must have been the latter one. It would be good to get some idea what is going wrong in my setup. I can’t download 10.14.3 anywhere now, can I?

The following worked for getting hold of 10.14.3 (I had installed it OTA and neglected downloading it at the time). Steps:
- download 10.14.3 from Mac Torrent: https://www.torrentmac.net/macos-mojave-10-14-3-18d42/. I used uTorrent for this. Results in six .rar files like macOS.10.14.3.part1.rar.
- uncompress the .rars. I used The Unarchiver from the App store. Open one of the .rar with this app and it will create a .dmg for the entire contents.
- double-click the .dmg to create the desired installer app.
- dosdude's patcher (1.2.3) happily creates an installer drive from this installer app. My MBP5,2 boots OK from this drive. I've installed the 10.14.3 obtained this way over an existing 10.14.4., and it boots and runs fine.
- installing the 10.14.3 Supplemental, as the latest macOS version before 10.14.4, I did not succeed. macOSUpd10.14.3Supplemental.dmg is available on Apple pages, but the installer says this .pkg is not supported on my system. I remember a remedy mentioned in this thread but can't find it back. I'm fine without the supplement.

 

[adeuxx]

Your machine should have native APFS support, but the firmware must be updated. Firmware update happens automatically when you install High Sierra. So it is not a good idea to go say from El Capitan to Mojave on the machine that has native APFS support.

What are my options now then? How do I get HS installed?

 

[avz]

What are my options now then? How do I get HS installed?

Time machine restore to the OS you had previously? Family member or a friend with a Mac that can be used to create High Sierra installer? For the future - it is super easy to dual boot Macs especially if you are doing experiments with unsupported systems.

 

[adeuxx]

Time machine restore to the OS you had previously? Family member or a friend with a Mac that can be used to create High Sierra installer? For the future - it is super easy to dual boot Macs especially if you are doing experiments with unsupported systems.

Hm, it isn’t letting me install HS, it needs Journaled filesystem. Disk Util only has APFS options. I don’t have a backup of this machine to go that route.

Edit: sorted by clicking view all devices. Once HS is installed though, won’t I have the same issue? I’ll need to format the drive APFS before trying Mojave again? HS won’t install on an APFS drive.

 

[Larsvonhier]

ACPI_SMC_PlatformPlugin.kext - this is a kernel extensions for CPU SpeedStep. Remove Speed Step - I don't think this is a good idea

View attachment 830984View attachment 830990

I have the MacBook6,1 and no any "kernel_task High CPU USAGE BUG"? I had a problem with Finder High CPU Load once, after some High Sierra minor update, and solved it easy to default finder settings
rm ~/Library/Preferences/com.apple.finder.plist

a big CPU load caused the speendump process sometimes. and sometimes another seems MRT process. I deleted that services.
View attachment 830991

Definitely not a good idea to remove or tamper with speedstep functions.

On most of my machines (unrelated to any Mojave CPU usage, which is fine here) I disabled Spindump and Tailspin
Here´s the instructions. (works since min. 10.12 and can be turned on again any time).
If you are a normal user and do not debug things, there are no side effects - other than a snappier machine.

 

[avz]

Hm, it isn’t letting me install HS, it needs Journaled filesystem. Disk Util only has APFS options. I don’t have a backup of this machine to go that route.

Edit: sorted by clicking view all devices. Once HS is installed though, won’t I have the same issue? I’ll need to format the drive APFS before trying Mojave again? HS won’t install on an APFS drive.

Once the High Sierra installer updates your firmware you can do whatever you want. You can even start with HFS+ drive and High Sierra installer might convert it to APFS by itself (without you knowing it).

 

[ASentientBot]

You could also use an El Capitan PlatformSupport.plist and overwrite the Recovery one, but APFS Recovery disk must be mounted otherwise you can't copy nothing on it.
[doublepost=1554625709][/doublepost]

on 10.14.2 just use the Post-Install Graphics Patch and you'll get acceleration.
[doublepost=1554626379][/doublepost]

For 10.14.4 you need to enter in safe mode to boot, boot holding CMD+S and type:
nvram boot-args="-no_compat_check -x -v"
reboot

then you need to use this archive.

GPUWrangler is only a workaround for .5 beta1.
[doublepost=1554628219][/doublepost]@ASentientBot can't find that address, if you could fix the file I attached then. Thanks.

Hope this helps @jackluke.

 

[adeuxx]

Once the High Sierra installer updates your firmware you can do whatever you want. You can even start with HFS+ drive and High Sierra installer might convert it to APFS by itself (without you knowing it).

I'm back up and running with HS installed. Opening Disk Util I can see that the FS is Journaled at the moment. If I now boot back into the Mojave installer and format the main disk as APFS and try the Mojave install again and run the post install patches afterwards can you confirm this should work now?

 

[jackluke]

Hope this helps @jackluke.
View attachment 831026

I didn't noticed the bottom bar, and I've tried also to search for "already NOP region", and on the original untouched file there were many.

Thank you! Always helpful, and your original patched file still worked even mixing it up with the "new" 2019 HS NvidiaTesla kext.

This is just for my attempt, but I guess fixing the GL acceleration on .5 beta1 is about AGC kext and a new NDRVShim kext.

edit:
Your method worked like a charm! And it seems a little faster on 10.14.4 maybe just an impression! Thanks again.

 

[pkouame]

When using a Non-Metal GPU with only framebuffer (example on .5 beta1) isn't needed the Hybrid Patch since it is already a "without acceleration/transparency system".

However your 10.14.2 Hybrid patch still work with 10.14.4 "accelerated/transparency system".
I am using it.
[doublepost=1554715952][/doublepost]

MRT is apple proprietary MalwareRemovalTool, I also got previously high %cpu and kernel_task on it, I fixed replacing the yara.framework inside the /S/L/Privateframeworks from a clean 10.14.4 , yara is the MRT.app engine: /System/Library/CoreServices/MRT.app

Cool. Yes it should still work with the 10.14.2 version.

So seems like I'm stuck @ .4. I'm Trying to revert back to .3 from an old .1 stick + downloaded comboUpdate10.14.3. Theoretically should work fine, but my machine spins with all kinds of MRT, spins and incessant ReportCrash issues. Haven't seen this since the old HS days. Most Apps crash with secinitd and sandbox errors (missing profiles etc...)

I know this may be old hat, but did some of you deal with this during the .2 to .3 update?

BTW, a OTA softwareupdate (still works) to the latest .4 (and post-install of course) solves the problem.

 

[avz]

I'm back up and running with HS installed. Opening Disk Util I can see that the FS is Journaled at the moment. If I now boot back into the Mojave installer and format the main disk as APFS and try the Mojave install again and run the post install patches afterwards can you confirm this should work now?

There is no guarantees in life. If I was you I would create a separate partition and try to install Mojave. Did your boot rom got updated? What is the firmware number? You can find that info in the system information. Since your Mac is officially supported for High Sierra, you should create and only use an official High Sierra installer.