Jump to content

[Guide] AIO Guides For Hackintosh


  • Please log in to reply
266 replies to this topic

#21
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Clover Config: Tweaking Clover menu entries

 
OS entries on Clover menu screen can be hidden, renamed by editing config.plist.
 
Step 1: Get the entry partition’s UUID by opening boot.log in /Library/Logs/CloverEFI/ ( this file is created only if you selected Install RC Scripts to target partitions upon installing Clover ). Locate Volume section. Compare existing partitions on your HDD/SSD with the log by typing this in Terminal:

diskutil list

Or simply remember the line “Boot Windows from Legacy HD3”, “Boot OS X from Macintosh” on the Clover menu screen to find the entry partition’s name. Get its UUID then save it on a text file
 

rZHfRF5.png

Step 2: Open Clover Configurator, import the current config.plist, switch to tab GUI.

If you want to hide all Legacy entries ( Boot … from Legacy HD… ), select Custom in Scan, then uncheck Legacy.

To edit entries manually, select the + button in Custom Entries (for UEFI entries like Windows UEFI, Linux UEFI, OS X ) or Custom Legacy ( for Legacy entries like Windows Legacy, Linux Legacy,…):

  • Volume: enter the entry partition’s UUID in step 1
  • Path: if the partition contains multiple entries, type the correct path to it ( separate by “\” )
  • Title/Full Title: check it to switch to Full Title, type the desired name which will shown on Clover menu screen.
  • Hidden: Hide the entry from Clover menu screen
  • Disabled: Completely remove this entry
  • InjectKexts: Automatically inject kexts in /EFI/Clover/kexts/ to this entry
  • NoCache: Don’t use cache for this entry
  • Type: Identify the type of OS

Note:

  • Entry partition’s UUID must be identified correctly. For example, Windows UEFI and Linux UEFI’s boot entries is stored in EFI partition ( because Windows’s bootmgfw.efi is located in \EFI\Microsoft\Boot, not in Windows partition, the same applies to Linux ). OS X boot entry is stored in \System\Library\CoreServices\boot.efi ).
  • If the Volume check mark is blank then Clover will identify the entry base on Type, and vice versa.

11096021326_2a9d6a965f_o.jpg



#22
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Everything you need to know about NVRAM

 

What is NVRAM ?

 

NVRAM is not popular to PC users but it is very familiar to Mac users. NVRAM is a type of RAM that retains data after the host device's power is turned off. ( in contrast to RAM ). NVRAM is used to store values like: brightness, volume, computer name, Find My Mac’s ID, etc… In Windows and Linux these values aren’t stored in NVRAM but on the HDD, as most PCs don’t have NVRAM. OS X utilizes NVRAM to run many services like iMessage, FaceTime, boot device, etc…

 

NVRAM on PC

 

NVRAM, like UEFI, is implemented many new PC models, and many OSes like Windows and Linux start using it. For example, Windows in UEFI mode uses NVRAM to check if Secure Boot is enabled or not.

 

But everything does not work smoothly in the world of PC. In the beginning of the migration from Legacy BIOS to UEFI, many PCs are badly damaged due to unstable NVRAM. Notably many Samsung PCs got bricked due to bad NVRAM writing, in which CMOS reset is the only option to revive it or worse, it can sometimes corrupt firmware. Other OEMs starts to take things carefully and in new BIOS update, they can turn off NVRAM if any possible dangers is exposed.

 

How to test NVRAM ?

 

Open Terminal in OS X, type:

sudo nvram MyVar=TestValue

Then type this to show the current NVRAM:

nvram -p

You will see:

MyVar   TestValue

After rebooting, type nvram –p in Terminal and if you can still see the previous result then your NVRAM is working

 

NVRAM and Hackintosh

 

1/ Chameleon

 

Due to this bootloader’s limited implementation, Chameleon won’t keep all system’s efi-runtime before booting OS X, which means NVRAM won’t work even even if you already have native NVRAM enabled.

 

To solve the matter, the module “FileNVRAM” is created to emulate NVRAM for Chameleon. By integrating a NVRAM emulating module into OS X’s core, all features required working NVRAM will work normally. This module will loads the nvram file from disk early into memory so Filenvram has it before OS X is up and running, It also injects a kext in to OS X. The kext will handle the NVRAM API that OS X expects. This kext does legacy translation as well as writing the nvram to /Extra/nvramxxxxxxxx.plist when nvram is changed.

 

