foster Posted July 23, 2014 Share Posted July 23, 2014 Allowed my system to update to DP4. When I restarted it would not finish booting Noticed that FakeSMC was not allowed to load even though NVRAM shows kext-dev-mode 1 in it I was trying everything to get FakeSMC to load put the kext-dev-mode=1 as a boot arguement which was in my clover config. systen started normally I mounted my EFI partition to read the clover config into clover configurator That is when I noticed EFI had been erased. Was not hard to fix, Install clover, copy a backup of config.plist back to EFI partition Rebooted and everything works fine Link to comment Share on other sites More sharing options...
Allan Posted July 23, 2014 Share Posted July 23, 2014 Try this, erase FakeSMC from S/L/E, and put them in EFI/CLOVER/kexts/10.10 (or "other"). After this, repair your permissions and rebuild the cache. Link to comment Share on other sites More sharing options...
foster Posted July 23, 2014 Author Share Posted July 23, 2014 It was not because FakeSMC was in S/L/E it was because was not reading any clover files from the EFI partition, the portion of the update process that occurs at a different run level before a restart erased everything in the EFI partition, which also removed the boot flag kext-dev-mode=1 While trying to get my system back up I moved FakeSMC to /Library/Extensions where some other kexts are located. I am not sure how the system was able to boot and stall with clover missing from the EFI partition. Link to comment Share on other sites More sharing options...
Recommended Posts