macOS 10.15 Catalina on Unsupported Macs

[K two]

I am a bit out of the loop. So I installed on my MP 5,1 Catalina 10.15.5 some time ago using @dosdude1 patcher (thanks). What is the easiest way now to bump it to the latest Catalina version 10.15.7 ? Is it via dosdude1 patcher again or via OTA by installing CatalinaOTAswufix.app (if that is even possible this way) ?

After running CatalinaOTAswufix.app what does the Software Update CP offer? Opt-out under Details to avoid any Beta offering. Or Just install H15 on top of .5, you won't lose anything. Update w/CatalinaOTAswufix.app from there. A USB may be necessary? If running with OpenCore either a createinstallmedia or @dosdude1 v.1.4.4 w/no patches selected USB will work.

 

[stiwi]

After running CatalinaOTAswufix.app what does the Software Update CP offer? Opt-out under Details to avoid any Beta offering. Or Just install H15 on top of .5, you won't lose anything. Update w/CatalinaOTAswufix.app from there. A USB may be necessary?

Good question really. In the end I have followed your method described few pages back, with the only difference being the 19H15 is under "6" number and not "5" right now. Can someone explain if going forward with CatalinaOTAswufix.app is the right way to get next security updates through "software update" ?

 

[K two]

Good question really. In the end I have followed your method described few pages back, with the only difference being the 19H15 is under "6" number and not "5" right now. Can someone explain if going forward with CatalinaOTAswufix.app is the right way to get next security updates through "software update" ?

Run CatalinaOTAswufix.app now but after opting-out, any update shown is good. 19H1217 s/b next, 2021-003.

 

[stiwi]

Run CatalinaOTAswufix.app now but after opting-out any update shown is good.

I have followed @jackluke post , applied CatalinaOTAswufix.app software update fix, opted out from any beta and set "check for updates" only.

I got the following Security update: macOS Catalina Security Update 2021-003 10.15.7 –– Restart Required
Shall I proceed?

It even allows me to upgrade to Big Sur on my Mac Pro 5,1 (RX 580), would that be as simple as that...?

 

[K two]

I have followed @jackluke post , applied CatalinaOTAswufix.app software update fix, opted out from any beta and set "check for updates" only.

I got the following Security update: macOS Catalina Security Update 2021-003 10.15.7 –– Restart Required
Shall I proceed?

It even allows me to upgrade to Big Sur on my Mac Pro 5,1 (RX 580), would that be as simple as that...?

Start the Update and immediately apply the OTA Update Fix button, that's it if Metal GPU on OpenCore. If not re-patching is required.

 

[stiwi]

Start the Update and immediately apply the OTA Update Fix button, that's it if Metal GPU on OpenCore. If not re-patching is required.

I don't use OpenCore, is it worth looking at compared to the existing mods available? It sounds a bit more risky.

I run the macOS Catalina Security Update 2021-003 10.15.7 and once it started downloading I applied "OTA update fix" from CatalinaOTAswufix.app. I have 19H1217 now but I must say it took quite some time to update.

So If I would not click on "OTA update fix" while downloading the security update, I would have to apply the 2 usual fixes (app compatibility and night shift) and 2x reboot, right?

 

[RogueB]

Hello @Ausdauersportler

MacBook Pro 5,2 (mid 2009), SSD. Catalina and Mojave installed on one (shared) partition, with Big Sur 11.5 installed on second (separate) partition.

Just successfully updated Catalina 10.15.7 with the latest security patch via jackluke's update CatalinaOTAswufix, followed by dosdude1's patcher. I have a Big Sur 11.5 installed (via OCLP 0.1.5) on same SSD, but different partition.

In process of applying security update to Catalina I noticed that, after auto-reboot, machine booted into the OCLP disk picker, rather than Apple's. I continued installation by selecting macos-installer icon (it was not chosen automatically).

