Jump to content

Mac os High sierra installation attempts


432 posts in this topic

Recommended Posts

Don't use afps.efi read older post i got same issue with beta 1 but it fix by removing apfs.efi from USB.

 

Sent from my XT1562 using Tapatalk

Deleted apfs.efi, rebooted, it's same, slow like a hell, experimenting with adding removing kexts, sofar no success, not getting what making it slow while with Sierra USB it boot smooth and show disks in a second.

 

Sent from my XT1060 using Tapatalk

Link to comment
Share on other sites

Deleted apfs.efi, rebooted, it's same, slow like a hell, experimenting with adding removing kexts, sofar no success, not getting what making it slow while with Sierra USB it boot smooth and show disks in a second.

 

Sent from my XT1060 using Tapatalk

That's strange see i am using clover r4097 without firmware feature, without apfs.efi (use hfs+ coz hdd) with smbios 8.2 which is not recommended as per updated bios versions but works great everything is works.

I recommend you to do like this for high Sierra

Do not change anything in plist use old plist which you use for Sierra.

Clean partition for hs with hfs and install high Sierra with beta.app. i got it by this method.

 

Sent from my XT1562 using Tapatalk

  • Like 1
Link to comment
Share on other sites

That's strange see i am using clover r4097 without firmware feature, without apfs.efi (use hfs+ coz hdd) with smbios 8.2 which is not recommended as per updated bios versions but works great everything is works.

I recommend you to do like this for high Sierra

Do not change anything in plist use old plist which you use for Sierra.

Clean partition for hs with hfs and install high Sierra with beta.app. i got it by this method.

 

Sent from my XT1562 using Tapatalk

I have two disks, HDD and SSD, unplugged HDD coz its just for data.

 

SSD has three partitions, Sierra, High Sierra DP1 on HFS+ (installed using Core.pkg from Sierra), now if I format third empty partition as APFS and install High Sierra DP2 using Core.pkg, it runs perfect with all hardware working.

 

But High Sierra DP2 USB installer cause this slow / unusable setup, now going to try your method :)

 

Sent from my XT1060 using Tapatalk

Link to comment
Share on other sites

My specs: 

 

- HP Z420, X79/C600 chipset, Intel Xeon E-1620 Sandy-Bridge-E, 8 Gb ECC 1600 MHz DDR3 ram, ATI Radeon HD5850, Gigabyte Ethernet, TP-Link Wi-Fi, External USB Sound Card (Realtek chipset), Samsung SSD 128 Gb & SSD 500 Gb, HDD 1 Tb, HDD 500 Gb. 

 

- Clover 4097, MacPro 6.1 SMBIOS

 

1. Downloaded HighSierra Beta 1 to MacOS Sierra partition -> Application folder

 

2. Installed the latest Clover on USB flash drive with Clover settings and kexts from Sierra

 

2. Created HighSierra HFS+ partition -> Run HighSierra DP1 from Sierra Application folder -> Chose HighSierra partition as target disk

 

3. When the first stage install finished I rebooted from USB flash drive with the latest Clover -> Chose HighSierra partition and finished installing

 

4. Downloaded HighSierra Beta 2 from App Store and upgraded

 

5. Downloaded Beta 2 Update 1 from App Store and upgraded

 

Everything works apart from USB3 ports (they never worked), and performance is excellent (it runs from SSD). Boot time 9 seconds.

 

I created another APFS partition, but not yet installed there.

 

post-605541-0-61208700-1498823173_thumb.jpg

 

post-605541-0-53343400-1498823372_thumb.jpg

  • Like 2
Link to comment
Share on other sites

 

Guys New seed for macOS High Sierra build 17A291m

 

 

 

How did you install the update? 

 

I have 10.13 beta 2 installed, I am running a fusion apfs drive. I allowed App Store to download and update the system with beta 2 update 1 on restart. When I look I see my system is still at beta 2 - not update 1. 

 

At clover boot screen I have four options, Boot from FileVault Preboot, MacOS Installer from HIgh Sierra, Boot MacOS from High Sierra, and Recovery From Recovery. 

 

1. Rebooting from Preboot works but system is still at Beta 2 without update

2. Booting from Installer results in message that OS can not be installed on this drive

3. Booting from MacOS on High Sierra results in booting but system is still at Beta 2 without update

 

Should I boot from Recovery? 

Should I boot from separate installations and run the update manually from there?

 

Help?!

Link to comment
Share on other sites

How did you install the update?

 

I have 10.13 beta 2 installed, I am running a fusion apfs drive. I allowed App Store to download and update the system with beta 2 update 1 on restart. When I look I see my system is still at beta 2 - not update 1.

 

At clover boot screen I have four options, Boot from FileVault Preboot, MacOS Installer from HIgh Sierra, Boot MacOS from High Sierra, and Recovery From Recovery.

 

1. Rebooting from Preboot works but system is still at Beta 2 without update

2. Booting from Installer results in message that OS can not be installed on this drive

3. Booting from MacOS on High Sierra results in booting but system is still at Beta 2 without update

 

Should I boot from Recovery?

Should I boot from separate installations and run the update manually from there?

 

Help?!

I used Piker Alpha script for updating macOS high Sierra. Look for older post or see this

 

https://github.com/Piker-Alpha/HandyScripts

 

Sent from my XT1562 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Thank you, that worked for me. I wonder why just using the automatic update through the App Store doesn't work for me.

'

Yes... I am glad that works for you... I was also not able to update via app store in my case i am able download the update but at time of installation my system restarted automatically this happens couples of times that's the reason I use this script

 

Sent from my XT1562 using Tapatalk

I have two disks, HDD and SSD, unplugged HDD coz its just for data.

 

SSD has three partitions, Sierra, High Sierra DP1 on HFS+ (installed using Core.pkg from Sierra), now if I format third empty partition as APFS and install High Sierra DP2 using Core.pkg, it runs perfect with all hardware working.

 

But High Sierra DP2 USB installer cause this slow / unusable setup, now going to try your method :)

 

Sent from my XT1060 using Tapatalk

That's strange in my case i have ssd and hdd. High Sierra and Sierra and win 10 in ssd and data in hdd but I tried high Sierra with the method i told you but it was working charm without any trouble but if I install in hdd then issue one more thing I am also unable to boot from USB don't know why but I install by method . But slice update the clover 4099 i gonna try and ping you

 

Sent from my XT1562 using Tapatalk

Link to comment
Share on other sites

That's strange in my case i have ssd and hdd. High Sierra and Sierra and win 10 in ssd and data in hdd but I tried high Sierra with the method i told you but it was working charm without any trouble but if I install in hdd then issue one more thing I am also unable to boot from USB don't know why but I install by method . But slice update the clover 4099 i gonna try and ping you

Sent from my XT1562 using Tapatalk

Old createmedia + Clover + kexts method isn't working (dp1 or 2) for me, now going to try it with public beta.

 

On last try I waited quite longer, finally installation window showed up, it took only 2 minutes to copy or install High Sierra to selected disk but after first reboot it freeze on blue screen (the one with tiny language selection flag at top right).

 

Sent from my XT1060 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Yeah, please share the EFI folder. I use ssd (850 evo) as well.

ok, here is it, this is the clover that is working for me on haswell and skylake hackintosh using uefi boot, i just used the default bios options with disabled vt-d and secure boot on other os, speedstep disabled and intel virtualization technology enabled, tested on asus motherboards only, but should work on other brands too

EFI.zip

  • Like 1
Link to comment
Share on other sites

I wonder why just using the automatic update through the App Store doesn't work for me.

 

It is only the update download, but after reboot the installation of the update is aborted by the reboot.
At the next reboot, the rest time is displayed for 13 minutes, it is installed only 5 minutes but not updated.
 
I can only download the Dev. Updates from the Appstore and with PikerAplha HandyScript then install the updates successfully.
Why is not it like vei Sierr 10.12.x?
 
If I try to install the old method with "createmediainstaller" and USB stick,
after copying the files and rebooting (also Clover 4097 is
installed on the USB stick with and FakeSMC etc. in Clover Kext Folder "other") the message
" High Sierra can not be installed "
 
and he Note:
 
/System/Installation/Packages/OSInstall.mpkg to to missing
 
Then I inserted into my SMBIOS area:
 
<Key>Firmware Features</ key>
<String>0xe907f537</string>      or with this Number: 0xe807e136
 
Because I've read it could be because of it.
But after a fresh reinstallation from the USB stick it was the same.
 
Why does not this work with "createmediainstaller"?
 
I would be glad about tips from experts here ... thank you
Link to comment
Share on other sites

I used Piker Alpha script for updating macOS high Sierra. Look for older post or see this

 

https://github.com/Piker-Alpha/HandyScripts

 

Sent from my XT1562 using Tapatalk

I couldn't figure out how that script works!

Like, how do I run it and does it need any changes so it knows what things to put where...

Could you give me a tiny bit of help please :)

edit: a search helped. It's downloading the package now. FYI I typed SH (+space) in terminal and dragged the script into the window. then enter of course.

 

Regarding the apfs, in AJA in hfs formatted my 960 evo reads 2850 about, and in apfs the read is over 3200, so it's working great after the boot. The write is about 500mbs faster. I think boot is slower because there is logging and debugging done on account of the newness of HS. Possibly.

Link to comment
Share on other sites

