Jump to content
xpamamadeus

Ozmosis

6,214 posts in this topic

Recommended Posts

Wa

 

You need to understand that theme is strict relation with Ozmosis Interface implementation, so all you can do is to use existing features that are implemented already, or wait for future implementations/releases.

 

Thats good to know and appreciate the information you have provided. Was just hoping to discover an undocumented feature or two to spice up the interface. Though one cool thing I have discovered is that the Theme.Plist references FFS GUIDs under the 'Command' key for certain functions that do not exist for everyone. So was wondering if perhaps I could replace one of the GUIDS with the 'QFlash'  bios module or some other efi program?

 

As far as getting a custom background image patience will be a virtue here I guess..

 

Thank you.

Share this post


Link to post
Share on other sites
Advertisement

...So was wondering if perhaps I could replace one of the GUIDS with the 'QFlash'  bios module or some other efi program?

I think a better answer you will get after you try and share the result with everyone.

Share this post


Link to post
Share on other sites

How can you link the OEM Splashscreen to the GUI and use it as background? I've never seen that and the Gigabyte Splashscreen doesn't get displayed either. So I don't get what you're saying or I'm just missunderstanding you...

The GUID I was talking about is for the pointer image which can be found in the Theme file. That's also why you can't find the ID in the UEFI.

 

My answer for you is a question! Why from the OzmosisGUI and when you double click on BIOS Chip icon it takes you to UEFI Settings after a reboot, or double click on HermitShell for example it takes you to it? How can it be possible, now you'll not misunderstand me!  :wink_anim:  ^_^

Share this post


Link to post
Share on other sites

That is possible because of the OzmosisUI Implemetation in Ozmosis itself. Both services have fixed file GUIDs which are set in the theme.plist under "Command". Ozmosis reads this value and starts the EFI Application with the GUID set in the propertylist.

An OEM splashscreen isn't an EFI Application, though...

Share this post


Link to post
Share on other sites

That is possible because of the OzmosisUI Implemetation in Ozmosis itself. Both services have fixed file GUIDs which are set in the theme.plist under "Command". Ozmosis reads this value and starts the EFI Application with the GUID set in the propertylist.

An OEM splashscreen isn't an EFI Application, though...

Not only that but in Ozmosis.ffs I have found the Hermitshell Guid referenced in code so its hardwired to load the shell. Unfortunately in my system i either have to do a cmos reset or delete HermitShell from the boot menu using bcfg so it is reinstated or else the reference is lost after a reboot. I dont know if references in theme.plist will make a difference in my case but going to try probably by Sunday. Stay tuned.

Share this post


Link to post
Share on other sites

Some things are referenced in ozmosis.efi. This way the command "Firmware" also works although its obviously not a File GUID... I don't think that these values in the Plist are only there to look good, they should serve a purpose unless it's not implemented (yet).

Do you use a shell where the File GUID matches the one in the Theme.plist?

Share this post


Link to post
Share on other sites

Some things are referenced in ozmosis.efi. This way the command "Firmware" also works although its obviously not a File GUID... I don't think that these values in the Plist are only there to look good, they should serve a purpose unless it's not implemented (yet).

Do you use a shell where the File GUID matches the one in the Theme.plist?

No I was forced to use bcfg boot add as I couldn't get the built in shell working. It would work only once then after reboot not work anymore. Ill try to alter theme.plist guids and see what can happen.

Share this post


Link to post
Share on other sites

No I was forced to use bcfg boot add as I couldn't get the built in shell working. It would work only once then after reboot not work anymore. Ill try to alter theme.plist guids and see what can happen.

what does not work after restart? Theme?

Share this post


Link to post
Share on other sites

@Crusher,

 

No not the theme. What doesn't work is the 'Builtin Shell' or Hermitshell from either the F12 boot menu or from the Oz GUI. Only works once. After reboot not work again when trying to load it from Firmware Volume. So I have to create a bcfg boot add to hermitshell off of my efi folder.

Share this post


Link to post
Share on other sites

@Crusher,

 

