macOS 10.14 Mojave on Unsupported Macs Thread

[antony34]

There is no flashing with the APFS system patch. It's just copying some files. The APFS ROM patch is the one with flashing and can be dangerous if it fails.

got it

let me try to install it @ HFS partition 1st

 

[0403979]

got it

let me try to install it @ HFS partition 1st

Good luck. Let me know if you have any issues.
[doublepost=1556036331][/doublepost]

I've released two huge updates today. One update to macOS Patcher and the other to macOS Downloader. I'm also introducing my new website/team called RMC.

Release notes for macOS Patcher:

• Add support for the MacBook4,1 in macOS 10.12 and 10.13 installers
• Add support for macOS 10.14.5 betas with full acceleration
• Add new prelinkedekernels for macOS 10.12 and 10.13 installers
• Completely rewrite code
• Improve the appearance
• Improve functionality and reliability
• Improve errors and warnings
• Rename System Update Detection to Patch Integrity Protection
• Improve Patch Integrity Protection functionality and alerts
• Improve the transutil tool and add newer transparency patches
• Improve the restore tool speed and reliability
• Improve restoring a system patched by a dosdude1 patcher
• Improve permission repair speed and functionality
• Improve and clean up code
• Improve and clean up file structure
• And much more

Release notes for macOS Downloader:

• Add latest macOS 10.14.5 betas
• Completely rewrite code
• Update the appearance
• Improve and clean up code
• Improve and clean up file structure
• And much more

Information about RMC:
RMC, or Research, Modification, Customization, is a team I'm starting to bring together people around the world who have a passion for computing and particularly macOS modification and customization. Currently there is only one active member aside from myself and he is Larsvonhier, the person who originally got macOS 10.14 Mojave running on an almost 10 year old MacBook4,1. I'm hoping to have more people join my team in the future and create more amazing tools together but for now it's mainly just a place to store my own tools and ideas. From now on macOS Patcher and macOS Downloader will be stored on RMC's GitHub page and all documentation will be stored on RMC's website.

Documentation on new releases:
I've currently only made new documentation and a guide for the macOS Patcher release. This can be found on the RMC website. I will create more documentation for macOS Downloader and also the errors and warnings in both macOS Patcher and macOS Downloader.

Links/where to download:

• New macOS Patcher release
• New macOS Download release
• RMC website
• RMC GitHub
• macOS Patcher documentation

If you have issues questions you can fill in the contact form on RMC's website or reply to this message for general questions about these releases. I have 5 more days of free time so now's the best time to ask me things. Thank you to all members of this community for their incredible research and inspiration. This community is what got me into bash scripting and macOS modification.

I'd particularly like to the thank the following people for their research, help, and inspiration:

• dosdude1
• parrotgeek1
• ASentientBot
• SpiraMira
• tiehfood
• jackluke
• Larsvonhier
  
• Czo

I think that concludes my super long post. If there's anything else I'll add it later. Have a good day everyone.
cc: @Larsvonhier, @visberry

An issue was found with macOS Downloader that results in a corrupted installer. This will be looked into and fixed shortly. My apologies for this issue. macOS Downloader did not receive sufficient testing.

 

[pkouame]

But do you have used these all from 10.14.4 :

AppleGraphicsControl.kext (the entire with all plugins inside)
AppleMCCSControl.kext (this is required to fix the "new" unresolved symbol)
IOGraphicsFamily.kext
IONDRVSupport.kext
IOAccelerator2D.plugin
IOAcceleratorFamily2.kext
/PrivateFrameworks/GPUWrangler.framework
/Frameworks/CoreDisplay.framework


from 10.14.3 only these two:

/Frameworks/OpenGL.framework
/PrivateFrameworks/GPUSupport.framework


And using the same external USB .5beta3 drive works exactly the same way on three different machines (also singleGPUs) with brightness, sleep and everything else.

Proof pictures attached.

Impressive!


@jackluke with .3 or .4 CoreDisplay?

 

[antony34]

OMG...suddenly can't boot up my mb4,1 after power off the machine from 10.7.5...

 

[jackluke]

Impressive!


@jackluke with .3 or .4 CoreDisplay?

.4 CoreDisplay, I've edited and re-attached in that post of mine the exact folder I used.

Only note I guess GPUWrangler must be replaced only through single user mode, since it is been constantly running and used by the system, perhaps more than OpenGL I guess.

But I repeat maybe yours Dual Nvidia Tesla is a particular machine and needs another treatment.

 

[0403979]

OMG...suddenly can't boot up my mb4,1 after power off the machine from 10.7.5...

Oh dear. Good luck getting it to work again.

 

[pkouame]

.4 CoreDisplay, I've edited and re-attached in that post of mine the exact folder I used.

Only note I guess GPUWrangler must be replaced only through single user mode, since it is been constantly running and used by the system, perhaps more than OpenGL I guess.

But I repeat maybe yours Dual Nvidia Tesla is a particular machine, don't have.

Yes, some frameworks are loaded and can't be swapped in or out easily. I do all of my framework and kext swapping from single user mode.

By the way, the way you describe your changes now is much clearer and well organized! I like.

(you may also want to mention that you are manual patching...I know that this may be a point of confusion for those trying to follow)

 

[alphascorp]

Hi everybody
I galley in a galley, first I can not download 10.14.5 Beta 3 from my apple developer account yet I downloaded several Beta version of 10.14 but today I have only "XCode" available
So I found a link to download "macOSUp10.14.5_3.pkg" and "macOSUpdCombo10.14.5_3.pkg" but it's impossible for me to install any of these updates I have the following error message:

"The installation failed.
The package "macOSUpd10.14.5_3.pkg" (or "macOSUpdCombo10.14.5_3.pkg") "requires additional components and can not be independently installed. "


So I decided to try to install "macOSUpd10.14.5_3.pkg" in first time (and "macOSUpdCombo10.14.5_3.pkg" in second time) with Pacifist
then every time I replaced CoreDisplay.framwork (.4) and I applied patch 1.3.0 of dosdude1 before reboot.
I have the same issue: my MBP5,3 reboot with a login screen where it is impossible for me to put the password as if the keyboard did not work while the trackpad, the backlight of the keyboard and the variation of brightness works correctly.



I think I'll wait for the release of 10.14.5 Final. It's really a shame

 

[avz]

10.14.5 Public Beta 3 is available!

 

[jackluke]

Hi everybody
I galley in a galley, first I can not download 10.14.5 Beta 3 from my apple developer account yet I downloaded several Beta version of 10.14 but today I have only "XCode" available
So I found a link to download "macOSUp10.14.5_3.pkg" and "macOSUpdCombo10.14.5_3.pkg" but it's impossible for me to install any of these updates I have the following error message:

"The installation failed.
The package "macOSUpd10.14.5_3.pkg" (or "macOSUpdCombo10.14.5_3.pkg") "requires additional components and can not be independently installed. "

View attachment 833495
So I decided to try to install "macOSUpd10.14.5_3.pkg" in first time (and "macOSUpdCombo10.14.5_3.pkg" in second time) with Pacifist
then every time I replaced CoreDisplay.framwork (.4) and I applied patch 1.3.0 of dosdude1 before reboot.
I have the same issue: my MBP5,3 reboot with a login screen where it is impossible for me to put the password as if the keyboard did not work while the trackpad, the backlight of the keyboard and the variation of brightness works correctly.

View attachment 833496

I think I'll wait for the release of 10.14.5 Final. It's really a shame

"Combo Update" is much larger and complete than an "Update" but I guess your main issue is that a manual installation from a .pkg must be done only from a Terminal Recovery Environment (or USB Terminal installer), because if you do it in-place many many files are busy and used by the system so they can't be overwritten. Now to avoid these issues you should re-install 10.14.4 over your current Mojave drive.

 

[0403979]

Good luck. Let me know if you have any issues.
[doublepost=1556036331][/doublepost]
An issue was found with macOS Downloader that results in a corrupted installer. This will be looked into and fixed shortly. My apologies for this issue. macOS Downloader did not receive sufficient testing.

This issue has now been fixed. You can download macOS Downloader 2.0.1 here.

Release notes for macOS Downloader 2.0.1:

• Fix installer corruption issue
• Improve installer download speed

cc: @MrZupp

 

[antony34]

Oh dear. Good luck getting it to work again.

i don't know what is the problem but it works again after disconnect the keyboard and reconnect again....
it takes some time to check out ifixit instruction...lol

EDIT: I used wrong version to made installer...lol

 

[alphascorp]

"Combo Update" is much larger and complete than an "Update" but I guess your main issue is that a manual installation from a .pkg must be done only from a Terminal Recovery Environment (or USB Terminal installer), because if you do it in-place many many files are busy and used by the system so they can't be overwritten. Now to avoid these issues you should re-install 10.14.4 over your current Mojave drive.

Thank you jackluke,
I installed the update with pacifist from another external drive under 10.14.4 in order to be able to replace all the system files.

 

[jackluke]

Thank you jackluke,
I installed the update with pacifist from another external drive under 10.14.4 in order to be able to replace all the files even those used by the system.

Correct, but I guess even in that case some spotlight or any OSX core apps can keep busy some target drive folders/files.

If you notice when you do the official apple updates they never do it directly in-place, but they reboot to a slim Recovery-Environment and from there the real installation overwriting begins.

I meant this, this is almost surely a slim apple Recovery pre-loaded in RAM to allow a complete update:

 

[0403979]

i don't know what is the problem but it works again after disconnect the keyboard and reconnect again....
it takes some time to check out ifixit instruction...lol

EDIT: I used wrong version to made installer...lol

