Recover HD booting with macosxbootloader

The macosxbootloader is almost fully functional. Adds support for OS X 10.10 Yosemite for the 2006/2007 Mac Pro models. Supports both grey and black theme mode – with the white process bar – but booting from the Recovery HD is still not working. Or maybe I should say no longer working? I mean. Did this ever work with the unmodified version of boot.efi (Tiamo’s), with Mavericks, or not?

If that is a yes, then something is obviously broken. I had a few ideas, and we’ve been testing some of them already, but I am getting confused. What I need now is a full list of all files, and directories, from a Recovery HD partition on a 2006/2007 Mac Pro. Mine appears to be quite different, or maybe it is borked, so that is where you guys come in handy.

p.s. I only need one list so if we have one, please only add omissions. This way we can keep it as clean as possible. Thanks!

Update

Good news. I remembered something from like five months ago. Yes. I already figured this out but I forgot about this change. Luckily some part of my brain recalled it and that was when I asked Mikeboss – a great help by the way – to backup: /com.apple.recovery.com/kernelcache and to copy: /System/Library/Caches/com.apple.kext.com/Startup/kernelcache over it. BOOM. A successful boot from his Yosemite Recovery HD!

In other words. The missing 28 bytes (before the mach_header) at the start of the kernelcache, which was removed by Apple in BaseSystem.dmg and the one on the Recovery HD, is causing this boot problem. I have no idea why Apple did remove it, but it is likely to break most boot loaders. With a few exceptions. And that ladies and gents was why the load routine in macosxbootloader is failing.

A fix to remedy this problem is being worked on and should soon be available.

Update 2

The last commit (bf5115b) probably doesn’t work, but the one before that (f519966) should work. Please give it a try.

146 thoughts on “Recover HD booting with macosxbootloader

  1. Hey Pike, I’ve been following this saga over at macrumors forums, just wanted to say thanks for all the work you’ve put into this !
    Hopefully this helps, it is from the recovery partition of Yosemite installed on an external drive on my 1,1to 2,1 flashed MacPro.
    Thanks again for all you’ve done on this project !

    – Jay

    sudo ls -R /Volumes/Recovery\ HD

    .DS_Store .fseventsd com.apple.recovery.boot
    .Trashes .metadata_never_index

    /Volumes/Recovery HD/.Trashes:

    /Volumes/Recovery HD/.fseventsd:
    no_log

    /Volumes/Recovery HD/com.apple.recovery.boot:
    .disk_label BaseSystem.dmg boot.efi
    .disk_label_2x PlatformSupport.plist com.apple.Boot.plist
    BaseSystem.chunklist SystemVersion.plist kernelcache

    • Hi Jay,

      Thanks. Not what I have here, and thus I may have been looking in the wrong spot for files. I’m going to check the: “Yosemite Recovery Update” (version 3.0) that I installed on 28 September 2014 to see if I can find the files/directories I have here…

      • Pike, in case you need a ZIP of the files (or a description of the contents in the case of plists) in the Yosemite Recovery HD, just let us know and we’ll be happy to upload them and provide the relevant link.

      • No thanks. I was only looking for a confirmation, that my Recovery HD was busted. Must have been one of the many experiments that I do here to get things going.

  2. Here is what is on my Mavericks partition (I left out all the spotlight data).
    Hopefully this helps.

    – Jay

    sudo ls -R /Volumes/Recovery\ HD

    .DS_Store .Trashes .metadata_never_index
    .Spotlight-V100 .fseventsd com.apple.recovery.boot

    /Volumes/Recovery HD/.Trashes:
    502

    /Volumes/Recovery HD/.Trashes/502:

    /Volumes/Recovery HD/.fseventsd:
    fc0074d090766b91 fc0074d090766b92 fseventsd-uuid

    /Volumes/Recovery HD/com.apple.recovery.boot:
    .disk_label BaseSystem.dmg boot.efi
    .disk_label_2x PlatformSupport.plist com.apple.Boot.plist
    BaseSystem.chunklist SystemVersion.plist kernelcache

  3. Oops… forgot to add that I can boot from the Mavericks recovery partition with the Tiamo boot.efi file, but have been unable to boot from the Yosemite recovery partition regardless of which boot.efi file I’ve tried.

    – Jay

    • I remember reading something about that stating that the failure was somehow dependent on how precisely the Fusion Drive had been created and/or maintained. Maybe you should make sure the Fusion drive receives a pristine copy of a fully functional HDD, but don’t ask me how to do that. I don’t have a Fusion drive myself.

  4. just as a sidenote: of course I will mention it specifically as soon as the Recovery HD will boot!

    latest build e38fee2fb1 gives:
    PIKE: Calling LdrpKernelCacheValid()
    PIKE: LdrpKernelCacheValid(8)
    PIKE: LdrpKernelCacheValid(1)

    • Sorry for the late response, but I was busy fixing other stuff. Anyway. The output tells me that I did something stupid. It does find the kernel cache, on the (HDD/SSD) drive, but not the one on the Recovery HD so let’s try something new (changes committed already).

  5. result when trying to boot Recovery HD (latest commit a82f6e6fcf):

    PIKE: NO recovery boot mode!
    PIKE: NO recovery boot mode!
    PIKE: NO recovery boot mode!
    PIKE: Calling LdrpKernelCacheValid()
    PIKE: LdrpKernelCacheValid(0)
    PIKE: LdrpKernelCacheValid(4)
    PIKE: Calling LdrpKernelCacheValid()
    PIKE: LdrpKernelCacheValid(0)
    PIKE: LdrpKernelCacheValid(1)
    _

    • Ok this is much better. Now it locates the kernel cache that is set in com.apple.Boot.plist and the next update should load the file.

      I don’t know if this: “NO recovery boot mode!” is a problem, but I will check that later today. Might as well be set later on in the boot process.

      • result when trying to boot Recovery HD (latest commit d72541f348):

        PIKE: NO recovery boot mode!
        PIKE: NO recovery boot mode!
        PIKE: NO recovery boot mode!
        PIKE: Calling LdrpKernelCacheValid()
        PIKE: LdrpKernelCacheValid(0)
        PIKE: LdrpKernelCacheValid(4)
        PIKE: in LdrpKernelCacheValid(x)

        then the Mac is rebooting immediately.

      • Normal boot still works?
        What do you get when you change DEBUG_LDRP_CALL_CSPRINTF to 1 in StdAfx.h?

        Edit: I have committed two changes. Try them one at a time.

  6. good morning!

    I didn’t try to boot the partition containing Yosemite. the new commit is not compiling:

    Error 1 error C2220: warning treated as error – no ‘object’ file generated C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\LoadKernel.cpp 433 1 boot
    Warning 2 warning C4002: too many actual parameters for macro ‘CHAR8_CONST_STRING’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\LoadKernel.cpp 433 1 boot
    Error 3 error C2664: ‘void CsPrintf(const CHAR8 *,…)’ : cannot convert argument 1 from ‘const char [54]’ to ‘const CHAR8 *’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 556 1 boot
    Error 4 error C2664: ‘void CsPrintf(const CHAR8 *,…)’ : cannot convert argument 1 from ‘const char [21]’ to ‘const CHAR8 *’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 560 1 boot
    Error 5 error C2664: ‘void CsPrintf(const CHAR8 *,…)’ : cannot convert argument 1 from ‘const char [21]’ to ‘const CHAR8 *’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 561 1 boot
    Error 6 error C2664: ‘void CsPrintf(const CHAR8 *,…)’ : cannot convert argument 1 from ‘const char [21]’ to ‘const CHAR8 *’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 562 1 boot

  7. 😉

    Error 1 error C2220: warning treated as error – no ‘object’ file generated C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 559 1 boot
    Warning 2 warning C4002: too many actual parameters for macro ‘CHAR8_CONST_STRING’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 559 1 boot
    Error 3 error C2146: syntax error : missing ‘)’ before identifier ‘filePath’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 559 1 boot
    Error 4 error C2059: syntax error : ‘)’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 559 1 boot
    Warning 5 warning C4002: too many actual parameters for macro ‘CHAR8_CONST_STRING’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 560 1 boot
    Error 6 error C2146: syntax error : missing ‘)’ before identifier ‘filePath’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 560 1 boot
    Error 7 error C2059: syntax error : ‘)’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 560 1 boot
    Warning 8 warning C4002: too many actual parameters for macro ‘CHAR8_CONST_STRING’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 561 1 boot
    Error 9 error C2146: syntax error : missing ‘)’ before identifier ‘filePath’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 561 1 boot
    Error 10 error C2059: syntax error : ‘)’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\Main.cpp 561 1 boot

  8. ok, compiled fine. here’s what I got:

    PIKE: setting BOOT_MODE_EFI_NVRAM_RECOVERY_BOOT_MODE
    PIKE: filePath = \com.apple.recovery.boot\boot.efi
    PIKE: filePath = \com.apple.recovery.boot\boot.efi
    PIKE: filePath = \com.apple.recovery.boot\boot.efi
    _

  9. I’m very sorry to read about your equipment going up in smoke!

    here are the results from the latest commit:
    PIKE: setting BOOT_MODE_EFI_NVRAM_RECOVERY_BOOT_MODE
    PIKE: filePath = \com.apple.recovery.boot\boot.efi
    PIKE: calling BlTestBootMode(FORCED)
    PIKE: in BlpRunRecoveryEfi(1)
    PIKE: in BlpRunRecoveryEfi(2)
    PIKE: in BlpRunRecoveryEfi(3)
    PIKE: in BlpRunRecoveryEfi(11)
    PIKE: in BlpRunRecoveryEfi(12)
    _

    • Ok. It seems that some setting isn’t set correctly. No idea why, yet, but I’ll look into it as soon as possible.

      Edit: Hey here is a new idea. What debug output data do you get when you boot from a Mavericks Recovery HD partition? That should help us.

      Thanks for testing this!

  10. okay, tested it with the Recovery HD from OS X Mavericks. for starters, it boots!

    output is exactly the same:
    PIKE: setting BOOT_MODE_EFI_NVRAM_RECOVERY_BOOT_MODE
    PIKE: filePath = \com.apple.recovery.boot\boot.efi
    PIKE: calling BlTestBootMode(FORCED)
    PIKE: in BlpRunRecoveryEfi(1)
    PIKE: in BlpRunRecoveryEfi(2)
    PIKE: in BlpRunRecoveryEfi(3)
    PIKE: in BlpRunRecoveryEfi(11)
    PIKE: in BlpRunRecoveryEfi(12)
    _

    • Hmm. That is quite interesting isn’t it. Let’s try to boot in verbose mode from the Yosemite Recovery HD. You can do this by adding the -v argument under ‘Kernel Flags’ in com.apple.Boot.plist, which you probably know of course, but just in case other people would like to give it a go. So where does it stop/fail? Is the DMG mounted? What’s the difference?

  11. PIKE: setting BOOT_MODE_EFI_NVRAM_RECOVERY_BOOT_MODE
    PIKE: filePath = \com.apple.recovery.boot\boot.efi
    PIKE: calling BlTestBootMode(FORCED)
    PIKE: in BlpRunRecoveryEfi(1)
    PIKE: in BlpRunRecoveryEfi(2)
    PIKE: in BlpRunRecoveryEfi(3)
    PIKE: in BlpRunRecoveryEfi(11)
    PIKE: in BlpRunRecoveryEfi(12)
    PIKE: \com.apple.recovery.boot\kernelcache
    PIKE: Calling LdrpKernelCacheValid()
    PIKE: LdrpKernelCacheValid(0)
    PIKE: LdrpKernelCacheValid(4)
    PIKE: in LdrLoadKernelCache(x)
    _

    • Ok so with Mavericks the last line you see is this: “PIKE: in BlpRunRecoveryEfi(12)” and then everything is fine, but with Yosemite it appears to load the kernelcache and then it hangs. Correct?

      Edit: Changed files, including cleanups committed.

  12. okay: trying it on Yosemite Recovery HD gives no output whatsoever and it hangs at the grey screen with grey Apple logo. Yosemite boots in verbose mode then switches to white logo on black background. seems to work nornal otherwise.

    • First. Thanks again for all your help with testing my changes!

      Now. So Yosemite boots fine with the latest cleanups/changes, which is good to hear, but booting from the Yosemite Recovery HD doesn’t even enter verbose mode. That is strange. Is that because you didn’t replace boot.efi on the Recovery HD partition? I presume that you have to do this for Mavericks as well. Correct?

  13. my pleasure to help and do some testing!

    I double checked again (as I usually do before posting) and it’s just like you wrote: latest commit boots Yosemite just fine, Yosemite Recovery HD does not boot and also it doesn’t give any output at all, even when in verbose. in verbose there’s only an underscore and that’s it. do you want me to try Mavericks, too? or Mavericks Recovery, or both?

    • Still Thanks man!

      Yeah the lack of output is unexpected. Say. Do you see any output when you boot from the Mavericks Recovery HD? And did you replace boot.efi on (both) partition(s)?

      Edit

      There are a couple of places in the source code that I don’t trust. They do something that is strange for Yosemite. The first check can be found in FileIo.cpp and I just made a change in this file to see if I am right.

  14. the “cleanup” release boots Mavericks Recovery HD. there’s no boot.efi debugging output but verbose kernel stuff afterwards. I made sure (again) that I replaced the boot.efi on the tested partitions. will test the latest commit “b6ca6d025e” in a few minutes…

  15. compiler throws an error:
    Error 1 error C2220: warning treated as error – no ‘object’ file generated C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\LoadKernel.cpp 599 1 boot
    Warning 2 warning C4002: too many actual parameters for macro ‘CHAR8_CONST_STRING’ C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\LoadKernel.cpp 599 1 boot

    • Oops. Same kind of error as the one we had a couple of days ago. Should be fine now.

      p.s. I am working on my iPad now so please forgive me for being slow (had to recharge the iPad).

  16. All earlier builds built with success.

    With build be4f1995d7, I get:

    Error 1 error C2220: warning treated as error – no ‘object’ file generated C:\Users\splifingate\Downloads\macosxbootloader-master_be4f1995d7\macosxbootloader-master\src\boot\LoadKernel.cpp 599 1 boot

    Warning 2 warning C4002: too many actual parameters for macro ‘CHAR8_CONST_STRING’ C:\Users\splifingate\Downloads\macosxbootloader-master_be4f1995d7\macosxbootloader-master\src\boot\LoadKernel.cpp 599 1 boot

    Am I alone?

    Regards, splifingate

  17. Insertion of b6ca6d025e boot.efi into all respective positions within the Recovery HD 10.10 (and Yosemite):

    Boot into Yosemite holds on black screen with underscore-cursor for approx. 7sec, then boots into a fully-functional Yosemite.

    Boot into Recovery HD 10.10 holds on black screen with underscore-cursor for approx. 7sec, then boots into a fully-functional Yosemite.

    Next try: re-image the stock Recovery HD 10.10 to see what happens….

  18. Edited be4f199 to move parenthesis on line 599 in parity with 8daba58, and replaced the newly-compiled boot.efi to each, respectively, on Recovery HD 10.10

    I then re-copied the stock BaseSystem.dmg back to the 10.10 Recovery HD (I have been using hdiutil to open, edit, and re-package the stock BaseSystem to include current changes).

    I also copied the newly-compiled boot.efi to each, respectively, on the working Yosemite partition.

    Booting into Yosemite, I get:

    PIKE: Calling BlDecompressLZVN().
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    _

    …with a short delay, then a successful boot into a fully-functional Yosemite.

    Booting into Recovery HD 10.10, I get:

    PIKE: Returning from LdrLoadKernelCache(2147483662).
    PIKE: Calling BlDecompressLZVN().
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    _

    After well-over five minutes, I am still looking at the latter output….

    Should I call these (apparent) Dallas, Texas phone number(s)?

    Regards, splifingate

    • Lol. Don’t call these numbers, but now seriously. 2147483649 = EFI_LOAD_ERROR and 2147483662 = EFI_NOT_FOUND. There are only two files where EFI_LOAD_ERROR is used. Let’s try to find out what is going on. New debug data added.

  19. I’m unable to build commit da25237509:

    Error 1 error C2065: ‘temp’ : undeclared identifier C:\Users\mikeboss\Desktop\macosxbootloader-master\src\boot\LoadKernel.cpp 560 1 boot

    • That would mean that it fails to unpack the kernel cache. New debug output added so that we can check this.

      I have already unpacked the kernelcache with the routine that I am using, and that works, but maybe there is something wrong with the file you are using (read: it might be different somehow). So what is the md5 of your copy of /com.apple.recovery.com/kernelcache?

    • I should have asked this earlier, but backup: /com.apple.recovery.com/kernelcache
      Then copy: /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache over it. I bet its due to the file headers being different.

      Yeah Apple stripped a few bytes off of at the start of the file. I knew it, but I somehow forgot about it. This is also why it works with Mavericks and not with Yosemite.

  20. really embarassing, I know. but it seems I’m unable to find the surprise 😦 anyway, everything now works beautifully and both partitions start just fine (using f519966 right now, didn’t try the latest commit yet). except, it looks like the system won’t start after being fresh installed. I created an installer disk, the install goes through flawless but at the first boot it hangs, being in the middle of the progress bar. I am looking into this right now, there’s a re-install running at this very moment…

  21. okay, here’s the last line of the output I see during first boot after fresh install:
    Sun Oct 26 05:48:33 2014 localhost com.apple.xpc.launchd[1] : Extension SDK cache is not present. Attempting to rebuild…

    I waited for like 10 or 15 minutes, nothing more happened. any ideas?

  22. strange… it somehow seems to be connected to the NVRAM. the only difference compared to the other installs I did was that I cleared PRAM with the command “nvram -c” before starting the install procedure. even with the old, known good Yosemite installer I failed (at the same point). now after resetting PRAM with option-command-P-R pressed after power on I’m able to install again (at least with the old known good installer). testing now again with the latest/new boot.efi install disk…

  23. Replaced the kernekcache, and tried both bf5115b and f519966.

    Both boot into Yosemite.

    Booting into Recovery HD with both gives me this:

    PIKE: Calling BlDecompressLZVN().
    PIKE: BlDecompressLZVN() returned: 2147483649!
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    PIKE: Calling BlDecompressLZVN().
    PIKE: BlDecompressLZVN() returned: 2147483649!
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    _

    With a perpetual wait….

    Just for fun, I replaced all the boot.efi with 6c697848ef, and I received only a black background with a white apple, and a perpetual wait….

    I tried all these with the stock BaseSystem.dmg /and/ a re-packaged BaseSystem with the modified boot.efi, /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache (17.9MB) copied, and updated PlatformSupport.plist info with the same results.

    new boot.efi added to Yosemite each time….

    I /did/ call that phone number, and I got a recording that said the next clue would be found in a hidden compartment in one of the four keystones located at Apple’s new campus, but I am unable to make a trip out there at this time.

    Regards, splifingate

  24. now it’s getting even weirder 🙂 I did a fresh install with an installer disk containing the f519966 boot.efi. everything went fine, Yosemite boots. Recovery HD looks like it’s booting but it somehow jumps to the standard Yosemite partition during boot. huh?

  25. Same jump to Yosemite for me, also, with f519966.

    Must now do a re-image from scratch to start with Stock.

    Just so I am on the same page:

    Should I be using the Debug/win32, Release/win32 or both?

    IIRC, have tried both with equal results….

    • Cool!

      I guess that you see this: “PIKE: SWAP_BE32_TO_HOST(KERNEL_CACHE_MAGIC) found!” and not this: “PIKE: KERNEL_CACHE_MAGIC found!”. Right?

      Edit: So everything is fine now?

      • yep, it boots into Recovery HD successfully. output is as follows:

        PIKE: SWAP_BE32_TO_HOST(KERNEL_CACHE_MAGIC) found!
        PIKE: Calling BlDecompressLZVN().
        PIKE: Calling MachLoadMachO().
        PIKE: Returning from LdrLoadKernelCache(0).
        _

      • The output looks fine, so just to be sure: This was with the factory/vanilla Recovery HD kernelcache?

        Note: I had to ask this, because the output that splifingate is reporting here is totally different.

  26. Booting using 81e474f53c into Recovery HD gives me:

    PIKE: Calling BlDecompressLZVN().
    PIKE: BlDecompressLZVN() returned: 2147483649!
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    PIKE: Calling BlDecompressLZVN().
    PIKE: BlDecompressLZVN() returned: 2147483649!
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    _

    Perpetual wait….

    Booting using 81e474f53c into Yosemite gives me:

    PIKE: Calling BlDecompressLZVN().
    PIKE: BlDecompressLZVN() returned: 2147483649!
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    _

    A short pause, then successful boot into Yosemite.

    • I may have misunderstood the last comment (2014/10/26 at 4:56 pm) made by mikeboss, or something strange is going on. What do you get with: xxd -l 64 /Volumes/Recovery\ HD/com.apple.recovery.boot/kernelcache

  27. 0000000: cafe babe 0000 0001 0100 0007 0000 0003 …………….
    0000010: 0000 001c 0111 a1d9 0000 0000 636f 6d70 …………comp
    0000020: 6c7a 766e 7d8e e05e 02f6 2000 0111 a059 lzvn}..^.. ….Y
    0000030: 0000 0001 0000 0000 0000 0000 0000 0000 …………….

  28. stock Recovery HD:

    $ xxd -l 64 /Volumes/Recovery\ HD/com.apple.recovery.boot/kernelcache

    0000000: 636f 6d70 6c7a 766e d392 eb77 02b0 0000 complzvn…w….
    0000010: 010b af35 0000 0001 0000 0000 0000 0000 …5…………
    0000020: 0000 0000 0000 0000 0000 0000 0000 0000 …………….
    0000030: 0000 0000 0000 0000 0000 0000 0000 0000 …………….

  29. funny stuff going on 😉 did a fresh install with an installer disk containing the latest commit (switched to grey boot and non-verbose before compiling). now boots again into Yosemite when trying to start the Recovery HD. hm.

    Edit: mystery has been solved: the installer routine copied Apple’s original boot.efi to /Recovery HD/com.apple.recovery.boot/boot.efi. I only can speculate that the installer copies the file from BaseSystem.dmg to the Recovery HD.

  30. o.k.

    So; it’s so.

    After a complete erase and [successful] re-install of Yosemite (using the Release build of 81e474f53c), I replaced all default boot.efi in both Yosemite and Recovery HD 10.10 with the Debug build of 81e474f53c.

    Booted to…

    PIKE: Calling BlDecompressLZVN().
    PIKE: BlDecompressLZVN() returned: 2147483649!
    PIKE: Returning from LdrLoadKernelCache(2147483649).
    _

    …with a short pause, then successful boot into Yosemite.

    If I use the Release build of 81e474f53c in Recovery HD 10.10, I get a black background, white apple, and a perpetual wait.

    Back in the day–right after I successfully installed Mavericks with the Tiamo boot.efi, I was unable to boot into the Recovery HD 10.9

    Only after replacing the stock boot.efi’s with Tiamo’s (including the ones inside BaseSystem.dmg) was I able to successfully boot into Recovery HD 10.9

    May not mean much, but with all these edits, I wonder if the Rubicon has been inadvertently been missed with an un-crossed detour.

    Still, I look forward to more, Mr. Alpha.

    Thanks for these things.

    Regards, splifingate

    • The boot.efi on the Recovery HD 10.10 should boot in verbose mode, but that doesn’t seem to be working on your setup. That has to be solved first. I know that I asked him to add the -v kernel flag in com.apple.Boot.plist on his Recovery HD, but I don’t know if he is still using it, or not. Mike? Are you?

  31. yes, unless otherwise mentioned, everything was tested with unmodified/vanilla system files. I did not use the “-v” kernel flag anymore, only that one time when you advised me to do so. I’m still using build f519966 (edited, so it will give grey bootscreens and non-verbose mode).

    now I re-tested this again a few minutes ago: I created an installer disk containing your boot.efi in the right places. I then was able to successfully install Yosemite, it works just fine. the Recovery HD was also created during install but somehow it ends up containing Apple’s own boot.efi. thus, the Recovery HD won’t start. I just replaced the boot.efi on the Recovery HD and voila: it boots flawless.

    • Great! What I also like to know if more people are reporting success, or is it still just you? I mean. We got to get more people involved with this. Can you help splifingate to get his MacPro going?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s