macOS 10.14 Mojave on Unsupported Macs Thread

[brian.tully]

Not sure whether that is the issue and just flagging it as a possibility.

DosDude stopped updating the Mojave Patcher long before he stopped updating the Catalina one. The Catalina Patcher has the current MouSSE kext but the Mojave one does not.

Note that updating this on Mojave is not a case of simply replacing the installed version as the Patch Updater will nag you to update when it notices the installed version is different from the distributed one as it assumes different means older.

The twist is that you must never accept the option to ignore the message as all future checks (on everything) by the tool will be skipped and not just checks on MouSSE. Basically a bug. Important...Never accept that option. It disables all checks and not just for the item that generates it as you would expect.

You need to follow these steps to get the latest version and skip the nagging while keeping checks on for other tools:

MP3,1 (& others?) SSE 4.2 emulation (to enable AMD Metal driver)

Pending updates to the backend by DosDude, I have overridden the patch updater to allow using recent MouSSE versions without warnings as attached below. Download and extract attached FixPatchUpdate093.zip or FixPatchUpdate095.zip file for the MouSSE version upgrade This will expand into an...

forums.macrumors.com

You will need to always repeat the process after using the Patcher following every software update.

I have modified my Patcher to avoid this.

You and @joevt are HEROES! Thanks so much ?

 

[Schneekristall]

My Mac Pro 3,1 (NVIDIA GT 710) works fine now, but it sometimes gets stuck in a very fast-paced boot loop when powering it on (about one start chime sound per second; it does not even finish playing the chime sound before it restarts). Then I have to power-cycle it after which it boots fine again. Will the APFS ROM patch fix this?

 

[alphascorp]

Hi all,

Successfully installed SecUpd2021-001Mojave (18G8012) on MBP5,3.

After, installing this update, needed reboot on USB Key and re-patch with Dosdude1 Patcher with cache rebuild and reinstall appleGVA.framework, softwareupdate.framework, HIToolbox, Siri.app and SiriUI.framework (for Siri waveform)

As for the other times, downgrading SoftwareUpdate.framework does not prevent receiving updates (like the one for Safari 14.0.3 for example, see screenshot below) but will prevent the proposal of major updates (Catalina and Big Sur) with the combined use of:

sudo softwareupdate --ignore "macOS Catalina"
sudo softwareupdate --ignore "macOS Big Sur"

REMINDER:
After replacing "SoftwareUpdate.framework" to remove the red badge (for those who might have it) run this:

sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate.plist LastRecommendedMajorOSBundleIdentifier
defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier
defaults write com.apple.systempreferences AttentionPrefBundleIDs 0
killall Dock

 

[nospamboz]

Does anyone know where the Security Update 2021-001 Mojave is downloadable? Here HFS+, SilentKnight doesn't work for me.

HFS+ here as well. I'm assuming it will be like 2020-007 (and -006 I think) and show up for download on the Apple Support Download page a week after release. Then "true-patch" the Distribution file as usual, boot @dosdude1 USB to re-patch, etc.

 

[Rob1n]

So Hrutkay Mods' claim in his YouTube video that only NVIDIA chipsets are affected is wrong?

No, I think he says that there is a very small chance to brick your system when you have an intel chipset. I think there is always a risk, for example if your power goes out or something else happens during the process. But the process is quick and I think you won't have any problems. I just don't want to be responsible if you brick your system. (It probably will be fine)

 

[K two]

No, I think he says that there is a very small chance to brick your system when you have an nvidia chipset. I think there is always a risk, for example if your power goes out or something else happens during the process. But the process is quick and I think you won't have any problems. I just don't want to be responsible if you brick your system. (It probably will be fine)

@dosdude1 recommends NOT using the ROM patcher on NVIDIA machines. FWIW The APFS patch installed by the v.1.3.7 patcher works just fine but not as "clean", scrolling text at boot, etc.

 

[K two]

HFS+ here as well. I'm assuming it will be like 2020-007 (and -006 I think) and show up for download on the Apple Support Download page a week after release. Then "true-patch" the Distribution file as usual, boot @dosdude1 USB to re-patch, etc.

There is no reason to cling to HFS+ with Mojave. It simply makes updates a PITA.

 

[Schneekristall]

@dosdude1 recommends NOT using the ROM patcher on NVIDIA machines. FWIW The APFS patch installed by the v.1.3.7 patcher works just fine but not as "clean", scrolling text at boot, etc.

I'm currently using the "scrolling text" patcher. My thought is this might cause the boot loops. I'm going to install the ROM patch for good measure tonight.

Edit: It worked perfectly and it did resolve the boot loop.

 

[K two]