By wrong version what version do you mean? It should work with 10.12.0 to 10.14.3

 

[alphascorp]

Correct, but I guess even in that case some spotlight or any OSX core apps can keep busy some target drive folders/files.

If you notice when you do the official apple updates they never do it directly in-place, but they reboot to a slim Recovery-Environment and from there the real installation overwriting begins.

I mean this, this is almost surely a slim apple Recovery pre-loaded in RAM to allow a complete update:

Yes I noticed this is why:
1- I replaced my internal drive with a clone of 10.14.4
2- I booted on an external drive under 10.14.4 and from that system I installed the update 10.14.5 Beta 3 with Pacifist on my internal drive (cloned).

I can not install the update from the target system, I have the following error message:

"The installation failed.
The package "macOSUpd10.14.5_3.pkg" (or "macOSUpdCombo10.14.5_3.pkg") "requires additional components and can not be independently installed. "

 

[jackluke]

Yes I noticed this is why:
1- I replaced my internal drive with a clone of 10.14.4
2- I booted on an external drive under 10.14.4 and from that system I installed the update 10.14.5 Beta 3 with Pacifist on my internal drive (cloned).

From normal boot I sometimes encounter also issues to build a correct kextcache on the target drive, instead is much better when I do that from single user mode directly on the target drive.

Moreover I have also issues when I want to clone some OSX installation into other external drives especially handling with APFS containers, instead doing that from a Recovery Environment works like a charm.

 

[antony34]

By wrong version what version do you mean? It should work with 10.12.0 to 10.14.3

i used release-10.13-151635-230419.zip to made 10.14.3..some mistake...haha

After made and it can't boot into installer. i re-download right one release-10.14-151635-230419.zip
and made it again.

 

[0403979]

i used release-10.13-151635-230419.zip to made 10.14.3..some mistake...haha

After made and it can't boot into installer. i re-download right one release-10.14-151635-230419.zip
and made it again.

Oh yeah those are version specific as indicated in the name. Does the one you made using the correct version work? Btw, you can also download the multi version zip but it's a bigger file so I wouldn't recommend it.

 

[jackluke]

Oh yeah those are version specific as indicated in the name. Does the one you made using the correct version work? Btw, you can also download the multi version zip but it's a bigger file so I wouldn't recommend it.

I just given a quick glance to your Mojave Patcher, I noticed that in every framework you have a double copy of the unix exec binary, for example "CoreDisplay binary" is both inside the CoreDisplay.framework and CoreDisplay.framework/Versions/A/

I guess the only path that OSX interprets valid to load is /Versions/A/ , I mean you could delete every binary you copied inside each framework root folder and make your patcher size slimmer.

 

[0403979]

I just given a quick glance to your Mojave Patcher, I noticed that in every framework you have a double copy of the unix exec binary, for example "CoreDisplay binary" is both inside the CoreDisplay.framework and CoreDisplay.framework/Versions/A/

I guess the only path that OSX interprets valid to load is /Versions/A/ , I mean you could delete every binary you copied inside each framework root folder and make your patcher size slimmer.

It's a GitHub thing. They don't support aliases. The zips I uploaded shouldn't include duplicates.
[doublepost=1556044783][/doublepost]

Thank you so much for letting me include it. I really didn’t expect that since it’s something you worked hard for and it’s an exclusive feature in your patcher right now. I assume the preference pane needs to also be included in order for it to function correctly?

On that subject, is there a difference between the EFIScriptHeader and EFIScriptMain between the ones within the preference pane and the ones that you replace them with? I'd prefer to just include one copy of those files. Thanks for your help. @dosdude1

 

[antony34]

Oh yeah those are version specific as indicated in the name. Does the one you made using the correct version work? Btw, you can also download the multi version zip but it's a bigger file so I wouldn't recommend it.

After used correct version, it works and installing. i will sleep soon and going to patch by tomorrow.

thanks and good night!

 

[0403979]

After used correct version, it works and installing. i will sleep soon and going to patch by tomorrow.

thanks and good night!

You're welcome. Good night.

 

[dosdude1]

It's a GitHub thing. They don't support aliases. The zips I uploaded shouldn't include duplicates.
[doublepost=1556044783][/doublepost]
On that subject, is there a difference between the EFIScriptHeader and EFIScriptMain between the ones within the preference pane and the ones that you replace them with? I'd prefer to just include one copy of those files. Thanks for your help. @dosdude1

No, there is not, they are both identical. Although, the PrefPane doesn't even work correctly in Mojave, so I just don't include it anymore. You can exclude it from your implementation.

 

[0403979]

No, there is not, they are both identical. Although, the PrefPane doesn't even work correctly in Mojave, so I just don't include it anymore. You can exclude it from your implementation.

There is actually a difference between the two EFIScriptMain files. I assume I can just include the one from the post install tool resources since that one is normally used to replace the one in the preference pane after it's copied? I assume it's the newer one then. @dosdude1