2/ Clover UEFI

 

Unlike Chameleon, Clover UEFI is more transparent for UEFI system, so it will use the system’s Native NVRAM (if exist).

 

To see if you have native NVRAM or not, go to /EFI/Clover/Drivers64UEFI/ and delete EmuVariableUEFI-64.efi, then restart. Follow the NVRAM testing procedure above, if it’s still working then you have native NVRAM support and you don't need to use EmuVariableUEFI-64.efi; if not then put back EmuVariableUEFI-64.efi to use NVRAM.

 

EmuVariableUEFI-64.efi works by loading the newest nvram.plist from HFS+/FAT32 partitions and emulate NVRAM for OS X. But this driver CAN NOT save NVRAM  into the nvram.plist. Therefore, we need some solution to save nvram.plist at shutdown.

 

Install RC Script

 

You can install this by select "Install RC Script to target partition" in Clover <=2711

 

This is how Clover Installer saved NVRAM (up to Clover 2711).  It utilizes OS X’s feature of loading /etc/rc.local when booting up, and /etc/rc.shutdown.local when shutting down, Clover Installer added execute scripts to save log files into rc.local and save nvram.plist into rc.shutdown.local.

 

The truth is RC Script has been deprecated since the day of Leopard (10.5) but for some reasons it still survives till Mavericks (10.9). Unfortunately it is gone completely in Yosemite ( 10.10 ), so Clover users using RC Script in old installer now won’t be able to keep NVRAM after restarting, due to nvram.plist saving scripts won’t run at shutting down.

 

Use LoginHook/LogoutHook

 

To temporarily replace RC Scripts, some users use LoginHook/LogoutHook to replace rc.local/ rc.shutdown.local. LoginHook command will be run when logging in, and LogoutHook will run when logging out. This method still has some problems. The scripts will run only when login/logout, not starting/shutting down. This method is also deprecated since Tiger ( 10.4 ), so it will be a matter of time until it’s completely disappears.

 

Launchd

 

You can install this by select "Install RC Script to target partition" in Clover > 2711

 

This is the official method that Apple recommends to run scripts when starting/shutting down, and Clover revisions since 2712 has implemented it for better OS X support.



#23
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Issues while booting into OS X

 
Graphics related problem
 
This occurs when your verbose booting screen shows that things are stuck at Bluetooth or Network or loading partitions.  To fix this temporarily:
 
Revise config/bootflag:
 
Wrong bootflag ( for Chameleon ) or bad config.plist ( for Clover ) can cause graphics issues, you should check it again
 
Boot in Safe Mode
 
For Chameleon: Add –x to your bootflag
For Clover: Hit Spacebar and choose Boot to safe mode
 
Remove graphics kexts:
 
You can temporarily remove graphics kexts in order to boot. If you have Windows or Linux, go to /System/Library/Extensions and move these kexts to another folder:
AMD ( for AMD only or Intel HD + AMD systems ): AMD*.kext
Nvidia ( for Nvidia only or Intel HD + Nvidia systems ): NVDA.kext, Geforce*.kext
Intel ( if above methods don’t work ): AppleIntelHD*.kext
 
If you don’t have other OS, boot into the installer or the Recovery partition, open Terminal and type:
 

cd /Volumes/
ls ( list of available partitions on the system )
cd “OS X partition name”
mkdir /Backup
cp –rf AMD* /Backup
rm –rf AMD* ( if you want to delete AMD kexts )
cp –rf NVDA* /Backup
rm –rf NVDA * ( if you want to delete NVDA kexts )
cp –rf Geforce* /Backup
rm –rf Geforce * ( if you want to delete Geforce kexts )
cp –rf AppleIntelHD * /Backup
rm –rf AppleIntelHD * ( if you want to delete AppleIntelHD kexts )

 
After successfully booting into OS X, you should patch your DSDT to inject the correct information about your GPU, or disable the dedicated GPU by DSDT/SSDT for AMD Switchable Graphics/Nvidia Optimus to prevent this from happening again.
 
