Jump to content
Allan

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

449 posts in this topic

Recommended Posts

Advertisement

New createinstallmedia terminal command?

 

There is no new createinstallmedia terminal command - it's always the same and works well.

Usage: createinstallmedia --volume <path to volume to convert>

Arguments
--volume, A path to a volume that can be unmounted and erased to create the install media.
--applicationpath, A path to copy of the OS installer application to create the bootable media from.
--nointeraction, Erase the disk pointed to by volume without prompting for confirmation.

Example: createinstallmedia --volume /Volumes/Untitled

This tool must be run as root.

Result:

Last login: Tue Sep 26 10:43:58 on ttys000
fantomass-iMac:~ fantomas$ sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ High\ Sierra.app 
Password:
Ready to start.
To continue we need to erase the volume at /Volumes/USB.
If you wish to continue type (Y) then press return: y
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.
fantomass-iMac:~ fantomas$

Share this post


Link to post
Share on other sites

 

Hi Guys,

 

Successfully updated both my desktop systems and my Dell XPS M1530 notebook to High Sierra Release - 10.13_17A365 :).

 

1.  GA-P55aUD3 with legacy BIOS/Intel i5-750/ATI HD5770/HFS+ HDD

 

2.  Skylake NUC6i5SYH with UEFI/Intel i5-6260U/Iris 540/APFS SSD

 

3.  Dell XPS M1530 legacy BIOS/Intel T9300/Geforce 8600M GT/HFS+ Ext HDD

 

 

Installation Notes
  • "Install macOS High Sierra.app" v 13.0.64 run directly from Applications folder for upgrade install of existing GM_17A362a
  • Updated to latest Clover r4220, Clover injected default values for FF/FFM/PF and BIOS ver/date/Board-ID data (iMac11,3, iMac17,1, MBP7,1) --> avoid error while "verifying firmware"
  • Latest apfs.efi driver in /EFI/CLOVER/drivers64 or /EFI/CLOVER/drivers64UEFI (only needed if APFS target volume)
  • Removed NVRAM.plist files from all EFI partitions (incl USB drives), ran sudo NVRAM -c command in terminal to reset NVRAM prior to update
  • On my Skylake NUC, I don't need or use EmuVariableUefi-64 ---> avoid OSInstall.mpkg damaged/missing error
  • If upgrading existing OS X on HDD, HFS+ is preserved (on SSD HFS+ will be converted automatically to APFS)
  • Certain SATA controllers will still have issues with AppleAHCIPort v329 (eg ICH10, 5 series, 7 series, ASMedia 1061) ---> Disks may fail to initialize, not readable or hot plug may fail.  AppleAHCIPort.kext v328 with version bundle 999.1.1 survives upgrade if installed in /L/E, and is loaded in preference to v329
  • A windows disk present on the machine during installation is OK.

 

Here, with the kexts on 10.13, the installer did not go up, only in Other.

 

EFI/Clover/kexts/Other

 

 

 

Share this post


Link to post
Share on other sites

 i have used same config.plist and kext/other that im runing with beta version to install the final version but stuck at

 

sound assertion in applehdadriver at line

 

any idea ?

Share this post


Link to post
Share on other sites

Guys, if you still are on a beta or GM build, do not bother with creating a new usb installer with createinstallmedia, use startosinstall instead. :yes:

 

It will start HSierra install and will save you time and stress. :P;)

 

 

what is the method to install in HFS? :rolleyes:

 

 

my HDD is in HFS! ;)

Share this post


Link to post
Share on other sites

Guys, if you still are on a beta or GM build, do not bother with creating a new usb installer with createinstallmedia, use startosinstall instead. :yes:

 

It will start HSierra install and will save you time and stress. ;)

 

 

 

 

my HDD is in HFS! ;)

I just ran the .app I downloaded from app store. What is startosinstall?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

You'll find it in the same folder as createinstallmedia 

 

/Applications/Install macOS Sierra.app/Contents/Resources

 

For me the installer has only 20 MB, why ? 

Share this post


Link to post
Share on other sites

I found something interesting on my ICH10 hack with 10.13:

I have 2 HDD WesternDigital that not working under 10.13 with AppleAHCIPort v329

Also I have 1 HDD Hitachi and 1 SSD Kingston that are working fine under 10.13 with v329

I tried changing sata ports but the result is the same: WD HDDs not working and Hitachi HDD and Kingston SSD are working fine, I can install HS on them without any trick(changing AppleAHCIPort or anything).

Share this post


Link to post
Share on other sites

I just ran the .app I downloaded from app store. What is startosinstall?

 

Sent from my SM-G930F using Tapatalk

You can find explanation on previous thread: http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/page-191 But I don't try it because I don't know how to migrate apps and data with this method

Share this post


Link to post
Share on other sites

Anyone has tried with an amd r7 vga?

 

I've got the black screen after apple logo problem, but the strange thing is that lilu + whatevergreen didn't fix it. I'm also using Pike's path for GraphicPolicy.kext

 

I'm using the r7 260x with fakeid injection connected with displayport. Even if screen si black I can hear sound routed from the vga.

Also if I boot with the intel igpu I can notice that the 260x is detected and (as ioRegistyExploer reports) everything is as in El Capitan.

 

I couln't understand why it isn't working.

 

 

Inviato dal mio iPhone utilizzando Tapatalk

Share this post


Link to post
Share on other sites

how did you install it in HFS?

 

 

As I said, I previously had GM installed on my HFS+ formatted HDD. Then I downloaded HS final release. When I wanted to create my new usb installer with createinstallmedia, I was curious about that startosinstall file that I found in the same folder (/Applications/Install macOS Sierra.app/Contents/Resources). I just clicked on it and Terminal was opened. Asked me to agree the licence (put A for agree) and my PC rebooted. After rebooting, it directly came at the second stage, when the install started (it remains 45minutes...).   :)

 

EDIT:

 

As I launched that file from my primary partition (to be installed on it), the installation processing worked well (finally, it more updated my GM build, instead of made a proper install), my apps and files were all safe.   :yes:

 

EDIT 2:

 

The funny thing in this story is that I have no longer HS app in my Application folder.   :P . I guess it served as a temporary file and once installed ,the app has been deleted.

Edited by fantomas1

Share this post


Link to post
Share on other sites

All fine except sleep (first hack in signature).

0YM1ZkS.png


LuCys-Mac-Pro:~ lucy$ diskutil ap convert disk3s3
Started APFS operation on disk3s3 High Sierra
Converting HFS Volume to an APFS Container which will export one APFS Volume
The target is the Journaled HFS+ volume "High Sierra" backed by the GPT partition disk3s3
Exiting conversion operations with error code -69546
Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

Any suggestions?

Share this post


Link to post
Share on other sites

All fine except sleep (first hack in signature).

0YM1ZkS.png

LuCys-Mac-Pro:~ lucy$ diskutil ap convert disk3s3
Started APFS operation on disk3s3 High Sierra
Converting HFS Volume to an APFS Container which will export one APFS Volume
The target is the Journaled HFS+ volume "High Sierra" backed by the GPT partition disk3s3
Exiting conversion operations with error code -69546
Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

Any suggestions?

Boot with macOS High Sierra installer and run the command in terminal 

Share this post


Link to post
Share on other sites

Boot with macOS High Sierra installer and run the command in terminal 

Thanks, but I can't do this because my drive isn't recognized in installer because of AppleAHCIPort, I explained it at post #64

Share this post


Link to post
Share on other sites

Thanks, but I can't do this because my drive isn't recognized in installer because of AppleAHCIPort, I explained it at post #64

Which of your hard disks is disk3s3? I assume that's the one that you are trying to convert to APFS. Right?

Share this post


Link to post
Share on other sites

Which of your hard disks is disk3s3? I assume that's the one that you are trying to convert to APFS. Right?

Yes, it's an WD 320GB with High Sierra installed.

Share this post


Link to post
Share on other sites

All good here, when returning from sleep USB devices are ejected is there any way/patch to fix it?

installing CUDA 9RC davinci resolve not recognize CUDA...strange

post-474300-0-75240100-1506433958_thumb.png

Share this post


Link to post
Share on other sites

Yes, it's an WD 320GB with High Sierra installed.

Sorry I'm confused, the installer doesn't recognize that HDD but in an installed version it's detected?

Share this post


Link to post
Share on other sites

Sorry I'm confused, the installer doesn't recognize that HDD but in an installed version it's detected?

I installed it on an recognized hdd and then restore the unrecognized hdd from high sierra installed with disk utility then replaced AppleAHCIPort and it's working.

Sorry, it's a little complicated, I hope you understand now :D

 

Sent from my HTC One M9 using Tapatalk

Share this post


Link to post
Share on other sites

I installed it on an recognized hdd and then restore the unrecognized hdd from high sierra installed with disk utility then replaced AppleAHCIPort and it's working.

Sorry, it's a little complicated, I hope you understand now :D

 

Sent from my HTC One M9 using Tapatalk

Ok, I see, in that case you might be able to boot from the recovery partition on your WD HDD and use the terminal in the recovery mode. But since you didn't install the macOS directly on that hard disk you might be missing the recovery partition.

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 glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs) New!
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • By fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo

      View full article
×