macOS High Sierra (10.13) Unsupported Macs Thread

[humanafterall]

I've always been fed up of getting the "An error occurred while running scripts from the package “XXXX.RecoveryHDUpdate.pkg”, so I followed my own suggestion of doctoring the script(s) so that at least the installation could run to completion and thereby show up in the install.log.

So, basically I followed the instructions in the OP for installing Security Updates. Downloaded the update manually. Added my board id and removed my model number as instructed. I also modified the replaceRecovery bash script - which is the one that fails (at the hdutil attach command). I commented out everything between creating and deleting the temporary mount point (which it creates in /var/folders). I know I could have commented out everything but I decided to only comment out the part that was causing the failure. I also edited the echo command so that I knew it was running my modified script. Repackaged per the instructions.

Suffice to say, the update ran to completion (no error report) and I got the Installation Successful dialog. About This Mac now reports build 17G4015. The security update also shows in the Installations list in System Report. The App Store doesn't show the security update as recently installed, but it also doesn't show the update as available anymore.

The other thing I did (and I don't know if this was strictly necessary) was to mount the Recovery partition and manually modify the System Version therein to say 17G4015.

No problems so far. I haven't tried booting into the Recovery partition yet but don't anticipate any problems.

Did you run dosdude1's Post Install Scripts again or rebooted without issues or performance lags after the update installation?

Could you please give some details on which files and what you modified:
I also modified the replaceRecovery bash script - which is the one that fails (at the hdutil attach command). I commented out everything between creating and deleting the temporary mount point (which it creates in /var/folders)

 

[mrploppy]

No, haven't run @dosdude1's post-install scripts again. Don't know if I should? I just rebooted and haven't noticed any issues yet. Having said that, the Patch Updater shows that I have various patches installed - one of which is Night Shift, but I don't see the Night Shift tab in the Displays preference pane. I don't really use Night Shift but maybe I should re-apply them all? Willing to take advice here.

You need to follow the instructions in section Security And OS Standalone Updates in the OP. That'll tell you how to add your board id, and remove your model from the Unsupported list. Being Unix-literate, I didn't faff around using Text Wrangler of BBedit - I just edited in place using old-skool vi.

When you've expanded the pkg, you'll find the replaceRecovery script in directory
SecUpd2018-003HighSierra.RecoveryHDUpdate.pkg/Scripts/

Again, I edited this with vi, but you can use your editor of choice. I commented out (effectively deleted) a bunch of lines in that script, so I was only left with

#!/bin/bash

set -e

TARGET="$2"

echo "Attempting to create temporary mount point"
MOUNT_POINT="$(/usr/bin/mktemp -d)"

echo "But NOT ... Attempting mount of ${PACKAGE_PATH} to ${MOUNT_POINT}"

echo "And NOT ... Probing Target Volume: ${TARGET}"

echo "Delete ${MOUNT_POINT}"
/bin/rm -rf "${MOUNT_POINT}"

I changed a couple of those echo commands so that I'd know for sure that it had executed the modified script - even though it actually does nothing.

Repackage and run.

 

[jbarley]

If you re-apply the nightshift patch there is a very good chance it will break some of your System Preference panels, namely the Trackpad and Keyboard panels.
If you'd like to test this, first make sure you have a known bootable backup of your system just in case you need to restore back to a working system.

 

[mrploppy]

If you re-apply the nightshift patch there is a very good chance it will break some of your System Preference panels, namely the Trackpad and Keyboard panels.
If you'd like to test this, first make sure you a a known bootable backup of your system just in case you need to restore back to a working system.

OK, thanks for the advice. I'll probably leave Night Shift as it is. Do you think I need to re-apply the others? I think what may have happened is that I had the Night Shift patch installed at some point (maybe when I did the full install of 10.13.5) but when I installed 10.13.6 I didn't choose Night Shift as one of the post-installs. I don't really know if that leaves the previous one "installed" but "inactive". Just guessing here. Is there advice anywhere about whether we need to re-install patches after a security update?

 

[humanafterall]

No, haven't run @dosdude1's post-install scripts again. Don't know if I should? I just rebooted and haven't noticed any issues yet. Having said that, the Patch Updater shows that I have various patches installed - one of which is Night Shift, but I don't see the Night Shift tab in the Displays preference pane. I don't really use Night Shift but maybe I should re-apply them all? Willing to take advice here.

You need to follow the instructions in section Security And OS Standalone Updates in the OP. That'll tell you how to add your board id, and remove your model from the Unsupported list. Being Unix-literate, I didn't faff around using Text Wrangler of BBedit - I just edited in place using old-skool vi.

When you've expanded the pkg, you'll find the replaceRecovery script in directory
SecUpd2018-003HighSierra.RecoveryHDUpdate.pkg/Scripts/

Again, I edited this with vi, but you can use your editor of choice. I commented out (effectively deleted) a bunch of lines in that script, so I was only left with

#!/bin/bash

set -e

TARGET="$2"

echo "Attempting to create temporary mount point"
MOUNT_POINT="$(/usr/bin/mktemp -d)"

echo "But NOT ... Attempting mount of ${PACKAGE_PATH} to ${MOUNT_POINT}"

echo "And NOT ... Probing Target Volume: ${TARGET}"

echo "Delete ${MOUNT_POINT}"
/bin/rm -rf "${MOUNT_POINT}"

I changed a couple of those echo commands so that I'd know for sure that it had executed the modified script - even though it actually does nothing.

Repackage and run.

Many thanks for all the details!

 

[humanafterall]

No, haven't run @dosdude1's post-install scripts again. Don't know if I should? I just rebooted and haven't noticed any issues yet. Having said that, the Patch Updater shows that I have various patches installed - one of which is Night Shift, but I don't see the Night Shift tab in the Displays preference pane. I don't really use Night Shift but maybe I should re-apply them all? Willing to take advice here.

You need to follow the instructions in section Security And OS Standalone Updates in the OP. That'll tell you how to add your board id, and remove your model from the Unsupported list. Being Unix-literate, I didn't faff around using Text Wrangler of BBedit - I just edited in place using old-skool vi.

When you've expanded the pkg, you'll find the replaceRecovery script in directory
SecUpd2018-003HighSierra.RecoveryHDUpdate.pkg/Scripts/

Again, I edited this with vi, but you can use your editor of choice. I commented out (effectively deleted) a bunch of lines in that script, so I was only left with

#!/bin/bash

set -e

TARGET="$2"

echo "Attempting to create temporary mount point"
MOUNT_POINT="$(/usr/bin/mktemp -d)"

echo "But NOT ... Attempting mount of ${PACKAGE_PATH} to ${MOUNT_POINT}"

echo "And NOT ... Probing Target Volume: ${TARGET}"

echo "Delete ${MOUNT_POINT}"
/bin/rm -rf "${MOUNT_POINT}"

I changed a couple of those echo commands so that I'd know for sure that it had executed the modified script - even though it actually does nothing.

Repackage and run.

Followed all steps to doctor the scripts, security update 2018-003 installed without issues or error message.

But again upon restart the boot screen is stuck with a loading spinner over and over and not progressing (screenshot attached).

Only way is to hard shut down, reinstall @dosdude1 post install scripts, then it boots normally but graphics performance is really awefull again. The security update might mess with AMD related kexts or something like that?

Mac Pro 3,1
ATI Radeon HD5770

 

[mrploppy]

Followed all steps to doctor the scripts, security update 2018-003 installed without issues or error message.

But again upon restart the boot screen is stuck with a loading spinner over and over and not progressing (screenshot attached).

Only way is to hard shut down, boot again, it boots normally but with same bad graphics performance even if I reinstall @dosdude1 post install scripts. The security update might mess with AMD related kexts or something like that?

Mac Pro 3,1
ATI Radeon HD5770

Can't really help you there I'm afraid. All I can say is that on reboot my progress bar sticks in that same area for a long time before eventually finishing. I guess it's only stuck for a few minutes but it seems endless when I'm watching it. I don't think I get the spinner though. How long do you leave it before hard shut down?

 

[humanafterall]

Can't really help you there I'm afraid. All I can say is that on reboot my progress bar sticks in that same area for a long time before eventually finishing. I guess it's only stuck for a few minutes but it seems endless when I'm watching it. I don't think I get the spinner though. How long do you leave it before hard shut down?

Longest it's been for 40 minutes before I do the hard shut down. When I do a complete reinstall of high sierra 10.13.6 with dosdude1 patch there is no issue. Maybe I'll have to wait for 10.13.7 if there will be one, or a new Mac perhaps Many thanks for all the help!

 

[mrploppy]

Longest it's been for 40 minutes before I do the hard shut down. When I do a complete reinstall of high sierra 10.13.6 with dosdude1 patch there is no issue. Maybe I'll have to wait for 10.13.7 if there will be one, or a new Mac perhaps Many thanks for all the help!

Ouch. 40 mins is a long time. I'd have given up by then also.

From what I understand there won't ever be a 10.13.7. However, I believe someone said if you download the full 10.13.6 now, it'll include the security updates, so maybe that's an option for you. Would need to confirm that though.

 

[dosdude1]

Followed all steps to doctor the scripts, security update 2018-003 installed without issues or error message.

But again upon restart the boot screen is stuck with a loading spinner over and over and not progressing (screenshot attached).

Only way is to hard shut down, reinstall @dosdude1 post install scripts, then it boots normally but graphics performance is really awefull again. The security update might mess with AMD related kexts or something like that?

Mac Pro 3,1
ATI Radeon HD5770

That's an issue with your video card... You need to verify that you apply the AMD Radeon HD 5xxx, 6xxx, 7xxx series patch using the post-install tool, and force rebuild caches.

 

[humanafterall]

That's an issue with your video card... You need to verify that you apply the AMD Radeon HD 5xxx, 6xxx, 7xxx series patch using the post-install tool, and force rebuild caches.

Many thanks for your reply!
I have tried to apply the AMD patch with the post-install tool after the security update, force rebuild caches and reboot but graphics performance is still very bad. I also tried to run sudo kextcache -system-prelinked-kernel as you mention in the instructions of the patch tool but without any results.

If I donwload High Sierra 10.13.6 now (thanks @mrploppy for the suggestion) will it include the security update? So I can install again via the patch tool?

 

[Lahmy88]

Hi guys,

On behalf of my Aunty, I had upgraded her Mid-2009 13” MBP to High Sierra using this patch process which went quite well

Problem I now have is I’ve just migrated her data over to her new 2018 13” MBP (with Mojave installed) using her Time Machine backup and whilst browsing for things to make sure are all good (initialise Photos & iTunes, activate Office licence again etc.), I noticed the Patch Updater app in the Utilities folder and reminded me of where this data migration has come from and what it still contains.

What I would like to know is, what ‘under the hood’ operations do I have to do to remove any of the patch associated software and it’s potential effect on this new Mac (that obviously doesn’t need a patch to have the latest macOS)? Or is it just a matter of dropping the Patch Updater in trash and that’s it?

Edit: Also realised it may be responsible for the “SIP Enabled” dialog box showing up every boot?

 

[Zefram]

Hello,

I own a Macbook pro 2010 (7.1) which is normaly compatible with High Sierra. But I have a soft SSD raid in this Mac (HFS) and Apple removed the possibility to boot from raid volume with High Sierra.
So, impossible to install High Sierra on my raid.
Thanks to the dosdude1's patch I have installed High Sierra on this Mac.

But now I can’t install the security update. The Mac reboot but the progress bar stops.
I tried many times without success, even with SIP disabled.
Here’s a link with the error log report.
https://www.dropbox.com/s/qud3ipdeo...Programme d’installation 11-Dec-2018.txt?dl=0

Is there anyone with an idea to solve this ? Thank you very much.

 

[BartmanEH]

[...]I’ve just migrated her data over to her new 2018 13” MBP [...]what ‘under the hood’ operations do I have to do to remove any of the patch associated software and it’s potential effect on this new Mac (that obviously doesn’t need a patch to have the latest macOS)?

Seems to me you could do an in-place re-install of legit High Sierra on the now support new MBP. That would freshen up the whole OS and remove any residual stuff from the old patched install and preserve all the data. I'm not an expert though.

 

[ScooterComputer]

When you've expanded the pkg, you'll find the replaceRecovery script in directory
SecUpd2018-003HighSierra.RecoveryHDUpdate.pkg/Scripts/

Sooooo… what would happen if you just renamed that script and replaced it with one that returned whatever success code that script returns? I mean, bypass the entire process. Further, what happens if you just rename the script? Think the calling script might gracefully pass its nonexistence over? (Could be that the calling script runs ALL the scripts in that folder, might need to move it to ../Scripts-DISABLED/ or such.)

 

[mrploppy]

Sooooo… what would happen if you just renamed that script and replaced it with one that returned whatever success code that script returns? I mean, bypass the entire process. Further, what happens if you just rename the script? Think the calling script might gracefully pass its nonexistence over? (Could be that the calling script runs ALL the scripts in that folder, might need to move it to ../Scripts-DISABLED/ or such.)

Renaming the script just to replace it is pointless as far as I can see. Just edit the script. Remove everything in the script if you wish (I chose to just remove the statement that fails, and every other statement that depends on it). It doesn't return a success code as such. I don't know whether deleting the script completely would have the same effect. I don't know where it's called from - otherwise I'd have a better chance of answering your questions. Maybe the calling script checks for its existence. Maybe it would execute all scripts it found in the folder - although I'd personally find that a strange approach.

Edit: the replaceRecovery script is mentioned in the PackageInfo for the SecUpd2018-003HighSierra.RecoveryHDUpdate.pkg. PackageInfo is an xml file so I'm guessing (and I'm no expert at all) that some higher level package installer decodes the file and runs the scripts mentioned. There's only one entry in the list of scripts and it's
<postinstall file="replaceRecovery" estimatedRunningTime="100"/>
So maybe removing that line from the PackageInfo file would be sufficient.

 

[eric89074]

I just installed high Sierra on a MB Pro 5,4. Applied the patches and it booted up great. I tried to install the security update and iTunes from the App Store but they failed. After restarting no updates are showing in the App Store any more. I tried deleting the App Store cache and running onyx and still nothing shows up. How can I get the updates to show again or at least manually update iTunes? Thanks

 

[jbarley]

How can I get the updates to show again or at least manually update iTunes? Thanks

You can get iTunes from here, Apple direct download.
https://support.apple.com/kb/DL1977?locale=en_US

 

[eric89074]

You can get iTunes from here, Apple direct download.
https://support.apple.com/kb/DL1977?locale=en_US

Thanks!

 

[Lahmy88]

Seems to me you could do an in-place re-install of legit High Sierra on the now support new MBP. That would freshen up the whole OS and remove any residual stuff from the old patched install and preserve all the data. I'm not an expert though.

Sorry I’ve just updated my post to mention the fact that the new Mac has Mojave installed.

 

[Caesar_091]

Never updated my system: this is the state from the very first installation of High Sierra OS.

Also:
- my MacBook on each reboot plays the "boong" sound two times (the first time I see a white backgroung with the gray Apple logo and the second time i see the "new" booting graphics with a black screen)... is that normal?
- my network location list was wiped out installing High Sierra with the reported tutorial... is that normal?

