Before we have another copy of the latest state duplicated here just scroll back to post #13,631 ...
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.15 Catalina on Unsupported Macs
- Thread starter 0403979
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Yes, I have read it twice.
"If your old Mac firmware can't boot an APFS partition, you need a loader that it can boot."
My Mac Pro can boot an APFS partition.
Do I am missing something ?
Okay, I am not an native English speaker:
But I would stop reading at this post at this line if I had a system booting APFS natively. So no OpenCore needed if you ask me.
Last edited:
Thank you very much for your help, K Two.
In which order are the two apps to be used? Do I need USBOpenCoreAPFSloader3 for updating to the latest OS build?
When comes the dosdude1 Catalina patcher into play?
I don't dare updating yet unless I have your instructions, as this is the only machine I have and can't take a risk. Pleass advise.
CatalinaOTAswufix.app goes first, follow the instructions, carefully. If your bootROM is patched, the USBOpenCoreAPFSloader3 is not needed, otherwise it is run from the Start-up Manager at first reboot to see the 'macOS installer' to complete the update. If the update fails for any reason, go to /Library/Updates ƒ and delete everything in there and start over. Be patient, it may take a few attempts. Good luck, if your power is intermittant wait until dependable power is on to do this.
Run the Start-up Manager at first reboot to see the 'macOS installer' to complete the update. If the update fails for any reason, go to /Library/Updates ƒ and delete everything in there and start over. Be patient, it may take a few attempts. Good luck, if your power is intermittant wait until dependable power is on to do this.
Just to make sure, I understood correctly: the 2 apps have to reside in the Applications folder and USBOpen...loader3 is automatically loaded during startup? And then after the update reboot into the macOS Base System with dosdude1's patcher on it and apply the patches again? Please advise
Hello,
My Mac Pro 3.1 is now running patched macOS Catalina with new Metal compatible MSI Frozr Nvidia 680.
Yesterday, I finally could plug my DisplayPort monitor to the Mac, because the Nvidia 680 has got DP connector.
So, then I started the Mac (booting the patched macOS Catalina). But nothing was showing on the DisplayPort Screen. The second screen, which is connected using HDMI was working fine. The DP screen was not even detected.
So then I tried booting in the officially supported, OSX El Capitan. And it all worked flawlessly.
Does anyone know, why my 2008 Mac Pro with MSI Frozr Nvidia 680 can't display ANYTHING on monitor plugged in to the DisplayPort connector on the GPU, when running macOS Catalina?
Any help is appreciated.
My Mac Pro 3.1 is now running patched macOS Catalina with new Metal compatible MSI Frozr Nvidia 680.
Yesterday, I finally could plug my DisplayPort monitor to the Mac, because the Nvidia 680 has got DP connector.
So, then I started the Mac (booting the patched macOS Catalina). But nothing was showing on the DisplayPort Screen. The second screen, which is connected using HDMI was working fine. The DP screen was not even detected.
So then I tried booting in the officially supported, OSX El Capitan. And it all worked flawlessly.
Does anyone know, why my 2008 Mac Pro with MSI Frozr Nvidia 680 can't display ANYTHING on monitor plugged in to the DisplayPort connector on the GPU, when running macOS Catalina?
Any help is appreciated.
Last edited:
I run CatalinaOTAswufix.app from the Downloads ƒ, and per the instructions built into OpenCoreAPFSloader3 a small USB disk or a tiny partition on the v.1.4.4 patcher USB. Both OpenCoreAPFSloader3 and the @dosdude1 patcher USB will appear in the Startup Manager at first restart if done per the built-in instructions, correctly.
K Two, thank you for your help! I managed to update just right now as per your instructions to build 19H1011 on my MBP4,1. Without your guidance I couldn't have don't it nor would have dard to do so. Thank you very very much.
Hm. Interesting, my OTA shows this as "newer" and I already have 19H1009.
Post below showed there is H1011 now...
So I´ll just try it out and report back.
This is weird. After resetting SMC, rebooting or shutting down now returns a code of 0 instead of 5. Something strange is going on...
Can anyone else with an MP3,1 see if they're getting similar results? I'm wondering if there's an actual issue with hardware, or if the patched OS is just misreporting the shutdown cause?
Thanks for the updated info. Much appreciated. 19H524 on this particular Mini does not show that Beta, as yet. A bit of a mystery, the second 19H524 Mini does not show that Beta, either. Will check the 19H1009 installs on that particular Mini, later on.Hm. Interesting, my OTA shows this as "newer" and I already have 19H1009.
Post below showed there is H1011 now...
So I´ll just try it out and report back.
Last edited:
Does anyone here got AppleTV content still working after Catalina dosdude install on a iMac 9,1 or similar? Just wondered why some movies turn black after some seconds. Sound is still there but the picture is black.
i need to deploy some unsupported offline catalina macs until 2022 so i wondered why this method stopped working:
forums.macrumors.com
install.log shows an authoring error so maybe it is because of code-signing?
i saw what jacklukem with CatalinaOTAswufix did to avoid checks - do you think this could be used somehow to get this method to work again?
macOS 10.15 Catalina on Unsupported Macs
Hi KennyW No, a .pkg cannot be opened with a simple right click, you have to use the Terminal "pkgutil --expand" command to extract the content. And after modifying the content, it is imperative to recreate the .pkg file with the terminal command "pkgutil --flatten" Here is the detailed...
forums.macrumors.com
i saw what jacklukem with CatalinaOTAswufix did to avoid checks - do you think this could be used somehow to get this method to work again?
i need to deploy some unsupported offline catalina macs until 2022 so i wondered why this method stopped working:
install.log shows an authoring error so maybe it is because of code-signing?macOS 10.15 Catalina on Unsupported Macs
Hi KennyW No, a .pkg cannot be opened with a simple right click, you have to use the Terminal "pkgutil --expand" command to extract the content. And after modifying the content, it is imperative to recreate the .pkg file with the terminal command "pkgutil --flatten" Here is the detailed...
i saw what jacklukem with CatalinaOTAswufix did to avoid checks - do you think this could be used somehow to get this method to work again?
Start with #19022 on this thread - https://forums.macrumors.com/threads/macos-10-14-mojave-on-unsupported-macs-thread.2121473/page-761 There has been some changes.
Cannot duplicate on Mini3,1. Movies run flawlessly to the end with 10.15.7 Build 19H524.
Apparently, U.S. servers were a little slow, earlier today.
Last edited:
My observations so far, still testing, compared to 19H15
+overall snappier
+ loading faster after restart
+nasty bug from 19H15, where applications wouldn't open or need several attempts to open, is gone!
+had to re-install Lulu, System Extension was being blocked by MacOS, running smoothly after re-install
--Time Machine stopped working, can't get it to run. Really nasty!!!
MRT was 1.62 had to update to 1.73. The Library Validation Patch wanted to update. Now, no issues whatsoever. Lower overhead than 19H524, as well. Video smooth at full resolution.
To get TM working, try running Onyx/Maintenance, the default settings are fine. After the app restarts , restart, again.
Last edited: