macOS 10.14 Mojave on Unsupported Macs Thread

[dictoresno]

Yep, that's actually a known hardware issue with that system. To repair it, you'll need to replace a capacitor on the GPU framebuffer power rail (C6950), and that will get the machine running without issue. The reason this happens when using the Photos app is because the Photos app makes the machine switch to its dedicated GPU. I've made a video of that repair on my YouTube channel:

jeeeeez thanks for that info. this isn't my main machine so it may not be a dealbreaker at this point. thanks so much for the info!

is this due to hardware/software compatibility or is this due to something physically wrong with my MBP?

If battery life is not of a concern, any way to prevent this from switching to the dedicated video card as a temp fix? And so this basically is a true hardware issue that would occur even if I revert the MBP to normal macOS software?


EDIT: I did some research in a huge thread dedicated to this issue. before I decide to do the capacitor replacement, I decided to give gfxCardStatus app a try. I found that by manually forcing to integrated graphics prior to opening the photos app, allows the app to be used and doesn't cause a kernel panic. once I close photos app, the computer switches itself back to the dedicated card without issue.

 

[XMPL]

Trying a different USB drive might solve your problem, as not all USB drives are created equal when it comes to booting on Macs.

yes, its about USB stcik, i try it with another USB stick, its done Mojave on Macbook 5,1 & Macbook 7,1. Thanks

 

[NiloGlock]

Just use Offline methods:
1. Download macOS Mojave 10.14.3 Supplemental Update.
2. Extract *.pkg (from *.dmg), assumed it' s located on ~/Downloads
3. Edit "Distribution" file for forcing installation on HFS+, Terminal:

Spoiler

$ cd ~/Downloads
$ pkgutil --expand [PackageName].pkg NewFolder
$ cd NewFolder && ls
$ nano edit Distribution
// or using your fav. xml editor, Find for:

function FileSystem1(prefix) {
    if (my.target.filesystem && my.target.filesystem.type == 'hfs') {
        return false;
    }
    return true;
}

// change to:

function FileSystem1(prefix) {
    if (my.target.filesystem && my.target.filesystem.type == 'hfs') {
        return true;
    }
    return false;
}

// Save.
$ cd ~/Downloads
$ pkgutil --flatten NewFolder [PackageNameHFS].pkg

4. Try updating with your new modified [PackageNameHFS].pkg

I've opened the file but the code, without editing, is

function FileSystem1(prefix) {
    if (my.target.filesystem && my.target.filesystem.type == 'hfs') {
        return true;
    }
    return false;
}

What's wrong?

 

[jackluke]

@olad, @Badruzeus I done another test, re-installing and overwriting the main drive using the full 10.14.3 (with 18D109 included) installer RAM saturation doesn't occur more, so I guess the issue is related only when using the combo/delta pkgs with patched "Distribution". This is a good hope when final 10.14.4 will be released that should include again the OpenGL init function for legacy machines, AAPL can't drop OpenGL feature versus Metal since many popular third-party apps are still based on that feature.

 

[16v]

Got my mbp 2011 13" today.
Tried to install mojave witch dosdudes stick.

Cant install, no install packages found...
Whats wrong?

 

[jackluke]

Got my mbp 2011 13" today.
Tried to install mojave witch dosdudes stick.

Cant install, no install packages found...
Whats wrong?

Try adjust date/time booting from any Recovery or USB Installer.
Launch Terminal and type:
date -u 0215122019

 

[16v]

I try internet recovery right now.

And what i see: usb is named os x basic install or somewhat like this, and when running installer usb is called untitled 1.

Maybe this is the issue?

But i try what you said. Thank you.

 

[jackluke]

I try internet recovery right now.

And what i see: usb is named os x basic install or somewhat like this, and when running installer usb is called untitled 1.

Maybe this is the issue?

But i try what you said. Thank you.

I don't think, once I got a similar issue when installing Mavericks from an USB Installer, fixed setting date/time.

 

[16v]

I'll try it...

But it has to wait... only a few hours...

 

[jackluke]

I'll try it...

But it has to wait... only a few hours...

Don't worry it should work, you have done the internet recovery restoring your macbook to its factory condition, sometimes Installer crash naturally or maybe it's a bit defective internal drive, but you don't need that Lion installation, you can hold power button and turn off, then relaunch the most recent USB Installer, trying first that date/time trick.

