macOS High Sierra (10.13) Unsupported Macs Thread

[rotarypower101]

Try just booting off your patched High Sierra installer USB drive (it is essentially the same thing as the recovery partition), and use Disk Utility from there to verify and repair the disk.

Thank you for taking to the time and effort to help so many people!




I erased the installer USB drive and utilized the card for its original purposes after instalation, not being instructed to keep it around or thinking I would ever need it again.

Would utilizing the disk utility that was included with my old existing 10.10 install via Command-R have been OK to utilize? assuming I still needed to "repair my 10.13.1 OS disk" I am installed on 10.13.1 and running perfectly fine now to reiterate!

I can easily rebuild a install tool specifically for the task if needed.


Just looking for clarity as to “If this was/is a expected omission” to a normal typical installation utilizing the “Patcher Tool” with my hardware configuration? Assuming there is a way to answer this question.


My inference is that I made a mistake or didn't follow directions correctly?


And wondering if others with similar setups might have the same omission, or if I can figure out why mine is missing the Mac OS Recovery tools if they where/are expected to be there?


Simply looking, if it can be answered.., did I make a mistake or is there something I did incorrectly to be missing these tools? Hoping to learn so that I don't make the same mistake in the future, or can figure out how to get it on there properly next time.

 

[ATC]

Yes, it is perfectly safe to install system updates, you may just have to re-run the post-install patch or re-install patches using the Patch Updater application after doing so. As for SIP, all you need to do is just ensure they you do not reset the PRAM, and SIP should remain disabled. You'll get a warning that pops up on boot if SIP somehow does became enabled.

Thanks. So far I've only come across two anomalies; One, iTunes wifi sync with my iPhone no longer works. It seems very flaky, seeing my phone wirelessly but drops the connection when "Sync" is selected. It's no big deal as I hardly wirelessly sync anyhow. Two, for some reason when I plug my iPhone into my mac's keyboard's USB port it now says that I need to plug it directly into the mac instead - something I never had to do before. Is this a High Sierra thing or some patch causing this?

 

[w1z]

Thank you for taking to the time and effort to help so many people!




I erased the installer USB drive and utilized the card for its original purposes after instalation, not being instructed to keep it around or thinking I would ever need it again.

Would utilizing the disk utility that was included with my old existing 10.10 install via Command-R have been OK to utilize? assuming I still needed to "repair my 10.13.1 OS disk" I am installed on 10.13.1 and running perfectly fine now to reiterate!

I can easily rebuild a install tool specifically for the task if needed.


Just looking for clarity as to “If this was/is a expected omission” to a normal typical installation utilizing the “Patcher Tool” with my hardware configuration? Assuming there is a way to answer this question.


My inference is that I made a mistake or didn't follow directions correctly?


And wondering if others with similar setups might have the same omission, or if I can figure out why mine is missing the Mac OS Recovery tools if they where/are expected to be there?


Simply looking, if it can be answered.., did I make a mistake or is there something I did incorrectly to be missing these tools? Hoping to learn so that I don't make the same mistake in the future, or can figure out how to get it on there properly next time.

If you converted your system drive to APFS then you can't boot into recovery and must boot of the USB patch install disk to carry out any maintenance tasks, however, if you chose to stay with HFS then you can boot into recovery regardless of whether or not you have filevault enabled.

Should you get the circle with a slash when booting into recovery on HFS, search for my fix in this thread.

Edited: removed double post

 

[robertosh]

Anyone lucky with an iMac early 2008? (C2d 3.06, 8800GS)

 

[w1z]

@dosdude1 Thank you for your efforts =) 1YB81204TN138921V

@foxlet Please pm me your paypal donation details.

 

[EugW]

As far as I know, handbrake 1.0.7 for Mac does not use the GPU for file conversion - at least not on Macs as old as mine. So any graphics driver issue for my GeForce 9400M shouldn't affect the conversion. But why does QuickTime only have trouble playing files converted using macOS High Sierra while it does play the files converted using macOS Sierra (and the very same handbrake version!) just fine?

If you'd like to test it, I uploaded a 10 seconds excerpt from the file converted in macOS High Sierra (620 KB) here:

https://www.dropbox.com/s/8ww0rz1g7hwg62z/test.mp4?dl=0

That file plays perfectly fine for me.

MacBook5,1 Core 2 Duo 2.0 GHz with GeForce 9400M and macOS 10.13.1, Safari 11.0.1. It also plays perfectly with QuickTime 10.4 (928).

However, the video in the X on www.apple.com/iphone-x is still garbled for me (and others).

EDIT:

Weird. It played fine in QuickTime fine the first time, but then it didn't.

So, then I logged out and logged back in and played it again in QuickTime, and it was still problematic. I then tried it in Safari again, and it was fine, and then tried it again in QuickTime, and it was also fine again.

When it works fine in QuickTime:

When it doesn't work fine in QuickTime:

The only difference is for the first image, I played it in Safari first directly from DropBox. It always plays fine there.

After I play it in Safari, then it sometimes works fine in QuickTime (but not always).

Very strange.

 

[seb.wagner]

Weird. It played fine in QuickTime fine the first time, but then it didn't. (...) After I play it in Safari, then it sometimes works fine in QuickTime (but not always).
Very strange.

Very strange, indeed. (But thanks a lot for testing it so extensively!)

Further testing on my MacBook Pro implies that it could be coincidental: I found some other files that don't play properly in QT under macOS High Sierra (while most play fine) – all of wich where converted using handbrake in macOS Sierra or previous versions of the OS. And I found that when I convert files that play fine in QT using handbrake in macOS High Sierra, the result also plays fine. So I still have no idea what causes the problem in QT; but it does not appear to be so that any conversion with handbrake in macOS High Sierra automatically produces a problematic file.

Erratic behavior like this does, however, not build trust ... so I'm still not sure I should continue converting files in 10.13.1 ...

Any idea if tinkering with the NVIDIA-kexts could help? Like replacing them with with old ones from macOS Sierra? However, I don't really know where to start with something like this, I'm afraid.

 

[Guy Clark]

dosdude1 once again pulls out all the stops to enable users to run the latest macOS release on older Macs.

I have macOS Sierra and High Sierra dual booting perfectly on my iMac 8,1 thanks to the dosdude1 patcher tools.

I was able to overcome the WiFi issue as I was fortunate enough to have an iMac 10,1 sitting around as spares so I just swapped the cards over. Problem solved.

It is ironic users of older Macs need to enter Hackintosh territory to be able to run the native platform.

 

[EugW]

Very strange, indeed. (But thanks a lot for testing it so extensively!)

Further testing on my MacBook Pro implies that it could be coincidental: I found some other files that don't play properly in QT under macOS High Sierra (while most play fine) – all of wich where converted using handbrake in macOS Sierra or previous versions of the OS. And I found that when I convert files that play fine in QT using handbrake in macOS High Sierra, the result also plays fine. So I still have no idea what causes the problem in QT; but it does not appear to be so that any conversion with handbrake in macOS High Sierra automatically produces a problematic file.

Erratic behavior like this does, however, not build trust ... so I'm still not sure I should continue converting files in 10.13.1 ...

Any idea if tinkering with the NVIDIA-kexts could help? Like replacing them with with old ones from macOS Sierra? However, I don't really know where to start with something like this, I'm afraid.

I’m optimistic Apple will fix it since the 9400M is a High Sierra-supported GPU, and as mentioned those with supported Macs have the same problem. So personally I will not mess with the kexts.

 

[slooksterPSV]

I’m optimistic Apple will fix it since the 9400M is a High Sierra-supported GPU, and as mentioned those with supported Macs have the same problem. So personally I will not mess with the kexts.

Do you think the converter uses the driver to render possibly causing garbled video though? I’m thinking it may...

 

[jhowarth]

Yes, it is perfectly safe to install system updates, you may just have to re-run the post-install patch or re-install patches using the Patch Updater application after doing so. As for SIP, all you need to do is just ensure they you do not reset the PRAM, and SIP should remain disabled. You'll get a warning that pops up on boot if SIP somehow does became enabled.
[doublepost=1509858510][/doublepost]
Try just booting off your patched High Sierra installer USB drive (it is essentially the same thing as the recovery partition), and use Disk Utility from there to verify and repair the disk.

The bit about it being perfectly safe to install system updates doesn't sound right. So far, for both the release 10.13.1 system update and the beta 10.13.2 system updates, the installation isn't cleanly completed due to the presence of firmware updates. IMHO, until Apple stabilizes the firmware and stops shoving out firmware updates with each successive Software Update release, users should be using the full installer.

 

[overcast]

I think I'll have to just sell off this RX480, I don't see any way of getting around it on a genuine Mac Pro.

 

[EugW]

The bit about it being perfectly safe to install system updates doesn't sound right. So far, for both the release 10.13.1 system update and the beta 10.13.2 system updates, the installation isn't cleanly completed due to the presence of firmware updates. IMHO, until Apple stabilizes the firmware and stops shoving out firmware updates with each successive Software Update release, users should be using the full installer.

What firmware updates in High Sierra were released for Macs this old?

Do you think the converter uses the driver to render possibly causing garbled video though? I’m thinking it may...

I had thought it was all software based, so if true it shouldn’t make much of a difference if it was encoded in Sierra or High Sierra or El Capitan for that matter. Have you tried a different preset, and/or the latest Handbrake nightly?

 

[jhowarth]

What firmware updates in High Sierra were released for Macs this old?


I had thought it was all software based, so if true it shouldn’t make much of a difference if it was encoded in Sierra or High Sierra or El Capitan for that matter. Have you tried a different preset, and/or the latest Handbrake nightly?

I suspect what we are seeing is the handling of the firmware updates crashing out the installation process because we are on unsupported hardware. Unless I am mistaken, this is similar to the situation early in the Sierra updates when those delta updates still contained new firmware releases on supported hardware. Like Sierra, once Apple moves past adding new firmware updates, the later Software Updates shouldn't be a problem for the older unsupported machines.

 

[EugW]

I suspect what we are seeing is the handling of the firmware updates crashing out the installation process because we are on unsupported hardware. Unless I am mistaken, this is similar to the situation early in the Sierra updates when those delta updates still contained new firmware releases on supported hardware. Like Sierra, once Apple moves past adding new firmware updates, the later Software Updates shouldn't be a problem for the older unsupported machines.

Well, I had no issues with my two machines (MacBook5,1 and MacBookPro5,5). However, both were clean installs of High Sierra 10.13, and then updated to 10.13.1.

 

[jhowarth]

Well, I had no issues with my two machines (MacBook5,1 and MacBookPro5,5). However, both were clean installs of High Sierra 10.13, and then updated to 10.13.1.

So you are using the full installer created by the High Sierra Patcher, correct? The problem being discussed is trying to use the delta or combo installer for the Software Update to go from 10.13.0 to 10.13.1 or from 10.13.0 or 10.13.1 to 10.13.2 beta. Those delta and combo software updates still are deploying new firmware which breaks the installation process on unsupported hardware.

 

[EugW]

So you are using the full installer created by the High Sierra Patcher, correct? The problem being discussed is trying to use the delta or combo installer for the Software Update to go from 10.13.0 to 10.13.1 or from 10.13.0 or 10.13.1 to 10.13.2 beta. Those delta and combo software updates still are deploying new firmware which breaks the installation process on unsupported hardware.

No. I used the full installer for 10.13. Then I just used the App Store to update to 10.13.1. Worked fine on both unsupported machines.

The only difference I've noticed is that for the MacBook5,1, my sleep process when I close the lid takes longer now, with a intermediary step for whatever reason. When I close the lid, the Apple logo shuts off, flashes once, and then comes back on again for ~30 seconds, before it shuts off again. Then it sleeps normally. On my MacBookPro5,5 the sleep process is unchanged from before. The Apple logo shuts off and stays off. Wake from sleep works the same on both machines.

I use the "Apple 1080p30 Surround" preset with the following modifications:
* Video > Encoder Options > Preset: > "veryfast" (instead of "medium")
* Audio > no AC3 passthrough
* Subtitles > "none" from source, adding an external .srt-file

