macOS 10.15 Catalina on Unsupported Macs

[lroncayo1]

I just installed Catalina on my 2010 5,1 Mac Pro using dosdude's macOS Catalina Patcher. For about a day I had been stumped by "The installer is damaged, and can't be used to install macOS", despite having just downloaded both the macOS Catalina Patcher and the Catalina installer. Thanks to this forum, I found ruprik's post (#13,129) about disabling SIP for installation, which solved the problem. Things are working well so far—I can see the M.2 drive shows up, the OWC Accelsior S PCIe Adapter is boots the SSD with the OS, it looks like the USB3/eSATA card is also working (drives show and work), and so far no issues with the software I've installed.

But there is a problem and I have a question.

The problem I'm facing is sudden, erratic sleep, which leads to shut down. Restarting reveals a crash report (see attachment). I've tried adjusting sleep (System Preferences > Energy Saver > Computer Sleep), but that only seems to lengthen usable computing time. Selecting "Computer sleep: never " doesn't prevent sleep—after an hour or so it goes into sleep/shut down. What's the next step for solving this sleep issue or finding a work-around?

Edited to add: I posted a screen shot of what I have installed, in order, as of this post. To be honest, the sudden sleep started by the first two or three installs... when sleep was set at 15 min.

The question I have is whether SIP needs to be on or off—what is the consensus on having SIP on or off?? It's currently off, as I haven't turned it back on since initial install. And I wouldn't mind leaving it off, which would allow me to continue using TotalFinder. As I comb through this thread it seems like it should be off, but I just want to make sure...

 

[Rob1n]

deleted

 

[jacksbikes]

Just plugin the USB installer, and choose it as boot drive in the System Preferences.

I can't open System Preferences or other programs. e.g. I can use cmd-spacebar to Spotlight the System Preferences but it doesn't open, using keyboard commands to open desktop files fails, Bluetooth for mouse is not working (no wired mouse in the house), wifi is off

To review my issue:
"...[late-2009 21.5” iMac 10,1, 500GB SSD, 8 GB RAM] ...I’ve been running Catalina Patcher 10.15.7 for a couple of months without issue and decided to attempt to use the CatalinaOTAswufix.app to update with the latest Supplemental Updates. Didn’t work and I’m stuck [seemed to be going well until the patch updater ...Restarting — and restarting while holding each of Cmd, option, Cmd-R, opt-cmd-R , cmd-opt-P-R, shift, C — only boots off the internal SSD and gets me to and past my login screen..." sometimes followed by “‘Patchupdaterd’ cannot be opened because the developer cannot be verified“ even though the Patcher USB is not inserted.

Thanks for any ideas!!

 

[Ausdauersportler]

I can't open System Preferences or other programs. e.g. I can use cmd-spacebar to Spotlight the System Preferences but it doesn't open, using keyboard commands to open desktop files fails, Bluetooth for mouse is not working (no wired mouse in the house), wifi is off

To review my issue:
"...[late-2009 21.5” iMac 10,1, 500GB SSD, 8 GB RAM] ...I’ve been running Catalina Patcher 10.15.7 for a couple of months without issue and decided to attempt to use the CatalinaOTAswufix.app to update with the latest Supplemental Updates. Didn’t work and I’m stuck [seemed to be going well until the patch updater ...Restarting — and restarting while holding each of Cmd, option, Cmd-R, opt-cmd-R , cmd-opt-P-R, shift, C — only boots off the internal SSD and gets me to and past my login screen..." sometimes followed by “‘Patchupdaterd’ cannot be opened because the developer cannot be verified“ even though the Patcher USB is not inserted.

Thanks for any ideas!!

SMC reset to get all your (USB) devices back in line followed by one to three PRAM resets, followed by disabling SIP. The patcherupdated is a program checking online for @dosdude1 patch updates.

Another thing:

I cannot understand why all you guys do no staging, e.g. use a cheap external SATA disk to test such updates before playing the one system you have to death. It is unsupported and with each new (beta) update Apple may strip some code from Catalina only used on our old unsupported hardware. So it does not matter how long you had a running unsupported system in the past when you do the next step over the cliff...

 

[lroncayo1]

Another thing:

I cannot understand why all you guys do no staging, e.g. use a cheap external SATA disk to test such updates before playing the one system you have to death.

The SSD with High Sierra I've used for the past two years is waiting patiently nearby incase the Catalina install on a new SSD goes wonky...

 

[K two]

I can't open System Preferences or other programs. e.g. I can use cmd-spacebar to Spotlight the System Preferences but it doesn't open, using keyboard commands to open desktop files fails, Bluetooth for mouse is not working (no wired mouse in the house), wifi is off

To review my issue:
"...[late-2009 21.5” iMac 10,1, 500GB SSD, 8 GB RAM] ...I’ve been running Catalina Patcher 10.15.7 for a couple of months without issue and decided to attempt to use the CatalinaOTAswufix.app to update with the latest Supplemental Updates. Didn’t work and I’m stuck [seemed to be going well until the patch updater ...Restarting — and restarting while holding each of Cmd, option, Cmd-R, opt-cmd-R , cmd-opt-P-R, shift, C — only boots off the internal SSD and gets me to and past my login screen..." sometimes followed by “‘Patchupdaterd’ cannot be opened because the developer cannot be verified“ even though the Patcher USB is not inserted.

Thanks for any ideas!!

Run the Patch Updater in the/Utilities ƒ if you have an internet connection.

 

[K two]

SMC reset to get all your (USB) devices back in line followed by one to three PRAM resets, followed by disabling SIP. The patcherupdated is a program checking online for @dosdude1 patch updates.

Another thing:

I cannot understand why all you guys do no staging, e.g. use a cheap external SATA disk to test such updates before playing the one system you have to death. It is unsupported and with each new (beta) update Apple may strip some code from Catalina only used on our old unsupported hardware. So it does not matter how long you had a running unsupporeted system in the past when you do the next step over the cliff...

Which is why I have two Catalinas installed on separate SSDs in this Mini3,1 but not everyone can easily do that. A fair point, tho.

 

[jacksbikes]

jacksbikes said:
I can't open System Preferences or other programs. e.g. I can use cmd-spacebar to Spotlight the System Preferences but it doesn't open, using keyboard commands to open desktop files fails, Bluetooth for mouse is not working (no wired mouse in the house), wifi is off

To review my issue:
"...[late-2009 21.5” iMac 10,1, 500GB SSD, 8 GB RAM] ...I’ve been running Catalina Patcher 10.15.7 for a couple of months without issue and decided to attempt to use the CatalinaOTAswufix.app to update with the latest Supplemental Updates. Didn’t work and I’m stuck [seemed to be going well until the patch updater ...Restarting — and restarting while holding each of Cmd, option, Cmd-R, opt-cmd-R , cmd-opt-P-R, shift, C — only boots off the internal SSD and gets me to and past my login screen..." sometimes followed by “‘Patchupdaterd’ cannot be opened because the developer cannot be verified“ even though the Patcher USB is not inserted.

Thanks for any ideas!!

Ausdauersportler:
"SMC reset to get all your (USB) devices back in line followed by one to three PRAM resets, followed by disabling SIP. The patcherupdated is a program checking online for @dosdude1 patch updates."

My response:
I can't boot into Recovery Mode or Internet Recovery mode to disable SIP. (Terminal from regular login won't disable SIP.)

(worse case scenario, I guess, is I open up the iMac and pull this SSD out to erase it and start over. I put it in a couple of months ago.)

 

[jacksbikes]

Run the Patch Updater in the/Utilities ƒ if you have an internet connection.

I'm not able to run any programs, though I do have a working Ethernet cable plugged into the iMac, so am unable to run PatchUpdater (which I see in the application folder).

Nor can I seem to be able to boot into recovery mode.

 

[amstel78]

