macOS 10.15 Catalina on Unsupported Macs

[nekton1]

Thanks Jack.

No problems with Catalina Patcher 1.1.2 creating a usable usb patcher from 15.0.30 under Mojave. Installs and runs fine on a MacPro 3,1 with GTX 680.

 

[alphascorp]

Successful installation (not a clean install but a DP8 update) to DP9 (19A573a)



Little Snitch 4.4.2 finally works again !!!

 

[nekton1]

Made a clean install om MP 3.1 using new patcher and getting this over and over.

How to remove?

Thanks Jack.

 

[dosdude1]

Made a clean install om MP 3.1 using new patcher and getting this over and over.

How to remove?

View attachment 862769

WTF? Apple requiring sigs on binaries now too? Try running the following in Terminal:

sudo mount -uw /
sudo codesign -f -s - /usr/local/sbin/patchupdaterd

Also, is SIP enabled? (It NEVER should be on an unsupported system)

 

[nekton1]

No AFAIK, SIP is not enabled. I will check again.

Here is the result of ther commands.

[automerge]1569289895[/automerge]
Just checked and it is enabled. I though the patcher automatically disabled?

 

[nekton1]

Just booting into USB installer to disable SIP

 

[dosdude1]

No AFAIK, SIP is not enabled. I will check again.

Here is the result of ther commands.

View attachment 862783
[automerge]1569289895[/automerge]
Just checked and it is enabled. I though the patcher automatically disabled?

Something is screwed up... Try re-applying patches and see if that helps.

 

[Bigpearl]

Is there anyway I can convert my internal Hdd to APFS without having to reformat and lose everything

 

[nekton1]

Booted to USB installer again and disabled SIP manually in Terminal and now seems OK. patchupdaterd message gone. Very odd. I have done nothing to re-enable SIP between beta 8 and beta 9 today.
Thanks for help.

 

[Bigpearl]

Is there anyway I can convert my internal Hdd to APFS without having to reformat and lose everything

Or is it a way I can bypass the APFS check when trying to install the update

 

[bigpoppa]

Getting this error with latest patcher: "asr: Couldn't get volume group information for device /dev/disk9s1"


Mounting BaseSystem.dmg...

/dev/disk8 GUID_partition_scheme
/dev/disk8s1 Apple_HFS /private/tmp/basesystem


Patching BaseSystem.dmg...

"disk8" ejected.
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $19CF5867: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $1A6E5D70: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $F9779FDF: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
(CRC32 $5683A2E2: disk image (Apple_HFS : 4))
Reading (Apple_Free : 5)…
(CRC32 $00000000: (Apple_Free : 5))
Reading GPT Partition Data (Backup GPT Table : 6)…
(CRC32 $F9779FDF: GPT Partition Data (Backup GPT Table : 6))
Reading GPT Header (Backup GPT Header : 7)…
(CRC32 $2CC3C4A0: GPT Header (Backup GPT Header : 7))
Adding resources…
Elapsed Time: 21.429s
File size: 692602865 bytes, Checksum: CRC32 $33ED8218
Sectors processed: 4187760, 3552436 compressed
Speed: 80.9Mbytes/sec
Savings: 67.7%
created: /private/tmp/BaseSystem.dmg


Restoring BaseSystem.dmg...

Validating target...done
Validating source...done
Retrieving scan information...done
Validating sizes...done
Restoring ....10....20....30....40....50....60....70....80....90....100
Restored target device is /dev/disk9s1.
Remounting target volume...done
asr: Couldn't get volume group information for device /dev/disk9s1

 

[TimothyR734]

Getting this error with latest patcher: "asr: Couldn't get volume group information for device /dev/disk9s1"

Are you using the new version of the patcher 1.1.3

 

[bigpoppa]

Yes!

 

[TimothyR734]

Yes!

go into your applications folder and right click on the macOS Catalina Patcher get info make sure it is version 1.1.3 as I thought Downloaded the current version but it downloaded version 1.1.2 but I did successfully made a patcher with Dev Beta 9 with the older version so I did clear my browser history and downloaded the current version 1.1.3 the other way to install is use the install to this machine if you have a backup working patcher like 1.1.1 or 1.1.2 then do the post install patchers with an older cat patcher I tried that method while Dosdude1 was working updating the patcher for dev beta 9

 

[dosdude1]

Getting this error with latest patcher: "asr: Couldn't get volume group information for device /dev/disk9s1"


Mounting BaseSystem.dmg...

/dev/disk8 GUID_partition_scheme
/dev/disk8s1 Apple_HFS /private/tmp/basesystem


Patching BaseSystem.dmg...

"disk8" ejected.
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $19CF5867: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $1A6E5D70: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $F9779FDF: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
(CRC32 $5683A2E2: disk image (Apple_HFS : 4))
Reading (Apple_Free : 5)…
(CRC32 $00000000: (Apple_Free : 5))
Reading GPT Partition Data (Backup GPT Table : 6)…
(CRC32 $F9779FDF: GPT Partition Data (Backup GPT Table : 6))
Reading GPT Header (Backup GPT Header : 7)…
(CRC32 $2CC3C4A0: GPT Header (Backup GPT Header : 7))
Adding resources…
Elapsed Time: 21.429s
File size: 692602865 bytes, Checksum: CRC32 $33ED8218
Sectors processed: 4187760, 3552436 compressed
Speed: 80.9Mbytes/sec
Savings: 67.7%
created: /private/tmp/BaseSystem.dmg


Restoring BaseSystem.dmg...

Validating target...done
Validating source...done
Retrieving scan information...done
Validating sizes...done
Restoring ....10....20....30....40....50....60....70....80....90....100
Restored target device is /dev/disk9s1.
Remounting target volume...done
asr: Couldn't get volume group information for device /dev/disk9s1

This isn't a patcher issue, this is an issue with DP8 of Catalina. Create your installer drive using any other version of macOS, and it'll work fine. Or, you can patch Catalina Patcher to bypass that check, using the instructions I posted earlier.

 

[Jehm83]

Decompress the zip file. you will have a release-004437-220819 folder with the bluesky files inside. Open terminal, cd to the release-004437-220819 folder, run in terminal: "sudo sh ./BlueSky.sh"

Hello everyone..
I managed to install MacOS Catalina on my Macbook Pro 5.3 (2009) with MacOS Catalina Patcher from Dosdude (Thanks a lot for your excellent work 🙏😄..) I am currently trying to install the BlueSky 1.4 patches to update the problem of darkish interface menu bar & windows..so I looked in this thread the simplest and best way to do it, the message of LuisN seemed correct to try..but the terminal seems to have a problem with the command: "sudo sh ./BlueSky.sh" to link the file and to activate the mod?.. I tested with only the source code file & with the full resource file it can not find the path to the file BlueSky.sh..I certainly miss something in the process, so thank you by advance for your help ..


In Catalina, they apparently changed the shell abbreviation to zsh..it may be one of the possible causes of the problem? ..

 

[480951]

Just to clarify (and I apologize if this has been asked several times already) but with Catalina can I update normally through software update and it’ll automatically patch it for me, or is it similar to the Mojave one and I have to make another USB with the installer and new update to make it upgrade(?)

 

[Jehm83]

Tested this method of BlueSky Patch installation as well ..but didn't work either, Terminal still doesn't manage to link to the BlueSky.sh file..I wonder if it would not be a problem of Catalina Beta version compatibility (Version 19A558d)?..by advance, thanks for the help..

 

[alphascorp]

Hello everyone..
I managed to install MacOS Catalina on my Macbook Pro 5.3 (2009) with MacOS Catalina Patcher from Dosdude (Thanks a lot for your excellent work 🙏😄..) I am currently trying to install the BlueSky 1.4 patches to update the problem of darkish interface menu bar & windows..so I looked in this thread the simplest and best way to do it, the message of LuisN seemed correct to try..but the terminal seems to have a problem with the command: "sudo sh ./BlueSky.sh" to link the file and to activate the mod?.. I tested with only the source code file & with the full resource file it can not find the path to the file BlueSky.sh..I certainly miss something in the process, so thank you by advance for your help ..


In Catalina, they apparently changed the shell abbreviation to zsh..it may be one of the possible causes of the problem? ..

Hello @Jehm83,
You're right, you have a message at the launch of the Terminal:

The default interactive shell is now zsh
To update your account to use zsh, please run 'chsh -s /bin/zsh'

Try to execute the requested code and restart the Terminal before executing your other commands

For me this line of code did not work I had to go in the preferences of the Terminal, in the General tab then in "Shells open with" select "Command (complete path)" and write below "/bin/zsh" instead of "/bin/bash"
Close preferences and restart Terminal

All future orders should work properly with Terminal ...

Otherwise to apply "Blusky" you can also do it manually:
Manual Install is as simple as:



• locate SkyLight in System/Library/PrivateFrameworks/SkyLight.framework/Versions/Current

• back it up

• replace it with SkyLight from the unzipped
• Execute the following 2 commands in the Terminal:
• sudo chmod -R 755 /System/Library/PrivateFrameworks/SkyLight.framework
• sudo chown -R 0:0 /System/Library/PrivateFrameworks/SkyLight.framework


• locate HIToolbox in System/Library/Frameworks/Carbon.framework/Frameworks/HIToolbox/Versions/Current

• back it up
• replace with HIToolbox from the unzipped
• Execute the following 2 commands in the Terminal:
• sudo chmod -R 755 /System/Library/Frameworks/Carbon.framework
• sudo chown -R 0:0 /System/Library/Frameworks/Carbon.framework

• reboot

If we replace only SkyLight we get all the transparency of the menus only in dark mode and the Finder transparency in Light/Dark Mode!
But in light mode we stay with only the grisly gray menubar.

If you can not "paste" your "SkyLight" and "HIToolbox" files
Execute the following 2 commands in the Terminal:
'sudo mount -uw /' then 'Killall Finder'

 

[0134168]

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.

In my Mac Pro 5.1 , continuity has always worked. And unlock witn the Apple Watch. No commands needed.

 

[roysterdoyster]

Constant error while creating bootable installer USB drive 32GB from latest patcher 1.1.3 from @dosdude1 's website and DP9. :

Mounting BaseSystem.dmg...

/dev/disk4 GUID_partition_scheme
/dev/disk4s1 Apple_HFS /private/tmp/basesystem


Patching BaseSystem.dmg...

"disk4" ejected.
Image-Funktion vorbereiten …
Protective Master Boot Record (MBR : 0) lesen …
(CRC32 $19CF5867: Protective Master Boot Record (MBR : 0))
GPT Header (Primary GPT Header : 1) lesen …
(CRC32 $1A6E5D70: GPT Header (Primary GPT Header : 1))
GPT Partition Data (Primary GPT Table : 2) lesen …
(CRC32 $F9779FDF: GPT Partition Data (Primary GPT Table : 2))
(Apple_Free : 3) lesen …
(CRC32 $00000000: (Apple_Free : 3))
disk image (Apple_HFS : 4) lesen …
(CRC32 $000C58AA: disk image (Apple_HFS : 4))
(Apple_Free : 5) lesen …
(CRC32 $00000000: (Apple_Free : 5))
GPT Partition Data (Backup GPT Table : 6) lesen …
(CRC32 $F9779FDF: GPT Partition Data (Backup GPT Table : 6))
GPT Header (Backup GPT Header : 7) lesen …
(CRC32 $2CC3C4A0: GPT Header (Backup GPT Header : 7))
Ressourcen hinzufügen …
Dauer: 36.668s
Dateigröße: 692587089 Byte, Prüfsumme: CRC32 $EE8FD444
Bearbeitete Sektoren: 4187760, 3552436 komprimiert
Geschwindigkeit: 47.3M Byte/s
Ersparnis: 67.7 %
created: /private/tmp/BaseSystem.dmg


Restoring BaseSystem.dmg...

Validating target...done
Validating source...done
Retrieving scan information...done
Validating sizes...done
Restoring ....10....20....30....40....50....60....70....80....90....100
Restored target device is /dev/disk2s3.
Remounting target volume...done
asr: Couldn't get volume group information for device /dev/disk2s3



and log from macOS patcher:
Mounting BaseSystem.dmg...

/dev/disk4 GUID_partition_scheme
/dev/disk4s1 Apple_HFS /private/tmp/basesystem


Patching BaseSystem.dmg...

"disk4" ejected.
Image-Funktion vorbereiten …
Protective Master Boot Record (MBR : 0) lesen …
(CRC32 $F83E1A9E: Protective Master Boot Record (MBR : 0))
GPT Header (Primary GPT Header : 1) lesen …
(CRC32 $C36086BE: GPT Header (Primary GPT Header : 1))
GPT Partition Data (Primary GPT Table : 2) lesen …
(CRC32 $51D0E1A7: GPT Partition Data (Primary GPT Table : 2))
(Apple_Free : 3) lesen …
(CRC32 $00000000: (Apple_Free : 3))
disk image (Apple_HFS : 4) lesen …
(CRC32 $543277EB: disk image (Apple_HFS : 4))
(Apple_Free : 5) lesen …
(CRC32 $00000000: (Apple_Free : 5))
GPT Partition Data (Backup GPT Table : 6) lesen …
(CRC32 $51D0E1A7: GPT Partition Data (Backup GPT Table : 6))
GPT Header (Backup GPT Header : 7) lesen …
(CRC32 $21FF0EB7: GPT Header (Backup GPT Header : 7))
Ressourcen hinzufügen …
Dauer: 57.588s
Dateigröße: 673811396 Byte, Prüfsumme: CRC32 $A50A9DB0
Bearbeitete Sektoren: 4192480, 3472524 komprimiert
Geschwindigkeit: 29.4M Byte/s
Ersparnis: 68.6 %
created: /private/tmp/BaseSystem.dmg


Restoring BaseSystem.dmg...

Validating target...done
Validating source...done
Could not unmount volume "/Volumes/Ohne Titel" (Ressource ist belegt)

erased USB, tried to recreate bootable installer with patcher 1.1.2 and DP8, same error.

What can I do?
Your assistance will be highly appreciated!

 

[Vyzantion]

Constant error while creating bootable installer USB drive 32GB from latest patcher 1.1.3 from @dosdude1 's website and DP9. :

Mounting BaseSystem.dmg...

/dev/disk4 GUID_partition_scheme
/dev/disk4s1 Apple_HFS /private/tmp/basesystem


Patching BaseSystem.dmg...

"disk4" ejected.
Image-Funktion vorbereiten …
Protective Master Boot Record (MBR : 0) lesen …
(CRC32 $19CF5867: Protective Master Boot Record (MBR : 0))
GPT Header (Primary GPT Header : 1) lesen …
(CRC32 $1A6E5D70: GPT Header (Primary GPT Header : 1))
GPT Partition Data (Primary GPT Table : 2) lesen …
(CRC32 $F9779FDF: GPT Partition Data (Primary GPT Table : 2))
(Apple_Free : 3) lesen …
(CRC32 $00000000: (Apple_Free : 3))
disk image (Apple_HFS : 4) lesen …
(CRC32 $000C58AA: disk image (Apple_HFS : 4))
(Apple_Free : 5) lesen …
(CRC32 $00000000: (Apple_Free : 5))
GPT Partition Data (Backup GPT Table : 6) lesen …
(CRC32 $F9779FDF: GPT Partition Data (Backup GPT Table : 6))
GPT Header (Backup GPT Header : 7) lesen …
(CRC32 $2CC3C4A0: GPT Header (Backup GPT Header : 7))
Ressourcen hinzufügen …
Dauer: 36.668s
Dateigröße: 692587089 Byte, Prüfsumme: CRC32 $EE8FD444
Bearbeitete Sektoren: 4187760, 3552436 komprimiert
Geschwindigkeit: 47.3M Byte/s
Ersparnis: 67.7 %
created: /private/tmp/BaseSystem.dmg


Restoring BaseSystem.dmg...

Validating target...done
Validating source...done
Retrieving scan information...done
Validating sizes...done
Restoring ....10....20....30....40....50....60....70....80....90....100
Restored target device is /dev/disk2s3.
Remounting target volume...done
asr: Couldn't get volume group information for device /dev/disk2s3



and log from macOS patcher:
Mounting BaseSystem.dmg...

/dev/disk4 GUID_partition_scheme
/dev/disk4s1 Apple_HFS /private/tmp/basesystem


Patching BaseSystem.dmg...

"disk4" ejected.
Image-Funktion vorbereiten …
Protective Master Boot Record (MBR : 0) lesen …
(CRC32 $F83E1A9E: Protective Master Boot Record (MBR : 0))
GPT Header (Primary GPT Header : 1) lesen …
(CRC32 $C36086BE: GPT Header (Primary GPT Header : 1))
GPT Partition Data (Primary GPT Table : 2) lesen …
(CRC32 $51D0E1A7: GPT Partition Data (Primary GPT Table : 2))
(Apple_Free : 3) lesen …
(CRC32 $00000000: (Apple_Free : 3))
disk image (Apple_HFS : 4) lesen …
(CRC32 $543277EB: disk image (Apple_HFS : 4))
(Apple_Free : 5) lesen …
(CRC32 $00000000: (Apple_Free : 5))
GPT Partition Data (Backup GPT Table : 6) lesen …
(CRC32 $51D0E1A7: GPT Partition Data (Backup GPT Table : 6))
GPT Header (Backup GPT Header : 7) lesen …
(CRC32 $21FF0EB7: GPT Header (Backup GPT Header : 7))
Ressourcen hinzufügen …
Dauer: 57.588s
Dateigröße: 673811396 Byte, Prüfsumme: CRC32 $A50A9DB0
Bearbeitete Sektoren: 4192480, 3472524 komprimiert
Geschwindigkeit: 29.4M Byte/s
Ersparnis: 68.6 %
created: /private/tmp/BaseSystem.dmg


Restoring BaseSystem.dmg...

Validating target...done
Validating source...done
Could not unmount volume "/Volumes/Ohne Titel" (Ressource ist belegt)

erased USB, tried to recreate bootable installer with patcher 1.1.2 and DP8, same error.

What can I do?
Your assistance will be highly appreciated!

I have the same issue. Perhaps the patch for the app did not worked. Check what dosdude1 said to me in the previous patches.

 

[Fangio]

Installed DP9 over DP8 on my cMP 4,1/5,1 successfully using Patcher 1.1.3.

After some attempts I've created the USB installer in Mojave before I read that there's a patch for using it in DP8. Did an in-place 'Install to this machine' then instead of booting from it and reached desktop. Patch updater notified me the NightShift Patch was overwritten, reapplied it and so far no problems, everything is working.

Pleased to see the FCP bug is gone.

 

[Vyzantion]

I have the same issue. Perhaps the patch for the app did not worked. Check what dosdude1 said to me in the previous patches.

The patch in terminal did not worked for me.

 

[roysterdoyster]

The patch in terminal did not worked for me.

followed @dosdude1 's instructions, terminal patch didn't work for me either.