Jump to content
Allan

macOS High Sierra - Final Release is out! (17A365)

448 posts in this topic

Recommended Posts

Well, I realize that I'm not be able to pass this by myself:

 

attachicon.gifIMG_20170927_185919641.jpg

 

I tried:

• Clover r4220;

• put firmwarefeatures on currently smbios (imac12,1 or 14,2);

• boot with HD3000 (instead gt610);

• CLOVERX64-High.efi inside drivers64UEFI (clover freezes before gui)

• create install media manual and automatized;

 

I noticed that others also have this problem:

http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2436372

http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2436993

http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2437148

http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2437172

 

But, appears that in my case the message is a little different.

 

I've system worked fine until 10.12.6, but nothing on 10.13.

 

What is missing? :cry:

You can try the EFI attaching

EFI.zip

Share this post


Link to post
Share on other sites
Advertisement

Interesting method  :)  But migrate (Time machine or else) seems to be impossible? Right or not?

 

@Matgen84,

 

Running startosinstall is basically the same as directly running "Install macOS High Sierra.app" but with the option to choose APFS or not.  The same data structure "macOS Install Data" is written to the target drive...

 

post-846696-0-33915700-1506558332_thumb.png

 

 

so an upgrade install of an existing HFS+ installation on SSD is possible, without conversion to APFS eg

fusion71aus-iMac:~ fusion71au$ /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/macSSD --converttoapfs NO --applicationpath /Applications/Install\ macOS\ High\ Sierra.app

where "macSSD" is the target for upgrade, and "Install macOS High Sierra.app" is in the /Applications folder.

 

 

Fusion, just to confirm, with or without the "--converttoapfs NO" parameter, if you're on a HFS+ formatted HDD, it won't get converted to APFS anyway, simply because it's an HDD, right?

 

Yes, the default behavior for HDD upgrade, if parameter not specified, is to keep existing HFS+ (same as for directly running the app - see post#60).

Share this post


Link to post
Share on other sites

@Matgen84,

 

Running startosinstall is basically the same as directly running "Install macOS High Sierra.app" but with the option to choose APFS or not.  The same data structure "macOS Install Data" is written to the target drive...

 

 

 

so an upgrade install of an existing HFS+ installation on SSD is possible, without conversion to APFS eg

fusion71aus-iMac:~ fusion71au$ /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/macSSD --converttoapfs NO --applicationpath /Applications/Install\ macOS\ High\ Sierra.app

where "macSSD" is the target for upgrade, and "Install macOS High Sierra.app" is in the /Applications folder.

 

 

Fusion, just to confirm, with or without the "--converttoapfs NO" parameter, if you're on a HFS+ formatted HDD, it won't get converted to APFS anyway, simply because it's an HDD, right?

Share this post


Link to post
Share on other sites

Fusion, just to confirm, with or without the "--converttoapfs NO" parameter, if you're on a HFS+ formatted HDD, it won't get converted to APFS anyway, simply because it's an HDD, right?

Yes that's correct only SSDs and PCIe Flash Storages will be converted to APFS automatically, although last night I replaced a MacBook Pro's HDD with SSD (non-Apple SSD) and installed the High Sierra but I had to format the SSD to APFS manually. No automatic conversion  :blink:

Share this post


Link to post
Share on other sites

Hi, I have two questions. Is Enable trim required for SSD? Is RC Scripts Necessary? I have UEFI boot. Thank you

Having trim enable will increase the performance and longevity of you SSD over time. It's better to have it enabled if possible. RC Scripts are not necessary unless you need them (In case of having trouble activating the nVidia Web Driver) you can easily use EmuVaraiableUEFI.efi and if that failed to make the web driver active you might need to use RS Scripts. Of course there are other use for RC Scripts which you can find out in clover discussion thread.

Share this post


Link to post
Share on other sites

Does the restore BaseSystem method still work with 10.13? Seen a lot of posts using that method with the missing or corrupt OSInstall.mpkg error. 

No it doesn't work anymore, only createinstallmedia or startosinstall method works.

 

as @camillionario stated on some systems having the EmuVaraiableUEFI.efi can also cause the OSInstall.mpkg error.

Share this post


Link to post
Share on other sites

Hello and thanks for all..

 

Installing hs went smooth in my hack .. dell skl hd 520 as on my signature . but i am having the power after sleep doesn't work. when closing the lid or click sleep .. only black screen shown .. i can hear the ding sound when clicking spacebar  which means the system is working but the display is not working after sleep .. i posted this problem since hs pb 8 ,

Waiting any reply .. with regards.

Share this post


Link to post
Share on other sites

No it doesn't work anymore, only createinstallmedia or startosinstall method works.

 

as @camillionario stated on some systems having the EmuVaraiableUEFI.efi can also cause the OSInstall.mpkg error.

 

Ahh that's an issue for AMD. Can startosinstall be used to install to another partition/drive?

Share this post


Link to post
Share on other sites

Ahh that's an issue for AMD. Can startosinstall be used to install to another partition/drive?

Yes !

Also used for Install any Mac Packages

with a respects permissions and authorizations
Exemple here of Install Package
 

--installpackage /Users/Shared/MyPackages.pkg --nointeraction

 

Share this post


Link to post
Share on other sites

 

Yes !

Also used for Install any Mac Packages

with a respects permissions and authorizations
Exemple here of Install Package
 

--installpackage /Users/Shared/MyPackages.pkg --nointeraction

 

 

 

So if I were to install the Core.pkg how would I point that to another volume? I tried running the OSInstall from Sierra but I don't think it worked correctly as I've noticed some 10.12 files were used.

Share this post


Link to post
Share on other sites

Hey @chris1111, what's your method to create a USB install media for High Sierra?

 

Your tools are great!  ^_^

 

Thanks

 

See Private message  :)

So if I were to install the Core.pkg how would I point that to another volume? I tried running the OSInstall from Sierra but I don't think it worked correctly as I've noticed some 10.12 files were used.

I don't think core.pkg working in the Release ?

Share this post


Link to post
Share on other sites

So if I were to install the Core.pkg how would I point that to another volume? I tried running the OSInstall from Sierra but I don't think it worked correctly as I've noticed some 10.12 files were used.

I made a new macOS High Sierra HD for the release 10.13

APFS or HFS+

 but video is not complete  :P

Share this post


Link to post
Share on other sites

I made a new macOS High Sierra HD for the release 10.13

APFS or HFS+

 but video is not complete  :P

 

That'll help out :P My current issue is getting stuck on IOConsole something before the login window. I'm sure it just didn't install correctly.

Share this post


Link to post
Share on other sites

Ahh that's an issue for AMD. Can startosinstall be used to install to another partition/drive?

I personally use the createistallemedia it works pretty much the same as the older BaseSystem method:

 

just use this command:

sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled  —nointeraction

I haven't tested the startinstall method yet

Share this post


Link to post
Share on other sites

That'll help out :P My current issue is getting stuck on IOConsole something before the login window. I'm sure it just didn't install correctly.

I  send you the link and the video tomorrow, you and spakk  B)

Share this post


Link to post
Share on other sites

I personally use the createistallemedia it works pretty much the same as the older BaseSystem method:

 

just use this command:

sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled  —nointeraction

I haven't tested the startinstall method yet

 

 

createinstallmedia doesn't work on AMD systems :(

 

I  send you the link and the video tomorrow, you and spakk  B)

 

Thanks mate. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
    • By t0mmenhansen
      I havent used my hackintosh in a while. I wanted to boot to my mac drive. This error comes up when i try to boot. Ive tryed using explorer++ and update the lilu kext and whatevergreen kext, no luck yet. Any ideas?
       
      9700k
      16GB corsair
      1080 nvidia card
      z370-f mobo
      mac drive is an SSD from kingston
      Display port outpoot
       
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

    • By fusion71au
      Clover r4961 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4961 for VMware.zip". Mount Clover-v2.4k-4961-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×