I'm currently using the "scrolling text" patcher. My thought is this might cause the boot loops. I'm going to install the ROM patch for good measure tonight.

Edit: It worked perfectly and it did resolve the boot loop.

Never seen the APFS Patch cause a boot toop, only an askew NVRAM. Suggest https://discussions.apple.com/docs/DOC-3603 as a good practice before an install or upgrade.

 

[nospamboz]

There is no reason to cling to HFS+ with Mojave. It simply makes updates a PITA.

Hey, as long as I don't have to use a paper tape reader, I'm OK with it. ;P

As far as I know, there is no free full R/W APFS support in Linux, which I also boot into. HFS+ suits me for now.

 

[K two]

SilentKnight strikes, again.

 

[Rob1n]

@dosdude1 recommends NOT using the ROM patcher on NVIDIA machines. FWIW The APFS patch installed by the v.1.3.7 patcher works just fine but not as "clean", scrolling text at boot, etc.

Sorry, my fault. I meant intel. I have edited my post for future reference.

 

[Rob1n]

Edit: It worked perfectly and it did resolve the boot loop.

Nice! Well done!

 

[iMacUser2007]

I didn't know about SilentKnight before I visited this forum and it's great. I'm running Mojave HFS on an iMac 7,1 (with an upgraded processor) and I just used SK to update XProtect, Gatekeeper and MRT. Of course I'm still waiting for 2021-001 but I was surprised I could use SK on HFS Mojave to update those.

What I don't get: on my other Mac running latest Catalina with 2021-001 SK still found some updates! Anybody knows why or how this is possible? I always thought those were updated automatically with every security update...

 

[K two]

I didn't know about SilentKnight before I visited this forum and it's great. I'm running Mojave HFS on an iMac 7,1 (with an upgraded processor) and I just used SK to update XProtect, Gatekeeper and MRT. Of course I'm still waiting for 2021-001 but I was surprised I could use SK on HFS Mojave to update those.

What I don't get: on my other Mac running latest Catalina with 2021-001 SK still found some updates! Anybody knows why or how this is possible? I always thought those were updated automatically with every security update...

Probably found MRT and a Safari update?

 

[iMacUser2007]

Probably found MRT and a Safari update?

Unfortunately I don't remember which ones were updated on the Catalina MacBook – but since it was running the latest Catalina release (including security updates) imo there shouldn't be any more updates. Are MRT/Gatekeeper etc. updates not installed automatically?

 

[K two]

Hey, as long as I don't have to use a paper tape reader, I'm OK with it. ;P

As far as I know, there is no free full R/W APFS support in Linux, which I also boot into. HFS+ suits me for now.

APFS and HFS+ partitions can peacefully co-exist on the same HDD or SSD.

 

[K two]

Unfortunately I don't remember which ones were updated on the Catalina MacBook – but since it was running the latest Catalina release (including security updates) imo there shouldn't be any more updates. Are MRT/Gatekeeper etc. updates not installed automatically?

If the S/W Update CP/Advanced is set to do so. Yes.

 

[macinfo]

@alphascorp, I wonder how you did patch the 'cog wheels' graphic (from BS?) in the system preferences window? I’d like to carry out this modification as well, because that is the only one icon I find not fitting well with the otherwise sleek Mojave look and feel. Changing of the app and dock icon should be more straight forward, I assume.

Many thanks in advance!

[EDIT]

I found these resources should be located in Big Sur at:

/System/Applications/System Preferences.app/Contents/Resources/Assets.car

As I don’t have Big Sur installed on any machine yet, I hope these can also be located in the full installer package.

 

[alphascorp]

@alphascorp, I wonder how you did patch the 'cog wheels' graphic (from BS?) in the system preferences window? I’d like to carry out this modification as well, because that is the only one icon I find not fitting well with the otherwise sleek Mojave look and feel. Changing of the app and dock icon should be more straight forward, I assume.

Many thanks in advance!

View attachment 1725282
[EDIT]

I found these resources should be located in Big Sur at:

/System/Applications/System Preferences.app/Contents/Resources/Assets.car

As I don’t have Big Sur installed on any machine yet, I hope these can also be located in the full installer package.

Hi @macinfo

System Preferences icon is PrefApp.icns file located in /System/Applications/System Preferences.app/Contents/Resources/

But for SoftwareUpdate it's in /S/L/SoftwareUpdate.prefpane
There are 2 files to replace ( SoftwareUpdate.icns and SoftwareUpdatePreferencePaneIcon.tiff ) in /System/Library/PreferencePanes/SoftwareUpdate.prefpane/Contents/Resources/
I extracted SoftwareUpdate.icns from Big Sur but I had to create SoftwareUpdatePreferencePaneIcon.tiff because it contains 2 formats (80 × 80 pixels 144 pixels/inch and 40 × 40 pixels 72 pixels/inch)

I enclose a SoftwareUpdate.icns.zip archive containing the 2 files for SoftwareUpdate.prefpane, and another PrefApp.icns.zip archive containing the icon for System Preferences.app

After replacing these files you have to correct the permissions with Terminal:

sudo chmod 644 /System/Library/PreferencePanes/SoftwareUpdate.prefPane/Contents/Resources/SoftwareUpdate.icns

sudo chown 0:0  /System/Library/PreferencePanes/SoftwareUpdate.prefPane/Contents/Resources/SoftwareUpdate.icns

sudo chmod 644 /System/Library/PreferencePanes/SoftwareUpdate.prefPane/Contents/Resources/SoftwareUpdatePreferencePaneIcon.tiff

sudo chown 0:0  /System/Library/PreferencePanes/SoftwareUpdate.prefPane/Contents/Resources/SoftwareUpdatePreferencePaneIcon.tiff

sudo chmod 644 /System/Applications/System\ Preferences.app/Contents/Resources/PrefApp.icns

sudo chown 0:0  /System/Applications/System\ Preferences.app/Contents/Resources/PrefApp.icns

 

[macinfo]

Thank you very much @alphascorp, it’s really appreciated!

 

[honeycombz]

So what’s the deal? Just updated yo Mojave two weeks ago. Everything is going swimmingly. If I try to install this latest sec update am I going to f everything up?

 

[K two]

So what’s the deal? Just updated yo Mojave two weeks ago. Everything is going swimmingly. If I try to install this latest sec update am I going to f everything up?

So far, Build 18G8012 performs w/o issues. Very stable on Mini3,1 and iMac10,2. If APFS can update w/SilentKnight.

 

[vdeal]

Video issues here. Running a MacPro 4.1 which had previously been updated through various macOSes with dosdude1's patcher. Used the Mojave Patcher and things went fine but I only had one of my two monitors working. Was running the stock Nvidia GeForce GT120. Went back and installed the Legacy Video Card Patch and both monitors started working. I did have strange coloration/video effects on the tabs in Safari - the one in use is black and if you move the cursor over it it pixelates gray. Decided to update to a Metal-compatible card so I got an AMD Radeon HD7950. Before installing I had removed the legacy video card driver from the installed patches plist. Machine booted fine but only one monitor is working again. Tried the AMD card patcher and the Legacy Video card patcher and neither help w/ either the dual monitors or the Safari strangeness. Any suggestions? At this point I'd be better off going back to the stock card. Thanks.

 

[brian.tully]

There is no reason to cling to HFS+ with Mojave. It simply makes updates a PITA.

The main reason to cling to HFS+ is attempting to convert to APFS twice, and both times the boot screen shows "Boot file not found, exiting..."

I am literally slamming my head against the wall because I thought that I'd be successful this time around. What a waste of time.

It doesn't seem like it's possible to boot a MacPro 3,1 from APFS using dosdude's Mojave Patcher, so I'm not really sure what that "APFS patch" checkbox is for. So frustrating. Here are the steps I followed in case anyone wants to enlighten me as to what I am doing wrong:

1. My boot volume was HFS+. I booted from the Mojave Patcher USB
2. Opened Disk Utility and unmounted my boot volume "Macintosh HD"
3. Selected my unmounted boot volume and chose "Edit -> Convert to APFS"
4. After a few minutes, the drive was converted and mounted
5. Reinstalled Mojave (probably unnecessary, but just in case Mojave would add apfs.efi when installing)
6. After install complete, rebooted into Mojave Patcher again and opened "Post Install Patcher"
7. Selected my model (MacPro 3,1) and this time when I selected my boot volume, the "APFS Patch" was not greyed out, so I was able to select it.
8. I ran the post install patcher, and when complete, chose force cache rebuild and restart
9. Mac boots up into weird terminal screen, showing a bunch of commands, the end of which states "Boot file not found, exiting"
10. Redo steps 6 - 8 to make sure the APFS patch get applied
11. Same error message on reboot
12. Try several methods of manually creating a Preboot volume directory and copying the contents of /Volumes/Macintosh\ HD/System/Library/CoreServices to /Volumes/Preboot/[UUID]/System/Library/CoreServices, but any time I try doing the copy command I get errors saying file doesn't exist on the target and all sorts of file attr errors, so it's like the Preboot volume isn't mounted or read/writeable

Am I farked again and forced to reformat my boot volume back to HFS+ and do another 14 hour restore from Time Machine backup?

Or is there some kind soul who can help me get out of this hole with a gentle hand?