macOS 10.15 Catalina on Unsupported Macs

[RV-ABZ]

For what it's worth because I don't have any unsupported Mac, I updated my Dell Latitude D630 Hackintosh from 10.15.3 to 10.15.4 a few days ago. This old C2D laptop is fitted with nVidia Quadro NVS 135m graphics, a dGPU based on GeForce 8400M GS, i.e. non-Metal Tesla chip.

Until Catalina 10.15.3 (same in Mojave 10.14.4/5/6), all I had to do, post-install or post-update, was to manually apply the required patches in single-user mode:

1. replacement of telemetry plugin in /S/L/UserEventPlugins with 10.13.6's (Core2Duo-oblige)
2. replacement of PlatformSupport.plist in in /S/L/CoreServices by a patched version (to support MBP7,1 SMBIOS)
3. installation of Tesla kexts in /S/L/E (not necessary beyond 1st install, unaffected by subsequent updates)
4. replacement/patching of the frameworks in /S/L/Frameworks and /S/L/PrivateFrameworks

With 10.15.4 update, this just would not work: I kept getting stuck at graphics failing to initialise with endless "AMFI..." messages, even with the library validation disabling plist in place (and SIP disabled, of course).

I was only able to fix this by re-installing 10.15.4 from scratch using a USB installer patched with Dosdude1's patcher v1.3.1. After applying all the required post-install patches, system worked as it used to before!

Couldn't suss out what difference it made compared to the manual process I followed before but was glad it led to success in the end.

 

[telepati]

Because to unlock NightShift feature on unsupported Mac you need also to apply the NightShift patch that is essentially a patched /System/Library/PrivateFrameworks/CoreBrightness.framework

After you applied the night shift patch, the @indiawallah method worked correctly to enable Night shift tab on Displays.prefpane .

I mean, I already installed the NightShift patch on the first boot after update.

 

[deeveedee]

For what it's worth because I don't have any unsupported Mac, I updated my Dell Latitude D630 Hackintosh from 10.15.3 to 10.15.4 a few days ago. This old C2D laptop is fitted with nVidia Quadro NVS 135m graphics, a dGPU based on GeForce 8400M GS, i.e. non-Metal Tesla chip.

Until Catalina 10.15.3 (same in Mojave 10.14.4/5/6), all I had to do, post-install or post-update, was to manually apply the required patches in single-user mode

With 10.15.4 update, this just would not work: I kept getting stuck at graphics failing to initialise with endless "AMFI..." messages, even with the library validation disabling plist in place (and SIP disabled, of course).

I was only able to fix this by re-installing 10.15.4 from scratch using a USB installer patched with Dosdude1's patcher v1.3.1. After applying all the required post-install patches, system worked as it used to before!

Congrats. Does your BIOS reset on shutdown? I tried to PM you so as not to clutter this thread with hackintosh questions, but it appears your PM is disabled.

 

[indiawallah]

Are you using a


I'm not seeing that problem at all on a MacPro 3,1 with GTX680. Using the Patch Updater offering of the 10.15.4 compatible version of the Night Shift patch and clicking on the restart button added the Night Shift tab to the Monitors system preference panel. Are you sure that you just aren't seeing a glitch in the kernel cache rebuild step as opposed to the Night Shift patch not actually applying?

I had noted in a previous post (no. 9399) by @Eithanius that he had had an issue with the Night Shift tab in the Monitors panel so was posting the fix on his behalf or any others with an issue.

As I said I did an OTA update needing to use @jackluke 's catalinaswufix5amfi command in terminal to get beyond the AMFI issue of going from .4 to .5 and subsequently to the GM so without using the updated patcher.

If the patcher now has fixed that slight issue I am not aware of that as I didn't use it but had to use the manual method I explained to get the Night shift tab after my OTA update.

 

[vik071]