Any solution to these issues?

 

[Forbidden Era]

Hello,

I own a Macbook pro 2010 (7.1) which is normaly compatible with High Sierra. But I have a soft SSD raid in this Mac (HFS) and Apple removed the possibility to boot from raid volume with High Sierra.
So, impossible to install High Sierra on my raid.
Thanks to the dosdude1's patch I have installed High Sierra on this Mac.

But now I can’t install the security update. The Mac reboot but the progress bar stops.
I tried many times without success, even with SIP disabled.
Here’s a link with the error log report.
https://www.dropbox.com/s/qud3ipdeomidhy5/Historique de Programme d’installation 11-Dec-2018.txt?dl=0

Is there anyone with an idea to solve this ? Thank you very much.

I had no issues installing latest HS w/dosdude1 patch on HFS+ apple software raid.

I do have no video acceleration though, tearing my hairs out over it!
[doublepost=1544739605][/doublepost]Hi

real cMP 3,1, 32gb 667, quadro 2000, geforce 560ti, 4x250gb hd in apple sw raid (which makes things a PITA too, as technically I have an EFI partition on each drive... generally things work out and just use the first drive..)

Upgraded to HS with Dosdude's patch..used it to download HS, and I ended up with build #17G2208, which is supposed to be a specific update only for 2018 MBPs - thus there will never be a webdriver build for this OS build.

Previously was on Yosemite with acceleration working fine. Followed Dosdude instructions to make USB for HS, booted it, installed, rebooted and it would turn off every boot, like literally power off..

Pull out the MBP, target disk mode, boot the USB again and run the post-install patches (I did do the AMD video patch, I hope this doesn't matter, it was auto-selected as my mbp has amd) on my volume. Shut down, boot the cMP again.. I do believe I booted to black screen at first.. Not sure how I rectified that, I think maybe I put in whatevergreen.kext, but when I did that at first, I didn't put in the lilu or whatever, so that shouldn't have affected anything..?

Anyway.. I am booted now, I do have graphics on both cards on all 4 screens at full resolution but no acceleration, no rotation, no fun.

I used nvidia-update.sh to install drivers, tried the latest, tried a few older versions back to the point where nvidia-update broke trying to patch them..378.05.05.25f12 I believe wouldn't patch anymore.

The web drivers DO load and DO show the cards, but no accel. Selecting the OS X driver doesn't change anything. It's almost like the drivers are ignoring my cards...but..the fermi graphics framework is still part of the driver package..? I don't even mind using older drivers if needed either..!

I did also eventually install lilu kext along with whatevergreen but this doesn't seem to make any/much difference.. The first boot after 'nvram ngfxgl=1', suddenly my 560ti was detected first and my quadro2000 second, which put my primary screen as primary like it should be..but still no accel, still glitchy graphics in some spots..

I know my card is old - but I also know people have gotten it and other fermi cards working in HS, heck I've seen people get them working in Mojave..??..unfortunately most of those people are on hackintoshes, I am not sure how different whatevergreen would work being injected by clover or something versus simply being in S/L/E..?

Also, once the graphics kick in, I get a 'boot screen' of sorts, black background apple logo and a progress bar, takes forever to finish booting at this point too..

I've been at this all day, trying different driver versions, etc.. no luck.

Please help me breathe a little more life into this cheese grater. At least until I can find/afford a new gfx card and/or a 5,1.. or build a hack maybe..

 

[jbarley]

Have you tried this "nvidia-update-master"?
It's a script that when run searches for the most compatible driver then downloads and patches it to run on whatever version macOS you're running.
It even managed to get me a webdriver for my Mojave test install.

https://github.com/Benjamin-Dobell/nvidia-update

 

[Forbidden Era]

Have you tried this "nvidia-update-master"?
It's a script that when run searches for the most compatible driver then downloads and patches it to run on whatever version macOS you're running.
It even managed to get me a webdriver for my Mojave test install.

https://github.com/Benjamin-Dobell/nvidia-update

Yes, this is the script I mentioned in my post that I used to update/install nvidia web drivers.

Tried a few diff web driver versions, they supposedly load even!

Just noticed that maybe NVDAStartup.kext isn't loaded ..?

Lilu:

  Version:    1.2.8
  Last Modified:    2018-12-13, 12:58 AM
  Bundle ID:    as.vit9696.Lilu
  Loaded:    Yes
  Obtained from:    Not Signed
  Kind:    Intel
  Architectures:    x86_64
  64-Bit (Intel):    Yes
  Location:    /System/Library/Extensions/Lilu.kext
  Kext Version:    1.2.8
  Load Address:    18446743521834100000
  Loadable:    No
  Signature Validation Errors:    Not Signed
  Dependencies:    Satisfied
  Signed by:    Not Signed

NVDAGF100Hal:

  Version:    10.32.0
  Last Modified:    2018-04-18, 5:05 PM
  Bundle ID:    com.apple.nvidia.driver.NVDAGF100Hal
  Loaded:    Yes
  Get Info String:    NVDAGF100Hal 10.32.0 355.11.10.10.40.102
  Obtained from:    Apple
  Kind:    Intel
  Architectures:    x86_64
  64-Bit (Intel):    Yes
  Location:    /System/Library/Extensions/NVDAGF100Hal.kext
  Kext Version:    10.3.2
  Load Address:    18446743521862500000
  Loadable:    Yes
  Dependencies:    Satisfied
  Signed by:    Software Signing, Apple Code Signing Certification Authority, Apple Root CA

NVDAResman:

  Version:    10.32.0
  Last Modified:    2018-04-18, 5:05 PM
  Bundle ID:    com.apple.nvidia.driver.NVDAResman
  Loaded:    Yes
  Get Info String:    NVDAResman 10.32.0 355.11.10.10.40.102
  Obtained from:    Apple
  Kind:    Intel
  Architectures:    x86_64
  64-Bit (Intel):    Yes
  Location:    /System/Library/Extensions/NVDAResman.kext
  Kext Version:    10.3.2
  Load Address:    18446743521859500000
  Loadable:    Yes
  Dependencies:    Satisfied
  Signed by:    Software Signing, Apple Code Signing Certification Authority, Apple Root CA

NVDAStartup:

  Version:    10.32.0
  Last Modified:    2018-04-18, 5:05 PM
  Bundle ID:    com.apple.nvidia.NVDAStartup
  Loaded:    No
  Get Info String:    NVDAStartup 10.32.0 355.11.10.10.40.102
  Obtained from:    Apple
  Kind:    Intel
  Architectures:    x86_64
  64-Bit (Intel):    Yes
  Location:    /System/Library/Extensions/NVDAStartup.kext
  Kext Version:    10.3.2
  Loadable:    Yes
  Dependencies:    Satisfied
  Signed by:    Software Signing, Apple Code Signing Certification Authority, Apple Root CA

NVDAStartupWeb:

  Version:    10.33.0
  Last Modified:    2018-12-13, 4:45 AM
  Bundle ID:    com.nvidia.NVDAStartupWeb
  Loaded:    No
  Get Info String:    NVDAStartupWeb 10.33.0 387.10.10.10.40.113
  Obtained from:    Unknown
  Kind:    Intel
  Architectures:    x86_64
  64-Bit (Intel):    Yes
  Location:    /Library/Extensions/NVDAStartupWeb.kext
  Kext Version:    10.3.3
  Loadable:    No
  Signature Validation Errors:    Kext signature validation error code -67030
  Dependencies:    Satisfied
  Signed by:    Unknown

WhateverGreen:

  Version:    1.2.4
  Last Modified:    2018-12-12, 11:46 PM
  Bundle ID:    as.vit9696.WhateverGreen
  Loaded:    Yes
  Obtained from:    Not Signed
  Kind:    Intel
  Architectures:    x86_64
  64-Bit (Intel):    Yes
  Location:    /System/Library/Extensions/WhateverGreen.kext
  Kext Version:    1.2.4
  Load Address:    18446743521834200000
  Loadable:    No
  Signature Validation Errors:    Not Signed
  Dependencies:    Satisfied
  Signed by:    Not Signed

 

[Forbidden Era]

I should note that while the graphics card info says that there is only two monitors connected, there is actually four, seems like it wasn't showing the ones connected to the 560ti.

Also, at one point it was showing the 560ti as card#1 (as it should, it's in slot#1) before..now it is back to the quadro2000 being first..when I first installed, the 2000 was first..then I believe I added whatevergreen then the 560ti came first, but, at that point I hadn't even added the lilu kext so I'm sure whatevergreen probably didn't affect it... I don't believe it is random though it could be..