Jump to content
fantomas1

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

@mnfesq  I have a HP Probook laptop and I used startosinstall

This is Apple's new way to deploy MacOS or Upgrade

I never have issue on that way in my Probook

 

Its the new tool inside the Install macOS High Sierra Beta.app

name is startosinstall

Your just need a Blank SSD formate in HFS+J (Mac OS Extended journaled / Guid table) before starting the tools

Make sure you have Install macOS High Sierra Beta.app in your Applications 

Working with BETA4, BETA 5, PBETA3, PBETA4

Working for Internal or External Drive

 

Command for APFS

"/Applications/Install macOS High Sierra Beta.app/Contents/Resources/startosinstall" --applicationpath "/Applications/Install macOS High Sierra Beta.app" --converttoapfs YES --volume /Volumes/USB --rebootdelay 30 --nointeraction

 

Command for HFS+J

"/Applications/Install macOS High Sierra Beta.app/Contents/Resources/startosinstall" --applicationpath "/Applications/Install macOS High Sierra Beta.app" --converttoapfs NO --volume /Volumes/USB --rebootdelay 30 --nointeraction

 

USB is the volumes, You can change he name of the volume

Usage: startosinstall

⬇︎

 

Usage: startosinstall --applicationpath <install macOS.app

path>

Arguments

--applicationpath, a path to copy of the OS installer

application to start

the install with.

--license, prints the user license agreement only.

--agreetolicense, agree to license the license you printed

with --license.

--rebootdelay, how long to delay the reboot at the end of

preparing. This

delay is in seconds and has a maximum of 300 (5 minutes).

--pidtosignal, Specify a PID to which to send SIGUSR1 upon

completion of the

prepare phase. To bypass "rebootdelay" send SIGUSR1 back

to startosinstall.

--converttoapfs, specify either YES or NO on if you wish

to convert to APFS.

If you do not specify this, the default is YES.--usage,

prints this message.

 

 

Its verry fast, when its finish you have to clic Terminate 

Reboot

⬇︎

 

page3i10.jpg

 

 

 

Alternate you can see my sig , My Hackintosh Stuff programme I made is MACOSXInstaller do the job verry good

 

 

 

error in install in volume 

post-979130-0-13660800-1502585320_thumb.jpg

post-979130-0-63365100-1502585361_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

Did you try: Open Sharing preferences (choose Apple menu > System Preferences, then click Sharing). Unselect the Remote disc Sharing checkbox

There's no such option as Remote Disc Sharing in the System Preferences > Sharing. All the checkboxes are already unselected.

Share this post


Link to post
Share on other sites

I'm using the ASUS BT400, works OOB in Sierra and High Sierra (with patch to enable handoff + continuity support).

It works without the need of installing any drivers in Windows 10 and Linux too

your efi please...thank

Share this post


Link to post
Share on other sites

@Bronxteck: KernelPM Patch is only needed if MSR is locked, which is not the case!

Bios is completely stock unlocked...

 

But beside of that I‘ve selected it and no changes...

Share this post


Link to post
Share on other sites

Let's check what will be changed then. ;)

 

Original apfs.efi from dp6:

dp6_apfs.efi.zip

 

Patched apfs.efi to suppress logs (thx http://www.insanelymac.com/forum/topic/291655-ozmosis/page-244?do=findComment&comment=2443313)

dp6_wo_log_apfs.efi.zip

 

Note: Seemingly we have to use the new apfs driver, otherwise it will stuck at boot logo.

 

Kext Inject - No changes, should be fine.

XCPM related patches - No changes, should be fine.

USB max limit patch - No changes.

 

Will add more info here if I can find anything interesting...

Share this post


Link to post
Share on other sites

@DSM2

Try removing EmuVariableuefi driver from Drivers64UEFI folder and reboot.

After High Sierra public Beta 4 install i got the same message on reboot, and this seemed to fix it.

Share this post


Link to post
Share on other sites

Does anyone has an Idea how to fix this error?

 

Using a Asus X299-A with an i7 7800X

I fixed it by using the apfs.efi from beta 5 (17A330h) instead of using the one from a previous beta

Share this post


Link to post
Share on other sites

hi..

@chris1111

 

is this the public one or the developer beta...

will you  need to update your "macosxinstaller" ?

c.frio

 

This is the Dev Beta 6

Not need update its work  B)

Edit***

I update later tonight  anyway for the apfs.efi drivers and also Clover

 

Edit**

after  5 test

its seems the BETA 6  not working good with startosinstall ?

Share this post


Link to post
Share on other sites

