macOS 10.14 Mojave on Unsupported Macs Thread

[adeuxx]

There is no guarantees in life. If I was you I would create a separate partition and try to install Mojave. Did your boot rom got updated? What is the firmware number? You can find that info in the system information. Since your Mac is officially supported for High Sierra, you should create and only use an official High Sierra installer.

My BR version on HS is 67.0.0.0.0, SMC version 1.62f7

Sorry for the potentially silly question but if I create a seperate partition and install Mojave there would that then be the default OS on boot? Or do I select which OS by holding the option key?

 

[avz]

My BR version on HS is 67.0.0.0.0, SMC version 1.62f7

Sorry for the potentially silly question but if I create a seperate partition and install Mojave there would that then be the default OS on boot? Or do I select which OS by holding the option key?

You can select your startup disk by going to System Preferences/Startup Disk.

 

[jackluke]

Cool. Yes it should still work with the 10.14.2 version.

So seems like I'm stuck @ .4. I'm Trying to revert back to .3 from an old .1 stick + downloaded comboUpdate10.14.3. Theoretically should work fine, but my machine spins with all kinds of MRT, spins and incessant ReportCrash issues. Haven't seen this since the old HS days. Most Apps crash with secinitd and sandbox errors (missing profiles etc...)

I know this may be old hat, but did some of you deal with this during the .2 to .3 update?

BTW, a OTA softwareupdate (still works) to the latest .4 (and post-install of course) solves the problem.

This happened to me also when I did an OTA from 10.14.2 to 10.14.3 , even using a patched upgrade.dmg/pkg produced the same side effects incessant ReportCrash issues and swapping RAM increasing.

I guess both OTA and official update.dmg/pkg don't work properly on our unsupported Mojave.

The only way I "fixed" that is re-installing over it starting from a full 10.14.3 Installer.
After all these high %cpu/RAM settled down alone.

 

[dosdude1]

Finally !!!

The problem is
kernel_task” High CPU Usage Bug

A solution was found to the problem:
1) First, enable the display of hidden folders:
- Go to the "Terminal"
- We drive in 2 teams:
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder

2) Then we determine the computer model:
- Click "About this Mac"
- Next, click "More"
- Click on the "System Report"
Where the hardware is, find and remember the "Model ID". In my case, this is a MacBook6.1

3) Follow this path:
/ System / Library / Extensions
Select the IOPlatformPluginFamily.kext file, click the right button and select "Show package contents"

4) Go to Contents / PlugIns , then on the file ACPI_SMC_PlatformPlugin.kext also select "Show package contents"

5) Next, in Contents / Resources, find the file with the laptop model. As you remember: I had a MacBook 6.1. Delete this file! (If there is no necessary file, delete the nearest models)

6) Restart the computer. This procedure will probably have to be done after every Mac OS update.

To return the display of folders, as it was before, run the following command in the Terminal:
defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder

That's not a bug with the software.... That indicates that a current sensor on your logic board is not working correctly, and needs to be repaired. I've repaired many boards that did just this.

For others: You should NOT do this on your macOS install.

 

[Pinarek]

Has anyone successfully installed the Mojave 10.14.5 Beta1?
I have successfully run the 10.14.4, see my signature in the laptop MCP79 with nVidia 9100M. Now with the 10.14.5 Beta 1 comes after applying the Mojave Patch 1.3.0 only at the Restart after loading bar, then the spinning loading gyro infinitely long. It does not appear to switch to the graphic. What do I have to do ?
Thanks for help tips.

 

[jackluke]

Has anyone successfully installed the Mojave 10.14.5 Beta1?
I have successfully run the 10.14.4, see my signature in the laptop MCP79 with nVidia 9100M. Now with the 10.14.5 Beta 1 comes after applying the Mojave Patch 1.3.0 only at the Restart after loading bar, then the spinning loading gyro infinitely long. It does not appear to switch to the graphic. What do I have to do ?
Thanks for help tips.

Try use the file attached (it's from stock .4 Mojave not patched) replace inside your .5 beta1 path: /S/L/PrivateFrameworks/

but take a copy of your current one somewhere.

This should allow to boot, however no OpenGL acceleration, only Framebuffer.

edit:
but reading your signature I guess no, for dual GPUs you need the stock GPUWrangler. Just try.
Another try, using your .5 GPUWrangler, try to delete the NDRVShim.kext from /S/L/E/.

 

[webg3]

Hi - I will be generating a 10.14.3 compatible version of hybrid in the coming week. A 10.14.4 compatible version of hybrid is testing well. Sorry, but I missed the 10.14.2 to 10.14.3 update cycle.

As always, match the Hybrid version to the Mojave version. Any other combination may destabilize your machine.
I don't plan on supporting 10.14.5 betas (at least until the issues are ironed out here)

By the way, is there any interest in the "flat" mode anymore? It's the AppKit code mod that turns transparency OFF in Light Mode (in a sort of "set and forget" mode as opposed to tweaking Accessibility features through scripts etc.) If not I will stop supporting it.

Follow the github page for more news.

Thanks.
[doublepost=1554674883][/doublepost]
Apparently Nvidia has dropped support for Mojave entirely. Sad.

Read about it here : https://devtalk.nvidia.com/default/...rivers-be-released-for-macos-mojave-10-14-/75

I don't know what this means for 10.15...

Yes, man. I'm interested in flat mode.
The only thing I would like to keep, are transparent menus.

 

[pkouame]

This happened to me also when I did an OTA from 10.14.2 to 10.14.3 , even using a patched upgrade.dmg/pkg produced the same side effects incessant ReportCrash issues and swapping RAM increasing.

I guess both OTA and official update.dmg/pkg don't work properly on our unsupported Mojave.

The only way I "fixed" that is re-installing over it starting from a full 10.14.3 Installer.
After all these high %cpu/RAM settled down alone.

Ok. So wasn't just me My throttling never settled - incessant crash loops. Used to be we could download our old "purchased" installers...oh the good ole days...Not allowing us to download full installers is just Apple arrogance (and I have a paid up developer account to boot).
Where did you get the old full installer? I don't really trust these torrent sites (just sayin...)

 

[jackluke]

Ok. So wasn't just me My throttling never settled - incessant crash loops. Used to be we could download our old "purchased" installers...oh the good ole days...Not allowing us to download full installers is just Apple arrogance (and I have a paid up developer account to boot).
Where did you get the old full installer? I don't really trust these torrent sites (just sayin...)

I still preserve some old copies of MacOSInstall.app downloaded from a supported Mac in its time, I also have a full 10.14.2 installer. But really can't upload I have a slow upload speed. Anyway I guess from torrent sites if you find a 18D109 full installer compressed in dmg, it's enough valid, only condition it must be in the form "Install MacOS Mojave.app" and I'd say it's safe even from there.

 

[pkouame]

Are you using a 2018 Mac to create the installer with Mojave Patcher? If so, that's your issue. The awful "T2" chip screws with disk access, making my tool not work as intended.

Hi - any workaround for this yet? I just tried your patcher on a 2018 mbp and got the asr: couldn't personalize error. Threw me a curve while trying to create a .4 patcher stick.
[doublepost=1554743042][/doublepost]

I still preserve some old copies of MacOSInstall.app downloaded from a supported Mac in its time, I also have a full 10.14.2 installer. But really can't upload I have a slow upload speed. Anyway I guess from torrent sites if you find a 18D109 full installer compressed in dmg, it's enough valid, only condition it must be in the form "Install MacOS Mojave.app" and I'd say it's safe even from there.

Lessons learned. Used to keep copies of my sticks...got a little lazy lately. Thanks.

 

[jackluke]

Hi - any workaround for this yet? I just tried your patcher on a 2018 mbp and got the asr: couldn't personalize error. Threw me a curve while trying to create a .4 patcher stick.
[doublepost=1554743042][/doublepost]
Lessons learned. Used to keep copies of my sticks...got a little lazy lately. Thanks.

from a 2018 Mac this user reported a link-tip
you should set lower T2 Chip protection, but I don't own it so don't know well.

 

[0403979]

Ok. So wasn't just me My throttling never settled - incessant crash loops. Used to be we could download our old "purchased" installers...oh the good ole days...Not allowing us to download full installers is just Apple arrogance (and I have a paid up developer account to boot).
Where did you get the old full installer? I don't really trust these torrent sites (just sayin...)

I still preserve some old copies of MacOSInstall.app downloaded from a supported Mac in its time, I also have a full 10.14.2 installer. But really can't upload I have a slow upload speed. Anyway I guess from torrent sites if you find a 18D109 full installer compressed in dmg, it's enough valid, only condition it must be in the form "Install MacOS Mojave.app" and I'd say it's safe even from there.

I have all full Mojave installers and updates. I also have gigibit internet. I can hook you guys up with them if want? In fact, if anyone wants an installer then dm me. I already have 10.14.3 uploaded so I’ll get you the link.

 

[pkouame]

I have all full Mojave installers and updates. I also have gigibit internet. I can hook you guys up with them if want? In fact, if anyone wants an installer then dm me. I already have 10.14.3 uploaded so I’ll get you the link.

Cool man. Thx

I'll PM. I was actually creating a .4 patcher for @TimothyR734...

 

[0403979]

Cool man. Thx

I'll PM. I was actually creating a .4 patcher for @TimothyR734...

I added you to a dm with a link.

 

[timidpimpin]

@dosdude1

Did you completely miss my questions? I'm not trying to sound entitled here, but I am a donor, and it's frustrating to see you assist others but ignore me. Whether intentional or not.

 

[avz]

@dosdude1

Did you completely miss my questions? I'm not trying to sound entitled here, but I am a donor, and it's frustrating to see you assist others but ignore me. Whether intentional or not.

I am just curious whats your questions are? They must be very unique and difficult, as I am following this thread fairly closely and all the questions have been answered millions times over.

 

[Pinarek]

Try use the file attached (it's from stock .4 Mojave not patched) replace inside your .5 beta1 path: /S/L/PrivateFrameworks/

but take a copy of your current one somewhere.

This should allow to boot, however no OpenGL acceleration, only Framebuffer.

edit:
but reading your signature I guess no, for dual GPUs you need the stock GPUWrangler. Just try.
Another try, using your .5 GPUWrangler, try to delete the NDRVShim.kext from /S/L/E/.

@jackluke it was already successful with your attached file to boot, just no OpenGL support. With the 10.14.4 Final everything goes to OpenGL support, what changed Apple at the 10.14.5 Beta1?

Update: without ndrvshim.kext only standart Grafik 1024x768 this is not the right way think.
i will test the GPUwrangler from 10.14.4-Beta4

 

[jackluke]

@jackluke it was already successful with your attached file to boot, just no OpenGL support. With the 10.14.4 Final everything goes to OpenGL support, what changed Apple at the 10.14.5 Beta1?

Update: without ndrvshim.kext only standart Grafik 1024x768 this is not the right way think.
i will test the GPUwrangler from 10.14.4-Beta4

You need nvdrshim.kext because probably you patched the .5 beta1 with dosdude1 tool, instead I used all stock .5 kext / frameworks so that's why I can avoid shim .

Anyway something is changed on .5 beta1 and we are still inspecting, maybe .5 beta2 can reveal more when they release I guess tomorrow.

 

[Pinarek]

yes is right i have patched with dosdude1 tool.

 

[gosvamih]

You need nvdrshim.kext because probably you patched the .5 beta1 with dosdude1 tool, instead I used all stock .5 kext / frameworks so that's why I can avoid shim .

Anyway something is changed on .5 beta1 and we are still inspecting, maybe .5 beta2 can reveal more when they release I guess tomorrow.

.5 beta 2 already coming

 

[jackluke]

.5 beta 2 already coming
View attachment 831125

They released, ahead of time? Knowing them surely they have fix the OpenGL acceleration for our unsupported mac. {ironic mode: on}

 

[pkouame]

They released, ahead of time? Knowing them surely they have fix the OpenGL acceleration for our unsupported mac. {ironic mode: on}

Release Notes as sparse as usual. Just one entry for beta 2:

• Copy-protected video content plays back correctly on iMac Pro. (49174801)
  

 

[jowaju]

I am just curious whats your questions are? They must be very unique and difficult, as I am following this thread fairly closely and all the questions have been answered millions times over.

No they have not. I see the same pattern as AVZ, dosdude will respond to one question but leave the previous one or the following one unanswered, seemingly at random. I myself have asked several very specific questions about his 2011 MacBook Pro Firmware patcher tool (that he mentions himself in this thread) and have yet to receive any sort of response, either positive or negative. Again, not trying to be rude or pushy, just pointing it out.

 

[jackluke]

Release Notes as sparse as usual. Just one entry for beta 2:

• Copy-protected video content plays back correctly on iMac Pro. (49174801)

Updated and just needed to (remove telemetry.plugin for C2D) replace IOUSBFamily and IOUSBHostFamily kext to boot in GUI mode, all the kext and frameworks are .5 beta2 . Still no OpenGL acceleration but at least boot with minimum effort.

I forgot to replace AppleHDA as you can noticed from top menu bar.

From News app there is no more the tab "News+".

edit:
However really impressed how much is faster in booting and using w/o Acceleration from a C2D this new .5 beta2, even Safari more reactive.

redit:
FYI almost all the updated binaries (in kext and frameworks) have the apple "touch" compiled date April 6th.

 

[dosdude1]

Hi - any workaround for this yet? I just tried your patcher on a 2018 mbp and got the asr: couldn't personalize error. Threw me a curve while trying to create a .4 patcher stick.
[doublepost=1554743042][/doublepost]
Lessons learned. Used to keep copies of my sticks...got a little lazy lately. Thanks.

I don't have a 2018 T2-based Mac to use for testing at this point, but I am looking into the issue. It's probably something simple, but for now, if a user enables external drive booting support on the system, it can create the installer successfully.
[doublepost=1554761208][/doublepost]

@dosdude1

Did you completely miss my questions? I'm not trying to sound entitled here, but I am a donor, and it's frustrating to see you assist others but ignore me. Whether intentional or not.

If I missed your question, I really apologize... I get a TON of support messages and emails about my patches all the time, and it gets hard to keep track of them (especially with most of my time consumed by college work, which is why I haven't been as active on here as usual). I've also been doing testing and preparing an update for my tool for better 10.14.4 support. If you have a pressing question that others on here haven't/can't answer, you can always PM me.