Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
That's the new APFS booting implementation. Unfortunately, you cannot hide it, but it will only show at boot time. Doesn't negatively affect the system at all.
It is great that it allows unsupported systems to use APFS just a bit unfortunate it is not completely seemless. However everything else went very well so far.
 
It is great that it allows unsupported systems to use APFS just a bit unfortunate it is not completely seemless. However everything else went very well so far.
I switched back to HFS+ for High Sierra for this reason. These are my secondary computers and will be used by n00bs who are not used to seeing this, so I'd rather have the Apple-like boot process that you can get with HFS+ installs on these unsupported machines.

---

BTW, the install process is faster off USB. I have a supported machine, a 2017 MacBook getting this installed off the installer on its own PCIe SSD, and an unsupported machine, a 2009 MacBook Pro 5,5 with USB installer. It seems to be going significantly faster off the USB drive, despite the laptop only having USB 2 and having a much, much slower CPU.
 
That's the new APFS booting implementation. Unfortunately, you cannot hide it, but it will only show at boot time. Doesn't negatively affect the system at all.
Love your utility! Did I do something wrong? I have a MacBook 5,1 (late 2008 Unibody) with SSD and the install left the drive as HFS+. Maybe that's just as well, but wondering.
 
MBP5,1, upgrade went well, but it didn't convert to APFS and booting to recovery mode, using disk utility, the convert option is greyed out. I have a Crucial 1TB MX200 SSD, currently Mac OS Extended (Journaled). Is it possible the mac thinks it's a fusion drive and that's why it won't convert?
 
MBP5,1, upgrade went well, but it didn't convert to APFS and booting to recovery mode, using disk utility, the convert option is greyed out. I have a Crucial 1TB MX200 SSD, currently Mac OS Extended (Journaled). Is it possible the mac thinks it's a fusion drive and that's why it won't convert?
Just boot to your patched USB installer drive and unmount the volume first, then Disk Utility should allow you to convert it. Be sure to apply the APFS patch using the post-install tool after doing so, or the volume will not be bootable.
 
  • Like
Reactions: elxeneize
Just boot to your patched USB installer drive and unmount the volume first, then Disk Utility should allow you to convert it. Be sure to apply the APFS patch using the post-install tool after doing so, or the volume will not be bootable.

THANKS! That did it.
 
Installed on MacBook Pro 5,5. Seems to work great so far! I'll wait a little before switching to APFS to see if it survives system updates.
 
Hrmmm. Seemed to go OK up until final boot sequence after typing in password to unlock drive for booting. Pinwheel went around for a bit. Progress bar at about halfway. And not appearing to be moving. Verbose mode gets up to the following that flashes over and over top left.

IOConsoleUsers time(0) 0->0, Lin 0, llk1,
IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0


Edit: Alright. Appears doesn't currently boot with BOTH video cards in.

HD2600XT works fine, only when I remove the RX480.

MacPro 3.1
 
Last edited:
@dosdude1 , I can confirm that this works on MBP 5,4.

The odd thing is that I had downloaded High Sierra on a different machine, used the patcher but somehow the beta was installed 17A362a. I suppose I could try the installation again.
 
@dosdude1 , I can confirm that this works on MBP 5,4.

The odd thing is that I had downloaded High Sierra on a different machine, used the patcher but somehow the beta was installed 17A362a. I suppose I could try the installation again.
You must have used an old version of High Sierra Patcher. The latest one (v 2.3.1) was updated to download the final release.
 
That's the version I believe that I used hence the confusion. Anyways, I can try it again.

Separately, will the previous trick of using SUVMMFaker.dylib to fake out App Store on Sierra work under High Sierra?
 
That's the version I believe that I used hence the confusion. Anyways, I can try it again.

Separately, will the previous trick of using SUVMMFaker.dylib to fake out App Store on Sierra work under High Sierra?
Yes. That's included with the patch.
 
I successfully upgraded my MacBook 5,1 to HS using dosdude1's tool. Thank you so much for all you've done to keep our old Macs going! Like some others here have mentioned, the HS installer did not convert my SSD to APFS (I did an in-place upgrade, rather than a clean install). Is that because it is an unsupported machine? I was under the impression that SSD's would be automatically converted, with no option to opt out, or is that only for supported machines?
 
I successfully upgraded my MacBook 5,1 to HS using dosdude1's tool. Thank you so much for all you've done to keep our old Macs going! Like some others here have mentioned, the HS installer did not convert my SSD to APFS (I did an in-place upgrade, rather than a clean install). Is that because it is an unsupported machine? I was under the impression that SSD's would be automatically converted, with no option to opt out, or is that only for supported machines?
It didn't get converted due to the method used for install. It only gets converted when running the "Install macOS High Sierra App" from within OS X. This, obviously, only works on supported machines. If you do want to convert it to APFS, though, you can do it with Disk Utility. Just make sure to apply the APFS patch in the post-install tool afterwards.
 
I just updated it to support the final release.
After reading the above post, I went to dosdudes website and downloaded both the the latest patcher (2.3.1) and the new install package.
After going through the usb creation and slowww install I ended up with High Sierra Beta5 (17A330h), WTH?

Screen Shot 2017-09-25 at 8.36.32 PM.png
 
After reading the above post, I went to dosdudes website and downloaded both the the latest patcher (2.3.1) and the new install package.
After going through the usb creation and slowww install I ended up with High Sierra Beta5 (17A330h), WTH?

View attachment 721193
What the... That's really weird... It's literally downloading the files STRAIGHT from Apple's server... IDK what they're doing.
 
Ok. So I'm not NUTS. =D

Couple of other observations, somehow my various network settings got blown away as well as the hostname.

  • VPN config got deleted
  • hostname defaulted back to MacBook Pro
  • ntpq -p fails. It looks like NTP is not running. Did HS switch to something else? This seems to be the case across multiple HS installs (MBP, VM and Mini)
 
Last edited:
After reading the above post, I went to dosdudes website and downloaded both the the latest patcher (2.3.1) and the new install package.
After going through the usb creation and slowww install I ended up with High Sierra Beta5 (17A330h), WTH?

View attachment 721193
Oh, wait a second... Did you use the Google Drive link? If so, that's why... LOL. I haven't been able to update that yet.

Went ahead and removed the link to avoid confusion.
 
Last edited:
It didn't get converted due to the method used for install. It only gets converted when running the "Install macOS High Sierra App" from within OS X. This, obviously, only works on supported machines. If you do want to convert it to APFS, though, you can do it with Disk Utility. Just make sure to apply the APFS patch in the post-install tool afterwards.

According to your tutorial, that is a clean install. What do I do if I want to upgrade to High Sierra on top of my 10.12 Sierra? Can I just straight away use your patcher, download High Sierra from the tab, and then start operation, all done within, without creating a USB stick? Cheers mate.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.