Is the full 10.13.5 installer download now available through the patching tool?
I don't mind doing this upgrade route instead of through the app store, so long as the patch tool has been confirmed to work for MacPro3,1.
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
Is the full 10.13.5 installer download now available through the patching tool?
I don't mind doing this upgrade route instead of through the app store, so long as the patch tool has been confirmed to work for MacPro3,1.
Looks like when I ran the Post Install Patch again on startup, chose the correct patch options this time, then selected rebuild the cache, then selected reboot the audio just started working again when I logged back into my Mac.
So selecting rebuild cache might have been the solution apparently, I'm guessing. Whatever happened it worked to resolve the issue thankfully. Pretty annoying and frustrating having no audio on your Mac.
Last edited:
Can I get in on that, dosdude1? I am having the same trouble where the laptop powers on to a black screen with the fans going. Exactly the same symptoms as Gunner12 has described.
I am in Canada so I can ship it over to you.
Thanks
Imran
dosdude1 please disregard the message above, the laptop finally booted up. I will reach out to you again, if its not recoverable.
Thanks,
Imran
Yeah, that seems what happens most of the time. Usually it'll hang a bit on the first boot after flashing the firmware, or you just have to shut it off, and turn it back on again. Afterwards it should work normally.
Seemed to take longer than normal to boot but its up now and it shows 10.13.5.
Thanks again for all you have done to support older and fully capable macs !!
Yes, the full 10.13.5 installer is available through the patching tool.
I did upgrade my mac pro 3.1 with a ATI Radeon HD 5770 using the usb key full installer over a previous 10.13.4 instalation and everything is working normaly no problem.
Tip of the hat and big tanks to dosdude1.
The 10.13.5 update was quite a mess for my iMac 9,1. After the MAS update failed (as posted yesterday), the modified combo update also failed. I had done the 13.4 update mod before without issues.
I ended up creating a whole new installer and clean installed 10.13.5 then migrated everything over from a TM backup.
I do have one question for @dosdude1, during the post install patch for the iMac 9,1 the Recovery Partition Patch was not selected by default. I manually selected it thinking it might help with future MAS point updates. Should I not have selected that patch? Or is it ok?
I ended up creating a whole new installer and clean installed 10.13.5 then migrated everything over from a TM backup.
I do have one question for @dosdude1, during the post install patch for the iMac 9,1 the Recovery Partition Patch was not selected by default. I manually selected it thinking it might help with future MAS point updates. Should I not have selected that patch? Or is it ok?
The same thing's happened to me with the 10.13.5 update on my MacBookPro 5,1 as with previous updates. Everything seems to go fine but at the end it brings up a dialog saying that there were errors running scripts from the xxxxRecoveryHD.pkg - didn't catch the exact name because it disappeared too quickly. In previous updates I've seen a similar error in the installation log but this is the first time I've seen a dialog box. About This Mac says 10.13.5, but it doesn't show in the Installations log, or the App Store history. Messages Preferences doesn't offer me the iCloud option, so I'm guessing 10.13.5 wasn't actually fully installed. Any help?
Edit: error running scripts from macOSUpd10.13.5.RecoveryHDUpdate.pkg
Edit2: I see this in the log
replaceRecovery: Attempting to create temporary mount point
replaceRecovery: Attempting mount of /Library/Updates/09186781/macOSUpd10.13.5.RecoveryHDUpdate.pkg to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.icvpufMH
replaceRecovery: hdiutil: attach failed - Device not configured
Edit: error running scripts from macOSUpd10.13.5.RecoveryHDUpdate.pkg
Edit2: I see this in the log
replaceRecovery: Attempting to create temporary mount point
replaceRecovery: Attempting mount of /Library/Updates/09186781/macOSUpd10.13.5.RecoveryHDUpdate.pkg to /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.icvpufMH
replaceRecovery: hdiutil: attach failed - Device not configured
Last edited:
Thank you so much @dosdude1 for being such a life saver!! El Capitan was a pain in the neck and I was about to give up on it, until I made the jump from El Capitan all the way to High Sierra, and I can say it is one of the best things happened to my old machine in years.
I upgraded my MacBook 5,1 unibody late 2008 to 10.13.5 almost trouble free. I encountered a black screen after rebooting where you can wait or force restart the machine if takes long to boot.
Also, I had to reinstall the night shift patch as it seems the update disabled it.
Other than these two minor things, it runs flawlessly on my almost 10 years old MacBook.
I upgraded my MacBook 5,1 unibody late 2008 to 10.13.5 almost trouble free. I encountered a black screen after rebooting where you can wait or force restart the machine if takes long to boot.
Also, I had to reinstall the night shift patch as it seems the update disabled it.
Other than these two minor things, it runs flawlessly on my almost 10 years old MacBook.
dosdude1,
First, thanks for all your time and efforts. I have a successfully boot-rom-patched MacPro 3,1 but I'm having problems creating a USB installer for 10.13.5 using your 2.6.2 patcher. I've tried 4 times, using both a full Apple 10.13.5 installer directly from Apple and downloaded using your tool (and downloaded this tool twice too). Each time I get a successful build but the US installer does not show in the boot screen when booting with Option pressed. If I move the USB installer to a regular supported Mac, it shows up fine in the boot screen with Option pressed. I have also tried building the USB installer on a supported Mac and on the boot-rom-patched MacPro 3,1. Same issue.
I've never seen this problem before and this USB key has been used previously to build full installers for 10.13.4.
Any ideas would be welcome. I include a screenshot of the USB installer file system—and of the EFI partition on the USB installer, which seems to be empty; is that as it should be?
Last edited:
So after downloading the standalone Combo update 10.13.5 and modifying the Distribution file so it will install on my old MacPro 3.1 it gets to near completion, but fails. The install.log reports that it failed at the point of trying to update the Recovery HD. This is something that happens every time whilst updating the OS so would like any input as to why this is happening. From what I recall there were never such problems with installing modified Combo updates in Sierra.
Are you getting the same error as I'm getting with the incremental update?
replaceRecovery: hdiutil: attach failed - Device not configured
Trust me, 10.13.5 is installed. The patch for the App Store prevent updating recovery partition because if Apple made any changes on it, it need to repatch to made bootable again. Every update "fails" to install, if that update contains anything for the recovery.
Check all the requirenments for messages in the cloud, this option is not visible on mac, if you logged in to iCloud and iMessage with different AppleID.
I'm logged in to iCloud and Messages with the same Apple Id, but I don't see the new check box in Messages pref pane.
Which version of Messages is the correct one for 10.13.5? Mine says "Version 11.0 (5500)".
I didn't quite understand what you meant regarding the recovery partition. Why would the script fail during "hdiutil attach"?
Last edited:
All of my macs are running Messages "Version 11.0 (5500)" and all running 10.13.5 (multiple models). If you logged in with the same Apple ID, the "enable messages in cloud" checkbox must be visible on the prefs. Check it again on the accounts page on the settings pane in messages.
The patch prevents App Store to download updates for recovery. So if the update file are missing, no one can execute anything from it.
It's not there. I've even signed out of iCloud and signed out of Messages, and back in. No difference.
So, with the recovery update - is there some magic patch in the download of the 10.13.5 update from the App Store that prevents it downloading anything to do with recovery? Because my 10.13.5 download included a macOSUpd10.13.5.RecoveryHDUpdate.pkg, whose scripts it tried to execute. Are you saying that it shouldn't have been included?
[doublepost=1528020397][/doublepost]Messages in iCloud needs two factor authentication—have you signed up for it with Apple?
You guys with the recovery updater problems: did you convert from HFS to APFS with Disk Utility and thus don't have a recovery volume inside the APFS container? I have a normal APFS layout (main volume, Preboot, Recovery, VM) on my iMac7,1 since I installed HS from scratch, and I didn't have this recovery updater issue.
If you don't already have the recovery volume inside the APFS container (or any of the other volumes HS expects on APFS, do a 'diskutil list' in Terminal to be sure) you could try the following in Terminal to add those volumes and see if it works with the updater:
Where X is the disk number of the APFS container not your main HS volume:
If you don't already have the recovery volume inside the APFS container (or any of the other volumes HS expects on APFS, do a 'diskutil list' in Terminal to be sure) you could try the following in Terminal to add those volumes and see if it works with the updater:
Where X is the disk number of the APFS container not your main HS volume:
Code:
diskutil apfs addVolume diskX APFS Preboot -role B
diskutil apfs addVolume diskX APFS Recovery -role R
diskutil apfs addVolume diskX APFS VM -role VNo.
On the face of it, this should be easy to debug for someone with any knowledge of "hdiutil attach", because that's what's failing. It's trying to mount the RecoveryHD.pkg on some temporary folder in /var/folders/zz. The one thing that jumps out at me is that /var/folders/zz has an extended attr (it's got a @ after in the ls -l listing) which is com.apple.rootless (something to do with SIP?). Maybe someone who knows more than me can say whether this is significant.
Last edited: