Jump to content
19 posts in this topic

Recommended Posts

Its the Graphics Issue.

The next thing to be loaded after Bluetooth is Graphics.

Which Intel HD Graphics do u have ? ( Other than AMD Radeon). Should be HD 4600 I think ? Right ?

First try to disable your AMD Radeon Graphics in BIOS, and then boot.

well, if you not know where is installed the kexts in the system MAC OS X , you have a big problem, try read a bit, try ask to Dr.Google , him can help you, then when you know where it is installed and you delete this kext, try the boot flag to boot, if have other problem, post here in your topic.

Which OS you were using before the Update ? Mountain Lion or Mavericks ?

And which bootloader you are using ? Chameleon, Chimera or Clover ?

 

For patching the mach_kernel for Haswell, you can refer to this guide by Rehabman here 

http://www.insanelymac.com/forum/topic/293503-haswell-early-reboot-mavericks-locked-msrs-and-hp-envy-15-j063cl-i7-4700mq/

But I dont think so that patching the kernel is an issue because, I also have Haswell and in my case, the system immediately restarted after booting. This patch solved the problem for me. But in your case it is totally Graphics issue. Have you tried the IG-Platform IDS ?

 

I was also facing this stuck at bluetoothe issue when I was installing Mavericks. My Thread is posted here

I was using 10.9.2 before security update 2014 -002 but after it i couldnt boot in normal mode.I am using chameleon.
After all i moved in beta 10.9.3 cause my gpu wasnt working and in 9.3 it does .but i still cant boot in normal mode
No i havent try the IG Platform IDS.

Shall i use this method to patch my kernel?

this is a problem with the kext TyMCEDriver.kext, delete this kext from USBInstaller  boot with -f -v -x GraphicsEnabler=No npci=0x2000   and if you CPU is a Haswell you need a pached kernel for this CPU

deleted the kext but still can't boot in normal mode except safe  mode..

Hmm. in that case, may be you can. May be the Security Update replaced the mach_kernel. May be. 

Create a backup of mach_kernel and then try to patch.

 

As a General Practice, before doing any update etc, I always create a Disk Image of Partition, so that if anything goes wrong then I can revert back. You can use Acronis, or may be R-Drive Image etc. 

 

Its wuite weird that you didnt had to use the IG Platform IDs. Out of the 15 possible values, there were only 2 values that worked in my case :-O

  • 1 month later...

when facing graphic issue, try boot in single user, rename or move all amd graphic kext , i prefer to rename the extension only.

example to rename extension for your amd gfx :

AMD7000Controller.kext rename to AMD7000Controller.next (u can change whatever u like for an extension)

 

so the command u should type something like this :

mv AMD70*.kext AMD7000Controller.next

 

and try rename all kext related to amd 7xxx like :

AMDRadeonX4000.kext

 

and if u can log in to the desktop, u can find any solution to make your gfx works.

×
×
  • Create New...