macOS 10.14 Mojave on Unsupported Macs Thread

[RK78]

Looks like alphascorp inadvertently gave us the wrong link. Was able to track down the proper one first from

URLs of the index files used by the software update client on OS X

URLs of the index files used by the software update client on OS X - osx-software-update-urls.md

gist.github.com

Next from (think the one he gave us appears here as well)

~/Desktop/index-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog:91417: <string>http://swcdn.apple.com/content/down...5fx2ccb8gdg28tqtllz0/SecUpd2021-005Mojave.pkg</string>


Finally the correct link for the 2021-005 package

http://swcdn.apple.com/content/downloads/33/28/071-44390-A_IQ4DD9ZA9P/xzbo7vu5wumlpv5fx2ccb8gdg28tqtllz0/SecUpd2021-005Mojave.pkg

Installed it to an HFS+ external and appears to work fine. Only issue is, and I don't think it's related to this specific package, as I've seen this before with other installers, it hangs on "Setting Up Your Mac" (seems to get things confused.*) Might not happen for you. Fixed with a hard shutdown and then was able to proceed.

Note: my head is spinning from all the hoops I jumped through to get to the final link. I'm certain about the final link to the installer, but not 100% certain about how I got to it, above. Anyway, no matter, the final link is the one that matters.

*EDIT: just installed to iMac. Didn't go through the "Setting Up Your Mac" freeze there. Guess YMMV. Also this time, to my relief, it's showing up in System Information->Installations.

 

[VaZ]

Curious as to why this package is almost half the size of the last one if it includes all the previous tweaks and doesn't need modifications to the Distribution file installing to an hfs+ drive?

 

[RK78]

Curious as to why this package is almost half the size of the last one if it includes all the previous tweaks and doesn't need modifications to the Distribution file installing to an hfs+ drive?

Can only answer the second question, which is that since it's already a package, doesn't need editing the way the full standalone does. Looked at it with Pacifist, but not seeing anything obviously missing, but not all qualified to analyze it in depth.

EDIT: crossed my mind that perhaps this is a delta, not the combo, which would explain the difference in size. That's why, in fact, before installing to that external, as a test, I checked that it had already run the 2021-004.

 

[VaZ]

Ah yes delta that could be the explanation.. So then this shouldn't be used on a fresh 10.14.6 install without any updates done to it?

 

[RK78]

Probably best to wait for the standalone, which I'm thinking should be along pretty soon now.

 

[Pralaya]

Looks like alphascorp inadvertently gave us the wrong link. Was able to track down the proper one first from

URLs of the index files used by the software update client on OS X

URLs of the index files used by the software update client on OS X - osx-software-update-urls.md

gist.github.com

Next from (think the one he gave us appears here as well)

~/Desktop/index-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog:91417: <string>http://swcdn.apple.com/content/down...5fx2ccb8gdg28tqtllz0/SecUpd2021-005Mojave.pkg</string>


Finally the correct link for the 2021-005 package

http://swcdn.apple.com/content/downloads/33/28/071-44390-A_IQ4DD9ZA9P/xzbo7vu5wumlpv5fx2ccb8gdg28tqtllz0/SecUpd2021-005Mojave.pkg

Installed it to an HFS+ external and appears to work fine. Only issue is, and I don't think it's related to this specific package, as I've seen this before with other installers, it hangs on "Setting Up Your Mac" (seems to get things confused.*) Might not happen for you. Fixed with a hard shutdown and then was able to proceed.

Note: my head is spinning from all the hoops I jumped through to get to the final link. I'm certain about the final link to the installer, but not 100% certain about how I got to it, above. Anyway, no matter, the final link is the one that matters.

*EDIT: just installed to iMac. Didn't go through the "Setting Up Your Mac" freeze there. Guess YMMV. Also this time, to my relief, it's showing up in System Information->Installations.

This worked for me, thanks a lot!?

 

[K two]

The joys of APFS Mojave OTA updates everything available updated like auto-pilot w/SilentKnight. However, when updating the post-install patches w/v.1.3.7 USB Mojave Patcher make certain the Force Cache Rebuild function takes a few seconds to run, if not reboot into USB and re-install patches, reboot w/Force Cache Rebuild. The only minor fly in the sauce. ?

?

 

[symm]

Mac Mini 5,2 (mid-2011) running High Sierra on APFS formatted SSD.