When installation completed and I rebooted holding the option key, machine again booted into OCLP disk picker, and I chose to boot from USB drive containing Dosdude1's patches. Once I lunched post-install patches (from USB drive) I noticed that none of the patch choices were pre-selected, nor was my computer's bios displayed. Under the circumstances I would expect this oucome if OCLP was globally applied(?) I selected necessary patches manually, and applied them successfully. On reboot into fully functional Catalina OS I checked the "about this mac" information and noted that my MacBook Pro 5,2 was listed as MacBook Pro 11,3 with firmware designation of 999.999, etc. It seems I inadvertently created a hybrid system with OCLP functionality (model spoofing), while maintaining compatibility with Dosdude1's patcher functions.

Note, that I did install OCLP 0.1.5 on the internal (SATA) SSD, but I assumed it would be only relevant to partition containing Big Sur; it seems OCLP became universal for the whole disk(?) Just curious if others experienced this behavior. I have no complaints, and my inquiry is driven by curiosity.

Thank you again, for the superb work, to all the developers listed in this post, as well as, many other contributors.

 

[K two]

I don't use OpenCore, is it worth looking at compared to the existing mods available? It sounds a bit more risky.

I run the macOS Catalina Security Update 2021-003 10.15.7 and once it started downloading I applied "OTA update fix" from CatalinaOTAswufix.app. I have 19H1217 now but I must say it took quite some time to update.

So If I would not click on "OTA update fix" while downloading the security update, I would have to apply the 2 usual fixes (app compatibility and night shift) and 2x reboot, right?

Not selecting will make the 2nd phase MacOS installer unavailable.

 

[stiwi]

Not selecting will make the 2nd phase MacOS installer unavailable.

So the only inconvenience is to remember applying "OTA update fix", as otherwise it won't install the update at all?

 

[K two]

So the only inconvenience is to remember applying "OTA update fix", as otherwise it won't install the update at all?

Right, it will just re-boot into the previous install. To make it work if that happens, one must go to Library/Updates ƒ and delete everything within and start over, again. 😵‍💫

 

[trifero]

I have updated to 19H1217 without problems.

 

[Ausdauersportler]

Hello @Ausdauersportler

MacBook Pro 5,2 (mid 2009), SSD. Catalina and Mojave installed on one (shared) partition, with Big Sur 11.5 installed on second (separate) partition.

Just successfully updated Catalina 10.15.7 with the latest security patch via jackluke's update CatalinaOTAswufix, followed by dosdude1's patcher. I have a Big Sur 11.5 installed (via OCLP 0.1.5) on same SSD, but different partition.

In process of applying security update to Catalina I noticed that, after auto-reboot, machine booted into the OCLP disk picker, rather than Apple's. I continued installation by selecting macos-installer icon (it was not chosen automatically).

When installation completed and I rebooted holding the option key, machine again booted into OCLP disk picker, and I chose to boot from USB drive containing Dosdude1's patches. Once I lunched post-install patches (from USB drive) I noticed that none of the patch choices were pre-selected, nor was my computer's bios displayed. Under the circumstances I would expect this oucome if OCLP was globally applied(?) I selected necessary patches manually, and applied them successfully. On reboot into fully functional Catalina OS I checked the "about this mac" information and noted that my MacBook Pro 5,2 was listed as MacBook Pro 11,3 with firmware designation of 999.999, etc. It seems I inadvertently created a hybrid system with OCLP functionality (model spoofing), while maintaining compatibility with Dosdude1's patcher functions.

Note, that I did install OCLP 0.1.5 on the internal (SATA) SSD, but I assumed it would be only relevant to partition containg Big Sur; it seems OCLP became universal for the whole disk(?) Just curious if others experienced this behavior. I have no complaints, and my inquiry is driven by curiosity.

Thank you again, for the superb work, to all the developers listed in this post, as well as, many other contributors.

While I am using OLCP just to install Catalina and need no further patching your system needs the @dosdude1 patches. When using and booting trough OpenCore your system gets another identity of a newer still Apple supported system and thus the installer will no complain and does his job.

At the very end you need to get rid of OCLP again. Do a PRAM reset, boot into the @dosdude1 patched USB installer and apply all patches. This time the correct identity of your 2009 macbook will be detected by the patcher and the correct patches will be applied.

Install and use OLCP again when the next update swing has to be made.

 

[K two]

While I am using OLCP just to install Catalina and need no further patching your system needs the @dosdude1 patches. When using and booting trough OpenCore your system gets another identity of a newer still Apple supported system and thus the installer will no complain and does his job.

