Mac Os High Sierra Installer Dmg

[Cre Moonin]

Have you tried installing OSX on an older vintage machine recently? Well, I came across a unique problem when trying to upgrade my HDD to an SSD on my Vintage 2009 iMac. I thought I would share my experience and potential work around to get OSX high Sierra (the latest compatible OSX for my system) working on my iMac (2009).

Firstly after coming from a windows environment where you can grab a ISO and just create a bootable disk quite easily. However on a new Mac (I currently use the new M3 MacBook Pro) it is impossible to download High Sierra thought the mac store unless you have an eligible machine.

It seemed quite a simple solution initially, and that I would download Sierra and then upgrade after a successful install. Again this proved fruitless as the ISO that I downloaded just had a .pkg file in the .dmg not a bootable usb drive!

I managed find a copy that someone had shared online (this is defo not recommended but I was frustrated after hours of getting nowhere), I was concerned about the download having a virus etc. But the website seemed legit and as this wasn't my main machine, I thought why not!

Below is the custom commands I then used in terminal to create the boot disk. The first step removes the signature error you receive when trying the run the command in step 2, so by doing the modification in step 1, it then in turn allows the installer to run in step 2.

Unfortunately, I came across an issue after trying to install the OS. It stated the install was corrupted, but after doing some research I found out this was due to the install being too old and apple adds a signature to the OSX download which keeps it current, again another annoying step to work around!

I should take this opportunity to report that the resulting volume, while it did not lead to a reinstallation of the operating system, did successfully boot. It did, however, leave the /macOS Install Data folder on my install partition, which I'm about to delete, since the converted partition already boots into a working installation.

I converted the TimeMachine volume of to APFS as it showed up under the Edit Menu in Disk Utility. I decided that the Boot Volume should also be converted but did not see the Convert to APFS volume under the Edit menu. I know from times past the cmdline DiskUtils has way more options than the GUI. I suspected I could conver to APFS using Terminal+diskutils. I did that conversion to disk0s2 (my HFS+ data volume).

Followed that same advice, I did a dirty re-install of High Sierra Beta 7, that fixed enough of the partition entries and blessing to force it to boot the Disk02s. I just had to be very, very patient, and keep my hands off the mouse and keyboard out of fear of interrupting whatever process it was going through to tie the boot files to the APFS converted disk partition.

It's really not worth the effort of getting it up and running again even if it's just a sacrificial test machine or VM. If it does show Convert to APFS under the Edit menu, give it shot. I converted my TimeMachine volume to APFS, but boot volume wasn't having it. Using Terminal and diskutil cmdline, forced it, but then it wouldn't bless.

I had this same problem happen to me recently. Went to reinstall high sierra (was currently running beta 8), went into recovery mode (Command +R at boot), erased the hard drive in diskutility and reformatted it in APFS encrypted. Went into the reinstall macOS and as it worked through the 8 minutes it would stop at the end with a pop up message saying "Could not create a preboot volume for APFS". This made things interesting so I tried reformatting the drive with the unencrypted APFS and still same error. I eventually made a really stupid move from diskutility and from the disk0 drive itself I right clicked and chose to Erase, somehow thinking what harm could be done at this point, thinking it would erase and reappear. Well that never happened. The internal disk0 drive did not come back. I ended up trying to create a backup from another computer and installing the backup to that. This didn't work either since it couldn't find the internal hard drive.

I created a bootable thumbdrive with high sierra from another computer and used that to boot up, and still the internal drive wasn't an option on diskutility. what eventually worked was somehow the drive appeared when I booted into recovery mode with the install thumbdrive and having another thumbdrive in the internal drive finally appeared. I was able to then format it again as APFS. It then populated when I did the reinstall from the install thumbdrive. After that it worked fine.

In hindsight I know I shouldn't have erased that drive, and I likely could have reformatted disk 1 from terminal and seen if it would repopulated in diskutility then. But either way the lesson here is don't erase the internal hard drive from diskutility. If you get that preboot error I would suggest creating a bootable thumbdrive from another computer and using that to enter recovery mode and doing the install this way.

Hi, I'm currently facing the same "Could not create a preboot volume for APFS" issue after i erased the drive from diskutility. I was on the latest version of High Sierra yesterday. Kindly, give me the lines of code necessary to create the bootable usb (especially with the changes you've mentioned). I'm new to macOS. So please bear with me.

I'm having the same issue on a MAC BOOK AIR 2017. First time it gave the error could not contact sever but after countless efforts I managed to to download via the MAC internet recovery afte the download this error popped up.Is there a solution for this ?

Hi I had the same problem. Did the same thing for about 3 times. Format the drive first to apfs 1.Power down the mac. 2.hold the Option-Command-R and power button. 3.a world logo will show and start loading. 4.reinstall mac os in recovery. 5.no more error "could not create a preboot volume for apsf install" Hope this helps

Now how do you convert to APFS? If you really want APFS then back your data up. It could go south. You can try to convert it from disk utilty while in recovery mode. You will find it under the "edit" menu once you've selected the drive.

Have same problem. MacBook Pro (Retina, 15-inch, Mid 2014). Am currently running 10.12.5 (non-beta version). Got the "verifying firmware" error on startup. Tried the cleanup procedure you described but it resulted in the same problem.

At the end of May, I did a fresh install of my OS -- backed up data, erased hard drive, installed 10.12.5 from a bootable USB, manually dragged-and-dropped appropiate files back to my system. So, all in all, I'm starting from a pretty clean base. Had Sophos Cloud installed but uninstalled it prior to trying to install the High Sierra beta.

Just to confirm: You removed the installer, the lpdf and eagle folder, logged out and back in of App store, downloaded the "Public Beta Access Utility" once more, ran it, then downloaded the high sierra installer?

The first time I tried the workaround, I did step 3-5 (deleted original beta files) then shut down. Did steps 1-2 and then steps 6-7. I don't think deleting the files first should have made any difference. My guess is step 8 is where the problem lies.

I'm including a link to a 20-second video I filmed using my iPhone while I walk through the install process (deleted a chunk in the middle to remove my authentication, but that's it). As you can see, at no point do I have an option to install without APFS. My drive is formatted as Mac OS Extended (Journaled). So maybe it's because I don't have an option to omit APFS this that the installation fails?

1. Only the very first time that I walked through the suggested workaround was there an "Eagle" folder to delete in the ./Library/Documentation/Resources path. Even though I've repeated the workaround a few times now (even re-downloading the beta installer each time), this "Eagle" folder has never reappeared.

2. You'll see in the movie that after I authenticate, for just a moment afterwards, there is "about 6 minutes remaining". But this message disappears a moment later and I'm asked to restart to complete the installation. I wonder if this indicates something is being skipped that is crucial to the upgrade?

3. My MacBook is probably configured in typical fashion but I do perhaps operate with one variation from the norm; I doubt this should be a problem but I mention it on the off-chance it is. I normally work within a standard (non-admin) account called "chris". This is the account attached to the iCloud ID that is registered with the beta program. I have a separate admin-level account ("panopticon") that I use strictly for authenticating installations. I have tried installing the beta while logged in as "chris" (still requires authenticating as "panopticon") and also logging in directly as "panopticon" to start the install. Both methods produce the same result. The "panopticon" account does not have any iCloud ID attached to it. I doubt this has any bearing but if other users with this same problem have the same configuration, then maybe it is somehow a factor.

If there are any logs from my system that would be helpful to diagnose this issue, please let me know and I can submit them. The link below is the clip I mentioned earlier that shows how the installation goes -- had to upload that to one of my own websites since it doesn't look like I can attach it here.

Shut down, booted up again this time on a macOS 10.12.5 USB drive and was able to use Disk Utility on that system to at least format the internal drive. Shut down, booted up on the beta USB a second time. Began install of beta but this time I left the drive formatted as Mac OS Extended. Doing it this way, I now DO get an option to "Upgrade to APFS" which I DID NOT get when I was trying to do the in-place upgrade on my own MacBook Pro. I think this was the checkbox you were looking to have me disable -- in this instance, it is disabled by default.

I've got screenshots documenting all this stuff. Doesn't look like there's any way to post screenshots here though. I wrote a good set of documentation on my efforts to do the in-place upgrade the other day but included a link to a movie stored on my own server (demonstrated the problems with the upgrade process) -- that mesage is still listed as "being moderated" and doesn't appear to be visible to the community at large here. So I'm not going to post pictures here with links to non-Apple sites; otherwise, sounds like people may not see this message.

c80f0f1006