macOS 10.15 Catalina on Unsupported Macs

[L Caputo]

@dosdude1 - So I had previously had trouble installing beta 10 with 1.1.5, but I somehow managed to successfully install the official Catalina release with 1.1.7. I don't know what caused it to work, but here is what I did in case someone else has the same problem.

Originally, when I tried to install beta 10 with 1.1.5, it started to boot off the USB drive, but then showed a screen with a circle and line thru the circle.

Today, I tried to install the official Catalina release with 1.1.7 from a USB stick and it showed me the same screen with a circle and line thru the circle.

I then tried to install the official Catalina release directly to the Mac Pro 3,1 instead of the USB stick, and it appeared to start installing, but then rebooted back into beta 8 (I had skipped beta 9). Before doing the direct install to the machine, I had also pulled all the drives except the Catalina SSD drive to make sure I didn't mess up my other drives.

Here's what I have in each bay...
Bay 1 - Mojave SSD - Mac OS Extended
Bay 2 - Catalina SSD - APFS
Bay 3 - Mojave HD - Mac OS Extended
Bay 4 - Windows Bootcamp SSD - NTFS

With only one drive in Bay 2 and the others removed, I then tried booting from the USB stick and it worked!!! Maybe having those extra drives installed caused my previous problem?!?!

Anyway.. the official Catalina release is all up and running on my MacPro 3,1 with a GTX 680 card and all the drives back in their bays.

@dosdude1 - Thanks for keeping these old Mac's up and running with the latest OS!!!!

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.

 

[ASentientBot]

(tl;dr: the AVX dependence for Japanese input goes back all the way to Catalina DP1, unfortunately)

For what it's worth, I found an external SSD installation of macOS Catalina DP1 (19A471t) that I did on an officially supported Mac back in June. On a MacBook7,1 (Penryn), I booted a USB drive of the Catalina release (19A583) with version 1.1.7 of the dosdude patch, used that to patch the DP1 external SSD, then booted off the external SSD and tried to use Japanese input. Japanese input was nonfunctional, and at one point TextEdit just crashed on me. Then I shut down, booted a MacBookPro8,1 (Sandy Bridge) off the same external SSD, and Japanese input worked fine. To be extra sure, I then booted the MacBook7,1 off the external SSD again, and again Japanese input failed to work (and I was also able to find the crash logs for JapaneseIM, showing illegal instruction crashes in MecabraQueue).

Yeah, I reported the same result a couple days ago, unfortunately.

That leaves pretty much the only option as copying in Mojave's library and either shim-ing it to be compatible with Catalina (hard), or replacing other related libraries as well (risky).

I'll mess around with it some more when I get a chance, but I'm not highly optimistic. If a 3rd party app (posted earlier on this page) works adequately, that's probably the best solution.

Or, just stay on Mojave, since Cat doesn't add many features anyways. I actually think it's more trouble than it's worth for 90% of use cases. To me, this is rapidly becoming a "can I do this" project, rather than a practical one. 10.14.6 is rock-solid and doesn't require my sketchy accel patches, so I'm sticking with that as my daily system until probably the end of time.

 

[Alex-Microsmeta]

@dosdude1 @ASentientBot @parrotgeek1 Almost all ok now with Cat final patched 1.1.7 on Macmini4,1. CPU is 3-10% IDLE and I can do heavy tasks like streaming contents from Plex Server to Chromecast.

Only USB wired PC keyboard caps locks, num lock and scroll lock LEDS do not light on Catalina, but they work on Mojave.

 

[LarryJoe33]

Hi, the answer to this is probably in this very long thread. I used DosDude's app to upgrade from Mohave to Catalina. I noticed I am signed up for betas now and wasn't before the in place upgrade.

Is this a requirement for his app to work properly?

 

[joevt]

I made a script some days ago (it still works with the current 10.15 release): https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27830096

I did exactly that, since for now there is no a way to boot a custom Recovery with CMD+R, a minimal script to replace the patched APFS Recovery BaseSystem.dmg with an apple stock one, replacing also the immutablekernel Recovery needed for machines with very legacy IOUSB and Wifi.

My script keep the same UUID without need to re-adjust, however re-adjusting manually the UUID for an APFS installation is relatively simple:
diskutil apfs changeVolumeRole diskXs3 R
diskutil apfs updatePreboot diskXs1

Does the script download the latest recovery or the beta recovery (the URL seems like it would be very specific)?
The script appears to need to be run from a Catalina system.
The script uses the first Recovery partition instead of the one belonging to the current system (if there's more than one)?
What's the purpose of backing up the PlatformSupport.plist file?
The script assumes the existing UUID is correct. Those separate diskutil apfs commands will fix the UUID if it is wrong? The diskutil man page in Catalina has much more info about the apfs commands than in Mojave. I think diskutil has more features in Catalina too.

Well as far as I can tell there are no ill effects so far using the Catalina Patcher USB on a supported machine. There was no Patch Updater installed, NightShift is original by Apple, and the MBP gets point updates via Software Update like any other supported Mac, i.e. 10.15.1 DP1.

And the MBP can boot into Recovery with Command-R (which is the problem I described with my Mac Mini 2018)?

How do we know what OS vertion is downloade from the patcher?

Instead of downloading using the patcher, I download installers from the App Store (or Software Update or wherever), and back them up to a different drive so they don't waste disk space on my OS partition and I can use the same installer later on a USB stick for a different Mac or Hackintosh using the various USB installer creators that exist (patcher, createinstallmedia, etc.)

 

[GSXB]

Just a thought, how do I / we install 10.15.1

 

[friolz]

I have a problem with the Catalina Patcher on my Mac Pro 4,1 (patched to a 5,1):
I've did I direct install and now after powering on the Mac it takes about 30 seconds and it is shutting off.
Seems like I've bricked it. Did anyone notice the same behavior and hopefully has a solution to this?

 

[Glujaz]

I have a problem with the Catalina Patcher on my Mac Pro 4,1 (patched to a 5,1):
I've did I direct install and now after powering on the Mac it takes about 30 seconds and it is shutting off.
Seems like I've bricked it. Did anyone notice the same behavior and hopefully has a solution to this?

If you can boot from the USB stick, you MP is not bricked, and there is simply a faulty installation. Did you do the Mac OS post install ?

 

[friolz]

I didn't create an USB stick but chose the Direct Install method from within Mojave. I also couldn't reach the point where I could do the post install.

 

[Glujaz]

You need to do it from a usb stick

 

[Flacko]

Am I just running these from terminal from the desktop or do I need to run these from terminal while booted in recovery? thanks for the help

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.

 

[Flacko]

I have a problem with the Catalina Patcher on my Mac Pro 4,1 (patched to a 5,1):
I've did I direct install and now after powering on the Mac it takes about 30 seconds and it is shutting off.
Seems like I've bricked it. Did anyone notice the same behavior and hopefully has a solution to this?

Hi, 4.1 >5.1 here running Catalina unpatched. Confirm you disabled SIP first and set the nvram no compat check. Then in options of the patcher deselect the APFS software patch and select not to have automatic patching before you start the patcher. This should bring you to a working Catalina. What is your actual configuration? Graphics card, Wi-Fi and ROM especially as there are a few issues with older hardware. Have a good look at the thread:

Obsolete, Use OpenCore instead | What you need to do to make Catalina work with MacPro5,1

Obsolete, please use OpenCore to have native installs of Catalina with MP5,1. https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/

forums.macrumors.com

 

[StarIlia]

Good day! MacBook Pro 2009 (5.5) Catalina. Tried from the very first versions, now tried and final. But the problem is always the same-the installation goes fine, the computer boots and works. But, spontaneous reboots begin. It cycles, one after the other. After reboot, the error comes out:
"panic(cpu 0 caller 0xffffff8001e689ca): Kernel trap at 0xffffff7f82f22f2d, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffef7f82ff6c50, CR3: 0x0000000179ba1000, CR4: 0x00000000000026e0
RAX: 0xffffef7f82ff6af8, RBX: 0xffffff8012b8f200, RCX: 0xffffff80133d9000, RDX: 0x0000000000000000
RSP: 0xffffff910e163b90, RBP: 0xffffff910e163bd0, RSI: 0x0000000000000024, RDI: 0xffffff801347cb40
R8: 0x0000000000000000, R9: 0xffffff802249ca90, R10: 0x000000044b82fa08, R11: 0x0000000000000000
R12: 0x15cc7d3c68c8ea22, R13: 0x0000000000000000, R14: 0x15cc7d3c690625a8, R15: 0x0000000000000024
RFL: 0x0000000000010282, RIP: 0xffffff7f82f22f2d, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffef7f82ff6c50, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1
Backtrace (CPU 0), Frame : Return Address
0xffffff910e1635f0 : 0xffffff8001d3f98b
0xffffff910e163640 : 0xffffff8001e76c15
0xffffff910e163680 : 0xffffff8001e6861e
0xffffff910e1636d0 : 0xffffff8001ce6a40
0xffffff910e1636f0 : 0xffffff8001d3f077
0xffffff910e1637f0 : 0xffffff8001d3f45b
0xffffff910e163840 : 0xffffff80024d2d89
0xffffff910e1638b0 : 0xffffff8001e689ca
0xffffff910e163a30 : 0xffffff8001e686c8
0xffffff910e163a80 : 0xffffff8001ce6a40
0xffffff910e163aa0 : 0xffffff7f82f22f2d
0xffffff910e163bd0 : 0xffffff7f82f15e6d
0xffffff910e163d50 : 0xffffff8001fcde12
0xffffff910e163dc0 : 0xffffff8001fbee6e
0xffffff910e163e20 : 0xffffff80022b8740
0xffffff910e163ee0 : 0xffffff80022b8a14
0xffffff910e163f40 : 0xffffff800239b999
0xffffff910e163fa0 : 0xffffff8001ce7206
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1412.11.7)[B26D7DE6-BE2D-3E44-B334-1346AEC6C3BB]@0xffffff7f82ed6000->0xffffff7f82ffafff
dependency: com.apple.kec.corecrypto(1.0)[263BCEB0-E4C5-3540-9E03-CC1F0A4D5BDF]@0xffffff7f8269f000
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[D4D0276C-28F7-3878-AC53-86A1134225E0]@0xffffff7f82e82000
dependency: com.apple.iokit.IOStorageFamily(2.1)[CAC103D2-4533-3A81-8190-D0133B4F8626]@0xffffff7f82665000
BSD process name corresponding to current thread: WhatsApp
Boot args: -no_compat_check
Mac OS version:
19A583
Kernel version:
Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64
Kernel UUID: 70EDD61F-86EE-3E1B-873F-98D909B78160
Kernel slide: 0x0000000001a00000
Kernel text base: 0xffffff8001c00000
__HIB text base: 0xffffff8001b00000

System model name: MacBookPro5,5 (Mac-F2268AC8)

System shutdown begun: NO

Panic diags file available: YES (0x0)

System uptime in nanoseconds: 233580430192

last loaded kext at 119607822920: com.adguard.nfext 26 (addr 0xffffff7f85074000, size 184320)

loaded kexts:

com.adguard.nfext 26

com.parrotgeek.SIPManager 1

@fileutil 20.036.15

>AudioAUUC 1.70

>!AGraphicsDevicePolicy 3.28.4

@AGDCPluginDisplayMetrics 3.28.4

>!AHV 1

@filesystems.autofs 3.0

|IOUserEthernet 1.0.1

|IO!BSerialManager 7.0.0f8

>pmtelemetry 1

>!AUpstreamUserClient 3.6.8

>!AHDAHardwareConfigDriver 281.52

>AGPM 110.23.46

>!AMikeyHIDDriver 131

@Dont_Steal_Mac_OS_X 7.0.0

@GeForceTesla 10.0.4

>AGDCBacklightControl 4.1.46

>!AHDA 281.52

>!AMikeyDriver 281.52

>!ABacklight 170.18

>SMCMotionSensor 3.0.4d1

@nvenet 2.0.22

>!ASMCLMU 212

>AirPort.Brcm4331 800.21.31

>!ALPC 3.1

>ACPI_SMC_PlatformPlugin 1.0.0

>!AFWOHCI 5.6.2

>!AFIVRDriver 4.1.0

>!A!ISlowAdaptiveClocking 4.0.0

@nvidia.NVDAStartup 14.0.0

>!AMCCSControl 1.5.6

>!UTCKeyEventDriver 255

>!UTCButtons 255

>!UTCKeyboard 255

|IO!BUSBDFU 7.0.0f8

>!AIR!C 360

>!U!SCoexistentDriver 489.11.2

>!UCardReader 489.11.2

@filesystems.apfs 1412.11.7

>!AFileSystemDriver 3.0.1

>!AVirtIO 1.0

@filesystems.hfs.kext 522.0.9

@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1

@BootCache 40

@!AFSCompression.!AFSCompressionTypeZlib 1.0.0

|SCSITaskUserClient 422.0.2

@private.KextAudit 1.0

>!AAHCIPort 341.0.2

>!ASmartBatteryManager 161.0.0

>!ARTC 2.0

>!AHPET 1.8

>!AACPIButtons 6.1

>!ASMBIOS 2.1

>!AACPIEC 6.1

>!AAPIC 1.7

>!A!ICPUPowerManagementClient 222.0.0

$!AImage4 1

@nke.applicationfirewall 302

$TMSafetyNet 8

@!ASystemPolicy 2.0.0

>!A!ICPUPowerManagement 222.0.0

|EndpointSecurity 1

>!AGraphicsControl 3.28.4

|IOAVB!F 800.17

@kext.triggers 1.0

>!ASSE 1.0

@plugin.IOgPTPPlugin 800.14

|IOEthernetAVB!C 1.1.0

|IOSkywalk!F 1

@nvidia.classic.NVDANV50HalTesla 10.0.4

@nvidia.classic.NVDAResmanTesla 10.0.4

>DspFuncLib 281.52

@kext.OSvKernDSPLib 529

|IOFireWireIP 2.3.0

@!AGPUWrangler 3.28.4

@!AGraphicsDeviceControl 3.28.4

>!ABacklightExpert 1.1.0

|IONDRVSupport 519.15

>!AHDA!C 281.52

|IOHDA!F 281.52

|IOAudio!F 300.2

@vecLib.kext 1.2.0

|IO80211!F 1200.12.2

>corecapture 1.0.4

>NVSMU 2.2.9

>IOPlatformPluginLegacy 1.0.0

>IOPlatformPlugin!F 6.0.0d8

>!ASMBusPCI 1.0.14d1

|IOFireWire!F 4.7.5

|IOSlowAdaptiveClocking!F 1.0.0

>!ASMBus!C 1.0.18d1

|IOGraphics!F 519.15

>!UMultitouch 264

|Broadcom!BHost!CUSBTransport 7.0.0f8

|IO!BHost!CUSBTransport 7.0.0f8

|IO!BHost!CTransport 7.0.0f8

|IO!B!F 7.0.0f8

|IO!BPacketLogger 7.0.0f8

>usb.IOUSBHostHIDDevice 1.2

>usb.!UHub 1.2

|IOUSBMass!SClass 4.0.4

>usb.cdc 5.0.0

>usb.networking 5.0.0

>usb.!UHostCompositeDevice 1.2

>!AXsanScheme 3

|IOSerial!F 11

|IOSurface 269.6

@filesystems.hfs.encodings.kext 1

|IOSCSIMultimediaCommandsDevice 422.0.2

|IOBD!S!F 1.8

|IODVD!S!F 1.8

|IOCD!S!F 1.8

|IOAHCISerialATAPI 268

|IOAHCIBlock!S 316.0.5

|IOAHCI!F 290.0.1

>usb.!UHostPacketFilter 1.0

|IOUSB!F 900.4.2

>usb.!UEHCIPCI 1.2

>usb.!UOHCIPCI 1.2

>usb.!UOHCI 1.2

>usb.!UEHCI 1.2

>!AEFINVRAM 2.1

>!AEFIRuntime 2.1

|IOSMBus!F 1.1

|IOHID!F 2.0.0

$quarantine 4

$sandbox 300.0

@Kext.!AMatch 1.0.0d1

>DiskImages 493.0.0

>!AFDEKeyStore 28.30

>!AEffaceable!S 1.0

>!AKeyStore 2

>!UTDM 489.11.2

|IOSCSIBlockCommandsDevice 422.0.2

>!ACredentialManager 1.0

>KernelRelayHost 1

>!ASEPManager 1.0.1

>IOSlaveProcessor 1

|IOTimeSync!F 800.14

