macOS High Sierra (10.13) Unsupported Macs Thread

[rktr]

Any idea to fix this?
Thanks.

Hi.

I did search this forum, havent gone through all the 80 pages we have here in this forum though.
Sorry if this is an already solved or a known issue.

Having a lot of problems with my MacBook5,1. despite it is reported no issues, on the first page, and many others reported here, but struggling now to make it work on my end somehow.

I have downloaded the most updated High Sierra Install app from Apple, and dosdude's tool, both as of yesterday.
El Capitan is the last officially supported OS for my macbook, and it is working flawlessly on the issues I have in High Sierra as:

1) imessage and facetime not working, telling me that problem occorred while activation.
Works on El Capitan.
2) I can login and use icloud, however everytime I reboot, it asks to enter my password again
No issues with El Capitan.
3) Mysteriously, most apps if not all apps I purchased through appstore doesnt launch at all. Waiting for a moment, it asks to enter the AppleID and password I used to purchase the app, I am quite sure I am entering the correct info. It is wierd that some apps are working.
4) My macbook appears to run slower than I expected, with 4GB OF RAM and 240GB SSD.

SIP is disabled for sure, I am checking that oftenly.
Havent forgot to apply the postinstall patch after OS install.
I talked with Apple Support, of this issue, to fix imessage and facetime, but no avail. It is working on El Capitan anyway.
I compared the info between EC and HS, I get with iMessagedebug.app. Both identical, however,
the row for "kbjfrfpoJU", being different.(heard the this kbjfrfpoJU row differs for each OS install attempt.True?)
I tried both APFS and HFS+, ending up the exact same issue i have above.

Thanks for any help in advance.

rktr

 

[fischersd]

Any idea to fix this?
Thanks.

I wonder if your iCloud credentials aren't getting messed up by having devices at varying levels of authentication (hit that during the HS / iOS 11 beta). What other devices (and software versions) are you using your iCloud account / AppleID on?

Also, if you haven't enabled 2FA yet (two factor authentication) then you should get on it....Apple's pretty much making it mandatory. Perhaps that's part of your problems with iCloud authentication.

If you want to get continuity working on your MacBook, you'll need to run the CAT tool.

 

[rktr]

I wonder if your iCloud credentials aren't getting messed up by having devices at varying levels of authentication (hit that during the HS / iOS 11 beta). What other devices (and software versions) are you using your iCloud account / AppleID on?

Also, if you haven't enabled 2FA yet (two factor authentication) then you should get on it....Apple's pretty much making it mandatory. Perhaps that's part of your problems with iCloud authentication.

If you want to get continuity working on your MacBook, you'll need to run the CAT tool.

fischersd,

Thanks for your reply.
Yes, I do believe all the issue comes from something related to iCloud or AppleID credentials.
Through appleid.apple.com, I see devices which is signed in with my appleid.
2 hackintoshes, 2 unsupported macs, 2 supported mac, 2 ipad, and 3 iphones.

I am trying to delete MacBook5,1 from that list and seeing how it goes.
Thanks for you suggestions on 2FA, I will try that and get back.

Thanks,

rktr

 

[fischersd]

You run the risk of getting messed up credentials unless they're all on the same level - this all changed with HS and iOS 11. So, if you don't upgrade all of them you may have some odd problems.

Apple's iCloud servers "in their infinite wisdom" made me change my iCloud password 4 times during the beta - because they thought something was "fishy" - obviously, no indication as to what it was, just that I had to change my password.

This was definitely, in part, due to me still having Sierra and iOS 10 devices on the same AppleID. (something I corrected after they went gold / public release)

 

[MacHighSierraNewBie]

If you downloaded the High Sierra installer from within the High Sierra Patch application after the Supplemental Update was released, it already contains the Supplement Update which would be why it isn't showing up for you in the App Store. Have you checked in the Finder to see what build of High Sierra is installed? If it shows 17A405, you already have the changes. Note that the version number of the High Sierra installer got bumped when they integrated the Supplemental Update into it.
[doublepost=1507899809][/doublepost]

We will have to wait until the 10.13.1 release occurs, download its full installer and use that to install a patched 10.13.1. On the positive side, assuming Apple finalizes its firmware changes, future incremental Software Update release (10.13.2, etc) shouldn't have that issue. If I'm not mistaken, the same thing happened early in Sierra as I recall complaints about failed Software Update installs on unsupported machines then as well but the issue didn't exist for the later Software Update releases.

thanks for your reply! I’m just in the process to reinstall High Sierra again. Must remind myself to turn off automatic updates and wait until the next update is released...

 

[MacGuyRookie]

What does Get Info in the Finder show for the "Install macOS High Sierra" application? If you have 13.0.65, you should discard that and download the installer so that you have 13.0.66 which contains the Supplemental Update and will install 17A405.

Thanks for your response jhowarth. I'm on the road this weekend without the 'old' MBP. But assuming that I've got the 13.0.65 installer, if I download the 13.0.66 installer will I need to go through the entire Dosdude1 patch routine or will it just install as on a supported machine? Thanks in advance.

 

[jhowarth]

Thanks for your response jhowarth. I'm on the road this weekend without the 'old' MBP. But assuming that I've got the 13.0.65 installer, if I download the 13.0.66 installer will I need to go through the entire Dosdude1 patch routine or will it just install as on a supported machine? Thanks in advance.

You will need to need to create a new USB installer from the 13.0.66 HS installer application and use that to repeat the installation of High Sierra.

 

[Hackintosh HD]

Any way to determine what version this is?

Yes, click on "Version 10.13".

 

[cinergi]

Just added support for booting encrypted APFS volumes to the latest version of High Sierra Patcher! As always, info and download is available here.

Note: Due to the nature of this kind of patch, it cannot be installed via Patch Updater. If you want to boot from an encrypted APFS drive on an unsupported machine utilizing this patch, you'll need to re-create a new installer USB drive, and use the post-install tool from within that to apply the necessary patches after converting your volume. Also not, that when booting from an encrypted APFS volume, there will be no boot screen, as shown here.

After following the above, I am now unable to boot: I get the "boot file not found" error in the EFI boot loader text-mode screen. I followed the following steps:

1) Created an installer USB drive using v2.4.0 of the patch tool, which should support booting from encrypted APFS volumes.

2) Rebooted from the installer USB drive.

3) Used Disk Utility from the installer USB drive to convert my existing encrypted High Sierra HFS+ boot volume to APFS. This completed successfully.

4) Launched the Post Install Tool and applied the APFS Patch (and no other patches, since I applied the other patches applicable for my Macbook5,1 when I originally installed High Sierra using an older version of the patch tool).

5) Rebooted to my usual boot volume (which is now encrypted APFS).

After doing the above, the EFI boot loader reports "Boot File Not Found". This is the same error I encountered the first time I tried to convert to APFS using an older version of the patch tool (which, unknown to me at the time, didn't support encrypted APFS volumes).

Any ideas what could be wrong? I noticed that the Post Install tool from v2.4.0 of the Patch Tool still reports v2.3.0 - not sure if that's normal?

Thanks
cinergi

 

[Luigi222]

After following the above, I am now unable to boot: I get the "boot file not found" error in the EFI boot loader text-mode screen. I followed the following steps:

1) Created an installer USB drive using v2.4.0 of the patch tool, which should support booting from encrypted APFS volumes.

2) Rebooted from the installer USB drive.

3) Used Disk Utility from the installer USB drive to convert my existing encrypted High Sierra HFS+ boot volume to APFS. This completed successfully.

4) Launched the Post Install Tool and applied the APFS Patch (and no other patches, since I applied the other patches applicable for my Macbook5,1 when I originally installed High Sierra using an older version of the patch tool).

5) Rebooted to my usual boot volume (which is now encrypted APFS).

After doing the above, the EFI boot loader reports "Boot File Not Found". This is the same error I encountered the first time I tried to convert to APFS using an older version of the patch tool (which, unknown to me at the time, didn't support encrypted APFS volumes).

Any ideas what could be wrong? I noticed that the Post Install tool from v2.4.0 of the Patch Tool still reports v2.3.0 - not sure if that's normal?

Thanks
cinergi

I had a similar issue due to a second hardrive replacing my superdrive, and that’s why if wouldn’t boot for me, and it wasn’t encrypted. I already exposed this issue to @dosdude1 .

 

[rktr]

You run the risk of getting messed up credentials unless they're all on the same level - this all changed with HS and iOS 11. So, if you don't upgrade all of them you may have some odd problems.

Apple's iCloud servers "in their infinite wisdom" made me change my iCloud password 4 times during the beta - because they thought something was "fishy" - obviously, no indication as to what it was, just that I had to change my password.

This was definitely, in part, due to me still having Sierra and iOS 10 devices on the same AppleID. (something I corrected after they went gold / public release)

Unfortunately, it didn't work for me.
I will try Sierra and will see whether it would work.
My hackintoshes and supported macs are now High Sierra and it is running well.
So only my MacBook5,1 is not working.

rktr

 

[fischersd]

Unfortunately, it didn't work for me.
I will try Sierra and will see whether it would work.
My hackintoshes and supported macs are now High Sierra and it is running well.
So only my MacBook5,1 is not working.

rktr

All your iOS devices are on 11?
If that's the case, then I'd log the 5,1 out of iCloud and make sure you delete it from your iCloud / AppleID pages, then log it back in again.
(also check FaceTime and iMessage - you'll likely have to log them back in manually after).

 

[rktr]

All your iOS devices are on 11?
If that's the case, then I'd log the 5,1 out of iCloud and make sure you delete it from your iCloud / AppleID pages, then log it back in again.
(also check FaceTime and iMessage - you'll likely have to log them back in manually after).

fischersd, thank much for your support.

No, my ios devices are not 11, and those are jailbroken on 10.2, so I don't want to update to 11 now.
However then why HS hackintoshes, and HS supported Macs are okey with iMessage and FaceTime?

I then installed now Sierra on my Macbook5,1 with Sierra patcher tool and everything is fine with
iMessage and FaceTime.
So it is really only my HS that doesn't work on MB5,1.

Really strange..

rktr

 

[fischersd]

fischersd, thank much for your support.

No, my ios devices are not 11, and those are jailbroken on 10.2, so I don't want to update to 11 now.
However then why HS hackintoshes, and HS supported Macs are okey with iMessage and FaceTime?

I then installed now Sierra on my Macbook5,1 with Sierra patcher tool and everything is fine with
iMessage and FaceTime.
So it is really only my HS that doesn't work on MB5,1.

Really strange..

rktr

That is strange. Yeah, with those iOS devices on 10, hopefully they play nice and don't cause iCloud credential issues for you in the future.

Now that Sierra's working ok, you could gamble and upgrade it to HS and see what happens.

 

[rktr]

That is strange. Yeah, with those iOS devices on 10, hopefully they play nice and don't cause iCloud credential issues for you in the future.

Now that Sierra's working ok, you could gamble and upgrade it to HS and see what happens.

Can Sierra go directly to HS with an unsupported Mac?
I have done it with a hackintosh, using a non conversion to APFS method, successfully.

 

[cinergi]

I had a similar issue due to a second hardrive replacing my superdrive, and that’s why if wouldn’t boot for me, and it wasn’t encrypted. I already exposed this issue to @dosdude1 .

I don't think that's the issue in my case; it looks like the custom EFI boot loader is not supporting the encrypted APFS volume properly. Hopefully dosdude1 can chime in. Do I have to do a full reinstall using the v2.4.0 High Sierra Patcher? From dosdude1's post I had understood that I just have to apply the APFS patch using the new Patcher, not do a full reinstall.

Thanks
cinergi

 

[dosdude1]

I don't think that's the issue in my case; it looks like the custom EFI boot loader is not supporting the encrypted APFS volume properly. Hopefully dosdude1 can chime in. Do I have to do a full reinstall using the v2.4.0 High Sierra Patcher? From dosdude1's post I had understood that I just have to apply the APFS patch using the new Patcher, not do a full reinstall.

Thanks
cinergi

You shouldn't need to do a full re-install... Just run the latest post-install patch on an encrypted APFS volume, and it should allow it to boot. You'll probably need to unlock the volume in Terminal first. Just run "diskutil apfs list", take note of the locked volume's UUID, then run "diskutil apfs unlockVolume <UUID>". The post-install patch should be able to be applied.

 

[cinergi]

You shouldn't need to do a full re-install... Just run the latest post-install patch on an encrypted APFS volume, and it should allow it to boot. You'll probably need to unlock the volume in Terminal first. Just run "diskutil apfs list", take note of the locked volume's UUID, then run "diskutil apfs unlockVolume <UUID>". The post-install patch should be able to be applied.

That's exactly what I did. I had to unlock the APFS volume in order for the APFS patch option to be available (not greyed out). The only difference is that I unlocked the volume using Disk Utility included on the bootable USB instead of the CLI command.

After I applied the APFS patch, my Macbook5,1 rebooted into the custom EFI boot loader, but then I got the "boot file not found, exiting" message. This is the same message I got before with an older version of the EFI boot loader that did not support encrypted APFS volumes.

The "Post Install" tool indicates v2.3.0 although the patcher version is v2.4.0; is this normal?

Thanks
cinergi

 

[macdos]

Mac Pro 3,1 / AMD Radeon HD 7950 Sapphire Mac:

• Smooth installation
• No sleep bug
• Red flashing bug only in Preview, can live with that…
• No garbled video

When will Apple hire Mr. Dosdude?

 

[fischersd]

Can Sierra go directly to HS with an unsupported Mac?
I have done it with a hackintosh, using a non conversion to APFS method, successfully.

Yep, should still boot from dosdude’s patched installer, install on your Sierra volume and it should upgrade it, then boot from the USB when the installer reboots and run the post-install patch

 

[rktr]

Yep, should still boot from dosdude’s patched installer, install on your Sierra volume and it should upgrade it, then boot from the USB when the installer reboots and run the post-install patch

I see. Will try if that route works. Thanks!

 

[roziek]

@dosdude1 Thanks again for all that you do!

Similar to the Unsupported WiFi Modules listed under Known Issues on http://dosdude1.com/highsierra/, would you consider creating a known issues section for graphics cards that are not fully supported? (For example, HD 5770 sleep/wake kernel panic and red display issues.)

On a side note, I'm looking to replace the HD 5770 causing issues in my Mac Pro 3,1. Since I run most of my displays off a second GPU (NVIDIA GTX 1060 PC Unflashed), I'm looking for the least expensive Mac Boot and High Sierra compatible GPU.

Has anyone on this thread tested an NVIDIA GT 640 on a Mac Pro 3,1? Any other low-cost recommendations?

/AK

ATI Radeon HD 2600 XT is probably the best choice.

1) Works on Mac Pros from 1,1 to 5,1.
2) You're using a GTX 1060, so with 2600 XT you won't run into weird issues caused by having two cards of same type (like if you would pair your GTX 1060 with, say, a GT 120).
3) Works fine on High Sierra.
[doublepost=1508109499][/doublepost]

Interesting - I had heard about doing it on a brand new install and I'll definitely try that next. I don't think the system I have is a refurb, but I'll keep that in mind too! Thanks.

If it still fails, try flashing on a fresh installation of some older macOS version (like, before Yosemite).
[doublepost=1508109692][/doublepost]

Having replaced my ATI Radeon HD5770 with an nVidia GTX285, my Mac Pro 3,1 has been running High Sierra for the last week with no discernible issues. However, if I try to boot using the recovery partition, I just get the 'no entry' sign (circle with diagonal line). I selected the "recovery partition patch" when doing the install, and left the SSD I was installing onto as HFS. Any ideas why it doesn't work? I can see it's there by using terminal and also the boot option screen, but it just won't boot from it.

How are you trying to get into the Recovery partition? Are you holding option key while booting and then choosing the Recovery partition? If so, try instead holding the R key (or CMD + R, can't remember) while booting. I had the same problem with Recovery partition on a patched Sierra installation on an unsupported Mac, and this worked for me.

 

[conifer]

Hi.

I did search this forum, havent gone through all the 80 pages we have here in this forum though.
Sorry if this is an already solved or a known issue.

Having a lot of problems with my MacBook5,1. despite it is reported no issues, on the first page, and many others reported here, but struggling now to make it work on my end somehow.

I have downloaded the most updated High Sierra Install app from Apple, and dosdude's tool, both as of yesterday.
El Capitan is the last officially supported OS for my macbook, and it is working flawlessly on the issues I have in High Sierra as:

1) imessage and facetime not working, telling me that problem occorred while activation.
Works on El Capitan.
2) I can login and use icloud, however everytime I reboot, it asks to enter my password again
No issues with El Capitan.
3) Mysteriously, most apps if not all apps I purchased through appstore doesnt launch at all. Waiting for a moment, it asks to enter the AppleID and password I used to purchase the app, I am quite sure I am entering the correct info. It is wierd that some apps are working.
4) My macbook appears to run slower than I expected, with 4GB OF RAM and 240GB SSD.

SIP is disabled for sure, I am checking that oftenly.
Havent forgot to apply the postinstall patch after OS install.
I talked with Apple Support, of this issue, to fix imessage and facetime, but no avail. It is working on El Capitan anyway.
I compared the info between EC and HS, I get with iMessagedebug.app. Both identical, however,
the row for "kbjfrfpoJU", being different.(heard the this kbjfrfpoJU row differs for each OS install attempt.True?)
I tried both APFS and HFS+, ending up the exact same issue i have above.

Thanks for any help in advance.

rktr

I have MacBook late 2008 aluminum on Yosemite and iOS devices are running 10. I have encrypted the volume. Would you advise installing Sierra first and then jumping to High Sierra or can I go directly to High Sierra from Yosemite?

 

[chrome-dome]

chrome-dome said: ↑
Having replaced my ATI Radeon HD5770 with an nVidia GTX285, my Mac Pro 3,1 has been running High Sierra for the last week with no discernible issues. However, if I try to boot using the recovery partition, I just get the 'no entry' sign (circle with diagonal line). I selected the "recovery partition patch" when doing the install, and left the SSD I was installing onto as HFS. Any ideas why it doesn't work? I can see it's there by using terminal and also the boot option screen, but it just won't boot from it.
[doublepost=1508109692][/doublepost]

How are you trying to get into the Recovery partition? Are you holding option key while booting and then choosing the Recovery partition? If so, try instead holding the R key (or CMD + R, can't remember) while booting. I had the same problem with Recovery partition on a patched Sierra installation on an unsupported Mac, and this worked for me.

I have tried both the Cmd+R and choosing I the boot option screen, the result is the same with both. It's not a huge issue as I can boot from the USB drive I set up to install HS, but I just wondered if there was a fix.

 

[gages]

Same issue on my primary SSD which is formatted as APFS. Can not boot from the recovery volume. I cloned a backup disk using HFS+ and CCC, and the recovery volume on that disk is fine.

BTW, if I format the backup disk as APFS and do a CCC clone, I can not select the backup disk as a boot drive from the Dosdude1 APFS Boot Applet or when holding down the Option key. I only get the EFI boot option, which boots into the primary disk.