Jump to content
Sign in to follow this  
Followers 0
HurricaneX

How To Install Supplementary Update(17A405) Using MBR For 10.13?

23 posts in this topic

Recommended Posts

Hey,guys,I wanna know how to install Supplementary Update(17A405) from App store using MBR For 10.13?It seemed that the update would never be applied when restarting to the desktop next time.Any suggestions to fix this?Thanks very much in advance!

 

Bootloader:Chameleon(10.12.6) + Clover(10.13) + MBR
OS: Win 7 Ultimate x64 SP1 + macOS Sierra 10.12.6 + macOS High Sierra 10.13
Processor: Intel® Core2 Quad CPU Q9650 @3 GHz
Motherboard: GA P43T S3L
GPU: NVIDIA GeForce GTX 650 2G
RAM: 16 GB 1333 MHz DDR3
Sound:Realtek ALC 888
Network: Realtek RTL8168D/8111D
 
 
 
 

post-1231439-0-04499100-1507951013_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

 

I had a similar problem (and I too have an MBR setup).  Rather than installing the update from the App Store, I downloaded and installed it from the following link, which worked:

 

https://support.appl...37?locale=en_US

 

I hv tried to use the offline update package,but finally it failed after restarting computer!Does this need some changes in the Clover configuration or neccessary kexts put in the EFI/Clover/kexts?

post-1231439-0-92806000-1508121169_thumb.png

Share this post


Link to post
Share on other sites

How did you get the HS to install to MBR? I'm trying using Enoch BL but no joy yet....

using MBR patch...

http://www.insanelymac.com/forum/files/file/762-high-sierra-mbr-and-firmware-check-patch/

Follow this tutorial to create a bootable USB/drive to install HS 10.13 on MBR!

Share this post


Link to post
Share on other sites

Did you hide your Preboot partition? Unhide it and it'll show you a entry named "macOS Install", use App Store to install it and reboot to that entry

Share this post


Link to post
Share on other sites

Did you hide your Preboot partition? Unhide it and it'll show you a entry named "macOS Install", use App Store to install it and reboot to that entry

I know the Preboot partition,but many hackintoshers confirmed that it is just available on GPT.Is there any method to show or create the Preboot partition on MBR?

Share this post


Link to post
Share on other sites

I know the Preboot partition,but many hackintoshers confirmed that it is just available on GPT.Is there any method to show or create the Preboot partition on MBR?

Hmm, that's hard. You can try some partition tool on Windows to convert it, I don't think it will work :(

Share this post


Link to post
Share on other sites

I tried building an MBR installer using the Supplemental installer but it won't install....guess the mods need tweaking for the supplement, so far cannot update the package from App Store or with stand along download update...

Need to crack the update and find our where it is failing....

Share this post


Link to post
Share on other sites

I tried building an MBR installer using the Supplemental installer but it won't install....guess the mods need tweaking for the supplement, so far cannot update the package from App Store or with stand along download update...

Need to crack the update and find our where it is failing....

 

indeed, I am afraid subsequent update of 10.13.1 and onwards will face the issue too. let's hope a solution will come to light soon ..

Share this post


Link to post
Share on other sites

Looking at the logs, it appears that the Supplemental update is looking for a partition (maybe  the rescue partition)...and not having it in MBR it fails.... I wonder if there is a way using MBR to create that partition?

Share this post


Link to post
Share on other sites

Looking at the logs, it appears that the Supplemental update is looking for a partition (maybe  the rescue partition)...and not having it in MBR it fails.... I wonder if there is a way using MBR to create that partition?

Yes,u need to select the rescue partition called"Preboot" to apply the updates when the computer restarts.And this is the only entry to apply the updates.Maybe we can try to manually create the Preboot partition for the updates.So what is the partition format of the Preboot partition?

Share this post


Link to post
Share on other sites

Looking at the logs, it appears that the Supplemental update is looking for a partition (maybe  the rescue partition)...and not having it in MBR it fails.... I wonder if there is a way using MBR to create that partition?

 

This did not happen during Sierra or El Capitan; am wondering whether it is a one off (needed by this particular supplemental update) or is it a new 'feature' of High Sierra system updates? Certainly hope it is the former ..

Share this post


Link to post
Share on other sites

I wonder if a 600 mb HFS+ partition called "Preboot" would do it.... ? 

 

interesting suggestion :) worth a try at least; is it possible to resize HFS+ partition under MBR? if i remember correctly, it cannot be done, needs a reformat ..

Share this post


Link to post
Share on other sites

With MBR how the devil do you get a recovery partition???

 

I installed it using the updated MBR patch posted on downloads, per crazybirdy... works perfectly with clover but no recovery partition was created....checked drive with GPRTD and nothing showing...

Share this post


Link to post
Share on other sites

I have the same problem on my laptop (Legacy+Chameleon+MBR system), I used to update my hack by download offline update installer then install it directly. But on High Sierra, it seems not to be working anymore :(.
But for me, there's a workaround. Thank God I have High Sierra installed on my external drive, so I booted my laptop to my High Sierra external drive and install updater pkg to High Sierra partition on laptop's internal drive(installed it just like normal application). After that, I rebooted back to High Sierra on laptop's internal drive, aaaand it worked(I think :)), even if installer show "install failed" before.

 

post-886162-0-42514900-1509816983_thumb.png

post-886162-0-76932100-1509817012_thumb.jpg

Share this post


Link to post
Share on other sites

I booted my laptop to my High Sierra external drive and install updater pkg to High Sierra partition on laptop's internal drive(installed it just like normal application). After that, I rebooted back to High Sierra on laptop's internal drive, aaaand it worked(I think :)), even if installer show "install failed" before.

 

glad to hear it works out for u :)

need to clarify with u - how many high sierra installation do you have? (reading the above gives the picture that you have 2 High Sierra installations, one external (usb) and one internal)

 

so u booted from USB (High Sierra system drive), and then installed the 10.13.1 update to the internal drive (that also has High Sierra 10.13), and when prompted to reboot, u now booted from the internal drive instead, and your internal drive shown it has been updated to 10.13.1.

 

is the above correct in describing your situation?

 

thkq :)

Share this post


Link to post
Share on other sites

I just went with Clover and it installed it fine from AppStore. As long as there is a Recovery Partition it works.

Pretty cool!How to create a Recovery partition on MBR??

Share this post


Link to post
Share on other sites

glad to hear it works out for u :)

need to clarify with u - how many high sierra installation do you have? (reading the above gives the picture that you have 2 High Sierra installations, one external (usb) and one internal)

 

so u booted from USB (High Sierra system drive), and then installed the 10.13.1 update to the internal drive (that also has High Sierra 10.13), and when prompted to reboot, u now booted from the internal drive instead, and your internal drive shown it has been updated to 10.13.1.

 

is the above correct in describing your situation?

 

thkq :)

 

