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.
The update is not completing. :eek:
Thank you for confirming.
Actually, tried to use the USBOpenCoreAPFSLoader3, booted into "macOS Installer" to finish the update, but here I ended up in a rescue boot loop (grey full screen text "Your computer was restarted due to ..." in multi language.) The solution was to shutdown the system and boot the dosdude1 Catalina Patcher, rerun the patches. Afterwards, the system boots correctly, and build id is 1712. Not sure what will happen next time I'll try the update.

All in all, I see tons of efforts spent by all experts here, and I am thankful for all this :) .
 
  • Like
Reactions: K two
You have a unpatched bootROM, so USBOpenCoreAPFSLoader3 or 4S1 will be required to see the macOS Installer with each new update. No problem, it just adds an additional step. Also, when patching upon completion - ALWAYS Force Cache Rebuild.? 19H1712 is the current release. ? MRT and the Validation Patch will need to be updated, as well. :cool:
 
Last edited:
  • Like
Reactions: djsaeng
Thanks to all who contributed to the Catalina patcher. I am having one issue with it however.

Macbook Pro 5,1 15" late 2008 w/ 2 GPUs. Installed Catalina patcher. Catalina 10.15.7 installed.

Machine sometimes has kernel panic with darkwakes but other times will sleep ok for an entire day with no issues. I've searched the entire MacRumors site for darkwakes issues and it seems that this has never been fully fixed. I've tried both darkwakes 0 & darkwakes 1 settings, doesn't seem to make any difference. Reset PRAM/NVRAM. Did notice some comments about dual GPU cause, but saw no solution other than disabling discrete GPU, which I'd rther not do.

I put a script to run in /library/launchagents to run via launchd to set darkwakes to 1, and then tried it at 0 at login, same result.

And there seems no way to see what the current darkwakes setting is. Pmset -g does not show it that I can tell.

Have I missed something? It's the randomness of it that's most perplexing; I can't see what it does consistently. All help greatly appreciated.

Partial Apple crash report follows, pretty much the same thing every time.

------------------
Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.
Failure code:: 0xd5f2a20d 00000031
================================================================
Model: MacBookPro5,1, BootROM MBP51.007E.B06, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.41f2
Graphics: kHW_NVidiaGeForce9400MItem, NVIDIA GeForce 9400M, 256 MB
Graphics: kHW_NVidiaGeForce9600MGTItem, NVIDIA GeForce 9600M GT, spdisplays_pcie_device, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x855D, 0x483634353655363146373036364700000000
Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1067 MHz, 0x855D, 0x483634353655363146373036364700000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Bluetooth: Version 7.0.6f7, 3 services, 25 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Hitachi HTS725050A9A364, 500.11 GB
Serial ATA Device: MATSHITADVD-R UJ-868
USB Device: USB 2.0 Bus
USB Device: Built-in iSight
USB Device: USB 2.0 Bus
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
Thunderbolt Bus:
___________________
 
  • Like
Reactions: K two
Hi all
Got a mid 2009 13" MBP running Catalina with the dosdude1 patcher. It was upgraded from El Capitan, I actually thought I was blowing away the old OS, and was surprised to see all my old files and apps still there and mostly working.

Overall it works very well and does everything I need it to, so thanks to dosdude1 and all who contributed to the patcher. :) I have a few puzzling issues still though. Not too bothered about fixing them, but would be very interested to get more information from a computer geek point of view.

First of all, the well-known issue with Chrome refusing to run after every time it updates itself and having to be code signed with an adhoc signature to make it work. I can believe the claims that this is an issue with Mac OS Gatekeeper etc as opposed to a problem with the patch. If I just have to do that after every Chrome update, no big deal.

Second, I patched/upgraded the MBP 2 months ago using the latest patcher and latest full version of Catalina available for download. The build number shown in About My Mac is 19H2. I also have a 2015 iMac running Catalina and this shows a build number of 19H1615. It just receives regular software updates, not subscribed to any beta channel.

So, can I get this version on the patched MBP using the CatalinaOTASWUFix thing? Is it worth bothering? (In particular, did Apple release a fix for the bug that makes me have to resign Chrome after every update?) I'm using SilentKnight to get the XProtect and MRT updates, so not too worried about the security issues of an older OS.

