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.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!
Yep, same hereThis is what happened after an hour![]()
Apparently it does not like booting to Recovery. I have not tested this, as it's not required for the installation. Test booting with option 1, Macintosh HD. The loader temporarily disables SIP, so you can run the necessary nvram command from within your root OS.Please Help what am i doing wrong (MacBook 7,1)![]()
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.
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.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).
Are you still working on CloneToolX? You seem to be an APFS God right nowso 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...
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.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!
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
you have to formate it macOS Extended Journaled before you start it and i believe it’s a GUIDHey 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!
Excellent. Great work.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.
try using an actual hard drive internally prepared as installer or external usb hdYep, same here
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!
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.
I don't have anywhere near the required coding skill for something like that, sorry. Perhaps ask @pkouame or @parrotgeek1.
[doublepost=1560569487][/doublepost]
The quote your message somehow attributed to me should be from @Starplayr.
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
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!
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!
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.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?
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.This is what happened after an hour![]()
No, due to the fact the OS relies on APFS for the second "User Data" partition in Catalina.is there any hope of getting Catalina to boot off of HFS+ rather than APFS?
Wait, wasn't there a post in which somebody managed to get it running by rsync-ing files from the APFS partitions or something? I can't find it now but I could've sworn it happened.No, due to the fact the OS relies on APFS for the second "User Data" partition in Catalina.