Jump to content
SuperThecomputergeek

Chameleon boot loader hangs at apple logo after install

3 posts in this topic

Recommended Posts

i installed chameleon boot loader to amd 10.6.8 and it said install successful then i rebooted and selected my partition and pressed enter.

 

it gets stuck at the apple logo and no HDD activity.

 

i am using virtualbox.

 

plz help 

post-1225233-0-20347800-1381505940_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

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 SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By Pericles
      I've been trying to boot MacOS Mojave (10.14.4) after installation on a system I've built.
       
      I was able to successfully install Mojave through my USB, it seemed like the installer recognised my gpu and was working with it in the installation screen as it looked like it was outputting video at 4k resolution. When the computer restarted I then booted into the "Preboot" option on clover twice (the first time I tried the progress bar got to a certain point and then the system restarted) and on the second attempt the progress bar filled up completelly and the mac installer counted down to a restart (which I took as meaning that it had successfully finished the installer). After restarting however I tried to boot into MacOS from the SSD I installed it on, the apple logo showed up with a progress bar that filled up completelly before the screen turned black, then grey with a cursor over the grey screen. Also, it's probably worth noting that the GPU's fans continue to spin from turning the system on, up to the point where the screen turns grey after which they stop spinning.
       
      My system specs are as follows:
      CPU: i5 3470
      GPU: RX 570
      RAM: 16GB DDR3 1600MHz 
      MB: Asrock B75m r2
      SSD: Samsung 850 Evo 250gb
      WiFi/BT: Fenvi FV-T919 PCIE Card
       
      I am thinking that it's probably a gpu related issue as everything about the installation process has gone pretty smoothly up to the point where it's displaying a grey screen at bootup (and not going further). I have attached a photo of the output from rebooting with the verbose bootflag (it's missing one line at the bottom "busy timeout[1], (240s): 'AppleACPICPU'"), after the verbose output stays on the screen for a few minutes the screen then turns grey with the cursor and hangs there.

    • By thiagomenini
      Hello everybody,
      I'm from Brazil, if someone wants to write in portuguese, i will understand too. But english is fine.
       
      Days ago I installed the High Sierra, using the image (HighSierraAMD V2 UEFI.dmg). I have an FX8320e, the Asus M5A78L-M / USB3 mobo, GTX 750 and 12GB of RAM.
       
      Well, I build Hackintosh to run audio programs. Everything is working except the USB audio card on the card. But I read that some gyus updates to 10.13.4 or higher and it work.
      But I have some problem with startup and shutdown. I had installed the Clover in different ways, but it did not appear at startup. If I do not use the pen drive to boot, I do not have access to the system.
       
      I've tried different solutions. I formatted the EFI partition using the Terminal and reinstalled the Clover, but it also did not work.
       
      The other problem is the shutdown. The system goes off, but the fans and the mobo remains on. I need to manually press the on/off button to turn off the computer. I had used the Clover Configurations App to set the flag (shutdonw fix) but it not work too. I think this might be related to the boot problem.
       
      Thanks for any help!
    • By Oschly
      Hi! I have a problem with 10.14.4 on booting stage (photo).
      My specs:
       
      MOBO: Z390 MAG Tomahawk
      CPU: i7-8700k
      GPU: RX 580 Nitro+
      Wifi: BCM4331CD
      RAM: Corsair Vengeance LPX 3000MHz 16CL
       
      I've updated every kext and driver (clover version too) and only difference is that I don't have lines informing about not loading kexts (common issue here as I see).

    • By outdoormagic
      Short Version:
      I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
      More Detail:
      I've done a few hacks so far and this never happened. (Gigabyte z370 / 8700k / Vega, Asus z390 / i5-9600k / 1080). Now, I'm setting up a ThinkPad X1 Gen 6. (Yes, I do expect problems on laptops, but that's not the question).
       
      Mojave 10.14.4 now boots from the internal SSD. So far, so good. Here's the problem.
       
      I installed Mojave on a USB drive (for backup / rescue) and copied the entire EFI partition of my boot drive to the EFI partition on the USB drive. So... I should be able to boot from the USB drive, right? Wrong. Ran Clover installer on the USB itself. Same outcome.
       
      With F12, I can boot from the USB into Clover and select the OS on the USB. The boot sequence hangs on End Random Seed, but before the usual '++++++++' line.
      So, boot into Clover on internal boot drive, then select OS on USB. Same thing.
       
      Read the forums, I saw the posts about AptioMemoryFix, so I tried the various other drivers on the USB. No go.
       
      I haven't found the solution yet to the USB boot issue, but what puzzles me is that if I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
       
×