macOS High Sierra (10.13) Unsupported Macs Thread

[Sedulous]

I think I solved double boot issue. At some point I tried the new APFS... didn't feel it was worth trouble and went back to AFS. Even though I erased disk, the EFI partition that supported the APFS was still there. And that seems to be the cause. After removing ALL the partitions (I used the DISKPART tool in Windows) and reinstalling patched OS 10.13.2, double boot is gone along with recurring issue I had with weird script running and failing at boot). Hope that helps.

Ok, for those experiencing double boot issue:
Double boot can be solved by removing a .scap file from the hidden EFI partition.
I used terminal to find EFI partition (diskutil list)
Then mounted EFI partition using terminal (sudo diskutil mount <type EFI disk here; likely named disk0s1>)
Navigated to EFI/APPLE/EXTENSIONS/ and removed Firmware.scap file.
The system will recreate a new .scap file after reboot (and bid double boots bye bye!)

 

[MaxinMusicCity]

I've done a preliminary update to macOS Sierra Patcher, just to add compatibility with the High Sierra installer. Keep in mind nothing else has changed, so I'm not sure if some of the post-install patches still work in High Sierra. Also, for those of you who cannot download a copy of High Sierra, I have a copy available for download here (if this is not allowed, let me know and I'll remove this link). Download "macOS High Sierra Patcher" here.

Why am I not able to download the macos High Sierra patcher? The link isn't working.

 

[dosdude1]

Why am I not able to download the macos High Sierra patcher? The link isn't working.

That link is old, this is the current link.

 

[medioevo]

As I said above I have to patch each time I boot. I forgot to describe the process: After the first installation/post install I need to patch only boot.plist but I have to force recheck. After that Mac boots and everything is fine. Following the instructions I run sudo kextcache -system-prelinked-kernel.
The result of 'sudo kextcache -system-prelinked-kernel' is

Kext with invalid signatured (-67062) allowed: <OSKext 0x7f979fe9d410 [0x7fff8be09980]> { URL = "LegacyUSBInjector.kext/ -- file:///Library/Extensions/", ID = "com.parrotgeek.LegacyUSBInjector" }
Kext with invalid signatured (-67062) allowed: <OSKext 0x7f979fd951f0 [0x7fff8be09980]> { URL = "ZTEUSBMassStorageFilter.kext/ -- file:///System/Library/Extensions/", ID = "com.ZTE.driver.ZTEUSBMassStorageFilter" }
Kext with invalid signatured (-67062) allowed: <OSKext 0x7f979fe45b70 [0x7fff8be09980]> { URL = "kudstplink.kext/ -- file:///System/Library/Extensions/", ID = "tl.uds.netusb.controller" }
kext file:///System/Library/Extensions/JRDMassStorageDriver64.kext/ is in hash exception list, allowing to load
kxld[com.apple.driver.AGDCBacklightControl]: The following symbols are unresolved for this kext:
kxld[com.apple.driver.AGDCBacklightControl]:     AppleBacklightParameterHandler::interpolatePanelTable(unsigned short const*, unsigned short, unsigned short, unsigned int, unsigned short*, unsigned short)
kxld[com.apple.driver.AGDCBacklightControl]:     AppleBacklightParameterHandler::loadScaledMobileBacklightTable(unsigned short, unsigned short**, unsigned short*)
Link failed (error code 5).
Prelink failed for com.apple.driver.AGDCBacklightControl; omitting from prelinked kernel.
KernelCache ID: AF2296594A8FF6FE9E3DE1FB7D4FEA0E

 

[mrploppy]

Ok, for those experiencing double boot issue:
Double boot can be solved by removing a .scap file from the hidden EFI partition.
I used terminal to find EFI partition (diskutil list)
Then mounted EFI partition using terminal (sudo diskutil <type EFI disk here>)
Navigated to EFI/APPLE/EXTENSIONS/ and removed Firmware.scap file.
The system will recreate a new .scap file after reboot (and bid double boots bye bye!)

You meant "sudo diskutil mount <EFI disk>"
Yes?
And then "cd /Volumes/EFI/EFI/APPLE/EXTENSIONS"

Any idea why the presence of that file causes a double boot? What's in it?

 

[alex.holliz]

I was able to modify the Distribution file in the installer for the 10.13.2 update for my Mac Pro 4,1. It at least doesn't kick me out of the setup menu right away. However, when I get to volume selection, I get this error:

macOS 10.13.2 Update can't be installed on this disk. In order to upgrade to a newer version of macOS high Sierra on this disk, please see the instructions here [https://beta.apple.com/sp/betaprogram/apfsfusion]

My disk is formatted as Mac OS Extended (Journaled) which is the same as all of my other macs that are supported on High Sierra. So... any idea why I would get that message?

 

[Sedulous]

You meant "sudo diskutil mount <EFI disk>"
Yes?
And then "cd /Volumes/EFI/EFI/APPLE/EXTENSIONS"

Any idea why the presence of that file causes a double boot? What's in it?

Yes, I forgot the "mount" part and will edit accordingly. Thanks!

I think this file location in EFI is where Mac looks for firmware updates to be applied. At some point a firmware update was applied and never checked off as "completed", maybe? Therefore Mac boots, thinks there is a firmware update, attempts to apply it, then reboots again. Removing the Firmware.scap breaks that cycle.

 

[L Caputo]

I was able to modify the Distribution file in the installer for the 10.13.2 update for my Mac Pro 4,1. It at least doesn't kick me out of the setup menu right away. However, when I get to volume selection, I get this error:

macOS 10.13.2 Update can't be installed on this disk. In order to upgrade to a newer version of macOS high Sierra on this disk, please see the instructions here [https://beta.apple.com/sp/betaprogram/apfsfusion]

My disk is formatted as Mac OS Extended (Journaled) which is the same as all of my other macs that are supported on High Sierra. So... any idea why I would get that message?

You are being directed to a beta program page, from this are you running a beta version of High Sierra.
If so I don't think that you can install the Supplemental on a beta installation.

I see also you have got a MacPro 4.1 why don't you upgrade the firmware so that it effectively becomes a 5.1 and then your Mac Pro would be officially supported in High Sierra.

 

[alex.holliz]

You are being directed to a beta program page, from this are you running a beta version of High Sierra.
If so I don't think that you can install the Supplemental on a beta installation.

I see also you have got a MacPro 4.1 why don't you upgrade the firmware so that it effectively becomes a 5.1 and then your Mac Pro would be officially supported in High Sierra.

I made my High Sierra installer from the same version that's running on my iMac, which is supported. It's entirely possible I made a mistake and used the beta, but in any case, this firmware update sounds interesting.
Can you link me to the instructions for that? I'd appreciate it greatly.

 

[L Caputo]

I made my High Sierra installer from the same version that's running on my iMac, which is supported. It's entirely possible I made a mistake and used the beta, but in any case, this firmware update sounds interesting.
Can you link me to the instructions for that? I'd appreciate it greatly.

Ok here is a link to the netkas discussion where it all started, http://forum.netkas.org/index.php/topic,852.0.html, please read all instructions.
try googling 'flashing mac pro 4.1 to 5.1' for further info and experiences

And please make sure you have backed up all your important data before trying anything like this.

 

[sputnikBA]

Ok... I've been trying to avoid going down this route — but I've had enough of iCloud tabs not syncing, apps I can't get because they require 10.12 / 10.13, other sync issues and 2 years worth of features I can't use and various other issues...

So I'm here to ask for some info on how to update my old Mac Pro 3,1 (2008) to High Sierra. This is to buy me some extra time while I think of what hardware to replace it with.

I've been following this thread on and off for a while now and I know that there are problems with this model if you have certain configurations, and issues with things like waking up from sleep. I'd like to ask about the experiences of people who have been using bootleg HS for a while and if they've been able to resolve their issues.

I have:

Mac Pro 3,1 (2008) [8c @ 2.8ghz]
Radeon 7950 (Mac Edition - legit, not a flashed card)
I have a compatible Wifi/BT card that I installed many years ago so I could get continuity features.

from reading the thread, I know there are some issues with Sleep mode & the graphics card, so if it will end up being too much trouble or I have to switch to a different card then I'll probably just stay on El Cap.

Can anyone share their experiences / tips / advice?

Thanks.

 

[L Caputo]

Ok... I've been trying to avoid going down this route — but I've had enough of iCloud tabs not syncing, apps I can't get because they require 10.12 / 10.13, other sync issues and 2 years worth of features I can't use and various other issues...

So I'm here to ask for some info on how to update my old Mac Pro 3,1 (2008) to High Sierra. This is to buy me some extra time while I think of what hardware to replace it with.

I've been following this thread on and off for a while now and I know that there are problems with this model if you have certain configurations, and issues with things like waking up from sleep. I'd like to ask about the experiences of people who have been using bootleg HS for a while and if they've been able to resolve their issues.

I have:

Mac Pro 3,1 (2008) [8c @ 2.8ghz]
Radeon 7950 (Mac Edition - legit, not a flashed card)
I have a compatible Wifi/BT card that I installed many years ago so I could get continuity features.

from reading the thread, I know there are some issues with Sleep mode & the graphics card, so if it will end up being too much trouble or I have to switch to a different card then I'll probably just stay on El Cap.

Can anyone share their experiences / tips / advice?

Thanks.

MacPro 3.1 here, running El Capitan, Sierra and High Sierra, no problems for me.
This machine doesn't use WiFi, so can't help there.
Has no problems waking from sleep.
Nvidia GeForce GT 120.

As you have 4 internal drive bays can you spare about 50GBs of space to make a partition and install High Sierra on that and give it a road test, see how you get on with it.

 

[ovirta]

Trying to update my old faithful Early 2008 Mac to Sierra with Dosdudes tools.

These are versions I am working with
Current OSX: 10.11.6
Target OSX: 10.13.2
Install MacOS Sierra.app: 13.2.01
Dosdude tool: 4.2.7

Downloading Sierra update with dosdude tool goes fine. USB drive is formatted as instructed to Journaled disk and drive prepared ok.
After reboot with Option key the USB drive is visible as bootable device.
Unfortunately booting the USB drive ends quickly with Prohibitory sign (Circle and slash) and mac shuts down. This apparently means: "...your Mac couldn't find a valid System Folder to start up from."
Date is fine on the mac as there was some comments about problems with that.

Any recommendation how to proceed?

 

[roronl]

Trying to update my old faithful Early 2008 Mac to Sierra with Dosdudes tools.

These are versions I am working with
Current OSX: 10.11.6
Target OSX: 10.13.2
Install MacOS Sierra.app: 13.2.01
Dosdude tool: 4.2.7

Downloading Sierra update with dosdude tool goes fine. USB drive is formatted as instructed to Journaled disk and drive prepared ok.
After reboot with Option key the USB drive is visible as bootable device.
Unfortunately booting the USB drive ends quickly with Prohibitory sign (Circle and slash) and mac shuts down. This apparently means: "...your Mac couldn't find a valid System Folder to start up from."
Date is fine on the mac as there was some comments about problems with that.

Any recommendation how to proceed?

The first thing to try, is to use another USB drive.

 

[L Caputo]

Trying to update my old faithful Early 2008 Mac to Sierra with Dosdudes tools.

These are versions I am working with
Current OSX: 10.11.6
Target OSX: 10.13.2
Install MacOS Sierra.app: 13.2.01
Dosdude tool: 4.2.7

Downloading Sierra update with dosdude tool goes fine. USB drive is formatted as instructed to Journaled disk and drive prepared ok.
After reboot with Option key the USB drive is visible as bootable device.
Unfortunately booting the USB drive ends quickly with Prohibitory sign (Circle and slash) and mac shuts down. This apparently means: "...your Mac couldn't find a valid System Folder to start up from."
Date is fine on the mac as there was some comments about problems with that.

Any recommendation how to proceed?

Can you clarify that you want to upgrade to Sierra or High Sierra
you mention both of them in your post.
In the version I am working with
you say your target is 10.13.2 which is High Sierra
you say Install macOS Sierra.app 13.2.01 the number refers to High Sierra, Sierra install apps are numbered with 12 preceding
Dosdude Tool 4.2.7 is for used for Sierra installs, Dosdude Tool 2.5.1 is for High Sierra installs.

If you want to update to Sierra you need the Install macOS Sierra.app along with the patch tool 4.2.7

If you want to upgrade to High Sierra you need the Install macOS High Sierra.app along with the patch tool 2.5.1

 

[jfcates]

I'm running a patched dosdude1 High Sierra 10.3.2 on a 2008 8-core Mac Pro 3,1. Just got a new (old) 2010 Mac Pro 8-core. After a clean install of High Sierra on the 2010 Mac Pro, can I use setup or migration assistant to bring over my settings, apps and files, from the patched version without creating headaches down the road? The big concern is the settings. Also I would assume I can enable SIP after setup/migration? Advice appreciated.

 

[ovirta]

The first thing to try, is to use another USB drive.

That hit the nail. Used same tools to copy installation media to another USB stick and things progressed well.

:
If you want to upgrade to High Sierra you need the Install macOS High Sierra.app along with the patch tool 2.5.1
:

This was my mistake. I was using wrong tool version number in the earlier post. High Sierra toolset was the one in use all the time.

Now I ran into another problem.

Safari and App Store stopped working although network is working fine via cable. Wifi is not functional but that was document well earlier. I am writing this with Chrome but Safari refuses to load web pages and App Store doesn't show anything.

Any suggestions here?

 

[dosdude1]

That hit the nail. Used same tools to copy installation media to another USB stick and things progressed well.



This was my mistake. I was using wrong tool version number in the earlier post. High Sierra toolset was the one in use all the time.

Now I ran into another problem.

Safari and App Store stopped working although network is working fine via cable. Wifi is not functional but that was document well earlier. I am writing this with Chrome but Safari refuses to load web pages and App Store doesn't show anything.

Any suggestions here?

Download the Onyx application, and run its "Maintenance" script.

 

[ovirta]

Download the Onyx application, and run its "Maintenance" script.

Fixed. Thanks Dude many times over.

Any idea what could cause that? Something common in sierra&highsierra?

 

[ovirta]

Fixed. Thanks Dude many times over.

Thank You again dosdude1 this time in Donation form. It wasn't much but just to show my appreciation of your efforts and making this available to rest of us. Saved me from needing to get newer mac to develop apps.

 

[lupine]

Mac Pro 3,1 (2008) [8c @ 2.8ghz]
Radeon 7950 (Mac Edition - legit, not a flashed card)
I have a compatible Wifi/BT card that I installed many years ago so I could get continuity features.

from reading the thread, I know there are some issues with Sleep mode & the graphics card, so if it will end up being too much trouble or I have to switch to a different card then I'll probably just stay on El Cap.

Can anyone share their experiences / tips / advice?

Minus the wifi/BT, I have the same setup. I upgraded without the knowledge of the sleep issues, and regret it considerably. I have an older ADM 5xxx series card somewhere, though haven't yet tried that to see if my precious sleep will return. Have seen a couple of reports of no issues with nVidia cards, so it must be a problem with AMD cards alone. I also get some issues with red surfaces in place of proper textures on some surfaces (such as Time Machine), which again I suspect is a driver issue. Have been unable to restore my Time Machine backup as the NIC doesn't seem to be recognised in the High Sierra recovery disk, and haven't had the time yet to try an alternate.

So maybe it's time to ditch the 3,1 and transition to my MBP and a TB3 dock...

 

[Czo]

Minus the wifi/BT, I have the same setup. I upgraded without the knowledge of the sleep issues, and regret it considerably. I have an older ADM 5xxx series card somewhere, though haven't yet tried that to see if my precious sleep will return. Have seen a couple of reports of no issues with nVidia cards, so it must be a problem with AMD cards alone. I also get some issues with red surfaces in place of proper textures on some surfaces (such as Time Machine), which again I suspect is a driver issue. Have been unable to restore my Time Machine backup as the NIC doesn't seem to be recognised in the High Sierra recovery disk, and haven't had the time yet to try an alternate.

So maybe it's time to ditch the 3,1 and transition to my MBP and a TB3 dock...

Same NIC is working under normal boot? Maybe try to use the kext cache buit under the running OS. Maybe, the prepatched kext cache does not contains the drivers for this NIC.

 

[sputnikBA]

Minus the wifi/BT, I have the same setup. I upgraded without the knowledge of the sleep issues, and regret it considerably. I have an older ADM 5xxx series card somewhere, though haven't yet tried that to see if my precious sleep will return. Have seen a couple of reports of no issues with nVidia cards, so it must be a problem with AMD cards alone. I also get some issues with red surfaces in place of proper textures on some surfaces (such as Time Machine), which again I suspect is a driver issue. Have been unable to restore my Time Machine backup as the NIC doesn't seem to be recognised in the High Sierra recovery disk, and haven't had the time yet to try an alternate.

So maybe it's time to ditch the 3,1 and transition to my MBP and a TB3 dock...

This is what I was looking for, thank you.

From skimming the thread, I think the issue is the card - but I don’t have another one to use, and I don’t really want to buy a compatible card.

1) there’s the performance hit
2) I’d rather just keep the money and put it towards buying a newer Mac.