Finally, I tried dosdude1's APFS ROM Patcher, in the hope of getting rid of the boot messages and making a future CatalinaOTASWUFix easier. I'm aware of the issues with NVidia chipsets and the multiple EEPROM IDs, so I opened the machine and checked the part number of the EEPROM. (MX25L3205DM2I if anyone cares.)

Unfortunately it just corrupted the EEPROM instead of patching it. On the next boot, the MBP made the SOS beep tones and reflashed the EEPROM with the original firmware. (Hats off to Apple for this magic self-unbricking feature!) Looking at the ROM images generated by the patcher with UEFITool, they were full of checksum errors and completely unreadable. Running the ROM patcher from the Applications folder instead of Downloads helped a lot (yes I tried it again ?) but didn't fix the problem completely, there were still a few errors.

So I'm wondering if this is an issue with the APFS ROM Patcher not being compatible with Catalina? Is it worth trying to run it again from an older OS? Or is it something about the MacBookPro5,5 hardware that just makes flashing unreliable?

Excuse my ramblings, I hope someone can be bothered to read them ?
 
  • Like
Reactions: K two
How to run Kali Linux VM in VMware Fusion v8.5.10 in Catalina on a MacPro 3.1

Download the 32-bit VMware pre-built VM image - https://www.kali.org/get-kali/

After downloading the VM and importing into Fusion, open the VM's settings, under General change the OS to "Other Linux 3.x kernel".

That's it - enjoy
 
Last edited:
Need some help post-Catalina install on 2010 iMac.

Thank you, in advance, to this awesome community... the work you folks are doing is making a big difference when the giant corporations stop caring about us little guys!!!

Here is my current setup... which btw, works flawlessly using High Sierra.
Screen Shot 2022-01-23 at 6.05.06 PM.png


Other than the GPU upgrade (GTX 780M with Nick[D]vB vbios) the machine has no other modifications. I used dosdude1's latest macOS Catalina Patcher (direct from his website) to install Catalina on a separate APFS partition on the internal HD. Just did this yesterday (1/22/2022).

Screen Shot 2022-01-23 at 6.17.16 PM.png


I followed the instructions to a tee. The installation worked fine without any errors. I can boot into Catalina without any visible issues or troubles. Once I'm in Catalina, this is when my problems begin...

The main issue comes up when resizing any window or moving any window around the screen. When I do this the windows do not repaint correctly. Sections of the window become disjointed from other sections... breaking the UI. Here is an example:

IMG_4687.jpg


Secondarily none of the non-Apple apps will load, they just crash when trying to open them (basic stuff like Chrome, other browsers, etc...). I just get the "error occurred" message and the option to report to Apple or quit.

Any ideas what might be wrong?
 
  • Like
Reactions: K two
Need some help post-Catalina install on 2010 iMac.

Thank you, in advance, to this awesome community... the work you folks are doing is making a big difference when the giant corporations stop caring about us little guys!!!

Here is my current setup... which btw, works flawlessly using High Sierra.
View attachment 1948539

Other than the GPU upgrade (GTX 780M with Nick[D]vB vbios) the machine has no other modifications. I used dosdude1's latest macOS Catalina Patcher (direct from his website) to install Catalina on a separate APFS partition on the internal HD. Just did this yesterday (1/22/2022).

View attachment 1948542

I followed the instructions to a tee. The installation worked fine without any errors. I can boot into Catalina without any visible issues or troubles. Once I'm in Catalina, this is when my problems begin...

The main issue comes up when resizing any window or moving any window around the screen. When I do this the windows do not repaint correctly. Sections of the window become disjointed from other sections... breaking the UI. Here is an example:

View attachment 1948544

Secondarily none of the non-Apple apps will load, they just crash when trying to open them (basic stuff like Chrome, other browsers, etc...). I just get the "error occurred" message and the option to report to Apple or quit.

Any ideas what might be wrong?
Yes, absolutely!

Just do not use this patcher! Please backup your data, create a clean unpatched and unmodified Catalina USB installer,
install OpenCore through the OCLP and set spoofing to moderate within the patcher settings. Installer from the new UBS installer and do not patch or post install patch at all. You system ist perfectly able to run Cataline using OCLP.

