Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
After/during downloading of the OTA update have you applied the catalinaswufix4amfi script ?
Because this through Pinarek method whitelist the machine for OTA installing.

These are the OTA phases:

- OTA download complete, then "restart" to install followed by an apple logo (without reboot)
- apple logo short loading bar followed by auto reboot (OTA packages preparing the "macOS Installer" temporary volume)
- apple logo long loading bar followed by Catalina logo installing (OTA stage2 installation on your APFS volume)
- apple logo long loading bar followed by direct boot to Catalina or a bootloop (because post-install patches are required)

If you applied the catalinaswufix then, right after the reboot during the OTA pre-installing with apple logo short bar (it takes about 5 minutes), if you after the reboot hold alt-option key (even till 15 seconds) this I guess overcome the APFS overlay loader, and you can then select the "macOS Installer" as temporary target volume, that should continue automatically the OTA stage 2 installer, after it completes you have to re-apply the post-install patches.

I have the OTA downloaded, I run the script (see photo of output), it shuts everything down and goes to a black screen with a white apple logo and a progress bar that never fills all the way up for about 3-4 minutes, reboots. As soon as it reboots I hold down the alt-option key, and I only get an option to boot into the EFI boot (see photo), and that brings me back to 10.15.1
 

Attachments

  • Screen Shot 2020-02-21 at 8.46.12 AM.png
    Screen Shot 2020-02-21 at 8.46.12 AM.png
    1,009.2 KB · Views: 1,136
  • Screen Shot 2020-02-21 at 8.43.39 AM.png
    Screen Shot 2020-02-21 at 8.43.39 AM.png
    25.8 KB · Views: 349
  • Screen Shot 2020-02-21 at 8.38.45 AM.png
    Screen Shot 2020-02-21 at 8.38.45 AM.png
    50.6 KB · Views: 379
I have the OTA downloaded, I run the script (see photo of output), it shuts everything down and goes to a black screen with a white apple logo and a progress bar that never fills all the way up for about 3-4 minutes, reboots. As soon as it reboots I hold down the alt-option key, and I only get an option to boot into the EFI boot (see photo), and that brings me back to 10.15.1

You're right, then I guess I was wrong, the "macOS Installer" is an APFS mount point, that's why you can't notice there in the apple startup manager, so you should redirect the APFS "overlay" boot script to the "macOS Installer" volume/label, but not sure exactly how to do this.

So if using an APFS script loader the "macOS Installer" is not detected, then @TimothyR734 , @hvds and @Larsvonhier have applied the "APFS ROM patch" to their unsupported machines to allow OTA updates ?
 
Last edited:
  • Like
Reactions: TimothyR734
Adguard is my extension.....
I started using Macs with MacOS Mojave.
Interesting avatar name then, HighSierraCosworth... ;-)
[automerge]1582295628[/automerge]
So if using an APFS script loader the "macOS Installer" is not detected, then @TimothyR734 , @hvds and @Larsvonhier have applied the "APFS ROM patch" to their unsupported machines to allow OTA updates ?
Correct. I did not shy away from the risk to have to desolder or re-flash the EFI flash ROM.
But there is a solution from @0403979 in the works that does the APFS trick by a two-stage approach and so he can get non-ROM-patched machines to update anyway. (Might be out in the wild already, or just for testers at the moment).
 
Correct. I did not shy away from the risk to have to desolder or re-flash the EFI flash ROM.
But there is a solution from @0403979 in the works that does the APFS trick by a two-stage approach and so he can get non-ROM-patched machines to update anyway. (Might be out in the wild already, or just for testers at the moment).

Thanks for the input, I'll spend some time at lunch seeing if it's in the wild, or if I can find a thread to follow for when it's released.
 
Correct. I did not shy away from the risk to have to desolder or re-flash the EFI flash ROM.
But there is a solution from @0403979 in the works that does the APFS trick by a two-stage approach and so he can get non-ROM-patched machines to update anyway. (Might be out in the wild already, or just for testers at the moment).

