Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 10.14 Mojave on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
K two

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
RK78 said:
Used SK 1.15 from the HFS+(HDD) volume, which updated Safari to the 14.0.2. But it didn't run the 2020-007 - not that I had high hopes that it would. So I'm supposing that it would be necessary, as usual, to boot to my APFS formatted volume (also HDD on external), in order to run the SecUpd, which clearly SK at the HFS+ volume wasn't able to see. Looks like it basically automates (for want of a better term) and runs whatever update is available normally. In that regard, while it was running I noticed that softwareupdated was running, as well as the native Mac installer application - what I would expect without SK.

One of my questions in my OP was whether SK would be able to run a standalone SecUpd full installer dmg, either from the HFS+ or APFS volume? You seemed to answer that question with an overall positive, but since SK appears to depend on the Mac native update/SU processes, I don't really understand how SK would be able to begin to access a SecUpdate standalone installer dmg (or package?), which would be sitting on the Desktop.

So back to that first question, already asked at https://forums.macrumors.com/thread...unsupported-macs-thread.2121473/post-29390944 which was, "Does this mean SilentKnight will be able to directly install a standalone SecUpd without needing to modify the distribution file, or will it only be able to install what is already available from SU on an APFS formatted volume, as per the usual caveats?"

In other words, it's nice to have all this automated, but wonder if it actually changes anything basic to the way updates are run?
Click to expand...
Never tried to install the stand-alone installer, only OTA w/SK1.8.
 
R

RK78

macrumors 6502
Oct 24, 2019
270
92
K two said:
Never tried to install the stand-alone installer, only OTA w/SK1.8.
Click to expand...
Yeah, don't see how using SK would change that. Another small question: you said to quit SK before the restart. When I saw that all updates had been installed, from SK, I quit SK, and didn't wait for the restart notice. After running the patcher twice, everything seems OK on the APFS formatted volume, but before I ran the patcher, seemed to get into a bit of trouble - hung up on "Setting up your Mac." So did a hard shutdown followed by a regular restart, then when it KPd, which is normal, I ran the patcher twice - force cache reboot.

So I'm thinking that I should have waited until the actual restart notice appeared before quitting SK, not just when SK showed all updates installed?
 
  • Like
Reactions: K two
K two

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
RK78 said:
Yeah, don't see how using SK would change that. Another small question: you said to quit SK before the restart. When I saw that all updates had been installed, from SK, I quit SK, and didn't wait for the restart notice. After running the patcher twice, everything seems OK on the APFS formatted volume, but before I ran the patcher, seemed to get into a bit of trouble - hung up on "Setting up your Mac." So did a hard shutdown followed by a regular restart, then when it KPd, which is normal, I ran the patcher twice - force cache reboot.

So I'm thinking that I should have waited until the actual restart notice appeared before quitting SK, not just when SK showed all updates installed?
Click to expand...
Force cache rebuild - yes.
 
R

RK78

macrumors 6502
Oct 24, 2019
270
92
K two said:
Force cache rebuild - yes.
Click to expand...
Thanks, but the question is exactly when to quit SK: when it shows all updates installed, or when the restart notice appears?* I quit SK when it showed all updates installed, and never saw the restart notice, nor did an automatic restart occur - had to do a manual restart to complete the installation. By closing SK before seeing the restart notice, did I prevent the automatic restart?

*EDIT: don't actually remember right now if a restart notice should appear with Mojave APFS run without SK, or if the restart just happens automatically, without giving any notice.
 
Last edited:
  • Like
Reactions: K two
alphascorp

alphascorp

macrumors 6502
Jul 16, 2018
343
635
Brest, France
Hi all,

Successfully installed SecUpd2020-007Mojave (18G7016) on MBP5,3.

After, installing this update, needed reboot on USB Key and re-patch with Dosdude1 Patcher with cache rebuild and reinstall appleGVA, softwareupdate.framework, HIToolbox Siri.app and SiriUI.framework (for Siri waveform)

Capture d’écran 2020-12-15 à 23.12.47.png
 
  • Like
Reactions: MTBnBeer, Dayo and K two
W

wire_

macrumors member
Nov 26, 2019
33
26
Trouble with Epson V500 scanner and X-Rite i1 Display Pro Plus

Mac Pro 3.1

I can use both of these devices with Apple and FLOSS SW, but the vendor SW fails to operate them

For example, EpsonScan reports "Communication Error"

X-Rite i1 Profiler can't see colorimeter.

But Apple Image Capture works the scanner, and so does Vuescan

And Argyll CMS works the colorimeter

I submitted a support request to Epson and they are at a loss

