Jump to content
pashoni

Can't boot into Mountain Lion

13 posts in this topic

Recommended Posts

Hello everyone.

 

I've used the instructions in this topic to install my OSX:

 

http://www.insanelymac.com/forum/topic/288795-guidecreating-os-x-usb-installer-using-a-windows-pc-only/

 

Now, it is only possible for me to boot into Mountain Lion with USB which has Clover installed, then selecting external, and after that I boot "normally". 

I would like to boot without this USB using Champlist, but when I try that, I get efi_inject_get_devprop_string null trying stringdata and instant restart.

 

Any help would be appreciated.

 

Cheers.

Share this post


Link to post
Share on other sites
Advertisement

Clover is a little bit harder to get working on some systems especially if its your first hackintosh.  What Im gonna recommend is you making a Mountain Lion bootable usb using myhack which will put Chameleon on it.  Once you get the system bootable without the flash drive and you get familiar with the system then you can try installing Clover as your boot loader.

Share this post


Link to post
Share on other sites

First of all, thank you for your response.

I did this as you said, but now, even when I install without clover, I can't boot into my system without it.

When I power on my computer, it lists boot:0 done, and goes to my dual boot menu.

If I choose Windows it boots like it should, but if I choose OSX (which is installed now without clover, using chameleon) it shows chameleon screen (different than it should be with type of install I did, to be more specific it shows the same screen as the one when I installed using clover).

Is there any way for me to get back at the state at which everything was?

How can I get rid of boot0 message?

 

Cheers

Share this post


Link to post
Share on other sites

boot0:done is just a console message that tells you the very very first boot on the hard disk drive is completed (which is the bootloader, Chameleon).

I am using Chimera actually and it worked fine until now, just looking for the solutions on my hackintosh, but that's not the point.

Try using Chimera, go to tonymacx86's website and download #####, then on ##### select Bootloader and select the latest Chimera.

You can set your themes again afterwards.

 

Or, on the bootloader, you can try using flags like -f to disable cache, -v to boot in verbose, and GraphicsEnabler=Yes|No to disable graphics support, or -x to boot in safe mode

 

Try to use the verbose and see what error it gives.


Or, you can try to rebuilt your installation disk with myHack. When your system boots the myHack disk, simply go to Utilities > MyHack and then run the myFix targeting on your Macintosh hard drive

Edited by fantomas1
InsanelyMac does not support tonymacx86 tools!!!

Share this post


Link to post
Share on other sites

I just realized that no matter if I have OSX installed or not, when I add OSX option in EASYBCD boot, it loads Chameleon which causes this error for me.

Is it possible that chameleon is installed at my Windows partition and works like that even through I rewrote my windows default bcd?

Share this post


Link to post
Share on other sites

Did that, but still no luck.

I boot both Win and OSX from the same drive (It worked before I installed OSX with clover, which is the part that messed up my hackintosh I think )

Share this post


Link to post
Share on other sites

First thing that I want to correct is that Chameleon, Chimera, or other bootloaders were not installed on partition, which consists of Windows' and Mac's. But, it was installed on the hard drive and set as the first step to boot before any operating systems which allows you to choose which partition to boot (like Windows, Mac, or Linux).

Every hard drive have bootloaders, even if you don't see them. If you install Windows only, your computer will automatically boot into Windows like usual, the bootloader is the one with black screen (maybe with "underscore") right after the motherboard screen. Installing Chameleon or Chimera is just simply replaces the previous bootloader with their's.

 

So, my laptop is now dual-booting Windows 8.1 Pro and OS X Mountain Lion 10.8 (which have some problems, if you can help me, it will be very helpful. Go to here to help me) seamlessly using the Chimera bootloader. Things that I can conclude from my method of installation is:

1. To dual-boot, you must firstly have a very clean hard drive. Nothing in it. Not a single file or OS. Just empty hard drive.

2. You must set your BIOS to boot in AHCI mode.

3. You must have access to other Mac (if you're not doing iATKOS) to build a bootable drive.

4. You must firstly install Mac, and format your hard drive into partitions with GUID Partition Method and for Windows', format it as MS-DOS (FAT).

5. Let it install. Next step is installing bootloader. Boot into Mac using the bootable drive. Mac will not work with DOS.

6. Now, after installing bootloader, boot your Windows' installation disc/disk.

7. Format the previous MS-DOS (FAT) drive(s) into Windows NT File System (NTFS).

8. Let Windows install.

9. Reboot your PC.

10. Boom! Dual-boot!

 

If I install Mac right after Windows, these are the problems:

1. You can't format your partition back to Mac OS Extended (Journaled). It will stay as NTFS. Because Windows uses the Master Boot Record (MBR) method.

2. You will get annoying "Errors occurred while trying to start up your computer. Pausing 5 seconds...". (even though it doesn't do anything).

3. Some GPUs will return an error code, like stuck in [iOBluetoothHCI] -- something.

4. And more upcoming problems.

 

So, I suggest you to go and buy an external hard drive (if you have then don't need to) to backup anything you want and need, then start from a clean slate.

 

Good luck!

 

By the way, why would you boot Mac using EasyBCD, and Chameleon? I didn't even use EasyBCD. It just simply mess up your boot orders.

Share this post


Link to post
Share on other sites

Thank you for your reply and your effort. 

This will be my last , but possibly the only option.

I've used EasyBCD because it worked before.

I've installed chameleon with my OSX, but Chamelon isn't working as it should, because at boot it showes some older version, than this one I have installed.

I'll give it another try, and than format everything and start over.

Share this post


Link to post
Share on other sites

Good choice, but just don't try to use EasyBCD for the second time. Format your hard drive clearly, and then boot up your installation disk.

 

Note: If you're stuck on the Apple logo when booting up the installation disk, tell me. Check your error code using the verbose mode (-v) and tell me, because I've experienced it before and I've fix it. The error code for me is actually [iOBluetoothHCIController][start] -- completed.

Share this post


Link to post
Share on other sites

I haven't had problems with install so far. 

I've got everything working before, with the same method I used this time, but update to 10.8.4 destroyed my hackintosh.

I've done everything the same, but because of the fact that I haven't had available mac or virtual mac, I had to make my usb in Windows, which was a mistake :)

Share this post


Link to post
Share on other sites

pashoni,

 

There's one thing that I need to tell you. If you're installing OS X from a clean slate--say version 10.8.0--then you have 10.8.0. If you're trying to update to 10.8.4--for example--using the combo update or supplemental update, then boom! You will get a kernel panic that you can't even fix it using myFix or Terminal. You must re-install OS X from a clean slate, again.

If you want to get 10.8.4, then download the full 10.8.4 image from the Mac App Store or other "not recommended" piracy website--which is about 4 - 5 GB--and then create a new bootable disk and boot the disk, then select your primary OS X partition and then install it there to update without losing your datas.

 

So, have you got the dual-boot working by now?

Share this post


Link to post
Share on other sites

I've installed ML again from clean state 10.8.0 so that is not an issue.

I think that the problem with my boot is that ML partition isn't active :)

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 Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
×