From 10.15.3 Final
[automerge]1584322011[/automerge]
From 10.15.3
[automerge]1584322159[/automerge]
I am really getting sick of thus macrumors redo nothing liking getting error messages trying to attach or upload I hope whoever came up with this gets their heads checked whoever thought of this must have an IQ of 60
[automerge]1584322297[/automerge]
going to post both the monitor panels on discord at least the devs don't **** with us there

How do you install this?

 

[learntofly83]

Could anyone tell me what version the stock Nightshift patch is on Dosdude1’s 1.3.5 tool? I could have sworn it was 4, but after reinstalling all patches it’s now 3. Am I mistaken?

 

[telepati]

I don't know but definitely something wrong 10.15.4 security. I uninstalled 1Password.app and try to reinstall again and it doesn't allow to install. Always crashing while installing.

The new method works in sight, but it definitely corrupts the OS.

Also Apple Internal SIP still shows enabled.

 

[cb4ii]

Mac mini 5,1 updated successfully to 10.15.4 via Patcher 1.3.5. Re-applied NightShift patch after installation of patched 10.15.4.

No issues so far.

Music & Fotos working as before.

Thanks for your extraordinary work Dosdude, Sentinel and all the other experts!

 

[nicksilverstein]

Well, today I found out how to get the MacBook Pro Early 2008 Brightness Control working in Catalina 10.15.4. Now, I am not the creator of the patch or tools but, I figured out how to get them working on the model mentioned above. I was thinking… The MacBook Early 2009 doesn’t have that much of a different screen to the Early 2008 MacBook Pro and the Brightness of the Early 2009 MacBook works with Dosdude1’s Patch Updater. The Early 2008 MacBook Pro Brightness does not. So, I thought why don’t I just copy it over. It worked like a charm. So, all you do is copy the Brightness Fix from an Early 2009 MacBook Pre-Unibody to an Early 2008 MacBook Pro Pre-Unibody and install it. It works totally fine. Please @dosdude1 Allow the MacBook Early 2009 Brightness Fix to work in Catalina, Mojave, High Sierra, and Sierra to work on the Early 2008 MacBook Pro 4,1 Pre-Unibody. The only thing that doesn’t work is the Keyboard Lights. I can live without that if I can adjust my brightness with F2 and F1 any day!

 

[lsalconi]

Hi all,

today I updated my macPro 5,1 2012 to Catalina 10.15.4 using the 1.3.5 patcher,
a new install over the previous configuration (making an usb, booting, installing os,
reboot, apply patch, reboot then log in).
Before (with 10.15.3) all was perfect. Now I have some issues: if I try to open "System
Preferences" and click on "Patch Updater" I have a crash, with an automatic problem
report opened that say that "System Preferences quit unexpectedly".

Can you suggest how I can fix this ?

Best regards,

L.

 

[indiawallah]

Well, today I found out how to get the MacBook Pro Early 2008 Brightness Control working in Catalina 10.15.4. Now, I am not the creator of the patch or tools but, I figured out how to get them working on the model mentioned above. I was thinking… The MacBook Early 2009 doesn’t have that much of a different screen to the Early 2008 MacBook Pro and the Brightness of the Early 2009 MacBook works with Dosdude1’s Patch Updater. The Early 2008 MacBook Pro Brightness does not. So, I thought why don’t I just copy it over. It worked like a charm. So, all you do is copy the Brightness Fix from an Early 2009 MacBook Pre-Unibody to an Early 2008 MacBook Pro Pre-Unibody and install it. It works totally fine. Please @dosdude1 Allow the MacBook Early 2009 Brightness Fix to work in Catalina, Mojave, High Sierra, and Sierra to work on the Early 2008 MacBook Pro 4,1 Pre-Unibody. The only thing that doesn’t work is the Keyboard Lights. I can live without that if I can adjust my brightness with F2 and F1 any day!

@nicksilverstein ..... I came across this from an earlier post with someone with a similar old machine perhaps it too could work for you with your non-working backlit keyboard.....

Yeah, at least for the meantime, "Lab Tick" a small keyboard light utility that will auto dim and turn off keyboard light at your desired setting, also don't forget to load lab tick in the "start up" folder after you set it up so you don't have to mess with it again. It's an excellent substitute until the patch is written for the ambient light sensor. I too have an early 2008.

 