Installing the kexts back to see if you have working graphics.
 
Still waiting for root device:
 
This happens because:

  • Using a 3.0 USB port to boot into the installer without having GenericUSBXHCI.kext in /Extra/Extensions or /EFI/Clover/kexts of the USB
  • Sata Mode isn’t set to AHCI in BIOS or is in RAID Mode that Apple doesn’t support

To fix this:

  • Add GenericUSBXHCI.kext to /Extra Extensions or /EFI/Clover/kexts of the USB
  • Add AHCIInjector.kext for systems using RAID Mode
  • Set Sata Mode to AHCI
  • If using Clover, you can try creating a config.plist with “still waiting for root device“ patch and use it

SMCReadKeyActionError:
 
This happens because vt-d is enable in BIOS



dscn20098ona2qd9y5_zps0fe8a64c.jpg

To fix this, do one of following:

  • Disable vt-d in BIOS
  • Boot with dart=0 flag
  • Set Drop DMAR table in Clover config.plist

PState Stepper Error on some Ivy Bridge CPUs:
 
If you follow the speedstep guide (link) and got this error, this happens because of bad ssdt for the cpu. To fix this:

  • Delete the current ssdt.aml
  • Create a Ivy or Haswell SMBios
  • Install vanilla AppleACPIPlatforms.kext
  • Generate SSDT with ssdtPrGen ( or can be found in HVT, which is always the latest version )
  • Copy vanilla mach_kernel to the root of the OS X partition, use HVT to patch it ( for Chameleon )or set KernelPM in config.plist ( for Clover )
  • Add –xcpm to your bootflag when booting ( org.chameleon.boot.plist for Chameleon/config.plist for Clover )


#24
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Touchpad/Keyboard won’t work after using Hackintosh for a while ( Laptop-exclusive )

 

After some time, your touchpad and keyboard may malfunction: not working, laggy cursor when moving, a few keys don’t work even though you have installed the right kext and using them just fine earlier. This often related to EC ( Embedded Controller )

 

EC is a device which controls the touchpad/keyboard and some other devices on the mainboard. Sometimes EC may malfunctions due to many reasons ( electric shock, bad dsdt, etc… ). You have to force EC to reset itself:

  • Turn off your computer
  • Unplug your computer and remove the battery
  • Press Power button for about 30 seconds
  • Put the battery back and use it normally

Special method for users with Elan touchpad: hit Escape button when your keyboard isn’t working



#25
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

DSDT/SSDT: Everything you need to know about SSDT

 
As mention in the basic knowledge guide about DSDT/SSDT, SSDT ( Secondary System Description Table ) are sub-tables which describe additional devices. By using SSDTs OEMs can manage DSDT better, and so SSDT can be shared between similar systems. SSDTs that comes with the system usually contain these information ( red means scope/device can be found in SSDT ):

  • SATA management: \_SB.PCI0.SATA
  • Sensor management: PTID
  • CPU management: \_PR.CPU
  • Intel HD Graphics management: PCI0.GFX0 or PCI0.VID
  • Dedicated GPU management: various names like GFX0, PEGP or DGFX, etc…
  • Features like Optimus, Switchable Graphics,..

To edit these tables, make sure to dump and decompile all DSDT/SSDT, edit the dsl file then save it as aml. To load the edited one, rename it by order: SSDT.aml, SSDT-1.aml, SSDT-2.aml,… and put them in the bootloader’s directory ( the same as DSDT.aml )
 
Drop OEM SSDT

 

This feature was created due to the fact that system’s original SSDTs that manage CPU are useless in OS X, which force users to create CPU management SSDTs which are optimized for OS X. By loading both OS X’s optimized SSDTs and original SSDTs, they can conflict each other, cause unstable CPU loading.
 
Drop OEM SSDT is made to wipe (drop) original SSDTs in BIOS/UEFI to avoid conflicts. Even though other SSDTs are also dropped, but these tables aren’t always important ( most systems can run with DropSSDT=True )
 
CPU management SSDTs

 

