Jump to content
Frank Nitty

"The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged" - Help Please

84 posts in this topic

Recommended Posts

What worked for me regarding this OSInstall.mpkg problem I encountered while upgrading 10.13.2 :

 

- have Lilu updated to 1.2.1 and have Lilu plugins updated

- have the most recent version of Clover (r4334 at the time of writing)

- have the version of apfs.efi for 10.13.2

- and remove the installer.failurerequests file that previous installation attempts left over at the root of the disk

Share this post


Link to post
Share on other sites
Advertisement

It did not work for me, have any other ideas? I can not get in into Fusion Drive HD, the clover does not find the boot. I'm just getting into the test HD.

Neither the new installer I made from 10.13.2 on a flash drive wants to enter.

Have something I can try?

I don't understand your status.

What is that "the clover does not find the boot"?

What is your clover revision?

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

 

It did not work for me, have any other ideas? I can not get in into Fusion Drive HD, the clover does not find the boot. I'm just getting into the test HD.
Neither the new installer I made from 10.13.2 on a flash drive wants to enter.
Have something I can try?

 

 

Do you have apfsefi in clover/Drivbers64EFI folder on USB?

Share this post


Link to post
Share on other sites

I don't understand your status.

What is that "the clover does not find the boot"?

What is your clover revision?

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

Hi Sherlocks,

 

He has a Fusion Drive.  I noticed that with upgrade of 10.13.1 to 10.13.2 on a Fusion Drive (simulated in VMware), the update boot files were placed in the following folders:

 

com.apple.boot.S on the "Recovery HD" partition

com.apple.boot.P on "Boot OS X" booter partition

 

instead of com.apple.boot.R for a clean install on a newly prepared Fusion Drive...

 

 

 

 

post-846696-0-73536100-1512800076_thumb.png

post-846696-0-81408100-1512800093_thumb.png

post-846696-0-74775700-1512800136_thumb.png

 

 

 

Slice has fixed the detection of the com.apple.boot.# folder (where #=R, P or S) in Clover r4337/4339  but it seems like he forgot to add OS ver detection (code doesn't parse SystemVersion.plist in the com.apple.boot.# folder?)...

 

Boot log for Clover r4339

 

 

 

0:100  0:000  Starting Clover revision: 4339 on VMware, Inc. EFI

0:100  0:000  Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t GCC53 | -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: 10.13.2]

122:567  0:000  Loading boot.efi  status=Success

122:628  0:060  GetOSVersion: 10.12

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: BD4D2798

122:668  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !

122:670  0:002  Use origin smbios table type 1 guid.

122:674  0:003  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other

122:674  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.12

 

post-846696-0-86804500-1512800285_thumb.png

post-846696-0-77536100-1512800311_thumb.png

post-846696-0-53769100-1512800354_thumb.png

 

 

 

 

 

It did not work for me, have any other ideas? I can not get in into Fusion Drive HD, the clover does not find the boot. I'm just getting into the test HD.
Neither the new installer I made from 10.13.2 on a flash drive wants to enter.
Have something I can try?

 

 

@Vinicius,

 

Try the update with Clover r4339, but make sure to put FakeSMC and other essential kexts in /CLOVER/kexts/Other instead of /10.13.

Clover_v2.4k_r4339.pkg.zip

com.apple.boot.P.zip

com.apple.boot.S.zip

Share this post


Link to post
Share on other sites

Hi Sherlocks,

 

He has a Fusion Drive.  I noticed that with upgrade of 10.13.1 to 10.13.2 on a Fusion Drive (simulated in VMware), the update boot files were placed in the following folders:

 

com.apple.boot.S on "Boot OS X" booter partition

com.apple.boot.P on the "Recovery HD" partition

 

instead of com.apple.boot.R for a clean install on a newly prepared Fusion Drive...

 

 

 

 

Slice has fixed the detection of the com.apple.boot.# folder (where #=R, P or S) in Clover r4337/4339  but it seems like he broke OS ver detection in the process (code doesn't parse SystemVersion.plist in the com.apple.boot.# folder?)...

 

Boot log for Clover r4339

 

 

 

0:100  0:000  Starting Clover revision: 4339 on VMware, Inc. EFI