That's right my friend. I have two High Sierra installation, one on my laptop and one on my external drive. I've tried to install Supplemental update and 10.13.1 update using this method, and both worked (I also updated High Sierra on my PC using this external drive, despite my PC using GPT :D)

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
Sign in to follow this  
Followers 0

  • 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 to options: boot macOS Mojave or Windows 10
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Have a blank 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 - Have 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.
       

       
       
      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  install is GPT UEFI then you should be able to boot into Windows directly from Clover boot screen.
       
      If Windows 10 install is MBR / Legacy BIOS  then convert to GPT / UEFI  following instructions below ( See 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:
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
    • By h2onions
      Hey all,
       
      First Hackintosh that I think I have completed! I've been working on it on and off for a month, but just grinded it this past weekend. I just have a small QOL issue. I have posted in the r/Hackintosh reddit, but have not gotten a reply to this specific issue, but did for other issues I was having. I also posted at tonymacx86 and was getting replies for other issues I was having, but got banned because I said, "used VM, but didn't work" in my OP I think ...
       
      I followed a PC vanilla guide from r/Hackintosh that I found as I did not have an Apple system. One monitor connected to a GTX 1080, CPU: i7-8700, Coffee Lake. Motherboard is Alienware specific 0VDT73, with chipset Z370.
       
      The issue is every time High Sierra boots up and gets to the login screen, my keyboard and mouse do not work. I only have to reseat both and then they work the whole time until I restart. They are both plugged into USB2.0 ports. I do have Lilu, WhateverGreen, USBInjectAll, and VoodooPS2 installed in my /Library/Extensions folder using #####. Mouse and Keyboard work fine each time I boot to Clover (USB). Any ideas?
       
      Thank you!
      Working: NVIDIA using (One) DisplayPort, USB3.0 (rear), USB-C (rear), USB2.0 (rear), Audio, Ethernet
       
      EDIT: Did some more testing, and it looks like my Keyboard works fine after each reboot, the only issue is that my mouse has to continuously be reseated. Any ideas? Could it just be the mouse?It's an old Inland USB mouse: 337451
    • By STLVNUB
      No sense re-inventing the wheel.
       
    • By Gymnae
      Introduction
      The H370 chipset powers 8th generation Intel Core-i CPUs. Even though the name H370 rings comparable to Z370, the H370 is based on newer silicon. This it also requires some new approaches compared to the Z370. An example would be on-die USB 3.1 and WiFi support.
       
      Since this guide is not a "hold-your-hand-every-step" guide, I assume you know:
      Clover installation and configuration How to create an install medium for MacOS Access and configure the BIOS Have heard of ACPI patching (I'm a newb at this myself)  
      What works
      Sleep (via DSDT edits and emulated NVRAM) On-board Audio (via AppleALC and native AppleHDA) Native power management (without any kext or patch) All USB ports (and only those present are active) iGPU for both acceleration and display dGPU (I'm running an Nvidia GTX 1080)  
      Untested
      NIC --> I'm using WiFi only  
      What doesn't work
      Native NVRAM via AptioMemoryFix.efi DMVT Pre-alloc higher than 64MB (but not necessary)  
      Community additions
      User @Panzerschiffe added a helpful post, altering this guide for user with AMD cards and not needing on-board sound.
      He also runs Mojave, which I don't run yet.
       
       
      Changes to the guide:
      22.5.18: Added SSDT hot-patching to enable sleep, replacing DSDT static patching as an alternative.
      23.5.18: Add iMac18,1 as alternative SMBIOS config for those relying on the iGPU for output
      25.6.18: Added update info
      28.8.18: Small changes for clarity, changed info for afps loading & updated USB patch for 13.6
      04.10.18: Update to Mojave will come once Mojave is more mature
      02.12.18: Removed unnecessary patches, fakepciid and audio patch method & linked to AMD post & added whatevergreen.kext as replacement for previous GPU kexts
      02.03.19: Removed unnecessary fakeid and ig_platform_id injections, ACPI patches - this is all handled by whatevergreen & lilu. In testing is a Framebuffer patch, see this post.
      04.03.19: Added Germany keyboard layout and updated pre-patched DSDT.aml removed DSDT patching
       
       
      1. Installation
      This guide heavy inspired by the work of /u/corpnewt of /r/hackintosh and his (sorta) Vanilla guide
       
      1.1 Create the install media for MacOS
      Follow this, if you are using a Mac to start off with. If you are totally new to MacOS, then please check the basic guide Creation of an installer media in windows or linux
       
      1.2 Install Clover on the install media
      Using the Clover installer, ensure you are installing to the USB medium you are using for the installer.
      Chose the following options, leaving the others on default: 
       
      UEFI driver: AptioMemoryFix UEFI driver: ApfsDriverLoader UEFI booting only Install to ESP  
      You have to get your hands on an apfs.efi. A google search can help, or extracting it from the Installer package. Make sure you procure a version matching the MacOS version you are about to install. Place the apfs.efi in drivers64UEFI.
       
      1.2 Adjust the config.plist for the installer
      You can use the config.plist attached as a guideline, but take a look at it before and at least adjust the SMBIOS - otherwise it won't boot.
      Attention: The attached plist contains audio patches introduced by a post-install step. If you run into problems, you might remove those. It also contains a manual slide value, which should normally not be needed, but works fine for me. It is also tuned for usage with an Nvidia Pascal dGPU as main GPU.
       
      The config you create now should serve you nicely for install and running the system.
       
      Take care of adding the following basics:
      SMBIOS: iMac18,3 - You can generate a serial number via Clover Configurator. The creation of a proper SMBIOS is covered in many guides to good extend Note: If you aim at using the iGPU for output, a user reported that iMac18,1 works better - since iMac18,3 produces severe flicker. I'm now also testing 18,1 Look at the graphics section and adjust the injection for Intel to your situation  
      Fixes

      Patches

      Devices

      Graphics
      Important:
      Change 0x59120003 to 0x59120000 if you don't use a dGPU as your main display Driver and instead use the iGPU for output.
      Also note. SMBIOS iMac18,1 has been reported to work better in this configuration. But 18,3 works fine for me.

      Kernel and Kext patches
       
      1.3 kexts and friends
      Add the supplied SSDT-UAIC.aml to "patched" - it limits the injected USB Ports to the actual number and ports valid for this board.
       
      Required kexts on "Other":
      FakeSMC.kext Whatevergreen.kext Lilu.kext AppleALC.kext IntelMausiEthernet.kext in case you're running Ethernet USBInjectAll.kext with the HCI-300-series-injector.kext --> These two should be installed to /L/E after install  
      We are leaving sound out at the moment, this is something for post-install.
       
      1.4 Check BIOS and install
      You should be ready for install. But before you reboot, please take a look at your BIOS and set it up accordingly (copied from the aforementioned guide and adapted):
      Load Optimized Defaults Disable VT-d setting If your system has Secure Boot Mode, disable it Enable CSM - This is sometimes needed to dual screens to work Set OS Type to Windows 8/10 or OtherOS - I have not seen a difference Turn off internal Serial and Parallel port Turn off Network stack for boot Turn off wake-on-lan (for now) Set XHCI Handoff to enabled Don't enable decode over 4G Depending on your GPU, set priority for boot Set internal GPU (iGPU) to enable - not auto or disabled Set DMVT pre-alloc min to 64MB and max to 128MB. For this selection to appear you might need to reboot after setting iGPU to enable Set USB legacy to enabled Activate XMP profile 1 f your Ram has it (mine doesn't and I added the timings manually) Set ERP to enable, disable platform power management (I need to do more research if this could be enabled)  
      I've attached my current BIOS config "hack2". You can place that on a fat32 drive (the EFI partition of your install USB drive might be an idea) and see if it loads. It's made for and with the F2 BIOS.
       
      The install itself should be like other MacOS Hackintosh installs with it several reboots and ensuring to select the correct boot device in Clover.
       
      2. Post-install
       
      2.1 Install clover on target
      This is a no-brainer, but install a fresh copy of Clover on your target medium.
       
      During install select again AptioMemoryFix but also additionally
      EmuVariableUefi-64.efi Install RC scripts on target volume because otherwise NVRAM doesn't seem to work
       
      After the install, copy
      config.plist contents of "Other" content of "patched" to your new clover install.
       
      2.2 Edit ACPI for slumber
      Choose one option, not both. The hot-patch is experimental, but for the moment it is stable.
       
      2.2.1 Edit DSDT
      No more need for manual DSDT patching. If you still do it, you might run into unstable sleep. SSDT hot-patching + sane clover.config edits are enough
       
      This is necessary only once on initial install and every time, you edit or upgrade the BIOS. The DSDT.aml attached to this post might work for your system or give you a file to compare to. Don't expect it to work for you, though.
      EDIT: Since moving from F2 BIOS to F12 I did not repatch and sleep is still somewhat reliable. But to be 100% sure, you can still follow these steps.
      I won't go into the details of DSDT extraction and patching. There are better guides (the linked guide is a rip-off of rehabman's guide from a different forum). Please follow such a guide to extract your ACPI data.
       
      Locate and disassemble the DSDT with the newest iasl binary you can put your hands on, then open it with MacIASL in its newest version you can find (Hint: Here is a good source) You can check if the version is new enough if MacIASL doesn't throw error upon compiling a freshly extracted DSDT.aml or DSDT.dst
       
      Add rehabmans repo (as per linked guide) and apply the following patches:
      Rename _DSM to _XDSM Fix _WAK Arg0 v2 USB3 _PRW 0x6D Skylake (instant wake) Find the CNVW device and remove the _PWR function there.
       
      Compile the DSDT and place it in "patched".
       
      2.2.2 Use SSDT hot-patching
      Instead of having to re-extract and re-patch the DSDT on every BIOS change or update, Hardware change one can also use ACPI hot-patching.
      It's a combination of config.plist patches and an SSDT, which is hot-patched into the ACPI (if I understand the process correctly)
       
      You need to add this SSDT-GPRW.aml to your Clover folder in the designated position at Clover/ACPI/patched You need to add this patch to your config.plist. It goes into the DSDT patch section  
      Note: This works for me, but the patch removes the _PRW method from all devices in the DSDT. This could have side-effects. So far, I have seen none. At the moment I'm also not applying any other patch, compared with the additional edits I made to the DSDT method before.
       
      2.3 Install kexts to system
      As mentioned in the install section, it's better to follow rehabman's instruction and install USBinjectAll.kext to /L/E:
      sudo cp -R Release/USBInjectAll.kext /Library/Extensions sudo touch /System/Library/Extensions && sudo kextcache -u / 2.4 Enable onboard Audio - Install AppleALC kext
      Make sure your EFI partition is mounted and that you have a vanilla AppleHDA kext available. See below for a guide how to get a vanilla AppleHDA if needed
      Note: Our Audio codec is ALC887 and it's running with layout ID 1.
      Download the newest AppleALC kext from here and install it together with lilu.kext from here into your usual /clover/kexts/others location. Done. No scripts or config.plist patches necessary.
      Add layout ID 1 to config.plist, if it's not there yet:
      <key>Audio</key> <dict> <key>Inject</key> <integer>1</integer> <key>ResetHDA</key> <true/> </dict> If you previously  installed any  audio patches, please follow this guide to "vanilla-ize" your install.
       
      2.5 Optional steps for Graphics
      If you have a dGPU, now it's the time to install its drivers and adjust the config.plist for it. The detaisl are specific to your GPU and thus of scope of this guide. Yet, my supplied config.plist is ready to be used with Nvidia Pascal cards and using the Nvidia web driver.
      Whatevergreen.kext helps with Intel iGPU and NVIDIA dGPU fixes.
       
      At the moment I'm also testing out a special bootflag: 'shikigva=12' to enable faster rendering in Final Cut Pro X. Without whatevergreen.kext and a shikigva bootflag, rendering in final cut seem very slow.
       
      2.5.1 Framebuffers
      If you're facing problems with output from your internal GPU, you can try the framebuffer patches listed by @BackwardMac:
       
      2.6 Install a proper keyboard layout
      You might not be using a fancy Apple branded keyboard. If you use a PC keyboard, you might be annoyed by the differing layout and usage of keys. As a German, you might find yourself quitting applications, since alt gr + Q won't add an @, but quit your current application. To fix this, you can simply install a different keyboard layout. Copy it to /Library/Keyboard Layouts/ and chose the layout in System Preferences, Keyboard in the section "Other". Deleting the previously selecting layout makes sure that only this one is used. Nice little trick.
       
      A keyboard layout for German keyboards is attached and works wonders
       
      3. Updating
      Updating inside 10.3.x/ 10.4.x point updates doesn't require much attention:
      Download the update from the AppStore as any Mac would do Allow the system to reboot Before booting MacOS with Clover, make sure to disable extra drivers for dGPUs which require non-native support. If using an Nvidia dGPU: Remove "nvda_drv=1"  from your boot arguments and disable Nvidia injection If using a non natively supported AMD card, do the same for AMD (I'm not using AMD, thus I cannot be specific) Boot into the newly created Install MacOS partition Repeat this process until the Install partition is gone Boot MacOS again, still following 3., and potentially install updated drivers Your Audio might require re-patching  
      4. ToDo
      Move away from static DSDT patching to SSDT hotpatching --> requires my work Native NVRAM --> requires developer work Audio without AppleHDA patching --> requires developer work  
      5. Thanks to
      @MaLd0nfor helping finding the right way with the DSDT
      @RehabMan, for being a legend and helping me out patching
      @toleda, for audio patches for the 300 series
      /u/corpnewt, for his superb vanilla guide
      @wmchris for his super XPS 9550 guide and introducing me to hot-patching
      @Panzerschiffe for his addition to this guide
      all the developers of clover and it's awesomeness
       
      SSDT-UIAC.aml
       
       
       
      win-germany.keylayout
       
    • By Utku
      Hi guys, I have a big problem for VT -x. I tried any things for example: dark=0 or already bios option is virtualization is enable. I don't understand this problem.
       
      Thanks guys!! And yes I have intel Q8400 quad core cpu, motherboard is Asus asus p5g41c-m lx.
       


×