macOS 10.15 Catalina on Unsupported Macs

[adam556]

I don't have an answer for you but I am interested to know if this is even possible. I believe AMFI requires SIP to be enabled and if you're running DosDude's Catalina patcher, SIP has to remain disabled otherwise you'll break some of the patches. Everything I've seen online indicates AMFI will trigger a kernel panic if SIP is turned off.

So the interesting thing is that I have been using Catalina with the latest version of the patcher with no problems AND amfi enabled (other than the issue of chrome and other third-party apps not opening due to codesignatures).

In order to solve this problem temporarily I was using xcode codesign command to manually codesign the app I want to open (which is a pain). In order to solve the problem "more permanently" I just today ran the code that @dosdude1 mentioned to disable AMFI. Now every app can open. But I dont want to keep AMFI disabled for security reasons.

 

[ulic]

Skylight is one of the Library Proxies installed by patcher v.1.4.4. If the Patch Updater in the /Libraryƒ has not been run very recently, do so. Also suggest running Onyx/Maintenance, the default settings are good. Trying to observe the failure with equivalent hardware and various adapters here yields nothing. One last thing - try a NVRAM reset. Let it bong three times. Since no one else is reporting this issue, suspect it is something local to your Mac? Hope this helps.

Hi, i got it finally working. I patched the SkylightOriginal file by removing the jump after the cmp command, that checks, if the library runs in the context of the WindowServer. So it will not throw the runtime assertion at address 00000000001d16fd.

So i replaced:
00000000001d155d cmp byte [_CGSRunningInServer.runningInServer], 0x1 ;
00000000001d1564 je loc_1d16e3

with:
00000000001d155d cmp byte [_CGSRunningInServer.runningInServer], 0x1 ;
00000000001d1564 nop
00000000001d1565 nop
00000000001d1566 nop
00000000001d1567 nop
00000000001d1568 nop
00000000001d1569 nop

After adhoc codesigning with "sudo codesign -f -s - SkyLightOriginal" and replacing the original, my displayport adapter is working.

I know, that this is not the optimal way to do this, but for me it worked. But I don't know, why it is working. Maybe a raise condition between WindowServer and the SkyLight library???

Thanks for all your help and the very good work to save an old mac, which is still working.

 

[K two]

So the interesting thing is that I have been using Catalina with the latest version of the patcher with no problems AND amfi enabled (other than the issue of chrome and other third-party apps not opening due to codesignatures).

In order to solve this problem temporarily I was using xcode codesign command to manually codesign the app I want to open (which is a pain). In order to solve the problem "more permanently" I just today ran the code that @dosdude1 mentioned to disable AMFI. Now every app can open. But I dont want to keep AMFI disabled for security reasons.

Keeping X-Protect and MRT up-to-date is far more important. ?

 

[a2ml]

Hello,

First at all, thank you in advance for your support and creating this patches that allows us to continue using our MacBooks with the latest OS after their "expiration date".

I want to upgrade the ROM on a mid-2009 13" MacBook Pro (A1278 - MacBookPro5,5). The chip from the board is 25L32050M2I.

I have a few questions for which I have not been able to find a definitive answer after some web searches. Apologies if they are too basic questions:

• Once that I upgrade the ROM, can I still boot HFS+ disks?
• I read that the APFS BootROM patch app saves a copy of the existing ROM, is it possible to program back the BIOS with this saved file without desoldering and soldering back the chip?
• Being my ROM a 25L32050M2I, what option should I select when I run the APFS ROM Patcher? I get the following three options:
  • M25L3205(A)
  • M25L3205D/M25L3208D
  • M25L3206E

I am attaching a picture of the chip as a reference and the options I get from the patcher.


Thanks in advance.

 

[K two]

Hello,

First at all, thank you in advance for your support and creating this patches that allows us to continue using our MacBooks with the latest OS after their "expiration date".

I want to upgrade the ROM on a mid-2009 13" MacBook Pro (A1278 - MacBookPro5,5). The chip from the board is 25L32050M2I.

I have a few questions for which I have not been able to find a definitive answer after some web searches. Apologies if they are too basic questions:

• Once that I upgrade the ROM, can I still boot HFS+ disks?
• I read that the APFS BootROM patch app saves a copy of the existing ROM, is it possible to program back the BIOS with this saved file without desoldering and soldering back the chip?
• Being my ROM a 25L32050M2I, what option should I select when I run the APFS ROM Patcher? I get the following three options:
  • M25L3205(A)
  • M25L3205D/M25L3208D
  • M25L3206E

I am attaching a picture of the chip as a reference and the options I get from the patcher.


Thanks in advance.

Suggest DM to collinmistr@gmail.com regarding this question.

 

[joevt]

Being my ROM a 25L32050M2I

The picture shows 25L3205DM2I so I guess you need to choose M25L3205D/M25L3208D

 

[jgleigh]

new security update 19H512 has anyone installed it?

Just installed using CatalinaOTAswufix on Mac Pro 5,1 and then updated dosdude1's patches. No issues so far.

 

[oeyvind]

thanks!

 

[KeithJohn]

Hi All, Just installed the 19H512 security update, well I thought I did because it shows I have still got macOS 10.15.7 (19H2) this is on my Mac Pro 3.1, I used dosdudes patcher and downloaded a fresh install through that, have I done something wrong ? All went well with the patch updater after so no problems, my Mac Mini late 2012 updated last night and that shows 19H512 or have I got the all wrong and my Mac Pro will only show macOS 10.15.7 (19H2) ?

 