0:100  0:000  Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_APPLE_HFSPLUS_DRIVER -t GCC53 | -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: 10.13.2]

122:567  0:000  Loading boot.efi  status=Success

122:628  0:060  GetOSVersion: 10.12

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: BD4D2798

122:668  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !

122:670  0:002  Use origin smbios table type 1 guid.

122:674  0:003  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other

122:674  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.12

 

attachicon.gifBoot macOS InstallP from Boot OS X.png

attachicon.gifBoot macOS InstallS from Recovery HD.png

attachicon.gifBlock injected kexts for target version of macOS null.png

 

 

 

 

 

@Vinicius,

 

Try the update with Clover r4339, but make sure to put FakeSMC and other essential kexts in /CLOVER/kexts/Other instead of /10.13.

 

try this

test.zip

Share this post


Link to post
Share on other sites

try this

 

@Sherlocks,

 

Your test r4339 looks good. 

 

Boot log shows correct GetOSVersion and Block Injected Kexts Menu shows 10.13 detected...

 

4:048  0:000  Starting Clover revision: 4339 on CLOVER EFI
4:048  0:000  Build with: [Args: -x64 -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13.2 | XCODE: 9.2]
120:136  0:000  Loading boot.efi  status=Success
120:239  0:103  GetOSVersion: 10.13.2
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DE721718
120:527  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !
120:527  0:000  Use origin smbios table type 1 guid.
120:528  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\Other
120:528  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\RTL8192SUs.kext
120:560  0:032  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\NullEthernet.kext
120:564  0:003  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext
120:566  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
120:570  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
120:571  0:001    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
120:573  0:001  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext
120:582  0:009    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\VoodooBatterySMC.kext
120:586  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\PC8739x.kext
120:588  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext
120:591  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\GeforceSensor.kext
120:595  0:003  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\10.13

 

post-846696-0-26700500-1512805618_thumb.png

post-846696-0-00421000-1512805786_thumb.png

 

 

Thanks Sherlocks  :).

Share this post


Link to post
Share on other sites

Do you have apfsefi in clover/Drivbers64EFI folder on USB?

Yep, i have, but I solve my problem, thanks.

 

I don't understand your status.

What is that "the clover does not find the boot"?

What is your clover revision?

 

나의 LG-F800S 의 Tapatalk에서 보냄

I was able to solve by installing via flash drive 10.13.2 over 10.13.1, thanks. I have Clover 3443. 

The problem was in the second stage of the installation, appeared the message "OSInstall.mpkg missing ...", and I could not get back in 10.13.1 to delete the folder and download again. Whenever I tried to boot into the normal partition, I had the mesangem that I show in the photo. I was able to resolve only by initializing the installation through the flash drive and installing over 10.13.1.

post-748259-0-27652800-1512810130_thumb.jpg

Share this post


Link to post
Share on other sites

Yep, i have, but I solve my problem, thanks.

 

I was able to solve by installing via flash drive 10.13.2 over 10.13.1, thanks. I have Clover 3443.

The problem was in the second stage of the installation, appeared the message "OSInstall.mpkg missing ...", and I could not get back in 10.13.1 to delete the folder and download again. Whenever I tried to boot into the normal partition, I had the mesangem that I show in the photo. I was able to resolve only by initializing the installation through the flash drive and installing over 10.13.1.

attachicon.gif327c8528-3b1d-4c61-9503-6cbc9e92c5d0.jpg

Try to test test.zip file above

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
On 11/28/2017 at 6:40 AM, Awesome Donkey said:

It'll probably happen with 10.13.2 too, sadly. =\

I know I'm 2 years late w/ a response which has been in part due to my disgust w/ Apple, as well as w/ NVIDIA regarding their ludicrous nonchalant attitude for not releasing compatible drivers for Pascal GPUs so I never updated from 10.13.1, but after reading your following comment:

 

I downloaded and installed the version of Clover (r4334) you had linked in your comment onto my High Sierra HDD installation and nothing else and I was able to successfully update to 10.13.2 w/o having to create a new USB install. Just wanted to let you know that, and thanks.

Edited by Frank Nitty

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×