[olrik77]

Bonjour,

After a clean install of 10.15.4 with @dosdude1 1.3.5 patcher on my MP3,1, I have this "panic" :

Any idea ?

Thanks in advance,

Serviteur,

panic(cpu 3 caller 0xffffff801ae4c32a): Kernel trap at 0xffffff7f9d25ee80, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000001e998000, CR4: 0x00000000000026e0
RAX: 0x0000000004240000, RBX: 0x0000000000000000, RCX: 0x0000000000010002, RDX: 0x0000000000000001
RSP: 0xffffff920cdabe10, RBP: 0xffffff920cdabe30, RSI: 0x0000000004244063, RDI: 0x0000000000000000
R8: 0x0000000000000001, R9: 0x0000000000000002, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000000, R13: 0xffffff803c1d53b0, R14: 0xffffff803fbc8780, R15: 0xffffff7f9d27c290
RFL: 0x0000000000010206, RIP: 0xffffff7f9d25ee80, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 1

Backtrace (CPU 3), Frame : Return Address
0xffffff920cdab870 : 0xffffff801ad215cd
0xffffff920cdab8c0 : 0xffffff801ae5a3c5
0xffffff920cdab900 : 0xffffff801ae4bf7e
0xffffff920cdab950 : 0xffffff801acc7a40
0xffffff920cdab970 : 0xffffff801ad20c97
0xffffff920cdaba70 : 0xffffff801ad21087
0xffffff920cdabac0 : 0xffffff801b4c2c7c
0xffffff920cdabb30 : 0xffffff801ae4c32a
0xffffff920cdabcb0 : 0xffffff801ae4c028
0xffffff920cdabd00 : 0xffffff801acc7a40
0xffffff920cdabd20 : 0xffffff7f9d25ee80
0xffffff920cdabe30 : 0xffffff801b414e04
0xffffff920cdabea0 : 0xffffff801b414c0a
0xffffff920cdabec0 : 0xffffff801ad63545
0xffffff920cdabf40 : 0xffffff801ad63071
0xffffff920cdabfa0 : 0xffffff801acc713e
Kernel Extensions in backtrace:
com.apple.iokit.IOUSBMassStorageDriver(157.101.3)[E83AC456-A4B2-3DC3-85C2-8B52B09F44DB]@0xffffff7f9d25a000->0xffffff7f9d28dfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f9b731000
dependency: com.apple.iokit.IOUSBHostFamily(1.2)[CC813BD5-B83C-3B83-A95E-796D87DE8F81]@0xffffff7f9ba3b000
dependency: com.apple.iokit.IOStorageFamily(2.1)[425BC668-32EC-368C-B4EB-CF8510846BEE]@0xffffff7f9b919000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(422.101.1)[E0A54FDE-501E-3BB4-A08C-C8AFA1719DE2]@0xffffff7f9b6ee000

BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check

