macOS 10.14 Mojave on Unsupported Macs Thread

[alphascorp]

Upgrading iMac 8.1 from Mac OS High Sierra 10.13.6 to Mojave 10.14.3 successfully...
Well, almost...
To run the WiFi under 10.13.6, I had replaced the famous Broadcom BCM4321 with an Atheros AR5BXB92 (worked very well under 10.13.6 ...) and to my surprise it does not work anymore with Mojave!!!
I fixed this automatically with the tool "AirPortAtheros40 installer.app" on this page:

https://www.insanelymac.com/forum/files/file/956-airportatheros40kext-installer-for-macos-mojave

here is the direct link, if someone is interressed: (an account must be created in order to download...)

https://www.insanelymac.com/forum/f...load&csrfKey=2e9e30bcccf9f9898705b5bb3d06a830

This application install the missing AirPortAtheros40.kext into /System/Library/Extensions, repairs authorization on /System/Library/Extensions and rebuilds system caches.
Now the Wifi of my iMac 8.1 works perfectly.

I have a question for Dosdude1: What exactly does "Legacy Wifi Patch" in the "macOS Post Install" application?

Only brightness no longer varies with the F1/F2 keys or system preferences . I installed "Brightness Slider" but it does not satisfy me. Is there a way to reactivate the F1/F2 keys for brightness?
or is there a post that explains how to solve this? I have a little fleme to reread the 467 posts...

View attachment 817765

Hello everyone,
Having no answer to my questions, I just reread 447 pages and I just saw Dosdude post #11156 regarding backlight control for the CCFL-based display systems. I make the fix as soon as possible.

 

[avz]

The Master has done it again!

Another success story for the dosdude1's mighty APFS ROM PATCHER!

The boot time of my MacBook5,1 is now 40 seconds!

 

[Vdovinea]

do on instructions. Error "File or directory does not exist". What am I doing wrong?

 

[DaniloGeekDude]

10.14.4 Beta Install Failed on un-supported MBs

Tried to upgrade/install from 10.14.3 Final to 10.14.4 Beta on both my MBP5,3 and MBAir4,2.

Unfortunately, both failed (boot does not complete).

Anyone on this thread able to successfully upgrade? If so, can you please share your experience with the steps required, etc. ?

Thanks.

 

[Henk Poley]

do on instructions. Error "File or directory does not exist". What am I doing wrong?

I think you will also need to tell at what step you get that error message. What were you doing ?

 

[carld]

10.14.4 Beta Install Failed on un-supported MBs

Anyone on this thread able to successfully upgrade? If so, can you please share your experience with the steps required, etc. ?

Thanks.

For me, installation went fine on a Mid 2011 Mac Mini, but on boot I discovered WindowServer was constantly crashing. Managed to resolve this by simply replacing the WindowServer binary with the one from 10.14.3 final.

 

[Vdovinea]

as here http://dosdude1.com/mojave/
[doublepost=1548517647][/doublepost]downloaded macOS Mojave from torren. Is that a problem?

 

[Henk Poley]

as here http://dosdude1.com/mojave/
[doublepost=1548517647][/doublepost]downloaded macOS Mojave from torren. Is that a problem?

Personally I would just open macOS Mojave Patcher, and then click on the menu Tools > Download macOS Mojave. As far as I know it fetches it directly from Apple, much like the App Store would.

But you may attempt less supported ways of acquiring the base image. It could be the source of your problem. You are still not saying what you were doing, except point to the huge list of steps "yeah it's somewhere in there, could you read my mind please".

 

[DaniloGeekDude]

For me, installation went fine on a Mid 2011 Mac Mini, but on boot I discovered WindowServer was constantly crashing. Managed to resolve this by simply replacing the WindowServer binary with the one from 10.14.3 final.

Thanks for the reply. Where (folder location) and what (file name) exactly is the WindowServer binary file?

Googled it and could not find in this location
/System/Library/Frameworks/CoreGraphics.Framework/Versions/A/Resources/WindowServer

Thanks.

 

[jackluke]

Thanks for the reply. Where (folder location) and what (file name) exactly is the WindowServer binary file?

Googled it and could not find in this location
/System/Library/Frameworks/CoreGraphics.Framework/Versions/A/Resources/WindowServer

Thanks.

Here:

/System/Library/PrivateFrameworks/Skylight.Framework/Versions/A/Resources/WindowServer
[doublepost=1548523520][/doublepost]

For me, installation went fine on a Mid 2011 Mac Mini, but on boot I discovered WindowServer was constantly crashing. Managed to resolve this by simply replacing the WindowServer binary with the one from 10.14.3 final.