I cannot boot DP6.  Same as DP5.  It loops right after I get to the second stage of the boot process (right after the boot glitch).  In verbose mode, there is some text that appears for a fraction of a second and disappears for a few seconds, then reappears for a fraction of a second and disappears once again.  That's why I think it's looping.  The last entry I can read is the com.apple.windowserver started for 0 seconds and is pushed out for 10 seconds - something like that.  Any ideas what's going on?  It has to be one of my hardware devices or DSDT patches.

Share this post


Link to post
Share on other sites

The same to me ..7700k - Gigabyte H270 -HD630 :(DP5 - DP6) com.apple.windowserver started for 0 seconds...I think it's in the loop :(

Share this post


Link to post
Share on other sites

Let's check what will be changed then. ;)

 

Original apfs.efi from dp6:

attachicon.gifdp6_apfs.efi.zip

 

Patched apfs.efi to suppress logs (thx http://www.insanelymac.com/forum/topic/291655-ozmosis/page-244?do=findComment&comment=2443313)

attachicon.gifdp6_wo_log_apfs.efi.zip

 

Note: Seemingly we have to use the new apfs driver, otherwise it will stuck at boot logo.

 

Kext Inject - No changes, should be fine.

XCPM related patches - No changes, should be fine.

USB max limit patch - No changes.

 

@crazybirdy: New MBR patch:

attachicon.gifOSInstaller_10.13_DP6_ 17A344b.zip

 

Will add more info here if I can find anything interesting...

 

Hi PMHeart ^_^

 

is there a clover version >4152? Do you have it? What about the External NVMe Icon Patch? Any updates?

 

Cheers,

 

KGP

Share this post


Link to post
Share on other sites

The only way I managed to get the Beta 6 is with the upgrade

Create install Media and satrtosinstall does not work here
Much work remains to be done to find the solution

Share this post


Link to post
Share on other sites

Update:

Bummer, back to square one for me  :(

I get this:

 

macOS could not be installed on your computer

 

An error occurred while verifying firmware.

Quit the installer to restart your computer and try again.

 

 

and after restart the OSInstall.mpkg error.

I tested with clover r4165 and r4166. Results were the same.

 

I was trying to install the new release on a HDD formatted as APFS. I'm gonna try installing it on the same HDD with HFS format to see if that makes any difference.


 

The only way I managed to get the Beta 6 is with the upgrade

Create install Media and satrtosinstall does not work here
Much work remains to be done to find the solution

 

Did you get the same errors as I did?

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.5_18F132
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.5.zip
       
       
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
    • By Aldaro
      I have been running macOS Mojave on my system for 3 months and everything was working pretty well.  After taking an update for clover, my entire system got wrecked, and I cannot even boot to an installation environment anymore (which I really need to do since I am starting back at square one).  I still have the old EFI folder backed up, but I know it'll only be a matter of time before Apple introduces an update that requires me to update Clover in order to work correctly.  I have tried all the available memory fixes, but none of them seem to work.  I was previously using the original osxaptiofix; so, I gave v2, and v3 a try, but to no success.  I read somewhere on the main discussion board for clover that AptioMemoryFix was no longer going to be supported and I therefor decided to skip over it (not to mention it isn't even available in newer clover installation packages).
       
      System specs:
      Motherboard: GIGABYTE Z390 M GAMING
      CPU Intel core i5 9600k @ stock 3.7GHz
      RAM 32GB DDR4 2667MHz
      GPU AMD Radeon RX 580 with 8GB of GDDR5
      SSD Intel 660p 512GB NVME
      NIC: Intel i210 10/100/1000 as it is natively supported in macOS
       
      I have been using the iMac 19,1 SMBIOs as I built this machine to match it as close as humanly possible.  As for my UEFI settings, I did the usual:
      Disabled Windows specific features and secure boot
      Enabled XHCI hand off
      Enabled Above 4G decoding
      Disabled onboard NIC since it is made irrelevant by my intel i210
       
      --INJECT KEXTS--
      FakeSMC
      Lilu
      WhateverGreen
      AppleALC
      USBInjectAll -- WITH PATCHED SSDT in /EFI/CLOVER/ACPI/patched
      Below are images of the errors I am receiving when trying to boot the macOS Mojave installer.
       
      with original osxaptiomemoryfix

       
      osxaptiofixv2

       
      osxaptiofixv3

       
      Anyway, if somebody can help me figure out what's going on, that'd be greatly appreciated.  My ultimate goal is to get an install with minimal clover patches as to be better prepared when the winds of change from Apple come roaring.
       
      p.s: I have also attached a copy of my EFI folder
       
       
      EFI.zip
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-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.
×