Mac OS version:
19E266

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide: 0x000000001aa00000
Kernel text base: 0xffffff801ac00000
__HIB text base: 0xffffff801ab00000
System model name: MacPro3,1 (Mac-F42C88C8)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 693809599240
last loaded kext at 641676871146: >usb.IOUSBHostHIDDevice 1.2 (addr 0xffffff7f9e005000, size 45056)
last unloaded kext at 181951492930: >!AXsanScheme 3 (addr 0xffffff7f9d898000, size 40960)
loaded kexts:
AAA.LoadEarly.MouSSE 0.38
com.parrotgeek.SIPManager 1
@fileutil 20.036.15
@filesystems.autofs 3.0
>!AGraphicsDevicePolicy 5.1.16
@AGDCPluginDisplayMetrics 5.1.16
>!AHV 1
|IOUserEthernet 1.0.1
>!AHDA 281.52
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.11
|IO!BSerialManager 7.0.4f6
@GeForce 14.0.0
>pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
>!ALPC 3.1
>!AFWOHCI 5.6.2
>AudioAUUC 1.70
>!A!ISlowAdaptiveClocking 4.0.0
>ACPI_SMC_PlatformPlugin 1.0.0
>!AVirtIO 1.0
@filesystems.hfs.kext 522.100.5
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
|SCSITaskUserClient 422.101.1
@filesystems.apfs 1412.101.1
>!AAHCIPort 341.0.2
>!A!IPIIXATA 2.5.1
>!A!I8254XEthernet 3.1.5
@private.KextAudit 1.0
>!AACPIButtons 6.1
>!AHPET 1.8
>!ARTC 2.0
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
>!A!ICPUPowerManagement 222.0.0
|EndpointSecurity 1
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
|IOAVB!F 840.3
@plugin.IOgPTPPlugin 840.3
|IOEthernetAVB!C 1.1.0
@kext.triggers 1.0
>!AHIDKeyboard 209
|IOFireWireIP 2.3.0
>!AGraphicsControl 5.1.16
>!ASSE 1.0
>DspFuncLib 281.52
@kext.OSvKernDSPLib 529
>!ASMBus!C 1.0.18d1
|IOAccelerator!F2 438.4.5
@nvidia.driver.NVDAGK100Hal 14.0.0
@nvidia.driver.NVDAResman 14.0.0
|IONDRVSupport 575.1
@!AGPUWrangler 5.1.16
@!AGraphicsDeviceControl 5.1.16
|IOFireWire!F 4.7.5
>!AHDA!C 281.52
|IOHDA!F 281.52

 

[TimothyR734]

The night shift patch does appear but sometimes it will not be shown on the display panel and the manual procedure is required to get it on there. My experience in any case although I updated to 10.15.4 with an OTA update and not the updated 1.3.5. Catalina patcher.

Thank you that worked on my mid 2009 iMac I had got shifty to work by replacing the Corebrightness from one that Jackluke patched on March 13th and I tried the unpatched from 10.15.3 but no Night Shift in Display settings but it works now
[automerge]1585494854[/automerge]

Patcher show me and I installed it but just like @indiawallah said it doesn't show under Preferences;

View attachment 902119

See if this works it is unpatched CoreBrightness from 10.15.3 it goes in /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A don't delete the one that's in there just replace I will also upload a patched copy from March 13th if any thing this will at least get Shifty work work but have the Brightness slider app from App Store installed the screen will remain dim after using Shifty

 

[telepati]

I just back to 10.15.3 its much stable and everything works without any problem. Fans are back to normal iCloud and iCloud related apps (1Password) working better.

 

[TimothyR734]

How do you install this?

[automerge]1585496093[/automerge]
Like this make sure you have a 16GB formatted HFS-Extended-Journaled download a copy of macOS Catalina then follow the instructions

 

[jhowarth]

For what it's worth because I don't have any unsupported Mac, I updated my Dell Latitude D630 Hackintosh from 10.15.3 to 10.15.4 a few days ago. This old C2D laptop is fitted with nVidia Quadro NVS 135m graphics, a dGPU based on GeForce 8400M GS, i.e. non-Metal Tesla chip.

Until Catalina 10.15.3 (same in Mojave 10.14.4/5/6), all I had to do, post-install or post-update, was to manually apply the required patches in single-user mode:

1. replacement of telemetry plugin in /S/L/UserEventPlugins with 10.13.6's (Core2Duo-oblige)
2. replacement of PlatformSupport.plist in in /S/L/CoreServices by a patched version (to support MBP7,1 SMBIOS)
3. installation of Tesla kexts in /S/L/E (not necessary beyond 1st install, unaffected by subsequent updates)
4. replacement/patching of the frameworks in /S/L/Frameworks and /S/L/PrivateFrameworks

With 10.15.4 update, this just would not work: I kept getting stuck at graphics failing to initialise with endless "AMFI..." messages, even with the library validation disabling plist in place (and SIP disabled, of course).

