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
Perhaps we'll be able to use this new patcher with Beta 5 tomorrow (or Thursday/Friday).
I tried setting up the USB using V1.1, the latest one you released, and it boots fine for about 3-4 seconds then all of a sudden all the processes start failing, too many corpses being created is at the end of each line. Any suggestions good sirJust finished updating High Sierra patcher, now working with the native High Sierra installer (well, sort of). No longer needing to distribute a copy of BaseSystem.dmg with the tool significantly reduces the download size, from about 500MB down to ~51MB. Download available here. Enjoy!
EDIT: I restored the USB multiple times to make sure it wasn't just a glitch or something. I also redownloaded the installer app each time because I noticed that after a few times, if you try to just open the installer app it will say it is damaged. So each time I downloaded it I made sure it would open fine and then used it to restore the USB
Hmm, it may be something to do with later versions of the installer... I've been using the Public Beta 2 installer for my testing.
Try unzipping the downloaded zip file using Pacifist and not the unarchiver that comes with macOS.
I found that unarchiver thinks zip files created by dosdude are damaged in some way too.
If a full beta 5 installer arrives tomorrow, I'll test the new patcher on it.
I found that unarchiver thinks zip files created by dosdude are damaged in some way too.
If a full beta 5 installer arrives tomorrow, I'll test the new patcher on it.
Last edited:
I’m really happy about all the work and energy you put into to this. It’s so awesome, and I fully understand the priorities that you’ve just mentioned. However, I hope that APFS support will be added at some point. Many of us with old macs have upgraded with SSD disks, and APFS is among other things optimized for running on SSD disks
Just in case apfs on older macs does not pan out in the longer term, openzfsonosx provides a robust modem file system that can boot older unsupported macs too! Some would argue it is much much better than apfs.
https://openzfsonosx.org/forum/
https://openzfsonosx.org/forum/
Has anyone been able to get 17A291m to apply the Public Beta 3 software update without the process hanging? With the current Patch Updater installed, on a MacPro 3,1, I find that the process hangs at around 75% on the software update progress bar with 16 minutes left. If I hard reset the machine, it claims to have 17A315i installed but the App Store Update window history doesn't show Public Beta 3 as being installed.
I installed PB3 on a MacPro 3.1 that had PB2 via the App Store.
Same thing the progress bar stalled 75% across with 16 mins remaining. I left it for one hour and did a power down. Restarted and in About This Mac the new Beta build number is displayed. It is not displayed in the System Report, Software Installations section, nor is it displayed in the 30 day section of the App Store Updates, but I'm not concerned about that as the recent update from Sierra 10.12.5 to 10.12.6 was not displaying in the 30 day list either.
The install log does show that PB3 is installed as does the fact that Nightshift is not available again and has to be rejigged to work again.
Has anyone with these hung software updates tried looking at the appstore and install logs to see if there is any error messages or what exactly the installer did just before the forced restartt? Also, if someone is repeating the software update today, perhaps hitting the command-V key combo during the SU restart will clarify where the hang is during the install.
Which patch did u use? My first patch sometimes hang (it's not a hang, Apple's update scripts waiting for the firmware update to finish, but our machines never will be getting any update anymore, so it's waiting forever) but the current one most of the time can install updates. The "hang" occurs on the last step (after every one package is installed) so after you hit a reboot, the OS are updated.
Hi everyone, even though I don't have expertise in this stuff, Beta 5 is now out, so I just wanted to let you guys know, also I wanted to say thank you everyone on this forum for helping us.
I can confirm that it's because of the installer. I used your tool with developer beta 4, and it successfully creates the drive but it does not boot... Then I tried it with public beta 2 and it boots and works properly, so yep definitely something with the installer....
Thanks for everything!
I assumed that I used the patch which was downloaded by the Patch Updater application in the Utilities folder which I launched after installing 17A291m using the High Sierra Beta dmg and v1.1 High Sierra Patch application from http://dosdude1.com/highsierra/. After launching the Patch Updater, it did download a new patch with a dialog appearing that noted a dylib fix and a fix to set the SU repo to the Public Beta one.
I wonder if the patch was really applied by the Patch Updater or was just downloaded? After the Patch Updater ran, the App Store system preference panel still showed no beta downloads as being enabled so I had to manually install the Beta utility to set that. Did I miss a step here? Do I have to manually apply the patch even after running Patch Updater to download it?
I also noted that the patching offered in the High Sierra patch installer for MacPro 3,1 didn't enable the Recovery Partition patching by default. Manually enabling that didn't seem to create a High Sierra Recovery Partition which could boot. Is that a known issue?
[doublepost=1502127242][/doublepost]Can someone clarify the correct usage of the Patch Updater application installed by the High Sierra Patcher v1.1? Do I need to perform an additional step to actually apply the patch after launching the application to download the patch update? It was unclear how the patch was supposed to be applied or if the Patch Updater automated the process as part of the update download.
I used dosdude's tool with the beta 4 release and it created the drive and installed and booted fine. Sometimes, booting is prevented by the GPU. On the Mac Pro 3,1 for example replacing the original GPU with a later non-Apple GPU (or even Apple GPU for a different model) will prevent the boot, so it may not be the patch causing your problem.
Well Im just a tester so technically in this area I am a complete newbie, you maybe right I don't know, but Im not the only one experiencing this issue, Im sure when @dosdude1 gets a chance he will look into it.
I'm about to try dosdude's new patcher from yesterday with the beta 5 install from today on a MacPro 3,1 so will post what happens.
[doublepost=1502146593][/doublepost]Bad news. Although dosdude's patcher from yesterday can build a USB boot stick using beta 5, when that boot stick is used to boot the 10.13 beta 5 installer on a Mac Pro 3,1, the boot bar reaches the end on the startup and the Mac Pro remains stuck at that screen and never proceeds to the OS X installer (see image below). It is also VERY slow getting to this point.
Right now I am trying the software regular update from beta 4 to beta 5 using the CzO/Dosdude SUVMMFaker.dylib patch and it is showing About 28 minutes. I'll post if it works.
If that fails (and it has with previous betas), I'll try building a boot/install USB with the old dosdude patch and beta 5.
[doublepost=1502146593][/doublepost]Bad news. Although dosdude's patcher from yesterday can build a USB boot stick using beta 5, when that boot stick is used to boot the 10.13 beta 5 installer on a Mac Pro 3,1, the boot bar reaches the end on the startup and the Mac Pro remains stuck at that screen and never proceeds to the OS X installer (see image below). It is also VERY slow getting to this point.
Right now I am trying the software regular update from beta 4 to beta 5 using the CzO/Dosdude SUVMMFaker.dylib patch and it is showing About 28 minutes. I'll post if it works.
If that fails (and it has with previous betas), I'll try building a boot/install USB with the old dosdude patch and beta 5.
Last edited:
Ater some oddities, the update from beta 4 to beta 5 using the Apple Software Update mechanism worked with the Czo/dosdude SUVMMFaker.dylib patch in beta 4.
Two things; first you need the macOS_Customer_Beta_Access_Utility.dmg installed in beta 4 to find the beta 5 update at Apple. Second, after the update downloads (1.59 GB) and the update install starts, at the point where it says About 20 minutes remaining, the screen went dark with an active cursor. I left it like this for 10 minutes and then gave up thinking the update install had failed. However, on the restart, it came to the setup iCloud screen and then went to the desktop—with About This Mac showing 17A330h (beta 5 is installed).
I have also built a USB installer using dosdude's patch (the older one using the El Capitan installer) prior to his newer release yesterday. It found the beta 5 dmg OK and built the USB stick but I have yet to see whether it can boot the Mac Pro 3,1 to the beta 5 installer stage.
[doublepost=1502149749][/doublepost]Good News. If you use the older patcher from dosdude (see screenshot) with the beta 5 download from Apple, it will build a USB booter/installer that can at least boot a MacPro 3,1 (see screenshot). I did not proceed to the actual install because I already have a working beta 5 install on the target disk.
Note to dosdude—at least for the MacPro 3,1, there is something not quite right with the latest patcher you released yesterday.
Two things; first you need the macOS_Customer_Beta_Access_Utility.dmg installed in beta 4 to find the beta 5 update at Apple. Second, after the update downloads (1.59 GB) and the update install starts, at the point where it says About 20 minutes remaining, the screen went dark with an active cursor. I left it like this for 10 minutes and then gave up thinking the update install had failed. However, on the restart, it came to the setup iCloud screen and then went to the desktop—with About This Mac showing 17A330h (beta 5 is installed).
I have also built a USB installer using dosdude's patch (the older one using the El Capitan installer) prior to his newer release yesterday. It found the beta 5 dmg OK and built the USB stick but I have yet to see whether it can boot the Mac Pro 3,1 to the beta 5 installer stage.
[doublepost=1502149749][/doublepost]Good News. If you use the older patcher from dosdude (see screenshot) with the beta 5 download from Apple, it will build a USB booter/installer that can at least boot a MacPro 3,1 (see screenshot). I did not proceed to the actual install because I already have a working beta 5 install on the target disk.
Note to dosdude—at least for the MacPro 3,1, there is something not quite right with the latest patcher you released yesterday.
Last edited:
wait, how were you able to update to beta 5 using App Store without it trying to do APFS? Since there isn't a checkmark doesn't it do it automatically?