macOS 10.15 Catalina on Unsupported Macs

[Pluda]

OUT OFF TOPIC

how about install Ipad OS on unsuported Ipads? I would love to have mu Ipad mini 2 using Ipad OS... 😁

 

[jackluke]

I have two disks. One with Mojave and another with Catalina. They both have a Recovery and Preboot partition in their APFS containers. The labels might be unique inside a container but there are two different containers which have the same labels. The command "diskutil info Recovery" gets info for the first Recovery partition which is in the Catalina APFS container no matter which OS I boot into.

If the two APFS containers share the same mount point for Recoveries, after my script in the worst case the APFS Mojave Recovery would be replaced by a Catalina APFS Recovery, but that boot the same with CMD+R.

Another example if you replace the HighSierra (or El Capitan) "Recovery HD" content inside the APFS Catalina Recovery UUID path it will work too with CMD+R.

The point is (till now) it's not possible to run with an "APFS Recovery role" the CMD+R with a customized/patched BaseSystem.dmg , only stock one will work due to an apple signature image integrity verification.

However mine is just a simple script for those who use it from Catalina for Catalina, in this scope I don't need to retrieve the Preboot UUID.

 

[jackluke]

OUT OFF TOPIC

how about install Ipad OS on unsuported Ipads? I would love to have mu Ipad mini 2 using Ipad OS... 😁

Minimum requirement is an iPad mini 4 for iPadOS (13.1), apart other improved hardware features, I guess at least 2 Gb RAM are required for every iOS 13 in general. Even iPad mini 3 had 1 Gb RAM.

 

[TimothyR734]

@TimothyR734 is your Safari same? I remembered you have an iMac9,1. This is probably a GPU related issue but I am not sure cause everything works better than Mojave on Catalina.

macOS 10.15 Catalina on Unsupported Macs

I have a problem with Safari on iMac 9,1. I am not sure this is discussed before but here it is; When I download something it is downloading, but the website turning to the white and no website address on the search bar. Does anyone know any solution for this problem?

forums.macrumors.com

Yes I have a iMac 9,1 and mine sometimes turns white while downloading as well but otherwise Catalina runs smooth for me

 

[BobW981]

Hi, my system is a late 2009 iMac 10.13 27, i7. A1312.
I followed Dosdude’s install video. Backed up my system to an internal Data drive using Time Machine. Installed the release version onto a memory stick. Reformatted my Mac SSD to apfs etc, and ran the install with the Patcher. No glitches, and all seemed well.

Problems started when I ran the Migration Assistant, which upon clicking on restore from a Time Machine, nothing happened. Needed a Force Quit to get out of it.

i then ran Time Machine, which doesn't recognise my Time Machine backup

Another glitch. As I loaded some of my photos to Photo, seems fine. When I double click on the images, they’re ’broken’ in psychedelic colours ????

I’ve manually restored a lot, and Catalina runs smoothly. Don't want to dig out the original software Apps, and hoped my backups would take care of things. ???

cheers, Bob

 

[Starplayr]

I am also experiencing no output from the DisplayPort on a Mac Pro 3,1 GTX 680 2GB Card on Catalina 10.15 GM. I have a previous beta and it works there.

HDMI and both DVI ports are working. Unable to get 4K @ 60 Hz on any of those ports. My card might only support 4k @60Hz on the DisplayPort.

I am using my own set of patches that can be found at https://starplayrx.com/#macpro

 

[jeffhalmos]

For anyone need to Repair or Create a Recovery HD of macOS Catalina 10.15
See this Catalina Recovery HD Partition
Thanks to Apple

Catalina installed. Samesung m.2 as boot drive. No Recovery volume. Command R not working. Followed the video letter for letter. BUT, now what? because Command R still doesn't work. Not sure what the next steps are if there are more steps.

 

[The.316]

Yes, yes, and yes. The only reason to not disregard the software update is if you wanted to download the Catalina installer through that source instead of through the patcher, but there's no need to do that. The Catalina patcher is al you need to run, though if you want light mode to work properly you will also need to install the BlueSky patch. I am able on my Mid 2009 MacBook Pro to transfer files freely between partitions on my hard drive using finder on Catalina, even though one partition is El Capitan and the other is Windows 7, so your files should transfer fine using that method.

So I can run the update through the official Mac update that its showing me? Sorry, thats whats confusing me. I don't really want to do a clean install, since Ive only been running Mojave for about 2 months.

 

[Starplayr]