I was only able to fix this by re-installing 10.15.4 from scratch using a USB installer patched with Dosdude1's patcher v1.3.1. After applying all the required post-install patches, system worked as it used to before!

View attachment 902123

Couldn't suss out what difference it made compared to the manual process I followed before but was glad it led to success in the end.

The difference is that by using the Catalina Patcher 1.3.1 to create the patched installer, you got the required 'DisableLibraryValidation' field in /Library/Preferences/com.apple.security.libraryvalidation.plist set to '1'.
[automerge]1585497931[/automerge]

Bonjour,

After a clean install of 10.15.4 with @dosdude1 1.3.5 patcher on my MP3,1, I have this "panic" :

Any idea ?

Thanks in advance,

Serviteur,

panic(cpu 3 caller 0xffffff801ae4c32a): Kernel trap at 0xffffff7f9d25ee80, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000001e998000, CR4: 0x00000000000026e0
RAX: 0x0000000004240000, RBX: 0x0000000000000000, RCX: 0x0000000000010002, RDX: 0x0000000000000001
RSP: 0xffffff920cdabe10, RBP: 0xffffff920cdabe30, RSI: 0x0000000004244063, RDI: 0x0000000000000000
R8: 0x0000000000000001, R9: 0x0000000000000002, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000000, R13: 0xffffff803c1d53b0, R14: 0xffffff803fbc8780, R15: 0xffffff7f9d27c290
RFL: 0x0000000000010206, RIP: 0xffffff7f9d25ee80, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0, VF: 1

Backtrace (CPU 3), Frame : Return Address
0xffffff920cdab870 : 0xffffff801ad215cd
0xffffff920cdab8c0 : 0xffffff801ae5a3c5
0xffffff920cdab900 : 0xffffff801ae4bf7e
0xffffff920cdab950 : 0xffffff801acc7a40
0xffffff920cdab970 : 0xffffff801ad20c97
0xffffff920cdaba70 : 0xffffff801ad21087
0xffffff920cdabac0 : 0xffffff801b4c2c7c
0xffffff920cdabb30 : 0xffffff801ae4c32a
0xffffff920cdabcb0 : 0xffffff801ae4c028
0xffffff920cdabd00 : 0xffffff801acc7a40
0xffffff920cdabd20 : 0xffffff7f9d25ee80
0xffffff920cdabe30 : 0xffffff801b414e04
0xffffff920cdabea0 : 0xffffff801b414c0a
0xffffff920cdabec0 : 0xffffff801ad63545
0xffffff920cdabf40 : 0xffffff801ad63071
0xffffff920cdabfa0 : 0xffffff801acc713e
Kernel Extensions in backtrace:
com.apple.iokit.IOUSBMassStorageDriver(157.101.3)[E83AC456-A4B2-3DC3-85C2-8B52B09F44DB]@0xffffff7f9d25a000->0xffffff7f9d28dfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f9b731000
dependency: com.apple.iokit.IOUSBHostFamily(1.2)[CC813BD5-B83C-3B83-A95E-796D87DE8F81]@0xffffff7f9ba3b000
dependency: com.apple.iokit.IOStorageFamily(2.1)[425BC668-32EC-368C-B4EB-CF8510846BEE]@0xffffff7f9b919000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(422.101.1)[E0A54FDE-501E-3BB4-A08C-C8AFA1719DE2]@0xffffff7f9b6ee000

BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check

Mac OS version:
19E266

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide: 0x000000001aa00000
Kernel text base: 0xffffff801ac00000
__HIB text base: 0xffffff801ab00000
System model name: MacPro3,1 (Mac-F42C88C8)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 693809599240
last loaded kext at 641676871146: >usb.IOUSBHostHIDDevice 1.2 (addr 0xffffff7f9e005000, size 45056)
last unloaded kext at 181951492930: >!AXsanScheme 3 (addr 0xffffff7f9d898000, size 40960)
loaded kexts:
AAA.LoadEarly.MouSSE 0.38
com.parrotgeek.SIPManager 1
@fileutil 20.036.15
@filesystems.autofs 3.0
>!AGraphicsDevicePolicy 5.1.16
@AGDCPluginDisplayMetrics 5.1.16
>!AHV 1
|IOUserEthernet 1.0.1
>!AHDA 281.52
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.11
|IO!BSerialManager 7.0.4f6
@GeForce 14.0.0
>pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
>!ALPC 3.1
>!AFWOHCI 5.6.2
>AudioAUUC 1.70
>!A!ISlowAdaptiveClocking 4.0.0
>ACPI_SMC_PlatformPlugin 1.0.0
>!AVirtIO 1.0
@filesystems.hfs.kext 522.100.5
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
|SCSITaskUserClient 422.101.1
@filesystems.apfs 1412.101.1
>!AAHCIPort 341.0.2
>!A!IPIIXATA 2.5.1
>!A!I8254XEthernet 3.1.5
@private.KextAudit 1.0
>!AACPIButtons 6.1
>!AHPET 1.8
>!ARTC 2.0
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
>!A!ICPUPowerManagement 222.0.0
|EndpointSecurity 1
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
|IOAVB!F 840.3
@plugin.IOgPTPPlugin 840.3
|IOEthernetAVB!C 1.1.0
@kext.triggers 1.0
>!AHIDKeyboard 209
|IOFireWireIP 2.3.0
>!AGraphicsControl 5.1.16
>!ASSE 1.0
>DspFuncLib 281.52
@kext.OSvKernDSPLib 529
>!ASMBus!C 1.0.18d1
|IOAccelerator!F2 438.4.5
@nvidia.driver.NVDAGK100Hal 14.0.0
@nvidia.driver.NVDAResman 14.0.0
|IONDRVSupport 575.1
@!AGPUWrangler 5.1.16
@!AGraphicsDeviceControl 5.1.16
|IOFireWire!F 4.7.5
>!AHDA!C 281.52
|IOHDA!F 281.52

What exact model is your graphics card?

 

[dosdude1]

Well, today I found out how to get the MacBook Pro Early 2008 Brightness Control working in Catalina 10.15.4. Now, I am not the creator of the patch or tools but, I figured out how to get them working on the model mentioned above. I was thinking… The MacBook Early 2009 doesn’t have that much of a different screen to the Early 2008 MacBook Pro and the Brightness of the Early 2009 MacBook works with Dosdude1’s Patch Updater. The Early 2008 MacBook Pro Brightness does not. So, I thought why don’t I just copy it over. It worked like a charm. So, all you do is copy the Brightness Fix from an Early 2009 MacBook Pre-Unibody to an Early 2008 MacBook Pro Pre-Unibody and install it. It works totally fine. Please @dosdude1 Allow the MacBook Early 2009 Brightness Fix to work in Catalina, Mojave, High Sierra, and Sierra to work on the Early 2008 MacBook Pro 4,1 Pre-Unibody. The only thing that doesn’t work is the Keyboard Lights. I can live without that if I can adjust my brightness with F2 and F1 any day!

A actually had that patch available to the MacBookPro4,1 before, but it caused a huge amount of issues on most people's machines.

 

[alphascorp]

Hi all,

today I updated my macPro 5,1 2012 to Catalina 10.15.4 using the 1.3.5 patcher,
a new install over the previous configuration (making an usb, booting, installing os,
reboot, apply patch, reboot then log in).
Before (with 10.15.3) all was perfect. Now I have some issues: if I try to open "System
Preferences" and click on "Patch Updater" I have a crash, with an automatic problem
report opened that say that "System Preferences quit unexpectedly".

Can you suggest how I can fix this ?

Best regards,

L.

Hi @lsalconi
With MP5,1 you do not need "Patch Updater" or any other Patch, so you must deselect "Auto-apply Post Install Patches" in Options menu when creating your USB installer.
If like me you forget this from time to time, there is no point in re-creating the USB installer, just modify the file "CatalinaPatcherFlags.plist" in the root of the USB installer and under: "< key> shouldAutoApplyPostInstallPatches </key> "
replace "<true />" with "<false />"
About your problem, did you try to remove "Patch Updater" from System preferences by right clicking on it (on Patch Updater)

 

