Jump to content

[pre-release] macOS High Sierra

fantomas

By fantomas,
in New Releases and Updates

 Share
3,737 posts in this topic

Recommended Posts

Sherlocks
Sherlocks
Posted
Posted

My install USB uses IMac 11,2 and no FF FFM values. The installed Beta 6 uses 13,2 and only FF has a value. 13,2 I have used since El Capitan in-spite of being told I should use Mac Pro 5,1 ;)

What is clover revision?

 

나의 LG-F800S 의 Tapatalk에서 보냄

@Sherloks Succes MACOSXInstaller= startosinstall/ APFS Volumes

new MBP 9.1 :thumbsup_anim::thumbsup_anim:

i fond the solution its put out Windows 10 SSD :hysterical:

img_1218.jpg

 

 

img_1217.jpg

 

I post config.plist after install

 

NO FF

NO FFM

NO Plattform Future

NO MLB

NO ROM

Clover r4178 :wink_anim:

Great news. Just upload clover log after install HS DP6

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

here the LOG

 

0:600  0:000  Using ProductName from config
0:600  0:000  ProductName: MacBookPro9,2
0:600  0:000  Using latest BiosVersion from clover
0:600  0:000  BiosVersion: MBP91.88Z.00D7.B00.1708080744
0:600  0:000  BiosReleaseDate: 08/08/2017
0:600  0:000  Using FirmwareFeatures from config
0:600  0:000  FirmwareFeatures: 0xFC0FE136
0:600  0:000  Using FirmwareFeaturesMask from config
0:600  0:000  FirmwareFeaturesMask: 0xFF1FFF3F
0:600  0:000  Using PlatformFeature from clover
0:600  0:000  PlatformFeature: 0xFFFF
 
your log. you used FirmwareFeatures: 0xFC0FE136 is imac17,1 or newer's FF value. reference value of mbp9,1 is "0xC00DE137". if you have a time, try "0xC00DE137"
thanks in advance

 

Clover r4173

 

okay. thanks

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

 

0:600  0:000  Using ProductName from config
0:600  0:000  ProductName: MacBookPro9,2
0:600  0:000  Using latest BiosVersion from clover
0:600  0:000  BiosVersion: MBP91.88Z.00D7.B00.1708080744
0:600  0:000  BiosReleaseDate: 08/08/2017
0:600  0:000  Using FirmwareFeatures from config
0:600  0:000  FirmwareFeatures: 0xFC0FE136
0:600  0:000  Using FirmwareFeaturesMask from config
0:600  0:000  FirmwareFeaturesMask: 0xFF1FFF3F
0:600  0:000  Using PlatformFeature from clover
0:600  0:000  PlatformFeature: 0xFFFF
 
your log. you used FirmwareFeatures: 0xFC0FE136 is imac17,1 or newer's FF value. reference value of mbp9,1 is "0xC00DE137". if you have a time, try "0xC00DE137"
thanks in advance

 

 

okay. thanks

 

This is the smbios

NO FF 

<key>SMBIOS</key>
<dict>
<key>BiosReleaseDate</key>
<string>08/08/2017</string>
<key>BiosVendor</key>
<string>Apple Inc.</string>
<key>BiosVersion</key>
<string>MBP91.88Z.00D7.B00.1708080744</string>
<key>Board-ID</key>
<string>Mac-4B7AC7E43945597E</string>
<key>BoardManufacturer</key>
<string>Apple Inc.</string>
<key>BoardSerialNumber</key>
<string>C02331500GUDMT3CB</string>
<key>BoardType</key>
<integer>10</integer>
<key>BoardVersion</key>
<string>MacBookPro9,1</string>
<key>ChassisAssetTag</key>
<string>MacBook-Aluminum</string>
<key>ChassisManufacturer</key>
<string>Apple Inc.</string>
<key>ChassisType</key>
<string>0x0A</string>
<key>Family</key>
<string>MacBook Pro</string>
<key>LocationInChassis</key>
<string>Part Component</string>
<key>Manufacturer</key>
<string>Apple Inc.</string>
<key>Mobile</key>
<true/>
<key>ProductName</key>
<string>MacBookPro9,1</string>
<key>SerialNumber</key>
<string>C02L559ZF1G4</string>
<key>Version</key>
<string>1.0</string>
</dict>

 

 

 

I post config  see above post

configMB9.plist.zip

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

This is the smbios

NO FF 