Thanks for the input, I'll spend some time at lunch seeing if it's in the wild, or if I can find a thread to follow for when it's released.

I can confirm my patch works flawlessly on non-APFS supported Macs. I also just released an update with a minor improvement to that patch. If anyone's been having issues with macOS Patcher, the latest release should fix them. https://github.com/rmc-team/macos-patcher/releases/tag/3.1.1
 
After/during downloading of the OTA update have you applied the catalinaswufix4amfi script ?
Because this through Pinarek method whitelist the machine for OTA installing.

These are the OTA phases:

- OTA download complete, then "restart" to install followed by an apple logo (without reboot)
- apple logo short loading bar followed by auto reboot (OTA packages preparing the "macOS Installer" temporary volume)
- apple logo long loading bar followed by Catalina logo installing (OTA stage2 installation on your APFS volume)
- apple logo long loading bar followed by direct boot to Catalina or a bootloop (because post-install patches are required)

If you applied the catalinaswufix then, right after the reboot during the OTA pre-installing with apple logo short bar (it takes about 5 minutes), if you after the reboot hold alt-option key (even till 15 seconds) this I guess overcome the APFS overlay loader, and you can then select the "macOS Installer" as temporary target volume, that should continue automatically the OTA stage 2 installer, after it completes you have to re-apply the post-install patches.
I had to reinstall 10.15.3 as I booted into verbose mode on 10.15.4 Dev beta 2 and for at least 20 mins it would say AMFI sip disabled core dump pid it started at 1 and when I rebooted it was at core dump pid 1750 did a PRAM reset got stuck at full progress bar then rebooted into the Catalina Patcher reapplied the post install patches still got stuck at full progress bar and one thing I do notice when you reinstall Safari stops working
 
  • Like
Reactions: Pinarek
I had to reinstall 10.15.3 as I booted into verbose mode on 10.15.4 Dev beta 2 and for at least 20 mins it would say AMFI sip disabled core dump pid it started at 1 and when I rebooted it was at core dump pid 1750 did a PRAM reset got stuck at full progress bar then rebooted into the Catalina Patcher reapplied the post install patches still got stuck at full progress bar and one thing I do notice when you reinstall Safari stops working

"AMFI sip disabled" repeated verbose string means that AMFI is enabled again that's why you can't boot more Catalina GUI, this happens when you reset PRAM and also when re-applying the post-patches will override the Preboot's com.apple.boot.plist adding only "-no_compat_check", useful, but not suffice to disable AMFI.

In both cases you can easily re-enter from an USB Installer environment opening a recovery terminal typing exactly this:

Code:
mount -uw /
nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
reboot
 
"AMFI sip disabled" repeated verbose string means that AMFI is enabled again that's why you can't boot more Catalina GUI, this happens when you reset PRAM and also when re-applying the post-patches will override the Preboot's com.apple.boot.plist adding only "-no_compat_check", useful, but not suffice to disable AMFI.

In both cases you can easily re-enter from an USB Installer environment opening a recovery terminal typing exactly this:

Code:
mount -uw /
nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
reboot
Yes - symptom, explanation and cure are exactly what I also had (post #8398) when installing DP1. DP1 booting and running fine since.
 
Got 10.15.3 up and running. Wasn't ever able to get the OTA update to work. Used the newest release of the patcher/installer. Still not sure if there's a way to select which APFS you want to boot to the overlay starts, guess we'll see when 10.15.4 goes live. One question, with the installer off DosDude1's website I had an icon to check to see if there where any updated patches, seem to be gone with the command line install method. Anyway to check if any of the patches have been updated?
 
  • Like
Reactions: TimothyR734
Got 10.15.3 up and running. Wasn't ever able to get the OTA update to work. Used the newest release of the patcher/installer. Still not sure if there's a way to select which APFS you want to boot to the overlay starts, guess we'll see when 10.15.4 goes live. One question, with the installer off DosDude1's website I had an icon to check to see if there where any updated patches, seem to be gone with the command line install method. Anyway to check if any of the patches have been updated?

I guess during the APFS "overlay" if you press "esc" key it should allow the shell terminal session, and there are some minimal unix shell commands to select a different APFS volume but haven't checked them yet, maybe type "help" or "?" during the efi shell, then "exit" to return to apple bootloader.
 
I guess during the APFS "overlay" if you press "esc" key, there are some unix shell commands to select a different APFS volume but haven't checked them yet, maybe type "help" or "?" during the efi shell, then "exit" to return to apple bootloader.

Alright, I've give that a shot, and take some pics when I do.
 
  • Like
Reactions: TimothyR734
"AMFI sip disabled" repeated verbose string means that AMFI is enabled again that's why you can't boot more Catalina GUI, this happens when you reset PRAM and also when re-applying the post-patches will override the Preboot's com.apple.boot.plist adding only "-no_compat_check", useful, but not suffice to disable AMFI.

In both cases you can easily re-enter from an USB Installer environment opening a recovery terminal typing exactly this:

Code:
mount -uw /
nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
reboot
That was happening before I reset the Pram
 
  • Like
Reactions: Pinarek
General question, doing just fine on a MacPro3,1 and 10.15.3 Catalina. How is the upgrade to 10.15.4 beta? I've always used dosdude's installers and they have been flawless.
 
Last edited:
  • Like
Reactions: TimothyR734
I have a question- how can I remove the APFS patch from the installed version of Catalina? I moved my hard drive from a Mac Pro 3,1 to a 5,1. The 3,1 does not support native APFS booting, but the 5,1 does, so I no longer need all that scrolling black text.

Thanks for any help.
 
I have searched and looked everywhere on this forum. How do you download the OTA on an unsupported system?
I have searched and looked everywhere on this forum. How do you download the OTA on an unsupported system?
[automerge]1582349600[/automerge]
run the swupatch in the terminal then before you restart to install the update run the catalinaswufixamfi in the terminal then you will have to replace the Asentientbot wrappers for dpi as there will be no graphics acceleration with out them and the display settings in system preferences is broke so if you accidentally hit a button you screen could go dark so I advise have an app like quick shade or brightness slider install until a fix is found and DP1 was running about 20 degrees hotter when I had it installed
 

Attachments

  • swupatch.sh.zip
    1.5 KB · Views: 147
  • catalinaswufix4amfi.command.zip
    1.9 KB · Views: 196
Last edited:
Not a proper solution, but I used Zoom on some of the early Cat dev betas about 6-7 months ago and it worked, so you might try installing an old version if you can find one. (I've long since deleted mine, otherwise I'd upload it here.)

Thanks. I'm not on Catalina, though the OP with this question is.

My 2 cents - I think the Zoom app has changed multiple times in the last 6-7 months, so one may also have to find an earlier version of Zoom to get it working on Catalina (or Mojave) on Unsupported Macs. However, note that Zooms app for some time prior to March 2019 and up to 16 July 2019 contained a serious exploit that could allow a hacker to gain control of ones webcam. Such versions were unpatched for so long that Apple malware removal tool was updated to remove Zoom clients in July: https://www.macrumors.com/roundup/zoom/

Maybe Zoom got more paranoid after that and clamped down on some exploits that are used to allow Catalina and Mojave to run on Unsupported Macs?

My problem is specifically only with Zoom. Google Hangouts, FaceTime and Skype all work fine for me with Mojave on an unsupported Mac, but they are not the zeitgeist nowadays.

I have an old High Sierra partition on an external USB drive, have installed Zoom and it works fine. It's a very clunky work around because booting takes ages via USB2 and the spinner, plus I can't use my up-to-date apps while using HS.
 
  • Like
Reactions: TimothyR734
Have you tried to apply the legacy audio patch

Since this is post install and the auto update from dosdude1's installer should be functioning, is there a way to trigger this patch again without repair mode since it doesn't boot to the repair volume (and since I can't easily boot to a USB since the video card won't show boot-time graphics)?
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.