Recovery HD partition with El Capitan

[zilath]

Works perfectly on Sierra mobo ga z170x ultragaming. Wifi,eth,help. One question: could you help me fo find my Mac disable every boot?

 

[Overkill303]

Confirmed working Sierra 10.12.4. Thanks so much!

 

[zilath]

Works perfectly on Sierra mobo ga z170x ultragaming. Wifi,eth,help. One question: could you help me fo find my Mac disable every boot?

Update. Find my mac works too, I don't lost in boot ... after bios upgrade.

 

[zilath]

Works perfectly on Sierra mobo ga z170x ultragaming. Wifi,eth,help. One question: could you help me fo find my Mac disable every boot?

Solved view post #23

 

[Steve28]

So.... I have a "Vanilla" install (i.e., no Mult/Unibeast) and all of .kext files are in the /EFI/Clover/kexts/other folder... I just tried to boot into recovery before doing anything and it worked fine. I'm assuming this is a side-effect of the vanilla install - and I can use it like normal?

 

[BreBo]

I just tried to boot into recovery before doing anything and it worked fine. I'm assuming this is a side-effect of the vanilla install - and I can use it like normal?

Yes you can use it like normal

 

[te3jay]

Got it working on 10.12.6.

I had to use the steps to update BaseSystem.dmg from https://www.tonymacx86.com/threads/recovery-hd-partition-with-el-capitan.181701/page-2#post-1400676 to get past the spinning beach ball though.

 

[bilditup1]

Finally! I had the same problem on El Capitan (yes, I'm upgrading now, but I wanted to have a complete El Cap system, including the recovery partition, on a USB key before moving on) and Sierra. Deleting and recreating the partition using that famous script did nothing for me. There should be a sticky somewhere about the necessity of copying the prelinkedkernel (which I guess is prelinked to FakeSMC etc) in order for the recovery partition to function. This information should not be as obscure as it is.
Note that even after this the El Cap partition has an image verification error; this does not appear to affect functionality though.
Anyway, thanks OP! This was the last piece of the puzzle.

ED: In case anybody else is having "launchd exited with code" 1 or 255 when trying to boot from Recovery HD, not having a prelinked kernel may be the issue. It was for me.

 

[G.Beared]

I edited EFI mounter a bit so it's now "Recovery HD" mounter...

Recovery Mounter .zip

 

[markjhatch]

Still works after all these years... works fine on 10.13.2 High Sierra. Tried diskutil and time machine, both appear to work.