Jump to content

VultUx

Members
  • Content count

    131
  • Joined

  • Last visited

About VultUx

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
    Male
  • Location
    Brasil

Recent Profile Visitors

4,532 profile views
  1. Hi! Could you explain a little more how to do that? I have the 387.10.10.10.40.105 here but is a pkg I don't know how open it.
  2. VultUx

    Ozmosis

    Hi! Could you explain how you did? I gave up from APFS and return to HFS+ because even loading the APFS from prompt the boot entry never show up on UEFI boot menu.
  3. VultUx

    Ozmosis

    Hi guys! I have a very old Gigabyte B75M-D3H with Ozmosis working with MacOS Sierra. Now that I'm on vacation at work, I'll finally try to install the High Sierra, after read a lot of topics I managed to change my Ozmosis with the version High Sierra compatible (thks @ammoune78 to point the topic to download), then I was trying to install the apfs.ffs provided by @CrazyCreator. But I think I don't have enough space because every time I try to insert and save the new ROM I receive the error: Invalid UEFI volume. Is there something that I can remove from my ROM to free up some space? ps.: I have already the minimum installed (Hfsplus, EnhancedFat, SmcEmulatorKext, HermitCsmVideo, Ozmosis). Thank you guys for all the hard work.
  4. VultUx

    Ozmosis

    @davidm71 I have this problem all the time with ArchLinux when I install other OS that change de boot partition, like Win10 with EFI for example. What I do to solve this is boot Arch with pendrive and do the EFI boot for Arch again with GRUB. But I don't know how to do this with Ubuntu.
  5. VultUx

    Ozmosis

    Thank you! You was correct! And for my luck, I had written down the UUID that I had from the Chameleon and the MacAddress too, putting this information the correct UUID was generated again. Thank you guys for the ideias, I thought the HardwareSignature was a forced way like Clover does.
  6. VultUx

    Ozmosis

    Thanks for reply, but something very weird it's happen, I changed the HardwareSignature and HardwareAddress (macAddress) to other but the UUID didn't change?!?
 
 Then just for test I removed this fields from my Default.plist and still nothing changed?!? I will delete the default.plist to see if still works, maybe there is another default.plist somewhere...
  7. VultUx

    Ozmosis

    Hi guys! I'm having a problem with Hardware UUID - I force a UUID that I use since Chameleon because some programs use this to know if you they have had reinstalled in other system and count how many reinstall you did. I use the same UUID in Clover and there works fine and worked fine with Ozmosis until I have upgraded to MacOS Sierra, now even I forcing UUID on Default.plist the system change the UUID after boot. Is this happen with you guys? Here my Default.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Version</key> <string>1.0.1</string> <key>Timestamp</key> <integer>0</integer> <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key> <dict> <key>BiosVersion</key> <string>MP61.88Z.0116.B04.1312061508</string> <key>BiosDate</key> <string>03/09/13</string> <key>ProductName</key> <string>MacPro6,1</string> <key>ProductFamily</key> <string>Mac Pro</string> <key>SystemVersion</key> <string>1.0</string> <key>SystemSerial</key> <string>F5KLCW72F693</string> <key>ProductId</key> <string>Mac-F60DEB81FF30ACF6</string> <key>BoardVersion</key> <string>10</string> <key>BaseBoardSerial</key> <string>C02140302D5DMT31M</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>ChassisAssetTag</key> <string>Pro-Enclosure</string> <key>EnclosureType</key> <integer>7</integer> <key>ProcessorSerial</key> <string>F5K3474002XFNN21A</string> <key>HardwareAddress</key> <string>FC:AA:14:F5:E1:DC</string> <key>HardwareSignature</key> <string>5BF6E328-FDF2-57E0-AF18-9F767AC78912</string> <key>FirmwareVendor</key> <string>Apple</string> </dict> <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key> <dict> <key>BootEntryTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label ($platform.$major.$minor)</string> <key>DarwinCoreStorageTemplate</key> <string>$label</string> <key>AndroidDiskTemplate</key> <string>$label</string> <key>AndroidDiskOptionTemplate</key> <string>initrd=$initfs root=UUID=$uuid androidboot.hardware=android_x86 ro SRC=$path</string> <key>LinuxDiskTemplate</key> <string>$label $build</string> <key>LinuxDiskOptionTemplate</key> <string>initrd=$initfs root=UUID=$uuid ro</string> <key>LinuxRescueDiskTemplate</key> <string>$label Rescue</string> <key>LinuxRescueOptionTemplate</key> <string>initrd=$initfs root=UUID=$uuid ro</string> <key>EnableKextPatcher</key> <true/> <key>TimeOut</key> <integer>7</integer> <key>DisableNvidiaInjection</key> <true/> </dict> <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-v nv_disable=1</string> <key>csr-active-config</key> <integer size=32>0x7F</integer> </dict> </dict> </plist And here the UUID after boot Sierra with Ozmosis.
  8. VultUx

    Ozmosis

    Thanks!
  9. VultUx

    Ozmosis

    Hi, could you share where did you find this patch? I've searched the forum but I didn't find anything about the patch.
  10. VultUx

    [pre-releases] macOS Sierra

    Humm... I don't remember how much memory El Capitan used, but in some OS memory used don't mean really used, just allocated by the OS, maybe they are using this way now. For Hackintosh in general the Gigabyte mobos are the best IMHO.
  11. VultUx

    [pre-releases] macOS Sierra

    No, everything normal here. Installed without any issue, even Nvidia Webdriver worked, don't need to update.
  12. VultUx

    Ozmosis

    And I can't get NVIDIA drivers to load. I've reinstalled them and typed sudo nvram boot-args="nvda_drv=1" Try that: sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="nvda_drv=1"
  13. VultUx

    Ozmosis

    Thank you Alberto! Now worked, but if I reenable SIP then the boot process keep rebooting. Probably Apple changed something related with SIP.
  14. VultUx

    Ozmosis

    Do you guys are having problem with the last El Capitan update 10.11.04? Here it's freezing, after boot to install update with OZMOSIS 167X-MASS. Already deactivated Nvidia driver, cleared NVRAM with Option+Command+P+R.
×