I'm not able to run any programs, though I do have a working Ethernet cable plugged into the iMac, so am unable to run PatchUpdater (which I see in the application folder).

Nor can I seem to be able to boot into recovery mode.

Can't remember if you said you already tried this, but if not, reboot and hold CMD-ALT-P-R to reset NVRAM. Keep holding and let go after the 5th chime. After that, see if you can hold ALT key down after rebooting to get the boot picker to appear.

 

[jacksbikes]

Can't remember if you said you already tried this, but if not, reboot and hold CMD-ALT-P-R to reset NVRAM. Keep holding and let go after the 5th chime. After that, see if you can hold ALT key down after rebooting to get the boot picker to appear.

I've only got the one startup chime every time I've held opt-cmd-P-R. (late 2009 iMac) Usually it runs straight thru the 20 second or so startup time to login screen. Occasionally it pauses for 5-10 seconds midway.

 

[Ausdauersportler]

I'm not able to run any programs, though I do have a working Ethernet cable plugged into the iMac, so am unable to run PatchUpdater (which I see in the application folder).

Nor can I seem to be able to boot into recovery mode.

The SMC reset does not need any booting into the installed macOS. This can/should bring back your lost USB devices. First step first.

I would not write it if I had not such situations regularly with my iMac11,x system constantly moving in and out different GPU and WiFi devices. Every two weeks I have a similar accident. Sometimes I have to strip the GPU completely out of the system and start it without to get the SMC in line, again.

 

[amstel78]

I've only got the one startup chime every time I've held opt-cmd-P-R. (late 2009 iMac) Usually it runs straight thru the 20 second or so startup time to login screen. Occasionally it pauses for 5-10 seconds midway.

You've got to keep holding it down and count up to at least 3 chimes. 4 or 5 for really good measure.

 

[jacksbikes]

The SMC reset does not need any booting into the installed macOS. This can/should bring back your lost USB devices. First step first.

I would not write it if I had not such situations regularly with my iMac11,x system constantly moving in and out different GPU and WiFi devices. Every two weeks I have a similar accident. Sometimes I have to strip the GPU completely out of the system and start it without to get the SMC in line, again.

