I installed mojave with patcher in iMac mid 2011 but I look no bleu color it is converse with red help me
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Sorry to ask this. What is the intent of this effort? We already have @dosdude1's Mojave Patch app to install and update for unsupported Macs, and regular install (via App Store) for supported Macs. Sorry again for being candid.
El Capitan is the last supported OS available on my MBP. So I keep a small partition of El Capitan incase the patched versions of high Sierra and now Mojave ever fail, or something goes wrong. Without it, if Apple ever did patch the patcher (very unlikely) my computer would not be bricked and I could just go back to running the supported OS. It just makes sense to me to keep a stable, legal OS on my Mac that, if need be, I can easily go back to using. Another way to do this is to keep a USB stick with the El Capitan (or latest OS supported on your machine) installer on it so that you could always install it if Mojave ever failed.
However, I am considering getting rid of the partition on my internal SSD and partitioning my old HDD (currently an external time machine) and installing el cap on it and single boot Mojave, but haven’t decided yet.
Also, it’s helpful pinpointing bugs. On Mojave startup yesterday, I ran into a kextstall on the trackpad and keyboard. Booted into el cap, no kextstall. Ran first aid on Mojave, booted back into Mojave without issues. Just a consideration.
I've done some observations, after I've replaced every Carbon.framework content from HS inside Mojave, and the only Mojave sub-framework mandatory needed is without doubt HIToolbox.framework, I'm starting to think that the Mojave "light mode" Finder grey menu bar could be definitely bordered to the only Carbon's HIToolbox sub-framework.
@pkouame when you have spare time, please check these headers, they are withdrawn from my High Sierra 10.13.6 beta installation.
@pkouame when you have spare time, please check these headers, they are withdrawn from my High Sierra 10.13.6 beta installation.
Yes, I know, I am a wizard in replacements, and already did some attempts before, you could try if you want, if you replace the entire OpenGL.framework together with OpenCL.framework from High Sierra into the Mojave /S/L/Frameworks/ Mojave will still boot correctly but with the Finder grey menu bar in "light mode".
Please note that OpenGL and OpenCL frameworks have dependancies between them and so need to be replaced together in order to work, replacing only OpenGL.framework is not suffice and will produce stuck on stage2 apple logo. Replacing together from HS into Mojave will work.
Last edited:
I only just replaced the OpenGL framework I had no issues booting into Mojave on my iMac 9,1
I have a small patch to Mojave HIToolbox that fixes the ugly menu bar: in Light it is solid white and in Dark it is solid black. This may be an acceptable workaround for my "Hybrid" mode since transparency is enabled everywhere else.
[doublepost=1536276656][/doublepost]
I think Apple is slowly "thinning" some old frameworks (like OpenGL and others), to get rid of the 32 bit versions. This probably accounts for the dramatic reduction in size.
It will be very acceptable! Great job!
So If I have understood correctly, you have achieved an hybrid "light mode" with a kind of "reduce transparency" applied only to the glitched "blur blending windows" turning into a solid white, while keeping untouched Dock, Notification bar and other some transparencies elsewhere.
I asked because I'd have too another workaround to turn solid white some side finder "grey" windows, safari favorites, disk utility left window "grey" bar and others, just turning them in solid white, but I cannot achieve a Finder menu bar solid white, and I repeat yours is a very good workaround, much better than Accessibility prefpane "reduce transparency".
Last edited:
Hello all,
I'm new here obviously. First let me express my utmost gratitude for all the hard work @dosdude1 has done on his own free time to save our older mac hardware from becoming obsolete.
I've been lurking for quite a while as I successfully patched my mid 2009 13" MacBookPro5,5 to one of the older Mojave public betas around a month ago and ended up finding this site/forum thread while doing research on the stability of this unofficial OSX installation.
I finally decided to "bite the bullet" and go all out with finishing the upgrades to my 09 macbook pro by installing a SSD and putting the latest currently available Mojave build (DP10/PB9 on it. I decided to for for it after again seeing in an older post in this thread that someone else with the exact macbook pro I have successfully patched their "EEPROM" to allow native APFS booting, and that's when I noticed that the link to the "2.0" APFS Rom patcher on the first page is down now as of 5:24 PM Pacific Standard Time.
Is there a particular reason that the APFS rom patcher file has been taken down or is there an alternate link someone can pm me that isn't meant to be publicly available anymore?
Thanks very much. I'm looking forward to being a part of the community here.
I'm new here obviously. First let me express my utmost gratitude for all the hard work @dosdude1 has done on his own free time to save our older mac hardware from becoming obsolete.
I've been lurking for quite a while as I successfully patched my mid 2009 13" MacBookPro5,5 to one of the older Mojave public betas around a month ago and ended up finding this site/forum thread while doing research on the stability of this unofficial OSX installation.
I finally decided to "bite the bullet" and go all out with finishing the upgrades to my 09 macbook pro by installing a SSD and putting the latest currently available Mojave build (DP10/PB9 on it. I decided to for for it after again seeing in an older post in this thread that someone else with the exact macbook pro I have successfully patched their "EEPROM" to allow native APFS booting, and that's when I noticed that the link to the "2.0" APFS Rom patcher on the first page is down now as of 5:24 PM Pacific Standard Time.
Is there a particular reason that the APFS rom patcher file has been taken down or is there an alternate link someone can pm me that isn't meant to be publicly available anymore?
Thanks very much. I'm looking forward to being a part of the community here.
Last edited:
That happens with the stock frameworks too.
I noticed when I just replaced the OpenGL framework with the one from HS my Mac booted faster wench I replaced the OpenCL framework it took 5 mins to boot
The link on the initial post to the APFS patcher started the download for me. Currently on a Windows machine, so it could be different on macs, but I clicked the link and it opened a new tab for a few seconds, then closed it and it started the download of the APFS ROM patcher.
Currently my "hybrid" mode does this:
- swaps light mode "vibrancy" (which doesn't work) for dark mode "vibrancy" in appkit. Therefore in Light mode, wherever "vibrancy" is needed you get the dark mode version as demonstrated in the previous screenshots.
- Now, I found the "switch" that turns off menu bar "back drops" off in HIToolbox, so the bar is no longer translucent but simply white in Light mode and black in Dark mode.
Your mode which, if I understand correctly, flattens all the problematic Light mode areas is also a viable alternative for a Light mode.
Personally, I like Dark mode. I'm just doing this for those of us who find Dark mode way too grim.
The ultimate is, of course to just fix Light mode, which may happen as I am getting more fluent with the code.
A utility to precisely control the amount of transparency/translucency/vibrancy may also be interesting to develop in the long run.
Working for me now as well on both Win 10 and Android devices.
It seems a silent update occurred or maybe it was a fluke
.Thanks for checking for me, and thanks to whomever fixed the link, if it was fixed that is.
Now I have two quick and simple questions regarding this Rom patching tool, if someone would be so kind as to answer them.
1. At what point does this rom patcher need to be run, for example, immediately after the Mojave post install or say completely before Mojave is ever installed on a newly made APFS partition? does it matter at all when it is run; could I do it before even reinstalling Mojave?
2. Will my machine still be able to boot from an hfs+ partition/drive after this patch has been applied to my Mac?
Ty ty
1. The APFS ROM Patcher needs to be applied BEFORE installing Mojave onto an APFS volume. Otherwise, it won't boot after the install completes (unless you apply the old APFS Patch using the post-install tool, which you will want to make sure to deselect if your ROM has been patched).Working for me now as well on both Win 10 and Android devices.
It seems a silent update occurred or maybe it was a fluke
Thanks for checking for me, and thanks to whomever fixed the link, if it was fixed that is.
Now I have two quick and simple questions regarding this Rom patching tool, if someone would be so kind as to answer them.
1. At what point does this rom patcher need to be run, for example, immediately after the Mojave post install or say completely before Mojave is ever installed on a newly made APFS partition? does it matter at all when it is run; could I do it before even reinstalling Mojave?
2. Will my machine still be able to boot from an hfs+ partition/drive after this patch has been applied to my Mac?
Ty ty
2. All original functionality will remain, the only thing the ROM patcher does is add native support for booting APFS volumes to your BootROM.
Just installed the latest Mojave beta to an HFS SSD and the first thing I noticed is that I cannot select a Time Machine drive to use for backup.
I get the select drive popup input box, but no drives are showing and I cannot see any way to add a drive.
Am I alone with this issue?
I get the select drive popup input box, but no drives are showing and I cannot see any way to add a drive.
Am I alone with this issue?
Is this only I should do to get finder sidebar turns white?
Thanks @thegurz, that makes good sense on that El Capitan partition.
Thanks also @jhowarth for your post responding to mine. macOS 10.14 Mojave on Unsupported Macs Thread
So I decided to re-install Mojave Beta. First, I erased the Mojave HFS partition and then changed to APFS format. Using @dosdude1's Mojave patcher app, installed via USB, ran macOS Post installed, and re-booted. What I noticed is when doing the post install step is that when selecting my Mac model and boot drive, the APFS Patch was automatically selected (greyed out during my previous Mojave post install step. I mentioned this since my attempt to do the APFS ROM / EEPROM patcher failed.
I now have a dual boot system on my SSD (High Sierra on HFS+ partition, Mojave on APFS partition). So I'm good.
Thanks Again.
EDIT - The thing I noticed when doing an "option boot" to select my OS to use, the Mojave boot drive shows as "EFI boot". Not sure the cause, but it works.
Last edited:
No just testing purposes to get light mode functioning as it should
[doublepost=1536296279][/doublepost]
Is your hdd/ssd for the time machine formatted HFS
I've solved the High Sierra naming issues with the patched Mojave installer application. Turns out I made a mistake and replaced files that didn't need to be replaced. The license is still from High Sierra. Here is the new patched installer.
I am actually really confused now at what this does. Does this allow in-OS upgrading from macOS High Sierra to macOS Mojave without booting up from a USB drive and turning on?
Yes, but it requires more patching on the users part. If done correctly though, this is easier.
Were you able to have the night shift work without patching the core brightness, no audio or legacy video issues is trackpad working and wifi as well