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.
So, I haven't posted in awhile so please, forgive me if the empirical data I'm about to espouse has already been discussed in this Thread or the, "macOS Big Sur on Unsupported Macs" Thread, but without even doing an intentional comparison, I was simply restarting my 2012 A1278 MBP, with 16GB RAM and a 500gb SSD Drive upgrade, because I wanted to switch Partitions. I currently have my 500GB hard drive divided into 2 equal partitions: One with macOS Big Sur 11.6.3 on it, (and only like 28gb left of storage space - The one I WAS on,) and One with macOS Monterey 12.2.1, with approx. 100gb left of storage, and on Big Sur, even playing media on VLC media player all night, my computer won't get that hot, but as soon as I booted up Monterey, I noticed the fans SIGNIFICANTLY increase, and could hear what sounded like a crackling inside my computer, so I very quickly switched back to my Big Sur Partition.
After upgrading the OS the Spotlight indexes have to be rebuilt, which takes time and stresses CPU and GPU. Fans at maximum for some hours is the consequence, as has been reported many times here.
So, no need to worry in my opinion.
 
That's very interesting... so there's a group of us who have reached the same conclusion on this. So your firmware got updated by installing the last production release of Catalina on the ext drive, correct?
I realize this is not the correct forum to post this, but on the subject of installing Catalina on a separate volume while running Monterey, the installer for Catalina won't run. Any idea on how best to approach this installation without messing up Monterey?
 
  • Like
Reactions: TimothyR734
ive been trying to download 12.2.1 (21D62) form oclp 0.4.2 and when the download is done it syas its 12.2 (21D49), i then tried to download from mr macintosh website and same thing happen does anybody notice this
in order for me to update my MBP 8,1 using OTA via update button in macOS I need to uninstall post patches in OCLP before they show up.
I then update and once completed I re-run post patches in OCLP
 
in order for me to update my MBP 8,1 using OTA via update button in macOS I need to uninstall post patches in OCLP before they show up.
I then update and once completed I re-run post patches in OCLP
I did the OTA update, and everything was ok but I want to make a bootable USB but I could not do that because every time I tried to download 12.2.1 it keep saying its 12.2
 
Have stopped doing bootable clones for a while now.
Guess what? Don't miss it. Have not needed it, once. That era is over.
Same here, although I always experiment on a copy of my production system and well, that's where a little bootable backup comes in handy, my hard rockin' amigo.
 
Making bootable USB, I suppose.
The only bootable USB I could make on a USB was using the Internet Recovery installation which put me at Mountain Lion (10.8) and I could not upgrade past that while booted there. I am unable to create a bootable USB using the OCLP-GUI as it errors out while trying to create the USB volume -
Failed to create macOS installer

Output: Started erase on disk2
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk2s2 as Mac OS Extended with name OCLP-Installer
Initialized /dev/rdisk2s2 as a 931 GB case-insensitive HFS Plus volume
Mounting disk
Finished erase on disk2
Error: 2022-02-14 12:54:27.560 OCLP-Helper[1267:12496] Starting...
/private/var/folders/tl/n671678j1fdc2knl5rrbw4v40000gn/T/_MEIpRyIOW/payloads/Installer.sh: line 4: /Applications/Install macOS Catalina.app/Contents/Resources/createinstallmedia: Permission denied
2022-02-14 12:54:45.051 OCLP-Helper[1267:12496] Done

I ran the GUI normally and receive the above, and I also ran it via sudo but in either case, I receive the same "Permission denied" error.
 
And you can make bootable install media of macos 12.2.1 (12.3), and after you boot in install enviroment - you can create separate partition for catalina.
Be sure, I tried to. All I got is SSD shown as inactive, + and - buttons inactive, guide message telling: "Impossible to divide this container because one or few of contained volumes are not connected".
 
Last edited:
The only bootable USB I could make on a USB was using the Internet Recovery installation which put me at Mountain Lion (10.8) and I could not upgrade past that while booted there. I am unable to create a bootable USB using the OCLP-GUI as it errors out while trying to create the USB volume -
Failed to create macOS installer

Output: Started erase on disk2
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk2s2 as Mac OS Extended with name OCLP-Installer
Initialized /dev/rdisk2s2 as a 931 GB case-insensitive HFS Plus volume
Mounting disk
Finished erase on disk2
Error: 2022-02-14 12:54:27.560 OCLP-Helper[1267:12496] Starting...
/private/var/folders/tl/n671678j1fdc2knl5rrbw4v40000gn/T/_MEIpRyIOW/payloads/Installer.sh: line 4: /Applications/Install macOS Catalina.app/Contents/Resources/createinstallmedia: Permission denied
2022-02-14 12:54:45.051 OCLP-Helper[1267:12496] Done

I ran the GUI normally and receive the above, and I also ran it via sudo but in either case, I receive the same "Permission denied" error.

If you have the "Install macOS Catalina.app" in your /Applications folder, and a USB key formated with a GUID Scheme named KEY for exemple, in the terminal the command :
Code:
sudo /Applications/"Install macOS Catalina.app"/Contents/Resources/createinstallmedia  --volume /Volumes/KEY
will create a install boot key for the Catalina System.
 
Same for you?
Yes, same here. I have read somewhere that the last Catalina installer and the original SSD for your MacBook Pro mightl force the firmware update. That is not an option for me as it is in my case long gone.
Here is a post that digs into this if you are feeling lucky.
Since we are not really using the Mac EFi these days as I understand it, on OCLPI am not sure if it is worth the risk of bricking. Let me know if you have other thoughts?
 
  • Like
Reactions: rehkram
If you have the "Install macOS Catalina.app" in your /Applications folder, and a USB key formated with a GUID Scheme named KEY for exemple, in the terminal the command :
Code:
sudo /Applications/"Install macOS Catalina.app"/Contents/Resources/createinstallmedia  --volume /Volumes/KEY
will create a install boot key for the Catalina System.
Unfortunately not,
~ ❯❯❯ sudo /Applications/"Install macOS Catalina.app"/Contents/Resources/createinstallmedia --volume /Volumes/Untitled
Password:
dyld[1956]: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD
Referenced from: /Applications/Install macOS Catalina.app/Contents/Resources/createinstallmedia
Reason: tried: '/Applications/Install macOS Catalina.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD' (no such file), '/Library/Frameworks/IAESD.framework/Versions/A/IAESD' (no such file), '/System/Library/Frameworks/IAESD.framework/Versions/A/IAESD' (no such file)
 
Unfortunately not,
~ ❯❯❯ sudo /Applications/"Install macOS Catalina.app"/Contents/Resources/createinstallmedia --volume /Volumes/Untitled
Password:
dyld[1956]: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD
Referenced from: /Applications/Install macOS Catalina.app/Contents/Resources/createinstallmedia
Reason: tried: '/Applications/Install macOS Catalina.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD' (no such file), '/Library/Frameworks/IAESD.framework/Versions/A/IAESD' (no such file), '/System/Library/Frameworks/IAESD.framework/Versions/A/IAESD' (no such file)

What's the size of your Installer and what's your actual System version?
 
So, I haven't posted in awhile so please, forgive me if the empirical data I'm about to espouse has already been discussed in this Thread or the, "macOS Big Sur on Unsupported Macs" Thread, but without even doing an intentional comparison, I was simply restarting my 2012 A1278 MBP, with 16GB RAM and a 500gb SSD Drive upgrade, because I wanted to switch Partitions. I currently have my 500GB hard drive divided into 2 equal partitions: One with macOS Big Sur 11.6.3 on it, (and only like 28gb left of storage space - The one I WAS on,) and One with macOS Monterey 12.2.1, with approx. 100gb left of storage, and on Big Sur, even playing media on VLC media player all night, my computer won't get that hot, but as soon as I booted up Monterey, I noticed the fans SIGNIFICANTLY increase, and could hear what sounded like a crackling inside my computer, so I very quickly switched back to my Big Sur Partition. I don't really even need the Big Sur partition, I just don't know of a free cloud big enough to store all my data from the Monterey partition while I erase it so I can re-download it.
**SO IN CONCLUSION, IMO, macOS Big Sur is much safer for older MBP's running it as an unsupported format.** At least for me, there's no real "dramatic improvements" Monterey has over Big Sur, and as a matter of fact, the reason I kept my Big Sur Partition this whole time is because while it CAN run Kali Linux and other Virtual Machine software, other than Parallels desktop, which barely works half the time and is no comparison to VMware Fusion Pro 12, I have yet to find a way to run a VM on the Monterey Partition. If I try to run VMware Fusion Pro 12, it'll say something like, "Connection Error: Pipe has been Broken"???
This is due to the post-install patches. I've noticed that my 2012 MBP runs VMWare Fusion without the pathes (for the HD4000 graphics, that was dropped by Apple. As the unpatched instance works, maybe there is hope, but that will require some changes to the patches.
 
Unfortunately not,
~ ❯❯❯ sudo /Applications/"Install macOS Catalina.app"/Contents/Resources/createinstallmedia --volume /Volumes/Untitled
Password:
dyld[1956]: Library not loaded: @executable_path/../Frameworks/IAESD.framework/Versions/A/IAESD
Referenced from: /Applications/Install macOS Catalina.app/Contents/Resources/createinstallmedia
Reason: tried: '/Applications/Install macOS Catalina.app/Contents/Resources/../Frameworks/IAESD.framework/Versions/A/IAESD' (no such file), '/Library/Frameworks/IAESD.framework/Versions/A/IAESD' (no such file), '/System/Library/Frameworks/IAESD.framework/Versions/A/IAESD' (no such file)
The most easy way to create an Catalina USB installer is using the @dosdude1 Catalina patcher tool. Just do not patch the installer in the last step. Just stop it after creating the USB flash drive….
 
Yes, same here. I have read somewhere that the last Catalina installer and the original SSD for your MacBook Pro mightl force the firmware update. That is not an option for me as it is in my case long gone.
Here is a post that digs into this if you are feeling lucky.
Since we are not really using the Mac EFi these days as I understand it, on OCLPI am not sure if it is worth the risk of bricking. Let me know if you have other thoughts?

Thanks houser. Just FYI, the SSD in my external drive enclosure is the original one, swapped out when I bought the OWC kit with the new 1 TB drive & empty enclosure for the old OEM drive.

Here's the workflow I'm currently planning to get Catalina installed on the external drive.

While booted into Monterey on the internal drive:
TM backup the internal drive (done).
Erase the whole external SSD (done).
Grab the Catalina full installer from the App Store (it's downloading now).
Unpack & run the installer; when it asks which drive to install Catalina on choose the external SSD. I've done this before a few times and it has always worked. The big question in my mind though is will it choke on installing an older version; I've only ever done this for newer macOS versions.

From there, if all goes well, I'll be selecting the external drive during the usual installation auto-reboots.
On final reboot create the admin user so I can log into the empty Catalina to be able to apply any future security updates as and when they are released.

Anyway, that's the plan. :) I will report back.

Edit, later: This did not work, see my later post down the page
 
Last edited:
Let's be honest here.

If you have trouble with simple creation of USB installer, you have no business mucking around with OCLP.

STOP, step back. This is not for you.
I had no problems creating the USB Installer, provided it wasn't mucked up by storing my "Install macOS ..." files on my NAS (ext-4 fs), which now I understand breaks things. Download good versions of installers from Apple or wherever and do not store out on any non-Apple FS (or create an archive if doing so). Downloading proper images from Apple now and will redo.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.