Being able to hibernate the computer is a thing I do a lot, so losing sleep makes me reluctant to want to try the upgrade. I don’t know if anyone has found a fix for it.

 

[kkkiller]

Yes, I forgot the "mount" part and will edit accordingly. Thanks!

I think this file location in EFI is where Mac looks for firmware updates to be applied. At some point a firmware update was applied and never checked off as "completed", maybe? Therefore Mac boots, thinks there is a firmware update, attempts to apply it, then reboots again. Removing the Firmware.scap breaks that cycle.

Hello everyone.
I have a MacBook 5.1 and also to me, after the upgrade to macOS 10.13.2 a double reboot occurs.
I deleted the .scap file but the problem continues. Any other advice?
Thank you

 

[TopHatProductions115]

I was able to install 10.13.2 Supplimental to MacbookPro5,2 directly from the Updates tab in the "App Store.app" as normal, without issue.

You can run "softwareupdate -l" in a terminal to manully scan for updates, in case there's something odd going on with the "App Store.app"

You might have to run to the app "/Applications/Uilities/Patch Updater.app" then [View Installed Updates], right click on the [Software Update Patch] row and select [Re-install...] to make sure the modified update service is running.

You can also run "defaults read /Library/Preferences/com.apple.SoftwareUpdate" in a terminal and see some potentially useful info. I'm not entirely sure, but I don't think you should see a CatalogURL listing -- at least I don't, on my machine.

I attempted everything you mentioned. In regard to the "software -l" suggestion, the Terminal keeps saying that it can't find that binary/program. Which is strange because, when I tried ls'ing through the common PATH locations, I couldn't find the binary either I also had the Patch Updater reinstall the Software Update Patch/service, which required a reboot. After the reboot, I opened the App Store (again), only to find that there are still no updates available (supposedly). With nothing coming to mind, I went on and ran your last suggestion - "defaults read /Library/Preferences/com.apple.SoftwareUpdate". I've included the relevant results in an attached png, for individual viewing (also for space-saving purposes).

TL;DR I have a feeling that there's something wrong with my MacBook Pro...

EDIT :: Is there a way I could download any missing files from a secondary source? Maybe I can replace whatever's missing...