You're right, both, to enforce them from a real-mac, you can boot from a Recovery environment (At least El Capitan when they introduced SIP), and from a Recovery Terminal type: csrutil disable
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.15 Catalina on Unsupported Macs
- Thread starter 0403979
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
You're right, both, to enforce them from a real-mac, you can boot from a Recovery environment (At least El Capitan when they introduced SIP), and from a Recovery Terminal type: csrutil disable
Ok thanks I wait for confirmation but but it's ugly that it can not be done in Catalina
Yes, when i installed catalina, i noticed that was created two partition for catalina, one for catalina with kexts and all that stuff and other Catalina-Data....
the catalina with the kexts and stuff is completely locked
Attachments
In Beta 1 that's not a problem to install in S/LE like any other OS's
Want to express my special thanks to @ASentientBot for all his amazing contributes to this 10.15 (and 10.14) community, and I add that he deserves another credit (and mention in the OP) for this great method to create a Catalina Installer almost identical to the stock apple createinstallmedia one: Catalina Installer for unsupported Mac
I knew how to clone a Catalina beta2 APFS from a supported Mac but this time I wanted to experiment an In-place Catalina beta2 upgrade over my Catalina beta1 unsupported Mac.
In my case a little modification to his method:
even if the Catalina Installer worked, I was unable to install it over my Catalina beta1 since I got an OSX Installer system message when selecting my target (not empty) APFS Catalina “You can’t install macOS over a more recent OSX” or similar, then here is how I fixed this:
Booting from another macOS HighSierra I replaced in my APFS Catalina beta1 Volume this file:
/System/Library/CoreServices/SystemVersion.plist
With SystemVersion.plist from an older HighSierra version, in this way I cheated the Catalina Installer making it believe that I was simply refreshing an HighSierra installation, and it worked!
Successfully in-place upgraded from unsupported Mac Catalina beta1 to Catalina beta2 keeping all my datas, apps and users settings.
I knew how to clone a Catalina beta2 APFS from a supported Mac but this time I wanted to experiment an In-place Catalina beta2 upgrade over my Catalina beta1 unsupported Mac.
In my case a little modification to his method:
even if the Catalina Installer worked, I was unable to install it over my Catalina beta1 since I got an OSX Installer system message when selecting my target (not empty) APFS Catalina “You can’t install macOS over a more recent OSX” or similar, then here is how I fixed this:
Booting from another macOS HighSierra I replaced in my APFS Catalina beta1 Volume this file:
/System/Library/CoreServices/SystemVersion.plist
With SystemVersion.plist from an older HighSierra version, in this way I cheated the Catalina Installer making it believe that I was simply refreshing an HighSierra installation, and it worked!
Successfully in-place upgraded from unsupported Mac Catalina beta1 to Catalina beta2 keeping all my datas, apps and users settings.
Attachments
Last edited:
Acceleration achieved on DP2!
View attachment 843591 View attachment 843597
Yay!
Unfortunately, I feel that this effort will soon come to an end if we can't find a better solution than replacing the entire SkyLight and CoreDisplay. But for now, I made stuff happy again by stubbing out another several functions. (It only took so long because dumbass me somehow removed the symlinks inside the OpenGL framework in the process of copying it, and apparently those are necessary.)
It's late so I don't have time to thoroughly test, but it seems much the same as before. Key differences include an actually read-only filesystem, some nice "Loading..." text in Finder's columns view, and a lot of changes to what seems to be mostly accessibility-related display code. (Related: none of the display-related accessibility features in System Preferences really work at the moment due to my stub functions not actually doing anything.)
Anyways, a new CoreDisplay.framework (the SkyLight wrapper is unchanged) is attached for those who want to be on the bleeding edge. Good luck and goodnight.
good job! i’m mega impressed by it!
Looks beautiful! Again, you're the man!Acceleration achieved on DP2!
View attachment 843591 View attachment 843597
Yay!
Unfortunately, I feel that this effort will soon come to an end if we can't find a better solution than replacing the entire SkyLight and CoreDisplay. But for now, I made stuff happy again by stubbing out another several functions. (It only took so long because dumbass me somehow removed the symlinks inside the OpenGL framework in the process of copying it, and apparently those are necessary.)
It's late so I don't have time to thoroughly test, but it seems much the same as before. Key differences include an actually read-only filesystem, some nice "Loading..." text in Finder's columns view, and a lot of changes to what seems to be mostly accessibility-related display code. (Related: none of the display-related accessibility features in System Preferences really work at the moment due to my stub functions not actually doing anything.)
Anyways, a new CoreDisplay.framework (the SkyLight wrapper is unchanged) is attached for those who want to be on the bleeding edge. Good luck and goodnight.
Got Catalina Beta 2 installed onto my MacBook Pro 8,2.
Have no WiFi, No Audio and no Graphics Acceleration.
Is there an easy way to get WiFi & Audio back working again? don't care so much for graphic acceleration as yet but Internet would be nice
Have no WiFi, No Audio and no Graphics Acceleration.
Is there an easy way to get WiFi & Audio back working again? don't care so much for graphic acceleration as yet but Internet would be nice
Last edited:
If I make a bootable USB installer with dosdues1's patcher could I run the sudo nvram boot-args="-no_compat_check" command from terminal when it boots up the first time off the usb? I'v no EFI on my Gfx card so I have to pick boot devices from Startup Disk.
RX590 now being properly recognised! Tested CS:GO and Fortnite, seems to run generally smoother with fewer lags/framedrops and less hard/stuttering as on Mojave 10.14.5..I wonder if they bring the GPU drivers to Mojave 10.14.6 and or 10.14.7 and up so that MP5,1 users could get at least some improvements and proper identification
Attachments
Does macOS automatically rebuild the cache and prelinked kernel if it detects changes in /System/Library/Extensions?
I have always been under the impression that you had to patch Mojave (and now Catalina) before the first complete reboot after installation in order to get those kext changes in before the first boot rebuilt the caches and prelinked kernel.
No, you're right, since is no more possible (from Catalina beta1) to execute "kextcache" from single user mode due to a security framework.
I'd actually like an answer to this too, it seems really hit or miss. Sometimes it'll auto-rebuild and other times it'll just proceed through the boot process without "noticing" that I changed any kexts. I've been rebuilding my Catalina prelinkedkernel from Mojave in order to reach the desktop, after which I can rebuild it again from the Terminal.
man kextd suggests some flags like -no-caches that might be useful for first boot (you'd have to edit the launchd plist to add the argument I guess?) but I haven't gotten around to trying them.
It would be great if dosdude1 could just add an app to the current USB patched Catalina that would allow you to select the installed volume and do a forced cache rebuild on it. I would think he could take his post-install patch app code from Mojave, disable the machine and patch selector and just leave in volume selection and forced cache rebuild options.
As for the cache rebuild, the approach that I have taken for ages under USB patched Mojave installers, is to prelaunch the post install patch app far enough into the Mojave installation that the volume selected is considered valid. Then when the installer reaches its final 10 second countdown to reboot after completion, I apply the post-installation patches and reboot.
The tricky bit with Catalina is that it has replaced the normal installer window with a splash screen and iOS like progress bar. This makes it far less obvious as to which reboot will be rebuilding the kernel caches.
Just discovered that if you run sudo mount -uw / in DP2, you can delete/modify files in the protected partition. (Might have to killall Finder afterwards for it to detect the change.)
Right, I've noticed too that from this beta2 the APFS System Volume is more locked especially in the system folders we need.
Have you noticed that IOHIDFamily.kext patch is no more required ?
I mean the beta2 one seems to work without boot delay.
Yes, just installed it a while ago
[doublepost=1560866994][/doublepost]Have you achieved graphics acceleration? How did you do it exactly? Which commands did you used?
I'm downloading the patch and I'm working on a usb install but the time it installs it redimare it my in set message
@ASentientBot I guess you noticed also that this time for Macbook7,1 Wifi is required also the IO80211FamilyV2.kext, while on beta1 I replaced only IO80211Family.kext and it worked, the weird thing is that using the same external SSD Catalina (beta1 in-place upgraded to) beta2 replacing only that one worked on the other macbookpro6,2 that has a very similar Broadcom Airport Wifi card.
I'm wondering if Apple is keeping a tab open on this thread and "patching your patches" to make Catalina unable to work on unsupported Macs.
While all is good and great, sometime I can't help thinking if this whole thing should go underground with patchers available only through VPNs or torrents or whatnot.
@jackluke -- You're right that the IOHIDFamily patch is no longer necessary to reach the desktop, but now I'm seeing an AppleUserHIDDrivers crash log from each boot. Doesn't seem to matter, but I might still keep the patch for now.
I still have wifi with only replacing IO80211Family.
I still have wifi with only replacing IO80211Family.