Jump to content
ACDindia

[HELP] MSI GV62-7RE Laptop| Installation: Boots only with invalid GPU FakeID

18 posts in this topic

Recommended Posts

Dear All,

 

I followed the Olarila (MaLd0N's) guide and made the Mojave USB.

I had to install the system using an invalid GPU FakeID (0x12345678) to get past the KP.

Even after installation, my system going into KP if I don't use this invalid fakeid.

With the FakeID, my system reports 7mb VRAM with Intel HD630.

I am using the DSDT from my 10.13 installation.

 

Used:

Whatevergreen.kext

Tried putting different FakeIDs

Put the Whatevergreen and Lilu in /Library/Extensions

Tried without Whatevergreen. The same setup used to work with 10.13.

 

My Laptop details are in my signature.

This is the link to the last time MaLd0N helped me get 10.13 working: https://www.insanelymac.com/forum/topic/332021-msi-gv62-7re-1013-installation/

 

Please help anyone.

 

Thanking you

 

Share this post


Link to post
Share on other sites
Advertisement

Hey! Thanks for the response Hervé!

I was reading the whatevergreen article... it asked to not inject Intel ?

I think I tried the MacBookPro14,3 ID...

I will give it a try again... will revert back...

Share this post


Link to post
Share on other sites
1 hour ago, Hervé said:

I guess you'll need to apply the necessary DVMT changes/patches that apply to HD630 graphics.

I think the “Whatevergreen.kext” does include all those fixes? Is there something that I should be doing to enable the same ??

Share this post


Link to post
Share on other sites
On 8/17/2018 at 7:53 AM, ACDindia said:

I think the “Whatevergreen.kext” does include all those fixes? Is there something that I should be doing to enable the same ??

 

Go to bios menu and set DVMT or Intel GPU minimum allocated memory setting to 64mb. 

Edited by Gigamaxx

Share this post


Link to post
Share on other sites
11 hours ago, Gigamaxx said:

 

Go to bios menu and set DVMT or Intel GPU minimum allocated memory setting to 64mb. 

Hey! Thanks for the response mate!

There isn’t any option in my BIOS which says anything about DVMT it minimum allocated memory.

I checked Windows and saw that the minimum memory given is 128 MB already.

I’ve read somewhere that we should reduce 32MB from what windows shows and it’s then the minimum allocated memory.

i think it’s alright ?

rectify me if I’m wrong..

thanks again!!

Share this post


Link to post
Share on other sites
36 minutes ago, ACDindia said:

Hey! Thanks for the response mate!

There isn’t any option in my BIOS which says anything about DVMT it minimum allocated memory.

I checked Windows and saw that the minimum memory given is 128 MB already.

I’ve read somewhere that we should reduce 32MB from what windows shows and it’s then the minimum allocated memory.

i think it’s alright ?

rectify me if I’m wrong..

thanks again!!

 

A lot of laptops come with 32mb min and that is a problem for MacOS it needs 64mb to function well.    Search for “min stolen size patch”.    It’s a fix for laptops that don’t have bios that allows 64mb settings.

Share this post


Link to post
Share on other sites

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)

fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:

setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

Edited by headkaze

Share this post


Link to post
Share on other sites
2 hours ago, headkaze said:

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)


fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:


setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

I’ll give this a try... thank you so much for the effort..

I’ll report back..

Share this post


Link to post
Share on other sites
5 hours ago, headkaze said:

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)


fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:


setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

 

Thank you!

 

I verified and successfully edited the lines as suggested and now the system boots fine.

Only that my old DSDT won't work anymore.

No HDMI Display.

Any solution to that ?

 

Thanks a ton man!

 

Share this post


Link to post
Share on other sites
On 8/20/2018 at 4:00 PM, headkaze said:

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)


fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:


setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

 

Hey! So I tried it... inserted the required data but still don’t have any HDMI output... please help...

also, how to get the battery status ?

thank you!

Share this post


Link to post
Share on other sites
On 8/20/2018 at 6:41 PM, headkaze said:

 

 Check out this guide

 

Hey! Please guide me a bit more on this.. Couldn't get it fixed.

 

My entries are in the attached picture.

1430967450_Screenshot2018-08-22at4_04_42AM.thumb.png.e86dd23bccac335b67eaf72f9c82fed4.png

 

System boots fine and I even have 2GB of VRAM.

Still, no HDMI :( :'(

 

PLEASE HELP......

 

Thank you!!

Share this post


Link to post
Share on other sites

So I compiled a new Whatevergreen.kext with New Lily (Debug) and used it. This time when I plugged in my HDMI, the system restarted...

Share this post


Link to post
Share on other sites

I’ve figured out one thing:

by mistake my InjectIntel was ticked as yes. And that was giving me a crash.

I’ve unchecked the same and now I’m back to just nothing...

when I connect the HDMI, nothing happens.

I tried going to Settings>Display and then tried doing “Detect Display” and still got nothing..

 

please, can someone help me ?

Share this post


Link to post
Share on other sites
1 hour ago, ACDindia said:

when I connect the HDMI, nothing happens.

 

If your HDMI port is connected to your eGPU you may not be able to use it. Maybe try the mDP with an adapter instead?

 

Also you should not set framebuffer-fbmem / framebuffer-unifiedmem as you have already set your DVMT-prealloc.

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 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 0x3EA6 0x3E92 0x3E91 0x3E98
      - 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 fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
    • 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, 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 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
    • 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
×