(My USB keyboard works; bluetooth doesn't, and I do not have a wired mouse)

SMC reset: unplug for 15 seconds, plug in, wait 5 seconds, push start button? (late 2009 iMac)

Tried several times. Followed by PRAM zapping once to multiple times or none. I still cannot open Startup Disk, System Preferences or other programs (though once I did get a "Startup Disk failed to open" type of message. I sometimes get different flashings after logging in, so it's doing different things after each attempt.

I'm just hoping to get into recovery mode at this point! That would save pulling out the SSD and reformatting it.

 

[jacksbikes]

You've got to keep holding it down and count up to at least 3 chimes. 4 or 5 for really good measure.

I've held opt-cmd-P-R for more than 5 minutes twice, pressing after the power button was pushed and before the grey screen. Still just the startup chime. Do I have to wait longer than 5 minutes??

While plugging the USB receiver for a Microsoft wireless mouse I found, I did notice that only 2 of the 4 USB ports worked. SMC reset didn't bring back those 2 that didn't work.

 

[wire_]

(My USB keyboard works; bluetooth doesn't, and I do not have a wired mouse)

SMC reset: unplug for 15 seconds, plug in, wait 5 seconds, push start button? (late 2009 iMac)

Tried several times. Followed by PRAM zapping once to multiple times or none. I still cannot open Startup Disk, System Preferences or other programs (though once I did get a "Startup Disk failed to open" type of message. I sometimes get different flashings after logging in, so it's doing different things after each attempt.

I'm just hoping to get into recovery mode at this point! That would save pulling out the SSD and reformatting it.

If you can't Option key a bootable part besides the Mac HD, that could mean there is no other bootable partition! IOW a corruption. So if you have another system at hand, remaking the Catalina installer drive is worth a shot.

To save time, maybe just make an OpenCore loader as described in prev posts. If you can't get it to work, then find another ext hard drive.

I had similar prob where a USB flash drive with OpenCore loader would not appear in Option boot menu. I remade the install a couple times and even zeroed the first couple megs of the flash drive with dd to clobber the partition table —which has helped on other occasions —but nope. I used another flash drive and it worked first go.

You keep mentioning the Cmd key, but it's the Option key, as in to choose an "optional" boot part. Verify the keyboard Option (PC keyboard Alt) key is working! Cmd goes with various letter combos, such as Cmd-R for boot Apple's stock Recovery partition, or V for verbose boot, etc.

PRAM reset, 1 chime is enough. I don't know where the lore about 3 chimes came from. 5 is eye-rolling / magickz. A red herring. PRAM should not affect Option boot with a wired keyboard, but SMC might affect readiness of USB / BT controller / config, maybe. I can Option boot a Mac Pro 3,1 with a BT keyboard so the wireless config is saved in some low-level location which pre-exists the running OS. Whether it is "PRAM" idk.

Focus on getting Option boot to work by verifying KB and building another boot drive.

 

[amstel78]

PRAM reset, 1 chime is enough. I don't know where the lore about 3 chimes came from. 5 is eye-rolling / magickz. A red herring..

@tsialex suggested waiting for 5 chimes for a full NVRAM reset. I'm assuming it's to fully flush everything out of VSS stores 1 and 2. He can correct me if I'm wrong, but since he does a lot of BootROM and EFI tweaking on our Macs, I'll take his word for it.

As for the 3 chime "lore" https://www.cnet.com/news/margin-note-why-are-three-chimes-recommended-for-a-pramnvram-reset/

 

[microtrash]

I tried to get the latest security update on my Mac Pro 5.1 with 10.15.7 installed on my internal SSD.
I did CatalinaOTAswufix.app and tried both option. Every time, the 10.15.7 supplemental update appear, I can download it and try to install it. I can see an install progress-bar but I'm back at the same release.

I tried many time. What's wrong ?

What did you mean by

• "If you find yourself waiting through an install progress-bar then back at the same release as you started from, steps need to be retraced."

I am missing something ? Thanks.

 

[wire_]

In one Apple Discussions

@tsialex suggested waiting for 5 chimes for a full NVRAM reset. I'm assuming it's to fully flush everything out of VSS stores 1 and 2. He can correct me if I'm wrong, but since he does a lot of BootROM and EFI tweaking on our Macs, I'll take his word for it.

As for the 3 chime "lore" https://www.cnet.com/news/margin-note-why-are-three-chimes-recommended-for-a-pramnvram-reset/

In one official Apple discussion thread on SMC reset, the informed opinion is that you need to disconnect the power cord from the Mac AND be sure to disconnect the power cord from the wall too — I am not making this up. Just to be sure electrons are flushed out of the cord I suppose.

I have a pet peeve about PRAM-reset as being the most over-rated Apple diagnostic operstion of all time. But my peeve is earned from hearing about the miracles it works — or doesn't — for 30 years.

Somehow PCs get by with no PRAM at all...? But we all know how terrible those are, so maybe all the Apple Quality is kept in the PRAM.

 

[wire_]

I tried to get the latest security update on my Mac Pro 5.1 with 10.15.7 installed on my internal SSD.
I did CatalinaOTAswufix.app and tried both option. Every time, the 10.15.7 supplemental update appear, I can download it and try to install it. I can see an install progress-bar but I'm back at the same release.

I tried many time. What's wrong ?

What did you mean by

• "If you find yourself waiting through an install progress-bar then back at the same release as you started from, steps need to be retraced."

I am missing something ? Thanks.

If you request the 10.15.7 Supplemental update and it appears to setup for the install, but the installer partition doesn't boot, because your mac firmware can't boot the APFS update installer partition and you weren't able to force it using OpenCore, so instead you boot back into OS, you will see an installer progress bar with a timer. When it gets done you end up back where you began.

You need to be able to boot the OpenCore loader and select "macos install" from its menu.

To find "macos install" in the OpenCore menu, you need to have setup the update properly using step-2 of the fix, as described in previous posts and in the very helpful instructions for the fix.

 

[amstel78]

In one Apple Discussions

In one official Apple discussion thread on SMC reset, the informed opinion is that you need to disconnect the power cord from the Mac AND be sure to disconnect the power cord from the wall too — I am not making this up. Just to be sure electrons are flushed out of the cord I suppose.

I have a pet peeve about PRAM-reset as being the most over-rated Apple diagnostic operstion of all time. But my peeve is earned from hearing about the miracles it works — or doesn't — for 30 years.

Somehow PCs get by with no PRAM at all...? But we all know how terrible those are, so maybe all the Apple Quality is kept in the PRAM.

I've taken BootROM dumps showing the free space in both VSS stores before and after resets. The difference is significant and have posted screen shots in the OpenCore thread.

As for the informed discussion about unplugging the power cable from both the PSU and the wall, well that's just silly.

Anyway, you're free to reset your nvram however you like. It's your computer. I'm not saying that 1 chime won't solve most people's issues. But, when someone who has an incredible amount of knowledge working on Apple EFI implementations tells me to wait for the 5th chime, I'm going to follow his advise.

 

[Brian1230]

Just wondering if there are any issues doing this on an early 2008 iMac? have an installer made that i used to get Catalina running on a 2008 black macbook before i got my macbook air, and it worked ok except for sound and sleeping.

 

[Ausdauersportler]

Just wondering if there are any issues doing this on an early 2008 iMac? have an installer made that i used to get Catalina running on a 2008 black macbook before i got my macbook air, and it worked ok except for sound and sleeping.

Try #13656 approx. 10 posts up on this page or boot into the USB patcher and redo the post install patching. Possibly something went wrong there.

 

[wire_]

I've taken BootROM dumps showing the free space in both VSS stores before and after resets. The difference is significant and have posted screen shots in the OpenCore thread.

As for the informed discussion about unplugging the power cable from both the PSU and the wall, well that's just silly.

Anyway, you're free to reset your nvram however you like. It's your computer. I'm not saying that 1 chime won't solve most people's issues. But, when someone who has an incredible amount of knowledge working on Apple EFI implementations tells me to wait for the 5th chime, I'm going to follow his advise.

That's a fine point, but we are no longer talking about Apple's PRAM reset, and this deserved to be called out.

The idea that EFI state for unsupported Macs (and Hackintosh) belongs to the user, and by running another bootloader and / or patching firmware the semantics of nvram persistence takes on new significance is great! I just wish the dialog here contained any details about such changes bc that's a big deal!

For all we know the USBOpenCore loader slips new 5-chime functionality into the base system. If so, it would be great to hear more about it. And anything else that may be coming along for the ride, like borrowing all my bitcoin, or maybe just hosing my thumb drive.

So thank you for opening the door on this subject, but this was not my point.

The discussion in context was the routine use of Cmd-Opt-PR as a lore panacea, when in thid case you are trying get past a simple problem with boot config absent any specialized reconfig of the system FW. My gripe was in this context.

If helpful 3rd party fixes are rewiring old Mac's FW I'd like to know more! I have no reason to think they do, and hence no reason to count chimes.

 

[microtrash]

If you request the 10.15.7 Supplemental update and it appears to setup for the install, but the installer partition doesn't boot, because your mac firmware can't boot the APFS update installer partition and you weren't able to force it using OpenCore, so instead you boot back into OS, you will see an installer progress bar with a timer. When it gets done you end up back where you began.

You need to be able to boot the OpenCore loader and select "macos install" from its menu.

To find "macos install" in the OpenCore menu, you need to have setup the update properly using step-2 of the fix, as described in previous posts and in the very helpful instructions for the fix.

Since my Mac Pro 5.1 have the latest firmware and can fully support APFS, I don't use openCore. I have just installed catalina with dosdude patcher.

So I have no choice but to install openCore ?