<key>SMBIOS</key>
<dict>
<key>BiosReleaseDate</key>
<string>08/08/2017</string>
<key>BiosVendor</key>
<string>Apple Inc.</string>
<key>BiosVersion</key>
<string>MBP91.88Z.00D7.B00.1708080744</string>
<key>Board-ID</key>
<string>Mac-4B7AC7E43945597E</string>
<key>BoardManufacturer</key>
<string>Apple Inc.</string>
<key>BoardSerialNumber</key>
<string>C02331500GUDMT3CB</string>
<key>BoardType</key>
<integer>10</integer>
<key>BoardVersion</key>
<string>MacBookPro9,1</string>
<key>ChassisAssetTag</key>
<string>MacBook-Aluminum</string>
<key>ChassisManufacturer</key>
<string>Apple Inc.</string>
<key>ChassisType</key>
<string>0x0A</string>
<key>Family</key>
<string>MacBook Pro</string>
<key>LocationInChassis</key>
<string>Part Component</string>
<key>Manufacturer</key>
<string>Apple Inc.</string>
<key>Mobile</key>
<true/>
<key>ProductName</key>
<string>MacBookPro9,1</string>
<key>SerialNumber</key>
<string>C02L559ZF1G4</string>
<key>Version</key>
<string>1.0</string>
</dict>

 

 

 

I post config  see above post

 

strange. clover mbp9,1 default FF 0xC00DE137 if you dont have FF on smbios in clover 4178.

also shown 

0:600  0:000  Using FirmwareFeatures from config
0:600  0:000  FirmwareFeatures: 0xFC0FE136
 
hmm.
upload your dmi dump from darwin dump.
 
thanks
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

 

strange. clover mbp9,1 default FF 0xC00DE137 if you dont have FF on smbios in clover 4178.

also shown 

0:600  0:000  Using FirmwareFeatures from config
0:600  0:000  FirmwareFeatures: 0xFC0FE136
 
hmm.
upload your dmi dump from darwin dump.
 
thanks

 

Ok now I rename config.plist and I boot to this one  by default 

 

see log please

 

EDIT here  DMI Darwin Dump

 

 

 

 

Clover Boot Log.txt.zip

DMI Tables.zip

  • Like 1
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted

 

I again tried to install beta 6 on the S400, the drive was formatted when installing, but still get the error firmware.
 
Also tried to install on ASUS 756, there is another error, which does not complete the installation of the Sierra 10.13.B6 (photos)

 

Your ASUS 756 has a SkyLake processor and for that you'll need to use another config.plist with another type of SMBIOS with different settings. For SkyLake it's better to use MacBook Pro 13,1 or MacBook Pro 13,2.

and your S400 has an IvyBridge CPU and you can use MacBookPro9,2 or MacBook Air 5,2 (as you already used for macOS 10.12.x)

  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Ok now I rename config.plist and I boot to this one  by default 

 

see log please

 

EDIT here Darwin Dump

 

now. log is good without ff on your config.

0:591  0:000  Using ProductName from config
0:591  0:000  ProductName: MacBookPro9,1
0:591  0:000  Found same BiosVersion in clover and config
0:591  0:000  BiosVersion: MBP91.88Z.00D7.B00.1708080744
0:591  0:000  BiosReleaseDate: 08/08/2017
0:591  0:000  Using FirmwareFeatures from clover
0:591  0:000  FirmwareFeatures: 0xC00DE137
0:591  0:000  Using FirmwareFeaturesMask from clover
0:591  0:000  FirmwareFeaturesMask: 0xFF1FFF3F
0:591  0:000  Using PlatformFeature from clover
0:591  0:000  PlatformFeature: 0xFFFF
 
your previous log has set value. did you try to surely install HS DP6 with 0xC00DE137 FF value before when success install?
The log does not lie. To prevent confusion, I added the log. To receive accurate reports from users. Because you can confuse it when you report it in words.
 
can't download darwin dump
 
sorry for my bad english.
 
thanks
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

 

now. log is good without ff on your config.

0:591  0:000  Using ProductName from config
0:591  0:000  ProductName: MacBookPro9,1
0:591  0:000  Found same BiosVersion in clover and config
0:591  0:000  BiosVersion: MBP91.88Z.00D7.B00.1708080744
0:591  0:000  BiosReleaseDate: 08/08/2017
0:591  0:000  Using FirmwareFeatures from clover
0:591  0:000  FirmwareFeatures: 0xC00DE137
0:591  0:000  Using FirmwareFeaturesMask from clover
0:591  0:000  FirmwareFeaturesMask: 0xFF1FFF3F
0:591  0:000  Using PlatformFeature from clover
0:591  0:000  PlatformFeature: 0xFFFF
 
previous log has set value. did you try to surely install HS DP6 with 0xC00DE137 FF value before when success install?
The log does not lie. To prevent confusion, I added the log. To receive accurate reports from users. Because you can confuse it when you report it in words.
 
can't download darwin dump
 
sorry for my bad english.

 

You have a  the good log now

I am boot in the wrong config in the first time

 you have also DMI

 

Some times I have 6 config.plist in Clover

 

what do you want more!

 

 

I install HS with config.plist attaching

  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

You have a the good log now

I am boot in the wrong config in the first time

you have also DMI

 

Some times I have 6 config.plist in Clover

what you want more

 

I install HS with config.plist attaching

1st log that your wrong config boot

2nd log that correct config boot with same like installed clean HS DP6.

 

1st log confused me. Because shown wrong info compared config.plist

 

Anyways 2nd is good. As result, FFM FF are no problem. Installation issue also consider another something(your case, windows disk?)

 

Thanks you for great report. Have a great day.

 

Soon i will make better FFM FF code without confusion in future.

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

2nd log that correct config boot with same like installed clean HS DP6.

 

 

Anyways 2nd is good. As result, FFM FF are no problem. Installation issue also consider another something(your case, windows disk?)

 

Thanks you for great report. Have a great day.

 

Soon i will make better FFM FF code without confusion in future.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Thank you !

my install method is the one recommend by Apple

startosinstall, thats never failed for me in the previous Beta 3,4,5

and now I see BETA 6 dont like Windows SSD

Thank you for your effort

  • Like 1
Link to comment
Share on other sites
jaymack
jaymack
Posted
Posted

 

now. log is good without ff on your config.

0:591  0:000  Using ProductName from config
0:591  0:000  ProductName: MacBookPro9,1
0:591  0:000  Found same BiosVersion in clover and config
0:591  0:000  BiosVersion: MBP91.88Z.00D7.B00.1708080744
0:591  0:000  BiosReleaseDate: 08/08/2017
0:591  0:000  Using FirmwareFeatures from clover
0:591  0:000  FirmwareFeatures: 0xC00DE137
0:591  0:000  Using FirmwareFeaturesMask from clover
0:591  0:000  FirmwareFeaturesMask: 0xFF1FFF3F
0:591  0:000  Using PlatformFeature from clover
0:591  0:000  PlatformFeature: 0xFFFF
 
your previous log has set value. did you try to surely install HS DP6 with 0xC00DE137 FF value before when success install?
The log does not lie. To prevent confusion, I added the log. To receive accurate reports from users. Because you can confuse it when you report it in words.
 
can't download darwin dump
 
sorry for my bad english.
 
thanks

 

Here        DarwinDumper_v3.0.3.zip

Link to comment
Share on other sites
brumas
brumas
Posted
Posted

 

When trying to update X756UV public beta 4 (beta 2 installed) stops after a reboot and goes no further. is there a solution ? clover is 4178, log attached.

Your ASUS 756 has a SkyLake processor and for that you'll need to use another config.plist with another type of SMBIOS with different settings. For SkyLake it's better to use MacBook Pro 13,1 or MacBook Pro 13,2.

and your S400 has an IvyBridge CPU and you can use MacBookPro9,2 or MacBook Air 5,2 (as you already used for macOS 10.12.x)

Yes of course for 756 I have a very different configuration . and it at me normally works 2 beta. when you update the stopper and clean install the same stopper.

prebootX756UV.log.zip

post-1538813-0-88708600-1503164758_thumb.jpg

Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted

When trying to update X756UV public beta 4 (beta 2 installed) stops after a reboot and goes no further. is there a solution ? clover is 4178, log attached.

Yes of course for 756 I have a very different configuration . and it at me normally works 2 beta. when you update the stopper and clean install the same stopper.

To be honest laptops aren't really my speciality because I don't have laptop PC. 

For your X756UV use this config and let me know how it works.

config.plist X756UV.zip

  • Like 1
Link to comment
Share on other sites
pbryanw
pbryanw
Posted
Posted

A while back I made a post and I was facing somewhat a similar problem as you do now (There was a Firmware verification failure and after that there was an error regarding the OSInstall.mpkg error)

There are few reasons for why you get that error.

 

Thanks for your detailed post to me a few pages back. I use a separate Clover USB flash drive, specially configured for my High Sierra install, and had deleted EmuVariableUEFI.efi from it before starting installation of High Sierra. However, I still had EmuVariableUEFI.efi on my main macOS SSD (along with an NVRAM.plist file) - maybe this is why when I disabled this drive I was able to proceed with the High Sierra installation?

 