[_Julian_]

I have tried to install the Update today on my iMac 9,1 but it hangs at the White Screen after a while saying that the Files can't be copied to the Destination, please reboot and try again. I can't get any further from that. Any suggestions?

 

[ghost82]

All good on my macbook pro early 2008 with 19H512: the catalina ota fix still didn't work for me, I used the manual approach:

macOS 10.15 Catalina on Unsupported Macs

@telepati I managed to install the 19H114 update in my macbook pro 4,1 in an hybrid and strange manner :D Here what worked for me: 1. Prepared a usb bootable with Opencoreloader v3 2. Downloaded the update from software update (do not restart), download it all 3. Show package content of the...

forums.macrumors.com

 

[KennyW]

Also work in my iMac 2010 with Catalina OTA swu fix for 19H512

 

[amstel78]

19H512 installed just fine on my APFS BootROM MP3,1 using CatalinaOTAswufix. Had to run post-install patches again and rebuild caches to get WiFi and audio back, but otherwise the update was uneventful.

 

[_Julian_]

After 7 Hours of trying to get this F... Patch onto my Girlfriends iMac i give up. It doesn't work no matter which Version of Updating this Machine i choose. That cost me way to much Lifetime in my opinion. Can i make a Windows PC out of this old crap? So that only Windows 10 boots up in Future where i can install the Updates normally.

 

[K two]

Hi All, Just installed the 19H512 security update, well I thought I did because it shows I have still got macOS 10.15.7 (19H2) this is on my Mac Pro 3.1, I used dosdudes patcher and downloaded a fresh install through that, have I done something wrong ? All went well with the patch updater after so no problems, my Mac Mini late 2012 updated last night and that shows 19H512 or have I got the all wrong and my Mac Pro will only show macOS 10.15.7 (19H2) ?

Suspect the v.1.4.4 Patcher still provides 19H2. You'll need @jackluke's CatalinaOTAswufix.app to update. The late 2012 Mini supports Catalina so updates occur, automatically.

 

[a2ml]

The picture shows 25L3205DM2I so I guess you need to choose M25L3205D/M25L3208D

Thank you. Looks like I need new glasses :-/

 

[K two]

Thank you. Looks like I need new glasses :-/

Good luck. ?

 

[K two]

All good on my macbook pro early 2008 with 19H512: the catalina ota fix still didn't work for me, I used the manual approach:

macOS 10.15 Catalina on Unsupported Macs

@telepati I managed to install the 19H114 update in my macbook pro 4,1 in an hybrid and strange manner :D Here what worked for me: 1. Prepared a usb bootable with Opencoreloader v3 2. Downloaded the update from software update (do not restart), download it all 3. Show package content of the...

forums.macrumors.com

If the OTA SW Fix button fails. Trash everything in the /Library/Updates ƒ and start over, both buttons. The problem is not applying the OTA SW Fix button early-on.

 

[K two]

I have tried to install the Update today on my iMac 9,1 but it hangs at the White Screen after a while saying that the Files can't be copied to the Destination, please reboot and try again. I can't get any further from that. Any suggestions?

Did you do this before you started? https://discussions.apple.com/docs/DOC-3603

 

[Jeff1casey]

Successfully intalled Catalina 10.15.7 on a PowerMac 5,1 mid 2012. However, it seems I have to reapply the post-install patches almost every time I reboot because startup stalls on the Apple logo. I then need to reboot from the USB installer, reapply the patches, then reboot to the drive with Catalina, and often need to reset PRAM in the process. Any ideas?

 

[Menno03]

I want to install Catalina on a Macbook 5,4 and need to convert to APFS. But I'm a bit confused about this warning: 'APFS BootROM Support: If you have a machine that supports High Sierra natively, you MUST ensure you have the latest version of the system's BootROM installed. If you have NOT previously installed High Sierra, you can download and install this package (if running OS X 10.10 Yosemite or later) to install the latest BootROM version (you MUST reboot after installing the package to apply the firmware update). When installing, ensure your system is plugged in to power, or the update will not be installed.'
My question is: 1) Does this message only apply to machines that support High Sierra natively? 2) do I install this package before upgrading to Catalina/APFS

 

[jgleigh]

Suspect the v.1.4.4 Patcher still provides 19H2. You'll need @jackluke's CatalinaOTAswufix.app to update. The late 2012 Mini supports Catalina so updates occur, automatically.

The Catalina Patcher relies on full installers. The last full installer was 19H15 and even that version usually required gibMacOS to download. Everything after 19H15 has been security updates that can only be loaded using CatalinaOTAswufix.

 

[K two]

The Catalina Patcher relies on full installers. The last full installer was 19H15 and even that version usually required gibMacOS to download. Everything after 19H15 has been security updates that can only be loaded using CatalinaOTAswufix.

The v.1.4.4 Patcher also D/L a full macOS installer, it may be 19H2? I haven't tried to use the built-in D/L function since using gibMacOS.

 

[K two]

Another update in - runs fine, no hiccups.

 

[makra]

I managed to install19H512 the way you did, but couldn't see any wifi networks at first. Tried to run the Post-install patches several times. SMC and PRAM didn't help either. Only after running OnyX everything was fine again.

Now I saw, that the firmware version of my AirPort Extreme is "Broadcom BCM43xx 1.0 (5.106.98.102.31)". Would it be a good idea to check the "Broadcom BCM4321"(?)-option in Dosdude1's patcher manually from now on?