Check the short guide on the first post of the iMac GPU thread about updateing macOS on modded iMacs.
 
First post and wanted to say thank you to dosdude1 and all the contributors. My Macbook Pro Early 2011 is happy and everything is working. I did notice that its also running the latest Catalina version - so it apparently pulls whatever the latest release is when you create the install media.
 
  • Like
Reactions: K two
Yes, absolutely!

Just do not use this patcher! Please backup your data, create a clean unpatched and unmodified Catalina USB installer,
install OpenCore through the OCLP and set spoofing to moderate within the patcher settings. Installer from the new UBS installer and do not patch or post install patch at all. You system ist perfectly able to run Cataline using OCLP.

Check the short guide on the first post of the iMac GPU thread about updateing macOS on modded iMacs.
Thanks, I'll take a look. I was hoping to avoid adding a separate bootloader, but if it's the only way....

How do I cleanly removing the "masOS Catalina Patcher"? I created a separate partition to install Catalina so wiping that new partition is not a problem... I'm concerned that there might be "other" changes that were made to my system... like the original EFI partition, Recovery partition, etc!
 
I am completely new to Mac’s and mentioned I picked up a 2009 iMac the other day. I did get a reply about using CatalinaOTAswufix for updates.

I am a bit confused and want to make sure I don’t mess something up.

I have high sierra how. I was about to use dosdude1 to install Catalina. I did put Windows 10 on it too and that works just fine.

After I install Catalina, is Apple still releasing updates for it? Will they show in the App Store? Is it okay to update it if they are there? Do I turn off updates somehow. Do I use dosdude1 again for updates?

Sorry, the CatalinaOTAswufix looked a bit confusing and I was looking for a easy way to do updates if they are still happening. I know it’s a lot of questions but there doesn’t seem to be any details on what to do after you install dosdude1’s patch.
 
  • Like
Reactions: K two
Thanks, I'll take a look. I was hoping to avoid adding a separate bootloader, but if it's the only way....

How do I cleanly removing the "masOS Catalina Patcher"? I created a separate partition to install Catalina so wiping that new partition is not a problem... I'm concerned that there might be "other" changes that were made to my system... like the original EFI partition, Recovery partition, etc!
Write OC and reboot into the Catalina installer. Within the installer start disk utility and delete the APFS used by the former installer, do not initialize the complete disk, you will loose OC and the ability to install Catalina.

This boot loader is the cleanest way to install an unsupported macOS - there is absolutely no reason to avoid it!
 
Need some help post-Catalina install on 2010 iMac.

Thank you, in advance, to this awesome community... the work you folks are doing is making a big difference when the giant corporations stop caring about us little guys!!!

Here is my current setup... which btw, works flawlessly using High Sierra.
View attachment 1948539

Other than the GPU upgrade (GTX 780M with Nick[D]vB vbios) the machine has no other modifications. I used dosdude1's latest macOS Catalina Patcher (direct from his website) to install Catalina on a separate APFS partition on the internal HD. Just did this yesterday (1/22/2022).

View attachment 1948542

I followed the instructions to a tee. The installation worked fine without any errors. I can boot into Catalina without any visible issues or troubles. Once I'm in Catalina, this is when my problems begin...

The main issue comes up when resizing any window or moving any window around the screen. When I do this the windows do not repaint correctly. Sections of the window become disjointed from other sections... breaking the UI. Here is an example:

View attachment 1948544

Secondarily none of the non-Apple apps will load, they just crash when trying to open them (basic stuff like Chrome, other browsers, etc...). I just get the "error occurred" message and the option to report to Apple or quit.

Any ideas what might be wrong?
After re-patching - Force Cache Rebuild!☑️ wait 10 sec. restart. Run the Patch Updater in the /Utiliies ƒ. :cool: Remove nothing, yet.:eek:
 
Last edited:
I am completely new to Mac’s and mentioned I picked up a 2009 iMac the other day. I did get a reply about using CatalinaOTAswufix for updates.

I am a bit confused and want to make sure I don’t mess something up.

I have high sierra how. I was about to use dosdude1 to install Catalina. I did put Windows 10 on it too and that works just fine.

After I install Catalina, is Apple still releasing updates for it? Will they show in the App Store? Is it okay to update it if they are there? Do I turn off updates somehow. Do I use dosdude1 again for updates?

Sorry, the CatalinaOTAswufix looked a bit confusing and I was looking for a easy way to do updates if they are still happening. I know it’s a lot of questions but there doesn’t seem to be any details on what to do after you install dosdude1’s patch.
Yes, Updates are still on-going. CatalinaOTAswufix is the proven method to update Catalina, with an up-patched bootROM, some form of OpenCore will be needed to see the macOS installer, up until now USBOpenCoreAPFSloader3.app has been used very successfuly or you can wipe the partition run OCLP from USB, re-install Catalina, post-install patch, migrate your data back into Catalina. Choose.
 
Last edited:
I am completely new to Mac’s and mentioned I picked up a 2009 iMac the other day. I did get a reply about using CatalinaOTAswufix for updates.

I am a bit confused and want to make sure I don’t mess something up.

I have high sierra how. I was about to use dosdude1 to install Catalina. I did put Windows 10 on it too and that works just fine.

After I install Catalina, is Apple still releasing updates for it? Will they show in the App Store? Is it okay to update it if they are there? Do I turn off updates somehow. Do I use dosdude1 again for updates?

Sorry, the CatalinaOTAswufix looked a bit confusing and I was looking for a easy way to do updates if they are still happening. I know it’s a lot of questions but there doesn’t seem to be any details on what to do after you install dosdude1’s patch.
The best thing you can do is changing the GPU and enjoying later (unpatched) macOS support including Monterey using OCLP.
 
First post and wanted to say thank you to dosdude1 and all the contributors. My Macbook Pro Early 2011 is happy and everything is working. I did notice that its also running the latest Catalina version - so it apparently pulls whatever the latest release is when you create the install media.
Look at the Build # it is likely 19H2, the last full installer is 19H15, the current release is 19H1615, the current Developer Release is 19H1712 all via OTA. :cool:
 
OK, OK! Finally got the stuff to try OCLP Catalina. Just received a SATA FireWire enclosure ? will slap a new SSD in it and use OCLP to fresh install and boot 19H15. Should work, right? ?‍♂️ And to make certain will make a fresh 19H15 installer USB with gibMacOS-Master and creatinstallmedia. :rolleyes:
 
Last edited:
  • Like
Reactions: windrider42
OK, OK! Finally got the stuff to try OCLP Catalina. Just received a SATA FireWire enclosure ? will slap a new SSD in it and use OCLP to fresh install and boot 19H15. Should work, right? ?‍♂️ And to make certain will make a fresh 19H15 installer USB with gibMacOS-Master and creatinstallmedia. :rolleyes:
Yes, you should be able to install and boot any macOS installation from it (as long as you've got enabled FireWire-Booting in OCLP of course) - but you'll not be able to directly install to it.
 
Yes, you should be able to install and boot any macOS installation from it (as long as you've got enabled FireWire-Booting in OCLP of course) - but you'll not be able to directly install to it.
"but you'll not be able to directly install to it." Where is this written? How to overcome? Will have a fresh 19H15 USB to install. :eek:
 
"but you'll not be able to directly install to it." Where is this written? How to overcome? Will have a fresh 19H15 USB to install. :eek:
I had mentioned that already. Catalina and later macOS installers do explicitly prohibit installation to drives connected via FireWire - obviously because they'll normally not be bootable.
So you'll have to make at least the first installation step via a different connection. When the Mac is about to be rebooted for continuing the installation you can instead switch it off, connect the drive via FireWire and manually set the boot drive to the installer.
 
  • Like
Reactions: K two
Thanks everyone. In the 09 iMac, I did just get Windows 10 installed, and that is working just fine.

I tinker a bit, but it seems installing Catalina has become a bit more complex then it was a year ago. I watched dosdude1’s video and it all looked very simple, but it didn’t mention all the work for the updates after.

Trying to understand the update process, and reading the beginning of post one, just confuses me for some reason.
 

Attachments

  • 486ADCE6-F066-45A5-ABB5-93AA1A517579.jpeg
    486ADCE6-F066-45A5-ABB5-93AA1A517579.jpeg
    1,019.6 KB · Views: 78
Last edited:
  • Like
Reactions: K two
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.