Error load prelinked kernel with status 0x800000000000e

raimue.blog

For testing purposes, I have a VM in VirtualBox currently runnning macOS 10.12 Sierra. Now that macOS 10.13 High Sierra is in Beta, I wanted to upgrade my VM to this new release. However, this proved to be difficult with the usual ways. This blog post will describe how to upgrade a Sierra VM to High Sierra.

The problem preventing the upgrade appears to be the boot sequence in VirtualBox. It looks like the EFI implementation of VirtualBox does not honor the way macOS wants to select the startup disk/volume/startup script or in whatever way that is actually supposed to work. The result is that you can click through “Install macOS 10.13 Beta.app”, but after the restart the old system comes up as if nothing happened.

Follow these steps to get around this problem:

1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the F12 key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit F12 at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:

With the last command, the system should continue booting. After a short moment, the installer will turn up and begin to upgrade your system from macOS 10.12 Sierra to macOS 10.13 High Sierra. Now you will have to wait for the macOS Installer to finish, which may take a while.

In case VirtualBox crashes with “Guru Meditation: VERR_IEM_INSTR_NOT_IMPLEMENTED” on the login screen when booting the new system, update to the latest VirtualBox test build, which implements the missing instruction.

This post was inspired by another blog post documenting similar instructions on how to enter the macOS Recovery in VirtualBox. For completeness and archival purposes, you can use the following EFI commands to boot macOS Recovery:

49 thoughts on “ Upgrading a VM from macOS 10.12 Sierra to macOS 10.13 High Sierra in VirtualBox ”

I tried this (without success) and noted the following:

I had to hold fn-F8 to get into the boot manager.

Although using the latest test build of VBox (5.1.x revision 116680) I get this message after entering the commands:

Read error 0xe
Error loading kernel cache (0xe)

I am getting the same issue as Lars is with the VM ending in
”
Read error 0xe
Error loading kernel cache (0xe)
”
After I execute the commands listed above.

Any idea on the fix?
VirtualBox 5.1.22 r115126 (Qt5.6.2) on macOS 10.12.5 host

Same issue
Read error 0xe
Error loading kernel cache (0xe)

Same issue. Error loading kernel cache.

Sorry that I did not come back to your questions. VirtualBox seems unable to boot the new macOS High Sierra Beta after migrating to APFS and there is no progress in getting that implemented. Therefore I decided to switch to VMWare Fusion instead, which I do not regret at all.

Just a note to confirm that this is working perfectly for me: Virtualbox 5.1.26
Thanks!!

I tried using latests Virtual Box (5.1.28) and current high sierra public release.
Now, there is no Locked Files folder inside of macOS Install Data, so i am not able to to boot to the new installer. Any clues?

Thanks for this blog entry. This was the smoking gun preventing me from upgrading my VirtualBox Sierra VM.

This worked great for me and allowed to create a new High Sierra VM. I was not upgrading. I had to make sure SSD was not enabled in VirtualBox preferences otherwise High Sierra would automatically want to migrate to APFS.

thanks a lot for your help

Great how-to, worked for me, but hitting F12 at the right time is very hard, so I made a snap-shot of the VM right before the reboot. That way you can avoid having to re-download the upgrade a couple of times.

I still needed to ram the F12 as fast as I could to make the EFI shell option appear.

`VBoxManage modifyvm OSX –bioslogodisplaytime 10000` –> Does not seem to work

I’m stuck here…
I had a OS X 10.12 on VMWare and started to upgraded to 10.13. When I cam back I saw the blue screen (boot menu). And failed to use your instructions, since there is no fs1 reachable in the internal shell. fs0 and blk0 to blk3. And it seems they are empty! What can I do here?

These instructions were written for VirtualBox and macOS 10.13 Developer Beta before APFS became mandatory. As far as I know, the VirtualBox EFI BIOS still does not support APFS. Personally I switched to VMWare Fusion due to this.

One thing you could try in VIrtualBox is to remove the checkbox on “Solid-state drive” in the storage settings of the VM. Then the High Sierra installer should no longer try to upgrade the disk to APFS, but leave it as HFS.

Following these steps, a message appears when run boot.efi –> “does prinf works??” and back to command line.
after that I type reboot and nothing happens, I’m in the same version.

I have the same problem as Pedro – “does printf works. ” and hangs…Any Idea what to do?

-I manually downloaded the combo update package 10.13.3 from Apple and launched it in the VM.
-The first part of update completed successfully, than it asked for restart.
-I restarted, entered the VirtualBox EFI Shell and launched boot.efi manually from the indicated path.
-After some work, message appears “macOS could not be installed on your computer – The path […]OSInstall.mpkg appears to be missing or damaged” (e.g. https://user-images.githubusercontent.com/192271/27255121-5811f2b4-538f-11e7-8117-9401bc9a7a80.png)
-I pressed Restart and the VM rebooted to High Sierra 10.13 (no update).

I think we are close to target, but some details are still missing to complete the update successfully.

Yes Yes Yes, thank, works perfectly.

first try I got kernel error like others. Tried second time and it worked don’t know what exaclty the reason for it. thanks

This was the solution I needed to upgrade from high sierra 10.13 to 10.13.4 using Virtual Box 5.2.8
Worked great! Thanks

I found the solution to “does printf works”

You can boot from instalation disk without shell, just open “boot from file” and find boot.efi on instalation disk.

@Babak Vandad: Did you see any error codes in the output? If so, was one of them ID10T?

The error
“Read error 0xe
Error loading kernel cache (0xe)”
can be solved by upgrading to the latest version of the Virtual box.

Thanks! This worked for me on VirtualBox going from 10.12 to 10.13 not in the Beta.

Thank you. Worked like a charm.

Thank you. It work with VirtualBox 5.2.8

Thank you!
It works, even it’s not worked from the first attempt.
The main cause of the fault was an old version of virtual box. With new Virtual Box (v 5.2.10) all goes well

My way of reaching 10.13.4 of Mac OS Sierra (probably you need last because of Xcode requirements)

upgrade Virtual Box to 5.2.10
do MacOs Recover
do Upgrade -> F2 …

I got this working.

Virtual Box – 5.2.12

Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

Every time I tried the above I could not get it to work and I received the error – error loading kernel cache 0x9 VirtualBox.

I did a bit of research and others were having the same issue, however, no one could get it to work.

What I did then was the following

Ran the update, reboot the machine and F12’ed into the boot manager.

I turned off the Virtual Machine and closed VBox

I then tried the following.

Opened CMD as admin and ran the following commands, these were the same commands needed when originally installed the Mac onto Vbox

VBoxManage.exe modifyvm “Mac” –cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemProduct” “MacBookPro11,3”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiSystemVersion” “1.0”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/efi/0/Config/DmiBoardProduct” “Mac-2BD1B31983FE1663”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/smc/0/Config/DeviceKey” “ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc”

VBoxManage setextradata “Mac” “VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC” 1

Once the commands complete, I started the VM on VBox and F12’ed into boot managed and followed the same procedure

Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

This time it worked and boot into the install/update – Took about 45 min +-

Hope that helps anyone.

I tried @Ghost’s solution and I got the “does printf work?” message.
Then I tried @Pedro’s “I found the solution to does printf work” and I *still* got the “does printf work?”

Then, I restored form snapshot, booted into the old version, started the install again, On bootup I tried Pedro’s solution to boot from file and this time it worked!

Thanks a lot to Ghost (2018-05-12 at 12:29) it worked for me with VB 5.2.12

The right first command is
VBoxManage.exe modifyvm “Mac” –cpuid-set 00000001 000306a9 04100800 7fbae3ff bfebfbff

Thanks a lot, worked with 10.14 beta. Not finished the installation yet, but the installer is up and running 👍🏼

I struggled to update macOS but finally worked it out.

You will find that any updates you apply will disappear after reboot as if they didn’t apply. You have to do the following as the update only completes after a reboot done in a certain way.

1) Download the update from the Apple website or apply from the App store.
2) When promoted to re-boot, press the F12 immediately after the restart, make sure the keyboard is captured in Virtualbox.
3) Press ESC key to stop the auto boot before the countdown finishes. You only have a few seconds to do this.
4) In the BOOT MANAGER option choose EFI Internal Shell.
5) Do the following at the shell command line:
fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

The system should then boot and continue the install and you are done. It is very important that you do all this on the first re-boot after applying the initial update as the update files are copied ready to complete the process. Miss the first boot and you will have to start again.

worked exactly as you described it! thanks mate!

To update mac os follow the below steps. If you will try to upgrade it normaly it would be locked by Apple and you will get the old version that you are currently running. To upgrade use the bellow steps:

Follow these steps to get around this problem:
1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the window+r key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit window+r at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:
Shell> fs1:
FS1:> cd “macOS Install Data”
FS1:macOS Install Data> cd “Locked Files”
FS1:macOS Install DataLocked Files> cd “Boot Files”
FS1:macOS Install DataLocked FilesBoot Files> boot.efi

@Ghost’s solution worked for me. Thanks!

@kundan’s worked for me.

Thanks Rainer Müller. This worked for me just fine. I even was surprised didn’t get first “restart” .. system just restarted, I didn’t repeat from step (2) , I just restarted again and hit F12, followed procedure and in aout 90 minutes system rebooted to High Sierra … !! fantastic.

Updating from High Sierra 10.x to the latest update through the store, it won’t boot anymore.
tried F12 and the folder is not there, since it was a 2.6 Gb update.

Anyway to get this update to work?

Using VirtualBox 5.2.18. I had High Sierra 10.13.4 installed and working well, but 10.13.6 would not install from the App Store. I found this post when searching, and the steps listed worked first time. Thanks for the post!

F12 just won’t work. Don’t know what I’m doing wrong… :/

Windows+R does nothing either. I guess @kundan meant HOST+F12 so i tried that (restarting the machine upon restart). I have to press ESC right after that to enter the boot menu but after launching boot.efi i end up getting a kernel cache error.

thank you @kundan this worked perfectly. F12 is the key that I used to get in.

Has anyone got this working with Mojave?

Im getting this error:

ERROR. Load prelinked with status 0x800000000000000e
Error loading kernel cache (0xe)

I tried to upgrade to Mojave from Sierra via the appstore and it crashed my partition. EFI manager did not recognize FS1 or FS2.

This is not working in VirtualBox 5.2.18. Reboots endlessly.

I was getting the Error. Load prelinked kernel with status 0x800000000000000e while trying to upgrade to Mojave MacOs on a VirtualBox virtual machine. Turns out I had the older USB 2 compatibility in the settings for VirtualBox.

If you run into this issue turn off the VM, go into VirtualBox settings USB and select USB 3.0 controller. Restart the VM and issue should be solved.

me stuck with 10.13.2
Upgrade to mojave by following the step above leaves with
ERROR. Load prelinked with status 0x800000000000000e
Error loading kernel cache (0xe)

Has anybody been able to upgrade to Mojave yet ?

This is great, you can also get to it from “Boot Maintenance” > “Boot From File” and navigating to the boot.ini visually if that’s easier.

I finally managed to get beyond “Error loading kernel cache (0xe)”.
The solution was to entirely delete the “macOS Install Data” Folder and simply restart the update in sierra.
But this folder isn’t to delete easily.

I did:
1. Boot into macOS Recovery Mode as describled in this blog post
2. Open a Termial (Menubar: Utilities->Terminal)
3. run “csrutil disable”
4. run “rm -rf “macOS Install Data”
5. run “csrutil enable”

reboot normally, run Mojave installer again, on first reboot follow the instructions in this blog post

Thanks for this post.
I tried it like described above.

First time i ran into
“Read error 0xe
Error loading kernel cache (0xe)”

But just tried it again and second time it worked.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Welcome!

This the personal blog of Rainer Müller, also known by his nickname raimue. This is the space where I publish what does not fit into a tweet.

Источник

Latest Sierra update crashed my MPB

This is the second time i get in trouble after updating my OSX!

I make clean installs now and then so my MBP is very clean and i don’t have much on it, basically use it for surfing nowadays.

Any how yesterday when i updated from App Store it rebooted my computer and all i saw what this sign:

After more digging i got to see these errors in the background:

ERROR. prelinked kernel corrupted

ERROR. Load prelinked kernel with status 0x800000000000001b

Error loading kernel cache (0x1b)

What is this all about. i tried to repair using disk utility and macOS Recovery where it did not allow me to continue and install again.

Got some other error:

It was only when i used my USB stick i had created with previous OSX version and run the disk utility and repair that i could finally get back into the computer. No idea what the **** it was all about but honestly i’m scared doing more OSX updated now. They seem to mess up to many times. Last time i also could not get into the OSX, don’t remember how i fixed that but it was also scary.

Did anyone else encounter this problem?

Also should i do some check to see if something is broken? if so how do i do that? Don’t want to reboot later and get into the same mess.

Personally i get a feeling that the quality has been worse with every software Apple releases these days. From iOS updates to OSX updates. Maybe i’m wrong but thats just my guts feeling.

macOS Sierra (10.12.3)

Posted on Feb 16, 2017 8:06 AM

Similar questions

Loading page content

Page content loaded

FWIW, your MBP is going on 7 years old and it is possible you could be having a hardware problem. You may want to make an appointment at an Apple store to have it evaluated.

ehmmm ok how do you come to that conclusion? Just because its 7 years old does not automatically mean its HW problem. Where did you draw the line. Seriously i want to get help from someone who knows more about the errors i provided and solution to them.

And if it was HW problem it would not magically solve itself when i run firstaid from an old start disk.

So no i dont believe its HW problem sorry.

ps. I ran the Hw test without finding problem also.

FWIW, I didn’t come to a conclusion, I said it was possible and you might want to have it looked at. As far as FirstAid, it’s not an exhaustive test.

Seriously i want to get help from someone who knows more about the errors i provided and solution to them

I’ll let you wait for someone else then.

It is very likely that a hardware fault is the cause of your problems; specifically, that Mac’s hard disk drive. Disk Utility is of limited use for such diagnoses, leaving only anecdotal methods. The problems you describe strongly support that hypothesis. For example, you wrote that you attempted to use Disk Utility to «repair» it, and attempting to reinstall macOS did not allow you to continue. You also wrote that you experienced similar problems in the past. Lastly, its age is reason to question the hard disk drive’s integrity.

Since Sierra introduced a completely new logging system, I do not know of a reliable way to diagnose potential hard disk problems. Disk Utility will not suffice. Until I come across a disk in a state of failure yet operational enough to test I can’t provide a means of extracting any applicable log entries that could definitively show those failures. A definitive conclusion could be drawn by installing Sierra on an external hard disk drive, booting from it, and determining if the symptoms are alleviated while running Sierra from that startup disk. To do that read How to set up and use an external Mac startup disk — Apple Support. If the external hard disk installation of Sierra works properly while the internal one does not, that is all the justification you need to replace the internal drive.

Hard disk drives are wear items that should be replaced when they become unreliable. Fortunately they are inexpensive and easy to replace on a MPB. Unfortunately, it has become abundantly clear that Apple is no longer interested in using them in any of their products, and that support for them is likely to diminish if it has not already disappeared altogether.

Источник

Latest Sierra update crashed my MPB

This is the second time i get in trouble after updating my OSX!

I make clean installs now and then so my MBP is very clean and i don’t have much on it, basically use it for surfing nowadays.

Any how yesterday when i updated from App Store it rebooted my computer and all i saw what this sign:

After more digging i got to see these errors in the background:

ERROR. prelinked kernel corrupted

ERROR. Load prelinked kernel with status 0x800000000000001b

Error loading kernel cache (0x1b)

What is this all about. i tried to repair using disk utility and macOS Recovery where it did not allow me to continue and install again.

Got some other error:

It was only when i used my USB stick i had created with previous OSX version and run the disk utility and repair that i could finally get back into the computer. No idea what the **** it was all about but honestly i’m scared doing more OSX updated now. They seem to mess up to many times. Last time i also could not get into the OSX, don’t remember how i fixed that but it was also scary.

Did anyone else encounter this problem?

Also should i do some check to see if something is broken? if so how do i do that? Don’t want to reboot later and get into the same mess.

Personally i get a feeling that the quality has been worse with every software Apple releases these days. From iOS updates to OSX updates. Maybe i’m wrong but thats just my guts feeling.

Источник

Error load prelinked kernel with status 0x800000000000e

UEFI bios:
• Скидываем все настройки в default.
• AHCI — enable;
• Vt-d: Disable (+ в Clover дропнуть DMAR таблицу)
• Vt-x: Enable (только для 10.13 и если используете виртуальные машины)
• Intel Virtualization Technology — Enable
• Serial-port: Disable (Можно оставить включеным, но это требует внесения изменений в загрузчик (Opencore)
• XHCI Hand-off: Enabled (рекомендуеться)
• XHCI Hand-off: Disable (только если что то не работает в режиме Enable )
• IOAPIC 24-119 Entries: Enabled (подмечено что у многих с этим пунктом паникует, поэтому тестируйте)
• CSM: Disable (если ваша видеокарта не умеет работать в режиме UEFI — не выключайте)
• Fasboot: Disable
• Secure boot: Disable or Other OS
• ResizeGPUBars: Disable (Можно оставить включеным, но это требует внесения изменений в загрузчик (Opencore)
• Above 4g decoding: Enable

Legacy bios:

Для установки потребуется флешка не менее 16Гб.

За данный споcоб установки благодарим cvad и Skvo
Данная инструкция написана по материалам с applelife.ru

• OPT — показать меню загрузки OpenCore. Также поддерживается клавиша Esc.
• CMD+OPT+P+R — очистить NVRAM. Требуется Misc-Security-AllowNvramReset=YES.
• X — загрузить первую найденную операционную систему Apple, если по умолчанию выбрана не операционная система Apple.
• CMD+R — загрузка в режиме восстановления (Recovery).
• CMD+C+MINUS — отключить проверку совместимости на board-id.
• CMD+K — загрузка актуального ядра, аналогично kcsuffix=release.
• CMD+S+MINUS — отключить KASLR slide, требуется выключенный SIP.
• CMD+S — однопользовательский режим, налогично флагу -s в аргументах загрузки.
• CMD+V — логирование загрузки, аналогично флагу -v в аргументах загрузки.
• Shift — безопасный режим, налогично флагу -x в аргументах загрузки.
В зависимости от железа, при загрузке может не все работать или работать не надежно. На PS/2 при загрузке доступно только Esc.

Комбинации клавиш в меню, после входа в него по OPT(Esc) или при ShowPicker=YES
За счет того что в меню действует параметр Misc-Boot-PollAppleHotKeys=YES успехов тут обычно больше. Не включайте, если с выключенным работает.

• Esc — отмена тайм-аута.
• CMD+OPT+P+R — очистить NVRAM. Требуется Misc-Security-AllowNvramReset=YES.
• CMD+C+MINUS — отключить проверку совместимости на board-id.
• CMD+K — загрузка актуального ядра, аналогично kcsuffix=release.
• CMD+S+MINUS — отключить KASLR slide, требуется выключенный SIP.
• CMD+S — однопользовательский режим, налогично флагу -s в аргументах загрузки.
• CMD+V — логирование загрузки, аналогично флагу -v в аргументах загрузки.
• Shift — безопасный режим, налогично флагу -x в аргументах загрузки.
• Index — загрузка раздела соответствующего индексу.
• Enter — загрузка дефолтного раздела или выбранного стрелками.
• CTRL+Enter и CTRL+Index — выбрать выделенный раздел для загрузки по умолчанию. Требуется Misc-Security-AllowSetDefault=YES.

CMD=Windows Key, OPT=Alt на windows ориентированной клавиатуре.

В зависимости от вашего BIOS и типа клавиатуры доступные комбинации могут варьироваться.
Больше деталей в актуальной документации.

Источник

MBP mid 2009 15″ not booting in any mode

So, after numerous search queries and attempts to create a bootable flash drive or boot at least in any mode, which all have not helped, I decided to make this post with a hope that someone will be able to assist me with my MBP.

The machine is MacBook Pro, mid-2009 running on El Capitan (as far as I know)

The Mac is not booting in Recovery or Safe mode. On startup, it shows a circle with a diagonal line across it (e.g. ⦸).

When booted in single-user mode, the only message showing is the «Error loading kernel cache (0x1b)». At this point, I have not succeeded in reaching Terminal.

In Verbose mode, the output I get before the Mac goes to Apple logo for about 10 seconds, and then goes to the very same crossed circle, is the following:

«efiboot loaded from device: Acpi (PNP0A03,0)/Pci(B10)/SAA(0,0)/HD(Part2,Sig00000DF8-66D4-0000-6932-0000AA090000)

efiboot file path: SystemLibraryCoreServicesboot.efi

ERROR. Prelinked kernel corrupted

ERROR. Load prelinked kernel with status 0x800000000000001b

Error loading kernel cache (0x1b)»

All the solutions available online involve booting in Recovery or Safe mode (neither of options are available for me on the machine).

On top of everything, when trying to boot up from external volume (32Gb flash drive) with macOS Sierra on it, it goes back to the crossed circle again.

To stress out, at this point I have not found a way to reach Terminal or any other way of manipulating the current contents of the HDD (which also means I am not able to change the corrupted kernel neither by hand, nor by command).

I am hoping someone can guide me through the steps, which could possibly fix the issue. Or tell me that the machine is toasted.

Источник

Installation Mojave Error Prelinked Kernel 0x8000000000e

Hallo, liebe Hackintosh-Gemeinde

Mein Name ist Chrisu und ich bin neu hier. Ich hab mir einen neuen PC zusammengestellt wie er in der Signatur steht. Ich lese nun schon etwas länger mit und versuche mir seit einigen Tagen nun selbst meinem eigenen Hackintosh zu bauen, bisher verlief es auch ganz und gut und die meisten meiner Hürden konnte ich selbst bewältigen, doch nun stehe auf dem Schlauch.

• Ich hab ein MacbookPro 2010 … damit hab ich HighSierra bekommen → Damit gab es nur Fehler bei der Installation auf meinem neuen PC. Bin Gar nicht weitergekommen
• Mit Hilfe vom Mojave Patcher hab ich mir Mojave geholt aufn USB Stick mit Tuni gepackt
  • ich hab mit einigen EFI Ordnern ausm Forum gearbeitet, die meisten haben nicht funktioniert, aber dann hab ich scheinbar einen gefunden, wo das Setup irgendwie gut passt.
  • Was ist passiert 😕
    • Ich hab das Video geguckt: von Patricksworld https://www.youtube.com/watch?v=cCxO-edVH0M und eigentlich hat alles geklappt, fast
      • 1. Installation ist durchgelaufen mit Formatierung der Festplatte etc. und hat einen Neustart gemacht. dann hab ich auf den Prebooter from Preboot Stick geklickt wie er im Clover Boot Menü erschienen ist
      • 2. Installation ist durchgelaufen und ich glaube es gab einen automatischen Neustart. Dann wieder auf den Preboot wie im Video geklickt um die 3. Installation zu machen und da war dann dieser Error:

ERROR. Load Prelinked Kernel with status 0x80000000000e
Error loading kernel cache (0xe)

Vielleicht gibt es ja den einen oder anderen, der sich dazu äußern kann und möchte. Ich hab schon im Forum gesucht und mir die Sachen durchgelesen, aber irgendwie weiß ich jetzt nicht genau was ich machen soll. Also ich kann mir halt vorstellen das mein EFI nicht so richtig gut ist. Ich kann mir auch vorstellen das die Driver teilweise nicht genau passen und die config.plist hatte ich eigentlich auf Mac18.3 eingestellt aber das hat sich irgendwie verändert. Ich hatte auch schon mal F11 (Im Forum hatte ich das hier gefunden und da hatte DSM2 geschrieben dass man F11 im Clover Boot Menü drücken soll umd so einen Reset zu machen. Hier ist der Link dazu: Gigabyte Z390 Aorus Master

Hat aber irgendwie nicht so richtig funktioniert .

Источник

For testing purposes, I have a VM in VirtualBox currently runnning macOS 10.12 Sierra. Now that macOS 10.13 High Sierra is in Beta, I wanted to upgrade my VM to this new release. However, this proved to be difficult with the usual ways. This blog post will describe how to upgrade a Sierra VM to High Sierra.

The problem preventing the upgrade appears to be the boot sequence in VirtualBox. It looks like the EFI implementation of VirtualBox does not honor the way macOS wants to select the startup disk/volume/startup script or in whatever way that is actually supposed to work. The result is that you can click through “Install macOS 10.13 Beta.app”, but after the restart the old system comes up as if nothing happened.

Follow these steps to get around this problem:

1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the F12 key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit F12 at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:

   Shell> fs1:
   FS1:> cd "macOS Install Data"
   FS1:macOS Install Data> cd "Locked Files"
   FS1:macOS Install DataLocked Files> cd "Boot Files"
   FS1:macOS Install DataLocked FilesBoot Files> boot.efi
   

With the last command, the system should continue booting. After a short moment, the installer will turn up and begin to upgrade your system from macOS 10.12 Sierra to macOS 10.13 High Sierra. Now you will have to wait for the macOS Installer to finish, which may take a while.

In case VirtualBox crashes with “Guru Meditation: VERR_IEM_INSTR_NOT_IMPLEMENTED” on the login screen when booting the new system, update to the latest VirtualBox test build, which implements the missing instruction.

This post was inspired by another blog post documenting similar instructions on how to enter the macOS Recovery in VirtualBox. For completeness and archival purposes, you can use the following EFI commands to boot macOS Recovery:

Shell> fs2:
FS2:> cd com.apple.recovery.boot
FS2:com.apple.recovery.boot> boot.efi

When I try to start boot.efi from Recovery volume copied to USB stick & booted with rEFIt on REAL Mac with Mojave 10.14.6, I get same error:

ERROR!!! Load prelinked kernel with status 0x800000000000000e

Error loading kernel cache (0xe)

This Recovery volume is definitely working (tested with Cmd+R)

Any help appreciated

sebus

edit:

Sorted, needed to use rEFInd Boot Manager (on real Apple hardware) or at least Clover 5129 (which had the fix for Recovery on USB)

This way I can booty into Recovery partition from USB without any need to be worried about internal HD (just like Windows PE from USB stick)

This environment is not as much useful (as hardly anything GUI based runs on it), but one can ie restore/create .dmg image with asr

FireWolf OS X PE 9 is still unusable as it always comes with error:

Recovery Image verification fail with status [0x800000000000000e]

Most likely it is down to the fact that both immutablekernel & prelinkedkernel are zero KB yet it is referenced in com.apple.Boot.plist

    <key>Kernel Cache</key>
    <string>com.apple.recovery.bootimmutablekernel</string>

Anybody has any idea what OS X version was used, so I can adjust the missing immutablekernel ?

edit 2:

It is 10.13.5, but never bothered to test it by replacement of both files

Edited March 14, 2021 by sebus

So, this is me, after two days having tried almost every possible solution from the internet and the Apple Support team.

I have a 2016 Macbook Air. It has worked greatly for all this time. And until wednesday (four days ago), I haven’t updated since El Capitan. I thought updating to Mojave would be a good idea. Yesterday in the morning I turned on the mac. Forbidden sign. (Circle+Slash). Restart. Again, and again, and again. Cmd+R. Recovery mode. Trying to reinstall Mojave: the Macintosh HD is encrypted and asks me for the password. Dialog box opens for me to type and…
JUST CAN’T TYPE.
Can’t click over the text box. Nothing. I restart to the same point to see if there was a keyboard problem. Try Terminal. It types. I try Disk Utility. In order to make any change, it asks me the password, but the same beautiful dialog box in which I can’t write anything. I create a partitioned APFS volume from the same disk. It works. I install Mojave in it. I start it correctly. When I go to finder, it states that the Macintosh HD (the other disk) is encrypted and blocked. In order to unlock it, the same dialog box in which, I CAN’T TYPE.

I google and google. I chat with the Apple Care team. They call me. Then they connect me with their manager, the superior service. They ask me to restart, to create a parallel startup disk in an external drive. I do it. I install Mojave in it. The same loop again. I try

resetpassword

in Terminal in recovery mode, for the Macintosh HD. It’s possible. I do it by connecting to icloud. (It was encrypted and accesible to get the pass by icloud). Now it appears ‘mounted’. I try

diskutil apfs unlockVolume /dev/disk2s1

(this solution) Can’t.

I try reinstalling Mojave in the disk when ‘mounted’ by resetting password again. It fails. Forbidden sign again. Now I’m trying the kernel solution from this question, but there’s something I might be doing wrong, because I can’t get to the list of the kext extensions.

I am lost. And I need to recover the data from the last three weeks before my last backup. I can’t lose that info. If I could just recover that, and lose all of the extra stuff, It won’t be a problem.

Do you have any input? Trying won’t hurt me Thank you!

EDIT:
When starting pressing Cmd+S, these are the errors:

BuildUser(): error building a user of type 0x20010008  
ERROR: no panel or special users!  

End OpenKernelRootVolume  
ERROR!!!Load prelinked kernel with status 0x800000000000000e  
Error loading kernel cache (0xe)  

Hi,

This is the second time i get in trouble after updating my OSX!

I make clean installs now and then so my MBP is very clean and i don’t have much on it, basically use it for surfing nowadays.

Any how yesterday when i updated from App Store it rebooted my computer and all i saw what this sign:

https://dl.dropboxusercontent.com/u/33591942/OSX%20Sierra%20crash/2017-02-15%202 2.10.31.jpg

After more digging i got to see these errors in the background:

https://dl.dropboxusercontent.com/u/33591942/OSX%20Sierra%20crash/2017-02-15%202 2.11.05.jpg

ERROR!!! prelinked kernel corrupted

ERROR!!! Load prelinked kernel with status 0x800000000000001b

Error loading kernel cache (0x1b)

What is this all about!?!? i tried to repair using disk utility and macOS Recovery where it did not allow me to continue and install again.

Got some other error:

https://dl.dropboxusercontent.com/u/33591942/OSX%20Sierra%20crash/2017-02-15%202 2.45.08.jpg

It was only when i used my USB stick i had created with previous OSX version and run the disk utility and repair that i could finally get back into the computer. No idea what the **** it was all about but honestly i’m scared doing more OSX updated now. They seem to mess up to many times. Last time i also could not get into the OSX, don’t remember how i fixed that but it was also scary.

Did anyone else encounter this problem?

Also should i do some check to see if something is broken? if so how do i do that? Don’t want to reboot later and get into the same mess.

Personally i get a feeling that the quality has been worse with every software Apple releases these days. From iOS updates to OSX updates. Maybe i’m wrong but thats just my guts feeling.

I am building my first Hackintosh using Mojave 10.14.5. I used the vanilla guide as recommended on this subreddit. I am seeing errors after the Clover bootloader and before the Mojave install begins. The verbose messages read:

Start UncompressKernelCache

End UncompressKernelCache

ERROR!!! Uncompress prelinked kernel

ERROR!!! Load prelinked kernel with status 0x8000000000000007

Error loading kernel cache (0x7)

My specs are:

CPU: Core i5-9400F

GPU:Sapphire RX 580 Pulse 8GB

Motherboard/Laptop model:Gigabyte Z390 M GAMING

What guide/tool followed: Vanilla for Coffee Lake https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/ I also used Install Disk Creator, the latest version of Clover, and Clover Configurator

What part I got an issue with: Clover bootloader into Mojave installer

What files/config I am using: recommendations from Vanilla guide

Extra Info: The CPU does not have a iGPU, but it should still work through the dGPU based on other posts. My build only has USB 3.0 and higher. I adjusted the motherboard BIOs as recommended from the vanilla guide. My SSD is not formatted yet.

Thank you for any assistance.

EDIT: I solved the problem by removing AptioMemoryFix-64.efi and adding OsxAptioFixDiv-64.efi. This could be because of the motherboard or the CPU. I also updated the BIOS on the motherboard from F4 to F6 (for support of 9th generation Intel CPUs; the motherboard ships with an outdated BIOS). Also, I did not have to include NoVPAJpeg.kext (formerly needed for CPUs lacking an internal GPU). The OS install worked fine.