Jump to content
ErmaC

Chameleon 2.4svn Official PKG Installer

4,313 posts in this topic

Recommended Posts

Advertisement

I have still Enoch 2905 wich boots 10.13.2 without any issues but I had to use a Clover pen to see the mac os install partition. I must check your new file in my next installation.

Share this post


Link to post
Share on other sites

Any news?

Still didn't work here with GPT.

As my test, it will load /macOS Install Data/Locked Files/Boot Files/prelinkedkernel, but did not mount BaseSystem.dmg.

 

We need to boot with /macOS Install Data/Locked Files/Boot Files/prelinkedkernel

and mount as rootdmg-ramdisk auth-root-dmg=file:///macOS%20Install%20Data/Locked%20Files/BaseSystem.dmg

 

refer to /macOS Install Data/Locked Files/Boot Files/com.apple.Boot.plist

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><plistversion="1.0">
<dict>
    <key>Kernel Cache</key>
    <string>/macOS Install Data/Locked Files/Boot Files/prelinkedkernel</string>
    <key>Kernel Flags</key>
    <string>-rootdmg-ramdisk auth-root-dmg=file:///macOS%20Install%20Data/Locked%20Files/BaseSystem.dmg</string>
    <key>Root UUID</key>
    <string>762395DE-A171-395B-8A4E-703454F769E1</string>
</dict>
</plist>

post-61100-0-29765600-1513518813_thumb.gif

Share this post


Link to post
Share on other sites

ErmaC, Regards. I am using Enoch-rev.2905_v2 along with FileNVRAM.dylib_rc6 and the NVRAM is not working. It does NOT generate the NVRAM.plist. At the moment I use El Capitan.

Share this post


Link to post
Share on other sites

ErmaC, Regards. I am using Enoch-rev.2905_v2 along with FileNVRAM.dylib_rc6 and the NVRAM is not working. It does NOT generate the NVRAM.plist. At the moment I use El Capitan.

Hi stinga11,

where you expect to find the generated nvram.plist file?

 

ErmaC

Share this post


Link to post
Share on other sites

Hi stinga11,

where you expect to find the generated nvram.plist file?

 

ErmaC

In the root or in the extra folder (I know it's hidden)

Share this post


Link to post
Share on other sites

In the root or in the extra folder (I know it's hidden)

Pls try the latest one 2908 --> http://www.insanelymac.com/forum/files/file/71-enoch/

 

Include the RC8 of FileNVRAM

(Module changes and build is courtesy of Micky1979)

 

@crazybirdy or all

can you tell me exactly where the new (temp?) files (I mean in 10.13) are stored

when and update as been done? Can you check it maybe looking from other OSX where those file/folder are stored?

 

I'm a bit lost with this...

 

ErmaC

Share this post


Link to post
Share on other sites

@crazybirdy or all

can you tell me exactly where the new (temp?) files (I mean in 10.13) are stored

when and update as been done? Can you check it maybe looking from other OSX where those file/folder are stored?

 

I'm a bit lost with this...

 

ErmaC

 

If the volume is /Volumes/Mac10131, when update to 10.13.2 from app store, it will auto-make a directory as /Volumes/Mac10131/macOS Install Data/ before restart to install the update.

 

Enoch need to boot with the updating boot system as below, to finish the updating.

 

/Volumes/Mac10131/macOS Install Data/Locked Files/Boot Files/SystemVersion.plist

/Volumes/Mac10131/macOS Install Data/Locked Files/Boot Files/prelinkedkernel

/Volumes/Mac10131/macOS Install Data/Locked Files/Boot Files/com.apple.Boot.plist

/Volumes/Mac10131/macOS Install Data/Locked Files/BaseSystem.dmg

 

I guess you mean this.

Share this post


Link to post
Share on other sites

Pls try the latest one 2908 --> http://www.insanelymac.com/forum/files/file/71-enoch/

 

Include the RC8 of FileNVRAM

(Module changes and build is courtesy of Micky1979)

 

@crazybirdy or all

can you tell me exactly where the new (temp?) files (I mean in 10.13) are stored

when and update as been done? Can you check it maybe looking from other OSX where those file/folder are stored?

 

I'm a bit lost with this...

 

ErmaC

Thanks for this new Enoch 2908 which can boot to the first stage of update process of High Sierra, but it always hanged after showing up of bright white Apple icon and installation icon and unable to complte the first stage of update.

It's a break-through and near success now.

How to fix it ?

Share this post


Link to post
Share on other sites

I need more investigation then...

sorry...

 

EDIT: w8... I wrote a stupid typo... (I think... :blush: )

now is...

"macOS%20Install%20Data"

was...

"macOS Install Data"

try now -> attachicon.gifboot_v2905_v2.zip

 

ErmaC

 

boot_v2905_v2 helped me in updating 10.12.6 to 10.13.2 on QEMU/KVM. Pre 2905_v2 every boot ended up with  "ParseTagdate Unimplemented". However, I have noticed two problems:

- Running a 10.12.2 can't download 10.13.2 from Apple store. I have to update to 10.12.6 first before download starts.

- Shutting down 10.13.2 hangs the virtual machine. This is worse of these two since it leaves VMs running when they should be deleted. 

Share this post


Link to post
Share on other sites
On 28/03/2018 at 2:38 PM, Hervé said:

I've noticed that my Haswell/HD 4600 Dell Latitude E6440 still can't fully boot High Sierra with r2905 or r2908. No problem booting all earlier OS X/macOS releases up to Sierra.

I am not getting any verbose at all  in SL up to Mountain Lion if using v2905  or v2908. im am just getting a blank screen untill the login appears. As if the verbose (-v) function does not work. All is OK in Mavericks to HS.

Share this post


Link to post
Share on other sites
On April 15, 2018 at 3:00 AM, ellaosx said:

I am not getting any verbose at all  in SL up to Mountain Lion if using v2905  or v2908. im am just getting a blank screen untill the login appears. As if the verbose (-v) function does not work. All is OK in Mavericks to HS.

Same here; I only see the messages that come out up to the point of resolution switch, then screen goes dark for the rest of the time until the desktop appears.  Have the backend verbose messages been disabled? How do I get them back?

Booting an El Cap partition; testing latest Enoch in prep for a HS upgrade.  Also, when booting to a different El Cap (test) partition, machine shuts down 5-10 seconds after screen goes dark--no message preceding it to indicate why.

Share this post


Link to post
Share on other sites

I'm struggling to get El Capitan installed/working consistently.

 

The most frustrating aspect of this is that VERBOSE booting in Enoch seems to have been removed or is broken.  Any word on that?  Why?  This doesn't make any sense to me.

 

At first I thought it was El Capitan that had removed support for verbose booting..  Then I started seeing people posting screenshots of El Capitan booting with verbose messages.  I was confused, I still thought it must be some other setting over-riding it or somehow preventing it or something.  Now I've discovered that others are experiencing the same things with Enoch so at least my mystery is solved.  But what I don't understand is how/why this happened, and even more so:   why it hasn't been fixed?!

 

It looks like someone has figured out when the problem started so I'll be able to install an earlier version and get back to diagnosing my problems with El Capitan without having having to reboot into another OS just to be able to look at the logs since I can't see those messages as it's booting.

 

El Capitan has quickly proved to be the most problematic version of MacOS to get working since my first hackintosh installing Leopard!

Share this post


Link to post
Share on other sites

Trying to find a link to download a version which I hope will not prevent verbose booting messages was very convoluted and felt like a wild goose chase!

But I finally found one....   here! &nbsp;(2902)  I guess we'll see in a few moments whether it does what I need or if I'll have to keep searching.

 

It would be nice if previous versions were a little easier to find!  (Maybe they are but I'm just not clever enough to find them?)

 

Especially when there is such a MAJOR bug or deficiency—or whatever you want to call it!  I mean, to me at least: being able to see the boot messages is CRUCIAL whenever there's a problem, or the potential for there to be one (after any update or change to the configuration/settings, etc.)   I'm still rather shocked and almost in disbelief that such an issue exists and hasn't been dealt with/fixed for SIX months!   I suppose it must mean that there aren't that many people using it...

Clover is not an option I am seriously considering because it takes 5 minutes or longer to even reach the boot screen on my motherboard!  I haven't been able to fix that; I assume it must be my motherboard.  Plus, El Capitan has the slowest boot times I've ever experienced in OS X since I started with Leopard.  8 minutes to reboot the computer (from when I select the reboot command until I'm back to a functional desktop) is simply absurd and unacceptable!

Edited by AuralArchitect
typo

Share this post


Link to post
Share on other sites
10 hours ago, AuralArchitect said:

Trying to find a link to download a version which I hope will not prevent verbose booting messages was very convoluted and felt like a wild goose chase!

But I finally found one....   here! &nbsp;(2902)  I guess we'll see in a few moments whether it does what I need or if I'll have to keep searching.

 

It would be nice if previous versions were a little easier to find!  (Maybe they are but I'm just not clever enough to find them?)

 

Especially when there is such a MAJOR bug or deficiency—or whatever you want to call it!  I mean, to me at least: being able to see the boot messages is CRUCIAL whenever there's a problem, or the potential for there to be one (after any update or change to the configuration/settings, etc.)   I'm still rather shocked and almost in disbelief that such an issue exists and hasn't been dealt with/fixed for SIX months!   I suppose it must mean that there aren't that many people using it...

Clover is not an option I am seriously considering because it takes 5 minutes or longer to even reach the boot screen on my motherboard!  I haven't been able to fix that; I assume it must be my motherboard.  Plus, El Capitan has the slowest boot times I've ever experienced in OS X since I started with Leopard.  8 minutes to reboot the computer (from when I select the reboot command until I'm back to a functional desktop) is simply absurd and unacceptable!

 

Hi,

 

I run into the exact same issue over the week-end, when I wanted to freshen up my USB install sticks for "Old" OS X version.

However, I would disagree on the fact that this is a major bug, since El Capitan and beyond are already 2.5 generations behind,..

 

Anyways, I can confirm there is a regression that has been introduced in 2902.

I have re-tried with 2889 (which I still had on my hard drive), and this solved the black screen issue.

 

2902 contains several required features for get proper High Sierra support.

We should most probably investigate what went wrong analyzing the diff.

Edited by MinusZwei

Share this post


Link to post
Share on other sites
9 hours ago, MinusZwei said:

 

Hi,

 

I run into the exact same issue over the week-end, when I wanted to freshen up my USB install sticks for "Old" OS X version.

However, I would disagree on the fact that this is a major bug, since El Capitan and beyond are already 2.5 generations behind,..

 

Anyways, I can confirm there is a regression that has been introduced in 2902.

I have re-tried with 2889 (which I still had on my hard drive), and this solved the black screen issue.

 

2902 contains several required features for get proper High Sierra support.

We should most probably investigate what went wrong analyzing the diff.

 

Thank you so much for your response and a definitive answer on a version that doesn't black the screens!  I had discovered that 2902 was not going to do what I hoped...

Fair enough...  (about it being a major bug)   It just feels like a major bug because of the inconvenience it has incurred!  

 

That is very good to know; unfortunately I have not been able to find that version available for download  :(   I was attempting to compile various revisions from sources to test but I've been getting an error.  At least now I do not need to go through the "testing" procedure!  Someone in another thread was kind enough to post a link to an older version like 27xx, so if I am unable to resolve the compile errors I can use that!  I very much appreciate all you have shared; it is very insightful!

 

 

13 hours ago, Slice said:

 

Thank you!!!  I will definitely go through that list again!  I did some research previously and I believe that is one of the threads I found while I was attempting to resolve the issues; but I could be mistaken of course, and I could have missed something—or something may have been added or changed.  More likely that I missed something or didn't apply it correctly!   I very much appreciate your response and I will absolutely investigate and re-attempt to get clover working at a reasonable speed because it certainly has some very useful and helpful features!

Share this post


Link to post
Share on other sites

Perhaps an additional download link of Enoch should be included in this thread for version 2889 specifying it for use on 10.11 and lower (in order to boot with verbose messages)?   That seems reasonable, and I think anyone trying to install the older versions of OS X (for whatever reason) would find that extremely helpful.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By vit9696
      OpenCorePkg / Documentation / Configuration Template / Bugtracker   Discussion and installation should be done in a separate thread! This thread is for development only!
      Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support  Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images  
      Known defects (for 02.05.2019): Custom memory configuration is unsupported, and provided as is. Full secure boot compatibility is in progress. Hibernation support is missing.  
      For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
    • By dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
    • By ErmaC
      Slice is glad to present a new EFI bootloader.
      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      http://cloverefiboot.sourceforge.net/

      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      CloverGrower Downloads Installation How to do UEFI boot How to use - common words Calculator for Automatic DSDT fix Instructions for GraphicsInjector ATIConnector patching Any kexts patching with some Samples CustomEDID Hiding unnecessary menu entries Instruction for DSDT corrections to do DeviceInjection works Development Themes About kexts injection Instructions for P- and C-states generator Patching DSDT to get Sleep working CPU settings and geekbench ACPI tables loading DSDTmini Custom SMBios F.A.Q. iCloudFix Using mouse. How to make orange icons to be metallic How to make software RAID (by Magnifico) How to modify InstallESD.dmg (by shiecldk) Config.plist settings Using extra kexts and skipping kernelcache Choosing EFI drivers Configuration files Automatic config.plist creating Custom DSDT patches How to do sleep/wake working with UEFI BOOT DeviceID substitution (FakeID) Using Custom OS Icons Hibernation Floating regions Error allocating pages while starting OS -----------------
    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





×