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)

31 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

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   1 member

  • Similar Content

    • By Yabusa
      PC Setup:
      Intel Core i7 8700K
      Gigabyte Z370 HD3P
      Ballistix Sport LT 16GB
      Gigabyte RX 580 8GB
      AMD Pro WX7100 8GB
       
      I was trying to do a fresh install to get my wx7100 working as it was not. I stupidly did not do a back up immediately before, because I was trying a patch and the os was not detecting the GPU and showing 7MB in installed graphics.
       
      So my last back up was at mojave 14. I'm trying to update to 14.2 but get the following code, then it restarts. I'm in desperate need of help

       
      Attached are my config.plist and installed kexts. Any help is grateful.
       
       
      kexts.zip
      config.plist
    • By mizznfizz
      Copying this over from the other major forum as things seem pretty dead over there. Didn't see a dedicated "builds" forum here so hope this is the right spot. People on other social media recommended coming here. 
      Alright, so the build has commenced, just waiting on the power supply (ended up not realizing that I bought the compatible power brick for the HDPlex 400w and then bought the PicoPsu 160, so that is going back and HDPlex is on its way) and monitor to get here.
      Found a smoking deal on an Acer-K272HUL-Dbmidpx 27" IPS display through Newegg ($216 shipped to my door) that has gotten great reviews, be careful when looking for this as the EBmidpx (different model) looks the exact same but is a TN Panel and comes up in many of the searches.
       
      Anyways, here is specs for final build...
      - Mobo - ASRock Z370m-itx/ac [$120 amazon]
      - RAM - Crucial Ballistix Sport LT 8gb [$49 amazon]
      - WiFi/BT - Lenovo Broadcom BCM94352Z [$13 ebay]
      - SSD - Samsung EVO860 1tb [$128 amazon]
      - CPU - Intel Core i5 8400 [$185 newegg]
      - Cooler - Noctua L9i [$40 amazon]
      - Case - Wesena ITX4 v3 [$97 perfect home theater]
      - PSU - HDPlex 400w [$95 hdplex]
      - PSU Brick - Dell PA-9E 240w [$37 ebay]
      - Monitor - Acer K272HUL 27" IPS [$216 newegg]
      Total: $883 (shipping included in prices, most were free shipping)
       
      This build will be mainly for your everyday computing needs, paying bills, watching YouTube videos and the occasional light photo editing session (have other expensive hobbies now so photography has fallen to the wayside). This is coming from a mid-2011 iMac 21.5" base model that is slowly dying (getting graphical artifacts on a constant basis now and the occasional sudden reboot). The iMac is no longer compatible with any new Mac OS upgrades (no Mojave) so I figured she had a good life over the last 8yrs and it was time to pick-up something new. Since I was fairly unimpressed with the specs for the money with regards to the new Mac Mini's I figured this would be a good chance for me to do a hackintosh.
       
      Install will be a Vanilla High Sierra build, since that is the only version I have access to on my iMac. From my research I have downloaded the following kexts for install.
      - Broadcom Fix (both the firmware repo and firmware patch)
      - IntelMausiEthernet
      - WhateverGreen
      - Lilu
      I am using the two following builds on the other forum as my baseline as they are very similar builds to mine.
      Suneys Mini Cube from the other forum and the Tiny But Might build from the same forum. 
       
      With that said, I plan to use Morgonaut's guide from YouTube to build the hackintosh up (hopefully next weekend). Once everything is running stable in High Sierra I will hopefully be able to update to Mojave without any major issues and then keep moving forward with life. So, am I forgetting anything?
    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Spoofing Intel CPU Gen
      If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
       
      Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - S/L/E/AppleIntelSNBGraphicsFB.kext
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
      - AAPL,snb-platform-id (desktop): 0x00030010 (default)
      - AAPL,snb-platform-id (laptop): 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - S/L/E/AppleIntelFramebufferCapri.kext
      - Support started with OS X 10.8.x
      - device-id: 0x0152 0x0156 0x0162 0x0166
      - AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
      - AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - S/L/E/AppleIntelFramebufferAzul.kext
      - Support started with OS X 10.9.x
      - device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
      - AAPL,ig-platform-id (desktop): 0x0D220003 (default)
      - AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
      - Support started with OS X 10.10.2
      - device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
      - AAPL,ig-platform-id (desktop): 0x16220007 (default)
      - AAPL,ig-platform-id (laptop): 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
      - Support started with macOS 10.12.6
      - device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
      - AAPL,ig-platform-id (desktop): 0x59160000 (default)
      - AAPL,ig-platform-id (laptop): 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - device-id: 0x3E9B 0x3EA5 0x3E92 0x3E91
      - AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Hackintool File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Hackintool File->Import->IOReg Dump menu
       
      3. Using Hackintool Framebuffer->macOS 10.14 menu
       
      Debug Output
      To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help

      To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.

      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By spec3
      Hi,
       
      is there a way to download 10.14.1 now? , i need to downgrade from 10.14.2..
       
      I would like to reinstall from zero, because i have problem of compatibility with some apps with 10.14.2.
       
      thanks
    • By Yuvraj Harod
      Hey there,
      Hope everything is fine with you admin
      I was installing Mojave and m constantly facing one single error please help me out with this
      An error occurred while running scripts from the package "OSInstall.prescript.pkg"
      quite installer to restart your computer 
      IDK why is this happening 
      My Notebook's Specs:
      i3 3110M 2.40ghz
      4GB Ram ddr3
      GTX 720M
      1TB hdd
       
      PS; I've already converted HDD into GUID Partition 
       
      I'm waiting for a reply dear
      hope to hear from you soon!
×