[pre-release] macOS High Sierra

[Cyberdevs]

@Sherlocks

 

Gooood news:

 

I changed the BIOS Released Date from 06/25/2017 to 06/25/17 as @Matgen84 suggested

When you get report, follow this
1. FF: 0xfc07e136

2. FFM: 0xff1fff3f

3. BIOS ROM: IM181.88Z.0147.B01.1706251744

 

and it's working

 

I'm going to use the iMac 17,1 next and see if it can be installed with the clover's default FF and FFM

[xtddd]

 

@Sherlocks

 

Gooood news:

 

I changed the BIOS Released Date from 06/25/2017 to 06/25/17 as @Matgen84 suggested

When you get report, follow this

1. FF: 0xfc07e136

2. FFM: 0xff1fff3f

3. BIOS ROM: IM181.88Z.0147.B01.1706251744

 

and it's working

 

I'm going to use the iMac 17,1 next and see if it can be installed with the clover's default FF and FFM

 

the true date mode is 06/25/17...you have done a great work

[Sherlocks]

@Sherlocks

 

 

Gooood news:

 

I changed the BIOS Released Date from 06/25/2017 to 06/25/17 as @Matgen84 suggested

When you get report, follow this

1. FF: 0xfc07e136

2. FFM: 0xff1fff3f

3. BIOS ROM: IM181.88Z.0147.B01.1706251744

 

and it's working

 

I'm going to use the iMac 17,1 next and see if it can be installed with the clover's default FF and FFM

the true date mode is 06/25/17

As result, date format should be MM/DD/YY?

 

Recent mac model has MM/DD/YYYY format.

 

In clover platformdata has ex. Imac17,1 06/26/2017

 

Now, in beta2, change from 06/26/2017 to 06/26/17 right?

 

Its important.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

[Cyberdevs]

the true date mode is 06/25/17...you have done a great work

This is the first Bios Version: iMac17,1 IM171.88Z.0105.B25.1704292104 and BIOS release date is: 04/29/17

and

The new BIOS Version is: IM171.88Z.0106.B01.1706260138 BIOS release date is: 06/26/17

As result, date format should be MM/DD/YY?

 

Recent mac model has MM/DD/YYYY format.

 

In clover platformdata has ex. Imac17,1 06/26/2017

 

Now, in beta2, change from 06/26/2017 to 06/26/17 right?

 

Its important.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

That's right.

I'm going to double check just to make sure.

I'll get back to you as soon as I test it.

[Sherlocks]

This is the first Bios Version: iMac17,1 IM171.88Z.0105.B25.1704292104 and BIOS release date is: 04/29/17

and

The new BIOS Version is: IM171.88Z.0106.B01.1706260138 BIOS release date is: 06/26/17

 

That's right.

I'm going to double check just to make sure.

I'll get back to you as soon as I test it.

Great you are forerunner.

To clear

 

1. FF

2. FFM

3. BIOS ROM

4. BIOS DATE FORMAT

 

Also i wonder cecekpawon's data actually causes to fail pass osinstall.pkg error.

 

Between Clover's FF, FFM and his FF,FFM

 

 

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

[xtddd]

Update to beta 2 update 1 and re-patched Nvidia driver with Nvidia updater fix app

 

All went fine

 

By the way thanks to PMHeart for dummy kext policy fix :-)

 

PS for gfx Apple software render in Cinebench

how you enable gtx1080ti....i still wait for webdriver fo high sierra

[Cyberdevs]

Thanks @Sherlocks 
Well with this settings I can also install macOS High Sierra DP2 Beta 1:

1. FF: 0xE907F537
2. FFM: 0xFFFFFFFF
3. BIOS ROM: IM171.88Z.0106.B01.1706260138
4. BIOS DATE FORMAT: 06/26/2017

But the thing is with this settings installation process reboots the system twice once after the first stage and once after firmware checkup, but with the previous and cecekpawon's FF,FFM settings the installation began immediately after the first reboot, there was no firmware check/reboot

I removed all the hard disks from the system and tested with a single HDD so I wonder maybe there was a problem with having multiple hdds with different OSes!

[xtddd]

great

[Sherlocks]

Thanks @Sherlocks 

Well with this settings I can also install macOS High Sierra DP2 Beta 1:

 

1. FF: 0xE907F537

2. FFM: 0xFFFFFFFF

3. BIOS ROM: IM171.88Z.0106.B01.1706260138

4. BIOS DATE FORMAT: 06/26/2017

But the thing is with this settings installation process reboots the system twice once after the first stage and once after firmware checkup, but with the previous and cecekpawon's FF,FFM settings the installation began immediately after the first reboot, there was no firmware check/reboot

 

I removed all the hard disks from the system and tested with a single HDD so I wonder maybe there was a problem with having multiple hdds with different OSes!

 

1. FF: 0xE907F537

2. FFM: 0xFFFFFFFF

3. BIOS ROM: IM171.88Z.0106.B01.1706260138

4. BIOS DATE FORMAT: 06/26/2017

 

-> can install. right?

 

what is "but with the previous and cecekpawon's FF,FFM settings the installation began immediately after the first reboot"

 

how about this?

1. FF: 0xFC07E136

2. FFM: 0xFF1FFF3F

3. BIOS ROM: IM171.88Z.0106.B01.1706260138

4. BIOS DATE FORMAT: 06/26/2017

 

this is cecekpawon data. 

 

also BIOS DATE FORMAT not relate? between MM/DD/YYYY and MM/DD/YY. 

 

case 1

1. FF: 0xE907F537(clover default)

2. FFM: 0xFFFFFFFF(clover default)

3. BIOS ROM: IM171.88Z.0106.B01.1706260138

4. BIOS DATE FORMAT: 06/26/2017

 

case 2

1. FF: 0xE907F537(clover default)

2. FFM: 0xFFFFFFFF(clover default)

3. BIOS ROM: IM171.88Z.0106.B01.1706260138

4. BIOS DATE FORMAT: 06/26/17

 

case 3

1. FF: 0xFC07E136(cecekpawon)

2. FFM: 0xFF1FFF3F(cecekpawon)

3. BIOS ROM: IM171.88Z.0106.B01.1706260138

4. BIOS DATE FORMAT: 06/26/2017

 

case 4

1. FF: 0xFC07E136(cecekpawon)

2. FFM: 0xFF1FFF3F(cecekpawon)

3. BIOS ROM: IM171.88Z.0106.B01.1706260138

4. BIOS DATE FORMAT: 06/26/17

[soto2080]

It seems that the new AppleGFXHDAController.kext was built to work with external PCIe cards. The IOPCITunnelCompatible entry is already there, it works without the HDA kexts and probably also for external PCIe sound cards. Bad news for the nVidia users there are only Intel and AMD entries.

AppleGFXHDA.png

But My GTX770 works fine with it.

[Cyberdevs]

The installation of the macOS High Sierra with these settings will reboot the system twice, once after copying the macOSInstall Data from USB disk to the HDD and once after the first reboot right after a few seconds (this is the part fro firmware check/update on Apple computers and on hackintoshes it will be bypassed ), and after that the last/3rd stage of the installation will start until the whole process is complete after about 15 minutes.

 

So

1. Booting macOS High Sierra installer

2. Copying the Installation files from USB to HDD then system reboots

3. Checking/updating the firmware then system reboots

4. Completing the installation process and the system reboots fro the last time and after that the macOS will start.

1. FF: 0xE907F537
2. FFM: 0xFFFFFFFF
3. BIOS ROM: IM171.88Z.0106.B01.1706260138 iMac 17,1 SMBIOS
4. BIOS DATE FORMAT: 06/26/2017

And

 

With these settings the whole process is only reboots the system once, Once after copying the macOSInstall Data from USB disk to the HDD and after that the installation will start until the whole process is complete after about 15 minutes. There will be no more reboots after firmware check/update.

1. FF: 0xE907F537
2. FFM: 0xFF1FFF3F
3. BIOS ROM: IM181.88Z.0147.B01.1706251744 - iMac 18,1 SMBIOS
4. BIOS DATE FORMAT: 06/25/2017

So

1. Booting macOS High Sierra installer

2. Copying the Installation files from USB to HDD then system reboots

3. Completing the installation process and the system reboots fro the last time and after that the macOS will start.

 

And the BIOS Release Date is not relevant anymore. It will start the installation with MM/DD/YYYY and MM/DD/YY format.

 

As I mentioned before I removed all the Hard Disks except for the one I'm trying to install macOS High Sierra and that's what makes me think that the OSInstall.mpkg error might have happen because of something rather that the clover's FF and FFM settings.

Update: Final Conclusion: @Sherlocks

 

So, I assume the iMac 18,1 SMBIOS doesn't require the firmware check/update in this scenario.

 

These settings also work perfectly:

1. FF: 0xfc07e136
2. FFM: 0xFFFFFFFF
3. BIOS ROM: IM181.88Z.0147.B01.1706251744 - iMac 18,1 SMBIOS
4. BIOS DATE FORMAT: 06/25/2017

In the next test I will use the SMBIOS of iMac18,1 alone with the clover's default FF and FFM settings just to see if the SMBIOS settings are the reason that the firmware check/update is getting bypassed rather that the FF and FFM that @cecekpawon's provided.

 

My assumption is the SMBIOS for now. Until proved otherwise.

[SavageAUS]

I can also concur with the multiple disks / operating systems. On my desktop with dp1 if I tried to install with other ssd's enabled I would get the OSInstall.mpkg error but if I disabled all other ssd's it would install fine.

As for my laptop it has macOS / Windows 10 / Manjaro on it. If I tried to install dp1 on another partition I would get OSInstall.mpkg error but installing it first installed fine. This is with USB install.

Install via the downloaded .app worked on both machines.

Both installations used the previous updated bios information not the new ones as of dp2 update 1.

 

Sent from my SM-G930F using Tapatalk

[Cyberdevs]

I can also concur with the multiple disks / operating systems. On my desktop with dp1 if I tried to install with other ssd's enabled I would get the OSInstall.mpkg error but if I disabled all other ssd's it would install fine.

As for my laptop it has macOS / Windows 10 / Manjaro on it. If I tried to install dp1 on another partition I would get OSInstall.mpkg error but installing it first installed fine. This is with USB install.

Install via the downloaded .app worked on both machines.

Both installations used the previous updated bios information not the new ones as of dp2 update 1.

 

Sent from my SM-G930F using Tapatalk

It's wired that it happens because with the DP1 and DP2 I didn't have this problem. It happened right after I tried to update to beta 1 from App Store.

[SavageAUS]

It's wired that it happens because with the DP1 and DP2 I didn't have this problem. It happened right after I tried to update to beta 1 from App Store.

Apple's way of reducing the hackintosh community?

 

Sent from my SM-G930F using Tapatalk

[xtddd]

Apple's way of reducing the hackintosh community?

 

Sent from my SM-G930F using Tapatalk

maybe it is not 

[Cyberdevs]

Apple's way of reducing the hackintosh community?

 

Sent from my SM-G930F using Tapatalk

Hahahah  

 

Even if it is they are not so good at it though it's only a matter of hours that we can install it on any given pc 

[xtddd]

@cyberdevs my friend only used the new biosversion and didnt change bios date....he updated smoothly from dp1 tp dp2 via app store

[Cyberdevs]

@cyberdevs my friend only used the new biosversion and didnt change bios date....he updated smoothly from dp1 tp dp2 via app store

Oh, Thanks fro sharing that, it's really good to know.

I was testing the new update late at night and I forgot to change the SMBIOS info before restarting the system maybe that's why it messed up the installation process.

SMBIOS info is correct

[xtddd]

@cyberdevs great...now biosversion should be updated before update new beta

[Cyberdevs]

I believe so, I need to install the DP 2 with the new config.plist and then try to see if the update from the App Store is working or not.

 

I saw some guys updated directly from App Store so I assume that it will work.

[Cyberdevs]

I have Always updated from App Store and without adding firmwared related part

 in High Sierra I have only to use a new cpu kernel patch because my cpu is an unsupported one

I am using also clover 4081 (Sherlock release I think) 

with Greater version I have problem (Ie 4097)

 

What kind of problems you've had with newer clover versions? I had some weird problem with clover 4080 to 4084 but now I'm using 4100 with no problems.

[Cyberdevs]

system hangs with stop sign (++++++++++++++++stage)

I see, but that wasn't the case for me,

 

I had a different problem, When I was trying to install macOS High Sierra (didn't test the other versions of macOS) after the first reboot system would freeze and I had to reset the BIOS with the jumpers on the mainboard. I never had this problem with 4079.

 

AND the SAD thing is that I'm using the 4100 right now and the system is froze up again!!!

 

Darn it! I don't know what am I doing wrong using the Build_Clover Command

[macq]

Developer Beta 2 Update 1: BCM94352 patches without changes!

Bildschirmfoto 2017-06-29 um 23.23.11.png

@neo darkeman, sherlocks

 On updating to Beta 2 Update 1, I get the pcie kernel panic with the usual patches.The patches are working well till dp2.

If I remove all wifi bcm 4352 patches then I am able to boot but the update then fails.

please help.

 

My config list attached.

config.plist.zip

[alfaSZ]

system hangs with stop sign (++++++++++++++++stage)

I can second that. With Clover 4084 and Broadwell-E the set_cpuid patch fails to apply when installing the system (presumably because clover doesn't see the temporary kernel in the MacOS Installation Files directory?..). Without the patch the kernel gets stuck at the initial stages with the ++++

I had to manually uncompress the prelinkedkernel file (using pike's lzvn utility, patch with a hex editor and recompress) before I could book into the 10.13 beta2 kernel and start the installation process.. Once installed, Clover is fine to apply the patch once the kernel is in the regular location..

Looks like I should be checking out newer versions of Clover, eg 4100.

[Neo.aka.Darkman]

 On updating to Beta 2 Update 1, I get the pcie kernel panic with the usual patches.

 

@macq, in Developer Beta 2 there was change in patches for com.apple.driver.AirPort.BrcmNIC, but not for com.apple.driver.AirPort.BrcmNIC-MFG

 

So, once again for com.apple.driver.AirPort.BrcmNIC is now 1 patch instead of 3 patches:

 

Find:

75166644 3BA3501A 0000750C 4183FE04 7406

Replace:

66906644 3BA3501A 00006690 4183FE04 6690

 

I've updated your config file for latest patches.

 

P.S. I'm not sure what does your last patch for Wi-Fi. It is also with wrong length of Find and Replace strings.

config.plist-2.zip