No not the theme. What doesn't work is the 'Builtin Shell' or Hermitshell from either the F12 boot menu or from the Oz GUI. Only works once. After reboot not work again when trying to load it from Firmware Volume. So I have to create a bcfg boot add to hermitshell off of my efi folder.

Try to add and hermitshell via bcfg like a boot.

Share this post


Link to post
Share on other sites

You could also put the file into EFI/Boot folder. Afterwards name it BOOTX64.efi if you don't mind. This way it will automatically get added...

Which shell do you use, could you attach it?

Share this post


Link to post
Share on other sites

 

HS DP6  install Success on QUO SysDef iMac 13,2 after changing Defaults.plist

		<key>BiosDate</key>
		<string>08/08/2017</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010F.B00.1708080805</string>

 

High Sierra DP7 from DP6 .. nothing to do, just works.

Share this post


Link to post
Share on other sites

High Sierra DP7 from DP6 .. nothing to do, just works.

		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

Share this post


Link to post
Share on other sites
		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

 

 

For 13,2.

post-971914-0-23015700-1503496967_thumb.png

Share this post


Link to post
Share on other sites
		<key>FirmwareFeatures</key>
		<integer>3909612855</integer>
		<key>FirmwareFeaturesMask</key>
		<integer>4280287039</integer>

:) HI  .I also use QUO SysDef iMac 13,2 

 

What's your FirmwareFeatures & FirmwareFeaturesMask?     I set  3909612855 & 4280287039 not work with High Sierra DP7 .....

 

<key>FirmwareFeatures</key>
<integer>0xE907F537</integer>
<key>FirmwareFeaturesMask</key>
<integer>0xFFFFFFFF</integer>

Share this post


Link to post
Share on other sites

Ok, a fresh question from an old time user. I have a Fusion Disk with Sierra on it booting from Ozmosis (a very old version that allowed for Fusion drives I believe it was 894M) it has served me very well thus far, however with High Sierra I can only get a KP, and it is so fast that It doesn't give me an option to view the error before it scrolls past with a full screen of debug followed by mach restart 3 times.

 

This is on a separate single SATA drive I use for Beta testing on my hack vs beta testing on my MacBook Pro (where I installed the OS on the disk like I did Sierra). All protections are disabled in firmware so it should see the FakeSMC.ffs like Sierra does, and load it.  Any help would be greatly appreciated.

 

HBP

:: Edited ::

After Screencapturing the monitor with my iPhone, the KP is on com.apple.driver.AppleACPIPlatform(6.1)

 

it does pick up FakeSMC but for some reason, the ACPI for Sierra doesn't work for High Sierra?  any thoughts?

Share this post


Link to post
Share on other sites

TY @Kynyo BackDash's post and my German Helped allot, now I just have to get my Nvidia card to be willing to work in something other than Vesa mode and I can begin testing it in earnest.

 

HBP

Share this post


Link to post
Share on other sites

I think I found a solution to the background image issue though it is a work around and have not implemented it. Think what would work is if you load another bootloader like Refind from the firmware volume setting up a background, and from there chain load Ozmosis or your choice of bootloader after from the fs0 or fs1 drive. I've done this virtually in OVMF and I think this is a better option than having Ozmosis load from the firmware. From there it would be theoretically possible to mod Clover to run from the firmware as well with a little work. 

Share this post


Link to post
Share on other sites

Why would you want to run Clover from Firmware? No offense but I think your solution is a little very complicated :|  :D

 

I really like the scripts that THe KiNG posted, they make it really fast setting up new Themes.

But there's one thing that really bothers me and that is that there's no way to setup an image for new OS X versions as Sierra atm. It appears that badges with an even number are supposed to be shown for OS X Installers. The ones with an odd numbers are there for the main OS X version. Following this scheme, Sierra should have the number 17 and the SierraInstaller the number 16. Setting it up like that, the PNG files are loaded but not displayed for Sierra. Instead the GUI shows the Generic.png. Since there's a typo in the Yosemite (Yosimite) badge, I figured that the name of the badge doesn't really matter which can be validated with tests.

