Installation Failed! High Sierra.

My hard disk is Samsung EVO 850 500GB SSD.

That's the reason.

You can see for yourself: "An error occurred while verifying firmware". Apple does not develop firmware for devices they do not incorporate in the products they sell, and they do not consider internal a storage user-replaceable option. In other words you're on your own. Samsung "EVO" SSDs are notorious for that problem and others. It will fail soon enough anyway.

Either replace it with a SSD known to work with macOS, or a conventional hard disk drive. If you want to continue using the Samsung SSD, then restore your Mac from a Time Machine backup and do not upgrade.

Try a PRAM reset:

macOS Sierra: Reset your computer’s NVRAM or PRAM

Then try and install.

FWIW, Samsung SSDs, especially the pro series seem to problematic

over the years in Macs.

Santhosh

Try this link first- you may need to update your firmware:

https://support.apple.com/en_US/downloads/macnotebooks

This whole thing is a joke. I’m starting to think the issue is with the Samsung SSD. I think Apple did something with the firmware on both the drive and the system.

I have two Macs. One updated to High Sierra and the 2009 I’ve been working on. I was on the phone with Apple support for HOURS. We tried erasing and reinstalling every which way you could imagine. Used two different external installers and you can’t install over Target Disk Mode.

And there seems to be obvious bugs in Disk Utility.

I’ve tried everything from installing from two different external installers

I’ve tried installing from recovery modes from:

- Sierra SSD environment (working)

- Sierra HDD environment (working)

- High Sierra SSD environment (working)

- High Sierra HDD environment (working)

Ditto using Disk Utility from all said environments. Tried erasing/formatting and then reinstalling.

By the way, you can install High Sierra on an external SSD over Thunderbolt.

NO GO.

Im going to remove the drive I’m going to research a way to ensure the EVO is erased *completely* because something tells me it isn’t being erased completely, then installing HS using my Thunderbolt Dock onto the drive and then make sure I can boot to it then install it back in.

This has been the absolute WORST install experience ever. Good thing I backed up my data. The goal now is to try and wipe, install and then call Apple and have the guy help me migrate my account info from the backup onto the fresh install.

Somehow I have a feeling that either Samsung, Apple or BOTH are responsible for this fiasco.

It’s a **** show.

I realize this isn't an EXACT answer to the specific question, but since this is a top hit on the subject of failed installs, I figured I'd add this here.

I finally decided that others would have worked out the kinks to a High Sierra upgrade, so I went ahead and upgraded my early 2011 MBP. (I should note, with a SanDisk Extreme SSD - previously tweaked to support TRIM, at least I THINK.)

Suffice to say, after the first reboot I would get the blinking crossed out circle. Forcing a reboot yielded the same.

However, for the first time in FOREVER, resetting the PRAM fixed the problem.

The system did hang up again later at the end of the upgrade. A forced reboot there fixed the problem.

I'm not sure what it was, but the machine did make that loud/low tone that I usually associate with a firmware update during the upgrade. I thought I was up to date on FW, but apparently not.

Regardless, I seem to be running fine now, but it was NOT a smooth upgrade at all.

Right, I said that Sierra is unavailable from the App Store. Boot into the Recovery Disk (I hold down the option key at boot and then choose the Recovery Disk) and then choose to Reinstall MacOS - I think it's the second option from the top in the window. That should give you a reinstall of Sierra.

This whole thing is a joke. I’m starting to think the issue is with the Samsung SSD. I think Apple did something with the firmware on both the drive and the system.

I have two Macs. One updated to High Sierra and the 2009 I’ve been working on. I was on the phone with Apple support for HOURS. We tried erasing and reinstalling every which way you could imagine. Used two different external installers and you can’t install over Target Disk Mode.

And there seems to be obvious bugs in Disk Utility.

I’ve tried everything from installing from two different external installers

I’ve tried installing from recovery modes from:

- Sierra SSD environment (working)

- Sierra HDD environment (working)

- High Sierra SSD environment (working)

- High Sierra HDD environment (working)

Ditto using Disk Utility from all said environments. Tried erasing/formatting and then reinstalling.

By the way, you can install High Sierra on an external SSD over Thunderbolt.

NO GO.