Very good hint, infact "WindowServer" handles with many "core things".

 

[DaniloGeekDude]

Here:

/System/Library/PrivateFrameworks/Skylight.Framework/Versions/A/Resources/WindowServer
[doublepost=1548523520][/doublepost]

Very good hint, infact "WindowServer" handles with many "core things".

Thanks @carld and @jackluke for your replies.

Still getting the same issue (boot does not complete)
Used the MojaveGM WindowServer binary file below and verified checksum value

-rwxr-xr-x 1 root wheel 32K Jan 15 17:20 WindowServer*

Any other files, such as the plist files in the same folder that are needed?

 

[jackluke]

Thanks @carld and @jackluke for your replies.

Still getting the same issue (boot does not complete)
Used the MojaveGM WindowServer binary file below and verified checksum value

-rwxr-xr-x 1 root wheel 32K Jan 15 17:20 WindowServer*

Any other files, such as the plist files in the same folder that are needed?

I am not sure since I haven't updated yet, but maybe could be addressed to the entire Skylight framework so replacing entirely from a previous Mojave stable release, otherwise trying a previous Mojave kernel binary instead (located here /System/Library/Kernels/kernel ), rebuilding a new kextcache against it.

Anyway to be sure about your issue you should boot Mojave holding CMD+V (verbose mode) and check the last lines where it hangs.

 

[Larsvonhier]

Pretty nice ! I have bought a beautifull black Macbook4,1 to do the test. I am trying to boot on the mojave (patched) setup disk but i alzays ends up with a forbiden sign. I have added my boardid and model in the platformsupport.plist of the key but it still doesn't boot. Did someone know why ? Thanks

If the -no_compat_check boot parameter does not work, try to boot your MB 4,1 from a volume that you installed/patched onto a known-working unsupported Mac. I did it this way.
Welcome, btw, to the current frontier of Mojave on old machines with your MB 4,1! ;-)

 

[DaniloGeekDude]

I am not sure since I haven't updated yet, but maybe could be addressed to the entire Skylight framework so replacing entirely from a previous Mojave stable release, otherwise trying a previous Mojave kernel binary instead (located here /System/Library/Kernels/kernel ), rebuilding a new kextcache against it.

Anyway to be sure about your issue you should boot Mojave holding CMD+V (verbose mode) and check the last lines where it hangs.

Sorry to keep asking you on this.

I have verbose mode enabled by default. If boot does not finish, where can I review the boot log? I usually just power off and then boot into the mojave patcher usb : run terminal and can go to my default folders. Where exactly is the verbose log file?

Also, I will try and replace the beta kernel file with the gm kernel one.

Thanks again.

 

[jackluke]

Sorry to keep asking you on this.

I have verbose mode enabled by default. If boot does not finish, where can I review the boot log? I usually just power off and then boot into the mojave patcher usb : run terminal and can go to my default folders. Where exactly is the verbose log file?

Also, I will try and replace the beta kernel file with the gm kernel one.

Thanks again.

this should be the path /var/log/system.log

or using "dmesg" after a booted system in GUI mode, surely there are other better methods but I guess the quickest way is to record a short video or take a picture of the screen during the verbose mode from any smartphone or cameras.

Consider that your issue could be in the earlier verbose lines too, and in the beta release itself, so waiting for next release could autofix it.

 

[Badruzeus]

Still getting the same issue (boot does not complete)
Any other files, such as the plist files in the same folder that are needed?

Beside WindowServer, also try replacing CoreDisplay binary from 10.14.3 (18D42): assumed, this is the last version that you were able to bypass the LoginUI previously.

/System/Library/Frameworks/CoreDisplay.framework/Versions/A

// Replace only the binary, either with WindowServer from SkyLight.framework. And you also need:
sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force

 

[macinfo]

does the delta update work? (the combo apparenly doesnt work at all for everyone) Or is everyone re-creating the USB

EDIT: the combo works fine. I had to unpackage the combo. Added in the 10.14.2 build number into the distribution file and patched it further by removing the macbook pro 6,2 from the unsupported list. Voila everything worked.

Could you please elaborate a bit on how to upackage it? Can Pacifist be used for this or another tool?
What would I have to add/remove for a Early 2008 15-inch MacBookPro4,1?

I first tried with converting the 10.14.2 Partition to APFS, which worked, but somehow the EFI-loader-workaround didn’t find the right partition and therefore didn’t boot (have about 5 partitions on that SSD, Mojave is the last one). That’s why I’m looking for another way to "skin the cat" ;-)

Another option would be the APFS ROM patch, but I’m still a bit hesitant about using it.

