macOS 10.15 Catalina on Unsupported Macs

[K two]

It should be the same for any mac, but at this point if with "csrutil disable" and "nvram boot-args with amfi" don't worked, I guess the 10.11 supported machines don't have that "amfi flags" in their EFI (non-APFS) firmware.

So probably that's why you can't disable AMFI after a fresh 10.15.4 install, instead the ASentientBot "disablelibraryvalidation.plist" method works to skip AMFI, but only if you are upgrading a 10.15.x installation with a default user already settled, because is a "all users Library Preference plist", but if you need to complete a welcome screen setup then it's not much effective.

This dot4 install was made on top of a perfect dot3 install. Firmware is barefoot (unpatched). So, "csrutil dsable" will be all that is req?

 

[jhowarth]

I can confirm it's the same behaviour on my cMP 3,1 with 10.15.4.

I haven't found a way to debug the origin of the window closing as it doesn't seem to emit any errors or warnings into the system log. If it works on the MacPro 5,1, that might suggest that Apple is using some SSE 4,2 opcodes in the TV.app.

 

[jackluke]

This dot4 install was made on top of a perfect dot3 install. Firmware is barefoot (unpatched). So, "csrutil dsable" will be all that is req?

I attach a picture of how I disabled amfi in nvram (since .4beta1 it worked for me), but machine is a MacBook7,1 that is a supported HighSierra with EFI APFS firmware, I repeat, probably the "El Capitan" machines don't have the "amfi flags" because maybe apple added those variables on later EFI firmware update.

Anyway, retry these steps:

From another macOS (or from a terminal) on the same machine, download and use this ASentientBot com.apple.security.libraryvalidation.plist.zip
and copy it inside your 10.15.4 path /Volumes/YourCatalinaLabel Data/Library/Preferences/

You have to mount the "Catalina Data" volume from diskutil to view this path /Library/Preferences/

In addition to this try again these example steps, booting from the USB Catalina Patcher or a macOS Recovery (even an El Capitan or HighSierra recovery should work), commands and results in the picture attached.

 

[K two]

I attach a picture of how I disabled amfi in nvram (since .4beta1 it worked for me), but machine is a MacBook7,1 that is a supported HighSierra with EFI APFS firmware, I repeat, probably the "El Capitan" machines don't have the "amfi flags" because maybe apple added those variables on later EFI firmware update.

Anyway, retry these steps:

From another macOS (or from a terminal) on the same machine, download and use this ASentientBot com.apple.security.libraryvalidation.plist.zip
and copy it inside your 10.15.4 path /Volumes/YourCatalinaLabel Data/Library/Preferences/

You have to mount the "Catalina Data" volume from diskutil to view this path /Library/Preferences/

In addition to this try again these example steps, booting from the USB Catalina Patcher or a macOS Recovery (even an El Capitan or HighSierra recovery should work), commands and results in the picture attached.

Thanks. The attached screenshot was very clear. Will advise of results.

 

[Larsvonhier]

I haven't found a way to debug the origin of the window closing as it doesn't seem to emit any errors or warnings into the system log. If it works on the MacPro 5,1, that might suggest that Apple is using some SSE 4,2 opcodes in the TV.app.

Tried it on an "unsupported" MBAir with i5 processor. Should have SSE4.2 instructions and does not crash/close the TV App, I just tested it with Snoopy and other free movies.

 

[eVasilis]

Unfortunately, that won't trigger the bug. Try this.

1) Launch the TV application
2) In the TV app window, enter 'free movies' in the search box at the upper righthand corner
3) Click on the 'Peanuts in Space' free movie that appears
4) In the 'Peanuts in Space' window that appears, click 'Play'

On my MacPro 3,1, the playback window opens, plays for a second and closes. This behavior has existed for all beta and release versions of Catalina.

It happened here too. Not with "Peanuts in Space" as it wasn't available but any other free movie.

 

[hvds]

I confirm your test results. With SIP always fully disabled, installation of 10.15.4 with patcher 1.3.1 never failed even when removing all AMFI tranquilizers before.
(Always using a bootable USB installer, didn‘t try install-to-this-machine as I don‘t have patcher 1.3.1 anywhere else)
MBP5,2, APFS ROM patch applied.

