Jump to content



Member Since 20 Aug 2005
Offline Last Active Nov 14 2017 07:53 PM

#2522632 High Sierra: Error Loading Kernel Cache 0xe - No fix! Help!

Posted by HBP on 26 October 2017 - 07:47 AM

Hello frustrated, what the below quoted code says is that #1, created a valid cache (that's good) #2 when it tried to update the symlink to point to it that process failed. to resolve that error, from ether single user mode ( -s boot mode) or the recovery partition run this list of commands.(CAUTION: both of these modes by default will give you SUDO access to the system be very carful what you type.) Hi! Thanks, the links was useful. But I am not getting any solution. The tutorial there does not account for the fact that the user needs SUDO permissions.  I ran with sudo and here is what I get...(not what the OP of that tutorial gets) This is so frustrating!!!KernelCache ID: C79B2CECB584A805F14556B0A116AE60symlink("../../../PrelinkedKernels/prelinkedkernel", "/Volumes/MAC SSD/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 2 (No such file or directory)iMac:~ b$ Help Please!Thank you so much P.S. I even re-ran without sudo code an...

#2515273 I can not get into the Boot OS X after update 05 October (Fusion Drive)

Posted by HBP on 14 October 2017 - 03:29 AM

It's been about 3 or 4 years since I used Fusion Drive, and that was the first time I had the problem. Do you think the clover that is not mounting the disXs3 partition? Do you know step-by-step I can do to solve this problem? I saved the "prelinkedkernel" but I do not know what to do with it.from any os that will read hfs+, mount the diskXs3, there will be 2 folders in it, the disk you want to mount: 3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3after Boot OS X is mounted go to the com.apple.boot.(Y) where Y is the random letter Apple has assigned the boot directory.inside that folder is 3 folders, the one you care about is System. Inside com.apple.boot.(Y)/System is Library/PrelinkedKernels. and inside that folder is the location to put your prelinkedkernel. after replacing that file you should be able to boot the fusion/raid drive without any issues. The other...

#2514671 I can not get into the Boot OS X after update 05 October (Fusion Drive)

Posted by HBP on 13 October 2017 - 05:49 AM

you have to understand how the Fusion drive/Any soft raid drive works with OSX, on your Base drive, the SSD or Spinning disk you will have a 3rd disk partition. that partition is the booster/boot partition for the raid. if you have Issues with unable to boot due to boot cache, then you need to mount that 3rd partition and update the prelinkedkernel on it. because that diskXs3 is the only thing that Clover or Ozmosis sees until the prelinked kernel takes over and initializes the software raid. I have been running Fusion Drives since their inception and the one thing I can tell you is that if you don't respect that 3rd partition you are fracked. and finely, something I learned long ago, make a copy of that prelinkedkernel somewhere safe, because you can always point the software to that kernel to boot (wether its on your Clover Partition or a thumb drive, it's a little bit more work, but it is your insurance against this happening. Just my 2 cents. HBP

#2469628 [pre-release] macOS High Sierra

Posted by HBP on 26 July 2017 - 04:52 PM

on a legit Macbook Pro 8,1 I have my battery monitor back. so they have done some work on the power management systems.

#2194927 Ozmosis

Posted by HBP on 08 December 2015 - 03:16 AM

ok, so when I update my OZ to 1669M a oddball thing happens. I lose the ability to boot from windows and Clover( my backup boot loader ) should OZ take a Dive.  what settings am I missing?  all the other settings seem Great and stable on my system in my Sig. HBP

#2170398 Ozmosis

Posted by HBP on 26 September 2015 - 08:06 AM

No official, they are still in testing phase and it is really stable ;) But it should pop in the next 4-10 days I would think, after the Official release of El Cap happens.  HBP

#2169916 Ozmosis

Posted by HBP on 23 September 2015 - 08:51 PM

for my yes, with a caveat, must have a valid MLB with your ethernet0 MAC address as your ROM.  At least for me that was the case as listed here. Good luck.  HBP on a side note, i have tried and can confirm, all version of Oz, from 894m up to the current builds will boot El Capitan.  HBP

#2169765 Pattern of MLB (Main Logic Board)

Posted by HBP on 23 September 2015 - 03:49 AM

having struggled with resolving the call Apple issue again with El capitan having used my macbook's Rom and MLB for Yosemite I found this floating on Reddit.  hope it helps the folks having issues...  https://gist.github....b46b14061d4c995 I have used it to gen MLB's for 3 hacks that have passed muster without needing to call, write or beg Apple to remember that we exist. HBP

#2167253 El Capitan GM won't install.

Posted by HBP on 12 September 2015 - 09:12 AM

you need to set your boot flags to allow unsigned kexts... a few ways to do it, (rootless=0) or search around the forums for the others. I use Ozmosis so I write directly to the nvram and am unfamiliar with the command line's of the other boot loaders. HBP the BeachBall of Death means your FakeSMC or other EMU (smc emulator) is not loaded...

#2069880 Problem booting after install

Posted by HBP on 15 October 2014 - 11:06 PM

the name on the bottom left is your computer name, if you want it changed, go to sharing in system settings and change it there. HBP

#2069273 Ozmosis

Posted by HBP on 14 October 2014 - 09:27 AM

 I removed both the DSDT and SSDT, but still restart when plug in any USB stick or external HDD and the USB ports.  May be it. But when I did not use this flag, I had only two energy states. Now with the flag "-xcpm" I have four states. And I never had this problem with the USB connections CloverEFI.  I do not even know how to solve this problem.  I'll have to go back even with my origial BIOS.   Thanks for your effort and nice work with my BIOS, Pavo. Thanks. @ Jorge, I read your KP and crash logs. what is KPing your system is the kext for the sensors kext in the bios. keep them in the OZ dir of the EFI partition and not hardcoded, or better yet, installed directly in /S/L/E. 1479 is unstable on some boards, and adding sensors to the bios adds to that problem. an alternative is to go back a revision to 894m. which is very stable and has fewer problems (it also has fewer graphics injectors). food for thought. HBP 

#2067139 Ozmosis

Posted by HBP on 07 October 2014 - 04:24 PM

Thank you HBP112358 My question it's' about AAPL injecting, i have a cpu with intel graphics 4400,so, reading default.plist i saw a specific nvram key to inject rigth AAPL code, my mind ask: it's' possible put AAPL into ozmosisdefault?  maybe yes, i have to do some experiment, maybe in the week-end :D now i'm play with xendesktop  :wallbash:if the setting exists in the defaults.plist, it can be put in the OzmosisDefaults.ffs in fact, if you read closer, for 1479 they populate all of those settings with a default in the OzmosisDefaults.ffs  the biggest reason to have the defaults file is for configuration testing before you burn your configuration to your EFI-bios. just my opinion.  HBP

#2066993 Ozmosis

Posted by HBP on 06 October 2014 - 11:28 PM

Hi folks, maybe a dumb question, can i put some data from default.plist into ozmosisdefault.plist ? if i know i compile a default.plist with some data that overwrite data presente in ozmosisdefault, the last win.Welcome and thank you for a great question.  if you follow the instructions in post #2106 of this thread you don't need a defaults.plist or writable nvram. I have tried it on 4 boards as well as having others try it, this method works with both 894M and the 1479 ozmosis and probably the earlier versions just I haven't tested with them. HBP

#2058899 Ozmosis

Posted by HBP on 08 September 2014 - 05:21 PM

How can i add it to ozmosis defaults as a bootflag? just with nvram? Or can i edit the files?on page 3 of this thread is the nvram settings and what they do... if you can reach it by remote you can reach it to change nvram settings, also, you should be thinking/looking at modifying the nvram from single user command prompt mode, if your worried about doing it remotely. HBP

#2056346 Fusion Drive [how to]

Posted by HBP on 29 August 2014 - 03:55 AM

I believe almost everyone who is out there playing with this has not been actually using a Fusion drive...after refollowing the steps from the before mentioned guide, I got to the part of making a LVG, but I named it 'FUSION' without the ' marks, then I went into disk utility (the Graphical interface) and did a repair disk on it, it asked it I wanted to restore a working Fusion Drive. I clicked yes.  and now I have a Fully working Fusion Drive. BEFORE:diskutil corestorage info FFC095BF-FB5E-4324-B598-DA80CA7AB4B0 Core Storage Properties: Role: Logical Volume Group (LVG) UUID: FFC095BF-FB5E-4324-B598-DA80CA7AB4B0 LVG Name: fusion LVG Version: 1 LVG Size: 1238926282752 B LVG Free Space: 0 B LVG Status: Online LVG Sparse: No Fusion Drive: NoAFTER:diskutil cs info 6F050F63-F87A-4690-AED4-7274C27DAC09 Core Storage Properties: Role: Logical Volume Group (LVG) UUID: 6F050F63-F87A-4690-AED4-7274C27DAC09 LVG Name: FUSION LVG Version: 1 LVG Size: 1249576288256 B LVG Free Space: 5734...

© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy