Problem installing Mojave SecUpd2020-004Mojave on unsupported macbook 5,1

[Vesicular-blue]

I've managed to install Mojave 10.14.6 on my old macbook unibody 5,1 late 2008. The drive is HFS format as converting it to APFS with the translator was too slow. Hence it doesn't get automatic updates from Apple. So I manually download OS security updates and modify the distribution file after expanding the package.

This worked for previous updates up until this one. It appears to install, writing packages but fails after validating packages then says installation failed. I compared it with an older distribution file and noticed the packages were in a different order, tried again with them in the same order, but to no avail.

Any ideas?

 

[avz]

Erase, format as APFS and clean install. No issues on my MacBook5,1, it was made for Mojave.

 

[Vesicular-blue]

Erase, format as APFS and clean install. No issues on my MacBook5,1, it was made for Mojave.

I did an installation after formatting my drive to APFS and found it too slow running as the hardware doesn't recognise this format you install Dosdudes fix which must be a translator and acts at every read/write so the hardware thinks its HFS. A clean install only loads 10.14.6 minus the security updates of which there are a few...as far as I can tell but I may be incorrect here. I want it to run as HFS and install the updates as they come out. I was able to install all manually bar the current issue SecUpd2020-004Mojave...not sure why. Are you saying you have the current update running?

 

[avz]

Yes, I do. Your issue is common, even High Sierra hates doing updates on HFS.

 

[DeltaMac]

You would see very poor performance, particularly if formatted as APFS, if you are still using an HDD (spinning hard drive). OR, have you replaced that with an SSD?

 

[Vesicular-blue]

Yes, I do. Your issue is common, even High Sierra hates doing updates on HFS.

View attachment 937927

Sorry, I wasn't doubting you. I should have added I have a mechanical drive not SSD and dual boot with windows 10. There has to be something subtly different in the SecUpd 004 outside the distribution file contents that is causing a validation error. I can live with it but its annoying.
[automerge]1595856879[/automerge]

You would see very poor performance, particularly if formatted as APFS, if you are still using an HDD (spinning hard drive). OR, have you replaced that with an SSD?

Yes, I don't have an SSD so I notice the slowness.

 

[avz]

Sorry, I wasn't doubting you. I should have added I have a mechanical drive not SSD and dual boot with windows 10. There has to be something subtly different in the SecUpd 004 outside the distribution file contents that is causing a validation error. I can live with it but its annoying.

As I said you will get the same validation error on High Sierra, I believe it has to do with updating recovery, APFS recovery is updated differently and thus not producing this error.

 

[DeltaMac]

SSD would be a great upgrade.
Unfortunately, later macOS systems are just not well optimized for use with spinning hard drives.
SSD is absolutely the best upgrade that you can do for your aluminum MacBook.

 

[Vesicular-blue]

SSD would be a great upgrade.
Unfortunately, later macOS systems are just not well optimized for use with spinning hard drives.
SSD is absolutely the best upgrade that you can do for your aluminum MacBook.

I think you are right there... Not sure if it affect dual booting on such an old mac.

As I said you will get the same validation error on High Sierra, I believe it has to do with updating recovery, APFS recovery is updated differently and thus not producing this error.

Just tried it with the recovery update package commented out in the distribution file but same failure.... it writes files then puts out the failed banner.

 

[avz]

Just tried it with the recovery update package commented out in the distribution file but same failure.... it writes files then puts out the failed banner.

I would not trust your ability to "comment out" any installer packages from the distribution file. I know it has been done before successfully(read the High Sierra on unsupported Macs thread) but in my opinion it is a totally useless exercise as APFS gives you the ability to install updates natively.

 

[LegacyUser12]

Erase, format as APFS and clean install. No issues on my MacBook5,1, it was made for Mojave.

I think you've successfully convinced me to make the jump on trying Mojave (and/or Catalina) on my YeOldeMacbook5,1 .
I just partitioned out a 1tb external to have an APFS partition (container?) of 250gb. I've piddled with enough other unrelated technology issues for the night though and the official party will have to start tomorrow evening.

 

[avz]