I took BIOS details & FF/FFM for my smbios from Sherlocks post on this, and didn't know Clover could do this for you, so thanks also for bringing this up and reminding me to download the latest Clover using the Build_Clover command (I'm using r4176 and don't know if a new version has been released since then).

 

Also, can I ask how APFS damaged your flash drive - I've heard of problems using it on magnetic hard drives - but if it also causes problems on flash drives, I'll reinstall with HFS+ if it means I won't corrupt my drive?

 

Edit: For brevity

Link to comment
Share on other sites
KGP-iMacPro
KGP-iMacPro
Posted
Posted

Dear, I also have this problem, config attached, what can I do to install the 6 beta? clover 4176.

Just look a few posts above man! You have to disconnect all drives except your USB flash drive and the target drive of the installation! This will solve the firmware verification problem!

 

Cheers, KGP

  • Like 2
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

Thank you !

my install method is the one recommend by Apple

startosinstall, thats never failed for me in the previous Beta 3,4,5

and now I see BETA 6 dont like Windows SSD

Thank you for your effort

startosinstall is only recommended if you are installing to an external drive, createinstallmedia is the recommended way for clean installs.

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

startosinstall is only recommended if you are installing to an external drive, createinstallmedia is the recommended way for clean installs.

No man  startosinstall is the same thing if you run the installer app on your SSD

good for install and good Upgrade 

 

Read here

Jamf site Create a Helper tool a few years ago for using startosinstal , but your not need this because the tools is inside installer.app  :D

you only need to used the Apple command line script

https://www.jamf.com/jamf-nation/discussions/22731/in-place-macos-sierra-upgrade-script

https://www.jamf.com/blog/streamlining-your-macos-upgrade-process/

Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

No man  startosinstall is the same thing if you run the installer app on your SSD

good for install and good Upgrade 

 

Read here

https://www.jamf.com/jamf-nation/discussions/22731/in-place-macos-sierra-upgrade-script

https://www.jamf.com/blog/streamlining-your-macos-upgrade-process/

startosinstall is intended for Enterprise deployment and is also used for NetInstalls, not intended to be used as a normal installer. Mainly used for custom install methods.

 

Read Here:

https://forums.developer.apple.com/message/143809#143809

  • Like 1
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted

 

 

startosinstall is intended for Enterprise deployment and is also used for NetInstalls, not intended to be used as a normal installer. Mainly used for custom install methods.

 

Read Here:

https://forums.developer.apple.com/message/143809#143809

I know mr  Rich Trouton  

It is not only used for companies that is a tool to integrate into the installer.app

Why do you believe business? quite simply that many companies use the jamf Soft

Because companies are deploying os x on several Macs 

now munki use the startosinstall because createosxinstallpkg is obsolète

Read here 

https://github.com/munki/createOSXinstallPkg

MR Greg Neagle said

 

 

Due to Apple changes, it's likely-to-virtually-certain that some functionality of createOSXinstallPkg is gone forever: nothing we do will bring back the ability to insert additional packages to be installed.

I think it's probably better longer-term for the community to focus on new tools and new workflows using the startosinstall binary inside the Install macOS.app. Munki 3 supports this workflow.

 

 

also here using startosinstall

So Create install Media and startosinstall do the same job, Installing Mac OS for anybody !

 

If you run install.app on your SSD you will have the same thing in the macOS Install Data folder as if you use startosinstall
It is the same exact things!
 
last edit by chri1111 19H pm
Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

@sherlocks and chris1111 - After spending a few more hours comparing config.plist entries and experimenting with different SMBIOS's, it appears that the problem I was having was due solely to my SSDT.  When I drop my SSDT.aml and use Clover's SSDT (enable PStates and CStates and enable C7) and also disable my Radeon GPU in my DSDT, I am able to load graphics just fine and install and run High Sierra DP 6. I have xcpm power management and 7 PStates.  Lid sleep/wake works as does battery icon.  The system hung on me once and required a hard boot but with that one exception, it has been running pretty stable and cool.  Most of the time, High Sierra was running at 55-65C.  Now, I have it running at 45-55C.  I'm sure it will run hotter as I install more apps and have more background processes.  Still, I'm happy to have solved my most difficult challenge in OSx86 since installing Leopard.

 

So I want to confirm, this was not an issue with either SMBIOS or ig-platform-id.

  • Like 3
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...