macOS 10.14 Mojave on Unsupported Macs Thread

[avz]

I have a late 2008 aluminum unibody that I was successfully running Mojave on. I'd made it through the update where the new patcher (1.3.0 or later) was required and everything was running smoothly. I left it to put itself to sleep as usual yesterday, but today when I went to wake it up it was powered down even though it was fully charged. When I tried to boot it, it got stuck and eventually told me that my computer failed to boot due to a problem. It still shows my user accounts and asks for the password during boot, but fails after that. When I tried to use the patcher USB to start it up, it asked me for the language I'd like to proceed in like it was a fresh install.

I have no idea what happened or what to do from here. The only thing I'm aware of that changed yesterday was I installed a patch for Night Shift - it was prompted from the patcher tool. My system was not 100% up-to-date, if that matters, as I'm working on a dissertation and was putting off messing with it until I finished at the end of the month. Maybe the Night mode patch was for a newer version than I have? I really don't know.

The best I can say with the info that you provided is that most likely you had automatic update turned on and your MacBook updated itself.

 

[0403979]

BlueSky

I just released a new tool for macOS 10.14 Mojave and macOS 10.15 Catalina.

Here are the release notes from GitHub: "BlueSky is a command-line patch tool for the SkyLight and HIToolbox frameworks. This tool is intended for non-Metal graphics cards running unsupported versions of macOS 10.14 Mojave and 10.15 Catalina. This tool fixes transparency issues by swapping UI materials in the SkyLight framework and setting the menubar and context menus to opaque in the HIToolbox framework. The HIToolbox framework patch is only supported on macOS 10.14 Mojave. The download size for the zip is around 100MB. If you download only the script then BlueSky will automatically download the full zip file that includes all the patched binaries. The original binaries are also included in the zip file and are used for the patch removing options. Backups are also made before and after patching in /Users/Shared. These backups can be restored manually but should only be used as a last resort. Please contact RMC if you need help in recovering a damaged system."

Download link: https://github.com/rmc-team/bluesky/releases/tag/1.0

View attachment 852098 View attachment 852099

A newer version of BlueSky has been released.

Here are the release notes from GitHub: "
Release notes for BlueSky 1.1:

• Add support for the HIToolbox patch on macOS 10.15 Catalina

The download size for the zip is around 100MB. If you download only the script then BlueSky will automatically download the full zip file that includes all the patched binaries. If you downloaded an older release, you have to download a newer one to get the changes. The script file has been changed in this release."

Download link for BlueSky 1.1: https://github.com/rmc-team/bluesky/releases/tag/1.1

 

[adibythesea]

The best I can say with the info that you provided is that most likely you had automatic update turned on and your MacBook updated itself.

And if that's what happened, there's no way to fix it except to restore from a backup, is that correct?

 

[avz]

And if that's what happened, there's no way to fix it except to restore from a backup, is that correct?

Normally you would just boot into your Mojave patcher and re-apply the patches. So I don't quite understand your issue. Usually it is something very simple unless your hardware started going south.

 

[Sko]

A newer version of BlueSky has been released.

Thank you very much. That was the last piece missing to give my MacBook Air 2,1 another year.

 

[adibythesea]

Normally you would just boot into your Mojave patcher and re-apply the patches. So I don't quite understand your issue. Usually it is something very simple unless your hardware started going south.

I put in a new SSD drive and new RAM when I installed Mojave about 8 months ago. Maybe that was too much for the old hardware to keep up with. :/

My only option when I press option on startup is an EFI boot (and the USB patcher if I have it plugged in). Should I select it?

 

[LarryJoe33]

Greetings all,

I'm wondering if someone could point me in the right direction. I have a mac mini 5,1 that I patched a few months ago and I recently went to update the OS to 10.14.6, but I ran into a small issue. When I plugged what I thought was my patched installer into my mini to rerun the post install process I came to the realization that my fiancé had wiped the drive to use for a project. Now said mini won't boot and the only other machine that I have that runs macOS is my T2 equipped MacBook Air.

Is there a way I can create a utility disk that's just the post process function of the patcher? Or do I need to reinstall High Sierra and try patching to Mojave again?