OSX86 users are affected as well with the DisplayPort and their iMac profiles. One user changed his profile.

Mojave to Catalina Displayport Not Working

Hi All, Seems to be a lot of people having issues with DisplayPort not working after upgrading to Catalina, but HDMI still does - and I'm one of them. Everything else works - just not DisplayPort Have been struggling to find answers on any other threads as to how to fix, and I can't work out...

www.tonymacx86.com

 

[drpaul50]

Is there a link to instructions on how to install Catalina (like the one that was on the Mojave page)? I am giving this a try and praying I dont brick my MBA....

 

[Flacko]

I've disabled SIP but what do you mean with nvram no compat check?
Also, as far as I can remember, there was no option in the patcher to deselect an APFS software patch an automatic patching. My actual configuration involves a Metal supported Radon RX 560 and actual Wi-Fi and Bluetooth hardware.

The options for the patcher are in the menu bar. Select these before running the patcher. With SIP disabled run from terminal: sudo nvram boot-args="-no_compat_check" or if you do it from recovery you do not need the sudo. The cMP5.1 can run Catalina with this argument in nvram. Much more detail is given in the previous link I provided. Best to have the latest ROM which is 144.0.0.0.0 and as you have an RX 560 then the video side should be ok apart from no boot screen. If you have the original Wi-Fi then this will not work with Catalina without patching. Original Bluetooth is fine. With an upgraded Wi-Fi/BT the cMP5.1 runs Catalina OOB.

 

[Starplayr]

OSX86 users are affected as well with the DisplayPort and their iMac profiles. One user changed his iMac19,1 profile to Mac Pro 6,1 (Late 2013) to get DisplayPort to work.

Mojave to Catalina Displayport Not Working

Hi All, Seems to be a lot of people having issues with DisplayPort not working after upgrading to Catalina, but HDMI still does - and I'm one of them. Everything else works - just not DisplayPort Have been struggling to find answers on any other threads as to how to fix, and I can't work out...

www.tonymacx86.com

I know this is not an approved way to run a Mac Pro 3,1. However, I would like to report that using the default iMac 10,1 profile from Clover EFI driver, I was able to get the Display Port to output and at 4k @ 60Hz just like it did before it was broken.

The DisplayPort could be a security measure as Supported Mac users who use Docks, Converters or Dongles that use DisplayPort are also not working. Some of these users are able to turn on ScreenRecording where an affected driver needed to be checked in their Security panel and their displays started working.

Unrelated but DisplayLink Users | DisplayLink USB devices are also affected with Catalina and those users have special drivers and also need to turn on the Screen Recording permission.

I believe the fix lies somewhere in the middle of Security and SMBIOS profiles, but I have not been able to track the source. I tried replacing Display drivers last night. No dice and I checked IOPlatform... and swapping that did nothing.

None of the Nvidia drivers seem to be affected. It seems to be a SMBIOS or OpenFirmware issue ?

Masquerading as an iMac (27-inch, Late 2009) is working for my at this time. <!-- This is the farthest I have gotten so far using Clover EFI. I cannot recommenced it. But it seems we should be able to patch our systems to get DisplayPort to work again w/o Clover.

In Catalina, I may try copying the iMac 10,1 plist and place it in the Mac Pro 3,1 plist inside the IOPlatform kext.
[automerge]1570988568[/automerge]

 

[drpaul50]

System did not crash and booted up after the install. It crashes when I try to run the post installer patches. I am not able to run them from the recovery window but must actually search for it the file on the usb drive under applications. It comes up with prechecked options but crashes when trying to install. The patch updater did update 2 patches after a reboot. I guess I am okay??? Anything I should look for at this point?
I am just happy to be able to use my macbook air 2011 for a while longer. Thanks to all of you who know how to program and created these files and patches and the testers out there. It is much appreciated.

 

[nnauq]

First of all, thanks to dosdude1 and all others dedicated to make our machines survive a bit longer

I've had no problems installing Catalina on my Mac Pro (4,1 -> 5,1) using the patched installer and everything seems to work perfectly, except for unexpected kernel panics. I have been unable to pinpoint what I'm doing to make them happen, nor have I found any solutions online. Would appreciate it if someone has some insight into this.

macOSPanicString is either panic(cpu 8 caller 0xffffff800da290b7): "IOSCSIPeripheralDeviceType05::setPowerState(0xffffff803b9c2640 : 0xffffff7f8dcf218a, 1 -> 4) timed out after 101029 ms"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.11.26/iokit/Kernel/IOServicePM.cpp:5302 or panic(cpu 8 caller 0xffffff80082290b7): "PRT4::setPowerState(0xffffff80362a7400 : 0xffffff7f8b16a626, 0 -> 2) timed out after 31091 ms"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.11.26/iokit/Kernel/IOServicePM.cpp:5302 (with different timeouts etc.). See below for a full log.

{"macOSProcessedStackshotData":"bm8gb24gZGlzayBvciBzbGVlcC93YWtlIGZhaWx1cmUgcGFuaWMgc3RhY2tzaG90IGZvdW5k","macOSPanicString":"panic(cpu 8 caller 0xffffff800da290b7): \"IOSCSIPeripheralDeviceType05::setPowerState(0xffffff803b9c2640 : 0xffffff7f8dcf218a, 1 -> 4) timed out after 101029 ms\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu-6153.11.26\/iokit\/Kernel\/IOServicePM.cpp:5302\n
Backtrace (CPU 8), Frame : Return Address\n
0xffffff82a81f3b40 : 0xffffff800d33f98b \n
0xffffff82a81f3b90 : 0xffffff800d476c15 \n
0xffffff82a81f3bd0 : 0xffffff800d46861e \n
0xffffff82a81f3c20 : 0xffffff800d2e6a40 \n
0xffffff82a81f3c40 : 0xffffff800d33f077 \n
0xffffff82a81f3d40 : 0xffffff800d33f45b \n
0xffffff82a81f3d90 : 0xffffff800dad2d89 \n
0xffffff82a81f3e00 : 0xffffff800da290b7 \n
0xffffff82a81f3e50 : 0xffffff800da28c79 \n
0xffffff82a81f3e60 : 0xffffff800da4002e \n
0xffffff82a81f3ea0 : 0xffffff800da27a28 \n
0xffffff82a81f3ec0 : 0xffffff800d3811d5 \n
0xffffff82a81f3f40 : 0xffffff800d380d01 \n
0xffffff82a81f3fa0 : 0xffffff800d2e613e \n
\n
BSD process name corresponding to current thread: kernel_task\n
Boot args: -no_compat_check\n
\n
Mac OS version:\n
19A583\n
\n
Kernel version:\n
Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2\/RELEASE_X86_64\n
Kernel UUID: 70EDD61F-86EE-3E1B-873F-98D909B78160\n
Kernel slide:     0x000000000d000000\n
Kernel text base: 0xffffff800d200000\n
__HIB  text base: 0xffffff800d100000\n
System model name: MacPro5,1 (Mac-F221BEC8)\n
System shutdown begun: NO\n
Panic diags file available: YES (0x0)\n
\n
System uptime in nanoseconds: 2386822275448\n
last loaded kext at 14245991402: >!A!BMultitouch\t97 (addr 0xffffff7f90804000, size 57344)\n
last unloaded kext at 197928610694: >!AFileSystemDriver\t3.0.1 (addr 0xffffff7f8e0c7000, size 8192)\n
loaded kexts:\n
com.parrotgeek.SIPManager\t1\n
>!A!BMultitouch\t97\n
@fileutil\t20.036.15\n
@filesystems.msdosfs\t1.10\n
@filesystems.exfat\t1.4\n
@filesystems.ntfs\t3.14.3\n
@filesystems.autofs\t3.0\n
>AGPM\t111.1.18\n
>!AUpstreamUserClient\t3.6.8\n
>!AMCCSControl\t1.12\n
@kext.AMDFramebuffer\t3.0.0\n
@kext.AMDRadeonServiceManager\t3.0.0\n
>!AMikeyHIDDriver\t131\n
@kext.AMDRadeonX4000\t3.0.0\n
>!AGraphicsDevicePolicy\t4.1.46\n
@AGDCPluginDisplayMetrics\t4.1.46\n
>!AHDA\t281.52\n
>!AHV\t1\n
>!AMikeyDriver\t281.52\n
|IOUserEthernet\t1.0.1\n
|IO!BSerialManager\t7.0.0f8\n
>pmtelemetry\t1\n
@Dont_Steal_Mac_OS_X\t7.0.0\n
>!ALPC\t3.1\n
>ACPI_SMC_PlatformPlugin\t1.0.0\n
@kext.AMD7000!C\t3.0.0\n
>!AFWOHCI\t5.6.2\n
>!A!ISlowAdaptiveClocking\t4.0.0\n
>AudioAUUC\t1.70\n
@filesystems.apfs\t1412.11.7\n
>!AVirtIO\t1.0\n
@filesystems.hfs.kext\t522.0.9\n
@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d1\n
@BootCache\t40\n
@!AFSCompression.!AFSCompressionTypeZlib\t1.0.0\n
|SCSITaskUserClient\t422.0.2\n
>AirPort.Atheros40\t700.74.5\n
>!I82574LEthernet\t2.7.2\n
>!AAHCIPort\t341.0.2\n
@private.KextAudit\t1.0\n
>!ARTC\t2.0\n
>!AHPET\t1.8\n
>!AACPIButtons\t6.1\n
>!ASMBIOS\t2.1\n
>!AACPIEC\t6.1\n
>!AAPIC\t1.7\n
>!A!ICPUPowerManagementClient\t222.0.0\n
$!AImage4\t1\n
@nke.applicationfirewall\t302\n
$TMSafetyNet\t8\n
@!ASystemPolicy\t2.0.0\n
>!A!ICPUPowerManagement\t222.0.0\n
|EndpointSecurity\t1\n
>IO!BHIDDriver\t7.0.0f8\n
>!AMultitouchDriver\t3400.35\n
>!AInputDeviceSupport\t3400.27\n
@kext.triggers\t1.0\n
>!AHIDKeyboard\t209\n
|IOFireWireIP\t2.3.0\n
@kext.AMDRadeonX4030HWLibs\t1.0\n
|IOAccelerator!F2\t438.1.23\n
@kext.AMDRadeonX4000HWServices\t3.0.0\n
>!AGraphicsControl\t4.1.46\n
|IOAVB!F\t800.17\n
>DspFuncLib\t281.52\n
@kext.OSvKernDSPLib\t529\n
>!ASSE\t1.0\n
>!ASMBus!C\t1.0.18d1\n
|IONDRVSupport\t558.3\n
@!AGPUWrangler\t4.1.46\n
>!ASMBusPCI\t1.0.14d1\n
>IOPlatformPluginLegacy\t1.0.0\n
>IOPlatformPlugin!F\t6.0.0d8\n
>!AHDA!C\t281.52\n
|IOHDA!F\t281.52\n
@kext.AMDSupport\t3.0.0\n
@!AGraphicsDeviceControl\t4.1.46\n
|IOFireWire!F\t4.7.5\n
|IOSlowAdaptiveClocking!F\t1.0.0\n
|IOGraphics!F\t558.3\n
@plugin.IOgPTPPlugin\t800.14\n
|IOEthernetAVB!C\t1.1.0\n
|IOSkywalk!F\t1\n
|Broadcom!BHost!CUSBTransport\t7.0.0f8\n
|IO!BHost!CUSBTransport\t7.0.0f8\n
|IO!BHost!CTransport\t7.0.0f8\n
|IO!B!F\t7.0.0f8\n
|IO!BPacketLogger\t7.0.0f8\n
>usb.IOUSBHostHIDDevice\t1.2\n
|IOAHCIBlock!S\t316.0.5\n
>!UAudio\t320.47\n
|IOAudio!F\t300.2\n
@vecLib.kext\t1.2.0\n
>usb.networking\t5.0.0\n
>usb.!UHostCompositeDevice\t1.2\n
>usb.!UHub\t1.2\n
|IOSerial!F\t11\n
|IOSurface\t269.6\n
@filesystems.hfs.encodings.kext\t1\n
|IOSCSIMultimediaCommandsDevice\t422.0.2\n
|IOBD!S!F\t1.8\n
|IODVD!S!F\t1.8\n
|IOCD!S!F\t1.8\n
|IOAHCISerialATAPI\t268\n
|IO80211!F\t1200.12.2\n
>corecapture\t1.0.4\n
|IOAHCI!F\t290.0.1\n
>usb.!UEHCIPCI\t1.2\n
>usb.!UUHCIPCI\t1.2\n
>usb.!UUHCI\t1.2\n
>usb.!UEHCI\t1.2\n
>usb.!UHostPacketFilter\t1.0\n
|IOUSB!F\t900.4.2\n
>!AEFINVRAM\t2.1\n
>!AEFIRuntime\t2.1\n
|IOSMBus!F\t1.1\n
|IOHID!F\t2.0.0\n
$quarantine\t4\n
$sandbox\t300.0\n
@kext.!AMatch\t1.0.0d1\n
>DiskImages\t493.0.0\n
>!AFDEKeyStore\t28.30\n
>!AEffaceable!S\t1.0\n
>!AKeyStore\t2\n
>!UTDM\t489.11.2\n
|IOSCSIBlockCommandsDevice\t422.0.2\n
>!ACredentialManager\t1.0\n
>KernelRelayHost\t1\n
>!ASEPManager\t1.0.1\n
>IOSlaveProcessor\t1\n
|IOUSBMass!SDriver\t157.11.2\n
|IOSCSIArchitectureModel!F\t422.0.2\n
|IO!S!F\t2.1\n
|IOUSBHost!F\t1.2\n
>!UHostMergeProperties\t1.2\n
>usb.!UCommon\t1.0\n
>!ABusPower!C\t1.0\n
|CoreAnalytics!F\t1\n
>!AMobileFileIntegrity\t1.0.5\n
@kext.CoreTrust\t1\n
|IOTimeSync!F\t800.14\n
|IONetworking!F\t3.4\n
|IOReport!F\t47\n
>!AACPIPlatform\t6.1\n
>!ASMC\t3.1.9\n
>watchdog\t1\n
|IOPCI!F\t2.9\n
|IOACPI!F\t1.4\n
@kec.pthread\t1\n
@kec.corecrypto\t1.0\n
@kec.Libm\t1\n
\n
\n
"}

 

[sergioa21]

Hello, thanks @dosdude1 for the great work!
I report macOS Catalina 10.15 working great on a MacBook Pro 5,4 Mid 2009 (SSD and 8Gb Ram).

Anyone knows if is it safe to use the APFS Rom patcher in this model? has anyone tried???
Thanks for your answer!

 

[R@zor]

Reporting that Catalina runs on Mac Pro 3,1 thanks to @dosdude1 !

 

[lamerz78]

I’ve tried today to upgrade Mojave (patched) on my 2011 iMac 21,5 with k2000m video card. Directly from the patcher.

Result....nothing!

Black screen and infinite reboot loop.

Doing a PRAM reset I’m able to boot in High Sierra (first os).

I’ve tried everything :

created a usb boot installer from my other MacBook Air : result the iMac boot from usb (selected from HS because I’m blind without boot screen) the installer starts but can’t do anything. Apply post install patches don’t do nothing. From the usb installer I can’t select Hs or Catalina boot disk. They aren’t visibile.

I’ve tried to run the Catalina patcher from HS directly ..... nothing to do.... I’ve to disable SIP but I can’t boot in recovery.....

I’m frustrated!!!!

Please help.

Thanks

 

[jackluke]

I’ve tried today to upgrade Mojave (patched) on my 2011 iMac 21,5 with k2000m video card. Directly from the patcher.

Result....nothing!

Black screen and infinite reboot loop.

Doing a PRAM reset I’m able to boot in High Sierra (first os).

I’ve tried everything :

created a usb boot installer from my other MacBook Air : result the iMac boot from usb (selected from HS because I’m blind without boot screen) the installer starts but can’t do anything. Apply post install patches don’t do nothing. From the usb installer I can’t select Hs or Catalina boot disk. They aren’t visibile.

I’ve tried to run the Catalina patcher from HS directly ..... nothing to do.... I’ve to disable SIP but I can’t boot in recovery.....

I’m frustrated!!!!

Please help.

Thanks

From what I read the "k2000m video card" is a swapped non-apple/non-EFI GPU so it's normal you don't have the bootscreen, verbose etc. , but since it seems an Nvidia Kepler based GPU, should be Metal supported, you don't have to apply the "Video Patch", so just re-install Catalina (it's the only way to toggle the Video Patch), and during the post-install do not apply the "Video Patch".

 