Bootloaders like Chameleon, Clover can create a SSDT compatible with OS X to control the CPU by setting GeneratePState/GenerateCState=True.
ssdtPrGen script made by Pike R. Alpha is better way to create CPU SSDTs for OS X, and will always be up-to-date. You can create your SSDT.aml using ssdtPrGen by selecting Tools > SSDT Generator in HVT
 
Note:

  • ssdtPrGen script only supports 2nd/3rd/4th Core I and Xeon Processor. Other CPUs have to use the bootloader’s Generate features.
  • Do not use both SSDT.aml and bootloader’s Generate features, it can cause unknown issues.
  • It is recommended to use Drop OEM SSDT features to avoid conflicts between SSDTs

Intel HD Graphics management SSDT ( laptop-exclusive )

 

Most Intel iGPUs is defined in DSDT, but in some cases ( especially Haswell laptops ), the iGPU is managed in SSDT.
 
To check whether DSDT or SSDT is managing your iGPU, find these in the tables:

Device (GFX0)
Device (VID)
Name (_ADR, 0x00020000)

 They are inside PCI0 scope.
For example, this system’s HD4400 is managed by ssdt7.dsl

PXUJYMe.png


In this case, for brightness fix you have to compile and load that ssdt. And if you apply a patch that rename GFX0 to IGPU, you have to do it in all related DSDT/SSDT.
 
Dedicated GPU management SSDT ( laptop-exclusive )
By default they are named DGFX, PEGP and have _OFF, _ON methods, for example:

nYbqiRq.png



#26
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

DSDT/SSDT: Disable dedicated GPU to extend battery life ( laptop-exclusive )



Only applied to laptops with both dedicated GPU (Nvidia/AMD) and Intel HD Graphics, has Nvidia Optimus Technology/AMD Switchable Graphics, and dedicated GPU can’t be turned off in BIOS

Step 1: Dump and decompile original DSDT/SSDT into dsl files

Step 2: Identify the DSDT/SSDT contains Intel HD Graphics (if exist) and dedicated GPU

Step 3: If you rename Intel HD GFX0 to IGPU, do it on all related DSDT/SSDT!

Step 4: Find the dedicated GPU’s _INI method, add _OFF ( ) at the end of the method

liRlcrG.png

 

Press Compile to check for error. If you have error "Object is not accessible from this scope (_OFF)", the _OFF method is not included in the same SSDT. You have to link it by adding this to SSDT:

External(\_SB_.PCI0.RP05.PEGP._OFF, MethodObj)

Note that you have to change the path to your External graphics device \_SB_.PCI0.RP05.PEGP to suit your system.

 

Step 5: Save all SSDTs related to iGPU (if exist) and dedicated GPU as aml, put it in the bootloader’s directory ( name it as SSDT.aml, SSDT-1.aml, SSDT-2.aml, etc… )

Step 6: Reboot and go to System Information, select Graphics/Display. If only Intel HD Graphics shows up and no Display/Nvidia/AMD related names are there then you have successfully disable the dedicated GPU.



#27
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

DSDT/SSDT: Brightness fix for Intel HD3000/4000/4400/4600 (Laptop exclusive)

 
Requirement:

Open DSDT.dsl or SSDT*.aml which contains the Intel HD Graphics, select Patch > go to 2.10 Brightness Fix (HD3000/4000) or 2.11 Brightness Fix (Haswell) to your choice, hit Apply
 

11649398415_27f5ae41dc_o.png

 
 
Hit Compile to check if there are errors or not, the most common error is Scope not found, due to you haven’t renamed all iGPU’s GFX0 device, try renaming all Intel HD's GFX0 to IGPU (do not mistake for dedicated graphics GFX0)
 
Another cause for this problem is that the Intel HD GFX0 device is not in DSDT, but in other SSDT* instead ( most Haswell laptops ). You need to find the SSDT*.dsl which contains GFX0 devices and redo the steps above.
 
Compile it to DSDT.aml or SSDT-*.aml (* start with 1), put it in the bootloader’s directory
 
Install Rehabman’s ACPIBacklight: https://bitbucket.or...light/downloads or use HVT to install it
 
REMEMBER that you have to rename Intel HD GFX0, VID->IGPU in all DSDT/SSDT to make it work.
 