At the very end you need to get rid of OCLP again. Do a PRAM reset, boot into the @dosdude1 patched USB installer and apply all patches. This time the correct identity of your 2009 macbook will be detected by the patcher and the correct patches will be applied.

Install and use OLCP again when the next update swing has to be made.

OCLP spoofing does not prevent manually selecting the actual Mac when using a @dosdude1 patcher. No NVRAM reset required. 😎

 

[stiwi]

Right, it will just re-boot into the previous install. To make it work if that happens, one must go to Library/Updates ƒ and delete everything within and start over, again. 😵‍💫

I am getting the following pop-ups after installing the latest security patch (with OTA update fix) and running 19H1217:

“Patch Updater” cannot be opened because the developer cannot be verified.

I have approved it in security settings but I am still getting it every hour or so... I can access Patch Updater successfully from System Preferences. Any idea how to fix it?

EDIT: Ok I found Patch Updater in Utilities folder, run it it and approved again in the Security & Privacy option, let's see if it helps.

 

[K two]

I am getting the following pop-ups after installing the latest security patch (with OTA update fix) and running 19H1217:

“Patch Updater” cannot be opened because the developer cannot be verified.

I have approved it in security settings but I am still getting it every hour or so... I can access Patch Updater successfully from System Preferences. Any idea how to fix it?

EDIT: Ok I found Patch Updater in Utilities folder, run it it and approved again in the Security & Privacy option, let's see if it helps.

Install the Validation Patch Update, seems to help some.🧐

 

[RogueB]

While I am using OLCP just to install Catalina and need no further patching your system needs the @dosdude1 patches. When using and booting trough OpenCore your system gets another identity of a newer still Apple supported system and thus the installer will no complain and does his job.

At the very end you need to get rid of OCLP again. Do a PRAM reset, boot into the @dosdude1 patched USB installer and apply all patches. This time the correct identity of your 2009 macbook will be detected by the patcher and the correct patches will be applied.

Install and use OLCP again when the next update swing has to be made.

Thanks for your reply.

I arrived at same conclusion, however, at this point in time I see no adverse effects with both, dosdude1's patcher and OCLP, existing side by side. I will still initiate updates to Catalina via @jackluke's CatalinaOTAswufix.app, but let OCLP act as bootloader. I am aware of which of dosdude's post-intall patches I need to apply, so I can choose those items manually. If I run into problems while maintaining this "hybrid" system I will share that information.

 

[pullman]

I'm trying to understand the below text from the wiki post.

I have a 3,1 with an Nvidia Quadro M4000 which means that I'm stuck at High Sierra. Does the below mean that those old cards will give boot screen but that more current AMD cards will work too?

Also there's something in the wiki post about multiple EEPROM and risks with regard to APFS. How do I know if I my system has multiple EEPROM?

Video Card Support
Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.)
Pre-Metal Nvidia video cards (GeForce 5xx series and older without acceleration, GeForce 3xx Series and older with acceleration i.e. 8600M(GT)/8800M(GT), 9400M/9600M(GT), 320M/330M)
Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)

 

[K two]

Hello @Ausdauersportler

MacBook Pro 5,2 (mid 2009), SSD. Catalina and Mojave installed on one (shared) partition, with Big Sur 11.5 installed on second (separate) partition.

Just successfully updated Catalina 10.15.7 with the latest security patch via jackluke's update CatalinaOTAswufix, followed by dosdude1's patcher. I have a Big Sur 11.5 installed (via OCLP 0.1.5) on same SSD, but different partition.

In process of applying security update to Catalina I noticed that, after auto-reboot, machine booted into the OCLP disk picker, rather than Apple's. I continued installation by selecting macos-installer icon (it was not chosen automatically).