EDIT:
Just found a forum comment regarding this topic, using pkgutil (.. and the seemingly corrupt distribution file of the 10.14.3 combo update): https://www.macfix.de/entries/view/930047

 

[DaniloGeekDude]

Beside WindowServer, also try replacing CoreDisplay binary from 10.14.3 (18D42): assumed, this is the last version that you were able to bypass the LoginUI previously.

/System/Library/Frameworks/CoreDisplay.framework/Versions/A

// Replace only the binary, either with WindowServer from SkyLight.framework. And you also need:
sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force

I copied the CoreDisplay binary file from my 10.14.3 installation.
For the 2nd step(s), will running the @dosdude1's Mojave Patcher | macOS Post Install | Rebuild caches before reboot do the same?

Thanks @Badruzeus !

Anyone know where I could download the full install of the 10.14.4 beta? I've been doing OTA for my previous attempts and I wanted to try the full install.

 

[L Caputo]

Could you please elaborate a bit on how to upackage it? Can Pacifist be used for this or another tool?
What would I have to add/remove for a Early 2008 15-inch MacBookPro4,1?

I first tried with converting the 10.14.2 Partition to APFS, which worked, but somehow the EFI-loader-workaround didn’t find the right partition and therefore didn’t boot (have about 5 partitions on that SSD, Mojave is the last one). That’s why I’m looking for another way to "skin the cat" ;-)

Another option would be the APFS ROM patch, but I’m still a bit hesitant about using it.

EDIT:
Just found a forum comment regarding this topic, using pkgutil (.. and the seemingly corrupt distribution file of the 10.14.3 combo update): https://www.macfix.de/entries/view/930047

Ha! thought I'd look at your link only to find somebody has copied and pasted my comment from another forum into their forum even down to the Crikey at the end, with no acknowledgement.

 

[0403979]

I copied the CoreDisplay binary file from my 10.14.3 installation.
For the 2nd step(s), will running the @dosdude1's Mojave Patcher | macOS Post Install | Rebuild caches before reboot do the same?

Thanks @Badruzeus !

Anyone know where I could download the full install of the 10.14.4 beta? I've been doing OTA for my previous attempts and I wanted to try the full install.

There is no full download for a beta.

 

[0134168]

Yeah, it happens... I'm actually planning on releasing a new "patch integrity check" feature in Patch Updater, which will alert you if it detects a patched file has been overwritten, and that a particular set of patches need to be re-installed. That way, you won't have to worry about things like this happening after updates.

You are no doubt the ****ing boss.

 

[ASentientBot]

I copied the CoreDisplay binary file from my 10.14.3 installation.
For the 2nd step(s), will running the @dosdude1's Mojave Patcher | macOS Post Install | Rebuild caches before reboot do the same?

Thanks @Badruzeus !

Anyone know where I could download the full install of the 10.14.4 beta? I've been doing OTA for my previous attempts and I wanted to try the full install.

The betas post-10.x.0 are never available as full installers, only deltas and combo updaters that I've had little success with installing manually on HFS+. 10.14.3 is the latest that comes as a full install app.

 

[ford.tonthat]

Could you show me how to edit the "Distribution" file after show package content?

 

[avz]

Could you show me how to edit the "Distribution" file after show package content?

View attachment 818382

I might be wrong but I believe the procedure would be similar to what is said in the 1st page of the High Sierra on unsupported Macs thread just with extra modifications to the distribution file.

 

[saudor]

Could you please elaborate a bit on how to upackage it? Can Pacifist be used for this or another tool?
What would I have to add/remove for a Early 2008 15-inch MacBookPro4,1?

I first tried with converting the 10.14.2 Partition to APFS, which worked, but somehow the EFI-loader-workaround didn’t find the right partition and therefore didn’t boot (have about 5 partitions on that SSD, Mojave is the last one). That’s why I’m looking for another way to "skin the cat" ;-)

Another option would be the APFS ROM patch, but I’m still a bit hesitant about using it.

EDIT:
Just found a forum comment regarding this topic, using pkgutil (.. and the seemingly corrupt distribution file of the 10.14.3 combo update): https://www.macfix.de/entries/view/930047

That is similar to what i did using pkgutil. I did open the distribution file in textwranger and added it to the array.

Just to be safe, i also added my board ID and you definitely need to remove MacBookPro4,1 from the unsupported array in that file.

To find your board id, use terminal and type in the following

var_ID=$(ioreg -p IODeviceTree -r -n / -d 1 | grep board-id);var_ID=${var_ID##*<\"};var_ID=${var_ID%%\">};echo $var_ID