If I have MP5,1 with 3rd party graphics Radeon RX 580, is there any way to disable SIP? I don't think the recovery mode work with this card anymore...
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
The update is 3GB download
[automerge]1574373263[/automerge]
boot into the Catalina Patcher then go into the terminal and type csrutil disable
If you installed patched Catalina on your MacPro 3,1 with a non-Metal graphics card installed (ie not your GTX680), the legacy video patches would have been applied. These will break Metal acceleration. Just remove all the graphic cards other than the GTX680 and do an re-installation over your current system volume. That will purge out the legacy video patches.
Sorry for asking the obvious I guess, but how do I exactly boot into the Catalina Patcher? By creating bootable USB?
Made a bootable USB, but while rebooting and holding option key it doesn't show me the volume options like in @dosdude1 tutorial, so perhaps this option is not supported on Radeon RX 580? Not sure how else can I boot into this patcher or disable SIP...
You MUST have a flashed or Apple original video card in order to see the boot screen and complete the Catalina install on a Mac Pro.
With two APFS containers on the same SSHDD each with a working OS, one Mojave dot 6 and the other Catalina dot one - both with the APFS patch booting, once booting into Mojave it renders the Catalina container unbootable which previously ran perfectly for five days. Very frustrating, resetting NVRAM yields only one EFI boot, Mojave. Disk Utility reports Catalina container and contents not bootable. Catalina was installed to this machine not from USB. Worthy of note? There is no APFS CP in the Mojave CPs where there is a APFS CP in the Catalina CPs. The Mojave .6 install was repatched with a 1.3.7 USB installer to no effect.
Why should booting into the Mojave container make the Catalina container unbootable?
Why should booting into the Mojave container make the Catalina container unbootable?
Last edited:
Yes it works .... BUT I was assuming that you, Timothy and other professionals, know that you still have to adjust the xxx.dist file (in Your Language) in Library / Update !!!"TimothyR734, Beitrag: 28004391, Mitglied: 1126371"]
Jetzt installieren 3GB Download Nein, es wurde gestartet und dann neu gestartet. Versuche es erneut
First of all the Mac-XXXXXC, the right one for your unsupported device has to be inserted (in the upper part with text-editor open and edit) then something further down in the xxx.dist file, with "not supportet device" the designation for yours Device to be removed. For me it was just MacBook Pro 5.2.
and now after the download in Library / Updates and the xxx.dist - file adapt accordingly and after restart already comes then the option: boot macOS install xxxxxxx Data. Then install and then again after restarting the dosdude1 patch (only for graphics is enough) and already the DP3 is installed.
Last edited:
yes is a old swupatch.sh from sierra or High Sierra. by chance and I thought give it a try and it worked
As I said, a coincidence that I had just found with me, in my backup archive.
Last edited:
Hi all! Just checking in to confirm that 10.15.2 DP3 (19C46a) is working seemingly normally on a non-Metal MacBook7,1 with the new GeForceTesla patch and a stock IOSurface. I'll report back if anything weird happens, but fingers crossed that the next couple betas will continue to be smooth sailing
For RAM upgrades, I go to macsales.com, click "My Upgrades", select my Mac model, then check the options. For the iMac8,1, the max option is 6GB.
The APFS patch goes to the EFI partition. There's only one EFI partition so only one of the OSs will boot. After the APFS patch is installed, move it to a new partition (20 MB is enough). Make it HFS+. Give it a nice name like "Catalina Boot". Give it a volume icon if you like. With HFS+, you need to use the bless command to bless the efi file. But you can also use the label parameter of the bless command to give the boot partition a better name than "EFI Boot".
I have a boot partition for each of my APFS partitions. Each one contains a BBEdit worksheet with the bless command for that partition. Remove the --setBoot parameter if you don't want to change the nvram boot setting (you just want to set the label and HFS boot file of the partition). The disk labels are created by the -label parameter of the bless command. For example, when I hold option at boot to boot from the Catalina Boot partition, I select the icon labeled "Catalina". The ShellX64.efi file is the bootx64.efi file from the EFI partition. You need to modify the startup.nsh file with the UUID of the partition containing the OS and the name of the folder on the Boot partition containing the apfs.efi file. The startup.nsh file appears to be UTF-16 LE with Windows CRLF line endings. Exclude the enable Alpine Ridge stuff - that's only for my computer.
Once you setup the separate boot partitions, you can remove the stuff from the EFI partition so that "EFI Boot" no longer appears in the Startup Manager (when you hold option key at boot).
Future installs of macOS on new AFPS partitions can be done without the APFS Patch option selected. Just create a new Boot Partition for the new install.
Code:
find -f /Volumes/*Boot \( -name '.VolumeIcon.icns' -or -name '*label*' -or -not -name '.*' \) -not -name '*.txt'
/Volumes/Catalina Boot
/Volumes/Catalina Boot/.VolumeIcon.icns
/Volumes/Catalina Boot/macOSCatalinaPatcher
/Volumes/Catalina Boot/macOSCatalinaPatcher/.disk_label
/Volumes/Catalina Boot/macOSCatalinaPatcher/.disk_label_2x
/Volumes/Catalina Boot/macOSCatalinaPatcher/apfs.efi
/Volumes/Catalina Boot/macOSCatalinaPatcher/Catalina_Boot.worksheet
/Volumes/Catalina Boot/macOSCatalinaPatcher/ShellX64.efi
/Volumes/Catalina Boot/macOSCatalinaPatcher/startup.nsh
/Volumes/Mojave4 Boot
/Volumes/Mojave4 Boot/.VolumeIcon.icns
/Volumes/Mojave4 Boot/macOSMojave4Patcher
/Volumes/Mojave4 Boot/macOSMojave4Patcher/.disk_label
/Volumes/Mojave4 Boot/macOSMojave4Patcher/.disk_label_2x
/Volumes/Mojave4 Boot/macOSMojave4Patcher/apfs.efi
/Volumes/Mojave4 Boot/macOSMojave4Patcher/Mojave4_Boot.worksheet
/Volumes/Mojave4 Boot/macOSMojave4Patcher/ShellX64.efi
/Volumes/Mojave4 Boot/macOSMojave4Patcher/startup.nsh
/Volumes/Mojave5 Boot
/Volumes/Mojave5 Boot/.VolumeIcon.icns
/Volumes/Mojave5 Boot/macOSMojave5Patcher
/Volumes/Mojave5 Boot/macOSMojave5Patcher/.disk_label
/Volumes/Mojave5 Boot/macOSMojave5Patcher/.disk_label_2x
/Volumes/Mojave5 Boot/macOSMojave5Patcher/apfs.efi
/Volumes/Mojave5 Boot/macOSMojave5Patcher/Mojave5_Boot.worksheet
/Volumes/Mojave5 Boot/macOSMojave5Patcher/ShellX64.efi
/Volumes/Mojave5 Boot/macOSMojave5Patcher/startup.nsh
/Volumes/Mojave6 Boot
/Volumes/Mojave6 Boot/.VolumeIcon.icns
/Volumes/Mojave6 Boot/macOSMojave6Patcher
/Volumes/Mojave6 Boot/macOSMojave6Patcher/.disk_label
/Volumes/Mojave6 Boot/macOSMojave6Patcher/.disk_label_2x
/Volumes/Mojave6 Boot/macOSMojave6Patcher/apfs.efi
/Volumes/Mojave6 Boot/macOSMojave6Patcher/Mojave6_Boot.worksheet
/Volumes/Mojave6 Boot/macOSMojave6Patcher/ShellX64.efi
/Volumes/Mojave6 Boot/macOSMojave6Patcher/startup.nsh
/usr/libexec/PlistBuddy -c 'Print :WorksheetContents' /Volumes/Catalina\ Boot/macOSCatalinaPatcher/Catalina_Boot.worksheet
sudo bless --folder /Volumes/Catalina\ Boot/macOSCatalinaPatcher --file /Volumes/Catalina\ Boot/macOSCatalinaPatcher/ShellX64.efi --label Catalina --setBoot
iconv -f UTF-16LE -t UTF-8 /Volumes/Catalina\ Boot/macOSCatalinaPatcher/startup.nsh | tr -d '\r'
echo -off
mode 320 84
set StartupDelay 1
set -v efishellmode 1.1.2
echo "Enabling Alpine Ridge..."
mm 000F000054C 0D -w 1 -PCIE -n
mm 0010000054C 0D -w 1 -PCIE -n
mm 000F0000548 -w 1 -PCIE -n
mm 00100000548 -w 1 -PCIE -n
echo "Searching for APFS driver..."
set macOSBootFile "System\Library\CoreServices\boot.efi"
set targetUUID "FD8B32D4-3574-4217-A742-797CEAAE6C85"
for %i in 0 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
if exist fs%i:\macOSCatalinaPatcher\apfs.efi then
load fs%i:\macOSCatalinaPatcher\apfs.efi
connect -r
map -u
endif
endfor
echo "Searching for macOS Boot File..."
for %m in 0 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
if exist "fs%m:\%targetUUID%\%macOSBootFile%" then
echo "Starting macOS..."
fs%m:\%targetUUID%\%macOSBootFile%
exit
endif
endfor
for %m in 0 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
if exist "fs%m:\%macOSBootFile%" then
echo "Starting macOS..."
fs%m:\%macOSBootFile%
exit
endif
endfor
echo "Boot file not found, exiting..."
exit
diskutil info "/Volumes/Catalina" | grep "Volume UUID"
Volume UUID: FD8B32D4-3574-4217-A742-797CEAAE6C85
It does if you buy from MacVid cards (but for an inflated price)!
I guess using the "Sierra's swupatch.sh" you should edit the XXX-XXXXX.languageID.dist file after you downloaded the OTA update in /Library/Updates/XXX-XXXXX/ and add your board-id and remove your machine model
From Catalina Terminal copy/paste this the output "Mac-ID" should be added the to OTA .dist file:
ioreg -l | grep -i board-idand copy/paste this you should remove from the OTA .dist file the ouput model string:
ioreg -l | awk '/product-name/ { split($0, line, "\""); printf("%s\n", line[4]); }'example OTA .dist file where to edit:
function InstallationCheck(prefix) {
var boardIds = ['Mac-9AE82516C7C6B903','Mac-031B6874CF7F642A','Mac-112818653D3AABFC','Mac-9394BDF4BF862EE7','Mac-AA95B1DDAB278B95','Mac-CAD6701F7CEA0921','Mac-50619A408DB004DA','Mac-7BA5B2D9E42DDD94','Mac-B809C3757DA9BB8D','Mac-AFD8A9D944EA4843','Mac-27ADBB7B4CEE8E61','Mac-F305150B0C7DEEEF','Mac-35C1E88140C3E6CF','Mac-827FAC58A8FDFA22','Mac-77EB7D7DAF985301','Mac-2E6FAB96566FE58C','Mac-827FB448E656EC26','Mac-66E35819EE2D0D05','Mac-031AEE4D24BFF0B1','Mac-00BE6ED71E35EB86','Mac-4B7AC7E43945597E','Mac-5A49A77366F81C72','Mac-63001698E7A34814','Mac-937CB26E2E02BB01','Mac-FFE5EF870D7BA81A','Mac-53FDB3D8DB8CA971','Mac-226CB3C6A851A671','Mac-C6F71043CEAA02A6','Mac-4B682C642B45593E','Mac-1E7E29AD0135F9BC','Mac-90BE64C3CB5A9AEB','Mac-7BA5B2DFE22DDD8C','Mac-66F35F19FE2A0D05','Mac-189A3D4F975D5FFC','Mac-B4831CEBD52A0C4C','Mac-FA842E06C61E91C5','Mac-FC02E91DDD3FA6A4','Mac-06F11FD93F0323C5','Mac-06F11F11946D27C5','Mac-6F01561E16C75D06','Mac-F60DEB81FF30ACF6','Mac-473D31EABEB93F9B','Mac-3CBD00234E554E41','Mac-BE0E8AC46FE800CC','Mac-9F18E312C5C2BF0B','Mac-81E3E92DD6088272','Mac-65CE76090165799A','Mac-CF21D135A7D34AA6','Mac-F65AE981FFA204ED','Mac-112B0A653D3AAB9C','Mac-DB15BD556843C820','Mac-27AD2F918AE68F61','Mac-937A206F2EE63C01','Mac-77F17D7DA9285301','Mac-E43C1C25D4880AD6','Mac-BE088AF8C5EB4FA2','Mac-551B86E5744E2388','Mac-A5C67F76ED83108C','Mac-747B1AEFF11738BE','Mac-EE2EBD4B90B839A8','Mac-42FD25EABCABB274','Mac-7DF2A3B5E5D671ED','Mac-2BD1B31983FE1663','Mac-7DF21CB3ED6977E5','Mac-A369DDC4E67F1C45','Mac-35C5E08120C7EEAF','Mac-C3EC7CD22292981F',];
var cpuFeatures = system.sysctl( 'machdep.cpu.features' );
cpuFeatures=cpuFeatures.split(" ");
for( var i = 0; i < cpuFeatures.length; i++ ){
if( cpuFeatures == "VMM" ){
return true;
}
}
var nonSupportedModels = ['MacBookPro4,1','MacPro2,1','Macmini5,2','Macmini5,1','MacBookPro5,1','MacBookPro1,1','MacBookPro5,3','MacBookPro5,2','iMac8,1','MacBookPro5,4','MacBookPro8,1','iMac5,1','iMac11,2','iMac7,1','MacBookAir4,1','MacBookPro3,1','Macmini5,3','MacBookPro1,2','Macmini4,1','iMac9,1','iMac6,1','iMac4,1','Macmini1,1','iMac4,2','MacBookPro2,2','MacBookPro2,1','iMac12,2','MacBook3,1','MacPro3,1','MacBook5,1','MacBook5,2','iMac11,1','iMac10,1','MacBookPro7,1','MacBook2,1','MacPro4,1','MacBookPro6,2','iMac12,1','MacBook1,1','MacBookPro5,5','MacPro5,1','MacBookPro6,1','Xserve2,1','MacBookAir3,1','MacBookAir3,2','MacBookAir1,1','Xserve3,1','MacBookAir2,1','MacBook7,1','Xserve1,1','Macmini2,1','iMac5,2','MacBookPro8,2','MacBookPro8,3','iMac11,3','MacBook6,1','Macmini3,1','MacBook4,1','MacBookAir4,2','MacPro1,1',];
var currentModel = system.sysctl('hw.model');
if (nonSupportedModels.indexOf(currentModel) >= 0) {
my.result.message = system.localizedString('ERROR_3491501876');
my.result.type = 'Fatal';
return false;
}
var boardId = system.ioregistry.fromPath('IOService:/')['board-id'];
if (boardIds.indexOf(boardId) == -1) {
my.result.message = system.localizedString('ERROR_3491501876');
my.result.type = 'Fatal';
return false;
}
if (system.compareVersions(system.version.ProductVersion, '10.15') < 0 || system.compareVersions(system.version.ProductVersion, '10.16') >= 0) {
my.result.message = system.localizedStringWithFormat('ERROR_7E7AEE96CA', '10.15');
my.result.type = 'Fatal';
return false;
}
return true;
Last edited:
Thanks dude
, My old installation works fine now at 1080p. I've done some further testing and found it will run @4k 30 on my TV, when using the HDMI 1.4 port. My though was that the DisplayPort might not be working under Catalina but when I use a DisplayPort to DVI cable on the 1080p monitor it works fine, so that can't be the issue.
Thanks for the corrective action info, very detailed and clear. I am curious why bootng into Mojave wiped out the Catalina EFI boot?
Good point, can't test this yet, but I am enough sure that will work, so maybe an advise is to disable any Automatic Catalina updates from the "Software Update" prefpane, in order to download only the OTA packages and allow an extra-time to edit the OTA XXX-XXXXX.languageID.dist file inside the /Library/Updates/XXX-XXXXX/ whitelisting the unsupported machine board-id and mac-model, so at the next reboot the OTA stage2 installer will continue automatically (or holding alt-option key picking manually the "macOS Install Data" temporary volume).
Note for those who want to attempt the Sierra's swupatch.sh for Catalina, the OTA is downloaded here /Library/Updates/XXX-XXXXX/
XXX-XXXXX folder is the Product number ID that identifies your OSX main language locale
XXX-XXXXX.languageID.dist is the file to edit to whitelist the board-id (adding) and the machine model (removing)
languageID generic is for example "en_US"
Opening the OTA .dist file add inside the board-id here:
Code:
function InstallationCheck(prefix) {
var boardIds = ['Mac-yourboardnumber',remove the machine model here:
Code:
var nonSupportedModels = ['MacExample7,1',My advise is to not chose to Download and Install, but Download only, after you edited your .dist file, you can re-open the "Software Update" and click "Update Now" button and OTA stage1 and stage2 installer should proceed.
Last edited:
As I mentioned earlier, "Labtick" small Keyboard light utility does everything with exception of Ambient sensor input, make sure you have it in the "Start Up" folder too, works well, set it and forget it. Tell me if you had issues with your 4,1 getting a little warmer than usual on Catalina? I did, back here with Mojave until further bugs get ironed out.
I am using an RX580 in a cMP 4.1>5.1 and it is possible to have a working Recovery partition. Mine is working right now. You can also disable SIP using the patcher USB. Select the USB in startup disk preferences and the machine should startup with the USB allowing you to access Terminal to set the csrutil disable command.
However, before you continue make sure you have updated your ROM to 144.0.0.0.0 and are running Mojave 14.6 successfully. If not, follow this thread:
https://forums.macrumors.com/thread...-bootrom-upgrade-instructions-thread.2142418/)
You will need an efi Mac graphics card to do this. Only when you have achieved this would I think of moving onto Catalina.
Once you have updated the ROM you can put the RX580 back and everything else can be done without the boot screen. At this stage (with Mojave) you will have a working Recovery partition OOB to disable SIP. Also set the NVRAM no compat check at the same time as this may help later and causes no issues.
Boot into Mojave, download dodsude1's latest patcher and use it to download Catalina. With your cMP 5.1 you have now have a few routes you can follow. The choice is yours! Using the patcher you will have to keep SIP disabled. The advantages of the patched route are that you get NightShift and if you have the original WiFi card then the patches give you WiFi. The patcher also removes the need to have the "no compat check" and will keep SIP disabled for you.
The other route that can leave SIP enabled is to install with no patches at all. Dosdude1's patcher has the option to do this which is great if you want a system with as little change as possible. However, you will have to have the NVRAM "no compat check" applied. My cMP5.1 is running like this at the moment. I do have an upgraded WiFi/BT card so it is running Catalina "OOB" if you like. To take this route set up the patcher options from the menu before you install - set APFS not to use the software patch (note: do this even if you are going to patch as the cMP5.1 has APFS natively) and the automatic patching off. After install the cMP5.1 will boot up into Catalina with no further actions needed. SIP can be enabled after this if you wish. I find "install to this machine" works well and only make the USB in case of emergencies.
Finally, you can fix the Recovery partition if you want it. In the past I never really used it as I had a boot screen (GTX680) and used the USB as the recovery. Now, with the RX580 I found the Recovery partition a little more useful. Here is a link do do this. Works well:
Catalina-Recovery-HD-Partition
If you do use this then you will need SIP disabled but you can enable once done.
Hi there
I have installed macOS 10.15.1 succesfully on 3.1 Mac Mini and 5.2 Macbook White. It works fine, just a little bit slow, but when I try to install it on my 8.1 Macbook Pro it aparently installs correctly excepts that when the installation is over, it keeps booting to USB drive, it never displays the setup screen. This has never happened to me on the other devices, just in the Macbook Pro 2011.
I've try to manually patch the system, but it's the same, keeps booting to USB. When I disconnect the drive, it shows the folder... i've tried 3 times, with APFS and with regular HFS+and the result is the same. Also i've tried Mojave and it installs and setup correctly, the problem it's just with Catalina.
Any idea? by the way, i'm using the same USB bootable drive on the 3 machines...
I have installed macOS 10.15.1 succesfully on 3.1 Mac Mini and 5.2 Macbook White. It works fine, just a little bit slow, but when I try to install it on my 8.1 Macbook Pro it aparently installs correctly excepts that when the installation is over, it keeps booting to USB drive, it never displays the setup screen. This has never happened to me on the other devices, just in the Macbook Pro 2011.
I've try to manually patch the system, but it's the same, keeps booting to USB. When I disconnect the drive, it shows the folder... i've tried 3 times, with APFS and with regular HFS+and the result is the same. Also i've tried Mojave and it installs and setup correctly, the problem it's just with Catalina.
Any idea? by the way, i'm using the same USB bootable drive on the 3 machines...
Hi Yamil did you find any solution for this? I have the exact same 2011 13" MacbookPro8,1 but I am now afraid to upgrade because it sounds like you are having problems.
Last edited:
Will this have the update to the Catalina version of Night Shift ? It appears the one I downloaded prevents my keyboard preference from opening.
Yes, I remember that issue with a "night shift" patch, it occurs because apple is constantly changing the offset in each minor Catalina update with their CoreBrightness , since the software update is still under testing, I uploaded a 10.15.1 pre-patched CoreBrightness and this should fix the side effect with keyboard prefpane.
open a Catalina Terminal and copy/paste this:
sudo mount -uw / ; killall Finderopen /System/Library/PrivateFrameworks/replace on-the-fly (do not merge) with this attached only valid for Catalina 10.15.1 build 19B88 (and maybe later builds).
Last edited:
Did you ensure you have the latest BootROM version installed, as described on the webpage in the "Important Info" section? This is extremely important to do before installing, as older BootROM versions cannot recognize or boot from APFS volumes.