As noted earlier, tested by booting to Mojave, where SIP is disabled by default, and then back to HSierra (supported), where SIP is enabled - or I should say, re-enabled, after discovering that it had somehow become disabled. Booting back to HSierra from Mojave, SIP remained enabled (at least for the time being, until something (weird) happens again.
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
Must admit I'm getting more confused. So, if you boot into Mojave and do
csrutil status
and then, without doing anything else, boot into HS and do
csrutil status
you should get the same answer
Are you saying you don't?
For now the @ASentientBot patches are sufficient for our needs but I have considered making it into an iHac?OCLP disables SIP only when system volume changes are unavoidable (aka patching back OpenGL graphics acceleration). You could mod your iMac11,2 to get an metal enabled GPU to move over to into the SIP enabled world, again
Hi all,
Successfully updated MBP5,3 (HFS+) with SecUpd2021-004Mojave (18G9216).
After, installing this update, needed reboot on USB Key and re-patch with Dosdude1's Patcher with force cache rebuild.
As every time, appleGVA.framework, softwareupdate.framework, HIToolbox, Siri.app and SiriUI.framework (for Siri waveform) have been replaced.
Successfully updated MBP5,3 (HFS+) with SecUpd2021-004Mojave (18G9216).
After, installing this update, needed reboot on USB Key and re-patch with Dosdude1's Patcher with force cache rebuild.
As every time, appleGVA.framework, softwareupdate.framework, HIToolbox, Siri.app and SiriUI.framework (for Siri waveform) have been replaced.
Last edited:
Updated my Metal GPU upgraded iMac late 2009 without patching to 18G9216, using latest OCLP nightly build.
Thanks alphascorp!
Since last security update I didn’t patch anything and software update has not been nagging to update to BigSur
If I check updates it’s there but that’s it.
Hi @L Caputo
Here is the link of SecUpd2021-004Mojave (18G9216) (.pkg). The full installer (.dmg) is available here.
But I think this is enough because the full installer also contains:
"EmbeddedOSFirmware.pkg" and "FirmwareUpdate.pkg" which are not necessary because I don't think Apple will update the Firmware on our machines not supported for a long time
."FullBundleUpdate.pkg" file contains the installation of Safari 12.1.2 and MRT 1.52 therefore not necessary either considering that we have made the update to Safari 14.1.1 and MRT is currently 1.78 updated automatically by the system.
"macOSBrain.pkg" file contains only the binary "atomicupdatetool", it's a helper tool for the macOS Software Update mechanism.
"SecureBoot.pkg" contains 11 "Boot.efi" files which are also installed by "SecUpd2021-004Mojave.pkg" (so is not necessary either).
Last edited:
Hi, Thanks for responding to my post, but the first link only downloads the SecUpd2021-004Mojave.pkg which cannot be installed on its own you do need all the other packages EmbeddedOSFirmware, FirmwareUpdate,FullBundleUpdateHi @L Caputo
Here is the link of SecUpd2021-004Mojave (18G9216), (direct link from Apple servers). This is not the full installer (not yet available here).
But I think this is enough because the full installer also contains:
"EmbeddedOSFirmware.pkg" and "FirmwareUpdate.pkg" which are not necessary because I don't think Apple will update the Firmware on our machines not supported for a long time
"FullBundleUpdate.pkg" file contains the installation of Safari 12.1.2 and MRT 1.52 therefore not necessary either considering that we have made the update to Safari 14.1.1 and MRT is currently 1.78 updated automatically by the system.
"macOSBrain.pkg" file contains only the binary "atomicupdatetool", it's a helper tool for the macOS Software Update mechanism.
"SecureBoot.pkg" contains 11 "Boot.efi" files which are also installed by "SecUpd2021-004Mojave.pkg" (so is not necessary either).
macOSBrain, SecUpd2021-004MojaveRecoveryHDUpdate and SecureBoot.pkg and the Distribution file.
I can pull all of these items from the Apple Server and then use Terminal to create a single .pkg but this will not install
even though I have altered the Distribution file so it can be installed on unsupported macs, I get an error that the Installer app can't find some needed data. So Ho Hum.
I was really hoping someone could give me the web address from where the full Security Update package can be downloaded. In days gone by people often posted the web address to get the standalone updates before they were posted on the Apple Support Downloads site, which Apple now take up to a week to update with new updates.
And in the case of Big Sur they don't even bother.
This why we are still using Mojave ….waiting to download the full installer too: maybe our wait would be shorter this time ?
After this Mojave SU is the process trustd running amok? Go to Library/Keychains/crls/ Delete the valid.sqlite3 files. When rebooting with a network connection Apple will rebuild the .sqlite files, trustd will peak briefly, then CPU activity will return to normal for good. Those files are in the directory /private/var/protected/trustd/ on Big Sur if also afflicted.
I had the trustd problem recently. Can't say for definite when it started but it was before this SU, obviously. Maybe it was the result of the previous SU - who knows. Anyway, I followed the instructions (found them on lapcatsoftware here) and everything was fine afterwards.
My point was that the trustd problem was probably not caused by SU, at least in my case. Plus AFAIK, it was the guy at lapcatsoftware that diagnosed the problem.
Thanks @K two for the information about "trustd" high CPU usage, I also got that but after the 2021-003 SU, I used the excellent Onyx and everything was fine.
Yes, Big Sur's .heic wallpapers work very well under Mojave (I've been using them for almost a year, and I'm currently using "blue hello" from 11.3)
But I've found that for a better reactivity of the thumbnails display in "DesktopScreenEffects. prefPane" of the System Preferences, it is advisable to add the thumbnails in the hidden folder ".thumbnails" (in the "Desktop pictures" folder) but also to add each added wallpaper name in the hidden file ".orderedPictures.plist" (also in the "Desktop pictures" folder) like this:
Yes, Big Sur's .heic wallpapers work very well under Mojave (I've been using them for almost a year, and I'm currently using "blue hello" from 11.3)
But I've found that for a better reactivity of the thumbnails display in "DesktopScreenEffects. prefPane" of the System Preferences, it is advisable to add the thumbnails in the hidden folder ".thumbnails" (in the "Desktop pictures" folder) but also to add each added wallpaper name in the hidden file ".orderedPictures.plist" (also in the "Desktop pictures" folder) like this:
Code:
<string>Big Sur.heic</string>
<string>The Cliffs.heic</string>
<string>The Lake.heic</string>
<string>The Desert.heic</string>
<string>The Beach.heic</string>
<string>Solar Gradients.heic</string>
<string>Big Sur Graphic.heic</string>
<string>Peak.heic</string>
<string>Tree.heic</string>
<string>Valley.heic</string>
<string>Dome.heic</string>
<string>Iridescence.heic</string>
<string>Big Sur Graphic Day.heic</string>
<string>Big Sur Graphic Night.heic</string>
<string>Big Sur Day.heic</string>
<string>Big Sur Night.heic</string>
<string>Big Sur Mountains.heic</string>
<string>Big Sur Aerial.heic</string>
<string>Big Sur Horizon.heic</string>
<string>Big Sur Coastline.heic</string>
<string>Big Sur Shore Rocks.heic</string>
<string>Big Sur Waters Edge.heic</string>
<string>Big Sur Road.heic</string>
<string>Big Sur Night Succulents.heic</string>
<string>hello Blue.heic</string>
<string>hello Green.heic</string>
<string>hello Grey.heic</string>
<string>hello Orange.heic</string>
<string>hello Purple.heic</string>
<string>hello Red.heic</string>
<string>hello Yellow.heic</string>Ran the 2021-004 .pkg linked above from alphascorp (agree with his opinion that, with our older machines, no need to wait for the full standalone for firmware updates, plus we already get latest Safari, MRT, XProtect). (Without the distribution file, just don't try installing it to a Snow Leopard volume ).
After patching all went well except the Mac (Late '09 iMac) seemed to think it was dealing with an OS upgrade, so hung interminably on Setting up Your Mac (have occasionally seen this before - even, I believe, with the full installer or directly from the APFS volume - wonder why?). Gave it some time, but then did a hard shutdown, restarted, and now seems just fine.
).After patching all went well except the Mac (Late '09 iMac) seemed to think it was dealing with an OS upgrade, so hung interminably on Setting up Your Mac (have occasionally seen this before - even, I believe, with the full installer or directly from the APFS volume - wonder why?). Gave it some time, but then did a hard shutdown, restarted, and now seems just fine.
Last edited:
We can still use recovery with our older machines which is updated when you use a full installer plus updating a system while being booted into that system is not a good idea(although it does work).Ran the 2021-004 .pkg linked above from alphascorp (agree with his opinion that, with our older machines, no need to wait for the full standalone for firmware updates, plus we already get latest Safari, MRT, XProtect). (Without the distribution file, just don't try installing it to a Snow Leopard volume
The mystery deepens: ran the 2021-004, then, after booting back to HSierra, discovered that SIP was once agin disabled. Aha, so think to myself culprit has to be the SIP Disabler Patch, which works in one direction only from patcher to HSierra. To test, re-enabled SIP at the HSierra, from recovery, then booted to the patcher and ran only the SIP Disabler, cache rebuild, booted to the Mojave, then booted back once again to HSierra and ran csrutil status.
Where, fully expecting to be seeing that csrutil status at HSierra was once again showing disabled, saw that SIP had remained enabled.
Only other explanation I can possibly come up with is that something to do with cloning the Mojave HFS volume on the internal, now at 18G9216, to the Mojave APFS volume on the external, and then booting to that volume was responsible.
Otherwise, this remains a total WTF.
Last edited:
1. For me, at least, I find that booting to the patcher seems to function just as well as an ordinary recovery partition. Everything I need is right there.
2. What's not a "good idea" to update while being booted to that system (volume?)? Especially, since as you say, it works?
Last edited:
I'm guessing here so don't take this as gospel. Having set SIP once (when booted in recovery) it doesn't look to me like you did anything to disable SIP. What you did was run the patcher to install the SIP Disabler Patch onto the Mojave partition - which AFAIK only installs the SIPManager.kext. AFAIK again, when you run Mojave the SIPManager makes it look like SIP is disabled, regardless of its actual state. So when you booted back into HS maybe it's not surprising that SIP was still enabled. I may be wrong, obvs. If you want the real answer, you could try asking @dosdude1 (he wrote the SIP DIsabler patch, yes?).
1. True, I just don’t like using extra USB sticks or detract from a hard drive for an extra patcher partition.
2. I am not an expert but there is a good reason for when you install an update it usually asks you to restart the machine and then proceeds with the installation from a specially created “volume”.
My guess then is that simply running the SIP Disabler, as I did, isn't sufficient to test. Not going to do this, but I assume what's needed for a valid test is to entirely reapply the 2021-004, which will overwrite the current patches, including the SIPManager.kext, and fully re-patch. My expectation then would be that SIP in HSierra would be disabled, as before.