Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
This is what happened after an hour :(
 

Attachments

  • Screen Shot 2019-06-16 at 3.07.37 PM.png
    Screen Shot 2019-06-16 at 3.07.37 PM.png
    2.9 MB · Views: 1,980
After many hours of research, patching, and fighting with Apple's codesinging enforcement, I have FINALLY managed to create a 100% WORKING installer patch for macOS Catalina installers! This will allow you to install Catalina on your system, just like you would on a supported Mac! Download and info can be found here. I will be making another post later today explaining exactly what I did to get this working. Remember, this is the first iteration, so I expect there to be bugs that I'll need to work out. Enjoy!
Ch-ching! I know he doesn't do this for the money, but be sure to send dosdude1 a big fat tip! Donation links are on his webpage. And dosdude1 be sure to have a beer on me.
 
dosdude1
You might save some duplicated effort by waiting a day or so for the full patcher release, b/c the second Catalina release could be imminent based on past experience.

More likely to just be a software update to the first developer seed. The first public beta of Mojave wasn't until June 26th. Actually, if I recall correctly, the WWDC keynote said that the first public beta of Catalina was in July. My bet would be on July 2nd.
 
Last edited:
  • Like
Reactions: TimothyR734
It depends on the speed of your USB drive. Slow drives will take over 30 minutes to complete. (And yes, I will be implementing an actual progress indicator when I release the full version of Catalina Patcher).
Dosdude1's installs run pretty quickly even over USB 2.0. I think for me, Mojave always installing around 14 minutes. His stuff tends to install faster than Apple's own methods on a support Mac.
[doublepost=1560723999][/doublepost]
Are you still working on CloneToolX? You seem to be an APFS God right now ;) so maybe you can help me here: the Catalina image I created a while ago on my pro 3,1 was from a dd'ed image to its 70Gb blank target APFS partition. My original image was from a 63.5GB stick. I ended up with a 63.5 GB partition on the pro 3,1. but I can't manage to re-size it in Disk Utility at all. There is about 50GB of unused space that can only be partitioned into its own volume. Ideally I would like to expand the Catalina partition but I'm stuck with what the original image size was...

Ok. I kinda reached the opposite of your dilemma. My hdiutil disks are the actual size of the data but the partition thinks it is the actual size. So it's a bitch taking one of mine and going back down to its partition size.

So where is what I am testing:

Converting my cloned image disk to read/write (UDRW).
then see if I can apply resize to the partition only on the image.

You could do the opposite. especially if what I am proposing works

you would convert your dd image to read / write
and then resize the image to around your target partition minus a gig or two just to be safe.

I'd still do a restore though using asr and the resize using hdiutil. (you may be able to also skip the resize step and just asr directly to the larger volume).

Now I am running into some caveats trying to replicate your scenerio. UDRW - read write image is making the full disk an actual size image . I tried resizing a sparsebundle but it errors out, there is another read /write image format that I 've tried yet and there's sparse along with several other disk image formats. I may end up just resizing the large image to a small one to get my 'dd' test to run. Now this may be easier just reinstalling a small image with dosdude's work and get there quicker. But I'd like to replicate your issue as asr should workaround going to a larger disk.

Gonna checkout dosdude1's work and get that rolling.

Thx.
[doublepost=1560724325][/doublepost]
In the future with CloneToolX (hdiutil and asr) you will have the best of both worlds. small disk images on large virtual disks that they are cloned from and they restore to same size or larger. Takes out most of the issues dd has.
[doublepost=1560724548][/doublepost]
After many hours of research, patching, and fighting with Apple's codesinging enforcement, I have FINALLY managed to create a 100% WORKING installer patch for macOS Catalina installers! This will allow you to install Catalina on your system, just like you would on a supported Mac! Download and info can be found here. I will be making another post later today explaining exactly what I did to get this working. Remember, this is the first iteration, so I expect there to be bugs that I'll need to work out. Enjoy!
I'll test my Mac Pro 3,1 patch shell script against your install and if I feel it does the job for at MP3,1 users, I'll post the most recent version of it.
 
Last edited:
Dosdude1's early patcher worked for me.

used Mojave and Beta 1 to make a patcher usb Stick. Used a 32 GB Stick.

Booted the stick on a 4.1/5.1 with Firmware 144

Formatted a Sata SSD APFS one Volume

Got Catalina installed and booting. No patches needed. Even the GT120 I had in for Bootscreen is working, unaccelerated of course but usable. Writing this in Catalina on 4.1/5.1 with GT120
 
Dosdude1's early patcher worked for me.

used Mojave and Beta 1 to make a patcher usb Stick. Used a 32 GB Stick.

Booted the stick on a 4.1/5.1 with Firmware 144

Formatted a Sata SSD APFS one Volume

Got Catalina installed and booting. No patches needed. Even the GT120 I had in for Bootscreen is working, unaccelerated of course but usable. Writing this in Catalina on 4.1/5.1 with GT120

Hey Macschrauber I can't get it work using the same config as you did. Did you formatted the stick as MBR-MacOS journaled? I can't even create the installer...

Thanks!
 
  • Like
Reactions: TimothyR734
Dosdude1's installs run pretty quickly even over USB 2.0. I think for me, Mojave always installing around 14 minutes. His stuff tends to install faster than Apple's own methods on a support Mac.
[doublepost=1560723999][/doublepost]

Ok. I kinda reached the opposite of your dilemma. My hdiutil disks are the actual size of the data but the partition thinks it is the actual size. So it's a bitch taking one of mine and going back down to its partition size.

So where is what I am testing:

Converting my cloned image disk to read/write (UDRW).
then see if I can apply resize to the partition only on the image.

You could do the opposite. especially if what I am proposing works

you would convert your dd image to read / write
and then resize the image to around your target partition minus a gig or two just to be safe.

I'd still do a restore though using asr and the resize using hdiutil. (you may be able to also skip the resize step and just asr directly to the larger volume).

Now I am running into some caveats trying to replicate your scenerio. UDRW - read write image is making the full disk an actual size image . I tried resizing a sparsebundle but it errors out, there is another read /write image format that I 've tried yet and there's sparse along with several other disk image formats. I may end up just resizing the large image to a small one to get my 'dd' test to run. Now this may be easier just reinstalling a small image with dosdude's work and get there quicker. But I'd like to replicate your issue as asr should workaround going to a larger disk.

Gonna checkout dosdude1's work and get that rolling.

Thx.
[doublepost=1560724325][/doublepost]

In the future with CloneToolX (hdiutil and asr) you will have the best of both worlds. small disk images on large virtual disks that they are cloned from and they restore to same size or larger. Takes out most of the issues dd has.
[doublepost=1560724548][/doublepost]
I'll test my Mac Pro 3,1 patch shell script against your install and if I feel it does the job for at MP3,1 users, I'll post the most recent version of it.
Excellent. Great work.
 
  • Like
Reactions: TimothyR734
Hey Macschrauber I can't get it work using the same config as you did. Did you formatted the stick as MBR-MacOS journaled? I can't even create the installer...

Thanks!

Yep, it's Guid for Mac of course.

----

on my other Mac Pro 5.1 I can't create a bootstick.

Error Saving Image
An error occurred while attempting to save a disk image.

Both 144, Mojave 10.14.5

different USB Stick, this time a 16 GB

maybe this helps ?

Code:
Jun 17 00:59:06 Mac-Pro-51 macOS Catalina PartialPatcher[2360]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jun 17 00:59:21 Mac-Pro-51 macOS Catalina PartialPatcher[2360]: objc[2360]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8dcd73d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x11ab0ef50). One of the two will be used. Which one is undefined.
Jun 17 00:59:50 Mac-Pro-51 macOS Catalina PartialPatcher[2391]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jun 17 01:00:01 Mac-Pro-51 macOS Catalina PartialPatcher[2391]: objc[2391]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8dcd73d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x149c1ff50). One of the two will be used. Which one is undefined.
Jun 17 01:04:05 Mac-Pro-51 macOS Catalina PartialPatcher[2512]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jun 17 01:04:10 Mac-Pro-51 macOS Catalina PartialPatcher[2512]: objc[2512]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8dcd73d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x1592f8f50). One of the two will be used. Which one is undefined.
Jun 17 01:06:33 Mac-Pro-51 macOS Catalina PartialPatcher[2589]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jun 17 01:06:37 Mac-Pro-51 macOS Catalina PartialPatcher[2589]: objc[2589]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8dcd73d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x15a367f50). One of the two will be used. Which one is undefined.
Jun 17 01:19:32 Mac-Pro-51 macOS Catalina PartialPatcher[2696]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jun 17 01:19:44 Mac-Pro-51 macOS Catalina PartialPatcher[2696]: objc[2696]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8dcd73d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x1542def50). One of the two will be used. Which one is undefined.
Jun 17 01:28:55 Mac-Pro-51 macOS Catalina PartialPatcher[2809]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jun 17 01:29:16 Mac-Pro-51 macOS Catalina PartialPatcher[2809]: objc[2809]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8dcd73d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x16929af50). One of the two will be used. Which one is undefined.
 
  • Like
