Jump to content

Search the Community: Showing results for tags 'Chameleon'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 82 results

  1. The Chameleon bootloader is an open source project and is released in accordance with the GPL v2 license. The source code can be found at the voodooprojects' forge where it can be downloaded and compiled.If you are not comfortable downloading and compiling source code or you just want a quick method of obtaining the last binaries then there is a Buildbot dedicated to compiling and making ready up to date builds for download. Chameleon can then be installed to your system using the Terminal and a lot of people choose this option as they have full control over what they're doing. However, other users prefer to have it automated and that is why the Chameleon package installer exists. This topic is dedicated to the Chameleon/Enoch package installer. What can I install to? • It can install to a hard drive or USB flash drive using either an MBR or hybrid GPT/MBR, and can install to FAT32, HFS and ExFat partitions. Note: the Installer allow the installation to the EFI partition also. What benefits do I get from using it? • Any existing stage 2 boot file and /Extra folder will be backed up before installation. • You can choose to select from the majority of supported available boot options and kernel flags. • Any existing boot options and kernel flags can be deselected if required. • Existing com.apple.Boot.plist will be changed to org.chameleon.Boot.plist. • Installation log is saved for your record. • Multi-language support. • Intelligent installation of stage 0 code (boot0, boot0hfs, boot0md) depending on existence of Windows. • Checks to avoid possibility of a b1f:error or boot1:error if installing a secondary boot partition. • Decide witch bootloader installation stage to skip to preserve your boot sector. • Modify the org.chameleon.Boot.plist, the kernel.plist, install Themes or modules w/o reinstalling the bootloader. • The installer is under continuous development. *What's New in Enoch Running OS X10.11 El Capitan since r2714 (credit Pike R. Alpha) Allow untrusted kexts w/o rootless=0 flag for safety reason since r2732 (credit Pike R. Alpha) Add ability to set custom CsrActiveConfig value in org.chameleon.Boot.plist r2736 (credit ErmaC) Black Mode for 10.10 + ported by ErmaC, since r2745 (credit Pike R. Alpha) implemented the Clover kernel patcher configurable by /Extra/kernel.plist, since r2768+ (credits goes to meklort, Clover team, ErmaC, Micky1979, Bronya, Pike R. Alpha, donovan6000, RehabMan, sherlocks, stinga11, Tora Chi Yo) Boot from Recovery HD since r2768 (credit Micky1979) Boot from Vanilla Installer created with "createinstallermedia" method since r2768 or running the "Install app" since r2770 (credit Micky1979) Booting the Recovery HD crsutil is now configurable with or w/o nvram support, since r2770 (credit Pike R. Alpha) Bing thanks to all who made tests, especially @crazybirdy who have tried all OSes/Installers and relative Recovery HD partitions since 10.4.11 *code will be ported to the main Trunk soon, just let users confirm that all is fine with the current code. ------------------------------------------------------------------------------------------- I do not consider myself responsible for any loss of data on your hard drives. Please don't upload it on other servers and don't repack it, thank you. Latest Trunk Pkg and Binaries ==> available in the download section >> HERE Latest Enoch Pkg and Binaries ==> avaiable in the download section >> HERE Please don't upload it on other servers and don't repack it, thank you. ------------------------------------------------------------------------------------------- Hi people. PLS help Previously, it was raised here (collected), a lot of languages... the localizable.strings file was translated into several languages ​​... Now it's time to dust off that file and re fit. and the list of the various languages ​​with relative links. will be added (after adjustment). For on-line Chameleon language package resource edit >> Pootle Pls translate/complete it. ___________________________________________________ How to install Chameleon manually HERE c0rk007hck topic How to install Chameleon manually to EFI partition HERE munky topic How to install chameleon manually to a software RAID HERE nathan7 topic _______________________________________________ Experimental .dmg February 17 2011 Chameleon.747.zip NOTE: Before restart the machine after using the pkg check the com.apple.Boot.plist into the Extra folder bug found ___________________________________________________ Related topic: Intel HD4000, Haswell and Broadwell Inject AAPL,ig-platform-id HDAEnabler for Chameleon and Enoch exFAT Volume Boot Record for Chameleon and Enoch nVidia Sub-Vendor & Sub-Device Injection for Chameleon and Enoch ErmaC
  2. *****NOW UPDATED FOR YOSEMITE - PLEASE REPORT ANY PROBLEMS IN THE COMMENTS***** *****There are subtle differences in the guide depending on whether you’re using Lion / Mountain Lion or Mavericks***** *****For Lion / ML use the blue line. For Mavericks use the red line. For Yosemite use the green line.***** *****If you're creating the installer for Lion/ML use "Essential 03.08.2012" attachment***** *****Otherwise use the attachment for the version you’re using***** *****This guide will not work for versions of OS X earlier than Lion (10.7)***** The all-in-one guide to vanilla OS X + Chameleon + DSDT for beginners Preface: So I’ve built a few hackintoshes now to the point where I’ve a good idea what I’m doing. I’ve gone the distro way before as well as the vanilla way and I agree fully with the idea that vanilla is better. The problem with it being that I haven’t found a well explained start to finish guide of how to do it without a lot of Googling and combining numerous different guides so my idea is to collate everything into one place for beginners to hopefully understand the process better and build better systems. A lot of the leg-work for this guide has been done by other people; although I’m rewriting most of it if anyone wants credit adding to something I’ve accidentally stolen from them just PM me. Throughout the guide I try to avoid scripts and utilities so you can learn what your doing. If you want a one-click install this is not the guide for you; having said that there is nothing technically complicated that isn’t clearly explained so don’t be scared off if you’re a rookie. If any one has any suggestions on how to improve this guide PM me or mention it on the forum thread. Those who experience problems make sure you’ve read Part 7 before posting to the forum asking for help. Part 1 - Prerequisites 1.0. Basic Requirements: The basic requirements for OS X from Lion onwards are: 1. A Core 2 Duo processor or later 2. 2GB or more RAM 3. 8GB of disk space N.B. For details of specific hardware compatibility see the hardware compatibility list (HCL) in the wiki: http://wiki.osx86project.org/wiki/index.php/Main_Page Further to compatible hardware you will need: 1. A working install of OS X (this may be in a virtual machine or a native install) to prepare the installer 2. A flash drive of minimum size 8GB 3. A copy of Lion / ML / Mavericks 4. Patience Note: All essential software / kexts below are in the attachment. 1.1. Essential Software You will need to obtain the following. I suggest you place them all in the same folder along with the essential kexts below for use later: 1. The Chameleon boot loader, the latest version of which can always be found here (You want "The Latest Trunk PKG ~ Standard and Official Revision"): http://www.insanelymac.com/forum/index.php?showtopic=231075 2. Chameleon wizard to create a smbios (basically identify your machine as a mac) and to help with bootloader problems http://www.insanelymac.com/forum/index.php?showtopic=257464 3. System info for finding device ID’s for general post-install troubleshooting (Check you get the Mac version). http://www.insanelymac.com/forum/index.php?showtopic=219584 4. DSDT editor for extracting your DSDT once were up and running: http://www.insanelymac.com/forum/index.php?showtopic=223205 5. Kext utility for installing additional kexts post-install: http://cvad-mac.narod2.ru/Kext_Utility/ 1.2. Essential Kexts (kernel extensions) 1. FakeSMC – absolutely essential – tricks OS X into thinking it’s a real Mac. http://www.projectosx.com/forum/index.php?showtopic=1643 2. NullCPUPowerManagement – generally required initially to prevent kernel panics, may not be needed once AppleIntelCPUPowerManagement is patched after install. http://www.osx86.net/view/16-nullcpupowermanagement_(32--64-bit).html Part 2 - Creating the installer 2.0. Preparing the USB 1. In your working OS X install open Disk Utility 2. Click on your USB drive in the left sidebar 3. Click the “Partition” tab 4. Under “Partition Layout” click “1 Partition” 5. Click Options -> select “GUID Partition Table”; check the format is set to “Mac OS X Extended (Journaled)”; name it “USB” and click Apply 2.1. Creating the OS X installer on the USB drive 1. Mount your OS X DMG. If using a copy downloaded from the app store: Navigate to Applications (which is where it will save your downloaded copy of OS X by default) -> right click "Install OS X *version*" and click "Show Package Contents" -> Contents -> SharedSupport -> Double click "InstallESD.dmg" 2. Mount BaseSystem.dmg by typing the following in terminal: open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg 3. Go back to disk utility and click on “(Mac )OS X Base System”, click the “Restore” tab then drag and drop “(Mac )OS X Base System” to “source” and your USB to “destination” and click restore then erase. This will take a while. 4. You’ll now have 2 “(Mac )OS X Base Systems present in Finder, right click them and “get info” to determine which is your USB drive (hint: look at the size). 5. Navigate to the one which is your USB drive, open it and go to /System/Installation. Delete the “Packages” link then create a folder called “Packages”. 6. Open a new Finder window and navigate to “(Mac )OS X Install ESD”. Copy everything inside the packages folder to the packages folder you have just created. This will take a while. 7. Copy mach_kernel from “OS X Install ESD” to the root of your USB drive. 7. Use pacifist to extract mach_kernel from “OS X Install ESD/Packages/BaseSystemBinaries.pkg” and copy it to the root of your USB drive (note: this is in the attachment). 7. Use pacifist to extract kernel from “OS X Installed ESD/Packages/Essentials.pkg/System/Library/Kernels/Kernel” and copy it to /System/Library/Kernels/ (You may need to create the “Kernes” folder) (note: this is in the attachment). 8. Copy BaseSystem.chunklist and BaseSystem.dmg from InstallESD.img to the root of your USB drive. Since these files are hidden you must first show hidden files by typing the following in Terminal "defaults write com.apple.Finder AppleShowAllFiles YES" followed by "killall Finder". Once copied you can type "defaults write com.apple.Finder AppleShowAllFiles NO" followed by "killall Finder" to hide hidden files. The terminal will look something like this when you are done: 2.2. Patching the installer for a PC 1. Remember the two kexts we downloaded above? Copy both of them to /System/Library/Extensions on your USB stick. 2. Run the chameleon installation package and ensure to choose your USB drive as the destination. 3. Go to the root of your USB drive and create a folder called “Extra”. This is used to store configuration files for the chameleon boot-loader. 4. Open Chameleon wizard, click the “SMBios” tab then click "Edit". Now there is a list of “Premade SMBioses”. Look through this list to see which relates best to your PC (Hint: iMac 12.2 for modern desktops or MacBook Pro 8.3 for modern laptops is a good place to look to start with). Click “Save As” and save it to the /Extra folder we created on the USB stick. N.B. make sure you’ve got a smbios from a Mac which supports your version of OS X, for a list of which do see here: http://www.apple.com/osx/specs/ 5. Use chameleon wizard to generate an “org.chameleon.boot.plist” this is necessary to set the kernel flag “kext-dev-mode=1” which allows us to boot using unsigned kexts. If you already have an org.boot.chameleon.plist you may simply add “kext-dev-mode=1” to your list of kernel flags. If not then use the one from the attachment. Copy this file to the /Extra folder we created on the USB stick. 6. Copy your folder of essential software & kexts to the root of your USB stick. N.B.1: For those with a fully-working Lion / ML install you may omit 2.C.3. & 2.C.4. and use your old /Extra folder (including smbios & org.chameleon.boot.plist & DSDT). N.B.2: ATi6xxx users see step 7.6 now! 2.3. A note for those wishing to boot OS X and Windows on the same HDD (This is not recommended but may be necessary for those installing on laptops) The OS X installer won’t install to an MBR partition scheme which Windows requires so we must patch the installer to allow this. If you intend on dual-booting OS X and Windows 7 then I suggest you install Windows 7 and update to Service Pack 1 before you install OS X to prevent problems updating to SP1 later. How to patch: 1. Download the required files from here: http://www.osx86.net/view/2815-osinstallmbr+osinstall.mpkg_10.8.gm.html 2. On the USB stick navigate to /System/Installation/Packages/. Delete OSInstall.mpkg and replace it with the one you just downloaded. 3. On the USB stick navigate to /System/Library/PrivateFrameworks/Install.framework/Frameworks/OSInstall.framework/Versions/A/. Delete OSInstall and replace it with the one you just downloaded. Part 3 – Installing OS X 3.1 Installing OS X 1. Stick the USB drive in the computer you wish to install OS X on and boot from your USB drive. If you’re unsure how to do this when your computer first turns on look for a prompt that says “Press X for boot selection menu” (where X is a key) or something of that effect. Common keys are F8 & F12. 2. When Chameleon comes up press enter to boot OS X. The OS X installer should boot. Go to the utilities menu and click disk utility. Select the disk / partition you wish to install OS X to, call it "OS X" and format it as “Mac OS X Extended (Journaled)” (See Part 2.1. if you’re a bit rusty with disk utility). N.B. For those dual booting on the same HDD as Windows ensure you've got the Partition Scheme set to MBR. 3. Follow the installer to install OS X to the desired partition. 4. Take a well-deserved rest while it installs. 5. Once the installer is finished it will reboot, on reboot boot back into the install USB NOT your OS X install. 3.1 Fixing the OS X install 1. From the installer go to Utilities and Terminal. 2. Type cp –R /System/Library/Extensions/NullCPUPowerManagement.kext /Volumes/"OS X"/System/Library/Extensions/ 3. Type: cp –R /System/Library/Extensions/FakeSMC.kext /Volumes/"OS X"/System/Library/Extensions/ 4. Type reboot NOTE: Include the quotes in the lines above. This assumes your install partition is called “OS X” as I said above. If for whatever reason you called it something else replace “OS X” with whatever you called it (still surrounded by quotation marks). Part 4 – Initial booot 1. Reboot your system and boot to the USB stick again but this time select your OS X install. This should boot you into your installed copy of OS X. 2. Open "System Preferences" go-to "Security and Privacy", click the lock and give it your password then set "Allow applications downloaded from" to anywhere. 3. Navigate to your folder of essential software and run the chameleon package, install it to your OS X drive. 4. Copy the Extra folder on your USB drive to the root of your HDD (open Finder -> Go -> Computer -> OS X -> paste folder). 5. Reboot, remove USB, and let the computer boot from your HDD, select OS X and it should boot straight to OS X. You are not finished! You now need to at least read through step 6! Part 5 – DSDT 5.0 Extraction Although not strictly required it is useful to have a DSDT for your system; with a bit of research and patching it can be used to solve almost all problems you may encounter. For those interested in what it actually is see here: http://wiki.osx86pro.../index.php/DSDT How to create it: 1. Open DSDT Editor 2. Go-to File -> Extract DSDT 3. Go-to to IASL -> Compile (if you get any errors click “Fix Errors”) 4. Go-to IASL -> Save AML as. Save it as “DSDT.aml” in /Extra. 5.1 Common Fixes (coming soon eventually…) Part 6 – Finishing Touches 6.0. A note on non-Mac monitors Most non-Mac monitors will start with the wrong color calibration. To fix this go-to "System Preferences" -> "Displays" -> "Color" -> select "Generic RGB Profile". Further to this, due to Mac monitor having a different dot pitch to normal monitors, LCD font smoothing may make the fonts appear blurred. To turn this off go-to “System Preferences” -> General -> uncheck “Use LCD Font…” (at the bottom). 6.1. Keymaps If you have a British standard keyboard you will need to install the keymaps in the attachment. To do so decompress the attached zip and copy its contents to /Library/Keyboard Layouts then change the keymap by going to System Preferences -> Keyboard -> Input Sources. 6.2. org.chameleon.boot.plist If you open Chameleon Wizard you can navigate to “org.chameleon.boot” here you can assign numerous settings which will be useful later as well as setting the default timeout and specifying the location of your SMBios and DSDT if you don’t place them in /Extra. I suggest you ensure the “Ethernet Built In” box is checked then set the "Time Out" to a reasonable figure and then click "Save As' and save it to /Extra (Note: save it as org.chameleon.boot, it automatically appends the .plist extension). When you've saved it you can go to "Theme" and download and apply a theme for the boot loader rather than having the default text boot. Once your system is stable and with all necessary hardware enabled set UseKernelCache=Yes to speed up boot times. 6.3. NullCPUPowerManagement Currently we have NullCPUPowerManagement.kext installed. This disables speed-stepping and thus sleep (by disabling AppleIntelCPUPowerManagement.kext) so we need to remove it for a better system. Unfortunately not all system’s will work with the version that comes with OS X. The first thing to do is to try your system without it, to do this simply navigate to /System/Library/Extensions on your OS X drive and delete it then reboot. It’s possible you will see a kernel panic on reboot, if this is the case you will need to reinstall the kext by following Part 3.1.1&3.1.2. If your system panics on boot then you require a patched version of AppleIntelCPUPowermanagement; reading round the forum should allow you to obtain this relatively easily. 6.4. Device Compatibility At this point it’s very likely you will have some devices not working. The best way to get devices working is through DSDT edits rather than by adding kernel extensions; often additional kernel extensions will have to be re-installed after updates whereas DSDT edit are permanent. To enable devices by using additional kexts: Run the “System Info” app we downloaded and click File -> check compatibility. This will let you see which devices are working and which aren’t. You can Google your vendor & device ID to find info about making them work. Once you find a kext that appears to be compatible for your hardware drag and drop it onto kext utility to install it. Example: If your Wi-Fi isn’t working you can look for your Wi-Fi device and find its device / vendor ID’s in my case its vendor ID is 168c and its device ID is 002a so Googling for “168c:002a kext” would return results about making the device work. 6.5. Finder grid view (windows explorer behaviour) To make finder sort files in a grid by default open Finder, navigate to your root folder of the OS X install. Go-to View -> Show View options -> Arrange by "Name" -> Click "Use As Defaults" Part 7 – Common Errors & Basic Diagnostics 7.0. Boot0:Error Boot0 error is most likely caused by incorrectly installing chameleon or having a drive with 4k-sector allocation. Try to reinstall chameleon (use the latest version!), if that doesn’t work see here: http://www.macbreaker.com/2012/02/hackintosh-boot0-error.html 7.1. Boot flags When the chameleon screen boots you can specify kernel arguments to attempt to solve problems you may be having. When you see the boot-loader pop up press any key and ensure your OS X install is highlighted. You can then type any combination of kernel flags (with a space between them) to try to boot OS X / diagnose problems. For a complete list of kernel flags see here: http://www.osx86.net/guides-tutorials/10747-guide-chameleon-bootloader-basics.html A few of the more common ones are: 1. –v verbose mode. If the system panics take a screen shot of the panic when you have typed this at boot and post it to the forums. It will help people diagnose your problems but won’t fix any problems. 2. –x safe boot (like windows safe mode – minimal drivers). 3. –f boot without the kernel cache (useful if you’ve installed kexts without rebuilding the kext cache – if you’ve used kext utility you shouldn’t have to use this). 4. –npci=0x2000 (or –npci=0x3000) fixes the “PCI configuration Begin” error. 5. PCIRootUID=0 solves problems for some NVIDIA graphics card users (if it doesn't solve your issue try =1 instead). 6. GraphicsEnabler=Yes (or GraphicsEnabler=No) add support for some non-OS X graphics cards. 7. Note: The arch=i386 boot flag is now depreciated due to ML’s 64-bit only kernel. 7.2. The console The console gives you a verbose output of any and all errors the system may encounter. It's particularly useful if you've a system which won't stay in sleep mode. Go-to Applications -> Utilities -> Console to open it. 7.3. App store "Your device or computer could not be recognised..." error. App-store requires a MAC address to verify your computer (any address, it doesn't have to be an apple one) hence you MUST have a working Ethernet or Airport card for App Store to work. The problem is if you've enabled network hardware after first boot OS X won't update its caches. The fix: Ensure "ethernet buit in" is checked in your org.chameleon.boot.plist. Go to system preferences and delete all the devices in the network section. Navigate to /Library/Preferences/SystemConfiguration and delete com.apple.airport.preferences.plist and networkinterfaces.plist and com.apple.boot.plist. Reboot then add your network interfaces in system preferences. Check app-store is now working. 7.4 Motherboard POST Freeze I your motherboard freezes during POST (you don’t even get past the BIOS screen) it’s possible your BIOS isn’t compatible with the GUID partition table of the USB we created the installer on. To fix this in step 2.0.5 select MBR instead of GUID. Note: If you make it to the OS X boot-loader this is not your problem and will not fix any issues other than hanging at POST. For more information see here: http://www.rodsbooks.com/gdisk/bios.html 7.5 When posting to the forum asking for help When posting to the forum asking for help if the installer / installation won’t boot please post a screenshot of where it stops – I suggest you post this to a new thread in a suitable place in the forum rather than this guide. 7.6 ATi6xxx card white screen error There is a know permissions error in Mountain Lion regarding the ATi6000Controller kext causing white screen. To fix this: Navigate to /System/Library/Extensions on your install USB and copy ATi6000Ccontroller to your folder of essential kexts. Delete ATi6000Controller from /S/L/E. Install OS X (note: you will only have basic graphics support). After install (at the end of step 4) you can drag & drop the kext onto kextutility then reboot to enable your card. Part 8 - Useful Tips 8.0. To show or hide hidden files: In the terminal type: defaults write com.apple.finder AppleShowAllFiles YES or defaults write com.apple.finder AppleShowAllFiles NO Followed by killall Finder 8.1. Spaces in terminal When using the terminal spaces must be preceded by \ or the file or folder name placed in quotations e.g.: open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg or open /Volumes/"Mac OS X Install ESD"/BaseSystem.dmg Part 9 – References Massive credit goes to this guide here: http://thetecherra.com/2012/07/10/tutorial-run-os-x-mountain-lion-10-8-gm-on-a-pc-hackintoshosx86-video/ and this guide here: http://www.insanelymac.com/forum/index.php?showtopic=277015 Part 10 – Change-log v2.3 - 25/07/2012 - Minor update to include InstallESD location from app-store. v2.4 - 27/07/2012 - Minor updates regarding Gringo Vermelho’s post. v2.5 - 03/08/2012 - Minor updates and touch-ups. v2.6 - 22/08/2012 - Addition of UseKernelCache=Yes plus key-maps and a few minor tweaks. v3.0 – 24/10/2012 – Addition of screenshots v3.1 – 03/12/2012 – British keyboard layout added v4.0 – 07/10/2013 – Updates so guide complies with Mavericks install procedure v4.2 – 10/11/2013 – Ironed out differences between Lion/ML and Mavericks v4.3 – 16/10/2014 – Added Yosemite support Essential - 03.08.12.zip Keyboard Layouts.zip Essential - Mavericks GM - 7.10.2013.zip Mavericks Install Guide - v0 - Quick Ref.pdf Mavericks install Guide - v4.2 - With Sreenshots.pdf Vanilla OS X Install Guide - v4.3 - With Sreenshots.pdf
  3. Enoch Bootloader The son of Chameleon by ErmaC Introduzione: ======================================== Aggiornamento : Per cortesia non postare questi file su altri server e non rielaborarli per altre distribuzioni, grazie. Enoch PKG & Binari rev 2210 nella nuova sezione Download >> Enoch Bootloader Tema personalizzato per Enoch creato da carlo_67 >> Enoch Thema.zip (6 Gennaio 2015) ======================================== Le KeyFlag di Enoch per l'org.chameleon.Boot.plist: IntelCapriFB settato con un valore compreso tra 0 e 11 (FB per le Intel HD4000) IntelAzulFB settato con un valore compreso tra 0 e 15 (FB per le Intel Haswell) IntelBdwFB settato con valore compreso tra 0 e 18 (FB per le Intel Broadwell) NvidiaGeneric settato su Yes nel o.c.B.p visualizza il nome generico per le schede grafiche nVidia (GraphicsEnbler) EnableDualLink settato su Yes nel o.c.B.p inietta il valore AAPL00,DualLink sia nVidia che ATi (GraphicsEnbler) SkipIntelGfx settato su Yes nel o.c.B.p salta il riconoscimento delle schede grafiche Intel (GraphicsEnbler) SkipNvidiaGfx settato su Yes nel o.c.B.p salta il riconoscimento delle schede grafiche nVidia (GraphicsEnbler) SkipAtiGfx settato su Yes nel o.c.B.p salta il riconoscimento delle schede grafiche AMD/Ati (GraphicsEnbler) USBInject settato su Yes nel o.c.B.p assegna valori alle tipologie di USB incontrate (UHCI/OHCI/EHCI/XHCI) EnableBacklight settato su Yes nel o.c.B.p abilita il Backlight © a Marchrius (GraphicsEnbler) EnableWifi settato su Yes nel o.c.B.p setta i device wifi come Built-In Le KeyFlag di Enoch per l'smbios.plist SMboardtype settato su 11 (congiuntamente a un MacProX.1) nel smbios.plist visualizza il numero slot processore in System Profiler ======================================== Caratteristiche in lavorazione: -------------------- Abilitazione Audio HDAEnabler senza ausilio di HDEF nel DSDT o HDAEnabler.kext TESTING -------------------- Riconoscimento del subvendorId e subdeviceId anche per le schede nVidia COMPLETATO -------------------- Abilitazione Connessioni HDMi su schede nVidia e Ati. COMPLETATO ======================================== Fabio
  4. Andy Vandijck

    My Github projects

    My main Github page is here: https://github.com/andyvand At current it has the following projects: - decompkernelcache: This is my decompkernelcache project, now also with updated code for LZVN decompression and soon it will be able to compress kernel cache too. - Enoch: This is a custom build of ErmaC's Enoch bootloader, prebuilt with Xcode 6.1.1 - LZVN: Pike R. Alpha's LZVN tool with some enhancements, this can compress and decompress LZVN code and has C library for LZVN compression and decompression (except for lzvn_encode_partial which at the moment is still assembly). - macosxbootloader: Custom version of boot.efi for Yosemite (and older) with universal EFI support. For booting Yosemite on 32-bit EFI Macs, such as the MacPro1,1 and 64-bit support too, this is in general a custom OS X boot.efi, also now support for building with Clover tools (GCC+binutils+latest nasm) or Xcode (needs mtoc and latest nasm), now also option for building installer packages and hackintosh specific version. - UEFIRomExtract: My UEFI VBIOS .efi file extractor, includes windows version and sources ofcourse for both *nix and Windows versions. Will update this page if more projects get added Enjoy
  5. I open this new topic to discuss/test (and hopefully improve) the proposed changes made by the user N3 on http://forge.voodooprojects.org So this code and work is not mine (ErmaC), also I not test it right now. I recentrly merge on the main trunk project the base icons for the recovery disk made long time ago by blackosx (Many thanks! Finally we can use it!) So let's start with the proposed patch: boot.c --- trunk/i386/boot2/boot.c 2014-10-30 15:01:44.000000000 +0000 +++ trunk_mod/i386/boot2/boot.c 2014-10-30 22:02:41.000000000 +0000 @@ -318,22 +318,28 @@ long LoadKernelCache(const char* cacheFi // If boot from a boot helper partition check the kernel cache file on it if (gBootVolume->flags & kBVFlagBooter) { - snprintf(kernelCachePath, sizeof(kernelCachePath), "com.apple.boot.P%s", kernelCacheFile); + snprintf(kernelCachePath, sizeof(kernelCachePath), "/com.apple.boot.P/%s", kernelCacheFile); ret = GetFileInfo(NULL, kernelCachePath, &flags, &cachetime); if ((ret == -1) || ((flags & kFileTypeMask) != kFileTypeFlat)) { - snprintf(kernelCachePath, sizeof(kernelCachePath), "com.apple.boot.R%s", kernelCacheFile); + snprintf(kernelCachePath, sizeof(kernelCachePath), "/com.apple.boot.R/%s", kernelCacheFile); ret = GetFileInfo(NULL, kernelCachePath, &flags, &cachetime); if ((ret == -1) || ((flags & kFileTypeMask) != kFileTypeFlat)) { - snprintf(kernelCachePath, sizeof(kernelCachePath), "com.apple.boot.S%s", kernelCacheFile); + snprintf(kernelCachePath, sizeof(kernelCachePath), "/com.apple.boot.S/%s", kernelCacheFile); ret = GetFileInfo(NULL, kernelCachePath, &flags, &cachetime); - if ((flags & kFileTypeMask) != kFileTypeFlat) + if ((ret == -1) || ((flags & kFileTypeMask) != kFileTypeFlat)) { - ret = -1; + snprintf(kernelCachePath, sizeof(kernelCachePath), "/com.apple.recovery.boot/kernelcache", kernelCacheFile); + ret = GetFileInfo(NULL, kernelCachePath, &flags, &cachetime); + + if ((flags & kFileTypeMask) != kFileTypeFlat) + { + ret = -1; + } } } } gui.c --- trunk/i386/boot2/gui.c 2014-10-30 16:41:03.000000000 +0000 +++ trunk_mod/i386/boot2/gui.c 2014-10-30 22:07:31.000000000 +0000 @@ -988,16 +988,14 @@ void drawDeviceIcon(BVRef device, pixmap { case kPartitionTypeHFS: { - // ErmaC : TODO test needed for recovery icon - // Use HFSRECOVERY icon. -// if (device->flags & kBVFlagBooter) -// { -// devicetype = iDeviceHFSRECOVERY; -// } -// else -// { + if (device->flags & kBVFlagBooter) + { + devicetype = iDeviceHFSRECOVERY; + } + else + { // Use HFS or HFSRAID icon depending on bvr flags. Fallbacks are handled by alt_image above. switch (device->OSVersion[3]) { @@ -1032,7 +1030,7 @@ void drawDeviceIcon(BVRef device, pixmap devicetype = (device->flags & kBVFlagBooter ? iDeviceHFSRAID : iDeviceHFS); break; } -// } + } break; disk.c --- trunk/i386/libsaio/disk.c 2014-10-30 15:07:54.000000000 +0000 +++ trunk_mod/i386/libsaio/disk.c 2014-10-30 22:03:26.000000000 +0000 @@ -1575,21 +1575,43 @@ static bool getOSVersion(BVRef bvr, char config_file_t systemVersion; char dirSpec[512]; - sprintf(dirSpec, "hd(%d,%d)/System/Library/CoreServices/SystemVersion.plist", BIOS_DEV_UNIT(bvr), bvr->part_no); + sprintf(dirSpec, "hd(%d,%d)/com.apple.recovery.boot/SystemVersion.plist", BIOS_DEV_UNIT(bvr), bvr->part_no); if (!loadConfigFile(dirSpec, &systemVersion)) { + bvr->OSisInstaller = true; valid = true; } - else + + if (!valid) { - sprintf(dirSpec, "hd(%d,%d)/System/Library/CoreServices/ServerVersion.plist", BIOS_DEV_UNIT(bvr), bvr->part_no); + sprintf(dirSpec, "hd(%d,%d)/System/Library/CoreServices/SystemVersion.plist", BIOS_DEV_UNIT(bvr), bvr->part_no); if (!loadConfigFile(dirSpec, &systemVersion)) { - bvr->OSisServer = true; + bvr->OSisInstaller = true; valid = true; } + else + { + sprintf(dirSpec, "hd(%d,%d)/System/Library/CoreServices/ServerVersion.plist", BIOS_DEV_UNIT(bvr), bvr->part_no); + + if (!loadConfigFile(dirSpec, &systemVersion)) + { + bvr->OSisServer = true; + valid = true; + } +/* else + { + sprintf(dirSpec, "hd(%d,%d)/.IAProductInfo", BIOS_DEV_UNIT(bvr), bvr->part_no); + + if (!loadConfigFile(dirSpec, &systemVersion)) + { + + } + } +*/ + } } if (valid) @@ -1633,7 +1655,19 @@ static bool getOSVersion(BVRef bvr, char } else { - close(fh); + sprintf(dirSpec, "hd(%d,%d)/.IAPhysicalMedia", BIOS_DEV_UNIT(bvr), bvr->part_no); + fh = open(dirSpec, 0); + + if (fh >= 0) + { + valid = true; + bvr->OSisInstaller = true; + strcpy(bvr->OSVersion, "10.9"); // 10.9 + + } + else + { + close(fh); + } } } return valid; stringTable.c --- trunk/i386/libsaio/stringTable.c 2014-10-30 15:12:08.000000000 +0000 +++ trunk_mod/i386/libsaio/stringTable.c 2014-10-30 22:04:06.000000000 +0000 @@ -614,8 +614,11 @@ int loadConfigFile (const char *configFi int loadSystemConfig(config_file_t *config) { char *dirspec[] = { + "/Mac OS X Install Data/com.apple.Boot.plist", "/OS X Install Data/com.apple.Boot.plist", + "/.IABootFiles/com.apple.Boot.plist", // OS X Installer "/Library/Preferences/SystemConfiguration/com.apple.Boot.plist", + "/com.apple.recovery.boot/com.apple.Boot.plist" // OS X Recovery }; int i, fd, count, ret=-1; Here the diff file to apply on the current trunk(2456) --> recovery.diff recovery.txt (I edit the file extension due to server restriction) Here the precompiled binaries with the changes included. Please don't upload it on other servers and don't repack it, thank you. i386_v2456_Recovery_v1.zip Please don't upload it on other servers and don't repack it, thank you. Credits to N3 Cordially ErmaC
  6. Hi all, First time poster so please excuse my general lack of knowledge I purchased a 'pre-built' Hackintosh around a year ago. It's been pretty smooth sailing, even given my lack of technical skills. I'm now looking at installing a larger SSD and, whilst I'm at it, upgrading to 10.9 Mavericks. Found a great guide on this here forum which looks relatively straightforward (even for me!) Only thing is, I'm not sure how I go about 'extracting' the customisations that were put in place by my kindly supplier to get the system running on 10.8. In other words, how do I extract the stuff in the 'Extra' folder (and elsewhere) to make the process of installing 10.9 as simple as possible? Any help would be greatly appreciated. Cheers, andy
  7. Salve a tutti, oggi mi sono trovato a dover superare un piccolo problema con Chameleon che non mi permetteva di avviare Yosemite dopo l'aggiornamento alla DP2. Il mio Hackintosh si bloccava a questa schermata, dandomi dei problemi legati al KERNEL. Ma vediamo come superare questo "ostacolo" Poiché il kernel, con l'uscita della DP2, è stato aggiornato alle versione 14.0.0, Chameleon ha bisogno di quello originale della DP2 per potersi avviare e completare l'aggiornamento. Ho estratto il kernel da un' altro Hack che non ha avuto problemi di aggiornamento, lo allego in fondo al post. Quindi: Posizionare il nuovo file mach_kernel, qua allegato nella USB dell'Installer (*ATTENZIONE A NON SOSTITUIRLO, POSIZIONATELO IN UNA SOTTO CARTELLA*) Avviare l'Installer ed aprire Disk Utility; Disattivare la partizione contenente Yosemite; Aprire il Terminale da Utility in alto; digitare "sudo cp -R /Volumes/*nomeinstaller*/*sottocartella*/mach_kernel /Volumes/*nomeYosemite*/ Così facendo, dopo aver inserito la password, se non riceverete errori di alcun tipo, potrete procedere all'avvio della partizione di Yosemite senza alcun problema legato al kernel. A presto, spero possa essere utile mach_kernel Originale 14.0.0: https://mega.co.nz/#...yiluc425PVoovMc
  8. I tried making a USB Installer for Mavericks DP1, I prepared a GUID'd 16GB USB key with the Mavericks Installation base and installed Chameleon 2.2 svn r2262 on it. I tried booting it on the following machine: Core i7 4770 (not 4770K) Asus Q87M-E motherboard (Intel Q87 chipset) 32GB RAM GeForce GTX 560 Ti 1024 MB BIOS/UEFI settings: disable iGPU, CPU State C, disable Vd-m, disable Vt-x, SATA AHCI mode, USB storate auto mode (also tried force HDD and force CD-ROM), Boot device USB in legacy BIOS mode (also tried UEFI mode). When it tried to boot off my USB key, I get a text cursor '_' in the upper left conner of the screen, the cursor drops to one line bellow, then it goes closer to the middle of the screen, then it disappears and nothing happens. I never even reach the bootloader's text menu. I also create an Mavericks installer on a SATA hard drive, put Chameleon on it and tried boot it from an internal SATA controller. Same result. I know the USB key is properly made since I tested it on my Core 2 Duo system and it boots fine. Could it be a compatibility problem between Chameleon and my motherboard or chipset? All the other posts I see for Haswell systems seem to be based on the Z87 chipset. I am planning on trying with RevoBoot. I also heard you can use GRUB2 to load the OS X kernel directly? If any one else with a Q87 system out there can try Chameleon, your results would be appreciated. As would any solution to my problem.
  9. Hola: Estoy probando Maverick en dos HD, uno con Chameleon y otro con Clover. En ambos casos cuando le doy al botón de encendido para que entre en reposo, la pantalla se apaga de inmediato pero los ventiladores tardan entre 20 y 30 segundos en detenerse. Luego al salir del reposo, la pantalla enciende normal pero a los 3-5 segundos pasa esto (en ambos HD): Tengo un DSDT que uso para ambas instalaciones. He investigado un poco de forma individual cada HD. CHAMELEON: Al encender el equipo veo este error : ¿Supongo bien si creo que es este el error que rompe el reposo? ¿Son estos los UIDs correctos? ¿debo poner el UID correspondiente a la partición Mav? ¿O son estos otros? ¿Donde los pongo y como? CLOVER: Mas de lo mismo: Distintos a los de arriba... Supongo que usando Clover iría aqui: ¿o no? Para mas datos dejo el DSDT y las configuraciones. MSI.zip Un saludo y gracias.
  10. Good evening ladies and gentlemen, iCloud, FaceTime and AppStore works perfectly ! My problem is that iMessages not working. I tested different solutions like delete Networking preferences and interfaces. Add my PlatformUUId into the nvram*.plist file. I have the FileNVRAM in the module folder with the latest chameleon r2258. Error message : Your Apple ID "xxxxxxxxxx@gmail.com" can not be used to configure iMessage at the moment. If it is a new Apple ID, there is no need to create another. To use this Apple ID with iMessage, contact the assistance of the iMessage app with the code below. Client code: xxxx-xxxx-xxxx This is the message original message in French : Votre identifiant Apple « xxxxxxxxxx@gmail.com » ne peut pas être utilisé pour configurer iMessage à l'heure actuelle. S'il s'agit d'un nouvel identifiant Apple, il est inutile d'en créer un autre. Pour utiliser cet identifiant Apple avec iMessage, contactez l'assistance de l'app iMessage avec le code ci-dessous. Code client : xxxx-xxxx-xxxx Last information : My account work perfectly on my Macbook. Waiting to hear from you I wish you happy holidays
  11. The embedded HDAEnabler It allows HDEF and HDAU audio device injection using the bootloader without requiring a DSDT/SSDT or injection kext. It needs to be enabled by adding the follow entry in org.chameleon.Boot.plist <key>HDAEnabler</key> <string>Yes</string>this is a replacement for HDAEnabler.kext or DSDT/SSDT HDEF and HDAU injections. also the layout-id can be customized for the HDEF and also for the HDAU HDEF <key>HDEFLayoutID</key> <string>0C000000</string> HDAU <key>HDAULayoutID</key> <string>01000000</string>DSDT entry provided by the HDAEnabler Method (_DSM, 4, NotSerialized) { Local0 = Package () { "subsystem-id", Buffer (0x04) { 0xA0, 0x00, 0x00, 0x00 }, "subsystem-vendor-id", Buffer (0x04) { 0x6B, 0x10, 0x00, 0x00 }, "built-in", Buffer (One) { 0x00 }, "layout-id", Buffer (0x04) { 0x07, 0x00, 0x00, 0x00 }, "PinConfigurations", Buffer (Zero) {}, "device-type", Buffer (0x25) { "High Definition Audio Controller" }, "device_type", Buffer (0x06) { "Sound" }, "hda-gfx", Buffer() { "onboard-1" } } DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Topic reference: AppleHDA patch request (thx Mirone) Other topic here ErmaC
  12. In the last couple of days, I was writing a Cosmetics nVidia support in Chameleon, and had a few testers, but I need to make sure it works on most supported cards. What cosmetics support would be? I added the recognition of the graphics cards also based on the Sub-Vendor ID and Sub-Device ID. What "COSMETICS" does this mean? It means that you... (we) can now customize the output "string" for your graphics card. Example: - Before1: reading just the Device Id was... GeForce GTX 470 - After1: reading also the Sub-VendorId and Sub-DeviceID will be Zotac GTX 470 - Before2: reading just the Device Id was... GeForce GTX 470 - After2: same Device ID (as for Before1) but different Sub-VendorId & Sub-DeviceId Zotac GTX 470 AMP What happens if the Sub-Vendor and Sub-Devices are missing in the boot loader? In this case will be assigned a standard string based only on the VendorID. First I would like to outline a few things: This isn't a HOW TO get your card working, this is a request for testing. Don't ask how to install the booter, how to use or add a given booter flag or how to run an update, if you don't know how to do that yourself, then this isn't for you, yet, learn that elsewhere, and you're more than welcome here. I don't take responsibility for any damage this may cause, so take your precautions before you use this. This project will take the name of Enoch. This will help you. To not confuse this with Chameleon. The core sources (Booting) are the same as my ErmaC Sub-Branch(Trunk) on voodooprojects. The source code will be committed/released when I have accumulated feedback and different "Subs_ID". Requirements: An NVIDIA already supported cards by Chameleon's GraphicsEnabler. How and what to report: Disable any kind of enabler,DSDT injection, injector or device-properties you're currently using. Save an bdmesg dump (From terminal or from Chameleon Wizard bdmesg’s TAB). A report example Report any observations or comments. Include a screenshot of the Graphics tab from System Profiler when reporting. Bootloader Binaries and changelog: 29th may 2012 More Subs ID 11th may 2012 More Subs ID 9th May 2012 Added a lot of new SubsID 5th May 2012 Added a lot of new SubsID 4th May 2012 Added some new ID and correct old bad names. 3rd May 2012 Added a couple of new Sub-VendorId e Sub-DeviceId with proper card name. Thanks all. Fabio (.: ErmaC:.)
  13. YbrisXtreme

    Problemi con il bootloader

    Salve a tutti, recentemente sulla mia macchina ho installato Backtrack Linux R2 (basato sulla release 11.04 di Ubuntu con desktop-manager KDE 4.2); da questo sorgono i vari problemi con il bootloader; leggendo in rete pensavo sarebbe stato possibile avviare Mac OS X Lion con Grub (v1.98 credo) ma così non è stato: infatti se cerco di avviare Lion mi si oscura il monitor, mi viene letto il disco per alcuni secondi e poi si riavvia...Non so come installare Chameleon con linux, quindi ho le mani legate...Spero possiate darmi una mano, e qualora aveste bisogno di informazioni basta chiedere. Grazie anticipatamente.
  14. carbo178

    Quale Bootloader?

    Salve a tutti, ho voluto provare a cambiare bootloader, installando Clover su una chiavetta, e sorprendentemente mi trovo delle cose in info di sistema che con Chameleon risultavano scorrette, quali la velocità del processore e la diagnosi all'avvio; per il resto non è cambiato nulla a livello di gestione energetica (ancora non va lo sleep anche cambiando i parametri "al volo" nelle opzioni di avvio). Una cosa alla quale non sono riuscito a porre rimedio è la risoluzione errata della grafica integrata quando scelgo di avviare Clover in UEFI; con Chameleon avevo lo stesso problema ma ho risolto semplicemente aggiungendo la stringa Graphics Mode con la risoluzione desiderata in ocbp. La grafica integrata è connessa in HDMI ad un TV LG 22" (l'unica altra connessione possibile è in D-SUB ma con SMBIOS iMac 13,1 non credo funzioni, e se anche funzionasse, la definizione sarebbe terribile), in attesa di acquistare un monitor vero e proprio. I parametri che uso per Chameleon li uso anche per Clover, compreso SMBIOS e DSDT (anche se Clover di default, in base al mio HW aveva deciso di assegnare iMac 12,2). In pratica vorrei sapere: 1- Se ci sono delle opzioni in Chameleon (o enoch) per correggere gli errori che non ho con Clover. 2- Se e come posso fare in modo che Clover gestisca lo sleep (ho cercato di capire il più possibile traducendo in italiano tutto ciò che trovavo, ma sono ancora in alto mare). Grazie a chiunque mi darà una mano
  15. Hej... I am trying to install Mountain Lion on a T430. I never built a Hackintosh before, and I'm a bit overwhelmed. I followed the instructions in this link: http://www.insanelym...howtopic=280756 which I found here on the forum, then looked around for a few kexts and managed to get the laptop keyboard and the trackpad working. It's booting and running smoothly now (with Chameleon), but... I still have two big problems: audio and wi-fi internet (I tried by installing the RealtekRTL81xx kext, but either that is not enough, or not right at all.) Can anyone help me getting them to work? Anything would be appreciated (a tip for kexts, explanation how to do it with DSDT - I still don't even know what that does -, a new installation with M u l t i B e a s t &c - which so far I didn't use - or whatever.) Also interesting would be to get full graphic support (which I just read about a lot, but how will I know when I have that - I mean, I can see things on my monitor already, so something is working) and also using the built-in camera (I read about a different ThinkPad that it only works together with CamTwist, which would be fine, I guess.) But really important are internet and sound, of course - can someone help with that? Some other info... "System Info" tells me I have the following: Intel Centrino Ultimate-N 6300 (Network Controller) Intel 7 Series / C210 Series Chipset Family High Definition Audio Controller (Audio device) Intel 82579LM Gigabit Network Connection (Ethernet Controller) Intel 7 Series / C210 Series Chipset Family KT Controller (Communication Controller / Serial Controller) NVIDEA GF108 High Definition Audio Controller (Audio device) NVIDEA GF108 Quadro NVS 5400M (Display Controller / VGA compatible Controller) ... and some other things - I can list them all, if someone things he can help me and needs to know about them, of course. I'm still trying around, but I'm completely new to this and most of the time I don't know what I'm doing. It's just try and error, but it's not a creative process, I know too little about all the steps or relations, so if I'd ever be halfway there or almost have it or just persue a dead end, I'd never know, it's all the same to me... So please - if someone could turn me in the right direction, that would be great! UPDATE: I have it identified as MacBook Pro 6.1 - should I use MacBook Pro 8.1 ? And can I still change that now?
  16. ErmaC


    Version r2922


    Enoch Latest revision of my Chameleon bootloader branch. Not able to boot AFPS yet.... Please don't upload it on other servers and don't repack it, thank you. - Installer PKG - Binaries format (Manual install) Please don't upload it on other servers and don't repack it, thank you. Chameleon bootloader credits goes to Chameleon Team http://forum.voodooprojects.org Changelog: http://forge.voodoop...e/changes/HEAD/ This revision of Enoch contain the upcoming FileNVRAM revision 1.1.5 (RC8) Credits to Micky1979 Language Translation: For on-line Chameleon language package resource edit >> Pootle Pls translate/complete it. Link here on InsanelyMac (Italian only): Enoch Bootloader Enjoy ErmaC
  17. I just installed Mavericks on my Atom-powered Asus 1201n. The installation method i used was cloning my successful installation on my main machine to a 16GB USB thumb drive, and then to a partition on my netbook, then adding fakesmc and nullcpupowermanagement, and installing Chameleon (r. 2171). Finally, i copied my working Extra folder from the main partition of my netbook to the new one.It sorta managed to boot - using -f - but it hangs right where the userland would, well, land. That means it's either something i missed - and i'm performing changes right now - or the kernel patcher module, that was our oasis with Mountain Lion, cannot handle Mavericks' kernel, which would be sad.I'll keep you all posted!
  18. carbo178


    Version 1.0


    New theme for Enoch/Chameleon included in the latest release of Pandora 2
  19. I have been trying to get iMessage working on my otherwise perfect Hackontosh. The problem is i cannot switch to clover due to exception 64 error and it's due to my motherboard which is super old it is a Asrock-VGS3-FX and I use a Amd Athlon x2 Black Edition OverClocked to Quad Core with 750 ti Graphics, Now with my specs out for the way I have tried file NVRAM I placed the kext in my Extra Folder and put the modules folder in the Extra Folder but with the filenvram.dylb in the extra folder the system will not boot and also had issues with yosemite I had filenvram in my extra folder when I was running yosemite but than I update to el captain but on yosemite I had no idea how to use file nvram and how to get iMessage working,
  20. Hello folks! GUIDE UPDATED - Added support for 10.10 XCPM kernel First of all it is very good that we have an updated version of Chameleon, so please take this most updated version right here in the official thread: http://www.insanelym...ameleon-22-svn/ Since 10.7.4 for CPUs and SandyBridger IvyBridger P and C States - that are responsible for the proper functioning of energy - are no longer provided by Chameleon, in others words, only activate GeneratePStates and GenerateCStates doesn't work any more. A quick exit is to use the kext NullCPUPowermanagement, but I don't recommend continued use of this kext because it disables AppleIntelCPUPowermanagement kext which is responsible for power management The most viable and recommended solution that will give to you a good power management is the creation of a SSDT which will contain all P-States and C-States. Step-by-Step Creating the SSDT Create your SSDT based on the script Pike R. Alpha Run these commands in terminal curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ssdtPRGen.sh ./ssdtPRGen.sh After you run it you need to put the Maximum Frequency and Maximum TDP of your CPU ... see these information about your CPU in here: http://ark.intel.com/ This is an example of one i7 2600 that has 3800MHz(3.8 Ghz) of maximum frequency and 95 of TDP sudo ./ssdtPRGen.sh 3800 95 Place the SSDT in Extra folder and rename ssdt_pr for SSDT Note: Some CPUs are auto-detected by the script, the script just now detects the maximum frequency and TDP, so if simply after running the first command you are prompted to save the SSDT in Extra folder(not asking to enter your max frequenc. and TDP as the guide teach),don't worry about it, just to confirm, because the script already detected everything and created the SSDT and the time is already asking to save the file. Patch AppleIntelCPUPowermanagement In older mobos is necessary to patch the kext AICPUPM to enable recording in Bios, otherwise you will get a kernel panic because it can't write to the Bios ... Download the patch: AICPUPMpatch Run in terminal cd ~/Downloads/AICPMPatch Just find and list ... sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement Then give patch in wrmsr to enable recording in Bios sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement --patch After that you need to update the cache sudo touch /System/Library/Extensions Kernel Patch for Haswell CPU(Kernel XCPM) Since version 10.8.5 a new kernel was implemented on OSX, he called XNU kernel(XNU CPU Power Management(xcpm)). This kernel has the power management moved down into it, in past we used AppleIntelCPUPowermanagement kext to control power management and some Bios were lockeds, in others words, were not allowed to write information on it, so the patch was created for kext AICPUPM to solve this problem (see above how to patch the kext AICPUPM). But with the power management moved down into the kernel(XNU kernel) AICPUPM the kext isn't loaded and so the same mistake that we were having in the past with AICPUPM kext(Kernel Panic)are having now with the XNU kernel in some models CPU haswell(mainly in portable models, some Desktop models doesn't need patch) To solve this problem it is necessary to patch the kernel. For 10.10 you need Open the terminal and type: cd /Volumes/Name of your HDD/System/Library/Kernels/ Note that in 10.10 kernel directory was changed. Copy this perl code is for 10.10 version, put line by line sudo perl -pi -e 's|\xe2\x00\x00\x00\x02\x00\x00\x00|\x00\x00\x00\x00\x02\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x4c\x00\x00\x00|\x00\x00\x00\x00\x4c\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x90\x01\x00\x00|\x00\x00\x00\x00\x90\x01\x00\x00|g' kernel For 10.9.x and 10.8.5 you need run this command in terminal: cd /Volumes/Name of your HDD/ Now copy this perl code if you use version 10.9.x sudo perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05..\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel or that other perl code if you use version 10.8.5 sudo perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g' mach_kernel Finally update the cache sudo touch /System/Library/Extensions Ready! XCPM patched kernel and is working perfectly on your CPU haswell Note1: XCPM only works in Ivy Bridge and Haswell CPUs, and the CPUs Ivy Bridger use by default the power management given by AICPUPM kext, to use the power management provided by the kernel XCPM you must enable this flag(Chameleon)/argument(Clover): -xcpm Haswell CPUs use XCPM management by default and doesn't change.The management XCPM not support CPUs Sandy Bridger, so who uses SB can stay quiet about it. Note2: Even Patching the kernel XCPM, you will need to patch the kext AICPUPM if your BIOS is locked for writing. Note3: If you have no problem with KP, it isn't necessary to patch the kernel, but in some cases, helped to patch the kernel to add some energy states. Note4: Clover bootloader already has this patched built-in, you just need edit config.plist to enableir it <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> </dict> So, if you enable it in Clover isn't necessary patch kernel, because Clover will make this for you Final adjustments To make the Chameleon recognize your SSDT, enable DropSSDT in org.chameleon <key>DropSSDT</key> <string>Yes</string> Don't install the NullCPUPM and don't enable P and C States in org.chameleon ... Don't forget to create a DSDT in future to help the power management Note: For those who are having difficulty with power management ... take a look to see if the kexts: X86PlatformPlugin, ACPI_SMC_PlatformPlugin, AppleLPC are loaded, type kextstat the terminal to see ... Good luck to all who try this guide, I just put it all together in a single tutorial to facilitate the understanding of power management in Sandy and Ivy Bridger, but all credits go to the respective owners of the wonderful tools that enable power management in our CPUs Credit: Pike R. Alpha flaked RevoGirl ReHabMan: http://www.insanelymac.com/forum/topic/302376-guide-patching-the-kernel-for-haswell-cpus-xcpm-early-reboot/
  21. Hello guys.. I'm doing another attempt to install Chameleon boot loader on my computer. Here the situation: I have just one hard disk with Linux Mint, Linux Swap Area, Windows 8, Data Partition and OS X Mavericks. I've installed Mavericks using Niresh's. Now my problem is: How can I install Chameleon on my computer? Because if i use the Chameleon Wizard it give me boot0: error when I turn on my computer. I've read that the problem is due to my hard disk that have 4096 byte sectors and so the installer of chameleon cannot write in. So i've followed a guide that suggested me these following steps: 1. Install using [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] 2. Boot new installation using [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] created USB. 3. Run [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] and install as normal 4. Reboot system back into OS X installer. 5. Run Disk Utility and unmount the drive you installed OS Lion on. 6. Launch Terminal and execute the following command: Code:dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2 7. Exit Terminal 8. Reboot Normally Of course, because I've Maverick already installed, i've started this guide from point 4. I entered the shell, I tried the command but it says me "No such file or directory". So, I rebooted on my Mavericks and went to check the usr folder. That file doesn't exist. So, my problem is: is this because I've installed Mavericks using Niresh and no [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]? Is there a way to fix this? Is there any other way to install Chameleon boot loader on my hard disk with 4k sectors without reinstall Mavericks again? ​Thanks all for help.
  22. Hi everyone, I decided to install Mac OS X 10.9 Marvericks on my Dell Latitude E6230 laptop. Dell Latitude E6230 information (generated by CPU-Z): ==================================== CPU: Intel Core i5 3320M 2.60GHz (Ivy Bridge) Mainboard: Dell 00314G (Chipset: Intel Ivy Bridge) Memory: DDR3 4GB Graphics: Intel HD Graphics 4000 (memory size 1792MB) ==================================== My problem: ==================================== Problem ONE ([url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] Method): I followed the steps presented by http://www.tonymacx86.com/374-unibea...-based-pc.html I chose "boot from USB-HDD" , enter the USB. A few seconds later, I saw the startup screen. [sCREENSHOT 1 ATTACHED] After several minutes passed, the PC showed a BLACK SCREEN. I had to reboot it by pressing the power button.... [i even tried -x & GraphicsEnabler=No, but still doesn't work!] ===================================== Problem TWO (Windows Chameleon 2.2 svn 2266 Method): I used the Chameleon to help install mac os on my Dell laptop. (I succeed in installing mavericks on my Acer laptop by using Chameleon 2.2) After reading all the HPS+ files, the laptop became like this....Seemed like a fatal crash..(I don't know what the code on the screen exactly means) [sCREENSHOT 2 & 3 ATTACHED] ===================================== Both of the mainstream Hackintosh methods didn't work, I feel so hopeless..... Can anyone help me ? MANY THANKS! Hope somebody can help me!
  23. Bansaku

    UseAtiRom Chameleon EFI help!

    I recently installed Chameleon onto my HD's EFI partition and it works great except for I can not get UseAtiRom=y to work; no matter what I try it keeps loading from the legacy space. 1002_679a.rom (both extracted by myself as well as I tried d/l from TechPowerUp) resides in the Extras folder on the EFI partition. Using UseAtiRom=y with GraphicsEnabler=y halts the boot as usual, AtiConfig=Aji/Futomaki does nothing. What am I missing?
  24. I can't log into FaceTime or the Appstore in 10.11.1 with Chameleon Bootloader. All the fixes for it seem to be for Clover, and Clover won't work with my Motherboard( Zotac GF9300 ). Does anyone know how to fix this? Also is there a Patched Real Time Clock .kext for 10.11.1? Is there a Shutdown/Reboot fix for El Capitan? Thanks.
  25. Hey Guys, I wanted to write a short guide on how to chainload Chameleon or legacy Clover from the Windows Bootloader using EasyBCD/Grub4DOS. This maybe useful for people who are reluctant to touch their legacy Windows installation and want to keep their OSX installed and separate on a new GPT Hard Disk. A common scenario would be to have an existing legacy install of Windows on a MBR partitoned hard drive. After installing OSX and then a bootloader (Chameleon or legacy Clover) on a separate GUID hard drive, you can still give the original Windows drive first boot priority in the BIOS and chainload to Chameleon/Clover from the Windows Boot Manager when required. Eg Below is the current disk/partition arrangement for my legacy BIOS (Non UEFI) desktop rig: Gigabyte P55aUD3/Intel i5 750/AMD Radeon HD 5770 diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *120.0 GB disk0 1: Windows_NTFS System Reserved 104.9 MB disk0s1 2: Windows_NTFS WIN7_X64SSD 119.9 GB disk0s2 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk1 1: EFI EFI 209.7 MB disk1s1 2: Microsoft Basic Data TSH_DATA 1.7 TB disk1s2 3: Apple_HFS Macintosh HD 133.6 GB disk1s3 4: Microsoft Reserved 133.2 MB disk1s4 5: Apple_Boot Recovery HD 650.0 MB disk1s5 6: Microsoft Basic Data WINDOWS 134.1 GB disk1s6 Windows 7 X64 is installed in legacy mode on an MBR 120GB SSD booted by the Windows Bootloader. OSX Yosemite and Windows 7 X64 are installed in UEFI mode and booted by legacy CloverEFI on the 2TB GPT Hard Disk. The SSD (and therefore the Windows Boot Manager) has first priority in the BIOS but I can also choose the GPT Hard Drive by pressing F12 during the BIOS post to boot Yosemite and UEFI Windows via Clover. Procedure Requirements 1. Existing install of legacy Windows on a MBR partitioned hard drive 2. OSX installed on a separate hard drive booted with Chameleon or legacy Clover 3. EasyBCD 2.2 Install Grub4DOS to enable chain loading 1. Open EasyBCD 2.2 and click on the BCD Backup/Repair button to save the current boot configuration data to somewhere safe. 2. Click the Add New Entry button and select the NeoGrub tab in the Operating Systems section a. Click the Install Button b. Click the Configure Button 3. Notepad should open Grub4DOS's menu.lst file (located in C:\NST\menu.lst) and you can now add the following lines to chainload the OSX bootloader from the MBR of the second hard drive.... chainloader (hd1)+1 rootnoverify (hd1) boot Notes: For GRUB, (hd0) represents the first disk, (hd1) the second disk, (hd2) the third etc. So chainloader (hd1) is used to boot the MBR of the second hard disk. The "+" symbol is used to specify a blocklist - in this case +1 is the first sector of the device (hd1). To chainload to a Partition Boot Record (PBR) on the second hard drive, a similar entry could be used eg to boot to the first partition on the second hard drive... root (hd1,0) chainloader (hd1,0)+1 boot 4. Close Notepad. 5. Click the Edit Boot Menu button to Rename your new menu entry from the default "NeoGrub Bootloader" eg I've named mine "Clover" since I use Clover but you can name it "Chameleon" if you use Chameleon. You can also move an entry up/down, set a timeout etc. 6. Finally, click Save Settings, exit EasyBCD and reboot the computer. Select Clover/Chameleon from the Windows Boot Manager to chainload Clover/Chameleon and boot into OSX....