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.
I installed Mojave on a MacBook Air 11" mid-2011 using DosDude patching. I also installed OCLP to facilitate the last updates, which did not work with DosDude alone.
Is there any advantage apart from updates that would make you prefer running one over the other?
Curious, you install OCLP and then choose the updates for the specific machine? Is there some benefits over the patcher? I am still running with only DosDude patcher on my MBP early 2011 BTW…

Latest OCLP or an older one?

***I got some updates with DosDude patcher but maybe I could get some more with OCLP?

Thanks!

***EDIT: specified in 0.4.4:
  • Remove Mojave and Catalina Root Patching
    • Never officially supported outside of developers, if required use 0.4.3
So, I’ve downloaded 0.4.3 but not in a hurry to test it…
 
Last edited:
Curious, you install OCLP and then choose the updates for the specific machine? Is there some benefits over the patcher? I am still running with only DosDude patcher on my MBP early 2011 BTW…

Latest OCLP or an older one?

***I got some updates with DosDude patcher but maybe I could get some more with OCLP?

Thanks!

***EDIT: specified in 0.4.4:
  • Remove Mojave and Catalina Root Patching
    • Never officially supported outside of developers, if required use 0.4.3
So, I’ve downloaded 0.4.3 but not in a hurry to test it…
I had downloaded updates on DosDue and they failed to install. When I used OCLP, updates were installed from the Setting panel.
 
Hello everyone, can’t believe it’s been 4 years since I last read this thread - crazy how time flies!

I’ve been looking to install Mojave on another early 2008 MacBook Pro, but I cannot find a full installer for 10.14.3, specifically 18D42 which is the last decent version without the RAM caching issues. I’ve tried torrentmac and Japanese forum sites which either have no seeders or are bundled with Clover and conflicting Hackintosh patches. I’ve also tried installing dot1 and upgrading with patched combo updates, but it each time I try patched get broken and even after re-patching, new bugs appear and the system runs less smoothly than it should.

Does anyone have a copy of the dot3 18D42 installer that they could share? @avz iirc you have a copy still? Or @alphascorp ? Cheers
 
Last edited:
Hello everyone, can’t believe it’s been 4 years since I last read this thread - crazy how time flies!

I’ve been looking to install Mojave on another early 2008 MacBook Pro, but I cannot find a full installer for 10.14.3, specifically 18D42 which is the last decent version without the RAM caching issues. I’ve tried torrentmac and Japanese forum sites which either have no seeders or are bundled with Clover and conflicting Hackintosh patches. I’ve also tried installing dot1 and upgrading with patched combo updates, but it each time I try patched get broken and even after re-patching, new bugs appear and the system runs less smoothly than it should.

Does anyone have a copy of the dot3 18D42 installer that they could share? @avz iirc you have a copy still? Or @alphascorp ? Cheers
Unfortunately I no longer have a copy of 18D42 but remember very well looking for it on the net. I think it was on allmac.
 
Unfortunately I no longer have a copy of 18D42 but remember very well looking for it on the net. I think it was on allmac.
Cheers mate - though the link on allmac goes to download 10.14.6. I contacted them and they gave me another link but it was a dot1 clover installer 🤦‍♂️😂
 
I found a dmg for 10.14.1, installed it and then installed combo updates to bring it to dot3 (by removing the "supported devices" lists in the installer distribution files), but now the install is left running slower with broken apps, even though I re-patched the system and followed the correct procedure as others have done.

Are there any notable differences running 10.14.1 vs 10.14.3 in terms of features and performance? I may just clean install 10.14.1 and run that as is, if there's no real benefit of upgrading/trying to find installers for dot2 or 3.
 
I’ve been looking to install Mojave on another early 2008 MacBook Pro, but I cannot find a full installer for 10.14.3, specifically 18D42 which is the last decent version without the RAM caching issues....
I might have missed part of this conversation, but have you tried DosDude1's Mojave patcher? --I have had good luck with it in Macbooks.

~ ~ ~

If anyone knows of a good combination of DosDude1 and/or OCLP 0.43 (or earlier) patches that work on the 2009-2011 era "silverback" iMacs and Minis (where hardware-acceleration, wifi, and or color-accuracy are usually fubared), please post of it. (I'm especially interested in anything set-up robust enough to work with all of the models (i.e., such that a single external boot drive will correctly launch on any 2008-2011 machine as well as the 2012-2019 ones).
 
For those iMacs, you should upgrade the GPU (AMD, with an EnableGOP VBIOS!) and wireless card and then use OCLP to install/boot Mojave unpatched. That way macOS works near perfectly on those machines up to Monterey.
No, I absolutely should *not* do that, because taking them apart is an unmitigated PITA (especially the 27" ones), and your suggested parts cost considerably more than the value of the 15+yo machine itself (which I am currently picking up from recyclers at $10-$25 a pop). Meanwhile, patched Mojave runs perfectly fine on C2D 2009 iMacs. It's only the i-series 2010 and 2011 models that are troublesome, and an issue of apparently incomplete hacking wizardry (i.e., lifting the necessities out of High Sierra, et al).
 
  • Like
Reactions: MBAir2010
...I cannot find a full installer for 10.14.3, specifically 18D42 which is the last decent version without the RAM caching issues....
What are these ram-caching issues? ...I occasionally encounter an irritating problem in which CCC5- and/or GBP3-made clones of Mojave volumes will inexplicably use inordinate amounts of ram (e.g. 6.5gb of 8 instead of 2.2ish) -- but this is also an issue with other OSes as well, so my problem doesn't appear to be Mojave specific.
 
Hi guys!

I have a late 2011 MacBook Pro (MacBookPro8,1) and I've installed Mojave using OCLP. Everything went ok. After using the patches (rebooted into usb and selected my mbp version and applied the patches), at the reboot the system finds a security update (2021-005) for Mojave (before patching there was only a Safari update).

If I choose to do the security update, at the reboot the system doesn't boot: it stucks with the loading bar at 100% and nothing more happens.

P.S.: I used an AFPS partition.

Is there anything I can do to solve it, or just I don't have to update?

Thanks in advance for the reply!
 
Hi guys!

I have a late 2011 MacBook Pro (MacBookPro8,1) and I've installed Mojave using OCLP. Everything went ok. After using the patches (rebooted into usb and selected my mbp version and applied the patches), at the reboot the system finds a security update (2021-005) for Mojave (before patching there was only a Safari update).

If I choose to do the security update, at the reboot the system doesn't boot: it stucks with the loading bar at 100% and nothing more happens.

P.S.: I used an AFPS partition.

Is there anything I can do to solve it, or just I don't have to update?

Thanks in advance for the reply!
Why did you use OCLP? As I understand it, OCLP is not the recommended patching method for Catalina, Mojave, and older versions of Mac OSX. You might have more success if you use the dosdude1 patching tools, which were recommended before Big Sur – https://dosdude1.com/mojave/
 
Last edited:
I've used OCLP 2.4.1 on a 15" 2011 MacBook Pro as well and it worked well for Ventura.
Yes, totally agree that OCLP works well for later versions of MacOS. I’ve also had Ventura running on my MacBook Pro (13-inch, Mid 2010, with 16GB RAM & SSD) via OCLP. But, personally, I found it a bit too laggy with the CPUs appearing to always be running flat out. I eventually rolled back to Mojave (dosdude1 patched) – and I’m much happier with that on the 15y+ old MBPro.
 
  • Like
Reactions: Audit13
Why did you use OCLP? As I understand it, OCLP is not the recommended patching method for Catalina, Mojave, and older versions of Mac OSX. You might have more success if you use the dosdude1 patching tools, which were recommended before Big Sur – https://dosdude1.com/mojave/
Hi and thanks for the reply!

I actually used dosdude1 tool to install Mojave and I have the error I've indicated.
 
  • Like
Reactions: mad-mushroom
Hi and thanks for the reply!

I actually used dosdude1 tool to install Mojave and I have the error I've indicated.
OK, understood. Did you update from High Sierra, or something earlier? There is an ‘important note’ on the dosdude1 pages about the need to have the latest BootROM version installed;not sure whether this is relevant to you. If that’s not relevant, another thing worth trying is to reboot from your patched USB installation stick and then repeating the MacOS Post Install stage. I have occasionally found it necessary to repeat the Post Install step on my own Mojave patched MacBook Pro, when things have broken. If you installed a system/security update, it is possible you might need to repeat that Post Install process to repair patching.
 
Last edited:
  • Like
Reactions: DS-1
OK, understood. Did you update from High Sierra, or something earlier? There is an ‘important note’ on the dosdude1 pages about the need to have the latest BootROM version installed;not sure whether this is relevant to you. If that’s not relevant, another thing worth trying is to reboot from your patched USB installation stick and then repeating the MacOS Post Install stage. I have occasionally found it necessary to repeat the Post Install step on my own Mojave patched MacBook Pro, when things have broken. If you installed a system/security update, it is possible you might need to repeat that Post Install process to repair patching.
Thanks for the reply.

I've done the installation from the usb stick a couple of times (formatting and not overwriting it) and every time I do the security update then I can't bott into Mojave anymore.

Talking about the BootROM, I don't know what was the last official macOS used because my cousin gave this Mac to me with an empty disk. I did the internet recovery and the Mac rebooted with Lion.
 
What are these ram-caching issues? ...I occasionally encounter an irritating problem in which CCC5- and/or GBP3-made clones of Mojave volumes will inexplicably use inordinate amounts of ram (e.g. 6.5gb of 8 instead of 2.2ish) -- but this is also an issue with other OSes as well, so my problem doesn't appear to be Mojave specific.
Bump.
 
If anyone knows of a good combination of DosDude1 and/or OCLP 0.43 (or earlier) patches that work on the 2009-2011 era "silverback" iMacs and Minis (where hardware-acceleration, wifi, and or color-accuracy are usually fubared), please post of it. (I'm especially interested in anything set-up robust enough to work with all of the models (i.e., such that a single external boot drive will correctly launch on any 2008-2011 machine as well as the 2012-2019 ones).
This a work-in-progress that I call MacOS Mojo (for Mojave-Optimized), and am close to the Grail of a single OS that will boot (externally) any C2D or i-series chip Mac of mid-2019 or earlier. This post concerns the "unsupported" Mac portion of that project. I thought about making a new thread (given that this one is nearing 800 pages and 20,000 posts), but will post here for now.

Prefatory note: I will not provide a list of software sources; a minimal level of prowess is required here, and the ability to find things on the internet serves as a handy Litmus test.

**=== Mojave on 2010/11 i-chip iMacs & others ===**
(...where "& others" refers to machines also not on Dosdude1's fully-patched list.)

**Recommended items list:**

1. external USB drive, ideally several. ( I get used SATA SSD mechanisms from a recycler very cheaply, and use them with a spiffy Sabrent SATA-USB csble.)
1a. (optional) Create a Yumi/Ventoy drive on one external with plenty of space (ideally 250gb or bigger). On it, have the latest ISO of RescueZilla. (Note: many flashstick-type USB devicrs are scam-trash with horrible throughput; a SATA SSD is vastly superior to most of them for, especially, external booting.)

2. The following software is required: DosDude1 Mojave patcher, and OpenCore v0.4.3 (and no later) for certain models not fully patched by dd1.
2a. All of the following software (some of which is now hard to find) is very useful: Carbon Copy Cloner 5 (CCC5), GetBackupPro3, Paragon Hard Drive Manager 1.2.241, Himmelbar, MainMenu, MacsFanControl, DriveDx, DiskWarrior5, Find Any File, Momiji and Orion and Chromium-Legacy browsers), and one of Peggle Nights or Angry Birds Seasons or any other OpenGL 32bit game.
2b. A wired keyboard and wired two-button wheel-mouse will save a fair bit of time not having to deal with bluetooth connection headaches or necessity of ctrl-key clicking.

3. (if necessary) Access to a second intel Mac, to marshal the items above and to create the resources below. (Note: the Dosdude1 patcher can be created with, but will not successfully boot on, most 2014+ Retina machines.)

**Procedure**

0. On your prep Mac, go to (menubar) Finder > Preferences and check the box to show hard-drives, then right-click the desktop and sort icons by Kind. In System Preferences > General, set scrollbars to Always.
00. (Aggravation avoidance) Launch Terminal, and input *sudo spctl --master-disable* and enter user password. Then in System Preferences > Users & Groups, change password to nothing. Then in System Preferences > Security & Privacy, click the lock (and don't type anything for a password), then uncheck rhe Require password box. (Allow apps downloaded From: section should show "Anywhere" with a dotted circle. --Yay! You can now use your Mac without having to type a password every five seconds, or be constantly thwarted by the App Store gatekeeper. (You are going to get asked for a user password a LOT doing all these steps.)
000. If you're attempting to backgrade to Mojave from a higher OS version, you may find yourself unable to boot from an external device until a firmware password has been removed. Boot into Recovery Mode, go to Utilities > Startup Security Utility, enter the password then disable any drive security as well as enable external booting. (You may have to restart a few times, as well as disable SIP...see below.)

1. Prepare a DosDude1 Mojave patcher: The dd1 patcher (like many installers) will wipe an entire external drive, but actually uses very little space. After creating it, launch (Applications > Utilities) Disk Utility and create a new 9gb size MacOS Extended-journaled partition at the end of the device. (The icons for these drive partitions will both appear on the desktop.)
1a. Launch CCC5, create a new cloning session (if none exist), drag the dd1 patcher partition icon into Source and the 9gb one into Destination. Under Source, set to Copy Some Files, and uncheck everything but the System Folder. Under Destination, set SafetyNet to Off. Then start the clone; as it finishes, CCC5 will ask if you wish to create a Recovery Partition; let it. Now under Source, set to Copy All Files, and do a second clone pass. (Congrats: the majority of that external drive is now freed up, and the small 9gb dd1 installer is easy to archive or clone elsewhere -- such as at the back end of the 500gb or 1tb internal drives in most iMacs.
1b. If your prep machine balks at performing any of these steps, you probably need to disable SIP.
1c. I find it useful to also have an El Capitan boot partition, also with respective Recovery Partition, on the same external drive. (This will permit us to easily launch an ElCap Recovery Partition on the target machine to disable SIP in Terminal and do a preliminary drive erase in Disk Utility (see step 4 below) on Mojave-unsupported machines; ElCap's version of Disk Utility is capable of brute-force erasing some drives that stymie newer versions.
1d. Do NOT set drive-encryption or case-sensitivity, and do NOT create a security password in Recovery Partition! --Save yourself a world of future hurt.

2. (Now on the target "unsupported" machine now, with the external drive connected....) Zap PRAM once, then disable SIP (see step 4, using any OS version Recovery Partition).
2a. Reboot into any viable OS on the target machine. Run DriveDx to determine the SMART (health) status of the internal drive(s). Any with a "red" color indication are nearly dead. (I generally advise against replacing drives in iMacs; it's much easier and less risky to attach a newer, faster external.) Drives in "red" will sometimes "heal" to "yellow" with a one-pass write of 0s erase in Disk Utility...or croak for good. "Yellow"-listed rotational drives are usually still good for many more years of moderate home use provided the APFS file-system is kept off them and machine ram increased to 8gb to eliminate most drive-caching.
2b. After disabling SIP and measuring the internal drive, reboot into the dd1 Mojave installer and open Disk Utility; erase the internal or target drive *again* to MacOS Extended-journaled, then partition it into three equalish pieces. Then erase the second one as APFS, then install Mojave into that APFS partition.
2c. During installation, decline virtually everything that is optional at that point: location services, wifi, Apple diagnostics, Siri, etc. Name the user account Admin
2d. When finished, run the post-installation patches over the same partition. (The Mac might reboot after installation -- and fail to launch since Mojave isn't patched yet -- requiring you to manually reboot into the dd1 installer.) Important: in the patcher option list, check the box for Recovery Partition, and select the disk(x)s(y) 650mb partition following the 9gb one at the end of the external installer drive. (Rerun additional times as needed for other applicable Mojave recovery partitions on the target machine. This step may have to be redone after cloning.)

3. Restart into Mojave. About this Mac > System Update ...install the 005 and Safari updates (which will take their jolly sweet time). Do NOT install any listed newer version of the OS! After it reboots, check Applications > Utilities > Activity Monitor's memory tab to verify that ram usage is not excessive (~2.2gb on 8gb machine, ~1.7 on 4). Install CCC5, GBP3, and the other utilities now. Clone the installation, even if still imperfect, to the third drive partition. Reboot into it to verify it works, then reboot back to the original, and clone a second time to the first drive partition. (If the clones use excessive memory according to Activity Monitor, run a second clone pass with GBP3, then a third with CCC5 again.)

On many Macs, you're mostly done at this point (skip to step 4, then 7) if the color palette looks correct and wifi works, and you can skip-read the rest. (Launch either of the games cited above to quickly verify if hardware-acceleration is wotking.) On a 2010 or 2011 iMac, colors will be wrong and/or hardware-acceleration disabled.

4. Reboot into Recovery Partition 10.14.6, and launch Terminal from the menubar. Input *csrutil disable* and hit Enter, then reboot into the first target drive partition (the MacOS Extended-journaled clone made above).

5. Launch OpenCore 0.4.3, and let it build, then install (note that the "build" button changed after clicking it) a boot EFI for your machine on the target drive. (It may require you reboot at this point.) The OpenCore EFI now becomes the default first-booted item on the machine, which then displays the usual option-key bootloader list (except with better icons) for a few seconds before launching the default OS partition (which will be the one used to install it); defaults for either can be reset using the usual (Option/Alt) and Ctrl key tricks.
5a: Paragon Hard Drive Manager 1.2.241 is occasionally used for two reasons: a) cloning 200mb EFI boot partitions (either OpenCore or "unmolested"), and b) cloning pre-migrate partitions whose clones made by CCC5 and/or GBP3 show wild ram consumption in Activiry Monitor. (Otherwise, do not overuse this application, as it does not respect the 134.22mb free-space segments left between HFS+ drive partitions created in Disk Utility, which will report errors during drive Repair scans if they're missing.)

6. On a 2010 or 2011 iMac (and perhaps certain others), you'll need to rerun the opencore 0.4.3 application and run the root-patch function *after* checking the box for 10.14/15 hardware-acceleration. (Note: running the dd1 patches again may bollocks the whole thing, which is why I tend to make backup partition clones every odd step of the way.)

After restarting, you'll have a Mojave 10.14.6 installation on an "unsupported" non-"metal" i-series DVD-model with working wifi, bluetooth, sound, color-palette, dual-mode, and hardware-acceleration and Open GL support.

7. (optional but recommended) Disable all of the following in Terminal (SIP must be disabled, and you'll need to temporarily recreate a user password): MRT, MDS_stores, Reportcrash, Spotlight Indexing (replace with Find Any File), and Software Update (disablement unnecessary if you're not using OCLP).
7a. I also disable Notifications because 99% of them are Apple scare-mongering BS always popping up over the desktop icons I'm trying to click.
7b. After disabling MRT, make a copy of Find Any File, rename it to MRT, and drag it into System > Library > Core Services. Get Info it, and click the Lock box to prevent the OS from ever reactivating default MRT.
7c. Install one or more "modern" browsers, and also adding the uBlockOrigin extension to each. Chromium-Legacy and Momiji are still nominally current, and Orion nearly so. (In any Firefox-fork, examine all preference settings and disable all suggestions and Mozilla telemetry.)
7d. Right-click to remove News, Safari, and any other "Apple ecosystem" launch icons you deem worthless from the dock. In the freed-up room, I usually drag on SimpleText, Calculator, Activity Monitor, CCC5, Disk Utility, and Terminal.

8. To create a pre-Migration "golden-master" archive of the working install, boot RescueZilla (using Grub mode on Macs) from the Yumi/Ventoy drive, and create a backup of the relevant partitions (which will be the 200mb EFI, the first OS partition, its 650mb Recovery Partition, and the 9gb dd1 installer partition if you like). After it's finished and you've restarted, *then* use the Migration Assistant to import your regular Mojave (or earlier) load-out from another machine's drive-clone.
8a. Keep both accounts when Migration Utility asks what to do with the existing Admin account.
8b. Remove no-longer-needed partitions with Disk Utility. Note that APFS partitions may need their individual compartments erased, and then the APFS parent erased to MacOS Extended-journaled (aka HFS+), before that partition can be "minused" (-) in Disk Utility.
8c. Do not use APFS boot-partitions long-term on rotational or Fusion drives (both of which are served very well by HFS+). Do NOT separate Fusion drives unless DriveDx reports one part is failing (note: rotational drives are usually still OK if listed as "yellow"/failing so long as they don't have hundreds of pending bad-block map-outs).

8d. The 3rd-party utility DiskWarrior5 is able to repair most instances of HFS+ partition corruption when Disk Utility is unable to*. It does, however, like to install annoying auto-launch components. (The, err, source of my copy allows running the utility from inside its launch container without having to fully install it. You will still have to remove its launch item from your Users and Groups settings afterwards, otherwise the installer will pop up every restart. (*If an external boot device ever becomes detached, do NOT reattach it! Instead, force power off the computer by holding the button, reattach the device, and then reboot. Otherwise, file-table corruption is likely to occur.)
8e. Examine the two Library > Launch folders for instances of things you don't want constantly running (as seen in Activity Monitor, if not more obviously). Note that many subscription-model application suites, Adobe in particular, will install tons of enervating crap in here. But be careful, as manually removing opencore root-patch components may prevent the machine from booting. (Correcting such F-ups is why is we make multiple partition backups, and consequently why CCC5 is the Mac GOAT utility.)

(Further edits and tweaks forthcoming....)

Deployment example: https://forums.macrumors.com/thread...sx-mojave-today.2322173/page-12#post-34421528

Addendum: I have discovered that, once set up on a 2010 or 2011 iMac, the resulting install, if CCC5-cloned to another unsupported machine, no longer needs the opencore utility (or EFI bootloader). This is the ideal situation for clone deployment to large numbers of recycler-obtained machines otherwise bound for scrap.
 

Attachments

  • 20260209_092324.png
    20260209_092324.png
    9 MB · Views: 107
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.