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
In the past I came across a couple of methods of modding the distribution file, I'm assuming you're using the same method as me of adding "return true;" to both the function installation check and function volume check?
That's all I did and it installed without issues on my iMac 9,1. The only other thing I had to do was run the post install patch on reboot.
Yes that is exactly what I did as I have done many times before, but yet this error keeps popping up.
So there must be something wrong on my Mac, perhaps the file com.apple.package-script-service
may be corrupt. Might have to reinstall Mojave and try the security update again.
Bother.
[automerge]1595004892[/automerge]
That is a different error from my problem, download the attachment from TimothyR734
and read its contents.
Before you reinstall everything I would run the maintenance routine of Onyx. I know this sounds like a random recommendation but it fixed installation errors caused by my last SU (003).
Hi, so i have ran Onyx on my Mojave HFS+ installation and restarted and Hey Presto the Security Update has installed.
Thank You very much for that.
Onyx worked, thanks a lot. Now on:
[automerge]1595015971[/automerge]
This is all a mystery. How it works or not. But the main part is the community!
[automerge]1595015971[/automerge]
This is all a mystery. How it works or not. But the main part is the community!
I used Onxy for the first two of three and not again. So I guess that when it was time for number 4, I had missed a step. Thus the fail. Also I'm not getting the (Revision Number) next to the Version Number in the "About" panel I have to tunnel into the System Report to see it.
Thanks for the kick in the butt!!!
Thanks for the kick in the butt!!!
I have a strange story, and I don't know where else to tell it.
I just applied the new "security update 2020-004 10.14.6 Mojave" on a patched MacBookPro8,3 (2011, 17-inch). Had a weird (unrelated) problem shutting down so I had to power off by holding the power button, and then the software update applied when I started the machine again. I let it do its thing (screen went black for a bit in the middle) until eventually it got to a gray screen with Apple logo and progress bar overlaid with a "stuck" white spinner. Then powered off again and went through reinstalling patches from a Mojave Patcher partition, then booted up and reinstalled all updated patches with the Patch Updater app, and rebooted again. The usual procedure for recovering a patched Mac after an Apple system update.
It's at night, and the room at this point is fairly dark with just one dimmable lamp on low, but my screen also seems darker than usual, which is bad because it's been pretty dark for months since I upgraded to Mojave with the patcher.
Without thinking, by force of habit, I reach for the brightness up key on the keyboard.
It works. The screen is very bright now.
What the... ?
I've run the DosDude1 patcher on several different Macs over the last several months. I've gotten used to the fact that brightness control is often lost. I am almost absolutely certain that I spent a couple of months trying various things to get brightness control back on this specific MacBook Pro, which is my main machine (it has a bad GPU disabled via the NVRAM trick). Nothing ever worked to get the brightness control back, and I haven't yet physically disabled the GPU so it also gets quite toasty at times because the trick of copying the old driver kext for the video card doesn't seem to work beyond High Sierra. But I eventually gave up fixing the brightness control and just set up the Brightness Slider app from the App Store using Fn+F1/F2 keys. It's sitting in my menu bar right now.
But suddenly the standard brightness controls are working again. Which I only discovered by forgetting that they weren't working.
I really have no idea exactly how excited to be about this. Did I just miss the trick that would have gotten this working months ago, or is this a sudden new development somehow caused by this recent security update?
Can anyone with a similar MacBook Pro confirm that they had no brightness controls prior to installing this recent security update, only to have the brightness controls start working again immediately afterward?
In other words, am I just an idiot or did some kind of minor miracle just happen?
I just applied the new "security update 2020-004 10.14.6 Mojave" on a patched MacBookPro8,3 (2011, 17-inch). Had a weird (unrelated) problem shutting down so I had to power off by holding the power button, and then the software update applied when I started the machine again. I let it do its thing (screen went black for a bit in the middle) until eventually it got to a gray screen with Apple logo and progress bar overlaid with a "stuck" white spinner. Then powered off again and went through reinstalling patches from a Mojave Patcher partition, then booted up and reinstalled all updated patches with the Patch Updater app, and rebooted again. The usual procedure for recovering a patched Mac after an Apple system update.
It's at night, and the room at this point is fairly dark with just one dimmable lamp on low, but my screen also seems darker than usual, which is bad because it's been pretty dark for months since I upgraded to Mojave with the patcher.
Without thinking, by force of habit, I reach for the brightness up key on the keyboard.
It works. The screen is very bright now.
What the... ?
I've run the DosDude1 patcher on several different Macs over the last several months. I've gotten used to the fact that brightness control is often lost. I am almost absolutely certain that I spent a couple of months trying various things to get brightness control back on this specific MacBook Pro, which is my main machine (it has a bad GPU disabled via the NVRAM trick). Nothing ever worked to get the brightness control back, and I haven't yet physically disabled the GPU so it also gets quite toasty at times because the trick of copying the old driver kext for the video card doesn't seem to work beyond High Sierra. But I eventually gave up fixing the brightness control and just set up the Brightness Slider app from the App Store using Fn+F1/F2 keys. It's sitting in my menu bar right now.
But suddenly the standard brightness controls are working again. Which I only discovered by forgetting that they weren't working.
I really have no idea exactly how excited to be about this. Did I just miss the trick that would have gotten this working months ago, or is this a sudden new development somehow caused by this recent security update?
Can anyone with a similar MacBook Pro confirm that they had no brightness controls prior to installing this recent security update, only to have the brightness controls start working again immediately afterward?
In other words, am I just an idiot or did some kind of minor miracle just happen?
Last edited:
Updated without an issue on a 17" MacBook Pro mid-2009 (MacBookPro5,2) using @TimothyR734 's notes on how to edit the Security Update's Distribution file and by modifying the Board-Id for my model within the very same file.
The revision number or build number is hidden by default in About This Mac, if you want to see itI used Onxy for the first two of three and not again. So I guess that when it was time for number 4, I had missed a step. Thus the fail. Also I'm not getting the (Revision Number) next to the Version Number in the "About" panel I have to tunnel into the System Report to see it.
Thanks for the kick in the butt!!!
move the cursor over the text Version 10.14.6 and click on your mouse or trackpad, you may have
to use the Control key as well.
See that option "Restore Defaults"? Click there and then "Run Tasks"
Having said that I wasn't going to install any more security updates because they break my sleep (from the Apple menu) ... well, read on.
At the same time that the latest security update appeared, there was also a Safari update. So I decided I would just do that, and guess what? It broke my sleep. I can't imagine what there can be in a Safari update that would break sleep, but anyway ....
So, what I did this time was, try and sleep from the Apple menu, wait for it to fail after 3 mins, whereupon it would restart itself. But on restarting I did a reset nvram (Cmd-Opt-P-R). Tried the sleep again and it failed and restarted. Did the reset nvram again. In total I had to perform 3 restarts and resetting nvram before sleep would work. Why 3, I have no idea.
Having determined that resetting nvram 3 times restores the sleep functionality, I bit the bullet and installed the security update. Restarted into the patcher, and installed all the post-install patches. To my surprise, after that, sleep worked without having to do any more resetting nvram.
So, I'm now not sure whether it was the security updates breaking my sleep previously or some other update e.g. Safari, that I was doing at the same time.
I still had to jump through some hoops this time though. Firstly it complained that the Night Shift patch had been overwritten so that needed reinstalling. Even after that I had no Night Shift tab in my Displays prefpane. What's more, my audio was messed up, I couldn't adjust the volume with the volume keys (prohibit sign) and the Audio Midi Controller app was empty. So I did a re-install all from the Patch Updater and everything was fine.
At the same time that the latest security update appeared, there was also a Safari update. So I decided I would just do that, and guess what? It broke my sleep. I can't imagine what there can be in a Safari update that would break sleep, but anyway ....
So, what I did this time was, try and sleep from the Apple menu, wait for it to fail after 3 mins, whereupon it would restart itself. But on restarting I did a reset nvram (Cmd-Opt-P-R). Tried the sleep again and it failed and restarted. Did the reset nvram again. In total I had to perform 3 restarts and resetting nvram before sleep would work. Why 3, I have no idea.
Having determined that resetting nvram 3 times restores the sleep functionality, I bit the bullet and installed the security update. Restarted into the patcher, and installed all the post-install patches. To my surprise, after that, sleep worked without having to do any more resetting nvram.
So, I'm now not sure whether it was the security updates breaking my sleep previously or some other update e.g. Safari, that I was doing at the same time.
I still had to jump through some hoops this time though. Firstly it complained that the Night Shift patch had been overwritten so that needed reinstalling. Even after that I had no Night Shift tab in my Displays prefpane. What's more, my audio was messed up, I couldn't adjust the volume with the volume keys (prohibit sign) and the Audio Midi Controller app was empty. So I did a re-install all from the Patch Updater and everything was fine.
Replying to myself with sad news. The party is over. After having some really odd little glitches with a couple of apps like Etcher that have never given me problems before, I ran Onyx maintenance and rebooted. Had to fix the NVRAM to once again disable the GPU (MacBookPro8,3).
Brightness control keys are once again non-functional.
Anyone have any idea how to get the brightness controls back? I don't even know where to begin looking. Obviously it is possible to get it working again since it was working after the last Mojave security update, before I used Onyx. How did Onyx wipe it out again?
On the plus side, Etcher is behaving much better.
Tried doing this, but I don't have the AMDRadeon file. Could there be another?
Hi all,
Mojave SecUpd2020.004 (18G6020) successfully installed on MBP5,3 and iMac8,1 a few days ago (After Distibution file modification)
Reapplied Postinstall with Force Cache rebuild at the first restart after update.
Like the other times, I replaced AppleGVA.framework (for videos fluidity), HIToolbox.framework (for dock menu shadows), SiriUI.framework and Siri.app (for waveform) and SoftwareUpdate.framework (to disable the Catalina upgrade proposal).
Everything works well
Mojave SecUpd2020.004 (18G6020) successfully installed on MBP5,3 and iMac8,1 a few days ago (After Distibution file modification)
Reapplied Postinstall with Force Cache rebuild at the first restart after update.
Like the other times, I replaced AppleGVA.framework (for videos fluidity), HIToolbox.framework (for dock menu shadows), SiriUI.framework and Siri.app (for waveform) and SoftwareUpdate.framework (to disable the Catalina upgrade proposal).
Everything works well
Luis, thanks for the quick reply. But perhaps you can explain why all of the items which appear in Restore Defaults would be necessary? Thinking that rebuilding all these caches will be time consuming and produce a great deal of beach balling. For example, the DNS or browser caches/history (browser cache/history I always deal with independently), Recent Items, Applications Cache, Fonts Cache. Perhaps you can say just what the minimum is for a satisfactory result? Would think that just the items checked in my screenshots in my first post would do the job. Besides those, can you say what others are really necessary, and why?
Last edited:
OnyX is safe to run been using it for years with the defaults no issues