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.
just upgrade your iMac's GPU.
just a little while back an bootscreen EFI mod is also released, and works great ;)

I've so far upgraded two iMac's and applied the EFI mod to hem, and Mojave/Catalina works fine now..

Check out this thread :

I still hope one day, HD3000 kexts are put back into the Mojave/Catalina patchers to get sleep mode working again, and I think also Airplay mirroring require them for these 2011 iMac's..

Also by default disabling legacy graphics patch on the Mojave patcher from dosdude1, like it is now with Catalina patcher would be great if made possible ! :)
My mac works perfect.
 

Attachments

  • Captura de pantalla 2019-09-20 a las 14.26.11.png
    Captura de pantalla 2019-09-20 a las 14.26.11.png
    57.9 KB · Views: 430
Hello,

I recently installed 10.15 onto my mbp 5,5 (mid-2009) and everything is working alright!
Back in the Mojave days, I used @dosdude1’s APFS Boot Rom Patcher so that my machine can natively boot APFS without the patch. However, now that patches are automatic through the installer, it automatically installs the APFS patch which runs the black and yellow lines of code before booting into any APFS drive.
Is there any way to uninstall this patch since I natively boot APFS now?
 
  • Like
Reactions: TimothyR734
Hello,

I recently installed 10.15 onto my mbp 5,5 (mid-2009) and everything is working alright!
Back in the Mojave days, I used @dosdude1’s APFS Boot Rom Patcher so that my machine can natively boot APFS without the patch. However, now that patches are automatic through the installer, it automatically installs the APFS patch which runs the black and yellow lines of code before booting into any APFS drive.
Is there any way to uninstall this patch since I natively boot APFS now?
Yeah, all you really need to do is set your Startup Disk in System Preferences. If you want to completely get rid of the files, you can mount your ESP, and remove the EFI/BOOT directory.
 
On my mac Pro 5,1 with an updated WiFi/BLE card, I turn off SIP and use a couple of commands done by CAT:

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-F221BEC8\0\0\0\0\0\0\0\0/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360

Actually I do this from a Mojave boot.

I re-enable SIP after that and Continuity and Watch Unlock works.
I can confirm this works from Catalina B8. Had to use these commands to get continuity fully working in my cMP5.1 but strangely my cMP3.1 works OOB with no further actions required. Both using BCM94360CD! Few extra steps when using Catalina.

1. SIP disabled
2. Mount system drive otherwise you cannot make any changes (do not know how long we will be able to do this)

sudo mount -uw /

3. Run these to add cMP5.1 "True" for continuity to work:

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-F221BEC8\0\0\0\0\0\0\0\0/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360

4. Kext Cache:

sudo touch /Library/Extensions

sudo kextcache -i /

Restart and all should now work fully. You can enable SIP if you want to.
 
Yeah, all you really need to do is set your Startup Disk in System Preferences. If you want to completely get rid of the files, you can mount your ESP, and remove the EFI/BOOT directory.

Collin, Thanks for the work on keeping these older Macs going. I hope most people who use your work would donate, as a way to say thank you. How do system updates work with this patcher? Security updates? Do we just reinstall as upgrade every time a new version is released or can we allow the regular upgrades through Mac to take place? In Mojave, I remember I could not allow regular updates.

So far for me, everything in this Beta works as it should in this Beta, according to official Mac released Beta's for supported machines. This includes the lag in preferences, night shift not working, and the auto dark mode switcher also not working.

Thanks for your hard work!
 
Collin, Thanks for the work on keeping these older Macs going. I hope most people who use your work would donate, as a way to say thank you. How do system updates work with this patcher? Security updates? Do we just reinstall as upgrade every time a new version is released or can we allow the regular upgrades through Mac to take place? In Mojave, I remember I could not allow regular updates.

So far for me, everything in this Beta works as it should in this Beta, according to official Mac released Beta's for supported machines. This includes the lag in preferences, night shift not working, and the auto dark mode switcher also not working.

Thanks for your hard work!

The most robust way to upgrade from one point release to the next is to recreate the usb installer from the most current Catalina Patcher and just do an upgrade install. This approach is bullet-proof through the final supplemental update releases (which get revised full installers). The later security updates can be a mixed bag. If they touch the recovery partition or provide firmware updates, the installer package will have to be hand patched and rebuilt.
 
The most robust way to upgrade from one point release to the next is to recreate the usb installer from the most current Catalina Patcher and just do an upgrade install. This approach is bullet-proof through the final supplemental update releases (which get revised full installers). The later security updates can be a mixed bag. If they touch the recovery partition or provide firmware updates, the installer package will have to be hand patched and rebuilt.

Okay, Thank you for your help.
 
  • Like
Reactions: TimothyR734
Yeah, all you really need to do is set your Startup Disk in System Preferences. If you want to completely get rid of the files, you can mount your ESP, and remove the EFI/BOOT directory.
Hi Dos...Beta 9 just came out 2 hours ago...Is it ready for the Catalina patcher?..Just being safe..?
 
  • Like
Reactions: TimothyR734
DP 9 is out. PB 8 is not out yet, I see. Has anyone managed to get DP9 or pb 8? I assume dosude1 app and macOS Downloader need to be updated. Right?
 
  • Like
Reactions: TimothyR734
DP 9 is out. PB 8 is not out yet, I see. Has anyone managed to get DP9 or pb 8? I assume dosude1 app and macOS Downloader need to be updated. Right?
Update has just been released for Catalina Patcher. It will be able to download the installer, and create a usable installer for you with DP9. If you're creating the drive using DP8, you'll have to apply this patch to Catalina Patcher to bypass an error only present in Catalina DP8: https://forums.macrumors.com/thread...supported-macs.2183772/page-176#post-27741278
 
I usually copy and keep your download and patch Catalina app outside the DMG into a folder on my secondary, ATA HFS+ hard drive and run it from there. If I do the same now and run the script into Terminal, it should ok? Or I need to keep the app into a certain location on the main APFS hard drive, where macOS is installed? Do I need to run it as sudo?
 
Last edited:
  • Like
Reactions: TimothyR734
Screen Shot 2019-09-23 at 2.33.39 PM.png
Screen Shot 2019-09-23 at 2.32.56 PM.png

[automerge]1569275170[/automerge]
Did successfully install Cat Dev beta 9 using an older cat patcher using the install to this machine method and applying the post install patches BlueSky also working :)
 
  • Like
Reactions: ASentientBot
I usually copy and keep your download and patch Catalina app outside the DMG into a folder on my secondary, ATA HFS+ hard drive and run it from there. If I do the same now and run the script into Terminal, it should ok? Or I need to keep the app into a certain location on the main APFS hard drive, where macOS is installed? Do I need to run it as sudo?
Yeah, that's fine. Should not need to run it as sudo, all it's doing is patching the "patcherd" binary in Catalina Patcher.
 
  • Like
Reactions: TimothyR734
The Catalina install app needs to be in a certain place?
Yes if you have the instal Catalina Beta app in applications and then make a patcher after you install the beta it gets erased from the application folder so I leave it it the downloads folder the only time I move it is to check to see if I have downloaded the current version
 
Public Beta 8 was released, I am downloading something that has about 5 gb. Is this the install app or do I need to download it using the dosdude1 app? The dosdude1 app has about 8 gb to download. DP8/PB7 was the first Catalina version I have successfully installed, so I do not know if this works?
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.