Is there something incomplete about legacy USB support that would affect closed source SW but not freer SW?

Thanks in advance
/wire
 
  • Like
Reactions: Pralaya
W

wire_

macrumors member
Nov 26, 2019
33
26
BTW—The colorimeter was accessible X-Rite i1 Profiler as recently as 10.14.6 second security update, and EpsonScan would sometimes see the scanner after a reboot then error later. But since this most recent security update both don't work with their vendors code. But 3rd party code still works with these devices.

Another strange thing is that the web browser extension Ublock Origin (firefox) control panel doesn't render on this Mac GTX-680. It just shows blank. I went through complete FF reset but no joy. It's the only SW I use on this Mac Pro that has graphics trouble. Other similar vintage Macs with Mojave and Firefox Ublock works, like 2008 MBP and 2009 Mini.
 
  • Like
Reactions: K two
K two

K two

macrumors 68020
Dec 6, 2018
2,314
3,187
North America
RK78 said:
Yeah, don't see how using SK would change that. Another small question: you said to quit SK before the restart. When I saw that all updates had been installed, from SK, I quit SK, and didn't wait for the restart notice. After running the patcher twice, everything seems OK on the APFS formatted volume, but before I ran the patcher, seemed to get into a bit of trouble - hung up on "Setting up your Mac." So did a hard shutdown followed by a regular restart, then when it KPd, which is normal, I ran the patcher twice - force cache reboot.

So I'm thinking that I should have waited until the actual restart notice appeared before quitting SK, not just when SK showed all updates installed?
Click to expand...
Not quitting SK prevented the auto restart. If I recall correctly? If I had another Mojave install, I'd make notes. We have six Mini3,1 between family and the office, Yucca Valley is the sole Mojave box. One on High Sierra, the remainder on Catalina.
 
R

RK78

macrumors 6502
Oct 24, 2019
270
92
K two said:
Not quitting SK prevented the auto restart. If I recall correctly? If I had another Mojave install, I'd make notes. We have six Mini3,1 between family and the office, Yucca Valley is the sole Mojave box. One on High Sierra, the remainder on Catalina.
Click to expand...
Please read again. I did quit SK, when it showed all updates installed. But the question was did I quit prematurely, which then prevented the auto restart?

About to try this again, but on Mini 4,1. Will see how it goes this time.
 
  • Like
Reactions: K two
Dayo

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
RK78 said:
In other words, it's nice to have all this automated, but wonder if it actually changes anything basic to the way updates are run?
Click to expand...
I have a preference for amending the distribution file manually or using a script I wrote: FixMacUpdates.sh

Usage:
Bash: 
###
# USAGE:
# 1. Make the script executable in Terminal by typing: chmod +x '/path/to/FixMacUpdates.sh'
#  - To get the path, drag the 'FixMacUpdates.sh' file into Terminal after typing: chmod +x
# 2. Download and mount the Apple Update dmg file
# 3. Drag the pkg file to your desktop from the dmg
# 4. Drag the 'FixMacUpdates.sh' file into Terminal
# 5. Leave a space after the command that appears and drag the pkg file into Terminal and press 'Enter'
#  - You can press 'Enter' directly after 'FixMacUpdates.sh' if you first rename the pkg file as 'SecUpd.pkg'
###
 
Last edited:
  • Like
  • Love
Reactions: vasigio and K two
L Caputo

L Caputo

macrumors 6502
Aug 11, 2015
404
279
Dayo said:
I have a preference for amending the distribution file manually or using a script I wrote: FixMacUpdates.sh

Usage:
Bash: 
###
# USAGE:
# 1. Download and mount the Apple Update File
# 2. Drag the pkg file to your desktop from the dmg
# 3. Drag the 'FixMacUpdates.sh' file into Terminal
# 4. Type a space, drag the pkg file into Terminal and press 'Enter'
#  - You can press 'Enter' directly after typing 'FixMacUpdates.sh' if you first rename the pkg file to 'SecUpd.pkg'
###
Click to expand...
Excellent thank you very much, will use this in the future rather than manually modifying.
 
TzunamiOSX

TzunamiOSX

macrumors 65816
Oct 4, 2009
1,057
435
Germany
Hi,
i have a MacBook 5,1 here and want to run Mojave on it.

What is the better solution?

HFS+ or APFS

At the Moment i have updated from El Capitan to Mojave with HFS+ (18G103). After this i have modified the SecUpd2019-001Mojave (18G1012) and and installed it too.

Now i have Mojave running on 18G1012

Because the updates are not displayed, what is the order of the updates? Suplemental update for example.

Or better delete and using APFS?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom