Boot mac os install prebooter from preboot что это

[Solved] Unable to boot into High Sierra after (successful?) install #21

Comments

ggctseng commented Jan 16, 2018 •

2018-02-01

I’m directing people to this who have problems booting into High Sierra installer to look for my post below. Do a search for «THIS IS THE SOLUTION REFERENCED IN MY FIRST POST» (searching for the word «solution» would probably work as well). Please start a new thread where appropriate (i.e., do not ADD to this thread as I won’t be checking it).

2018-01-17 1:52pm PST

Resolved one issue, which was I didn’t add FixHeaders_20000000 correctly (should be added as a boolean value). However, the system just reboots after a few screens of logs. I’ll update with more information once I’m able to capture a video.

Please ignore anything beyond this point and go to the 2nd post (1st response) to see my question.

I can’t seem to run the installer. The last thing I have tried, after reading the other reported issues, is

• removing all kexts except VoodooPS2 and FakeSMC
• added FixHeaders_20000000 to ACPI/DSDT/Fixes/ in plist
• removed SSDT-XHC.aml from ACPI patched.

I used the plist from the git but removed all the IONVMeFamily patches under KextsToPatch based on this thread:

I’m not sure what to try next.

Attached is my CLOVER directory and a picture of the last screen when I try to run the installer. Lots of text scrolling by. I also attached a screenshot of what I see right as clover is booting up (I note I was actually able to go through the first phase of the installer using the sysctl version, but I was hitting an error and so I tried to reinstall using your files.

The text was updated successfully, but these errors were encountered:

ggctseng commented Jan 18, 2018

I started over with the Clover folder from the git with only these two changes:

• added FixHeaders_20000000 (this got rid of the weird error above in the 2nd screen shot).
• removed IONVMeFamily patches

and was able to boot to the installer, formatted the drive as APFS using Disk Utility, and then ran the first install portion. Then rebooted and ran the second install portion, so it looked like the install finished.

However, when trying to boot into macOS right after the second install portion, the system restarts.

Here’s what I see when I boot into clover, in addition to my USB entry:

• Boot FileVault Prebooter from Preboot
• Boot macOS Install Prebooter from Preboot
• Boot macOS from Macintosh HD
• Boot Recovery from Recovery

Should I see the first 2 entries in clover? I’ve tried booting using the first 3 entries, starting with the Boot macOS from Macintosh HD option. Same results.

I feel I am really close, but stuck and am hoping there’s help!

Here’s my current CLOVER folder:

I was able to take a video and put together the boot screens.

ggctseng commented Jan 18, 2018 •

But not sure if the Boot macOS Install Prebooter is supposed to be there.

P013onEr commented Jan 18, 2018 •

I met this problem after I upgrade S to HS , like this syscl#171
and I also found @ZombieTheBest https://www.tonymacx86.com/threads/solved-kernel-panic-10-13-2-update-cant-even-install.241361/
BUT how to solve it ?

rpruden commented Jan 18, 2018 •

You can hide the Preboot entries using your config.plist. The name of the entry you will want to hide will be called «Preboot» without the quotes. It’s under the GUI tab in Clover Configuration Editor.

When I first finished my upgrade to HS, I was getting a boot loop. Some kernel panic and then a reboot. I was able to resolve it by changing my SMBIOS from 13,2 to 13,3. Give that a try. I also noticed that running the latest Deploy.sh seems to make my config.plist unreadable by clover configuration editor so I am not sure what is breaking that. Be sure that your config.plist isn’t corrupted. You may need to generate a completely new SMBIOS using the 13,3 model type.

ggctseng commented Jan 18, 2018

@rpruden My install is a completely new install and I haven’t been able to get into High Sierra yet, but changing SMBIOS from 13,2 to 13,3 still results in boot loop. I’m going to try and generate a new SMBIOS because I don’t have anything in there right now.

ggctseng commented Jan 18, 2018

Just as a note, I’m getting errors with Apple Keystore and apfs key bag so I’m not sure if it’s something related to «security». I formatted the drive with just APFS (not APFS encrypted).

rpruden commented Jan 19, 2018

@ggctseng So you have prepped the USB (using current version of Clover and the Clover folder from the build on this repo), booted from it and ran the install. Install has completed but you have not been able to make it in to MacOS yet. Is that correct? Have you hit F4/FnF4 at the clover screen before trying to boot in to OSX?

Have you tried using Verbose and Safe Mode along with the 13,3 SMBIOS to get in to the install to ensure that it finished everything that it needed to finish? After my install was done, I would just get an Error icon if I tried to boot to it. After that, I just booted to clover, hit F4 then Fn+F4, waited a minute then adjusted the SMBIOS at the clover boot screen (Options Menu) and was able to get in. From there, I then installed clover to the SSD and created a new SMBIOS from Clover Configurator, then ran Deploy.sh.

I hope that you can find you way to the end on this.

ggctseng commented Jan 19, 2018

So you have prepped the USB (using current version of Clover and the Clover folder from the build on this repo), booted from it and ran the install. Install has completed but you have not been able to make it in to MacOS yet. Is that correct? Have you hit F4/FnF4 at the clover screen before trying to boot in to OSX?

Yes and yes. I was able to boot into the install after just adding the Fix_Headers (see my 2nd post) and I believe install has completed because I’ve gone through the first and second reboots. I just didn’t know if I’m supposed to have «Boot macOS Install Prebooter from Preboot». Do you still have this entry?

Have you tried using Verbose and Safe Mode along with the 13,3 SMBIOS to get in to the install to ensure that it finished everything that it needed to finish? After my install was done, I would just get an Error icon if I tried to boot to it. After that, I just booted to clover, hit F4 then Fn+F4, waited a minute then adjusted the SMBIOS at the clover boot screen (Options Menu) and was able to get in. From there, I then installed clover to the SSD and created a new SMBIOS from Clover Configurator, then ran Deploy.sh.

I haven’t tried Safe Mode, but regular boot with the SMBIOS to 13,3 in config.plist still doesn’t work. I’ll have to double-check and try adjusting SMBIOS using the clover boot screen.

So you didn’t have any patched items in your APCI?

ggctseng commented Jan 19, 2018 •

THIS IS THE SOLUTION REFERENCED IN MY FIRST POST

@rpruden Update. I am able to boot into High Sierra after I started with a minimal install of CLOVER using Rehabman’s guide here:

Note that this is not the clover configuration I used to install High Sierra, just to boot into it after I installed it using the CLOVER folder I attached above.

For prosperity’s sake I am attaching it here.
CLOVER.zip

First thing I did is get the laptop display working properly
Interestingly, I noticed I had a lot of artifacts because I don’t think I had the ig-platform-id set properly (it was 0x191b0000 by default from Rehabman’s config.plist repository but I see it is 0x19260004 in ZombieTheBest’s config.plist). Regardless, I was able to connect my Dell U3818DW monitor to USB-C and it was able to use both displays at full resolution (without the artifacts on the internal display). I installed the supplemental 10.13.2 update, rebooted and then the laptop display wouldn’t work (it just ended at the last printout of the verbose boot log). However, I was able to plug the my U3818DW and the picture showed up there (so maybe one way to debug your screen is to have an external monitor handy). Once I changed the ig-platform-id to 0x19260004. The laptop and U3818DW seem to work—and the display hot plugs! Not sure if USB works though.

Now the real work begins to start getting everything to work.

rpruden commented Jan 19, 2018

@ggctseng Fantastic! I am so glad that you got it up and running. These things can be a white rabbit chase sometimes. I am going to check that ig-platform-id setting on mine, because ever since I switched to High Sierra, I have been unable to use my external monitor. I’m using a Dell P2715Q and I’m only making it work via a crappy USB adapter right now. I would really love to get DisplayPort via USB-C working again. Just to confirm, your USB-C DisplayPort connection works even if you weren’t plugged in at boot?

To answer your earlier question, yes I still have the reboot to FileVault and the Reboot to install entries. They never went away so I just hid them in clover.

ggctseng commented Jan 19, 2018 •

@rpruden It seems totally random sometimes, though I’ve learned from my previous Hackintosh experience (don’t know how relevant this is now because that was back in Yosemite and Clover was catching on) that sometimes it was because I didn’t rebuild my cache while other times I didn’t save something where I thought I did.

Re: USB-C. Yes, I have been able to plug in the monitor after boot (to clarify, the config.plist is NOT the one modified by deploy.sh but it’s the bare minimum one I used to finally boot into the installer, which I attached to the posts a couple of posts above). I note that the U3818DW has a USB-C port (provides PD so charges laptop too, so awesome) so that is what is directly hooked up to the laptop—not being familiar with the DP standard yet, not sure if the display signals are going over as DP or USB-C. The one quirk I’ve noticed so far is that randomly the screen will black out for a few seconds, then come back on. The U3818DW has a USB 3.0 hub that’s assignable to USB-C too, but I haven’t been able to test whether the hub is recognized by the laptop.

ggctseng commented Jan 19, 2018

@rpruden I’m slowly adding in patches, etc. to enable features, but I’m presuming you have the configuration I do (QHD, i7, sk Hynix pc300 SDD). Would you mind sharing your config.plist and current Clover folder-with your SMBIOS info and ACPI folders removed, of course?

aizigao commented Jan 20, 2018

same problem after upgrade from 10.12.6, mark

ggctseng commented Jan 20, 2018

@aizigao Are you referencing the booting issue? You can try the Clover that I put a few posts up. Backup your current clover completely.

aizigao commented Jan 20, 2018 •

@aizigao Are you referencing the booting issue? You can try the Clover that I put a few posts up. Backup your current clover completely.

I use you clover and enter system, but screen is break

what is next step to do, should I run ./Deploy to fix it?

aizigao commented Jan 20, 2018

@ggctseng My machine use 0x19260004 is work great, 👍

ggctseng commented Jan 20, 2018

Yeah. I forgot to put that into the config.plist. Now it’s patching and etc. for you.

rpruden commented Jan 22, 2018

not sure if the display signals are going over as DP or USB-C. The one quirk I’ve noticed so far is that randomly the screen will black out for a few seconds, then come back on.

That screen flicker is something I have seen a lot with DisplayPort. I would be willing to bet you are sending DisplayPort over USB-C. If you click Apple > About this Mac > System Report > Graphics/Displays I believe it will tell you if you are using Display port. Mine is blank because I am using USB adapters right now though.

I will upload a copy of my clover folder and config.plist. I think we are using the same model. (QHD, i7, but with a replaced NVMe Toshiba SSD) Perhaps you will be able to help me fix it.

rpruden commented Jan 22, 2018

@ggctseng Attached is my CLOVER folder along with my config.plist. I removed the serials from the SMBIOS.

ggctseng commented Jan 23, 2018 •

@rpruden I think we should move the discussion to the other thread you created and I can mark this as solved, but one last note is that, yes, the U3818DW is sending DP over USB-C as confirmed using System Report.

Источник

[Solved] Boot FileVault Prebooter from Preboot.

sanyi83

I have a Permanent Solution to this problem.
Add Preboot and Recovery in HIDE VOLUME pane in the GUI section of clover.
This will remove all redundant boot entries.

BreBo

Moderator

Westsurf

claaron1000

claaron1000

Just incase it can help somebody else, I searched for the install error from log file «failed to locate volume with uuid» and found this thread right off the bat

which lead to this Guide

Which was the original page I found before vacation. Now if I can just get this update to install.

UPDATE: So. like some others I deleted everything that was there but did still had a «Prebooter» option in Clover. I ended up using terminal to delete the volume entirely.

diskutil list (to find the disk number disk1s2 in my case)
diskutil mount disk1s2 (to see what was inside the volume just for giggles)
diskutil unmount disk1s2
diskutil apfs deleteVolume Prebooter

Rebooted and only my high Sierra and recover entries were left. System booted fine and installation of Mojave when smoothly. Hope this may help others who search.

Источник