[lsalconi]

Hi @lsalconi
With MP5,1 you do not need "Patch Updater" or any other Patch, so you must deselect "Auto-apply Post Install Patches" in Options menu when creating your USB installer.
If like me you forget this from time to time, there is no point in re-creating the USB installer, just modify the file "CatalinaPatcherFlags.plist" in the root of the USB installer and under: "< key> shouldAutoApplyPostInstallPatches </key> "
replace "<true />" with "<false />"
About your problem, did you try to remove "Patch Updater" from System preferences by right clicking on it (on Patch Updater)

... done! Seems to be fixed, for what concern the "Patch Updater".

Mine is a 5,1 Mac Pro 2012 with two CPU 3,46, 64GB, a classic SM951 SSD and a patched RX580 Sapphire. ... good, that I can see the boot...
So this system do not requires the "Patch Updater" now and for the future?
In other words, if I will re-install I will not apply any kind of patch or post-install ?

I find it also in my "Utility" folder...

Thanks of course for your previous answer,

L.

PS.
Maybe is my mistake because even in my previous update (10.15.3 with patch 1.3.0) I still have it in my System Preference panel. :O

 

[Meelas]

I’m putting a previous posters post here as it describes the exact same issues that I’m having
since ever and always was successful with patching my systems until now. On my MacbookPro 5.5, I installed the new 1.3.5 patch and downloaded the new Catalina app. Once finished I was able to create a brand new USB flash boot drive. The 2 following options to upgrade to 10.15.4 did not work:
- installing after downloading and patching the new Catalina version results in a classic reboot without any update
- booting from the flash drive results in the "damaged Catalina version" and hence no ability to update either (tried the csrutil terminal command but tells me the system is unknown).

 

[alphascorp]

... done! Seems to be fixed, for what concern the "Patch Updater".

Mine is a 5,1 Mac Pro 2012 with two CPU 3,46, 64GB, a classic SM951 SSD and a patched RX580 Sapphire. ... good, that I can see the boot...
So this system do not requires the "Patch Updater" now and for the future?
In other words, if I will re-install I will not apply any kind of patch or post-install ?

I find it also in my "Utility" folder...

Thanks of course for your previous answer,

L.

PS.
Maybe is my mistake because even in my previous update (10.15.3 with patch 1.3.0) I still have it in my System Preference panel. :O

Great!
I have the same MP5,1 as you with same CPU ...
You can also delete "Patch Updater" from the "Utilities" folder.

 

[olrik77]

The difference is that by using the Catalina Patcher 1.3.1 to create the patched installer, you got the required 'DisableLibraryValidation' field in /Library/Preferences/com.apple.security.libraryvalidation.plist set to '1'.
[automerge]1585497931[/automerge]


What exact model is your graphics card?

My graphic arc is a GTX680

Serviteur,

 

[jhowarth]

My graphic arc is a GTX680

Serviteur,

When you said 'clean install', did that mean that you repartitioned your drive to install on a empty APFS partition? Or do you mean the you reinstalled over a pre-existing installation?

 

[olrik77]

When you said 'clean install', did that mean that you repartitioned your drive to install on a empty APFS partition? Or do you mean the you reinstalled over a pre-existing installation?

I Nuked the disk before installing on an empty APFS partition.
Note : in my csrutil status I have "Apple internal : enabled"...all the other thing : Disabled

Serviteur,

 

[RV-ABZ]

The difference is that by using the Catalina Patcher 1.3.1 to create the patched installer, you got the required 'DisableLibraryValidation' field in /Library/Preferences/com.apple.security.libraryvalidation.plist set to '1'.

I'm not sure; I had manually added that (natively non-existing) plist to the /Library/Preferences folder (and verified permissions) when I was initially trying to fix things after the update.