|IONetworking!F 3.4

|IOUSBMass!SDriver 157.11.2

|IOSCSIArchitectureModel!F 422.0.2

|IO!S!F 2.1

|IOUSBHost!F 1.2

>!UHostMergeProperties 1.2

>usb.!UCommon 1.0

>!ABusPower!C 1.0

|CoreAnalytics!F 1

>!AMobileFileIntegrity 1.0.5

@kext.CoreTrust 1

|IOReport!F 47

>!AACPIPlatform 6.1

>!ASMC 3.1.9

>watchdog 1

|IOPCI!F 2.9

|IOACPI!F 1.4

@kec.pthread 1

@kec.Libm 1

@kec.corecrypto 1.0"

 

[friolz]

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.

Hi, 4.1 >5.1 here running Catalina unpatched. Confirm you disabled SIP first and set the nvram no compat check. Then in options of the patcher deselect the APFS software patch and select not to have automatic patching before you start the patcher. This should bring you to a working Catalina. What is your actual configuration? Graphics card, Wi-Fi and ROM especially as there are a few issues with older hardware. Have a good look at the thread:

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.

 

[jackluke]

Does the script download the latest recovery or the beta recovery (the URL seems like it would be very specific)?
The script appears to need to be run from a Catalina system.
The script uses the first Recovery partition instead of the one belonging to the current system (if there's more than one)?
What's the purpose of backing up the PlatformSupport.plist file?
The script assumes the existing UUID is correct. Those separate diskutil apfs commands will fix the UUID if it is wrong? The diskutil man page in Catalina has much more info about the apfs commands than in Mojave. I think diskutil has more features in Catalina too.

And the MBP can boot into Recovery with Command-R (which is the problem I described with my Mac Mini 2018)?

Instead of downloading using the patcher, I download installers from the App Store (or Software Update or wherever), and back them up to a different drive so they don't waste disk space on my OS partition and I can use the same installer later on a USB stick for a different Mac or Hackintosh using the various USB installer creators that exist (patcher, createinstallmedia, etc.)

It downloads the stock Catalina GoldenMaster Recovery "Basesystem.dmg" (that it's almost identical to the current public release).

Yes, it needs to be runned from a Catalina system (as per this thread is about Catalina).

The script uses the APFS Recovery associated to the local current booted system (Catalina) and the best prelinkedkernel generated from that machine, on any standard apple machine you can't have more than one Recovery associated to CMD+R. If there is more than one it won't touch them since the HFS Recovery is totally different (Recovery HD not APFS), and the next possible APFS Recovery on multiple volumes has this unique label "Recovery 1" the next "Recovery 2" and so on.

Maybe PlatformSupport.plist is not needed, "-no_compat_check" already "whitelist" its content, however it should contain your Mac-ID, but not needed.

Those commands fixed UUID on APFS Mojave so they should work the same on Catalina too, however from Catalina they added more roles to APFS and more features to diskutil, so surely there are other ways for this, but the APFS Recovery points to the Preboot UUID in general, not to the System (or Data) Volume.

 

[hvds]

Neither the Activity Monitor nor the Network Utility reports accurate information on an iMac8,1.
The iMac boots into El Capitan, Mojave and Catalina. All screenshots were taken from the same iMac, suggesting that any variations are caused by the OS, not the hardware.
Activity Monitor shows the individual Processes, but no statistics. See screen shots from Catalina and from Mojave to compare.
Network Utility shows a WiFi Link speed of 5.74 Mbit/s under Catalina, compared with 130 Mbit/s under Mojave. The lower value is not correct. The ISP charges for 100 Mbit/s but usually provides between 85 Mbit/s and 115 Mbit/s. This corresponds to the actual download time of approx. 7 minutes for "Install macOS Catalina Beta", which is a 6 GB file.
The measurements were repeated over 2-3 days with several restarts and are reasonably consistent, but consistently incorrect.
Don't know if these are core Catalina issues, relate to the patched macOS version or are specific to the iMac8,1.

On MBP5,2 with 10.15.0 Release, still observe this:
the network graph in Activity Monitor shows no read activity, while in fact reads are going well on full speed (example of downloading the os with patcher 1.1.7).

Using an Ethernet wire for this.
Looks reasonable when using WIFI.

Not a significant thing, but weird.

Edit: both WIFI and Cable look fine on a supported MBP11,1 (cable connected via Thunderbolt adapter though).

 

[Yiorlis59]

Catalina 10.15 successfully installed on MBPro 5,5,apfs rom patch installed, runs very well although from usb.No major problems..bluesky is working ok, Temps stable, cpu idle 60 to 70,mem usage half.
Good luck for all the newbies!!!

 

[Glujaz]

Catalina 10.15 successfully installed on MBPro 5,5,apfs rom patch installed, runs very well although from usb.No major problems..bluesky is working ok, Temps stable, cpu idle 60 to 70,mem usage half.
Good luck for all the newbies!!!View attachment 869114View attachment 869113View attachment 869118

Yeah... have problems with brightness on my 5,2 MacBook (not pro)... happy to see that everything is working for you

 

[joevt]

The script uses the APFS Recovery associated to the local current booted system (Catalina) and the best prelinkedkernel generated from that machine, on any standard apple machine you can't have more than one Recovery associated to CMD+R. If there is more than one it won't touch them since the HFS Recovery is totally different (Recovery HD not APFS), and the next possible APFS Recovery on multiple volumes has this unique label "Recovery 1" the next "Recovery 2" and so on.

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.

 

[telepati]

@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

 

[Michael Mrak]

Is there a summary what exactly BlueSky is and if I can benefit from it on my MacMini 3,1? And of course I would be glad if there are some instructions steps by steps how to install it

best regards
Michael

 

[GSXB]

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.

To turn of APFS booter and auto patch, go menu bar options and deselect APFS booter and autopatch

 

[zfrogman]

Yeah to regain access back I needed to install "Legacy USB injector" that is within Dosdude's 1.1.7 Patcher and ignore the latest update from Patch Updater. Please can anyone else reconfirm this issue? I'm on Mac Pro 3,1 with GT730 non Mac-EFI card, 16GB RAM and on Catalina release 10.15.0.

Hello, looks like no one has encountered the problem so far in reading the forum that I am aware; I am more of a interested user than a skilled user/techie but perhaps something in my MBP 15" 2011 specific or linked to the defective dGPU bypass software solution may have something indirectly related?? Everything btw "works" very smoothly, seems even faster and more efficient than Mojave. I have noticed however that removing the AMDRadeonX3000.kext required in the dGPU bypass solution and moving it to an "Extensions-off" folder in /System/Library actually crashed the boot process into a boot loop or hang. Leaving the AMDRadeonX3000.kext in /Extensions as happens with the install using 1.1.7 "enables" the regular boot process in contradiction with the dGPU workaround. Perhaps Dosdude solved this problem or the new Catalina container structure has something to do with it? I have however maintained the loginhook essentially from my understanding that it reduced temperature of system overall. However if I do a reset of PRAM, i revert back to the funky screen (even in single user mode obviously because of defective dGPU)) and need to redo process of disabling dGPU using the force-iGPU-boot.sh or the long form version of the command. (i have placed the force-iGPU-Boot.sh in the root of Catalina (not the Catalina-data) just in case. I realize you have a different system altogether but it is interesting to note that the issue of the Legacy USB injector update (via 1.1.7 patch) is the same. Perhaps this need to PM Dosdude or create a separate thread? Let me know your thoughts (or any one else of course). Cheers

 

[cymorrow]

I didn't create an USB stick but chose the Direct Install method from within Mojave. I also couldn't reach the point where I could do the post install.

Same thing happened to me. You will first have to remove the drive that you attempted to Direct install from your MacPro. Hopefully you have another drive that you can boot from. Once you have booted w/o the said drive, then you can set the boot drive to something else.

What worked for me was to disable SIP from the Recovery boot (CMD-R) and to set NVRAM:
sudo nvram boot-args="-no_compat_check"

Then install from a USB installer OR if you are brave enough, do the direct install again.

 

[Pluda]

Instead of downloading using the patcher, I download installers from the App Store (or Software Update or wherever)

In my third atempt that was exactly what I did, software update downloaded the installer to applications folder and then I patched the installer with @dosdude1 1.7.7 patcher. Worked prety fine. (remember, turn firewall OFF)