I know this isn’t going to be helpful now because you didn’t do this. But I highly recommend cloning your system with CCC5 before you do this type of stuff. When things go south, I just restore to the working version of Mohave and start over. For the matter, I also have clones of the final releases of HS and Sierra that were installed on my system if I ever want to go back.

 

[Eithanius]

A newer version of BlueSky has been released.

Here are the release notes from GitHub: "
Release notes for BlueSky 1.1:

• Add support for the HIToolbox patch on macOS 10.15 Catalina

The download size for the zip is around 100MB. If you download only the script then BlueSky will automatically download the full zip file that includes all the patched binaries. If you downloaded an older release, you have to download a newer one to get the changes. The script file has been changed in this release."

Download link for BlueSky 1.1: https://github.com/rmc-team/bluesky/releases/tag/1.1

View attachment 852143

Can this also fix the jagged edge font issue...?

 

[avz]

I put in a new SSD drive and new RAM when I installed Mojave about 8 months ago. Maybe that was too much for the old hardware to keep up with. :/

My only option when I press option on startup is an EFI boot (and the USB patcher if I have it plugged in). Should I select it?

Yes, you should select it, as this is your only current option to boot into anything isn't it?

 

[0134168]

I understand that's what I should do in theory but judging from a previous post on this thread from @dosdude1 the T2 enabled Macs don't play nice with his software. I've tried several times to recreate the installer on my 2018 MacBook Air with no luck.

Has anyone found a work around for using the patching software on a T2 enabled Mac?

Did you change the settintgs of the T2?

 

[adibythesea]

Yes, you should select it, as this is your only current option to boot into anything isn't it?

It is, I was just afraid if I did I might wipe whatever might still be on my drive. After selecting it, I got the same result as when I tried a regular boot, which makes sense.

First, I get the usual Mojave script output, then a prompt for a user password with our accounts and settings still visible (which is normal):



Then, after accepting the password, it thinks for a few seconds and one of two screens display:



or



No matter which screen shows, it then restarts.

 

[dosdude1]

It is, I was just afraid if I did I might wipe whatever might still be on my drive. After selecting it, I got the same result as when I tried a regular boot, which makes sense.

First, I get the usual Mojave script output, then a prompt for a user password with our accounts and settings still visible (which is normal):



Then, after accepting the password, it thinks for a few seconds and one of two screens display:



or



No matter which screen shows, it then restarts.

You may just need to re-applt post-install patches. Seeing that you're using FileVault, ensure you unlock your volume with Disk Utility before applying the patches.

 

[adibythesea]

You may just need to re-applt post-install patches. Seeing that you're using FileVault, ensure you unlock your volume with Disk Utility before applying the patches.

Sorry for my ignorance, but if I boot with the patcher and it's trying to get me to start a new install, I should be able to go in through Disk Utility, unlock my hidden existing volume, and it will appear again?

 

[dosdude1]

Sorry for my ignorance, but if I boot with the patcher and it's trying to get me to start a new install, I should be able to go in through Disk Utility, unlock my hidden existing volume, and it will appear again?

Yes, then run the post-install tool.

 

[adibythesea]

Yes, then run the post-install tool.

That solved it. I can't even begin to thank you enough.

 

[adibythesea]

Yes, then run the post-install tool.

I'm back. Since sorting everything out and making sure everything is fully updated, I cannot get the display to sleep or change brightness. I've tried the usual resetting the NVRAM and SMC, checking the activity monitor, checking the display settings, and checking other user accounts where it shows up as well. Is this likely to be a problem with my hardware or is this a Mojave thing?

 

[0403979]

Can this also fix the jagged edge font issue...?

That's because of font smoothing on non-Retina devices. BlueSky doesn't help with that.

 

[avz]

I am wondering if there is any downside of permanently running an internal SSD as an external, connected via SATA - USB adapter? I noticed in System Information there is no way to see the TRIM status or the SMART status. Not sure if it is a problem in itself.
I am so impressed with the way Mavericks(10.9.5) handles FullHD(including 60fps) playback on my 2GHz C2D MacBook5,1, that I decided to move the MBP9,2's original 500GB HDD(with Mavericks) to MacBook5,1's HDD bay and run Mojave SSD via SATA - USB adapter. If my Superdrive stops working I will consider moving Mojave SSD to optibay.

 