When installation completed and I rebooted holding the option key, machine again booted into OCLP disk picker, and I chose to boot from USB drive containing Dosdude1's patches. Once I lunched post-install patches (from USB drive) I noticed that none of the patch choices were pre-selected, nor was my computer's bios displayed. Under the circumstances I would expect this oucome if OCLP was globally applied(?) I selected necessary patches manually, and applied them successfully. On reboot into fully functional Catalina OS I checked the "about this mac" information and noted that my MacBook Pro 5,2 was listed as MacBook Pro 11,3 with firmware designation of 999.999, etc. It seems I inadvertently created a hybrid system with OCLP functionality (model spoofing), while maintaining compatibility with Dosdude1's patcher functions.

Note, that I did install OCLP 0.1.5 on the internal (SATA) SSD, but I assumed it would be only relevant to partition containing Big Sur; it seems OCLP became universal for the whole disk(?) Just curious if others experienced this behavior. I have no complaints, and my inquiry is driven by curiosity.

Thank you again, for the superb work, to all the developers listed in this post, as well as, many other contributors.

Correct. OCLP is installed unto the entire disk not just the partition. The Boot Picker comes in handy in any event.

 

[Ausdauersportler]

Correct. OCLP is installed unto the entire disk not just the partition. The Boot Picker comes in handy in any event.

It is even better. You might only need to install the legacy video patches since OCLP may provide the other functionality by injection. But this would have to be tested on a case by case base. OCLP is not just some OpenCore. It comes with nearly all functionality out of the box (planned to be used for Big Sur). Check what is already working before applying the @dosdude1 patches. You may already have working USB, WIFI, Ethernet...

EDIT:
On the iMac11,x and iMac12,2 with a metal GPU one can use OCLP with moderate spoofing to install and maintain Mojave or Catalina without using ANY @dosdude1 patches at all.
Just to be clear: After installing and booting OCLP one can use an unpatched original Apple installer to get Catalina and Mojave on the systems. Updates work without any patching or using other third party software just like on a completely supported system.

 

[stiwi]

Start the Update and immediately apply the OTA Update Fix button, that's it if Metal GPU on OpenCore. If not re-patching is required.

Issue is: every time I reboot my Mac Pro 5,1 I now get the following message from Patch Updater:

System Patches Overwritten:

"Patch Updater has detected that some system patches have been overwritten, and need to be re-installed. Not re-installing these patches may result in some system functionality issues. The following patches will need to be re-installed:

- Night Shift Patch"

I click on re-install patches, reboot and same all over again.

EDIT: I have re-installed all patches again from Patch Updater, then upon reboot I got notification about Night Shift Patch which I re-installed once again, rebooted and now it seems okay.

 

[K two]

It is even better. You might only need to install the legacy video patches since OCLP may provide the other functionality by injection. But this would have to be tested on a case by case base. OCLP is not just some OpenCore. It comes with nearly all functionality out of the box (planned to be used for Big Sur). Check what is already working before applying the @dosdude1 patches. You may already have working USB, WIFI, Ethernet...

EDIT:
On the iMac11,x and iMac12,2 with a metal GPU one can use OCLP with moderate spoofing to install and maintain Mojave or Catalina without using ANY @dosdude1 patches at all.
Just to be clear: After installing and booting OCLP one can use an unpatched original Apple installer to get Catalina and Mojave on the systems. Updates work without any patching or using other third party software just like on a completely supported system.

LOL. Metallizing the iMac11,2 is on the to-do list. OCLP v.0.1.6 has matured enough for daily use. Nagging to dig into the documentation reminds of the good professors who actually teach, many thanks for that. Your work and that of your cohorts has produced a great tool. Congratulations. 🤝

 

[Macbook_catalina]

Thanks a lot to all of you.

 

[deamondev19995]

macOS catalina is required graphics card above intel hd 3000 or also check it you using second generations motherboard such sandy bridge. I have seen mojave work for intel hd 3000 by adding some patch in your efi partition

 

[trifero]

macOS catalina is required graphics card above intel hd 3000 or also check it you using second generations motherboard such sandy bridge. I have seen mojave work for intel hd 3000 by adding some patch in your efi partition

HD3000 works great in Catalina

 

[Mac_tech]

Help, could someone point me in the right direction? I’m trying to install macOS Catalina on a iMac, 10,1 that was running High Sierra before. I get this message during install after 23 minutes remaining. When I boot it goes into the install loop. The drive is APFS but after three attempts I get the same message. I used the patch from @dosdude1