Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

ammoune78
ammoune78
Posted
Posted (edited)
14 minutes ago, cecekpawon said:

LOL really cant help your HD4600 @ammoune78

But, you might be interest to try this beast.

 

 

Don't worry, got the HD4600 working using 32 Memory and 128 DVMT in Bios settings, for the APFSLoader already on ROM this is why i reacted to @crusher. , now booting fine Mojave :frantics: Ozmosis is now like :robot: , but i'm boring MAN :whistle:

Edited by ammoune78
  • Like 1
Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

AppleLoadImage added into repo by savvas to get work with native / Apple ApfsJumpStart.
Form sources comment: ApfsJumpStart looking for AppleLoadImage to load apfs.efi
ApfsJumpStart --> AppleLoadImage --> apfs.efi
So ideally, AppleLoadImage need to be loaded first before ApfsJumpStart.

 

* It doesnt work with my pc. Attached compiled binary for anyone to test ;)

 

https://1drv.ms/u/s!AjxLshYT0HDug2LrpkE7XWBJ20XB

  • Like 4
Link to comment
Share on other sites
Kynyo
Kynyo
Posted
Posted (edited)

So I will remove APFSDriverLoader.

EDIT:

Tried only with AppleLoadImage, not working.

Rolled back to APFSDriverloader.ffs, all good.

Single problem remaining with Oz and mojave it's injection that i cant boot mojave installer. 

Says something like: "Couldn't get SMCProvider."

Edited by Kynyo
Link to comment
Share on other sites
savvas
savvas
Posted
Posted (edited)
On 6/23/2018 at 5:18 PM, cecekpawon said:

Erm @Kynyo AppleLoadImage designed to be load with ApfsJumpStart. While APFSDriverLoader should work ok, alone, without AppleLoadImage & ApfsJumpStart.

I forgot to mention about ApplePartitionInfo protocol which installs by Apple partition driver.

Apple's ApfsJumpStart depends on ApplePartitionInfo and AppleLoadImage protocols.

AppleLoadImage is just an abstraction over UefiLib's LoadImage

Edited by savvamitrofanov
  • Like 1
  • Thanks 1
Link to comment
Share on other sites
korlione2009
korlione2009
Posted
Posted
10 hours ago, savvamitrofanov said:

Я забыл упомянуть о ApplePartitionInfo протокола, который устанавливает драйвер раздела Apple.

ApfsJumpStart от Apple зависит от протоколов ApplePartitionInfo и AppleLoadImage.

AppleLoadImage просто абстракция над LoadImage UefiLib в

 

Не грузит твой драйвер апфс ни как, не хочет видить раздел после первой установки.

Link to comment
Share on other sites
savvas
savvas
Posted
Posted (edited)
1 hour ago, korlione2009 said:

 

Не грузит твой драйвер апфс ни как, не хочет видить раздел после первой установки.

Mobo from Gigabyte?

Old versions of firmware doesn't have PartitionDriver AT ALL! 

I won't support such things like Ozmosis and write guides how to make it work, if use it - you should do it yourself, not playing with firmware like a kid. 

So I have two ways to solve your problem:

1) update firmware to the latest version;

2) add PartitionDriver ffs from newer firmware with right boot order.

Edited by savvamitrofanov
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
7 hours ago, korlione2009 said:

 

Не грузит твой драйвер апфс ни как, не хочет видить раздел после первой установки.

Insert ApfsDriverLoader into ROM, after installing Mojave, do bcfg to add boot entry. Maybe the installed Mojave container partition is fs5, so:

fs5:

cd System\Library\CoreServices

bcfg boot add 1 boot.efi "Mojave"

Reboot and you should see the Mojave drive

Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted
On 10/15/2017 at 10:45 AM, cecekpawon said:

....

 

You may try another build here. Prev it used same instance of Clover Memlog lib.

 

With Oz, sorry I believe no.

 

:king:  :hammer:  :wallbash:  :boxing:  :geek:  :happymac:

 

Hi Cecekpawon,

 

AcpiPatcher and KernelPatcher are no more available with this link.

Can u update ?

  • Like 1
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted (edited)
4 hours ago, cecekpawon said:

Hey @FredWst

 

I moved the project over here

Read the wiki to extract the module(s)

 

KernextPatcher.efi from firmware does not work. (seems not last commit of GitHub)

Build version of your GitHub works.

Remember length taken to patch prelink was not enough. ;)

 

Fred

Edited by FredWst
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted (edited)
8 hours ago, crusher. said:

Download section and later just extract files in efi or ffs files

AM9ef.gif

 

I know that :)

This version is not working for me.

Fred

 

Edited by FredWst
Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

Thanks for video @crusher. !!!

 

@FredWst, Id like to know on what case why it doesnt work for you.

Would you like share your patches? Something like TRIM enabler patch? Im currently use it for 10.13.5 and its all ok for me.

**Attached my log.

 

5 hours ago, FredWst said:

Remember length taken to patch prelink was not enough. ;)

 

LOL yes, I remember that. But it should no longer problem now.

 

KernextPatcherLog.txt.zip

  • Like 1
Link to comment
Share on other sites
FredWst
FredWst
Posted
Posted
1 hour ago, cecekpawon said:

Thanks for video @crusher. !!!

 

@FredWst, Id like to know on what case why it doesnt work for you.

Would you like share your patches? Something like TRIM enabler patch? Im currently use it for 10.13.5 and its all ok for me.

**Attached my log.

 

 

LOL yes, I remember that. But it should no longer problem now.

 

KernextPatcherLog.txt.zip

 

Found my mistake with Crusher help. :)

 

Fred

  • Like 1
Link to comment
Share on other sites
TypeThree
TypeThree
Posted
Posted (edited)
On 6/23/2018 at 1:20 PM, Kynyo said:

Single problem remaining with Oz and mojave it's injection that i cant boot mojave installer. 

Tried to fix that, this is what @cecekpawon and I came up with. This is just a new approach / alternative way to make kext-injection work with Ozmosis and the newest OS.

Please don't confuse this with a new Oz Version, it is not!

 

To differentiate, the patch is called 167X-XMAX and is fully based on 167X-MASS but used extended with cecekpawons UEFTW-Tools.

 

To make kext-injection work with Mojave a few things are needed:

Using this Oz file you will not have working injection! You must use KernextPatcher with a special KernextPatcher.plist! This plist holds everything for injection from ML-->Mojave. The Plist is included into the following FFS, if you use the EFI version you need to use the attached Plist (which you can extend with your own (Kext/Booter...)-patches).

After several tests I can confirm that Kext Injection and installation with Mojave works using this Ozmosis + Kernextpatcher but we need braveheart testers.

To install Mojave use: Ozmosis 167X-XMAX, KernextPatcher with right Plist, EnhancedFat, ApfsDriverLoader, HFSPlus, latest FakeSMC and an updated defaults.plist (this is a template/example: Defaults.plist / OzmosisDefaults.ffs).

Also the use of AcpiPatcher is recommended to fix bad ACPI-Headers and apply renames.

 

Please use all these files at your own risk!

Good luck!

Edited by TypeThree
  • Like 5
Link to comment
Share on other sites
Kynyo
Kynyo
Posted
Posted (edited)

Installed, successfully using this methot and I can confirm that IT WORKS! Thank you!

At the first boot kernelcache its being verified "Invalid kexts allowed...", it restarts and after that it works as intended.

Now we'll need two more things: webdrivers and a new maxlimit usb patch for HighSierra but that'll be at the final release I guess.

Edited by Kynyo
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...