I followed all the directions except the Install Mojave app was downloaded two days ago via the installinstallmacos.py script, but the Mojave Patcher app verified the installer app.

I erased a high quality 16GB USB and formatted as Mac OS (Journaled). The flash drive is one that I've successfully used for Catalina (most recently, on another Mac) and other Mac OS installers over the years and setup via Patcher app. there were no failure/error messages.

But the USB stick fails to boot (after USB drive selection) and displays a gray circle slash before restarting. I've retried a few times with hot and cold boots as well as rerunning patch app and setting up another flash drive but it refuses to boot/run the Mojave installer.

Any ideas? My Google Fu has failed me. All hits are for already patched systems that fail after some time.

Thanks.

 

[Dilli]

Mac Mini 5,2 (mid-2011) running High Sierra on APFS formatted SSD.

I followed all the directions except the Install Mojave app was downloaded two days ago via the installinstallmacos.py script, but the Mojave Patcher app verified the installer app.

I erased a high quality 16GB USB and formatted as Mac OS (Journaled). The flash drive is one that I've successfully used for Catalina (most recently, on another Mac) and other Mac OS installers over the years and setup via Patcher app. there were no failure/error messages.

But the USB stick fails to boot (after USB drive selection) and displays a gray circle slash before restarting. I've retried a few times with hot and cold boots as well as rerunning patch app and setting up another flash drive but it refuses to boot/run the Mojave installer.

Any ideas? My Google Fu has failed me. All hits are for already patched systems that fail after some time.

Thanks.

Sometimes flash drive are not compatible always with the OS. If you have another flash drive try it. Grey circle slash is an indicator that your USB stick has not been installed fully and is missing the hidden EFI drivers. As suggested try another stick and make the usb installer. Good Luck

 

[symm]

Mac Mini 5,2 (mid-2011) running High Sierra on APFS formatted SSD.

I followed all the directions except the Install Mojave app was downloaded two days ago via the installinstallmacos.py script, but the Mojave Patcher app verified the installer app.

I erased a high quality 16GB USB and formatted as Mac OS (Journaled). The flash drive is one that I've successfully used for Catalina (most recently, on another Mac) and other Mac OS installers over the years and setup via Patcher app. there were no failure/error messages.

But the USB stick fails to boot (after USB drive selection) and displays a gray circle slash before restarting. I've retried a few times with hot and cold boots as well as rerunning patch app and setting up another flash drive but it refuses to boot/run the Mojave installer.

Any ideas? My Google Fu has failed me. All hits are for already patched systems that fail after some time.

Thanks.

OK, pretty sure I have it worked out. I had expanded verbose output to get more details and severely underestimated the time to patch. The verbose output unhelpfully only covers the original installer imaging and stops test output with with "Done". I missed the lack of the progress bar completion and the patcher app doesn't warn on quit despite the patching not being complete. Nor was there any text output indicating patching was started/in progress. A simple "Patching..." would have been greatly appreciated.

After a long time, it finally finished with no further "verbose" output but a subtle and small "Completed" text above the progress bar, not in the verbose text field or any other feedback e.g. dialog or sound.

The low contrast "prohibited" graphic was Apple's "helpful" of half-ass informing that the installer boot volume wasn't supported. I guess some explanatory text or a dialog box would have cut into their profits too much. /s

Any way the fix was simple if not very obvious to this new user of the app.

Successfully booted and installing Mojave now.

I hope this helps someone else.

 

[symm]

OK, pretty sure I have it worked out. I had expanded verbose output to get more details and severely underestimated the time to patch. The verbose output unhelpfully only covers the original installer imaging and stops test output with with "Done". I missed the lack of the progress bar completion and the patcher app doesn't warn on quit despite the patching not being complete. Nor was there any text output indicating patching was started/in progress. A simple "Patching..." would have been greatly appreciated.

After a long time, it finally finished with no further "verbose" output but a subtle and small "Completed" text above the progress bar, not in the verbose text field or any other feedback e.g. dialog or sound.

The low contrast "prohibited" graphic was Apple's "helpful" of half-ass informing that the installer boot volume wasn't supported. I guess some explanatory text or a dialog box would have cut into their profits too much. /s

Any way the fix was simple if not very obvious to this new user of the app.

Successfully booted and installing Mojave now.

I hope this helps someone else.

Damn, started upgrade installation over High Sierra OK but failed with "Undefined Error: 0".