[zephar42]

Hi I see you have a MacPro 3.1 with an Nvidia GTX680 installed, same as me. Recently installed Catalina
and would like to ask you a question if I may.
The GTX is connected to my Cinema Display via one of the DVI outputs, works fine. I also connect to my Sony 4k TV using the Displayport output to the Sony HDMI input, and there is no signal. Just to confirm there is no issue with this approach in Mojave, Sierra, El Capitan. Are you able to replicate this to see if you experience this problem. If I use the HDMI output on the card to the HDMI input on the TV there is no problem with the signal. Another thing is that in order to get sound from HDMI/ Displayport in other OS's it was necessary to install an HDMIAudio.kext that would allow the HDMI device to be selected in the Sys Prefs> Sound> Output selector, but needless to say it is not happening in Catalina. I wonder if you have any advice on that.

Thanks in advance.

@L Caputo - I use the HDMI port on my 4k TCL 43" TV. However, I was able to connect a 27" Dell monitor and can get a signal on both the DVI ports, but not on the DisplayPort. I believe there are other posts that stated the same thing. At some point the DisplayPort stopped working. Hopefully, Apple will fix that in a later update, but I'm running fine with the HDMI port.

 

[jackluke]

First of all, thanks to dosdude1 and all others dedicated to make our machines survive a bit longer

I've had no problems installing Catalina on my Mac Pro (4,1 -> 5,1) using the patched installer and everything seems to work perfectly, except for unexpected kernel panics. I have been unable to pinpoint what I'm doing to make them happen, nor have I found any solutions online. Would appreciate it if someone has some insight into this.

macOSPanicString is either panic(cpu 8 caller 0xffffff800da290b7): "IOSCSIPeripheralDeviceType05::setPowerState(0xffffff803b9c2640 : 0xffffff7f8dcf218a, 1 -> 4) timed out after 101029 ms"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.11.26/iokit/Kernel/IOServicePM.cpp:5302 or panic(cpu 8 caller 0xffffff80082290b7): "PRT4::setPowerState(0xffffff80362a7400 : 0xffffff7f8b16a626, 0 -> 2) timed out after 31091 ms"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.11.26/iokit/Kernel/IOServicePM.cpp:5302 (with different timeouts etc.). See below for a full log.

Maybe unrelated, but I'd attempt to boot in safe mode to check if kernel panic occurs, after power-on hold shift-key. Or remove some RAM, example if you have 32 gb leave 16 gb and check the behavior, otherwise try ask here: https://forums.macrumors.com/thread...-bootrom-upgrade-instructions-thread.2142418/

 

[Vyzantion]

Thank you. Did you create an installer with dosdude1 patcher then install the clover this installer USB right?

Yes. Edited the config.plist with Clover Confgurator. On Mojave I have initially used Multibeast, but it became buggy.

 

[lamerz78]

From what I read the "k2000m video card" is a swapped non-apple/non-EFI GPU so it's normal you don't have the bootscreen, verbose etc. , but since it seems an Nvidia Kepler based GPU, should be Metal supported, you don't have to apply the "Video Patch", so just re-install Catalina (it's the only way to toggle the Video Patch), and during the post-install do not apply the "Video Patch".

The only 1 time I’ve seen the post install patch the video card patch is not selected. Yes I’ve swapped video card in order to have Metal Support on Mojave.
Ok to reinstall Catalina....the problem is....HOW????

The usb installer created from HS or from Catalina (MacBook Air) reports an error like :The installer does not function....

 

[nandor690]

See my earlier post:https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27783779 you need to mount the disk and set it to read/write.
i did this in Beta 8 and it worked. Since then I have not needed to use it when moving through the betas and on to 15.0 so somehow the initial fix stuck.

Thank you sir. this worked perfectly. After restart I just had to turn handoff off and then back on in Catalina and all is good now.

 

[jackluke]

The only 1 time I’ve seen the post install patch the video card patch is not selected. Yes I’ve swapped video card in order to have Metal Support on Mojave.
Ok to reinstall Catalina....the problem is....HOW????

The usb installer created from HS or from Catalina (MacBook Air) reports an error like :The installer does not function....

If you need to disable SIP without a bootscreen, try this from your iMac HighSierra (assuming that is an HFS+ installation), open HighSierra Terminal and type:
sudo nvram boot-args="-no_compat_check"
(this should also allow to boot Catalina without patches)

Then from your HighSierra, open System Preferences - Startup Disk - pick your HighSierra Volume label, and let system reboot, right after the "power-on chime" hold CMD+R for 20 seconds, then wait at least 5 minutes, after that timeframe you should land on the official HighSierra Recovery and from there disable SIP with recovery terminal: csrutil disable

 

[FrankieDax]

It’s too bad I wanted to see if catalinia would work on a unsupport mid 2011 MacBook Air I got Catalina installed on a external hard drive, and I connected to my iMac I can boot into catalinia, if I try my MacBook Air it dose not boot

Did you ever make any progress with this? I also am trying to install catalina on a 2011 MacBook air. I have mojave on it and ran into no trouble installing that but for some reason no mater what I try I get the same prohibitory symbol (circle with diagonal line) when trying to instal catalina. I click the installer, I get the apple symbol, loads half way and then I get the prohibitory symbol.