Jump to content
fusion71au

Making a bootable High Sierra USB Installer Entirely From Scratch in Windows or Linux Mint (without access to Mac or App Store Installer.app)

34 posts in this topic

Recommended Posts

On 11/23/2017 at 1:45 AM, fusion71au said:

6)  Type dmg2img -l BaseSystem.dmg to list the "partitions" in the compressed disk image file "BaseSystem.dmg"...

 

 

What exactly are we looking for when we run this command? Are we looking for the partition that lists "disk image"?

 

I am thinking of making a python program that can automate this on Linux, but I need to know the takeaway from running this command.

Share this post


Link to post
Share on other sites
Advertisement
On 11/20/2017 at 4:59 PM, fusion71au said:

Updated Download Links for macOS Mojave 10.14_18A391

Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...

  1. BaseSystem.dmg
  2. BaseSystem.chunklist
  3. InstallInfo.plist
  4. InstallESDDmg.pkg
  5. AppleDiagnostics.dmg
  6. AppleDiagnostics.chunklist

 

How did you find 10.14 18A391? When I tried looking through the software catalog link you gave there, I could only find the following versions:

10.13.6 (17G65)
10.13.6 (17G2208)
10.14.1 (18B75)
10.14.1 (18B2107)
10.14.1 (18B3094)

 

This is the process I followed to find these versions
1. I looked for all "BaseSystem.dmg" URLs in the catalog and noted them

2. I looked at the "English.dist" corresponding to each of those BaseSystem URLs (since both share a similar URL pattern)

3. I noted the build and version of each English.dist.

 

Did I do that right? Following these steps, I could only find the above mentioned 5 builds from the catalog. Where is 10.14 18A391?

 

Reason I'm asking: I was trying out a weekend project to make a tool that would automatically parse an apple catalog XML for you, find the different mac builds in it and download the files of whichever one you choose (and automatically rename InstallESDDmg.pkg and update InstallInfo.plist). So I wanted to figure out the exact process of extracting the different macOS files and versions from the catalog

Edited by george_m

Share this post


Link to post
Share on other sites
On 11/22/2018 at 5:27 AM, george_m said:

 

How did you find 10.14 18A391? When I tried looking through the software catalog link you gave there, I could only find the following versions:


10.13.6 (17G65)
10.13.6 (17G2208)
10.14.1 (18B75)
10.14.1 (18B2107)
10.14.1 (18B3094)

 

This is the process I followed to find these versions
1. I looked for all "BaseSystem.dmg" URLs in the catalog and noted them

2. I looked at the "English.dist" corresponding to each of those BaseSystem URLs (since both share a similar URL pattern)

3. I noted the build and version of each English.dist.

 

Did I do that right? Following these steps, I could only find the above mentioned 5 builds from the catalog. Where is 10.14 18A391?

 

Reason I'm asking: I was trying out a weekend project to make a tool that would automatically parse an apple catalog XML for you, find the different mac builds in it and download the files of whichever one you choose (and automatically rename InstallESDDmg.pkg and update InstallInfo.plist). So I wanted to figure out the exact process of extracting the different macOS files and versions from the catalog

 

Yes, you are correct.

 

Apple removed the URLs for 10.14_18A391 from the software catalog and replaced them with URLs for 10.14.1_18B75.  I just hadn't gotten around to updating the links for 10.14.1 in the first post :).

 

On 11/12/2018 at 9:32 AM, CuriousTommy said:

 

What exactly are we looking for when we run this command? Are we looking for the partition that lists "disk image"?

 

I am thinking of making a python program that can automate this on Linux, but I need to know the takeaway from running this command.

 

Yes, you need the partition number of the hfs BaseSystem image for the next step...

 

sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sdb3

 

Share this post


Link to post
Share on other sites

@fusion71au I followed the instructions for the installer, but when I boot to Clover and select the Mac partition it shows the Apple Logo, then reboots my system and bounces me back to the Clover screen - this loops continuously. I had previously installed using VMWare and the command line following some of your other posts, but now I'm looking for a dual boot solution so I can leverage my GPU. Any idea what would cause the loop of Clover > Apple Logo > Restart > Clover? Just need an idea of how to troubleshoot. I'm a complete n00b when it comes to Clover.

 

I'm happy to provide any additional details you need.

 

Specs:

Motherboard: ASUS Rog Strix z370e, CPU: Intell i5-8600k, GPU: Nvidia GeForce GTX-1060, Storage: 2TB HDD and 2x 500 GB Samsung Evo SSD, OS: Windows 10 Pro

 

 

Share this post


Link to post
Share on other sites

 
Hello. I'm trying on linux and can't do that


1) 7Z l BaseSystem.dmg gives me many text, i attached file

2) dmg2img gives error:

 

Quote

[awful@memory SharedSupport]$ sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sda3
[sudo] password for awful:

dmg2img v1.6.7 (c) vu1tur (to@vu1tur.eu.org)

BaseSystem.dmg --> /dev/sda3

reading property list, 44376 bytes from address 486174238 ...
partition 0: begin=203, size=430, decoded=284
partition 1: begin=948, size=430, decoded=284
partition 2: begin=1695, size=430, decoded=284
partition 3: begin=2424, size=430, decoded=284
partition 4: begin=3137, size=34763, decoded=23404
partition 5: begin=38183, size=430, decoded=284
partition 6: begin=38911, size=430, decoded=284
partition 7: begin=39656, size=430, decoded=284

decompressing:
opening partition 4 ...       [574]  98.97%ERROR: writing file /dev/sda3

[awful@memory SharedSupport]$ lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda           8:0    1 14.5G  0 disk
├─sda1        8:1    1  200M  0 part
├─sda2        8:2    1  5.7G  0 part
└─sda3        8:3    1  1.9G  0 part

 

Please help me. Thanks!

1.txt

Share this post


Link to post
Share on other sites

I Just created a account here to say thank you. I've looked for months a solution. Only this worked. 

I Just created a account here to say thank you. I've looked for months a solution. Only this worked. 

Share this post


Link to post
Share on other sites

I ve been through some of the steps. I restored the hfs file to the second partition. Then on trying to extend the partition to the maximum, I cant do that. The software suggested here is paid. So i tried using alternatives. I get the error that "no partition table found on this device."

 

How do i proceed? Anyone else experiencing similar problems? 
THanks

Share this post


Link to post
Share on other sites

WOW, I really could've started from vanilla, without commercialized software, to get to the App Store to download and create a vanilla usb!!! Really wish I knew about this method before.

 

Has this ever been a option before?

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 tonyx86
      I was inspired by @duduclx post for installing El Capitan on a Dell Latitude E6410, so I decided to install Mojave 10.14.5.  Everything works perfectly except for sleep.  I'm starting this thread hoping to help others install Mojave on their E6410s and to diagnose and resolve the sleep issue.  This thread is not currently intended to be an installation guide and is better suited to the intermediate/advanced hackintosher.  Eventually, it may evolve into a guide.
       
      I started with this thread (Many thanks, @duduclx !!!) and ended up with the system captured in the attached files.  The keys were to change the LPCB._DSM.Name to "3b09" and remove all CLOVER configs not necessary for Mojave, plus some other items mentioned below.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) MacOS: Mojave 10.14.5 (APFS) (Patched with DosDude Mojave Patcher 1.3.3) MacModel: MacBookPro 6,2 (LPCB._DSM.Name "pci8086,3b09") Kexts: Lilu 1.3.6, VoodooHDA 2.9.2, AirportBrcmFixup 2.0.0, IntelMausiEthernet 2.4.1d1, ACPIBatteryManager 1.90.1, BrcmPatchRam2.kext, BrcmFirmwareRepo.kext, VoodooPS2Controller (the "Refined ALPS Touchpad" version - release 5, not the original version) Wi-Fi: Broadcom BCM 94352HMB (with AirportBrcmFixup.kext) MacOS: Mojave 10.14.5 CLOVER (Legacy): R4961  
      Configuration items that may be different from what you have seen in other E6410 configurations
      LPCB._DSM patched with device-id "3b09" AND "name", "pci8086,3b09" for native Nehalem power management with MacBookPro 6,2 ECDV renamed to EC so that AppleBusPowerController loads AGP.VID._DSM patched with device-id "0a29" so that AppleGraphicsPowerManagement loads  No CLOVER Generate P or Generate C States (with the correct LPCB._DSM and MacBookPro 6,2, these CLOVER options are unnecessary for this architecture and only limit max multiplier and reduce number of P states) DSDT patched to include HDAU device (device-id 0x0be3)   
      What is NOT working:
      Sleep (display goes blank, but power light stays on.  System cannot wake and must be forced off with power button) Display brightness can be controlled with keyboard keys, but cannot be controlled with slider in Display settings.  The slider appears in Display settings (because of the backlight DSDT injection in AGP.VID._DSM), but the slider doesn't work (yet).  Haven't spent time to figure this out, but would love help. Graphics Power Management - AGPM loads (because 10de,0a29 device is injected), but there's no evidence that 3100m frequency and voltage is changing.
        What is NOT tested:
      SD Card Slot Smartcard Reader eSata (I have this disabled in my BIOS) Display Port Firewire Port (it does appear in the Network settings, just haven't tried it) Microphone Jack PC Card Slot (I have this disabled in my BIOS) Camera (I have this disabled in my BIOS)  
      What IS working:
      Everything else not mentioned above.   Speedstep/CPUPowerManagement is perfect, system temps are low, CPU multiplier operates as expected, battery life is long Shutdown is fast Display/graphics acceleration is perfect (thanks to DosDude's Mojave patcher) Brightness (adjusted with brightness keys on keyboard) works perfectly Battery Manager works (battery status is displayed in menu bar) simply by installing ACPIBatterManager.kext. Wi-Fi (after changing to Broadcom BCM94352HMB and installing AirportBrcmFixup.kext) Audio (volume adjustable, volume indicator appears in menu bar).  Switched to VoodooHDA from AppleALC after AppleALC caused slow boot due to "IOHDACodecFunction timeout." Ethernet port (with IntelMausiEthernet.kext) Broadcom BCM20702A0 Bluetooth (with BrcmPatchRam2.kext and BrcmFirmwareRepo.kext) Optical Drive External VGA (with corrected NVCAP.  Need NVCAP 04000000 00000100 0E000000 00000007 00000000 (credit: @PlutoDelic) for working external VGA display. Headphone jack  
      Known issues and their solutions
      AAPL,clock-id and device_type do not appear in IORegistry for EHC1.  Solution is to use CLOVER on-the-fly patching/fixing/renaming for EHC1 and EHC2.  This has been completed and tested, but does not fix the sleep behavior.  This fix is not reflected in the attached files. ALPS trackpad performance is not good with the "standard" VoodooPS2Controller.kext that I initially used.  Switching to the "Refined ALPS TouchPad driver" is a big improvement.  I've implemented and tested this on my system.  The ALPS version of VoodooPS2Controller.kext mixes up a few keys.  Need to switch the Command and Option keys (System Preferences > Keyboard > Modifier Keys) and change keyboard type to ISO European.  The updated VoodooPS2Controller.kext is not reflected in the attached files. This proposed configuration uses an injected device-id (10de,0a29) for NVidia 3100m to get AGPM to load.  While I haven't observed any performance differences, a better approach may be to inject AGPM properties for device 10de,0a6c (the actual device-id for the 3100m).  This AGPM method is discussed later in this thread.  I have briefly tested this "FakeSMC.kext method" for injecting AGPM attributes without any noticeable changes in laptop/graphics behavior and have not updated attached files to reflect this change. IOHWControl is not loaded under AGPM (Should be AGP > VID > NVDA,Display-A@0 > NVDATesla > AGPM > gpu-control > IOHWControl as viewed in IORegistryExplorer).  It is loaded on a real MacBookPro6,2 running Mojave and is loaded on this Dell Latitude E6410 running High Sierra.  If I "Inject NVidia" via CLOVER, IOHWControl loads properly.  I have made this change and am testing it on my system, but have not updated the attached configuration files. The Dell Latitude DSDT (BIOS A17) has a bug in Method (GNOT).  In the method, the expression  If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6))) always evaluates to TRUE, so the patched DSDT has no dependency on the value of OSYS.  I suspect that LOr should be replaced with LAnd, so that this expression is TRUE for variants of Windows 2001 and False for any other OS.  While this may have no affect on MacOS, it makes one wonder how such an obvious bug made it through Dell QA and is still present in BIOS A17.  Also makes one wonder whether the sleep problem (which no one has solved) was fixed in Windows to address another DSDT bug.  
      Brief Installation Guide (for the experienced Hackintosher):
      Follow duduclx's guide for BIOS config Create your MacOS installer USB (Use DosDude's Mojave Patcher for Mojave) (start with High Sierra and not Mojave if you're new to hackintosh). Install CLOVER (Legacy) on installer USB using attached EFI as your guide for patched ACPI, kexts and config.plist Install MacOS to your SSD Install the following kexts in /Library/Extensions:  ACPIBatteryManager.kext, AirportBrcmFixup.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakeSMC.kext, FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_GPUSensors.kext, FakeSMC_LPCSensors.kext, IntelMausiEthernet.kext, Lilu.kext, USBInjectAll.kext, VoodooPS2Controller.kext (the "Refined ALPS Touchpad driver," not the original) Switch Command and Option keys to compensate for Refined ALPS driver issue (System Preferences > Keyboard > Modifier Keys).  Also change keyboard type to ISO European to fix the [ ` ~ ] key (to the left of the "1" (one) key. Install VoodooHDA Install HWMonitor application  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z  
       


      CLOVER.zip
    • By Jessi-mj
      No success so far.
       
      There is no way I can get Mojave (or High Sierra) to install on this rig.
       
      I'd be really grateful for any help.
       
      My config is 
      Asus Maximus XI Hero (no WiFi); 
      I9-9900k; 
      Sapphire triX Radeon R9 290; 
      Corsair Pro RGB 2x16GB CMW32GX4M2C3200C16
       
      I am using my R9 290 I had at home because I don't need powerful graphics really.
       
      So what I've done
      1) Created USB installation drive using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] -  UEFi option
       
      2) Bios settings
      - Updated BIOS to lastest version
       
      - Load Optimised defaults
       
      - applied the following
      VT-d, disabled
      CFG-Lock, disabled
      Secure Boot Mode, disablef
      OS Type set to Other OS
      XHCI Handoff Enabled
      AI Overclocked set to XMP 3200
      Extreme twerking enabled
      Graphics Primary display set to PCIe
      Legacy USB support enabled
      Power on by PCI disabled
      Fast boot disabled
      Boot logo display disabled
      Boot option 1 set to UEFI usb installer
      Saved and rebooted.
       
      I either get no screen response (stuck in qcode 99 on MB) or stuck on PCI configuration begins.
       
      So what am I doing wrong?
       
      Five hours of trial and error and I gave up on installing from USB.
       
      I am now  installing Mojave from my MacBook Pro to SSD and will use [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] before moving the drive over to my PC
       
      The settings I am going to use in [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]
       
      Quick Start > UEFI Boot Mode
      Drivers > Audio > AppleALC
      Drivers > Misc > FakeSMC Plugins
      Drivers > Misc > FakeSMC HWMonitor Application
      Drivers > Misc > Core Graphics Fixup AKA WhateverGreen
      Drivers > Network > Intel > IntelMausiEthernet (I used the latest version)
      Drivers > USB > Remove XHCI USB Port Limit <--- Adds PMHeart’s patch to remove XHCI USB Port Limit
      Drivers > USB > USBInjectAll
      Bootloaders -> Clover v2.4k r4xxx UEFI
      Customize -> System Definitions > iMac > iMac18,3
       
      If you have any suggestions please help.
       
      Perhaps someone can share their EFI folder for a similar rig?
       
    • By Kielligzind
      Hello, i am trying to boot the installer of MacOS Mojave 10.14.5 on my HP Z220 CMT Workstation, but it gets stuck at this error. i attached pictures of this error and i posted my EFI folder. 
      i hope someone can help me. Thanks in advance.
       
      https://drive.google.com/file/d/1qH_ok-jzIwiLXd5LEEvVloRFZDgPAY2d/view?usp=sharing
       

    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14.
      4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+ partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.14 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      How to make 10.14 installer for MBR (MBR-Automatic-Method)?
      Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.13.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       


       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.
       

       
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.13 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.13 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?

      How to make 10.13 installer for MBR (MBR-Automatic-Method)?
      Just use 13MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, new for 10.13+.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       


       
×