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.
Ich bekomme als Download mit dem neuen Patcher 1.1.9 und dem 10.15.1 DP1 also den 19B68f Full Installer?
[automerge]1571226067[/automerge]
I get as a download with the new Patcher 1.1.9 and the 10.15.1 DP1 So the 19B68f full installer?
 
  • Like
Reactions: TimothyR734
I was able to hack my system literally and got the DisplayPort to function.

This is not recommended, but I have some follow up stuff that may be of interest to whoever wants to create a patch.

Using Clover and Clover Configurator, selecting only a SMBIOS profile of Mac Pro 3,1 profile for my system and only changing the Board ID to the Mac 10,1 board ID of 'Mac-F2268CC8', and using the Clover boot loader, I was able to get DisplayPort to function on a Mac Pro 3,1 with an Nvidia GTX 680 Card with 4K@60Hz on the Display Port just like it did on the the early betas.

Now I did a search high and low for that 27" iMac 2009 board ID F2268CC8 and it is present in 4 files:

IOBluetoothUSBDFUTool
IOBluetooth.framework/.../SystemParameters.plist
.../PrivateFrameworks/ServerInformation.framework/ServerInformation
/private/var/db/uuidtext/dsc/7D86856A80053540B79F20A432768DAB <!-- that # may vary

I don't know if this matters but the Mac Pro 3,1 board ID is not in the two IOBluetooth files.

Now I have not tried swapping out that data from my working Catalina Beta or tried doing any hex editing yet. It spent a good bit of time all day yesterday just swapping out .kext files to no avail.

I did see an osX86 user have the same issue and he chose a Mac Pro 6,1 profile. That just KPs my system.

Again, using Clover is not recommended and once there is a proper patch, I will discontinue using it. I think for troubleshooting purposes, it does show that the DisplayPort can still be made active on Cat 10.15 GM and this does not appear to be a Video driver issue at all. I don't even think it is actually an AppleSMBIOS or System.kext issue either as I originally had thought. Just that Apple probably removed DisplayPort access on certain configurations.

Hope this information is helpful and that someone finds a fix so Clover or another bootloader does not have to be used. Attached are some screenshots of my findings.

Also several iMac profiles do not allow the DisplayPort to be used either, so this issue could be fixed by Apple, but also they may only fix it with certain board types. We shall see what .1 and .2 bring.

If no one tackles this, I may run a few more tests next weekend. I am hoping we can collaborate on this problem as I know there are better patchers on here than me.

Only caveat to swapping on a board ID is Apple may deprecate another board ID in the future. We all might be on borrowed time, but so far I am just glad to have 4k@60Hz back and can start building my 10.15 system out.

View attachment 869296View attachment 869297View attachment 869298View attachment 869299View attachment 869300


I got through literally all posts you made in last days. I'm sitting here with the same issue although my machine is MacBook Pro 13 2011. I even downloaded clover and clover configurator but I'm completely unaware what should I do with it in my case. And I don't want to break anything.

I got that you don't have that much time to mess around (jobs and everything) with helping but I would highly thank you if you could somehow put an instruction on what to do to make my display port working the same way you did. I don't mind waiting at all. Thanks anyway for putting any info on the common issue with DisplayPort me and others are experiencing...
 
I've made a clean install yesterday based on 1.1.7 patcher. Everything seems to have gone well, including after install patching, and automatique patch updater.

But today, in Terminal, when trying "csrutil status", it says "unknown" with all configurations "disabled".
- Is that normal?
I think so but I'm not sure. I believe the current value is stored in nvram:
Code:
hex=$(printf "$(nvram csr-active-config | sed -E '/^csr-active-config.(.*)/s//\1/g;/\\/s//\\\\/g;/%/s//\\x/g')" | xxd -p);hex=0x${hex:6:2}${hex:4:2}${hex:2:2}${hex:0:2};echo $hex
The number I get is 0x00000077. I think a normal value is 0x00000067. Anyway, 0x77 has 6 bits set but the csrutil status lists 7 different disabled items so I don't know what's going on:
Code:
Configuration:
    Apple Internal: disabled
    Kext Signing: disabled
    Filesystem Protections: disabled
    Debugging Restrictions: disabled
    DTrace Restrictions: disabled
    NVRAM Protections: disabled
    BaseSystem Verification: disabled

No issues here on the Mac Pro using Patcher 1.1.9 and the 15.0.33 Installer including the Supplemental Update. Used my MBP to download from the App Store and 'Installed to this Machine' over the first public release.
Same on MacPro3,1

Edit: added zsh compatibility for hex command
 
Last edited:
No problems here on a MacPro 3,1 with GTX680 with a usb installer created with the 15.0.33 full installer and Catalina Patcher 1.1.9. Also, the Apple ID login problems disappeared after the upgrade as expected.
 
  • Like
Reactions: TimothyR734
I can safely report the installation went ok this time around.
I downloaded 1.1.9 and install it fresh again. My Macbook Pro 13" Early 2011 is now using Catalina.
Good work @dosdude1, some token of appreciation is on your way.

Great! Although I cannot create a new installer as the Mini won't boot now! :-(
I'm making one more attempt with 1.1.8 USB as there doesn't appear to be a way to restore from my Time Machine backup.
 
  • Like
Reactions: TimothyR734

Attachments

  • Screenshot 2019-10-16 at 15.07.14.png
    Screenshot 2019-10-16 at 15.07.14.png
    2.3 MB · Views: 221
Somewhat interesting problem...
I have an iMac 9.1 running Catalina thanks to dosdude's patcher. And I have an external hard drive connected via FireWire800.
For the last 2 months I've been trying to install Catalina on one of the smaller partitions on this external drive. First this was formatted as HFS+Journaled, but hey, let's try to install Catalina on this.
No work: I can create an USB-stick with Catalina, I can boot into this, but I can't select this partition due to no APFS.
I format only this partition to APFS ( so I have 2 partitions, 1 HFS+, and 1 container with APFS.
This time I can select this partition as destination, iMac reboots and starts the installation.
After about 4 minutes (of the progress bar that indicates it would take 10min) the machine just reboots into my Catalina.
Tried this a few times, but no, I can't get Catalina installed on that partition.

Today I try again, with all the latest versions (of patcher, and Catalina itself), I boot into the USB-stick ready to select my APFS formatted partition.
Boom: I get the message when hovering over this destination: "You cannot install on a FireWire drive."

Is this a known issue? Limitation of the installer, Catalina, the patcher ??? I can't find any info about this on the 'nets.

Next I'm gonna try this exercise on a partition on an external USB drive, but that is gonna be a lot slower then FW.
 
  • Like
Reactions: TimothyR734
I usually just follow this thread without posting. I also noticed with USB boot drive that I couldn't install over Firewire.

Under Mojave, this was my go-to method for installation of my MacPro 3,1 with Metal-compatible but non-EFI video card. Now, under Catalina the only method is the "Install to this Machine" which has worked perfectly for both the initial release and the supplemental.
 
  • Like
Reactions: TimothyR734
I installed using the 1.1.6 patcher. Does the "Patcher Update" tool update the fixes in the newest patchers or i need to install again?

I`ve the 2011 mbp with the AMD GPU problem(8.2). In catalina its everything working well, except the bugs in light mode. In dark mode its all right.
 
  • Like
Reactions: TimothyR734
@dosdude1, I’d like to request a small change to the Catalina patcher. In previous versions of the patcher, you could choose where the macOS installer download went. Now it’s just dropped in the download folder on the boot drive. Can we get that feature back please?
 
  • Like
Reactions: TimothyR734
I have a MacPro 5,1 with the original release installed (19A583, released 10/7/19). I downloaded Catalina Patcher 1.1.9, used it to download the new Catalina installer (intsaller version 15.0.33) and then attempted the "Install to this machine" option that has always worked flawlessly on this machine. It went through the initial install process and rebooted but rather than installing the new version, it just booted back into the untouched, previous version. I then created a USB installer and rebooted to that. The installer would not even attempt to install to that volume, so I used an external drive, formatted as APFS and this install terminated with an "This operation can't be completed. Permission denied".

Am I alone in this or is this something specific to my system? Any suggestions would be welcomed!
 
  • Like
Reactions: TimothyR734
Oh right, then it's simply this, type from Catalina Terminal:

sudo mount -uw / ; killall Finder

then repeat your commands to replace on-the-fly the file, it works just tested.

That command worked to allow me to replace the file, but when I went to install HIToolbox, my computer would no longer start up from Catalina. It would take about 30 minutes for the loading bar to reach the end, and then it would just sit there and get really hot indefinitely, not actually starting up, with the loading bar full. I reinstalled Catalina, and will try it again soon. This time, however, I will install HIToolbox before replacing the file.
 
  • Like
Reactions: TimothyR734
I have to revert back to High Sierra (and start from scratch).

Will I be able to recover all my files which are on Time Machine (created on Catalina), or will I have to upgrade to Catalina with Patcher to recover those files on Time Machine? Thanks.
 
  • Like
Reactions: TimothyR734
I have a MacPro 5,1 with the original release installed (19A583, released 10/7/19). I downloaded Catalina Patcher 1.1.9, used it to download the new Catalina installer (intsaller version 15.0.33) and then attempted the "Install to this machine" option that has always worked flawlessly on this machine. It went through the initial install process and rebooted but rather than installing the new version, it just booted back into the untouched, previous version. I then created a USB installer and rebooted to that. The installer would not even attempt to install to that volume, so I used an external drive, formatted as APFS and this install terminated with an "This operation can't be completed. Permission denied".

Am I alone in this or is this something specific to my system? Any suggestions would be welcomed!

I am not sure of all of the details, but on the past few pages people have been having problems with installing the newest Catalina Beta, with it just installing the full release 15.0. The answer that was given had to do with being enrolled in apple's beta program, which you can do at beta.apple.com. I am not sure of all of the details, but rereading the past ~10 pages should answer your question.
 
  • Like
Reactions: TimothyR734
I have a MacPro 5,1 with the original release installed (19A583, released 10/7/19). I downloaded Catalina Patcher 1.1.9, used it to download the new Catalina installer (intsaller version 15.0.33) and then attempted the "Install to this machine" option that has always worked flawlessly on this machine. It went through the initial install process and rebooted but rather than installing the new version, it just booted back into the untouched, previous version. I then created a USB installer and rebooted to that. The installer would not even attempt to install to that volume, so I used an external drive, formatted as APFS and this install terminated with an "This operation can't be completed. Permission denied".

Am I alone in this or is this something specific to my system? Any suggestions would be welcomed!
Do you have SIP disabled whilst you run the patcher? Can enable SIP after once installed.
 
  • Like
Reactions: TimothyR734
I have to revert back to High Sierra (and start from scratch).

Will I be able to recover all my files which are on Time Machine (created on Catalina), or will I have to upgrade to Catalina with Patcher to recover those files on Time Machine? Thanks.

If you have access to Migration Assistant, you can restore your files from your Time Machine Backup, so it should work. Obviously programs that require Catalina to run may not run, but all of the files would be in tact and accessible. Using Migration Assistant, the files are migrated onto a new OS. If you use 'Restore From Time Machine Backup' under Disk Utility, however, it will migrate both the files and the OS you were on.

See this article: https://support.apple.com/en-us/HT203981
 
  • Like
Reactions: TimothyR734
5 and half hour later, still showing same screen, loading bar underneath apple logo.
Not sure what is wrong. Probably going to try installing again.
For MBP 13" Late 2011, 1.1.8 and 1.1.9 doesn't makes a difference, right?
You need to use patcher version 1.1.9 as there is a legacy video glitch with 1.1.8 I wasn't successful with that version
[automerge]1571246679[/automerge]
Do you have SIP disabled whilst you run the patcher? Can enable SIP after once installed.
SIP need to remain disabled as things may stop working if your using any post install patches
[automerge]1571246791[/automerge]
Screen Shot 2019-10-16 at 10.18.22 AM.png

[automerge]1571246934[/automerge]
I was unsuccessful with Patcher version 1.1.8 created successfully 1.1.9 then installed to this machine successfully used patcher 1.1.9 to apply the post install patches and then I had to manually open the patch updater to apply Night Shift then after reboot applied successfully BlueSky patches :)
 
@dosdude1, I’d like to request a small change to the Catalina patcher. In previous versions of the patcher, you could choose where the macOS installer download went. Now it’s just dropped in the download folder on the boot drive. Can we get that feature back please?
The reason why the macOS goes into the download folder if you put it in the application folder after install the macOS Catalina updates it gets erased by the update therefore you have to download it again if something were to go wrong
 
Think this is a bug or limitation to running Cat on my 2011 MBP. On the Photo app, I do not have the icon or view to "All Photo's" in the sidebar. Therefore I can't get to the slick new screen with all the different sized photo's and video previews.

Here are some screenshots of the issue:


I don't remember where it was, but this issue was addressed a few pages ago. I don't think there's currently a fix, or know if there is one in the works, but you can right click (control-click) on an image and click 'Show in All Photos' to get to the All Photos tab
 
I am not sure of all of the details, but on the past few pages people have been having problems with installing the newest Catalina Beta, with it just installing the full release 15.0. The answer that was given had to do with being enrolled in apple's beta program, which you can do at beta.apple.com. I am not sure of all of the details, but rereading the past ~10 pages should answer your question.


This is not the beta, this is the new "release" version, which is the full version of the installer that get you what you would have if you have a supported machine and applied the supplemental update. To be sure that the installer was okay, I used it to install into a VMWare Fusion virtual machine and all is good there (which virtualizes a supported machine).
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.