edit:
Oh wait, you own a MBP 2011, so better to install HighSierra that will bring you native APFS firmware support.

 

[Pralaya]

I've opened the file but the code, without editing, is

function FileSystem1(prefix) {
    if (my.target.filesystem && my.target.filesystem.type == 'hfs') {
        return true;
    }
    return false;
}

What's wrong?

Badruzeus gave you just the wrong info, like to me before.
Thanks to L Caputo, I was able to install it.
IT MUST BE LIKE THIS:


L Caputo said: ↑
If you want to try again, this works.

Download the update.

Open the update.

Move the update.pkg to Desktop.


Open Terminal.


Enter pkgutil --expand now drag and drop the .pkg from the Desktop into the Terminal window and type after a space ~/Desktop/Expanded hit Return and wait, this takes a little while.


Open Expanded folder and then open Distribution file in Text Edit


Scroll down to the line


function InstallationCheck(prefix) {


enter the text return true; so it looks like this


function InstallationCheck(prefix) {return true;

Now save the changes


If you are trying to install the update to an HFS+ disk then there is another alteration you can make, before flattening and creating the package.

Again in the Distribution file scroll down to


function VolumeCheck(prefix) {


again enter return true; after the bracket, so it looks like this,


function VolumeCheck(prefix) {return true;


Save changes


Go back to Terminal enter pkgutil --flatten ~/Desktop/Expanded ~/Desktop/Modified.pkg

Using the .pkg extension is crucial.


One thing to note is if your Mac like mine has different OS's on it on other drives this method will tell you that all drives are able to install the update, DO NOT INSTALL ON ANY DISK/ PARTITION, ONLY INSTALL TO A DISK/ PARTITION THAT HAS MOJAVE ON IT. Select your disk wisely, and double check.

 

[olad]

@olad, @Badruzeus I done another test, re-installing and overwriting the main drive using the full 10.14.3 (with 18D109 included) installer RAM saturation doesn't occur more, so I guess the issue is related only when using the combo/delta pkgs with patched "Distribution". This is a good hope when final 10.14.4 will be released that should include again the OpenGL init function for legacy machines, AAPL can't drop OpenGL feature versus Metal since many popular third-party apps are still based on that feature.

@jackluke... it is near the final release of 10.14.4 enough to wait a bit for it. but thanks.

 

[avz]

I am happy to report that Mojave 10.14.3(18D109) is working great with only 2GB of RAM. Still fast and snappy(open Safari, Firefox(YouTube), Apple Mail, Skype, Activity Monitor, Coconut Battery).
Since I dual boot with High Sierra it would be interesting to see if High Sierra is up for the 2GB RAM challenge.

 

[16v]

Don't worry it should work, you have done the internet recovery restoring your macbook to its factory condition, sometimes Installer crash naturally or maybe it's a bit defective internal drive, but you don't need that Lion installation, you can hold power button and turn off, then relaunch the most recent USB Installer, trying first that date/time trick.

edit:
Oh wait, you own a MBP 2011, so better to install HighSierra that will bring you native APFS firmware support.

I installed this Lion through internet recovery and then tried to install mojave.
But there seems also a problem.
I cant watched the progress cause i had to work.
I tried date in terminal and it was set correct.

I use a 120gb hdd. For testing only.
Used extended journaled format - no apfs yet.
Will buy a ssd then i use apfs.

O.k. i try this date thing first, then hugh sierra.

 

[Badruzeus]

Badruzeus gave you just the wrong info, like to me before.
Thanks to L Caputo, I was able to install it.

Yeah, I could be wrong. I realized that on prev. post; was from already edited "Distribution" file; that's why.
Thanks for correction anyway.

 

[K two]

In-place installed 18D109 on top of 18D42 with the new 14.3.3 installer on a Mini3,1 HFS+ SSD. Had to re-install the post-install patches and force cache rebuild three iterations to get the Mini to boot all the way through. Also had to re-enter DNS, IPv6 settings in the Network CP and the machine name in the Sharing CP. Everything else, intact.

The good news is the machine runs a bit cooler with no high CPU usage or other issues reported from Supplemental updated 18D109 versions. Well worth the tiny hassle. YMMV

If APFS use the Update CP.

 

[olad]

I am happy to report that Mojave 10.14.3(18D109) is working great with only 2GB of RAM. Still fast and snappy(open Safari, Firefox(YouTube), Apple Mail, Skype, Activity Monitor, Coconut Battery).

2GB RAM? What are the remaining specifications of the machine?

 

[16v]

Don't worry it should work, you have done the internet recovery restoring your macbook to its factory condition, sometimes Installer crash naturally or maybe it's a bit defective internal drive, but you don't need that Lion installation, you can hold power button and turn off, then relaunch the most recent USB Installer, trying first that date/time trick.

edit:
Oh wait, you own a MBP 2011, so better to install HighSierra that will bring you native APFS firmware support.

No.
That date thing didnt work...

How can i check hdd in terminal?

 

[jackluke]

In-place installed 18D109 on top of 18D42 with the new 14.3.3 installer on a Mini3,1 HFS+ SSD. Had to re-install the post-install patches and force cache rebuild three iterations to get the Mini to boot all the way through. Also had to re-enter DNS, IPv6 settings in the Network CP and the machine name in the Sharing CP. Everything else, intact.

The good news is the machine runs a bit cooler with no high CPU usage or other issues reported from Supplemental updated 18D109 versions. Well worth the tiny hassle. YMMV

If APFS use the Update CP.

Agree, on the top of the current build a full installation refresh is the best choice to avoid issues, for reference the main issue encountered with combo/delta in-place update was only addressed to full RAM Usage/Saturation, cpu was ok.
[doublepost=1550305486][/doublepost]

No.
That date thing didnt work...

How can i check hdd in terminal?

fsck -fy
or use DiskUtility's First Aid.
But probably you need an official machine firmware update, do-able with HighSierra, and if you intend to upgrade to HighSierra through AppleStore (better choice to me), you require at least Mountain Lion 10.8 or later.

So your steps should be:
- Install Lion from your Internet Recovery
- Upgrade Lion to 10.7.5 through AppStore (no login required)
- Upgrade Lion to El Capitan through AppStore
- Upgrade El Capitan to High Sierra through AppStore

Then you will have official APFS firmware.

 

[avz]

2GB RAM? What are the remaining specifications of the machine?

It is in my signature, MacBook5,1. High Sierra on this machine is doing great with 2GB RAM as well.
I am wondering is it just an SSD that makes all the difference, or is it SSD+APFS?

 

[16v]

O.k. mojave is running now.

What do you mean saying native apfs support?

Efi update?
How to check latest update?

 

[jackluke]

O.k. mojave is running now.

What do you mean saying native apfs support?

Efi update?
How to check latest update?

From Mojave Terminal:
system_profiler SPHardwareDataType

Check BootROM and SMC version and compare somewhere on online search database if those are latest version for your MacbookPRO model. In that case you can install or convert Mojave to APFS and will work natively.

 

[moppy]

Hi everyone, is there anyone with MacBook 5,2 being able to have iSight working? I own early 2009 MacBook White already up and running with the latest 10.14.3 (clean install) but missing the iSight, I already tried manually replacing IOUSB*.kext from High Sierra but it's not working too. I know there is a note in the first post that iSight might work and might not, but maybe there is some steps that I can give it a try to see if my iSight could work. TiA

 

[16v]

From Mojave Terminal:
system_profiler SPHardwareDataType

Check BootROM and SMC version and compare somewhere on online search database if those are latest version for your MacbookPRO model. In that case you can install or convert Mojave to APFS and will work natively.

There is a small problem...
It is a late 2011 13" but smc is from early 2011... (what i found on apple website)

Im not at home right now
But smc is 1.69f99 if i remember and on apple website latest for late 2011 is 1.69f98!

Native means i dont need apfs rom patcher?

 

[jackluke]

There is a small problem...
It is a late 2011 13" but smc is from early 2011... (what i found on apple website)

Im not at home right now
But smc is 1.69f99 if i remember and on apple website latest for late 2011 is 1.69f98!

Native means i dont need apfs rom patcher?

Yes, you don't need rom patcher, and I guess your SMC is ok, so you can install or convert your Mojave in APFS.

There are also standalone efi bootrom update for example: https://support.apple.com/kb/DL1499
but you don't need, you already have the latest update.

Here is the official database: https://support.apple.com/en-us/HT201518