I used the last Handbrake Nightly (Nov. 4) to transcode the LG Jazz TV 4K HEVC demo to 1080p h.264, using the "Super HQ 1080p30 Surround" preset, with no modifications (on my iMac). The resultant h.264 file plays perfectly in QuickTime on my 2.0 GHz MacBook5,1 with High Sierra 10.13.1.

 

[EugW]

No. I used the full installer for 10.13. Then I just used the App Store to update to 10.13.1. Worked fine on both unsupported machines.

The only difference I've noticed is that for the MacBook5,1, my sleep process when I close the lid takes longer now, with a intermediary step for whatever reason. When I close the lid, the Apple logo shuts off, flashes once, and then comes back on again for ~30 seconds, before it shuts off again. Then it sleeps normally. On my MacBookPro5,5 the sleep process is unchanged from before. The Apple logo shuts off and stays off. Wake from sleep works the same on both machines.

I forgot to mention that I had to repatch the 10.13.1 (HFS+) Recovery Partition, but the main 10.13.1 boot partition did not need to be repatched. But it seems many of you don't even care about the Recovery Partition so if that Recovery Partition is not important to you, then no repatching (or full installer needed). Just the App Store 10.13.1 update was fine for me for updating the main boot partition.

 

[takfai168]

Thanks Dosdude1. I DO have the Software Update Patch installed. Re-installed but that didn't solve the problem. Cleared the Software Update Catalog in Terminal. I didn't copy the exact wording but it said something like "update changed to Apple Production." I restarted the computer and checked for the updates in the App Store. Took a couple of tries hitting the Update button, but finally the updates showed up. (Back when you were working on the Sierra updates, wasn't there a patch by someone (maybe you?) where the source of updates was changed? Wonder if my 'source' never got changed back to Apple?)

Whatever...thanks again Dosedude1 for sharing your knowledge.

Dear all, I got the APP Store "No Updates Available" after 10.13.1 update. Can anyone help how to fix it? Although I have follow the steps:

1. Software Update Patch re-install.
2. run "sudo softwareupdate --clear-catalog" in Terminal
3. Restart ?

 

[dosdude1]

Dear all, I got the APP Store "No Updates Available" after 10.13.1 update. Can anyone help how to fix it? Although I have follow the steps:

1. Software Update Patch re-install.
2. run "sudo softwareupdate --clear-catalog" in Terminal
3. Restart ?

Because there are no updates available after 10.13.1......

 

[slooksterPSV]

Dear all, I got the APP Store "No Updates Available" after 10.13.1 update. Can anyone help how to fix it? Although I have follow the steps:

1. Software Update Patch re-install.
2. run "sudo softwareupdate --clear-catalog" in Terminal
3. Restart ?

Yup at the present moment in time 10.13.1 is the latest update. You’re not trying to get the beta right?

 

[Yoshua]

Mac OS High Sierra 10.13.1

Macbook 2009 Mid 2009

The fuction keys don't work.

Is there a possibility to turn up the brightness in another way?

Thanks!

 

[Guy Clark]

Mac OS High Sierra 10.13.1

Macbook 2009 Mid 2009

The fuction keys don't work.

Is there a possibility to turn up the brightness in another way?

Thanks!

Have you tried System Preferences>Display

 

[dosdude1]

Mac OS High Sierra 10.13.1

Macbook 2009 Mid 2009

The fuction keys don't work.

Is there a possibility to turn up the brightness in another way?

Thanks!

Re-install patches using Patch Updater, that should fix it.

 

[pietrogregorini]

Hi there guys. I would like to know some quick info: I have a MacBook Pro 5,3 (Mid 2009) with Sierra and it works like a charm with @dosdude1 patch. I'd like to update to High Sierra but I've read about issues with NVIDIA GeForce 9400M: is the bug still present after 10.13.1? Does everybody have some issue with this graphic card?

Another question: did you notice any effective improvement using APFS instead of HFS+? Is the boot fast enough or slower than before?

One last question: @dosdude1 is there any possibility to do some aesthetic improvement to verbose mood boot? I mean, like hiding all the text with a black screen or something like that? I think it would be nicer to see to end users, but of course I don't know if it's something effectively possible to do.