Jump to content
127 posts in this topic

Recommended Posts

Hi there, actually before came across this guide, i was following this instead:  and i have followed the same customization for the clover bootloader as him. I just checked i have the fakesmc in my Yosemite extensions folder. Do you think i should redo and follow yours? Or does his work just as well? Thank you very much.

 

Have you had any luck with this?  I've got the same issue.  Installed OK, rebooted and stuck after the AppleMobileDevice line.  Tried various boot flags.

 

Thanks.

Have you had any luck with this? I've got the same issue. Installed OK, rebooted and stuck after the AppleMobileDevice line. Tried various boot flags.

 

Thanks.

Nope. Same try with several boot flag but to no avail. I've somewhat given up. And resorted to installing mavericks but mavericks I couldn't sign in to App Store nor iBook so I restore back to ml. I think I shall wait for the official release as I currently have no time to do this as I need to study for my final year exam. By the time my final year exam finishes, its fall!! :) but I've tried niresh macpwn method and during installation it failed unlike the youtube guy method which installed successfully and even though it failed when I try to reboot it, during clover bootloader screen, my yosemite drive became a recovery drive and I try to boot it using verbose mode and it shows a different error which is error 0. Sigh. Yosemite is much harder compared to mavericks. I still remembered last year I managed to install mavericks to a core 2 duo without any hiccups!

Have you had any luck with this?  I've got the same issue.  Installed OK, rebooted and stuck after the AppleMobileDevice line.  Tried various boot flags.

 

Thanks.

Have the same problem. I deleted in boot args "kext-dev-mode=1" and insert boot "dart=0"; and boot in single mode. 

Ok, so I got it to boot into install partition. Then after chosing another disk to install Yosemite, the white installtion screen stays there forever even it says the process would take 16 minutes.

Does anyone know what this problem might be?

That happened to me the first time around, I just redid my install USB and started over. Not sure what I did wrong but redoing it fixed it.

Have the same problem. I deleted in boot args "kext-dev-mode=1" and insert boot "dart=0"; and boot in single mode. 

 

So do you have yet working now?  You're saying you're NOT booting with kext-dev-mode=1 but had to add dart=0 and boot into single user mode?   what do you do after that?

Hey AD HD MEDIA I have the same cars did you ever find out how to fix the no support I tried a dsdt from mavericks and everything I could thank of and can't figure it out.

On a side note wow this is not fun installing at all

Hey AD HD MEDIA I have the same cars did you ever find out how to fix the no support I tried a dsdt from mavericks and everything I could thank of and can't figure it out.

On a side note wow this is not fun installing at all

Mine boots like once out of every three or four boots lol other than that, I just get a reboot right where the desktop should come in.

I did find that the graphics kexts were all missing the info.plist file, don't know if you checked that already?

Not missing, hidden. Google Search ShowAllFiles or

Terminal:

defaults write com.apple.finder AppleShowAllFiles TRUE

killall Finder

I'm aware of 'hidden' files and how to show them. My kexts were literally missing the plist files. All of the AMD and NVDA kexts were without them. Wasn't just me, either.

I'm also aware of what a Google search is and how to perform one. Thanks tho.

  • Like 1

If I don't boot with "kext-dev-mode=1" I can boot into Yosemite.  Obviously that presents it's own problems as I can't load my networking kext or others.

 

If I do boot with it set, I get hung up after "AppleMobileDevice  xxxx".  Any idea why?  

 

Booted as is, Yosemite is very unstable for me.. playing around in Terminal or finder (copying/pasting files) often results in reboots.

 

Small steps, I guess.

can't  get hd3000 to work.the first reboot after install,HD3000 appear with only 4mb Vram.my laptop using optimus.i 'v deleted all nvidia and ATI kext.after that.using kext wizard to put AppleIntelSNBGraphicsFB.kext and AppleIntelFramebufferCapri.kext.but got panic after reboot.

If I don't boot with "kext-dev-mode=1" I can boot into Yosemite. Obviously that presents it's own problems as I can't load my networking kext or others.

 

If I do boot with it set, I get hung up after "AppleMobileDevice xxxx". Any idea why?

 

Booted as is, Yosemite is very unstable for me.. playing around in Terminal or finder (copying/pasting files) often results in reboots.

 

Small steps, I guess.

I had the same problem as you then to find out fakesmc was not installed correctly. Very small steps indeed I was using kexts utility and it rebooted in properly and now it fails to load cache. So I guess I have to reinstall but to anyone having this problem be sure you see smc loading in verbose mode or your going to have this problem. And then again this is a beta 1 so there is going to be problems. I had to install this on an external hard drive as when I install it on a hard drive it only sees a recovery partition for some reason. And I did not know hacks partitioned for recovery

After about the third or fourth reinstall, I've finally gotten Clover/Yosemite working really well.  The only main thing I really did different this last time is I didn't ever boot into single user mode, I just dropped all my needed kexts into the 10.10 folder in Clover.  I went into the config.plist and changed inject kext to yes instead of detect.  I also used Clover Configurator to change my SMBIOS to MacPro, since that's what I've always used.  And viola.  I can now actually boot both Yosemite and Mavericks 10.9.3 with no issues.  

 

If it doesn't work the first time, my best advice is to try again.  If you have experience with Clover then you're already one step ahead of me lol

After about the third or fourth reinstall, I've finally gotten Clover/Yosemite working really well. The only main thing I really did different this last time is I didn't ever boot into single user mode, I just dropped all my needed kexts into the 10.10 folder in Clover. I went into the config.plist and changed inject kext to yes instead of detect. I also used Clover Configurator to change my SMBIOS to MacPro, since that's what I've always used. And viola. I can now actually boot both Yosemite and Mavericks 10.9.3 with no issues.

 

If it doesn't work the first time, my best advice is to try again. If you have experience with Clover then you're already one step ahead of me lol

How is the graphics for you do you have acceleration?

i'm getting the Kernel Panic.. "Unable to find driver for this platform: ACPI bla..bla..", anyone how to fix this in yosemite?

I had this same problem. I stopped using the 'kext-dev-mode=1' flag and now my system boots fine

If I don't boot with "kext-dev-mode=1" I can boot into Yosemite.  Obviously that presents it's own problems as I can't load my networking kext or others.

 

If I do boot with it set, I get hung up after "AppleMobileDevice  xxxx".  Any idea why?  

 

Booted as is, Yosemite is very unstable for me.. playing around in Terminal or finder (copying/pasting files) often results in reboots.

 

Small steps, I guess.

i don't use kext-dev-mode and all my hackintosh kext boot fine. it will give errors in verbose mode but they all work

Im getting this error: "kext com.apple.driver.applemobiledevice 303009000 is in exception list, allowing to load" after successfully installing it!

Don't use 'kext-dev-mode=1' as a boot flag and you should be able to boot into yosemite

×
×
  • Create New...