Im going to remove the drive I’m going to research a way to ensure the EVO is erased *completely* because something tells me it isn’t being erased completely, then installing HS using my Thunderbolt Dock onto the drive and then make sure I can boot to it then install it back in.

This has been the absolute WORST install experience ever. Good thing I backed up my data. The goal now is to try and wipe, install and then call Apple and have the guy help me migrate my account info from the backup onto the fresh install.

Somehow I have a feeling that either Samsung, Apple or BOTH are responsible for this fiasco.

It’s a **** show.

Same problem here.

Nov 2 21:25:17 MacBook-Pro OSInstaller[544]: ROM Features returned: 4228117814

Nov 2 21:25:17 MacBook-Pro OSInstaller[544]: ROM does not support APFS

Nov 2 21:25:17 MacBook-Pro OSInstaller[544]: Clearing automation and attempting to rebless.

Model Name: MacBook Pro

Model Identifier: MacBookPro11,5

Processor Name: Intel Core i7

Processor Speed: 2,5 GHz

Memory: 16 GB

Boot ROM Version: MBP114.0172.B07

SMC Version (system): 2.30f2

Did you restart your computer and try again?

Ok, so tomorrow my goal is to look into this:

https://bombich.com/kb/ccc5/high-sierra-testing-and-known-issues

Apparently you cannot erase a volume unless you unmount/dismount the drive FIRST. Then erase.

I forgot to mention that I tried making another bootable High Sierra instal stick out of a 32GB USB thumb drive I had laying around. Just for stihs-and-giggles I erased and then immediately ran FirstAid and sure enough it threw an error. Got it to crest the external installer but it wasn’t able to install correctly.

Something got seriously corrupted on that Samsung Evo 850.

If everyone just gets in touch with Apple (it's free) I think we all might get a resolution to this obvious and annoying problem.

Same here! Have this error on MBP 13 2015 with original Apple SSD. Try to update from 10.12.6 with no luck. Log:

Sep 26 06:16:18 MacBook-Pro OSInstaller[547]: ROM Features returned: 4228117814

Sep 26 06:16:18 MacBook-Pro OSInstaller[547]: ROM does not support APFS

Sep 26 06:16:18 MacBook-Pro OSInstaller[547]: Clearing automation and attempting to rebless. source volume: SKDisk { BSD Name: disk0s2 Mount point: /Volumes/Macintosh HD Role: kSKDiskRoleLegacyMacSystem Type: kSKDiskTypeHFS } rebless: 46CC9562-A01E-3E91-8A8B-BDD957042114

Sep 26 06:16:18 MacBook-Pro OSInstaller[547]: OSIInstallElement <OSIVerifyROMElement: 0x7fbcb3f60ed0> errored out:Error Domain=com.apple.osinstall Code=512 "При проверке прошивки произошла ошибка." UserInfo={NSLocalizedDescription=При проверке прошивки произошла ошибка.}

Sep 26 06:16:18 MacBook-Pro storagekitd[548]: storagekitd: copyDiskForPath returned nil, error: -69808

Similar issue. I was updating a late 2009 iMac i7. About a year ago I swapped out for 2 GB Samsung Evo. All was working perfect with the update then an error saying system can’t be updated.

I can still gain access to all the data via Target Disk Mode, but no way to effect repairs. I do see the Mac HD as well as a “PreBoot” disk and a “recover” disk.

I have a hunch that it performs a firmware update where it IDs the particular system and probably expects that there is a spinny disk still in there. Apple should probably actually verify what type of storage exists and build toward that.

I still think it has to to with firmware and maybe the fact that Apple is targeting machines expecting to find the OEM configuration.

I have a volume that is APFS which has sub volumes: Preboot, Macintosh HD, Recovery.

All the data is still intact, but I can’t seem to have High Sierra attempt to re install

same problem with a Mac Book Pro late 2011, i have Mac OS X.12,Linux debian and windows 10 on a MBR disk,

i know the EFI is bugged on those mac , for this reason no GUID triple boot is possible,High Sierra refuse to install on MBR disk ,so i installed on an external disk with GUID and also tried a patched MBR install of high sierra but no luck!

even on a pure GUID disk the install fails with a "firmware check error"

Damien