Use BlueSky. Transparency utility is deprecated. https://github.com/rmc-team/bluesky
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
Hi @0403979, I just wanted to say thanks your BlueSky patch is really awesome. Finally I can enjoy light mode again on 10.14.6. One question though: Why don't you include it in your main macOS Patcher? Thanks again
I wish to have some more clarity in your approach. I have followed http://dosdude1.com/gpudisable/.
Now to follow your approach what should I do?
I can confirm this works on an iMac 7,1 with 10.14.3 to return native keyboard function brightness control.
macOS Patcher 2 needs an update to remove transutil, which is still integrated in macOS Pacther and can still function on 10.14.0-10.14.6 by using the hybrid mode patches. macOS Patcher 3 won’t have any additional utitilties included in it. I also want this tool to be available for all users, regardless of what patcher they’re using.Hi @0403979, I just wanted to say thanks your BlueSky patch is really awesome. Finally I can enjoy light mode again on 10.14.6. One question though: Why don't you include it in your main macOS Patcher? Thanks again
Anybody got issues with getting the Mac to sleep when closing the lid? It seems mine is not detecting it. Running a Mid 2009 Macbook Pro. Also, anyone could properly calibrate the battery? Thanks.
I want to share an experience with Mac Pro 3.1 converting to APFS:
Did the step upgrading my production system (El Cap) to Mojave 14.6
Went ok, still in HFSplus
Used Disk Utility to convert to APFS, could not select Mojave no more in startup disk utility (could not bless)
System was booting thru efi boot anyway, have apfs rom patch in firmware. No Mojave Icon in boot picker, just efi boot.
Investigated a bit more and have seen that NO preboot volume was created when converting to APFS.
So there was nothing to bless, of course for apfs.
Installed Mojave again over the old, converted system. Run patches again and a working preboot apfs volume was created. Startup disk worked and a Mojave Icon is in the boot picker.
So the conclusion is: dont convert an installed hfsplus system to apfs - you will lose the ability to let the system bless it. Or re-instal it after, without data loss. As always: backup, backup, backup...
Did the step upgrading my production system (El Cap) to Mojave 14.6
Went ok, still in HFSplus
Used Disk Utility to convert to APFS, could not select Mojave no more in startup disk utility (could not bless)
System was booting thru efi boot anyway, have apfs rom patch in firmware. No Mojave Icon in boot picker, just efi boot.
Investigated a bit more and have seen that NO preboot volume was created when converting to APFS.
So there was nothing to bless, of course for apfs.
Installed Mojave again over the old, converted system. Run patches again and a working preboot apfs volume was created. Startup disk worked and a Mojave Icon is in the boot picker.
So the conclusion is: dont convert an installed hfsplus system to apfs - you will lose the ability to let the system bless it. Or re-instal it after, without data loss. As always: backup, backup, backup...
I want to echo what is said here. Love being able to use light mode in Mojave and Catalina. Great work!Hi @0403979, I just wanted to say thanks your BlueSky patch is really awesome. Finally I can enjoy light mode again on 10.14.6. One question though: Why don't you include it in your main macOS Patcher? Thanks again
My iMac 9,1 (mid-2009) updated to Mojave 10.14.6 this week. Now, it is stuck in a cycle where it is just rebooting over and over again. I never get to the MacOS desktop. This is the first issue I have had with my iMac.
My MacBookPro 5,5 (also mid-2009) is still on Mojave 10.14.5. The only issue I am having with it is that Quicken 2019 will not register because the thread (process?) communicating to the Quicken website is terminating abnormally. This happened at first on my iMac 9,1 after installing Mojave 10.14.5. Then a MacOS update came along that fixed the problem. Later, the Patch Updater introduced a patch that prevented that MacOS patch from installing on my MacBookPro. Now, I can't figure out which Patch Update it was (it was posted somewhere in this thread) and how to "undo" it.
Any help on either of these problems would be greatly appreciated. I don't have any other MacOS machines and I depend on Quicken for Mac to manage my finances several times a week. With my iMac rebooting and Quicken not registering on my MacBook, I'm kinda dead in the water.
Thanks.
HRC3 aka RickC
iMac9,1 - Mojave 10.14.6 (and stuck in a reboot loop at the moment)
MacBookPro5,5 - Mojave 10.14.5 (and Quicken won't register at the moment)
My MacBookPro 5,5 (also mid-2009) is still on Mojave 10.14.5. The only issue I am having with it is that Quicken 2019 will not register because the thread (process?) communicating to the Quicken website is terminating abnormally. This happened at first on my iMac 9,1 after installing Mojave 10.14.5. Then a MacOS update came along that fixed the problem. Later, the Patch Updater introduced a patch that prevented that MacOS patch from installing on my MacBookPro. Now, I can't figure out which Patch Update it was (it was posted somewhere in this thread) and how to "undo" it.
Any help on either of these problems would be greatly appreciated. I don't have any other MacOS machines and I depend on Quicken for Mac to manage my finances several times a week. With my iMac rebooting and Quicken not registering on my MacBook, I'm kinda dead in the water.
Thanks.
HRC3 aka RickC
iMac9,1 - Mojave 10.14.6 (and stuck in a reboot loop at the moment)
MacBookPro5,5 - Mojave 10.14.5 (and Quicken won't register at the moment)
I'm experiencing the same bug, just reopen the lid and close again ... it's a silly solution but works for me :')
This is awesome work! And it has been great to get my Mac Pro 4,1 to Mojave. I do have one question though. I am thinking of selling my Mac Pro so I would like to undo all of the changes that were made. Is there an easy way to do that?
Thank you!
Thank you!
Macschrauber,
When I installed Mojave 10.14.5, I went through the entire post-installation process and have been fine for a couple of months. Do I need to do all that again after the 10.14.6 update from Apple?
Sorry. Don't mean to seem ignorant here, but this process was new to me a couple of months ago. I want to be sure I am doing the right thing before proceeding...
Thanks!
HRC3/RickC
DOH! Never mind. When in doubt, Read The Fine Manual...
Please forgive my thick-headedness. All is well after following the 10.14.6 post-install patches.
Collin, this thing just flat-out rocks. Thank you, thank you, thank you.
I'm asking this question under an abundance of caution, and I've searched around a bit and can't find the specific answer, so here goes.
Updated my Mid 2009 MBP to Mojave 14.4 several months ago with no issues, but have avoided subsequent version updates since.
I would like to get it current but, but would prefer to update through the normal system updates, vs going through the whole patching process again, if possible.
Noticed the "software update" patch in the "Patch Updater", and it appears as though this will enable us to just do a normal App Store update without any negative side effects?
Is this a correct assumption?
Again, sorry if this has been covered, as I'm sure it has, but can't find specifics of what to look out for, and if this method is better avoided.
Thanks for any help!
Updated my Mid 2009 MBP to Mojave 14.4 several months ago with no issues, but have avoided subsequent version updates since.
I would like to get it current but, but would prefer to update through the normal system updates, vs going through the whole patching process again, if possible.
Noticed the "software update" patch in the "Patch Updater", and it appears as though this will enable us to just do a normal App Store update without any negative side effects?
Is this a correct assumption?
Again, sorry if this has been covered, as I'm sure it has, but can't find specifics of what to look out for, and if this method is better avoided.
Thanks for any help!
Last edited:
Not too bad TBH. When I'm doing web browsing, HD video playback and office stuff the CPU is between 60 °C and 70 °C. The northbridge core is the hottest part in my Mini being usually around 80 °C and pretty much always 10 to 15 degrees warmer than the main CPU. The fans do seldom go higher than 3500 rpm so I'm quite happy with the thermal situation of my Mini. It is not specific to the OS X version however IMO. I also have 10.9.5 installed on my Mini and in terms of temperatures it is basically the same.
So i am having a little trouble getting mojave installed on my Xserve that is flashed to cMp5,1 firmware. I have so far been able to install Sierra and High Sierra with the use of dosdude1 patchers. In post installation i have only selected the .boot.plist to add and it has booted right up both times.
So now when i goto use the Mojave Patcher usb i cannot get it to boot. Although if i flash my firmware back to Xserve 3,1 i can boot the usb drive and install and use mojave no problem. But after i flash the firmware back i cannot boot into that same mojave install.
Overall i can use El Capitan-Sierra-High Sierra, all with both the Xserve3,1 firmware and the cMp5,1 firmware.
Does anyone know why the firmware would prevent me from booting the Mojave patcher usb?
So now when i goto use the Mojave Patcher usb i cannot get it to boot. Although if i flash my firmware back to Xserve 3,1 i can boot the usb drive and install and use mojave no problem. But after i flash the firmware back i cannot boot into that same mojave install.
Overall i can use El Capitan-Sierra-High Sierra, all with both the Xserve3,1 firmware and the cMp5,1 firmware.
Does anyone know why the firmware would prevent me from booting the Mojave patcher usb?
First of all your cMP 5.1 can run Mojave natively so there should be no need to run any patcher. I am writing this on a 4.1>5.1 with Mojave without any patches. Your guess that the firmwares the problem is I suspect correct. What firmware do you presently have? The latest is 144.0.0.0.0.
You will need to go back to High Sierra to get a firmware update. This must be the one from Apple as it will contain the correct firmware. To update the firmware you must have a graphics card that has the Mac efi otherwise it will not work. Once the firmware has been updated to MP51.0089.B00 you can then move onto Mojave. You will now have APFS natively. You can replace the graphics card to a metal one and then install Mojave. Again use Apple's as it will have further firmware updates included and will now work without a Mac efi graphics card. You should end up on 144.0.0.0.0 and Mojave without needing any patches. I have recently carried out this procedure with no problems. The other advantage is that you can use an NVME drive for boot. For an excellent and more detailed explanation see:https://forums.macrumors.com/thread...-bootrom-upgrade-instructions-thread.2142418/
You will only get OTA updates if you drive is formatted as APFS. If it is then this has been the way I have updated Mojave but you will have to be prepared to repatch as often the patched files get overwritten. So the foolproof way is to always have the latest USB patcher to hand. As Mojave is updated I will make a new patcher USB first - wait for dosdude to update the patcher. You then have 2 ways to proceed. You can boot to the USB and install the new Mojave over the top of your present one (backup first!). This invariably works and you keep your data and settings. Then when the update is finished reboot into the USB and apply the relevant patches. Or you can use the OTA update and see what happens. If you are lucky then the Mac may boot up but do check that everything is ok. I lost audio on my 4.2 macbook air once so just reapplied the audio patch. More often than not though the Mac will not boot up so boot to the usb (the latest one you prepared before) and then reapply all the patches.
The firmware that is installed currently on my Xserve is cMP5,1-144.0.0.0.0
Are you saying i should go back to MP51.0089.B00 then try to install mojave from that firmware?
The firmware i have flashed with is pulled from my working fully updated cMP5,1 using dosdude1 rom tool.
I understand that it should install natively. But it wont. Not through the app store, or the install dmg, or if i boot from a vanilla usb installer it shows circle slash.
Well it looks like you have the most up to date firmware but how you got there may be the problem. I would definitely look at following the guide as outlined in the link I gave you on my last post. If you can get it back to an earlier firmware then following the guide provided by Apple is probably worth a go. The recommendation by Apple is that you do go to Mojave from MP51.0089.B00 (High Sierra firmware update) so as you are having problems I would start from there. It certainly worked for me.