Jump to content

ntsmkfob

Donators
  • Content Count

    367
  • Joined

  • Last visited

About ntsmkfob

  • Rank
    InsanelyMac Sage

Recent Profile Visitors

12,809 profile views
  1. EFI is a separate partition that has to be mounted to open. Use a tool like Hackintool or EFI Agent to see which disks have an EFI and mount them to make changes.
  2. On my Catalina system, I did ls fs1:, ls fs2: etc. 2 of the filesystems only had a folder with a long UUID starting with the letter A. I did an ls fs4:\A and hit the tab key to fill the UUID and then Enter to see what was there. One of these folders had just a System directory, which led to a Library and then a CoreServices folder, which contained boot.efi. I set up a boot entry for that boot.efi as explained above. I assume it is a Preboot volume, but it is the one I use to boot Catalina, once I put it first in the boot sequence in the BIOS and then made it the startup disk in Catalina.
  3. KernextPatcher.plist should be in the EFI folder, not the /EFI/Oz folder.
  4. Sorry - another error on my part! The Locked Files\Boot Files bit was to get the install restarted, and isn't present after the install completes. Glad you worked through it. You usually only need to zap the PRAM to load a modified Defaults.plist. If you install a new BIOS image, it zaps the PRAM and your BIOS settings anyway.
  5. My apologies, I missed part of a statement, and you're right it should be backslashes. So if you say you found the boot.efi on \System\Library\CoreServices\Locked Files\Boot Files\ on fs2: then you need to type into the shell: bcfg boot addp 4 fs2:\System\Library\CoreServices\Locked Files\Boot Files\boot.efi "Mojave" If you reboot and press F12 to get the boot menu, Mojave should be listed. As long as you have the Defaults.plist in the /EFI/Oz folder it will have been read in when the screen flashed different colours. You can type 'ls fs2:\EFI' to check for the Oz folder.
  6. The Ozmosis BIOS has a built in Defaults.plist that contains the MacPro 3,1 definition, and to override that it needs to have loaded into NVRAM, a Defaults.plist from the EFI/Oz directory of the first drive it interrogates (SATA 0), with either a Mac mini or an iMac 13,2 definition. Command+Option+P+R at boot time (easier from the Shell prompt) will load an available /EFI/Oz/Defaults.plist into NVRAM and then restart the PC with the new definition. It doesn't reload the Defaults.plist at every boot, only when the Cmd+Opt+P+R occurs or a new BIOS is uploaded. You need to find the filesystem that has boot.efi present. At the shell prompt type ls fs0: If you see s System directory you've probably found it. If not try ls fs1:, ls fs2: etc until you do. Once found, type 'bcfg boot dump' to list your boot list - let's say you already have 3 entries Replace fsx: below with the fs1: or fs2: etc. where you found the \System folder now type bcfg boot addp 4 fsx:\Sy and hit the tab key to select System type Li and hit tab type Co and hit tab type Lo and hit tab type Bo and hit tab You should now have bcfg boot addp 4 fsx:\System\Library\CoreServices\Locked Files\Boot Files\ If it didn't work you may be on the wrong files system - try more ls fsx: commands increasing the number for x each time add boot.efi then a space to the end and finally add your preferred name for the volume in quotes e.g. "Mojave" You should now have (assuming 4 is the correct value for your system) bcfg boot addp 4 fsx:\System\Library\CoreServices\Locked Files\Boot Files\boot.efi "Mojave" Press enter. You can type bcfg boot dump to list the entries. Type reset to reboot and hit F12 to get the boot list again and choose Mojave. You can then set Mojave as the startup disk in SysPref once booted, and move it to the top in the BIOS boot options as well. Remember you will also need the KernextPatch.plist in the EFI partition. Connecting another disk that has an EFI partition may change the filesystem (fsx:) number and invalidate the above. It's all different for Catalina.....
  7. If it's not creating the Oz directory where you expect it to be, you should check any other disks you have for an EFI directory, which is being used as the boot device instead of the one you expect. Make sure the Mac drive is connected to SATA port 0 on the motherboard. That will then be the drive the BIOS goes to for the EFI.
  8. You need a Defaults.plist in the EFI/Oz folder of your boot device. Back in this topic there is a recent example of a plist with an iMac (13,2) configuration. Others here successfully use a MacMini setup. All you should need to do is insert a SystemSerial number and BaseBoardSerial number - probably ones you used previously. You should also put kernextpatcher.plist (below) in the EFI partition. Hold down F12 during boot to get to the boot menu. When there press Cmd+Option+P+R simultaneously to get the BIOS to read the new Defaults.plist. You'll need to go into the UEFI shell to find the file system to boot. If all OK you can update the BIOS to XMAX-E and try again. KernextPatcher.plist
  9. No, I have a QUO motherboard as the topic title indicates.
  10. Thanks to TypeThree, IronManJFF, elviejo and probably a load more unnamed hackers, the update from Mojave to Catalina 10.15.2 is pretty painless. Whether all of the following is necessary, I can't say, but what I did after downloading Install MacOS Catalina app from the app store was: Put new format Defaults.plist in EFI/Oz per IronManJFF's post with latest firmware info Put updated KernextPatcher.plist in EFI (needs 10.15 patches) Ozmosis-Catalina.rom from elviejo's post installed and configured with Internal GPU disabled and PEG selected instead of Auto, plus my usual profile1 for RAM and vt-d for Parallels. I have an AMD RX560 video card. Put latest Lulu.kext, WhatEverGreen.kext and FakeSMC.kext in /Library/Extensions chmod -R 755 /Library/Extensions/* chown -R root:wheel /Library/Extensions/* touch /Library/Extensions This should all boot into Mojave OK Run the Install Catalina app. There comes a point where my screen went black, but with lots of disk activity, probably as it shifted stuff around to create the system and data volumes. Came back 20 minutes later to the login screen for Catalina! Thanks again to the people who did all the hard work behind the scenes.
  11. You may be getting the mismatched kexts msg because Fakesmc is still in the cache. Rebuild your cache to remove it completely.
  12. Best way to get there is to hold down F12 during boot to get to the boot list menu. Then you have plenty of time to hold down Cmd+Option+P+R keys.
  13. Replace the bios info in your version with the code below. Also, use clover configurator to generate a valid serial number, then add 5 extra chars for the baseboard number. Don't forget to cmd/option/P/R to reload the bios and pull in the updated plist. <key>BiosDate</key> <string>06/13/2019</string> <key>BiosVersion</key> <string>IM131.88Z.F000.B00.1906132045</string> <key>EfiVersion</key> <string>287.0.0.0.0</string> <key>FirmwareFeatures</key> <integer>0xE00DE137</integer> <key>FirmwareFeaturesMask</key> <integer>0xFF1FFF3F</integer> <key>ProductId</key> <string>Mac-FC02E91DDD3FA6A4</string> <key>ProductFamily</key> <string>iMac</string> <key>ProductName</key> <string>iMac13,2</string>
  14. Hi IronmanJFF, Here's the darwindumper output plus the kernextpatcher plist I'm using. I have a Xeon E3-1240 v2 CPU, just in case that makes a difference. DarwinDumper_3.0.4_26.09_08.30.53_iMac13,2_Ozmosis_1.03.167X-XMAX_Unknown_18G95_John.zip
×