Reactions: TimothyR734
Yep, it's Guid for Mac of course.

----

on my other Mac Pro 5.1 I can't create a bootstick.

Error Saving Image
An error occurred while attempting to save a disk image.

Both 144, Mojave 10.14.5

different USB Stick, this time a 16 GB

I was getting the same error as you do, on my MBP 8.1...

So I took the USB stick, the "Install macOS 10.15 Beta.app" and "macOS Catalina PartialPatcher.app" to my cMP 4.1>5.1 to try there and it worked. It created the installer at the first attempt (It didn't take more than 5-8 mins to do so).

I've run the installer, wrote the command: sudo nvram boot-args="-no_compat_check" and restarted.

The installation have finished and everything went well (Apparently) but it never finish to load the OS, keep saying there was an issue and the system will restart...

Any ideas?

I'll take that SSD and put it inside my MBP 8.1 today to see if there is working...

Thanks guys,
 
Last edited:
After many hours of research, patching, and fighting with Apple's codesinging enforcement, I have FINALLY managed to create a 100% WORKING installer patch for macOS Catalina installers! This will allow you to install Catalina on your system, just like you would on a supported Mac! Download and info can be found here. I will be making another post later today explaining exactly what I did to get this working. Remember, this is the first iteration, so I expect there to be bugs that I'll need to work out. Enjoy!

A thunderous and well deserved standing ovation goes out from me to @dosdude1 , @ASentientBot , @pkouame , @0403979 , and all the other very clever MacOS experts out there!

My MacBook Pro 5,1 is currently running Mojave 10.14.5 using the APFS post-installation patch to boot. I am wondering if it is possible to dual boot my Mojave setup with the Catalina beta? I haven’t done the APFS firmware patch using the ROM patcher tool.

Also, is there any way to enable Airplay on this machine? I’m using it as a media computer.

Thanks in advance.
 
So I got it installed using dosdude1s patcher on macbook pro 8,1

Need some help getting wifi working properly used the kext utility and it shows wifi but wont detect any networks
 
  • Like
Reactions: TimothyR734
After many hours of research, patching, and fighting with Apple's codesinging enforcement, I have FINALLY managed to create a 100% WORKING installer patch for macOS Catalina installers! This will allow you to install Catalina on your system, just like you would on a supported Mac! Download and info can be found here. I will be making another post later today explaining exactly what I did to get this working. Remember, this is the first iteration, so I expect there to be bugs that I'll need to work out. Enjoy!

No problems creating a bootable patched 10.15 installer key on a MacPro 3,1. However, can you clarify on the requirement of executing...

sudo nvram boot-args="-no_compat_check"

Is this really required for the installation to complete or is this just required as a workaround for the absence of the postinstall Boot.plist patch for the resulting installed 10.15 volume?
 
  • Like
Reactions: TimothyR734
No problems creating a bootable patched 10.15 installer key on a MacPro 3,1. However, can you clarify on the requirement of executing...

sudo nvram boot-args="-no_compat_check"

Is this really required for the installation to complete or is this just required as a workaround for the absence of the postinstall Boot.plist patch for the resulting installed 10.15 volume?
There are 2 reasons for it. One is, as you mentioned, so that the system will boot once installed. The second reason is that the second "phase" of the installer generates its own boot.plist, without the -no_compat_check flag. This I am working on patching, but for now setting it in NVRAM is required.
 
Is anyone on here good with graphics cards? I have a r7 370 that I have working in high Sierra great. But in Catalina it won’t work with the same “fix”. If anyone can point me in the right direction to finding a solution that would be awesome
 
This is what happened after an hour :(
Hmm... What size USB drive are you using? 16GB or larger is necessary for this. Also you may want to try renaming your external volume to something else, and see if that makes any difference.
 
on my desktop my usb is named macOS10.15 but when I reboot into it says base system but I think I have my nvram settings correct and sip is disabled :)
 

Attachments

  • Screen Shot 2019-06-16 at 5.46.41 PM.png
    Screen Shot 2019-06-16 at 5.46.41 PM.png
    3.1 MB · Views: 311
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.