Note: ACPIBacklight use nvram to save brightness values when shutting down, so you need working nvram to save them after restarting:

  • Chameleon: Use FileNVRAM module
  • Clover UEFI: When installing the bootloader select EmuVariableUEFI-64.efi and Install RC Script on target volume


#28
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Clover Config: Convert your patched AppleHDA to Clover patching-on-the-fly


Requirement:
- Get a working sound with patched AppleHDA

The guide is based on piker's discovery, and will help you turn from a patched AppleHDA to Clover patching-on-the-fly.

Step 1: Download bcc9's script modified by RehabMan here, decompress it to desktop.
 
 Go to terminal, type these commands:

cd ~/Desktop/patch-hda
./patch-hda.pl -x 111d7605

REMEMBER to change 111d7605 to your audio codec id.
 
The patching entry will be output:


HR8kPCj.png

Open your config.plist by TextEdit, copy the generated scripts to KernelAndKextPatches > KextsToPatch section:

hWtsISD.png

Save the config.plist
 
Step 2: Download DummyHDA here. Copy LayoutX.xml.zlib và Platforms.xml.zlib from AppleHDA.kext/Contents/Resources/ (this is the working AppleHDA) to DummyHDA.kext/Contents/Resources/
 
Step 3: Open Info.plist in AppleHDA.kext/Contents/Plugins/AppleHDAHardwareConfigDriver.kext/Contents/ (this is the working AppleHDA). Copy all the value here:

IOKitPersonalities/HDA Hardware Config Resource/HDAConfigDefault

to Info.plist in DummyHDA.kext/Contents/:

IOKitPersonalities/HDA Hardware Config Resource/HDAConfigDefault

ThIaDqc.png

save the Info.plist
 
Step 4: Reinstall vanilla AppleHDA and DummyHDA to S/L/E by Kext Wizard, rebuild cache/repair permission then restart. You may need to restart once more to get the sound.



#29
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Installing Yosemite using Clover (UEFI)



You need a Yosemite installer for Mac, it can be downloaded from Appstore for free. Note that with Haswell CPUs you need a 10.9 installer or above. This guide is done under OS X, if you don’t own a Mac then you can always create a virtual machine.

Create a Yosemite USB Installer

Step 1: You need a 8GB USB stick, format it with Disk Utility with the following options:

  • Partition: 2 partitions
  • Partition 1: name it Clover, Format MS-DOS (FAT), size larger than 300MB
  • Partition 2: name it MacUSB, Format Mac OS Extended ( Journaled ), size larger than 6.5GB
  • Options: Master Boot Record (MBR)
  • Hit Apply

12475004833_baec2d51ba_o.jpg


Step 2: Download this Clover.zip, unzip and copy the EFI folder to the root of the CLOVER partition. Use Hackintosh Vietnam Tool to create the suitable config.plist for your PC:
- CPU: Select your CPU
- Graphics: Select your graphics
- SSDT: Generate

- Bootflag: kext-dev-mode=1
Install to current HDD, then copy the generated config.plist on the desktop IN YOUR HDD to the folder EFI\Clover of the CLOVER partition.



12475039433_50ef8d883b_o.jpg


At this point you have 2 choices of creating the installer

Choice 1 (easy guide, but can result in blank screen after boot)

Step 3: Download OS X Yosemite from the Appstore, check if the “Install OS X Yosemite.app” is in the folder Application. Open Terminal and run this command ( note that Untitled is a HFS+ partition )

sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/MacUSB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction

Choice 2 (manual method)
Step 3: - Right click to Yosemite Install app > Show Package Contents > Contents > Shared Support, open InstallESD.dmg.
- Open OS X Install ESD partition, open BaseSystem.dmg (hidden file)
- Use Disk Utility to clone OS X Base System to MacUSB partition.
Ub9sEsy.png
- Go to System/Installation of USB and delete the alias “Packages”, then go to “OS X Install ESD” partition, copy the “Packages” to the folder System/Installation of your USB
- Copy BaseSystem.dmg and BaseSystem.chunklist (hidden files) from OS X Install ESD to OS X Base System (on your USB)

Installing Yosemite

Step 1: Boot from the USB installer, select “Boot OS X Install from Install OS X Yosemite”

Step 2: If the config.plist is correct, you should arrive at the installation windows. Hit Spacebar if any notifications about bluetooth keyboard/mouse appears. Select menu Utilities, select Disk Utility

Step 3: Select the partition you want to install OS X to, switch to Erase tab, do the following options:


  • Format: Mac OS Extended (Journaled)
  • Name: Pick anything you want
  • Hit Erase

Step 4: After the formatting process is done, close Disk Utility, hit Continue, hit Agree. Select the formatted partition then hit Install
Note
- It will automatically restart and you will have to reboot into the installer again in order to begin the REAL installation process.

Step 5: After installation process is done, reboot into the USB Installer and boot into your newly created OS X partition.



#30
midi ッ

midi ッ

    YYEEEEEEP .... just try it ...

  • Members
  • PipPipPipPipPip
  • 270 posts
  • Gender:Male

lol hold this



#31
Ahmed_shiko

Ahmed_shiko

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 129 posts
  • Gender:Male
  • Location:EGYPT

problem p- state stepper error 18 at step 35 in context 2 on cpu 0 

 

mydsdt-ssd thttps://www.dropbox.com/s/2ayc1d0v8qlkuur/My%20dsdt%20-ssdt.rar



#32
vusun123

vusun123

    Watching Breaking Bad ...

  • Members
  • PipPipPipPip
  • 233 posts
  • Gender:Male

Based on the CPU in your signature, I guess you are using both GeneratePState / GenerateCState with your SSDT and didn't DropSSDT ?



#33
midi ッ

midi ッ

    YYEEEEEEP .... just try it ...

  • Members
  • PipPipPipPipPip
  • 270 posts
  • Gender:Male

 

DSDT/SSDT: Basic knowledge

...

Note: If you have multiple SSDT that is needed to be loaded, rename them as: SSDT.aml, SSDT-1.aml, SSDT-2.aml, … and so on.

 

I have 6 SSDTs, if I rename them like that, they will all load @ boot ?



#34
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Yes, but if you want to load all OEM ssdt, just set DropOEM SSDT = false. Read here:

http://www.insanelym...-2#entry2030039



#35
AsusGuy

AsusGuy

    InsanelyMac Protégé

  • Members
  • Pip
  • 39 posts

Hello,

 

Before I go on, here is my spec:

- Asus Touch Laptop

- Intel i5 4th gen

- Intel 4400 HD

- 6GB Ram

- 750GB HDD

 

I put config.plist in my EFI Clover (EFI/Clover)

 

When I boot up, and select Boot Mac OS X Base System, it just restarts (I even tried the bootflags as well, -v and -x).

 

Any help would be great.

 

Thanks.



#36
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male

Hello,
 
Before I go on, here is my spec:
- Asus Touch Laptop
- Intel i5 4th gen
- Intel 4400 HD
- 6GB Ram
- 750GB HDD
 
I put config.plist in my EFI Clover (EFI/Clover)
 
When I boot up, and select Boot Mac OS X Base System, it just restarts (I even tried the bootflags as well, -v and -x).
 
Any help would be great.
 
Thanks.


Post your config.plist.

#37
AsusGuy

AsusGuy

    InsanelyMac Protégé

  • Members
  • Pip
  • 39 posts

Post your config.plist.

 

Config.plist:

Since I cannot attach it, I paste them in pastebin.

http://pastebin.com/n6M1eGea

 

Here is the fully laptop spec:

http://www.newegg.co...N82E16834231549



#38
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male
You have Haswell Mobile CPU, not IvyBridge Mobile CPU. What did you select when you generate config.plist?

#39
AsusGuy

AsusGuy

    InsanelyMac Protégé

  • Members
  • Pip
  • 39 posts

You have Haswell Mobile CPU, not IvyBridge Mobile CPU. What did you select when you generate config.plist?

I selected 

- CPU: IvyBridge Mobile

- SSDT: Generate

- Graphics: HD4400/4600 Mobile

 

Oh okay, gottca. So I change CPU (in hackintosh vietnam tool) to Haswell Mobile?



#40
pokenguyen

pokenguyen

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 459 posts
  • Gender:Male
You are using Haswell, not Ivybridge.





34 user(s) are reading this topic

11 members, 23 guests, 0 anonymous users


© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy