Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Hey @dosdude1, I’m getting a 27” iMac from a buddy in a few weeks. It’s a Late 2009 and it has a i7 and a Radeon HD 4850 gpu. I have two questions I hope you can help me with.
1. Do these AMD gpus still have the App Store auto play crash issue?
2. I know the Radeon HD 5xxx and 6xxx series do not have working acceleration under Mojave. My question is why do the others work? (such as the 4850 and 2600 Pro) Do they use different kexts with different requirements?
I have the same iMac and I can report that Mojave works perfectly.
 
  • Like
Reactions: TimothyR734
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.

Hi!
Thanks for the detailed explanation!
I’m having the same issue…
However, I want to apply the Continuity Activation Tool patch on my system anyway.
Should I revert the kext files before applying the additional patch or would the kexts be overwritten anyway?
Thanks :)
 
Hi!
Thanks for the detailed explanation!
I’m having the same issue…
However, I want to apply the Continuity Activation Tool patch on my system anyway.
Should I revert the kext files before applying the additional patch or would the kexts be overwritten anyway?
Thanks :)

If you have an airport Wifi/BT 4.0 card then use these without any Continuity patch: Bluetooth 4.0 untouched Mojave kext

Otherwise if you have a BT 2.1 card, then I guess you should try the Continuity Act tool over your unpatched Wifi kext, however I don't use that tool, so can't help further.
 
  • Like
Reactions: TimothyR734
Well, I just tried this and it didn't work either. Maybe I need to zap my PRAM or something?

Does your machine actually have any high temperatures?

If not, a SMC reset may clear the issue. Be aware that any volatile boot arguments will be cleared by doing so, as may some software specializations (ie. SIP arguments, video card memory adjustments/discrete GPU bypass).
 
Thanks!
I’m using a USB BT4.0 dongle, so I definitively need to run the Continuity Act tool...
If you have an airport Wifi/BT 4.0 card then use these without any Continuity patch: Bluetooth 4.0 untouched Mojave kext

Otherwise if you have a BT 2.1 card, then I guess you should try the Continuity Act tool over your unpatched Wifi kext, however I don't use that tool, so can't help further.

Ok, at first, forget about Continuity act tool for now ;) I’d like to restore bluetooth functionality first…

So, what I did now:

- last High Sierra TM-Backup: took both kexts, restored them, entered terminal commands, rebooted:
BeatsX only connect for a short while, not possible to play sound through them :(

- first Mojave backup, right after the dsodude1-patched installation: took both kexts, restored them, entered terminal commands, rebooted:
BeatsX only connect for a short while, not possible to play sound through them :(

-> both HS kexts and initial patched Mojave kexts don’t bring back bluetooth headset functionality…

Anything else I can try?

UPDATE: using both kexts from the installer stick works (although much smaller...)
 
Last edited:
Installed sucessfully on iMac 8,1. Only issue is volume control that was fixed by the "Volume Control Patch" on High Sierra, tried running the High Sierra "macOS Post Install" to install the patch but that did not fix it. Can anyone help me?

Just been alerted by Patch Updater that "Volume Control Patch" is available. Installed and restarted and can confirm it works ok. Thanks for that.
 
  • Like
Reactions: TimothyR734
@jackluke... you wrote "...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..." etc. I have just applied your instructions to a MBP4,1 (2008), and the bluetooth has started to work. Both files replaced the original files which were version 6.0.7 (yours, 6.0.8). Thank you for providing both file and explanation.
 
Last edited:
Upgraded my old 2008 MacBook unibody (MacBook5,1) to Mojave with no problems! Only issue I've seen so far is the known issue about sidebar shading, which isn't noticeable when all's kept in Dark Mode :)

One question for anyone listening: I kept my internal third-party SSD formatted HFS+ extended journaled, but am curious – is there any performance improvement if I format the drive for APFS? Has anyone tested performance or run benchmarks on third-party SSDs in Mojave that use HFS+ vs. APFS?

(Several articles written last year during High Sierra said APFS performance slightly lagged HFS+, but wonder if that's improved now under Mojave.) Thanks!
 
Does your machine actually have any high temperatures?

If not, a SMC reset may clear the issue. Be aware that any volatile boot arguments will be cleared by doing so, as may some software specializations (ie. SIP arguments, video card memory adjustments/discrete GPU bypass).

No, no thermal issues that I'm aware of.
 
  • Like
Reactions: TimothyR734
Upgraded my old 2008 MacBook unibody (MacBook5,1) to Mojave with no problems! Only issue I've seen so far is the known issue about sidebar shading, which isn't noticeable when all's kept in Dark Mode :)

One question for anyone listening: I kept my internal third-party SSD formatted HFS+ extended journaled, but am curious – is there any performance improvement if I format the drive for APFS? Has anyone tested performance or run benchmarks on third-party SSDs in Mojave that use HFS+ vs. APFS?

(Several articles written last year during High Sierra said APFS performance slightly lagged HFS+, but wonder if that's improved now under Mojave.) Thanks!
No major issues here with APFS in terms of I/O speed. Only increased boot times might be noticable in comparison to HFS+.
 
Does not work, i have another osx installed on my imac and was able to paste the file into the folder which is located on the other hdd which will not but my os mojave...any other options? Was waiting for a update on the pacther.

Try use this file into your Mojave: Mojave patched CoreBrightness Night Shift
After download before copy be sure that is renamed correctly into CoreBrightness (NOT CoreBrightness-1 , CoreBrightness-2 and so on)

If neither the linked file will work for you then simply try to delete this file and reboot Mojave:
/YourMojavelabel/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness
 
  • Like
Reactions: TimothyR734
zielinski's project hasn't been updated in a while (three years) so I'm refreshing the CoreUI framework headers to see if that has an effect. Definitely an issue though. @testheit has been making some excellent headway with CoreUI materials, hence the interest in .car and .caar files. Discussion under way in my git repo...
Thank you for your contribution on this UI issues! When the solution will be available?
At least, would you be so kind to upload some progress info with screenshots and explanations, etc.?
Thank you!
 
  • Like
Reactions: TimothyR734
Try use this file into your Mojave: Mojave patched CoreBrightness Night Shift
After download before copy be sure that is renamed correctly into CoreBrightness (NOT CoreBrightness-1 , CoreBrightness-2 and so on)

If neither the linked file will work for you then simply try to delete this file and reboot Mojave:
/YourMojavelabel/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness

Thats what i did, i was able to access my hdd through another OS, followed the file path and replaced with authentication...reboot and does not work...

Are you saying i should delete the file and it will auto load a new one?
 
  • Like
Reactions: TimothyR734
Thats what i did, i was able to access my hdd through another OS, followed the file path and replaced with authentication...reboot and does not work...

Are you saying i should delete the file and it will auto load a new one?

Not exactly but deleting that file should allow to boot Mojave without using another OS to view inside your Mojave hdd volume.

What do you mean doesn't work ? It stucks on Apple logo loading bar, prohibitory symbol or quick reboot ?

However do you have updated Mojave to 10.14.1 beta ?
If so then the reason why you can't boot more Mojave is not addressed to the patched CoreBrightness, but other incompatibilities on some machines not yet fixed.
 
  • Like
Reactions: TimothyR734
Maybe it just needs a bit of time to get the brightness fixed? I'm on MacBook Pro 2011 and ironically my AMD GPU has died on me. So the discrete GPU blocking sort of became a gift because the integrated GPU seems to work seamlessly. I havent gone through the complete thread here, but I think for people with older devices it seems reducing transparency in the accessibility settings does keep the Mac a bit cooler
 
  • Like
Reactions: TimothyR734
I am currently running MacOS 10.14 on a MacBookPro5,4 and cannot seem to update to the latest beta 10.14.1
I have installed the developer's seed and have tried to run the patcher and besides some updates on that end I cannot seem to update for the life of me.
 
  • Like
Reactions: TimothyR734
Not exactly but deleting that file should allow to boot Mojave without using another OS to view inside your Mojave hdd volume.

What do you mean doesn't work ? It stucks on Apple logo loading bar, prohibitory symbol or quick reboot ?

However do you have updated Mojave to 10.14.1 beta ?
If so then the reason why you can't boot more Mojave is not addressed to the patched CoreBrightness, but other incompatibilities on some machines not yet fixed.

Apple logo, the first boot when we switch on the mac, and the loading bar loads full but stays there...could be beta 6 maybe...

I will wait for a patch update then...
 
  • Like
Reactions: TimothyR734
I am currently running MacOS 10.14 on a MacBookPro5,4 and cannot seem to update to the latest beta 10.14.1
I have installed the developer's seed and have tried to run the patcher and besides some updates on that end I cannot seem to update for the life of me.
Same issue for me. I think this is because of some uninstallable part of the update. @ASentientBot Do you know how I can download the update package itself? What to search for on the software catalog.
 
  • Like
Reactions: TimothyR734
Same issue for me. I think this is because of some uninstallable part of the update. @ASentientBot Do you know how I can download the update package itself? What to search for on the software catalog.

You can't get a full InstallESD for the point update, it seems.

Looks like the update package URL for the latest (actually released today) update is this, right at the end of the software catalog:
http://swcdn.apple.com/content/down...u5vjq53xbqd4ifcn3mt5qhmlr/macOSUpd10.14.1.pkg

Haven't tried installing it yet though.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.