I think you've successfully convinced me to make the jump on trying Mojave (and/or Catalina) on my YeOldeMacbook5,1 .
I just partitioned out a 1tb external to have an APFS partition (container?) of 250gb. I've piddled with enough other unrelated technology issues for the night though and the official party will have to start tomorrow evening.

Yes, if your external drive is an SSD, you should be fine. I would start with the drive formatted as HFS+, then partition the drive and create the Mojave partition, then format your Mojave partition as APFS and install Mojave. If you decide to dedicate the whole drive to Mojave, you can just format the whole drive as APFS.

 

[M3Stang]

Did you install the APFS patch or the APFS ROM patch. About to go through this with a 17” MBP 4,1 with HDD trying to see what to expect.

 

[avz]

I did the APFS ROM patch.

 

[LegacyUser12]

Yes, if your external drive is an SSD, you should be fine. I would start with the drive formatted as HFS+, then partition the drive and create the Mojave partition, then format your Mojave partition as APFS and install Mojave. If you decide to dedicate the whole drive to Mojave, you can just format the whole drive as APFS.

My external is not, its a 1tb LaCie HDD. My internal is a Crucial SSD and I have a Samsung SSD somewhere I haven't opened yet I could use as an external.

 

[LegacyUser12]

Did you install the APFS patch or the APFS ROM patch. About to go through this with a 17” MBP 4,1 with HDD trying to see what to expect.

I actually have a want for that setup. Is that your everyday?

 

[M3Stang]

I actually have a want for that setup. Is that your everyday?

No I actually just bought it a couple weeks ago just to have it. I collect mostly PowerBooks but some earlier MBPs. I did Mojave on some newer mid 2010 MBP but I did not need to mess with rom since they run High Sierra. If this ends up being too involved I’ll just use this one with el cap until I get bored with it lol. Def do not want to do the rom patch but it’s inconclusive on whether or not I NEED to do it or if it’s optional. The APFS patch is ok since it’s on the HD. I wanted one of those 17” when they were new finally got this one mint under $250 so happy about that.

 

[LegacyUser12]

No I actually just bought it a couple weeks ago just to have it. I collect mostly PowerBooks but some earlier MBPs. I did Mojave on some newer mid 2010 MBP but I did not need to mess with rom since they run High Sierra. If this ends up being too involved I’ll just use this one with el cap until I get bored with it lol. Def do not want to do the rom patch but it’s inconclusive on whether or not I NEED to do it or if it’s optional. The APFS patch is ok since it’s on the HD. I wanted one of those 17” when they were new finally got this one mint under $250 so happy about that.

ditto. A friend got the 17" when they first came out and my envy was intense over the screen real estate. As my eyes age into my 30's I'm more dissatisfied with the 13" so I'm actively looking for a used/refurb 15" MBP.
This past December my favorite independent computer shop had a MBP 8,2 Early 2011 i7 2.0 15" for $600 but when we connected it to a plain external display it crashed repeatedly and I wasn't feeling the vibes of what the internets had to say about that model's GPU set up.
I'm wary of any 2011-2013 MBP 15" GPU issues. Seems to be 2014 is the MBP 15" sweet spot era and then we know after 2015 the insides are not to be played with anymore.
What say you of the 15"'s that'll be forward compatible for at least another 5ish years?

 

[M3Stang]

ditto. A friend got the 17" when they first came out and my envy was intense over the screen real estate. As my eyes age into my 30's I'm more dissatisfied with the 13" so I'm actively looking for a used/refurb 15" MBP.
This past December my favorite independent computer shop had a MBP 8,2 Early 2011 i7 2.0 15" for $600 but when we connected it to a plain external display it crashed repeatedly and I wasn't feeling the vibes of what the internets had to say about that model's GPU set up.
I'm wary of any 2011-2013 MBP 15" GPU issues. Seems to be 2014 is the MBP 15" sweet spot era and then we know after 2015 the insides are not to be played with anymore.
What say you of the 15"'s that'll be forward compatible for at least another 5ish years?

I would say its possible if the community keeps the patching going for sure. On the other hand, Apple could pull a PPC to Intel transition and drop Intel Macs after Big Sur, which I doubt since back then OSes were like every 2-3 years where as now it is yearly. So with that we should maybe see 11.1 and 11.2 and maybe 11.3 at least working on Intel Macs.