The official HorizontalTheme in it's newest version consists of a badge for Sierra. But also here, the badge isn't displayed in the GUI.

This issues was the main reason for me to start this theme discussion which ended with THe KiNG releasing the scripts. But this must be something about Theme implementation in the main driver. Since Sierra is the first OS that behaves like that with badges and also the first OS to have the name "macOS" rather than "OS X", that rename could be a starting point. I don't have any access to source code or anything which is why I can't help myself and am asking this over here. I would love to be able to setup badges for upcoming macOS Versions since I would like to use Ozmosis as long as that is still possible.

Share this post


Link to post
Share on other sites

Why would you want to run Clover from Firmware? No offense but I think your solution is a little very complicated :|  :D

 

I really like the scripts that THe KiNG posted, they make it really fast setting up new Themes.

But there's one thing that really bothers me and that is that there's no way to setup an image for new OS X versions as Sierra atm. It appears that badges with an even number are supposed to be shown for OS X Installers. The ones with an odd numbers are there for the main OS X version. Following this scheme, Sierra should have the number 17 and the SierraInstaller the number 16. Setting it up like that, the PNG files are loaded but not displayed for Sierra. Instead the GUI shows the Generic.png. Since there's a typo in the Yosemite (Yosimite) badge, I figured that the name of the badge doesn't really matter which can be validated with tests.

The official HorizontalTheme in it's newest version consists of a badge for Sierra. But also here, the badge isn't displayed in the GUI.

This issues was the main reason for me to start this theme discussion which ended with THe KiNG releasing the scripts. But this must be something about Theme implementation in the main driver. Since Sierra is the first OS that behaves like that with badges and also the first OS to have the name "macOS" rather than "OS X", that rename could be a starting point. I don't have any access to source code or anything which is why I can't help myself and am asking this over here. I would love to be able to setup badges for upcoming macOS Versions since I would like to use Ozmosis as long as that is still possible.

 

I would do it for the same reason as why you would install Ozmosis in the firmware if not for the fact that every new release would require a new flashing because Clover updates are more frequent than Oz. Of course it makes more sense to leave it on your efi folder. Easier to manage. Its doable as difficult as it is to implement and getting close to have Refind bootloader running off of the firmware such that you would have a graphical boot menu. As far as getting Oz to recognize Sierra and Hi Sierra it would take understanding where on the boot drive and what sector address + phrase Oz is using to verify Yosemite or El Cap or Tiger and replace it with the appropriate keyword for Sierra and replace the old bagdes no one ever uses anymore.

 

Anyhow I've given up playing with the Themes for now. Got 'The Kings' theme files unpacked and modded the compile.bat file to use the Tools I posted earlier. Just compile from the root folder like 'compile.bat Horizontaltheme'. Gave up on getting the background to be utilized though even though the script includes it in there. Though think I understand why Hermitshell wont load from firmware memorymapped volume more than once. I read some bioses will resort the boot menu items and the memory mapped volume address gets displaced due to incorrect formatting.

 

Still got work to do..

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.

