Thanks. I was having the same issue, no iCloud option for Messages. I hope two-factor authentication has gotten more reliable. I enabled it when it first came out and it wreaked havoc with my Apple TVs accessing my apple account. So I disabled it and haven't tried since. But I'll give it another try for this.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS High Sierra (10.13) Unsupported Macs Thread
- Thread starter foxlet
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thanks. I was having the same issue, no iCloud option for Messages. I hope two-factor authentication has gotten more reliable. I enabled it when it first came out and it wreaked havoc with my Apple TVs accessing my apple account. So I disabled it and haven't tried since. But I'll give it another try for this.
What I find odd is that it’s trying to mount the pkg file and not the dmg within the package. I haven’t looked at the script within the package yet to see what it’s trying to do, but trying to mount the pkg file doesn’t make sense to me. It should be unpacking the pkg and mounting the dmg that is inside it.
Messages.app version Version 11.0 (5500) had the checkbox in the settings window to enable Messages in the Cloud. If you meet the requirements, it will visible to you.
Don't know what I'm doing wrong but cannot build a full installer on USB memory using 2.6.2 MacOS High Sierra Patcher and downloaded full 10.13.5 install that my boot-rom patched MacPro 3,1 can detect when booting with Option key pressed. I've done this dozens of times before and never had an issue where the USB installer is not seen.
Any ideas?
[doublepost=1528079652][/doublepost]Auggie, is that a boot-rom patched MP 3,1?
Any ideas?
[doublepost=1528079652][/doublepost]Auggie, is that a boot-rom patched MP 3,1?
Another favourable here for a Mac Pro 3,1., I installed 10.13.5 directly from the app store updater with a USB stick on hand in case of trouble. The update hung after getting about 80% of the way through the white bar with two minutes left of update to go; I didnt touch it for five minutes time then a click on the mouse brought up a black screen. I long pressed the power button to turn off and then booted back up as normal. The boot back took longer than normal as if it was completing the installation and everything worked as normal. In case its relevant I have a mac efi GTX graphics card so I could see the longer boot up as it progressed.
Installer is booting and running here fine with and without a APFS-patched boot ROM on MP3,1.
1. Try PRAM reset, if not
2. Use a different USB flash stick as these are known to partly fail causing errors with the installer/installations
Yes I do, it hangs in the last two minutes and stays the same way until a window appear saying there's an error and needs to reboot, it reboots very normal and seems to work normally, it says 10.3.5.
The only thing is no info about the installed update list.
Another successfull update to 10.13.5 on a Mac Pro 3.1 (with ATI HD2600). I updated via the App Store. Install hung at the 2 minutes remaining mark. After waiting another 5 minutes, I forced a power off and then repowered. Boot up was slow; took 3+ minutes, but eventually got to the login screen and successfully logged in.
Same as me and others. I'm happy to believe I'm running 10.13.5 despite what the installations list says. Would be really nice if we could get the installer to complete without error but there seems little appetite from anyone on here who knows how to debug the problem. Either that or no-one on here has the expertise.
Are you sure you were updated correctly? Mine was the same as yours but things were a little off even though it says 10.13.5 in About this mac. For example, iMessage in iCloud (which is part of the 13.5 update) wasn't there. You can check if you have the setting (in Messages app - Preferences - Accounts tab - Enable Messages in iCloud checkbox).
I have since clean installed 10.13.5 and have everything running correctly including messages in the cloud.
All those that have updated via the app store, your update is partially complete as the 'Recovery' volume or HD is not updated.
You can verify this by mounting the recovery volume/HD and checking the macOS version in the .plist files.. (Can't remember which)
Look at my previous posts for the recommended route.
Edit: I also recall seeing the storage space of my OS drive decrease by 400~500MB after manually installing using the USB installer - makes you wonder what else the app store update missed. Then again, could be anything as I didn't bother checking to see what was behind the difference.
You can verify this by mounting the recovery volume/HD and checking the macOS version in the .plist files.. (Can't remember which)
Look at my previous posts for the recommended route.
Edit: I also recall seeing the storage space of my OS drive decrease by 400~500MB after manually installing using the USB installer - makes you wonder what else the app store update missed. Then again, could be anything as I didn't bother checking to see what was behind the difference.
Last edited:
Sorry @Czo, I don't think I understood the significance of this answer you gave to my previous question. So, let me just try and clarify.
What you're saying is, if i try and do an incremental update via the App Store, and part of the installation is a macOS10.xx.yyRecoveryHDUpdate.pkg, then that part will always fail but it doesn't affect the rest of the installation (it's just annoying that the update isn't listed in the installations log?). Is that correct?
Is the same true for a Combo Update?
Is the solution to do a full install (in this case 10.13.5) using the High Sierra Patching tool? I can't remember, does the patcher tool update the RecoveryHD correctly?
How do we know in advance whether an incremental update contains a RecoveryHD update? Would be nice, then we'd know which route to take.
[doublepost=1528126709][/doublepost]
Sorry @W1SS, I was posting my question as you were posting your clarification. Could you link to your post explaining the recommended route to save people searching (there are lots of pages now)?
Yeah I think we all know that a full (over) install will overcome the problem, but we really want an answer as to why the update fails at updating the Recovery HD, and if we can overcome that without resorting to a full install.
I believe @Czo intentionally caused this to happen with the Software Update Patch, to prevent the system from overwriting a patched Recovery HD. I don't see the Recovery HD update as being necessary, so it should be just fine installing 10.13.5, even when that error does occur.
Don't we ultimately want the Recovery HD to be updated though (obviously without breaking the system)? What kind of updates are they?
The Recovery HD is nearly useless, especially on these unsupported machines. Anything Recovery HD can do can be done by booting off a USB installer drive. These Recovery HD updates literally do nothing but update the system version of the Recovery HD (and consequently removes the patches that makes it bootable on these unsupported systems).
I am updating via the Combo update, modified to install on a MacPro 3.1 rather than using the App Store, just something I prefer to do, so the software update patch should not be involved using the Combo or indeed the Delta.