I couldn't figure out how that script works!

Like, how do I run it and does it need any changes so it knows what things to put where...

Could you give me a tiny bit of help please :)

 

Regarding the apfs, in AJA in hfs formatted my 960 evo reads 2850 about, and in apfs the read is over 3200, so it's working great after the boot. The write is about 500mbs faster. I think boot is slower because there is logging and debugging done on account of the newness of HS. Possibly.

Read this

http://www.hackintoshmumbai.com/upgrade-macos-high-sierra-easily/

 

Sent from my XT1562 using Tapatalk

  • Like 1
Link to comment
Share on other sites

High Sierra Public Beta showing 'Waiting' for last 10 minutes, while connection is stable and fast. What should I do? Please advise.

10 min to download ? If yes then I got the same i download via torrent afterwards.

 

Sent from my XT1562 using Tapatalk

Link to comment
Share on other sites

guys if you still having trouble doing the update, just remember that, it creates an installer on the boot volume, so you have to boot that from clover if you want to update

Link to comment
Share on other sites

guys if you still having trouble doing the update, just remember that, it creates an installer on the boot volume, so you have to boot that from clover if you want to update

How to do that ?

MacOS High Sierra Public Beta with APFS. By changing SMBIOS from 8.2 to 10.1 my High Sierra Boot Fast on HDD :D

post-957871-0-62332400-1499002079_thumb.png

Link to comment
Share on other sites

to do that you have just to install the update using the app store, at the reboot in clover you will find another boot option that is "boot mac os install from [your high sierra partition/drive]" and you have to boot that to do the update, otherwise it will not be installed

  • Like 1
Link to comment
Share on other sites

Here it installs successfully updating from Sierra

 

Only issues was USB was not working at first (needed USBInjectAll) macOS partition not showing up in Clover (needed apfs.efi) and lack of Nvidia web driver

 

 


to do that you have just to install the update using the app store, at the reboot in clover you will find another boot option that is "boot mac os install from [your high sierra partition/drive]" and you have to boot that to do the update, otherwise it will not be installed

Note that if you have hidden volumes in Clover in some cases you will have to unhide them or Clover won't show the installer, happened to me.

  • Like 1
Link to comment
Share on other sites

For your platformdata update @Sherlocks:

 

 

 

EFIPayloads:

- IM101.88Z.00CD.B01.1706261549
- IM111.88Z.0035.B01.1706261406
- IM112.88Z.0058.B01.1706261628
- IM121.88Z.004A.B01.1706261231
- IM131.88Z.010C.B01.1706261419
- IM141.88Z.0119.B01.1706261354
- IM142.88Z.0119.B01.1706261827
- IM143.88Z.0119.B01.1706261217
- IM144.88Z.0180.B01.1706261218
- IM151.88Z.0208.B01.1706261354
- MB61.88Z.00C9.B01.1706261518
- MB71.88Z.003A.B01.1706261443
- MBA31.88Z.0064.B01.1706261714
- MBA41.88Z.0078.B01.1706261217
- MBA51.88Z.00F1.B01.1706261433
- MBA61.88Z.0100.B01.1706261827
- MBP101.88Z.00EF.B01.1706261418
- MBP102.88Z.0107.B01.1706261827
- MBP111.88Z.0139.B01.1706261010
- MBP112.88Z.0139.B01.1706261355
- MBP61.88Z.0058.B01.1706261104
- MBP71.88Z.003A.B01.1706261020
- MBP81.88Z.0049.B01.1706261922
- MBP91.88Z.00D4.B01.1706261216
- MM41.88Z.0043.B01.1706261836
- MM51.88Z.0078.B01.1706261437
- MM61.88Z.0107.B01.1706261217
- MM71.88Z.0221.B02.1706261516
- MP61.88Z.0117.B01.1706261354
- IM161.88Z.0209.B02.1706261516
- IM162.88Z.0209.B02.1706261516
- IM171.88Z.0106.B01.1706260138
- IM181.88Z.0147.B01.1706251744
- IM183.88Z.0147.B01.1706251744
- MB101.88Z.0150.B01.1706260154
- MB81.88Z.0165.B01.1706261516
- MB91.88Z.0155.B01.1706260138
- MBA71.88Z.0167.B01.1706261032
- MBP114.88Z.0173.B01.1706261516
- MBP121.88Z.0168.B01.1706261516
- MBP131.88Z.0206.B01.1706260154
- MBP132.88Z.0227.B01.1706260154
- MBP133.88Z.0227.B01.1706260154
- MBP141.88Z.0161.B01.1706251744
- MBP142.88Z.0161.B01.1706251744
- MBP143.88Z.0161.B01.1706252330


SMCJSONs:

- Mac-031B6874CF7F642A: 2.14f24
- Mac-189A3D4F975D5FFC: 2.16f68
- Mac-27ADBB7B4CEE8E61: 2.15f7
- Mac-2BD1B31983FE1663: 2.19f12
- Mac-35C1E88140C3E6CF: 2.12f143
- Mac-35C5E08120C7EEAF: 2.24f32
- Mac-3CBD00234E554E41: 2.18f15
- Mac-42FD25EABCABB274: 2.22f16
- Mac-473D31EABEB93F9B: 2.36f97
- Mac-65CE76090165799A: 2.33f10
- Mac-66E35819EE2D0D05: 2.37f20
- Mac-77EB7D7DAF985301: 2.17f7
- Mac-7DF21CB3ED6977E5: 2.13f15
- Mac-81E3E92DD6088272: 2.21f92
- Mac-937CB26E2E02BB01: 2.27f2
- Mac-9AE82516C7C6B903: 2.35f105
- Mac-9F18E312C5C2BF0B: 2.26f2
- Mac-A369DDC4E67F1C45: 2.31f36
- Mac-A5C67F76ED83108C: 2.38f7
- Mac-B809C3757DA9BB8D: 2.34f2
- Mac-BE0E8AC46FE800CC: 2.25f87
- Mac-DB15BD556843C820: 2.33f10
- Mac-E43C1C25D4880AD6: 2.28f7
- Mac-F60DEB81FF30ACF6: 2.20f18
- Mac-FA842E06C61E91C5: 2.23f11
- Mac-FFE5EF870D7BA81A: 2.32f20


FirmwareFeatures(Mask):

- IM131.88Z.010C.B01.1706261419: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
- IM141.88Z.0119.B01.1706261354: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
- IM142.88Z.0119.B01.1706261827: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
- IM143.88Z.0119.B01.1706261217: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
- IM144.88Z.0180.B01.1706261218: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf007e137
- IM151.88Z.0208.B01.1706261354: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf807e137
- MBA41.88Z.0078.B01.1706261217: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xd005e137
- MBA51.88Z.00F1.B01.1706261433: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
- MBA61.88Z.0100.B01.1706261827: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
- MBP101.88Z.00EF.B01.1706261418: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
- MBP102.88Z.0107.B01.1706261827: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
- MBP111.88Z.0139.B01.1706261010: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe807e137
- MBP112.88Z.0139.B01.1706261355: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe807e137
- MBP91.88Z.00D4.B01.1706261216: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xc005e137
- MM51.88Z.0078.B01.1706261437: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xd005e137
- MM61.88Z.0107.B01.1706261217: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
- MP61.88Z.0117.B01.1706261354: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe807e136
- IM171.88Z.0106.B01.1706260138: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
- IM181.88Z.0147.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
- IM183.88Z.0147.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
- MB101.88Z.0150.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e
- MB91.88Z.0155.B01.1706260138: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e
- MBP131.88Z.0206.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
- MBP132.88Z.0227.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
- MBP133.88Z.0227.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e
- MBP141.88Z.0161.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
- MBP142.88Z.0161.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
- MBP143.88Z.0161.B01.1706252330: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e

 

 

 

 

New SMBIOS for my iMac 10,1 is now: IM101.88Z.00CD.B01.1706261549

 

what I have set FirmwareFeatures(Mask), FirmwareFeatures, PlatformFeature (there is not info)?

 

I use 10.13 DP2 version 17A291 and not show update in Mac App Store about "DP2 Update 1", please help  

 

clover 4102 

Bios date set: 06/26/17

------------------------------

 

:happymac:  Solved error installed script download DP2 update 1 from https://github.com/Piker-Alpha/HandyScripts/blob/master/install_1013_DP2_17A291m.sh

:thanks_speechbubble: Pike-Alpha https://github.com/Piker-Alpha/HandyScripts

Edited by hackintosh1984
Link to comment
Share on other sites

guys if you still having trouble doing the update, just remember that, it creates an installer on the boot volume, so you have to boot that from clover if you want to update

 

Nice info  :) I think it's better using "Auto Scan" on Clover GUI for testing purpose; especially using APFS under 10.13 Beta. I figured out that also got difficulties to set Custom Entry for "Recovery HD" since it becomes APFS Volume inside the Container (\VenMedia), on HFS+ is much easier with the UUID info I guess.

Link to comment
Share on other sites

Run Install macOS High Sierra Beta from Sierra, choose convert to APFS, added apfs.efi to Clover, on reboot it freeze just before language selection screen, if I use -v then it show white screen with black Apple logo, otherwise it's white logo on black, otherwise no difference.

 

d2149193dfc27b4f789ecec675b8eda8.jpg

Link to comment
Share on other sites

 Share

×
×
  • Create New...