Announcements

  • Similar Content

    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
      Anyone who likes the program, please support its Community Score.
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
    • By PropoFlexWX4
      After hearing that OpenCore is so much better than Clover, and that it will probably be able to boot Big Sur before Clover does, I decided to take the jump.
       
      Running Catalina 10.15.5 18F101 with OC 0.5.9.
       
      So far I like the result. The OS feels faster, boots faster.
      And absolutely everything works (sleep, network, etc...)
       
      So, that's it? Is there anything else I have to do?
    • By MacPato
      ALL-IN-ONE OPENCORE EFI CREATION UTILITY
      OC Gen-X Opencore EFI Creator Utility  First-Ever Beta is now released to the Public for Testing. Bugs or Issues please submit bug reports via the GitHub page! https://github.com/Pavo-IM/OC-Gen-X  Also, tell us what you think and what future features you would like to see in the release.
      Opencore Generation X is a Utility to create a pre-structured EFI Folder to the Desktop Based on the selection of the user. This Application is currently in beta testing it was designed and developed to make it easy to get Opencore installed. The configuration file is based on the dortania guide.

      if you have any request, suggestions feel free to make a submission at the GitHub page   Disclaimer: This application is not endorsed or support by the opencore development team, all app support and bugs must be reported via the app repo page : https://github.com/Pavo-IM/OC-Gen-X         
    • By blackosx
      Do you want to quickly find your boot log, or ever wanted to know which version of bootloader is installed on your disk(s), had the need to dump your BIOS from OS X, just curious about your own system setup or been asked to provide your setup information to others when asking for assistance?
       
      DarwinDumper is a useful collection of readily available tools, and scripts wrapped in an application framework giving you a convenient method to quickly gather a system overview of your hack or Mac. And rest assured that enabling the privacy option will mask sensitive data like the IOPlatformSerialNumber, IOPlatformUUID, IOMACAddress(s), USB Serial Number(s), SystemSerialNumber, serial-number, fmm-mobileme-token-FMM, MLB and ROM efi vars and CustomUUID in the dumped files and report.

      Current Release Version: 3.1.1



      The system dumps are saved to a folder or your choice, but defaulting to the same directory as the main application. You can choose to setup a symlink to make it simple to run DarwinDumper from the Terminal.
       
      There is an option to create an html report showing a complete overview of the dumps. This report will mostly just contain the text dumps as you'll find in the main dump directory, but for some dumps there is extra processing to try to present the information in a better way. For example, the Disk Partitions and Unique ID's dump will show a visual map of the disk layout, and the DMI Tables (SMBIOS) dump will show the data split by table type.
       

       
      Note: The html report does not contain all files from a complete dump so if seeking assistance for a problem and you wish to send someone a DarwinDump then you will want to send the complete dump directory and not just the .html report file.
       
      The following can be read and dumped by DarwinDumper:
      - ACPI tables.
      - Audio codec and further info.
      - Boot loaders and configuration files.
      - CPU info.
      - Device-properties.
      - Disk partition structure / info.
      - Disk sectors (hex).
      - DMI (SMBIOS).
      - EDID.
      - I/O Kit Registry.
      - EFI Memory Map.
      - EFI vars (some).
      - Kernel information
      - Kexts - (list of currently loaded kexts).
      - Memory.
      - NVRAM (both Apple specific and UEFI firmware variables).
      - SMC Keys.
      - LSPCI (PCI vendor & device codes) dumps.
      - Power (Sleep/Hibernate) settings.
      - RTC.
      - System Profiler.
      - System BIOS.
      - System Log(s).
      - Video BIOS.
       
      License:
      DarwinDumper is licensed under GNU General Public License, version 3.0 (GPLv3).
       
      Tools included:
      AnalyseVBIOS
      Copyright: Not Known. License: Not known Source: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/ Alt Link: https://www.dropbox.com/s/dnp903x2z9pqf8k/AnalyseVBIOS.zip?dl=0   AppleIntelInfo Copyright: © 2012-2017 Pike R. Alpha. All rights reserved. License: Creative Commons Attribution-NonCommercial Source: https://github.com/Piker-Alpha/AppleIntelInfo   atomdis Copyright: Michael Larabel @ Phoronix.com License: GPL Version 2 Source: http://www.phoronix.com/scan.php?page=article&item=amd_atombios_dumper   bgrep Copyright 2009 Felix Domke <tmbinc@elitedvb.net>. All rights reserved.   Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:      1. Redistributions of source code must retain the above copyright notice, this list of       conditions and the following disclaimer.      2. Redistributions in binary form must reproduce the above copyright notice, this list       of conditions and the following disclaimer in the documentation and/or other materials       provided with the distribution.   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.   The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the copyright holder.   Source: https://github.com/tmbinc/bgrep   bdmesg Copyright 2010 by Islam M. Ahmed Zaid. All rights reserved. License: GPL Version 2 Source: http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/util/bdmesg.c Alt Link: https://sourceforge.net/p/cloverefiboot/code/1905/tree/CloverPackage/utils/bdmesg/bdmesg.c   cmosDumperForOsx Created by rafirafi, revised extensively by STLVNUB License: Information not available Source: https://www.dropbox.com/s/bg1q0yho6g7u3xn/cmosDumperForOsxV0.1.zip?dl=0   csrstat Created by Piker-Alpha Copyright: © 2015-2017) by Pike R. Alpha License: Information not available Source: https://github.com/Piker-Alpha/csrstat   dmidecode Original nongnu.org
      License: GPL Version 2
      Now updated and hosted by acidanthera Source: https://github.com/acidanthera/dmidecode   dumpACPI Created by blackosx. Idea taken from PHPdev32's MacIASL. Source: https://bitbucket.org/blackosx/dumpacpi   edid-decode Created by Adam Jackson, revised by Andy Vandijck License: Information not available Original Source: http://cgit.freedesktop.org/xorg/app/edid-decode Revised Source: https://www.dropbox.com/s/l0htffnqzs9e1vg/edid-decode.zip?dl=0   fdisk440 Apple Computer, Inc. License: APSL v2.0 Original Source: http://www.opensource.apple.com/source/diskdev_cmds/diskdev_cmds-491/fdisk.tproj/mbr.h Modified by Zef Source: http://forge.voodooprojects.org/p/chameleonApplications/source/tree/HEAD/trunk/fdisk.tproj Alternate Link: https://www.dropbox.com/s/odl9kp38j3flla5/fdisk440.zip?dl=0   FirmwareMemoryMap script Amit Singh (showbootermemorymap) Further development by bcc9 and dmazar License: Information not available   flashrom http://flashrom.org/Flashrom License: GPL Version 2 Source: https://www.dropbox.com/s/gfmqx2t7lvofs1v/flashrom.zip?dl=0   getcodecid Copyright © 2012 AnV Software. All rights reserved. License: Information not available Source: https://github.com/Gengik84/getcodecid   getdump Created by fassl?, modifications by Slice and AutumnRain? License: Information not available Source: https://sourceforge.net/projects/voodoohda/files/   gfxutil Copyright 2008 mcmatrix. All rights reserved. License: Information not available Historic detail can be found at forum.netkas.org Source: https://github.com/acidanthera/gfxutil   iasl Copyright © 2000 – 2014 Intel Corporation. License: Information not available Source for v20200110: https://www.acpica.org/node/176   ioregwv Apple Computer, Inc. License: APSL v2.0 Original Source: https://opensource.apple.com/source/IOKitTools/IOKitTools-86/ Modified by blackosx Source: https://bitbucket.org/blackosx/ioregwv   lzma Copyright © 2013 Igor Pavlov. License: GNU Lesser General Public License Source: http://www.7-zip.org/sdk.html This build by Slice at insanelymac.com: https://www.insanelymac.com/forum/topic/311786-updated-lzma-utility-v1514/   lzvn Copyright: © 2014 Apple Computer, Inc. All rights reserved. License: APSL Credit: Piker-Alpha, Andy Vandijck, MinusZwei. https://github.com/Piker-Alpha/LZVN   MacGap2 Created by Tim Debo. All rights reserved. License: MIT Source: https://github.com/MacGapProject/MacGap2   Macpmem driver (Macpmem.kext) Copyright © 2007-2011 Volatile Systems. Copyright 2013-2014 Google Inc. All Rights Reserved. License: GPL Version 2 Source Code: https://github.com/google/rekall/tree/master/tools/osx/MacPmem]https://github.com/google/rekall/tree/master/tools/osx/MacPmem   nvram Apple Computer, Inc. License: APSL v2.0 Modified by blackosx Source: https://bitbucket.org/blackosx/nvram   oclinfo Copyright © 2009 cmf License: GPL Version 2 Source: http://www.insanelymac.com/forum/topic/170796-opencl-info/   pciutils driver (DirectHW.kext) DirectHW is Copyright © 2008-2010 coresystems GmbH License: GPL Version 2 Source: https://github.com/CloverHackyColor/directhw Kext: Pre-built (Signed) Kext   pciutils lspci Copyright © 1997--2008 Martin Mares License: GPL Version 2 Source Code: https://git.kernel.org/pub/scm/utils/pciutils/pciutils.git
      RadeonDump Created by Dong Luo. Copyright 2008. All rights reserved. Modified by Andy Vandijck License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068 Alt Link: https://www.dropbox.com/s/5drpckxlmaot732/RadeonPCI.zip?dl=0   radeon_bios_decode Created by Dong Luo. Copyright 2008. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068   SMC_util_FansOnly Copyright © 2006 devnull  License: GPL Version 2 Source: https://www.dropbox.com/s/ra9h6gbjj6yhgol/SMC_util_FansOnly.zip?dl=0   smcutil Copyright © 2006 devnull  License: GPL Version 2 Source: https://www.dropbox.com/s/0dgvexijx4oewfr/smcutil.zip?dl=0   VoodooHDA.kext Created by fassl?, modifications by Slice and AutumnRain? License: https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h]https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h Source: https://sourceforge.net/p/voodoohda/code/HEAD/tree/]https://sourceforge.net/p/voodoohda/code/HEAD/tree/   x86info Written to succeed CPUID by Phil Karn (KA9Q). Contributed to by various people. OS X compatability by Slice License: GPL Version 2 Original Source: https://github.com/kernelslacker/x86info Revised Source: https://github.com/CloverHackyColor/x86info  
       
      Running DarwinDumper from the command line:
      From Terminal, you can initiate DarwinDumper by running the following script directly.
      /DarwinDumper.app/Contents/Resources/public/bash/script.sh To help with this, the UI has a Symlink option which you can click to create a symbolic link which points to the above script. DarwinDumper can then be subsequently run from the command-line by loading a new Terminal window and typing darwindumper followed by return.
      $ darwindumper usage: [-a zip,lzma,none] [-d acpi,appleintelinfo,audio,biosSystem,biosVideo,codecid,cpuinfo,devprop,diskLoaderConfigs,bootLoaderBootSectors,diskPartitionInfo,dmi,edid,bootlogF,bootlogK,firmmemmap,memory,ioreg,kernelinfo,kexts,lspci,rcscripts,nvram,opencl,power,rtc,sip,smc,sysprof] [-h] [-l] [-o html,private] [-p 1,2,3,4,5,6,7,8] [-v] Example:
      $ darwindumper -l Will re-run the last dump used options.

      Credits (in alphabetical order):
      acidanthera team, Adam Jackson, Amit Singh, Andy Vandijck, Apple Inc., arsradu, bcc9, blackosx, cmf, DieBuche, dmazar, Dong Luo, droplets, ErmaC, Felix Domke, Google Inc., Intel Corporation, InsanelyDeepak, JrCs, Kabyl, Kynnder, Martin Mareš, mcmatrix, Michael Larabel, Mickey1979, phcoder, Phil Karn, Piker-Alpha, rafirafi, гык-sse2, Slice ,sonotone, STLVNUB, THe KiNG, Trauma, Volatile Systems, xsmile, !Xabbu.
       
      DarwinDumper was originally inspired as an open project by Trauma, it has remained an open project and please keep it an open project, so if you make any changes or additions to it then please share your work here.
       
      Please report any feedback, requests or bugs.
       
      Known issues: v3.1.0
      1 - When SIP File Protection is enabled, dumping disk partition info of non-APFS containers and disks which are not APFS physical stores may fail when running from DarwinDumper via the graphical interface. However, it's been known to succeed when using DarwinDumper from the command line. Something to do with osascript.
      2 - lzma archive option has been known to fail on macOS 10.15 when running dumps requiring root privileges.
       
      macOS Version support:
      - v2.9.9.2 is for older macOS versions
      - v3.0.4 requires OS X 10.9 and newer to run in the Finder, though it should work from the command line okay on older OS versions.
      - v3.1.0 was updated for newer macOS versions and has been tested on 10.13 and 10.15.

      DarwinDumper Download
×