Did more testing, and finally I'm happy that I got some non-working setup.

1 - removed /Library/Preferences/com.apple.security.libraryvalidation.plist

2 - made sure that /Volumes/Preboot/xxx/Library/Preferences/SystemConfiguration/com.apple.Boot.plist and /Volumes/Catalina Data/Library/Preferences/SystemConfiguration/com.apple.Boot.plist contain as kernel flags only -no_compat_check

3 - made sure that nvram boot-args contain only -no_compat_check

All that I already did in the previous testing. Then in order to get rid of any other hidden state I reset nvram and SMC.
I did not re-disable SIP at that point (resetting nvram does enable SIP if I'm not mistaken).

Then used the existing bootable USB installer with 10.15.4/1.3.1 to install over my existing+working external 10.15.4 SSD.
Also did a clean install on a freshly erased APFS HDD.
In both cases:
-> installation went fine through the three phases (Catalina logo, short grey-on white phase, long white-on-black with remaining-time display).
But the resulting system won't boot. Inspected that SIP is disabled at that point and that .libraryvalidation.plist is in place.
Added amfi_get_out_of_my_way=1 to boot-args in nvram - still won't boot.
When watching the boot process in single-user mode, the usual AMFI complaints are shown, leading to an endless grey-on-white booting phase.

Repeated the installation. nvram has csr-active-config w%00%00%00.
-> same as before! installs fine, doesn't boot.

Now I'll do csrutil disable from within the terminal of the bootable USB installer and install again... I'll report the result.
So far I guess that confirms the SIP hypothesis, unless I have reset some other, hidden state as well.

 

[jackluke]

Did more testing, and finally I'm happy that I got some non-working setup.

1 - removed /Library/Preferences/com.apple.security.libraryvalidation.plist

2 - made sure that /Volumes/Preboot/xxx/Library/Preferences/SystemConfiguration/com.apple.Boot.plist and /Volumes/Catalina Data/Library/Preferences/SystemConfiguration/com.apple.Boot.plist contain as kernel flags only -no_compat_check

3 - made sure that nvram boot-args contain only -no_compat_check

All that I already did in the previous testing. Then in order to get rid of any other hidden state I reset nvram and SMC.
I did not re-disable SIP at that point (resetting nvram does enable SIP if I'm not mistaken).

Then used the existing bootable USB installer with 10.15.4/1.3.1 to install over my existing+working external 10.15.4 SSD.
Also did a clean install on a freshly erased APFS HDD.
In both cases:
-> installation went fine through the three phases (Catalina logo, short grey-on white phase, long white-on-black with remaining-time display).
But the resulting system won't boot. Inspected that SIP is disabled at that point and that .libraryvalidation.plist is in place.
Added amfi_get_out_of_my_way=1 to boot-args in nvram - still won't boot.
When watching the boot process in single-user mode, the usual AMFI complaints are shown, leading to an endless grey-on-white booting phase.

Repeated the installation. nvram has csr-active-config w%00%00%00.
-> same as before! installs fine, doesn't boot.

Now I'll do csrutil disable from within the terminal of the bootable USB installer and install again... I'll report the result.
So far I guess that confirms the SIP hypothesis, unless I have reset some other, hidden state as well.

I guess this AMFI issue is also related on how the kextcache (prelinkedkernel) is build from the post install patches, and it seems that “csrutil disable” is more effective from a macOS Recovery than an USB Patcher, I used a patched APFS Catalina Recovery (not the usb installer), running csrutil from HighSierra Recovery HD worked too for 10.15.4 .

 

[serafin79]

I also can confirm that on a previously install of 10.15.3 on 8,1 that 10.15.4 installed and booted using 1.31 patcher.
I did have to go into terminal after the install and run the following:

csrutil disable
nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
reboot

 

[deeveedee]

EDIT (again).

I thought that AirPlay to Apple TV was working in Catalina 10.15.3 on my MBP6,2 but I had inadvertently booted Mojave 10.14.6 (where AirPlay to Apple TV does work). I found this post by @jackluke which indicates that AirPlay no longer works with patched legacy video after Mojave.

I'll assume that AirPlay to Apple TV is no longer an option after Mojave unless anyone knows differently.

Thanks again to all who are keeping our old Macs alive!

 

[Syncretic]

Unfortunately, that won't trigger the bug. Try this.

1) Launch the TV application
2) In the TV app window, enter 'free movies' in the search box at the upper righthand corner
3) Click on the 'Peanuts in Space' free movie that appears
4) In the 'Peanuts in Space' window that appears, click 'Play'