This has been harder than installing Mojave on an upgraded classic Mac Pro with OpenCore. I chose this as it was supposed to be easier and the Mini 5,2 was supported (2011 vs 2009 hardware).

 

[symm]

Damn, started upgrade installation over High Sierra OK but failed with "Undefined Error: 0".

This has been harder than installing Mojave on an upgraded classic Mac Pro with OpenCore. I chose this as it was supposed to be easier and the Mini 5,2 was supported (2011 vs 2009 hardware).

OK second time (or 36th...) was the charm. Restarting and installing again completed without the undefined error.

I appreciate the tool and the hard work that went into this. It was a little rougher than I hoped but some of that was my inclination to go straight to verbose mode and missing the more subtle progress feedback.

 

[bazman1995]

Thanks. I wiped and converted my MacBook 5,1 partition to apfs, and installed Mojave from scratch with the USB installer. Repatched using the dosdudebpatcher tool and then Updates were available in software update panel

Installed them and had to repatch again, Everything was working great but then installed Google chrome which has all my necessary shortcuts but it’s instantly started doing the blank screen thing and freezing, (gpu hardware acceleration problem?) so inevitably moving on to tackle my next problem…

b.tw, Is there a known way of turning off chrome’s hardware acceleration without opening chrome to do it , because it’s non functional after ‘starting’?

I fixed the blank window problem with Chrome when upgrading a Mac Book Air Late 2010 3,2 from Yosemite to Mojave.

Here's how to turn off Chrome's hardware acceleration using startup options from the terminal shell... Create a file in the /Applications/ directory with this contents without an extension, eg 'chrome_no_gpu'

#!/usr/bin/env bash
cd /Applications/Google\ Chrome.app/Contents/MacOS/
./Google\ Chrome --disable-gpu-sandbox

Using the terminal set the executable permissions so that the script will run:

cd /Applications/
chmod 755 chrome_no_gpu

You can run the script by opening the file through Finder or through Spotlight.

Discovered this yesterday so I have only done brief testing. Video playback in YouTube works.

If you run into problems with other website this page has more options which may help:

https://gist.github.com/bangonkali/be61ab880c890c17cb3d

Funny thing is that after a day of using the new version of Safari on Mojave my wife now doesn't want to use chrome!

 

[Pralaya]

Now available:

Security Update 2021-005 (Mojave)​

Security Update 2021-005 (Mojave) - Apple Support

macOS Mojave Security Update 2021-005 (18G9323) is recommended for all users and improves the security of macOS.

support.apple.com

 

[markj3000]

Apologies for adding to an old post, but I too have this problem after installing Mojave via the DOSDUDE patch, though it only seems to be for Prores 422 HQ , 422 and lower. Other codecs seem ok (prores 4444, h264), but everything I have is stored as this 422 HQ. Doesn't look wrong in Premiere, or VLC & legacy QT 7 player, but its totally glitching in the native Quicktime player.

Did you ever find a fix?

I'm using MacBook late 2008, Mojave 10.14.6, 8gb RAM.

I installed Mojave on apfs on my ‘new’ Mac mini late 2009. It still shows QuickTime 422hq etc as if it was a corrupted green codec issue. I can mostly get around this by installing QuickTime 7 player and making it the default program for QuickTime files, but if I spacebar preview files it still uses OS X player to show the pop up previews that look corrupted. Does anyone use a patched machine for video editing and got this fixed somehow?

 

[K two]

I installed Mojave on apfs on my ‘new’ Mac mini late 2009. It still shows QuickTime 422hq etc as if it was a corrupted green codec issue. I can mostly get around this by installing QuickTime 7 player and making it the default program for QuickTime files, but if I spacebar preview files it still uses OS X player to show the pop up previews that look corrupted. Does anyone use a patched machine for video editing and got this fixed somehow?

See #19,481 ?

 

[markj3000]

See #19,481 ?

Hmmm, sorry not sure how that post helps with my specific Quicktime issue. Everythings already been repatched after the security update, but still getting the corrupted video. This also happens on my Macbook 5,1 too with the same OS
version.

 

[K two]

Hmmm, sorry not sure how that post helps with my specific Quicktime issue. Everythings already been repatched after the security update, but still getting the corrupted video. This also happens on my Macbook 5,1 too with the same OS
version.


View attachment 1817711

Look harder. ?

 

[markj3000]

