Jump to content
xpamamadeus

Ozmosis

5,903 posts in this topic

Recommended Posts

Advertisement

;((

 

I have yet to try all this new stuff. But I have been reading every post. With this new version, am I still supposed to add the firmware parameters in default, etc etc.

 

What should be different then the previous one you posted.

 

Thanks

Share this post


Link to post
Share on other sites

What should be different then the previous one you posted.

 

Im trying to patch type0->BiosSegment as suggested by bs0d to prevent firmware check error during installation.

Share this post


Link to post
Share on other sites

Its working! Thanks to cecekpawon, modbin and entire crew of community involved into this great project! c1c02dfde9c00dbcc0b1b79b6c4d558c.jpg


Sent from my iPhone using Tapatalk4a350723f0713a5ab75192273beb1c6b.jpg

Share this post


Link to post
Share on other sites

Sorry to ask, so, with this new OZ version. What is it required at the end? Only update the fss? Or also FakeSMC, defaults.plist?

Share this post


Link to post
Share on other sites

Guess its only oz wich needed patching. Devs could say more. Whats import: it works!

4dddd7640e2d7d702b14223b2915ac87.jpg

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Guess its only oz wich needed patching. Devs could say more. Whats import: it works!

4dddd7640e2d7d702b14223b2915ac87.jpg

 

 

Sent from my iPhone using Tapatalk

 AWesome, will test in a bit.

Share this post


Link to post
Share on other sites

I can confirm HFS+ install from flashdrive with only OZ (i have no room for apfs in bios, when i put it in third section- its not working). 

So this OZ fresh and should be used as default one. 

Share this post


Link to post
Share on other sites

Im trying to patch type0->BiosSegment as suggested by bs0d to prevent firmware check error during installation.

 

Would that eliminate the need for FF & FFM in Defaults.plist ?

I built the rom image will test it after I am done with the russian method which failed with Apple Installer but might still work with Pacifist (under test atm)

Share this post


Link to post
Share on other sites

@cecekpawon you´re the man :D

It works I write this from a freshly installed HighSierra Copy just using OZ :D

 

Well I think "Ooops you did it again" with a little help from @bsod pointing you in the right direction. OZ does now boot and install HighSierra like a breeze thank you for that :D

Share this post


Link to post
Share on other sites

@cecekpawon & other developers thanks for your hard work.@cecekpawon I have loaded you latest oz2a file to my  Gigabyte z97PD3 Bios. and it as improved the install.

could someone point me to how I can update my smbios to date 05/01/2017 has the install as it showing verify ferm wear eeror  

Share this post


Link to post
Share on other sites

Need braveheart testers >>>

 

@cecekpawon and @modbin, if you was women then I could send you an very hot and fresh kiss, but as you're THE MAN'S, respectable  :wub:  :thanks_speechbubble:  :thanks_speechbubble:  :thanks_speechbubble:  :thanks_speechbubble:, and I wish for you all the best in every kind of think you putted your hands! Thank's modbin, thanks cecekpawon :wink_anim:  

Share this post


Link to post
Share on other sites

@cecekpawon & other developers thanks for your hard work.@cecekpawon I have loaded you latest oz2a file to my  Gigabyte z97PD3 Bios. and it as improved the install.

could someone point me to how I can update my smbios to date 05/01/2017 has the install as it showing verify ferm wear eeror  

 

You're welcome my friend, you need also to change bios date, for example: iMac14,4 IM144.88Z.0179.B30.>170501<1718  red numbers are Bios Date and it will be: 05/01/2017, this is why in OzmosisDefaults we will set it like that:

 

Bios Date

05/01/2017

Bios Version

iMac14,4 IM144.88Z.0179.B30.1705011718

 

:wink_anim: 

Share this post


Link to post
Share on other sites

The FirmwareUpdate datas come with 10.13 installer:

 

 

 

EFIPayloads:

 - IM101.88Z.00CC.B0C.1705021259
 - IM111.88Z.0034.B12.1705021416
 - IM112.88Z.0057.B0D.1705021559
 - IM121.88Z.0047.B33.1705101231
 - IM131.88Z.010A.B1C.1705011311
 - IM141.88Z.0118.B46.1705011412
 - IM142.88Z.0118.B46.1705011513
 - IM143.88Z.0118.B46.1705011514
 - IM144.88Z.0179.B30.1705011718
 - IM151.88Z.0207.B26.1705011718
 - MB61.88Z.00C8.B0A.1705021739
 - MB71.88Z.0039.B1A.1705021813
 - MBA31.88Z.0061.B12.1705022008
 - MBA41.88Z.0077.B32.1705022117
 - MBA51.88Z.00EF.B1B.1705011412
 - MBA61.88Z.0099.B52.1705011614
 - MBP101.88Z.00EE.B17.1705012106
 - MBP102.88Z.0106.B1C.1705011311
 - MBP111.88Z.0138.B38.1705011614
 - MBP112.88Z.0138.B38.1705011718
 - MBP61.88Z.0057.B1B.1705021138
 - MBP71.88Z.0039.B1A.1705021852
 - MBP81.88Z.0047.B39.1705101327
 - MBP91.88Z.00D3.B21.1705012105
 - MM41.88Z.0042.B0D.1705021222
 - MM51.88Z.0077.B31.1705011214
 - MM61.88Z.0106.B1D.1705011514
 - MM71.88Z.0220.B28.1705011413
 - MP61.88Z.0116.B44.1705011717
 - IM161.88Z.0207.B19.1705011046
 - IM162.88Z.0207.B19.1705011413
 - IM171.88Z.0105.B25.1704292104
 - IM181.88Z.0145.B07.1705082121
 - IM183.88Z.0145.B07.1705082121
 - MB101.88Z.0148.B00.1705090111
 - MB81.88Z.0164.B31.1705021217
 - MB91.88Z.0154.B21.1704292104
 - MBA71.88Z.0166.B29.1705011046
 - MBP114.88Z.0172.B23.1705011413
 - MBP121.88Z.0167.B31.1705011413
 - MBP131.88Z.0205.B21.1704292116
 - MBP132.88Z.0226.B24.1704292117
 - MBP133.88Z.0226.B24.1704292117
 - MBP141.88Z.0160.B00.1705082121
 - MBP142.88Z.0160.B00.1705082121
 - MBP143.88Z.0160.B00.1705090111


SMCJSONs:

 - Mac-031B6874CF7F642A: 2.14f24
 - Mac-189A3D4F975D5FFC: 2.16f68
 - Mac-27ADBB7B4CEE8E61: 2.15f7
 - Mac-2BD1B31983FE1663: 2.19f12
 - Mac-35C1E88140C3E6CF: 2.12f143
 - Mac-35C5E08120C7EEAF: 2.24f32
 - Mac-3CBD00234E554E41: 2.18f15
 - Mac-42FD25EABCABB274: 2.22f16
 - Mac-473D31EABEB93F9B: 2.36f97
 - Mac-65CE76090165799A: 2.33f10
 - Mac-66E35819EE2D0D05: 2.37f20
 - Mac-77EB7D7DAF985301: 2.17f7
 - Mac-7DF21CB3ED6977E5: 2.13f15
 - Mac-81E3E92DD6088272: 2.21f92
 - Mac-937CB26E2E02BB01: 2.27f2
 - Mac-9AE82516C7C6B903: 2.35f105
 - Mac-9F18E312C5C2BF0B: 2.26f2
 - Mac-A369DDC4E67F1C45: 2.31f36
 - Mac-A5C67F76ED83108C: 2.38f7
 - Mac-B809C3757DA9BB8D: 2.34f2
 - Mac-BE0E8AC46FE800CC: 2.25f87
 - Mac-DB15BD556843C820: 2.33f10
 - Mac-E43C1C25D4880AD6: 2.28f7
 - Mac-F60DEB81FF30ACF6: 2.20f18
 - Mac-FA842E06C61E91C5: 2.23f11
 - Mac-FFE5EF870D7BA81A: 2.32f20

 

 

Share this post


Link to post
Share on other sites

what is the actual SMC rev ? i think its not 130f3 from FakSMC.kext ?

 

thanks very much for your work here and your Knowledge....

Share this post


Link to post
Share on other sites

what is the actual SMC rev ?

- Try to: mount your ESP, search for EFI/APPLE/UPDATERS/MULTIUPDATER/*.smc if any, and run this command

- Copy from Clover source which heavily maintained by our friend @Sherlocks

- Or grab it from real macs :)

Edited by cecekpawon

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.

  • Similar Content

    • By partha.slg123
      Hackintosh High Sierra 10.13.3 USB Installer Boot Into USB DIrectly Enter Exit Option Menu. Clover Boot Menu Not Showing. Plz Help .................
       

       
      My System Specification :

      CPU : Core i5 6400
      MB : Asus H110M-CS
      RAM : 8GB DDR 4
      HDD : WD 1TB For Windows And WD 500 GB For Hackintosh
      Bootloader : Clover
    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      BDU_v2.1.2018.023b.zip
      MakeCloverBDUReadyZip.bat.zip
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
      BDU_v2.1.2015.016b.zip
      BDU_v2.1.2015.018b.zip
      BDU_v2.1.2016.019b.zip
      BDU_v2.1.2016.020b.zip
      BDU_v2.1.2017.021b.zip
      BDU_v2.1.2017.022b.zip
    • By cvad
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
       
       
       
      Feel free to "Rate File"
    • By MacNB
      Recently transition from ###### to Clover.
      All work great on my raging Dell530 (with Quad-core Xeon E5450).
      I can triple boot Snow-Leopard, Mavericks or Yosemite.
      Really love the way clover does dynamic patching.
       
      Decided to add a second drive that had the original Dell-installed Windows Vista.
       
      Question for the community: Is it even possible to boot legacy Vista on the second drive using Clover ?
       
      I ask because I cannot. I have searched and all topics discuss UEFI boot which is OK for Win7 and up.
      Vista does not support UEFI boot.
      And this good old Dell only has BIOS.
       
      Clover GUI lists two new partitions after the Recovery HD partition.
      The last one is called "Boot Windows from OS" (screenshot0):
       
      When I hit enter, the screen clears to black and Clover windows badge is displayed but does not boot.
      If I hit enter again, I see the Clover GUI again.
       
      It just will not boot Vista.
       
      Disk details are as shown:
      OSX-YS-Pro:~ MacNB$ diskutil list /dev/disk0    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *1.0 TB     disk0    1:                        EFI EFI                     209.7 MB   disk0s1    2:                  Apple_HFS OSX-SL                  803.3 GB   disk0s2    3:                  Apple_HFS OSX-MV                  153.3 GB   disk0s3    4:                  Apple_HFS OSX-YS                  42.4 GB    disk0s4    5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5 /dev/disk1    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:     FDisk_partition_scheme                        *750.2 GB   disk1    1:                 DOS_FAT_16 DellUtility             74.0 MB    disk1s1    2:               Windows_NTFS RECOVERY                10.7 GB    disk1s2    3:               Windows_NTFS OS                      739.3 GB   disk1s3 OSX-YS-Pro:~ MacNB$ OSX-YS-Pro:~ MacNB$ sudo fdisk440 /dev/disk1 Password: Disk: /dev/disk1 geometry: 91201/255/63 [1465149168 sectors] Signature: 0xAA55          Starting       Ending  #: id  cyl  hd sec -  cyl  hd sec [     start -       size] ------------------------------------------------------------------------  1: 06    0   1   1 -    8 254  63 [        63 -     144522] DOS > 32MB    2: 07    9  13   5 - 1023 254  63 [    145408 -   20971520] NTFS         *3: 07 1023 254  63 - 1023 254  63 [  21116928 - 1444028416] NTFS          4: 00    0   0   0 -    0   0   0 [         0 -          0] unused       OSX-YS-Pro:~ MacNB$    FDISK shows that the 3rd partition is ACTIVE on the Vista drive (disk1).
       
      Clover is installed on EFI partition on the OS X drive (disk0).
       
      Config.plist attached.
      debug.log attached.
       
      If I boot from a Chameleon USB-stick, I can select the OS partition and it boots, but Clover does not.
       
      Edit: I can boot Vista via the BIOS by hitting F12 and selecting the vista hdd.
      screenshot0.bmp
      MacNB-debug.log.zip
      MacNB-config.plist.zip
      MacNB-530-Generic.zip
    • By Soeren_DK
      Hi there.
      I'm new to this site but not totally new to hack. I've had a hack since 10.4 and the latest version I ran was 10.9, not totally fixed but it worked to what I needed. Now I want to make the machine run as good as it can. I can see there has been a lot of changes/upgrades/new solutions since I installed my hack and I have a hard time to catch up.  
      I've been able to boot and install macOSX and now I need the POST installation.
      I tried to install the clover EFI boot loader with these settings:
       
      and found the DSDT.aml and SSDT-0.aml from HERE
      found the apfs.efi
      and placed it in EFI -> EFI -> CLOVER -> driver64
      and these kext in here:

       
       
      But when I boot it up this is the first bootscreen I have. No partions, no mouse control, no nothing.

      if I exit clover this screen appear.

      and now everything works. 
       
      What is wrong?
      Cheers
      Soren
×