[0134168]

I am wondering if there is any downside of permanently running an internal SSD as an external, connected via SATA - USB adapter? I noticed in System Information there is no way to see the TRIM status or the SMART status. Not sure if it is a problem in itself.
I am so impressed with the way Mavericks(10.9.5) handles FullHD(including 60fps) playback on my 2GHz C2D MacBook5,1, that I decided to move the MBP9,2's original 500GB HDD(with Mavericks) to MacBook5,1's HDD bay and run Mojave SSD via SATA - USB adapter. If my Superdrive stops working I will consider moving Mojave SSD to optibay.

SMART status and others does not work on USB devices. But you can make it to work. Don´t know if works on Catalaiina, though. In Mojave works like a charm.

https://github.com/kasbert/OS-X-SAT-SMART-Driver

 

[avz]

SMART status and others does not work on USB devices. But you can make it to work. Don´t know if works on Catalaiina, though. In Mojave works like a charm.

https://github.com/kasbert/OS-X-SAT-SMART-Driver

Thanks for the info but I was more interested to know if you move your internal SSD with activated TRIM to the USB port, would the TRIM still function as it should even though no info is displayed in System Preferences?

 

[0134168]

Just wanted to let you know that Beta 5 works very fluid in my Mac Pro 5.1. Been using it since day 1 and no hangs, and very fast. Only had to look for alternatives for some 32 bits apps.

I think it´s gonna be a great macOS.

Thanks again to all the people that is making this possible.

 

[MacPeet]

Good Morning.
I have an iMac8,1.
APFS ROM Patcher worked without problems.
Installation Mojave 10.14.6 (APFS) without problems.
Everything works, only the brightness control has no function.

Is there a solution for brightness control?

 

[0134168]

Good Morning.
I have an iMac8,1.
APFS ROM Patcher worked without problems.
Installation Mojave 10.14.6 (APFS) without problems.
Everything works, only the brightness control has no function.

Is there a solution for brightness control?

View attachment 852393

https://apps.apple.com/es/app/brightness-slider/id456624497?mt=12

 

[alphascorp]

Good Morning.
I have an iMac8,1.
APFS ROM Patcher worked without problems.
Installation Mojave 10.14.6 (APFS) without problems.
Everything works, only the brightness control has no function.

Is there a solution for brightness control?

View attachment 852393

Hello @MacPeet
I also have iMac8,1 and I found the solution (without using Brightness Slider.app) here are the links to my previous message #15477 and #16717. I followed message #11156 from @dosdude1 but didn't work on iMac8,1.

For iMac8,1 only replace the file "DisplayServices.framework" contained in "/S/L/PrivateFrameworks" and repair permissions (maybe it works on machines other than iMac8,1 but I could not test)

1. Download the archive below and unzip it.
2. Search for "DisplayServices.framework" in /System/Library/PrivateFrameworks and Back it up.
3. Then replace "DisplayServices.framework" with the one contained in the archive you just unzipped.
4. open the Terminal and enters the following commands (to repair permissions):

sudo chmod -R 755 /System/Library/PrivateFrameworks/DisplayServices.framework
sudo chown -R 0:0 /System/Library/PrivateFrameworks/DisplayServices.framework

5. After reboot the brightness control works with F1/F2 keyboard keys

It works with .3 .4 .5 and .6 (not tested on .1 and .2)

 

[avz]

I am wondering if there is any downside of permanently running an internal SSD as an external, connected via SATA - USB adapter? I noticed in System Information there is no way to see the TRIM status or the SMART status. Not sure if it is a problem in itself.
I am so impressed with the way Mavericks(10.9.5) handles FullHD(including 60fps) playback on my 2GHz C2D MacBook5,1, that I decided to move the MBP9,2's original 500GB HDD(with Mavericks) to MacBook5,1's HDD bay and run Mojave SSD via SATA - USB adapter. If my Superdrive stops working I will consider moving Mojave SSD to optibay.

I ended up connecting Mojave SSD to the optical drive SATAII connector and was happy to see that my negotiated link speed is 3 Gigabit. I read somewhere that the late 2008 MacBooks can only get SATAI 1.5 Gigabit link speed in the optical drive bay but it all worked out well for me.