Well replacing the provided Mojave AppleGVA.framework with the one from High Sierra doesn't seem to have changed anything, apart from giving me a double window (one distorted as before and a new one with a blurred background) for a few seconds if I spacebar preview, if thats what you were inferring. Post #15,834
appleGVA.framework


Are the others relevant to this? I'm fine to leave them out if not.
softwareupdate.framework
HIToolbox
Siri.app
SiriUI.framework

 

[K two]

Well replacing the provided Mojave AppleGVA.framework with the one from High Sierra doesn't seem to have changed anything, apart from giving me a double window (one distorted as before and a new one with a blurred background) for a few seconds if I spacebar preview, if thats what you were inferring. Post #15,834
appleGVA.framework


Are the others relevant to this? I'm fine to leave them out if not.
softwareupdate.framework
HIToolbox
Siri.app
SiriUI.framework

If not AppleGVA Framework or HIToolbox you have uncovered a feature requiring a Metal GPU ?

And was the previous appleGVA.framework removed before applying the HS version?

 

[markj3000]

If not AppleGVA Framework or HIToolbox you have uncovered a feature requiring a Metal GPU ?

And was the previous appleGVA.framework removed before applying the HS version?

Yes I did remove the Mojave AppleGVA.framework folder before replacing with the High Sierra one in the link.

I may just have to accept on such old machines (2008/2009) that the Quick Look spacebar function and the native OSX Quicktime player cannot play some versions of ProRes (422, 422HQ), without severe artifacts caused by having a non metal graphics card.

I guess a 2012 MacBook pro/ mini onwards would be more compatible as they do support Metal, but then they would not need patching to run Mojave or Catalina....

 

[K two]

Yes I did remove the Mojave AppleGVA.framework folder before replacing with the High Sierra one in the link.

I may just have to accept on such old machines (2008/2009) that the Quick Look spacebar function and the native OSX Quicktime player cannot play some versions of ProRes (422, 422HQ), without severe artifacts caused by having a non metal graphics card.

I guess a 2012 MacBook pro/ mini onwards would be more compatible as they do support Metal, but then they would not need patching to run Mojave or Catalina....

Well stated. ??

 

[PamelaGirl80]

Hello Good People,
Can someone please explain why from time to time I get windows and pop up notification that is not readable / containing unidentifiable characters?

T.I.A.

 

[whitedb]

Am I trying the impossible? New install of Mojave on a MacPro 3,1 using and external Samsung SSD

I am trying to install Mojave on an external Samsung SSD plugged into the native USB2 port of my Mac Pro. This approach worked for High Sierra (with the disc formatted in HFS+ but it had to be the native port, not a USB3 on my PCI card). This time I tried APFS for the Mojave install.

Everything seems to work - I booted from the Patched USB stick, formatted the external drive and did the install followed by a second boot to the installer where I applied the patches. On the reboot, I got all the text scrolling through before the gray apple boot screen. The machine booted but had dropped back to El Capitan (I have several systems on the internal discs.)

I rebooted using the option command and my test system disc was not visible, the only USB attached devices were the Patched Mojave installer and and EFI drive.

Is it possible to install Mojave on an external USB attached drive on a 3,1? If not I will have to wipe one of my internal drives and try it there. I just wanted to see if it worked and could be updated before investing too much time. I had High Sierra working but the security update bricked it and I had to start again.

Thanks for any suggestions/information.

 

[Ausdauersportler]

Am I trying the impossible? New install of Mojave on a MacPro 3,1 using and external Samsung SSD

I am trying to install Mojave on an external Samsung SSD plugged into the native USB2 port of my Mac Pro. This approach worked for High Sierra (with the disc formatted in HFS+ but it had to be the native port, not a USB3 on my PCI card). This time I tried APFS for the Mojave install.

Everything seems to work - I booted from the Patched USB stick, formatted the external drive and did the install followed by a second boot to the installer where I applied the patches. On the reboot, I got all the text scrolling through before the gray apple boot screen. The machine booted but had dropped back to El Capitan (I have several systems on the internal discs.)

I rebooted using the option command and my test system disc was not visible, the only USB attached devices were the Patched Mojave installer and and EFI drive.

Is it possible to install Mojave on an external USB attached drive on a 3,1? If not I will have to wipe one of my internal drives and try it there. I just wanted to see if it worked and could be updated before investing too much time. I had High Sierra working but the security update bricked it and I had to start again.

Thanks for any suggestions/information.

Check out the OCLP. Makes even Big Sur running on your Mac…