On my MacPro 3,1, the playback window opens, plays for a second and closes. This behavior has existed for all beta and release versions of Catalina.

Another data point: MP3,1 w/RX570 (& MouSSE), Catalina 10.15.0 (yes, I'm behind on Catalina releases).

Following your instructions above, when I press "play" I get a solid red screen. However, the controls work, audio plays, subtitles work and are in sync with the audio. I can use the controls to move within the video; I can quit the video and it will restart exactly where I left off. I can quit the TV app, then the video will resume when I restart the app. My only issue is the lack of video (other than red, that is ;-).

A quick scan of the TV.app executable found no SSE 4.2 instructions. If SSE4.2 is (part of) the issue, it's in a library or some ancillary executable. I'll look further when I have some time. If we can identify the instruction(s) at fault, I may be able to incorporate them into MouSSE.

(By the way, JH, please check your PMs.)

 

[telepati]

I have successfully installed 10.15.4 on my Early 2009 iMac. Are there any issues for which I should look out?

What is your GPU?

 

[serafin79]

Can anyone confirm that if this is a bug of unsupported 10.15.4 or not.
Location services don't work on Apple maps or Google maps unless I toggle off then on.
Upon reboot it loses the setting and have to do it again in order to get location services working

 

[jhowarth]

Can anyone confirm that if this is a bug of unsupported 10.15.4 or not.
Location services don't work on Apple maps or Google maps unless I toggle off then on.
Upon reboot it loses the setting and have to do it again in order to get location services working

No problems with Location Service support in Apple Maps on a MacPro 3,1 with GTX680 under patched 10.15.4 installed over patched 10.15.3 using Catalina Patcher 1.3.1.

 

[serafin79]

No problems with Location Service support in Apple Maps on a MacPro 3,1 with GTX680 under patched 10.15.4 installed over patched 10.15.3 using Catalina Patcher 1.3.1.

It worked fine in patched 10.15.3 but not on 10.15.4, it's odd

 

[honestone33]

It worked fine in patched 10.15.3 but not on 10.15.4, it's odd

From what I am gathering, including conversations with disdude1, there are issues involved with OS 10.15.4 period. That is, according to what he told me, both the full installer for OS 10.15.4 and the OS 10.15.4 Combo Update are problematic, and are not to be used.

 

[serafin79]

From what I am gathering, including conversations with disdude1, there are issues involved with OS 10.15.4 period. That is, according to what he told me, both the full installer for OS 10.15.4 and the OS 10.15.4 Combo Update are problematic, and are not to be used.

I was able to fix the issue by resetting permissions

tccutil reset All

 

[iamMacPerson]

So I'm having a bit of a problem. Updated to 10.15.4 last night on my cMP (4,1 to 5,1) and everything seemed to go fine. Had no problems as all with the update and even got some files moved around and backed up before shutting it down. Went to boot it again right now and I have no video. The machine seems to boot as I can see it on the network from my other Macs but I cannot remote into it and have no video on my display. Any idea what I can do to try and fix this?

 

[honestone33]

I was able to fix the issue by resetting permissions

tccutil reset All

Thanks. But I think I'll still wait.

 

[iapplerandomthings]

Hi!

I have a 2010 Macbook 7,1 and an Early 2009 Mac Pro 4,1 flashed to 5,1 with MacOS 10.15.1 Catalina.

I've tried to updated them to 10.15.3 searching for updates in the AppStore it does not find anything. I've also tried to download the combo update and installing it manually, but it says that it is not compatible with my system.
I've tried re applying the patches in recovery mode just checking if I miss something but still nothing.

Does anyone has a clue about how to update the system?

 

[TimothyR734]

Hi!

I have a 2010 Macbook 7,1 and an Early 2009 Mac Pro 4,1 flashed to 5,1 with MacOS 10.15.1 Catalina.

I've tried to updated them to 10.15.3 searching for updates in the AppStore it does not find anything. I've also tried to download the combo update and installing it manually, but it says that it is not compatible with my system.
I've tried re applying the patches in recovery mode just checking if I miss something but still nothing.

Does anyone has a clue about how to update the system?
[/QUOTE

http://dosdude1.com/catalina/

 

[hvds]

Did more testing, and finally I'm happy that I got some non-working setup.

1 - removed /Library/Preferences/com.apple.security.libraryvalidation.plist

2 - made sure that /Volumes/Preboot/xxx/Library/Preferences/SystemConfiguration/com.apple.Boot.plist and /Volumes/Catalina Data/Library/Preferences/SystemConfiguration/com.apple.Boot.plist contain as kernel flags only -no_compat_check

3 - made sure that nvram boot-args contain only -no_compat_check

All that I already did in the previous testing. Then in order to get rid of any other hidden state I reset nvram and SMC.
I did not re-disable SIP at that point (resetting nvram does enable SIP if I'm not mistaken).

Then used the existing bootable USB installer with 10.15.4/1.3.1 to install over my existing+working external 10.15.4 SSD.
Also did a clean install on a freshly erased APFS HDD.
In both cases:
-> installation went fine through the three phases (Catalina logo, short grey-on white phase, long white-on-black with remaining-time display).
But the resulting system won't boot. Inspected that SIP is disabled at that point and that .libraryvalidation.plist is in place.
Added amfi_get_out_of_my_way=1 to boot-args in nvram - still won't boot.
When watching the boot process in single-user mode, the usual AMFI complaints are shown, leading to an endless grey-on-white booting phase.

Repeated the installation. nvram has csr-active-config w%00%00%00.
-> same as before! installs fine, doesn't boot.

Now I'll do csrutil disable from within the terminal of the bootable USB installer and install again... I'll report the result.
So far I guess that confirms the SIP hypothesis, unless I have reset some other, hidden state as well.

Just to confirm that csrutil disable from within the terminal of the bootable USB installer worked - installing, and booting the installed system is again fine and fully automatic (10.5.4/1.3.1).
Thanks fabioroberto and jackluke!

EDIT: did this with a clean install, and with an install over an existing 10.15.4. Both installed+booted fine.

 

[Dannyy]

I could use some help. I'm experiencing an odd display error on my mbp 8,1 running 10.15.3. It began when I initially force installed Mojave in late 2019. The borders of certain graphics elements displays a black line where I imagine it should be transparent. Has anyone experienced this problem and does anyone have ideas on how to fix it? Thanks

you should see this post https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28238740

 

[fabienpascal]

Everyone of his patchers have the legacy video patches all you have to do is uncheck macOS 10.15.3 is the one that doesn't have the AMFI issues thus patcher 1.3.0 supports that version of Catalina

@vjani understood what I was asking and sent the 1.3.1 he downloaded.
The update is done to 10.15.4. No issues at all. It didn't work originally because I was attempting the update from the 1.3.0 patcher (I thought the Patch Updater will also update the macOS catalina patcher app) which can't patch the 10.15.4 installer properly (the installer will not work - USB and install over existing OS won't go beyond 5% boot loading bar). I have a metal card in my 2011 iMac so the legacy video patch is disable for me by default thus I am not running into all the issues reported by the users on legacy cards.

 

[hvds]

Just to confirm that csrutil disable from within the terminal of the bootable USB installer worked - installing, and booting the installed system is again fine and fully automatic (10.5.4/1.3.1).
Thanks fabioroberto and jackluke!

EDIT: did this with a clean install, and with an install over an existing 10.15.4. Both installed+booted fine.

Then repeated the boot part of the exercise.
- verified that the .libraryvalidation.plist is in place on the clean-installed dsik and on the over-installed.
- reset the nvram
- the clean-installed doesn't boot, with the AMFI messages shown in single user mode.
- csrutil status in single user mode shows SIP disabled, but there is no csr-related entry in nvram
- the over-installed disk boots nevertheless...

Then in terminal of the bootable USB installer. Also here csrutil status shows SIP disabled. Still did csrutil disable. Now there is this entry in nvram: csr-active-config w%00%00%00.

Now booting works again with both disks (clean-installed and over-installed).