Successful update to macOS 10.15.7 (19H1011) using jackluke's CatalinaOTAswufix.app (Thanks!!) and finalizing with Dosdude 1.44 patcher. All working fine and smooth.....
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
I ran the patcher 1.4.4 from the default downloads ƒ where the app downoaded to from Safari.
The macOS was an original install, updated all the way from OS X Sierra...to Catalina.
TM had done this before, stopped working out of the blue, then I usually reformatted the TM external USB drive, and it worked again.
Can you make something of this?
Thanks very much for your help K Two.
The Patcher works best if run from the Applications ƒ or from Applications/Utilities ƒ and not the .DMG image, drag the Patcher from the .DMG into either of the aforementioned ƒ, also it seems that Apple changed some Security parameter and giving the installed Patcher v.1.4.4 Full Disk Access, Accessibility and Finder Automation access in the Security & Privacy CP may assure the integrity of the USB build.
Last edited:
Thank you for your advice, based on which I will proceed thus:
1. Re-create the USB drive "macOS Base System" as per your instructions from scratch
2. make sure of the parameters/permissions from System Preferences as mentioned afore
3. Re-patch 19H1011 from the freshly created Boot drive
4. Give TM a new shot
I will then report the outcome to you.
Thank you very much for your kind assistance K Two
'Force Cache Rebuild' post re-patch. Hopefully, a full re-install and CatalinaOTAswufix.app update won't be necessary?? ?
I'm trying to install Catalina on a mid-2009 MacBook Pro (11,4 MJLQ2LL/A Retina, 15-inch, mid-2015, 16 GB RAM, 1 TB SSD, Model A1398, EMC 2909, Integrated Graphics) using dosdude1’s "macOS Catalina Patcher.app" (v.1.4.4), but find that the installation repeatedly stalls partway through. I hope this is the proper forum to ask for advice; if not, I'd be grateful for a redirect. Many thanks in advance.
At what phase in the install does it stall? Black screen white progress bar? How was the USB built on the 09 MBP?
Last edited:
The installation USB is a new (but astonishingly slow!) 64 GB flash drive, erased and reformatted as OS X Extended (Journaled), GUID Partition Map, and built with dosdude1’s "macOS Catalina Patcher.app" (v.1.4.4, located in Applications/Utilities) using the “Create a Bootable Installer” option. After booting up the old MacBookPro holding dpwn the Option Key, I booted up new volume "EFI Boot", ran Disk Utility and erased/reformatted my 500 GB SSD as APFS. I then quit Disk Utility, selected “Reinstall macOS”. The install screen appears to be the typical one: a separate window entitled "Install macOS Catalina", with a round photo of the funky Catalina Island and "macOS Catalina" underneath. I selected the APFS SSD volume, agreed to the license, and a thin white progress bar appears with a blue progress indicator filling in from the left. The first time, it immediately stalled, with 13 minutes remaining. I shut down and tried again, made more progress than before, but it stalled out again with 10 minutes remaining. Repeat: 9 minutes. Repeat: 11 minutes. I note that the mouse/trackpad pointer becomes frozen at some point in the operation.
Try to run it again but open the log window. Also select "all messages" instead of "errors only". That way you can tell us more about the phase where your machine stalls, or throws an error msg.
The dreaded sudo bug - good news
Per CVE-2021-3156
The following versions of sudo are vulnerable:
All legacy versions from 1.8.2 to 1.8.31p2
All stable versions from 1.9.0 to 1.9.5p1
sudo -V
Result: MacOS 10.15.7 Build 19H524
Last login: Mon Feb 22 10:21:58 on ttys000
mini@MacMineeee ~ % sudo -V
Sudo version 1.9.5p2
Sudoers policy plugin version 1.9.5p2
Sudoers file grammar version 48
Sudoers I/O plugin version 1.9.5p2
Sudoers audit plugin version 1.9.5p2
19H524 is patched, as is 19H1011
Per CVE-2021-3156
The following versions of sudo are vulnerable:
All legacy versions from 1.8.2 to 1.8.31p2
All stable versions from 1.9.0 to 1.9.5p1
sudo -V
Result: MacOS 10.15.7 Build 19H524
Last login: Mon Feb 22 10:21:58 on ttys000
mini@MacMineeee ~ % sudo -V
Sudo version 1.9.5p2
Sudoers policy plugin version 1.9.5p2
Sudoers file grammar version 48
Sudoers I/O plugin version 1.9.5p2
Sudoers audit plugin version 1.9.5p2
19H524 is patched, as is 19H1011
Last edited:
How long did you wait before shut-downs? Often during @dosdude1 USB macOS installs progress appears to freeze, have patience the install will eventually complete.
Last edited:
Did as instructed, can confirm, did no re-install. No success. I still get the same error message that Time Machine can make no snapshot.
Also, re-naming the external USB drive to "Time Machine" did not solve the problem. (I had instances, in which I had to re-name a drive, in order for it to work, actually recently, when USBOpenCoreAPFSloader3 did not accept the designated USB drive under the name of "NO NAME", after renaming it to "Untitled" it worked)
Under no circumstance I can re-install the whole MacOS 10.15.7 19H1011 from scratch, since this MBP4,1 is the only machine, I own --
Is there anything left I can do to repair Time Machine?
As for now, I use CCC to make a bootable clone, but that is not the same thing as Time Machine.
Thank you very much indeed for your help K Two
The problem likely involves the macOS install rather than the patches. Agreed, getting TM to work is the best approach, CCC now 'owns' your BU. You can re-install on top the existing install, safely. Tedious, I know, but worth the effort. If possible, use 19H15 to build the USB, the final full release. Get it from gibMacOS-master or MDS.
Last edited:
I got a late 2009 27" iMac on the cheap the other day. It currently has a 1tb HDD (and 8gb ram) and High Sierra installed. My 500gb SSD is arriving on Wednesday and I'm going to swap out the 1tb HDD for the SSD. Is the firmware already updated to support APFS boot, since the machine already has High Sierra? Or would it only update the firmware if High Sierra had been installed on a SSD?
Basically, I don't know if I should install Catalina right onto the new SSD, or if I should install High Sierra on the new SSD first to trigger the firmware update, and then install Catalina over that.
Basically, I don't know if I should install Catalina right onto the new SSD, or if I should install High Sierra on the new SSD first to trigger the firmware update, and then install Catalina over that.
If the bootROM is already current install Catalina. Confirm, first. Go to: System Information/Hardware
Last edited:
Thanks a ton for your help. I must apologize... Apparently I didn't wait long enough; the installation had NOT stalled, but instead was just grinding along glacially - seemingly frozen - as a result of my absurdly slow flash new drive. The installation eventually worked flawlessly, and I'm now looking at a brand new macOS Catalina on my mid-2009 MacBook Pro. Yippee!! Many thanks to dosdude1 and all you marvelous folks!
Actually I thought that could be the reason... I had the same problem once when restoring a Mac from a Time Machine Backup via USB 2.0. The bar stopped moving, the mouse pointer was frozen. I started over again - and realised that everything was working. A mouse click freed the mouse pointer und made the progress bar jump to the correct position.
Thank you for the above information. I have a gut feeling, in accordance with you, the TM problem stems for either a corrupted MacOS on my MBP4,1 (having updated from Sierra->High Sierra->... and so on to Catalina) or a faulty MacOS from Apple. Usng TM from its introduction up till now, it always has caused problems (much alike iCloud services).
However, if I understood your advice correctly, I can boot from the external USB macOS Base System with dosdude1's patcher on it, an choose the option to re-install over the existing MacOS, which is safe, right?
There are two installers available:
2020/09/24 10.15.7, build 19H2, installer 15.7.02
2020/11/13 10.15.7 supplemental, build 19H15, installer 15.7.03
With which one should I create the external patched boor drive?
As I am right now on 19H1011, can I install an older build over it, and then update it again to 19H1011, as per your initial successful advice?
Please advise, thank yery much K Two
Yes, you can install an older build over the 19H1011 (or any other) without losing any user data or configuration.
Just post-patch again as you´d do with a fresh installation also - and remember to force kernel cache rebuild at the end of the patching run.
I´d suggest the 15.7.03 installer version.
A new one is also to be expected after Apple finishes the beta phase in a couple of days...
19H15 is recommended and safe. Nothing will be lost. ?
Last edited:
If my Boot ROM is updated, does that mean my system can boot from APFS as is?
If so, do I need to manually disable the APFS booter on the Catalina patcher install somehow? Or will the install recognize that my system can boot from APFS and so not enable the patcher’s APFS booter?
If your system can boot APFS natively, then to bypass the APFS loader, just select the the OS drive from Startup Disk menu in System Preferences.
I was able to install Catalina on my late 2009 27" iMac. But I was trying to disable system integrity protection and am running into issues. I startup the iMac holding Command+R. Once in the recovery mode I open terminal and type:
csrutil disable
I get:
csrutil: failed to modify system integrity configuration. This tool needs to be executed from the Recovery OS.
And then I try:
csrutil status
And I get:
System Integrity Protection status: unknown (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Dtrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: disabled
This is an unsupported confutation, likely to break in the future and leave your machine in an unknown state.
Any idea what I should do?
csrutil disable
I get:
csrutil: failed to modify system integrity configuration. This tool needs to be executed from the Recovery OS.
And then I try:
csrutil status
And I get:
System Integrity Protection status: unknown (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Dtrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: disabled
This is an unsupported confutation, likely to break in the future and leave your machine in an unknown state.
Any idea what I should do?