Ozmosis

al6042 · November 13, 2017

@ammoune78:

Since the kext will not be added to the rom itself, the size doesn't matter...

Since all those kexts, that some folks add to their rom, except for any kind of FakeSMC, the kext development is sometimes so fast, that any OZM-ROM creator might have to update his/her roms every other month...

The idea of an modular structure, which can be easily done by putting those kexts and other addons into the EFI-Partition, is - in my opinion - neglected.

Rather use the available rom space for important tools, like the kernextpatcher, and keep the rom as flexible as possible...

This also means to create roms without any sensor kexts, to be able to use the rom for Pascal Nvidia cards, without trying to troubleshoot the already known issue with the GPUSensors.kext...

Some guy said "Keep it simple..."

keeping a rom as modular as possible would keep it simple...

ammoune78 · November 13, 2017

Can you explain more or send a link to post about bcfg? I missed it somehow.

So, I tried your DSDT and SSDT with my F8g bios and can confirm it works fine, thank you very much. The reboot and shut down problems gone, System works.

But I can't boot without VoodooTSC or NullCpu, if I remove one of them or both, the boot hangs on the first step immideately after apple logo shown. With them I can normally work.

First go to cecekpawon post #5503# , then place does files here:

In

└── EFI

├── KernextPatcher.efi

├── KernextPatcher.plist

├── AcpiPatcher.efi

├── AcpiPatcher.plist

├── KernextPatcherLog.txt

└── AcpiPatcherLog.txt

Download this Shell #5580# and put it in Firmware or Efi/BOOT/.

Now reboot and go to Shell by selecting UEFI OS from F12, at the prompt wright this:

fs0:

cd EFI

bcfg driver add 0 KernextPatcher.efi "KernextPatcher"

Note that the fs0: for you will not work maybe, so you have to try fs1: fs2: until you get the EFI that have the files needed to be registered.

Why not trying the F7 that I've posted instead of f8g, you can update the ROM with UBUTool in order to have latest OROM's, result will be better than f8g.

What CPU you use because I boot without "VoodooTSC or NullCpu", Ozmosis will detect automatically your CPU and start booting, you just need the InjectorKext 1.3 to detect SATA Ports. Please write down your signature.

@ammoune78:

Since the kext will not be added to the rom itself, the size doesn't matter...

Since all those kexts, that some folks add to their rom, except for any kind of FakeSMC, the kext development is sometimes so fast, that any OZM-ROM creator might have to update his/her roms every other month...

The idea of an modular structure, which can be easily done by putting those kexts and other addons into the EFI-Partition, is - in my opinion - neglected.

Rather use the available rom space for important tools, like the kernextpatcher, and keep the rom as flexible as possible...

This also means to create roms without any sensor kexts, to be able to use the rom for Pascal Nvidia cards, without trying to troubleshoot the already known issue with the GPUSensors.kext...

Some guy said "Keep it simple..."

keeping a rom as modular as possible would keep it simple...

Excuse me IMHO, if you put Oz then the ROM will no longer be a virgin, space, kext or whatever you're talking about, you touched your firmware, modular as it is, updated OROMs and such things, are the same! You just have to know what you do, I keep all things in firmware, I'm aware about flashing many times, I update it only until the Big Official.

Kernext and ACPI patchers are in Firmware, I only keep the Shell on the drive with this 64 mb ROM, and it's simple, i don't bother my time for an small piece of update if my system is running well

I forgot, compared to yours, the AppleALC size of mine is only 20 Kb and contain no extra, just the needed and I made kext and ffs, I let him to make choice between Kext or ffs,

You maybe forgot Fredde2209 AppleALC topic also, which is already here in Ozmosis general page.

in your web site you can not make AppleALC kext and ffs for each codec ID, in order to simplify the life for users, like you said: I will take him by the hand? The source code is already waiting for it!

Anyway, if no xpamamadeus topic maybe, German website will remain to other boot loaders only!

Edited November 14, 2017 by ammoune78

Tusskan · November 13, 2017

I have this stored as AddBoot.nsh in EFI\Tools:
@echo -off

if x%1% == x then
  echo Missing argument!
  echo Usage:
  echo AddBoot UUID
  goto END
endif

set -v DiskUUID %1%
set -v macOS notfound
set -v Recovery notfound
set -v UefiShell fs0:\EFI\Shells\HermitShellX64.efi

for %a run (0 9) 
  if exist fs%a:\%DiskUUID%\System\Library\CoreServices\boot.efi then
    set -v macOS fs%a:\%DiskUUID%\System\Library\CoreServices\boot.efi
    goto FSFOUND
  endif
endfor

goto NOTFOUND

:FSFOUND

for %a run (0 9) 
  if exist fs%a:\%DiskUUID%\boot.efi then
    set -v Recovery fs%a:\%DiskUUID%\boot.efi
  endif
endfor

bcfg boot rm 1
bcfg boot rm 1
bcfg boot rm 1

if not %macOS% == notfound then
  bcfg boot add 1 %macOS% "macOS"
endif

if not %Recovery% == notfound then
  bcfg boot add 2 %Recovery% "Recovery"
endif

if exist %UefiShell% then
  bcfg boot add 3 %UefiShell% "HermitShell"
endif

:NOTFOUND

bcfg boot dump

:END
After a Ozmois reset, I boot to HermitShell and call the script like that:
FS1:
ls
AddBoot X[TAB][RETURN]
X is the first char from the UUID that was listed by 'ls'.
The TAB to complete the selection and RETURN...

I use this script with HermitShellX64 (EFI\Shells\HermitShellX64.efi)

Be aware that bcfg from HermitShell uses 1 for the first entry instead of 0 like many other shells.

Well, Booted from a shell in USB and ran this and aut added the Mac OS X entry to my menu.

that's cool though.

If "manually loading" were equal to re type & entering those entry from shell after each boot sure that was pain man. But if we could just manually add it with bcfg (after some entries gone / nvram reset) then it must be worth to do imo. You can start to improve script provided by @uglyJoe to feed your needs. Or with @dosdude1 script (designed for auto boot). Or Bless (with some other tool there).

Can't we mod a shell to load these script at each boot to verify the boot entries and reload them?

Can this also auto load oz and shell from disk without the need to inject oz into rom?

This is another script for adding the drivers from disk.

Put Ozmosis.efi, HFSPlus.efi, APFS.efi and HermitShellX64.efi (renamed to ShellX64.efi) into the efi root directory.

AddDriver can take a given FS number or is searching for ozmosis.efi to get the correct one.

The script puts ShellX64.efi as a boot entry and reboots the system.

After reboot I execute the AddBoot.nsh from above.

AddDriver.nsh
@echo -off
set -v EfiFs 0

## Read user input
if not x%1% == x then
  if exist fs%1%:\ozmosis.efi then
    set -v EfiFs %1%
    goto FSFOUND
  else
    goto END
  endif
endif

## Search FS
for %a run (0 9) 
  if exist fs%a:\ozmosis.efi then
    set -v EfiFs %a
    goto FSFOUND
   endif
endfor

goto END

:FSFOUND
echo Found driver at fs%EfiFs%:\

## Remove old drivers
bcfg driver rm 1
bcfg driver rm 1
bcfg driver rm 1

## Add drivers
bcfg driver add 1 fs%EfiFs%:\apfs.efi APFS
bcfg driver add 2 fs%EfiFs%:\hfsplus.efi HFSPlus
bcfg driver add 3 fs%EfiFs%:\ozmosis.efi Ozmosis
bcfg driver dump

## Add boot entry for Uefi Shell
set -v UefiShell fs%EfiFs%:\ShellX64.efi
if exist %UefiShell% then
  bcfg boot rm 1
  bcfg boot rm 1
  bcfg boot rm 1
  bcfg boot add 1 %UefiShell% "UEFI Shell"
endif

## Reboot
echo ""
echo Reboot system now?
pause
reset

:END
echo ""
echo ERROR: Driver not found!
Some more scripts to use with HermitShellX64:
Put them into EFI\Tools or any other directory that belongs to the shell environment (PATH). Type 'set' to verify.

Than you can execute them from anywhere in the shell.

Disable SIP
@echo -off

setvar -guid 7C436110-AB2A-4BBB-A880-FE41995C9F82 csr-active-config =67000000

setvar -guid 7C436110-AB2A-4BBB-A880-FE41995C9F82 csr-active-config
Enable SIP (except NVRAM)
@echo -off

setvar -guid 7C436110-AB2A-4BBB-A880-FE41995C9F82 csr-active-config =40000000

setvar -guid 7C436110-AB2A-4BBB-A880-FE41995C9F82 csr-active-config
Reset SIP (delete entry)
@echo -off

setvar -guid 7C436110-AB2A-4BBB-A880-FE41995C9F82 csr-active-config =

That's super, coming to that all i need in my rom is just the shell and the reset will be done with driver scripts and addboot

I'm testing that tonight(the adding only shell to the rom)

uglyJoe · November 13, 2017

My ZboxNano is flying with Ozmosis from Disk.
I put the Shell into the EFI, because the Zotac can load ShellX64.efi from bios menu.

But I replaced Fat.ffs with EnhancedFat.ffs and apply the UEFIPatch for the ROM to unlock the msr.

Many Boards should autostart fs0:\EFI\BOOT\BootX64.efi if there is no other boot entry.

Tusskan · November 13, 2017

My ZboxNano is flying with Ozmosis from Disk.

I put the Shell into the EFI, because the Zotac can load ShellX64.efi from bios menu.

But I replaced Fat.ffs with EnhancedFat.ffs and apply the UEFIPatch for the ROM to unlock the msr.

Many Boards should autostart fs0:\EFI\BOOT\BootX64.efi if there is no other boot entry.

So you say, instead of fatten the rom with oz and its dervatives i can load all that from the disk, Okay how to check if my mother board autoloads the shell whenever i create \EFI\BOOT\BOOTX64.efi doesn't load when i'm on factory BIOS

uglyJoe · November 13, 2017

If auto-boot is not working for you, try with a pen-drive

Format the pen-drive with guid partition-table

Mount ESP and save HermitShellX64.efi as \EFI\BOOT\BootX64.efi

I placed all OZ stuff, DSDT, SSDT, kext and the efi-drivers to the ESP:

00:000 00:000 Ozmosis 1.03.167X-CPWN RELEASE (2015-12-24 09:12:07 VS2013x86) on 2017-11-13 19:44:33
00:000 00:000 Found Firmware UEFI Spec  :2.31:
00:000 00:000 Found Firmware Vendor     :American Megatrends:
00:000 00:000 Found Firmware Revision   :4.653:
00:258 00:258 Connected PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,CBFBF263-8796-4BAF-98C0-041BC1CB2688,0x64028,0x1DC8F260)
00:375 00:116 BootOrder 01 02 03 04
00:375 00:000 Found Intel(R) Core(TM) i7-3537U CPU @ 2.00GHz (3A.06.00) Cores 2 Threads 4
00:375 00:000  P-State Coordination Type HW_ALL -> SW_ANY = SW_ANY
00:375 00:000  Bus Ratio 8 - 25 (19)  
00:375 00:000  Disabling Invalid Flex-Ratio 110000 -> 100000 = 100000
00:375 00:000  TSC Frequency  2494351600  2494MHz
00:375 00:000  CPU Frequency  2494351600  2494MHz
00:375 00:000  FSB Frequency    99774064    99MHz
00:375 00:000 Found 00.00.02.0 Intel Graphics Controller [8086:0166] [19DA:2111] rev 9
00:376 00:000 Found 00.02.00.0 Realtek Lan Controller [10EC:8168] [19DA:8168] rev 7 00:00:00:00:00:00
00:376 00:000 Found 00.00.1F.3 Intel SMBUS Controller [8086:1E22] [19DA:A247] rev 4
00:377 00:001  Slot 0 8192MB DDR3 SDRAM 1600MHz "Crucial Technology" "CT102464BF160B.M1" "00000000"
00:382 00:004 Found 1 GPU Controller 
00:382 00:000 Found Storage PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,18CCD4FB-C08A-4CB9-8B34-632A1579D55F,0x28,0x64000)
00:384 00:001 Found Defaults \Efi\Oz\Defaults.plist
00:415 00:031 Validated Boot0001 "macOS"
00:415 00:000  PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,CBFBF263-8796-4BAF-98C0-041BC1CB2688,0x64028,0x1DC8F260)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,1F90E55323C307489624FC94C337226F)/\2705DBDE-D93D-3EA4-9902-5B97D261AC20\System\Library\CoreServices\boot.efi (0x108)
00:420 00:005 Validated Boot0002 "Recovery"
00:420 00:000  PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,CBFBF263-8796-4BAF-98C0-041BC1CB2688,0x64028,0x1DC8F260)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,38E133ADA9E9874EBA0229E29CCD3B40)/\2705DBDE-D93D-3EA4-9902-5B97D261AC20\boot.efi (0xD0)
00:420 00:000 Validated Boot0003 "LibreElec"
00:420 00:000  PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,886EA49D-FB01-4685-ADA6-842CE476367F,0x2000,0x100000)/\EFI\BOOT\bootx64.efi (0x7A)
00:421 00:000 Validated Boot0004 "Uefi Shell"
00:421 00:000  PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,18CCD4FB-C08A-4CB9-8B34-632A1579D55F,0x28,0x64000)/\ShellX64.efi (0x6A)
00:421 00:000 Scanning Bootable Devices...
00:890 00:469 Completed Bootable Device Scan
00:891 00:001 BootOrder 01 02 03 04
02:049 01:157 StartImage: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,CBFBF263-8796-4BAF-98C0-041BC1CB2688,0x64028,0x1DC8F260)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,1F90E55323C307489624FC94C337226F)/\2705DBDE-D93D-3EA4-9902-5B97D261AC20\System\Library\CoreServices\boot.efi
02:049 00:000 Found Current Graphics Mode 0 1920 x 1080
02:092 00:042 Setting Graphics Mode 0 1920 x 1080
02:135 00:042 Found 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AcpiGeneratorMode 0x45 01000101 Enabled | Darwin | Update Legacy
02:135 00:000 Using AcpiGeneratorMask 0x04 00000100 Darwin
02:135 00:000 Remove SSDT r1  0x09AA 0xBC "PmRef " "Cpu0Ist " 0x00003000 "INTL" 0x20051117 - Success
02:136 00:000 Remove SSDT r1  0x0AA2 0x75 "PmRef " "CpuPm   " 0x00003000 "INTL" 0x20051117 - Success
02:136 00:000 Inject SSDT r1  0x06D0 0xAC "APPLE " "CpuPm   " 0x00021500 "INTL" 0x20140926 "SSDT.aml" - Success
02:137 00:001 Loaded DSDT r2  0x7187 0x73 "APPLE " "A M I   " 0x00000024 "INTL" 0x20100331 "DSDT.aml" - Success
02:137 00:000 Found DMI Anchor 0xBA4E3498 v2.7 Table Address 0xBA436018 Length 0x0971 - Success
02:154 00:017 Updated DMI Anchor 0xB9EDB000 v2.7 Table Address 0xB9EDB020 Length 0x094B
02:155 00:000 Found 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args " " (1)
02:155 00:000 Found LoadedImage->LoadOptions "<null string>" (0)
02:155 00:000 LoadedImage->LoadOptions "slide=0" (16)
02:156 00:000 Found Intel HD Graphics 4000 [8086:0166] PciRoot(0x0)/Pci(0x2,0x0)
02:156 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "model" = "Intel HD Graphics 4000" (22) - Success
02:156 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "built-in" = 00  (1) - Success
02:156 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "graphic-options" = 0C 00 00 00  (4) - Success
02:156 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "hda-gfx" = "onboard-1" (10) - Success
02:156 00:000 Using Custom AAPL,ig-platform-id 0x0166000B
02:156 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "AAPL,ig-platform-id" = 0B 00 66 01  (4) - Success
02:156 00:000 Found Intel Panther Point HDA Controller [8086:1E20] PciRoot(0x0)/Pci(0x1B,0x0)
02:163 00:006 Found \Efi\Oz\Darwin\Extensions\Common\FakeSMC_LPCSensors.kext [plist][x86_64]
02:164 00:000 Found \Efi\Oz\Darwin\Extensions\Common\EFICheckDisabler.kext [plist]
02:166 00:002 Found \Efi\Oz\Darwin\Extensions\Common\RealtekRTL8111.kext [plist][x86_64]
02:167 00:001 Found \Efi\Oz\Darwin\Extensions\Common\FakeSMC_CPUSensors.kext [plist][x86_64]
02:169 00:001 Found \Efi\Oz\Darwin\Extensions\Common\FakeSMC.kext [plist][x86_64]
02:170 00:001 Found \Efi\Oz\Darwin\Extensions\Common\IntelGraphicsFixup.kext [plist][x86_64]
02:172 00:002 Found \Efi\Oz\Darwin\Extensions\Common\Lilu.kext [plist][x86_64]
02:173 00:001 Found \Efi\Oz\Darwin\Extensions\Common\AppleALC.kext [plist][x86_64]
02:178 00:004 Found \Efi\Oz\Darwin\Extensions\Common\AppleALC.kext\Contents\PlugIns\PinConfigs.kext [plist]
02:178 00:000 Setting DataHub 64517CC8-6561-4051-B03C-5964B60F4C7A:FSBFrequency = 70 6E F2 05 00 00 00 00  8 bytes - Success
02:179 00:000 Setting DataHub 64517CC8-6561-4051-B03C-5964B60F4C7A:DevicePathsSupported = 01 00 00 00  4 bytes - Success
02:180 00:001 Setting DataHub 64517CC8-6561-4051-B03C-5964B60F4C7A:Model = "Macmini6,2" 20 bytes - Success
02:181 00:001 Setting DataHub 64517CC8-6561-4051-B03C-5964B60F4C7A:SystemSerialNumber = "XXX" 24 bytes - Success
02:183 00:001 Setting DataHub 64517CC8-6561-4051-B03C-5964B60F4C7A:system-id = XXX bytes - Success
02:185 00:002 Setting RT+BS 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB = "XXX" 17 bytes - Success
02:187 00:002 Setting RT+BS 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM = XXX  6 bytes - Success
02:188 00:000 Setting RT+BS 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:BackgroundClear = 00 00 00 00  4 bytes - Success
02:189 00:000 Setting RT+BS 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures = 37 E1 0F E0  4 bytes - Success
02:190 00:000 Setting RT+BS 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask = 3F FF 1F FF  4 bytes - Success
02:195 00:005 Setting DataHub 64517CC8-6561-4051-B03C-5964B60F4C7A:boot-log 2191360 bytes - Success
02:197 00:001 Setting Firmware Vendor "Apple Inc." 1.10
02:561 00:364 GetDeviceProperties Buffer 0xB640E018 Size 0xF1 Protocol Size 0xF1 1 Devices - Success
02:564 00:002 Found BootArgs 0xAD681000 Version 0x2 Revision 0x0
02:573 00:009 Found Darwin Kernel Version 17.2.0: Fri Sep 29 18:27:05 PDT 2017; root:xnu-4570.20.62~3/RELEASE_X86_64 0xAA91B000 Kernelcache
02:573 00:000 Injected Call __ZN12KLDBootstrap20readBooterExtensionsEv Into __ZN12KLDBootstrap23readPrelinkedExtensionsEP10section_64
02:573 00:000 Ignore result from call __ZN12IOUserClient21copyClientEntitlementEP4taskPKc in __ZN6OSKext14loadExecutableEv
02:573 00:000 Injecting FakeSMC_LPCSensors.kext "Driver-2F8B000" 0x356CA bytes
02:573 00:000 Injecting EFICheckDisabler.kext "Driver-2FC1000" 0x1065 bytes
02:574 00:000 Injecting RealtekRTL8111.kext "Driver-2FC3000" 0x4497E bytes
02:574 00:000 Injecting FakeSMC_CPUSensors.kext "Driver-3008000" 0xB7D2 bytes
02:574 00:000 Injecting FakeSMC.kext "Driver-3014000" 0x1E9A7 bytes
02:574 00:000 Injecting IntelGraphicsFixup.kext "Driver-3033000" 0x8E2A bytes
02:574 00:000 Injecting Lilu.kext "Driver-303C000" 0x1A1C4 bytes
02:574 00:000 Injecting AppleALC.kext "Driver-3057000" 0xB2F0 bytes
02:574 00:000 Injecting PinConfigs.kext "Driver-3063000" 0x1E4FB bytes
02:575 00:000 RSDP 0xB9EDC000 r2  0x0024 0xA4 "ALASKA" 0xFE 0xB9EDC028 0x00000000B9EDC078
02:579 00:003 RSDT 0xB9EDC028 r1  0x0048 0xAC "ALASKA" "A M I   " 0x1072009  0x5446534D 0x10013
02:579 00:000 FACP 0xB9EDC0F0 r2  0x0084 0x4D "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:579 00:000 FACS 0xB9EE6040 r0  0x0040 0xA3 "      " "        " 0x0        0x0        0x0
02:579 00:000 DSDT 0xB9EDC178 r2  0x7187 0x73 "APPLE " "A M I   " 0x24       0x4C544E49 0x20100331
02:579 00:000 APIC 0xB9EE3410 r3  0x0072 0x46 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:579 00:000 FPDT 0xB9EE3488 r1  0x0044 0x3A "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:579 00:000 ASF! 0xB9EE34D0 r32 0x00A5 0x2E "INTEL " " HCG    " 0x1        0x4D534654 0xF4240
02:579 00:000 MCFG 0xB9EE3578 r1  0x003C 0xA9 "ALASKA" "A M I   " 0x1072009  0x5446534D 0x97
02:579 00:000 HPET 0xB9EE35B8 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
02:579 00:000 SSDT 0xB9EE35F0 r1  0x0315 0xCE "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
02:579 00:000 SSDT 0xB9EE39C0 r1  0x06D0 0xAC "APPLE " "CpuPm   " 0x21500    0x4C544E49 0x20140926
02:579 00:000 XSDT 0xB9EDC078 r1  0x006C 0x41 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:579 00:000 FACP 0xB9EE3300 r5  0x010C 0x71 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:579 00:000 FACS 0xB9EE6080 r0  0x0040 0xA1 "      " "        " 0x0        0x0        0x2
02:579 00:000 DSDT 0xB9EDC178 r2  0x7187 0x73 "APPLE " "A M I   " 0x24       0x4C544E49 0x20100331
02:579 00:000 APIC 0xB9EE3410 r3  0x0072 0x46 "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:579 00:000 FPDT 0xB9EE3488 r1  0x0044 0x3A "ALASKA" "A M I   " 0x1072009  0x20494D41 0x10013
02:579 00:000 ASF! 0xB9EE34D0 r32 0x00A5 0x2E "INTEL " " HCG    " 0x1        0x4D534654 0xF4240
02:579 00:000 MCFG 0xB9EE3578 r1  0x003C 0xA9 "ALASKA" "A M I   " 0x1072009  0x5446534D 0x97
02:579 00:000 HPET 0xB9EE35B8 r1  0x0038 0xB6 "ALASKA" "A M I   " 0x1072009  0x2E494D41 0x5
02:579 00:000 SSDT 0xB9EE35F0 r1  0x0315 0xCE "SataRe" "SataTabl" 0x1000     0x4C544E49 0x20091112
02:579 00:000 SSDT 0xB9EE39C0 r1  0x06D0 0xAC "APPLE " "CpuPm   " 0x21500    0x4C544E49 0x20140926
02:580 00:000 Shrinking Kernel Memory Map 0xAE0 (58) -> 0x6C0 (36)
02:581 00:001 Found BootArgs 0xAD681000 Version 0x2 Revision 0x0
02:581 00:000 CommandLine "slide=0"
02:581 00:000 EfiMode             0x40 (64) DebugMode 0x0 Flags 0x49 01001001 (RebootOnPanic | CSRActiveConfig | BlackTheme)
02:581 00:000 MemoryMap           0x008ABC000 Size   0x000006C0 DescSize 0x00000030 Version 01
02:581 00:000 Video Info     Base 0x0C0000000 Width 1920 Height 1080 Depth 32 RowBytes 0x1E00 Display 1 (Graphics)
02:581 00:000 Kernel Address      0x000100000 Length 0x089BD000
02:581 00:000 EfiRuntimeServices  0x000003182 Pages  0x0000593A VirtualPageStart 0x000FFFFFF8003182
02:581 00:000 EfiSystemTable      0x003182000
02:581 00:000 PerformanceData     0x000000000 Size   0x00000000
02:581 00:000 KeyStoreData        0x000000000 Size   0x00000000
02:581 00:000 BootMem             0x000000000 Size   0x00000000
02:581 00:000 PhysicalMemorySize  0x200000000 (8192 MB)
02:581 00:000 FSBFrequency        0x005F26E70 (99 MHz)
02:581 00:000 DeviceTree          0x002F6A000 Length 0x00000FA0
02:581 00:000 PciConfigSpace Base 0x0F8000000 StartBus 0x0 EndBus 0x3F
02:581 00:000 CsrActiveConfig     0x40 01000000 (UnrestrictedNVRAM)
02:582 00:000 CsrCapabilities     0x0 00000000 ( )
02:582 00:000 boot_SMC_plimit     0x0
02:582 00:000 bootProgressMeter   Start 0 End 0
02:582 00:000 MemMap 0xB31D7000 MemMapSize 0x000006C0 DescriptorSize 0x00000030 DescriptorVersion 01
02:582 00:000  ++ Physical Range            Virtual Start      Pages     Attributes         Type
02:582 00:000  01 0x0000000000-0x000009DFFF 0x0000000000000000 0x000009E 0x000000000000000F available
02:582 00:000  02 0x000009E000-0x000009FFFF 0x0000000000000000 0x0000002 0x0000000000000000 ACPI_NVS
02:582 00:000  03 0x0000100000-0x001FFFFFFF 0x0000000000000000 0x001FF00 0x000000000000000F available
02:582 00:000  04 0x0020000000-0x00201FFFFF 0x0000000000000000 0x0000200 0x000000000000000F reserved
02:582 00:000  05 0x0020200000-0x0040003FFF 0x0000000000000000 0x001FE04 0x000000000000000F available
02:582 00:000  06 0x0040004000-0x0040004FFF 0x0000000000000000 0x0000001 0x000000000000000F reserved
02:582 00:000  07 0x0040005000-0x00A9FD7FFF 0x0000000000000000 0x0069FD3 0x000000000000000F available
02:582 00:000  08 0x00A9FD8000-0x00AA065FFF 0x0000000000000000 0x000008E 0x000000000000000F LoaderCode
02:582 00:000  09 0x00AA066000-0x00B9916FFF 0x0000000000000000 0x000F8B1 0x000000000000000F available
02:582 00:000  10 0x00B9917000-0x00B9C0AFFF 0x0000000000000000 0x00002F4 0x000000000000000F reserved
02:582 00:000  11 0x00B9C0B000-0x00B9D3BFFF 0x0000000000000000 0x0000131 0x000000000000000F reserved
02:582 00:000  12 0x00B9D3C000-0x00B9D41FFF 0x0000000000000000 0x0000006 0x000000000000000F reserved
02:582 00:000  13 0x00B9D42000-0x00B9DA6FFF 0x0000000000000000 0x0000065 0x000000000000000F reserved
02:582 00:000  14 0x00B9DA7000-0x00B9E46FFF 0x0000000000000000 0x00000A0 0x000000000000000F available
02:582 00:000  15 0x00B9E47000-0x00B9E47FFF 0xFFFFFF8003182000 0x0000001 0x000000000000000F ACPI_NVS
02:582 00:000  16 0x00B9E48000-0x00B9E48FFF 0x0000000000000000 0x0000001 0x000000000000000F BS_code
02:582 00:000  17 0x00B9E49000-0x00B9ED8FFF 0x0000000000000000 0x0000090 0x000000000000000F ACPI_NVS
02:582 00:000  18 0x00B9ED9000-0x00B9EDAFFF 0x0000000000000000 0x0000002 0x000000000000000F ACPI_NVS
02:582 00:000  19 0x00B9EDB000-0x00B9EE7FFF 0x0000000000000000 0x000000D 0x000000000000000F ACPI_NVS
02:582 00:000  20 0x00B9EE8000-0x00BA2ACFFF 0xFFFFFF8003183000 0x00003C5 0x800000000000000F MemMapIO
02:582 00:000  21 0x00BA2AD000-0x00BA4E4FFF 0xFFFFFF8003548000 0x0000238 0x800000000000000F MemMapIO
02:582 00:000  22 0x00BA4E5000-0x00BA503FFF 0xFFFFFF8003780000 0x000001F 0x000000000000000F ACPI_NVS
02:582 00:000  23 0x00BA504000-0x00BA578FFF 0xFFFFFF800379F000 0x0000075 0x000000000000000F ACPI_NVS
02:582 00:000  24 0x00BA579000-0x00BA579FFF 0x0000000000000000 0x0000001 0x000000000000000F BS_data
02:582 00:000  25 0x00BA57A000-0x00BA5BCFFF 0x0000000000000000 0x0000043 0x000000000000000F ACPI_NVS
02:582 00:000  26 0x00BA5BD000-0x00BAD5EFFF 0x0000000000000000 0x00007A2 0x000000000000000F BS_data
02:582 00:000  27 0x00BAD5F000-0x00BAFF1FFF 0xFFFFFF8003814000 0x0000293 0x800000000000000F MemMapIO
02:582 00:000  28 0x00BAFF2000-0x00BAFFFFFF 0x0000000000000000 0x000000E 0x000000000000000F BS_data
02:582 00:000  29 0x00BB800000-0x00BF9FFFFF 0x0000000000000000 0x0004200 0x0000000000000000 reserved
02:582 00:000  30 0x00F8000000-0x00FBFFFFFF 0xFFFFFF8003AA7000 0x0004000 0x8000000000000001 MemMapIO
02:582 00:000  31 0x00FEC00000-0x00FEC00FFF 0xFFFFFF8007AA7000 0x0000001 0x8000000000000001 MemMapIO
02:582 00:000  32 0x00FED00000-0x00FED03FFF 0xFFFFFF8007AA8000 0x0000004 0x8000000000000001 MemMapIO
02:582 00:000  33 0x00FED1C000-0x00FED1FFFF 0xFFFFFF8007AAC000 0x0000004 0x8000000000000001 MemMapIO
02:583 00:000  34 0x00FEE00000-0x00FEE00FFF 0xFFFFFF8007AB0000 0x0000001 0x8000000000000001 MemMapIO
02:583 00:000  35 0x00FF000000-0x00FFFFFFFF 0xFFFFFF8007AB1000 0x0001000 0x8000000000000001 MemMapIO
02:583 00:000  36 0x0100000000-0x023F5FFFFF 0x0000000000000000 0x013F600 0x000000000000000F available

ammoune78 · November 13, 2017

So you say, instead of fatten the rom with oz and its dervatives i can load all that from the disk, Okay how to check if my mother board autoloads the shell whenever i create \EFI\BOOT\BOOTX64.efi doesn't load when i'm on factory BIOS

~~Place the shell on the Efi/Dir/ or in Efi/BOOT/ or in ROM and when you reboot, if you press the F12, you should see a "UEFI OS" from the boot entries, then your mobo autoload the shell.~~

Hhh We posted at the same time

Edited November 13, 2017 by ammoune78

uglyJoe · November 13, 2017

For installation to an unformatted disk, I put all stuff to the ESP of the macOS installer.

Then I start this script from the uefi shell

fs0:

install.nsh

@echo -off

if exist HFSPlus.efi then
  load HFSPlus.efi
else
  echo HFSPlus.efi not found, exiting...
  goto END
endif

if exist Ozmosis.efi then
  load Ozmosis.efi
else
  echo Ozmosis.efi not found, exiting...
  goto END
endif

for %m in 0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
  if exist blk%m:\.IABootFiles\boot.efi then
    echo Starting macOS installer...
    blk%m:\.IABootFiles\boot.efi
    exit
  endif
endfor

:END
echo Boot file not found, exiting...

This way I can start the Installer and format the drive from DiskUtility.

After a reboot I copy all stuff from the Installer's ESP to the ESP of the target disk.

Add Driver and start the Install again...

Full macOS installation - OZ only

Tusskan · November 13, 2017

For installation to an unformatted disk, I put all stuff to the ESP of the macOS installer.

Then I start this script from the uefi shell

fs0:

install.nsh
@echo -off

if exist HFSPlus.efi then
  load HFSPlus.efi
else
  echo HFSPlus.efi not found, exiting...
  goto END
endif

if exist Ozmosis.efi then
  load Ozmosis.efi
else
  echo Ozmosis.efi not found, exiting...
  goto END
endif

for %m in 0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
  if exist blk%m:\.IABootFiles\boot.efi then
    echo Starting macOS installer...
    blk%m:\.IABootFiles\boot.efi
    exit
  endif
endfor

:END
echo Boot file not found, exiting...
This way I can start the Installer and format the drive from DiskUtility.
After a reboot I copy all stuff from the Installer's ESP to the ESP of the target disk.

Add Driver and start the Install again...

Full macOS installation - OZ only

All that without injecting oz or anything into BIOS rom? please pm me all the scripts.

Merronk · November 14, 2017

First go to cecekpawon post #5503# , then place does files here:

In

└── EFI

    ├── KernextPatcher.efi

    ├── KernextPatcher.plist

├── AcpiPatcher.efi

├── AcpiPatcher.plist

    ├── KernextPatcherLog.txt

└── AcpiPatcherLog.txt

Download this Shell #5580# and put it in Firmware or Efi/BOOT/.

Now reboot and go to Shell by selecting UEFI OS from F12, at the prompt wright this:

fs0:

cd EFI

bcfg driver add 0 KernextPatcher.efi "KernextPatcher"

Note that the fs0: for you will not work maybe, so you have to try fs1: fs2: until you get the EFI that have the files needed to be registered.

Why not trying the F7 that I've posted instead of f8g, you can update the ROM with UBUTool in order to have latest OROM's, result will be better than f8g.

What CPU you use because I boot without "VoodooTSC or NullCpu", Ozmosis will detect automatically your CPU and start booting, you just need the InjectorKext 1.3 to detect SATA Ports. Please write down your signature.

So, I don't need InjectorKext for SATA it works perfect without it and I thought SATA will be taken from DSDT.

What I needed was USB Injector, I did it by myself for XHC EH01 and EH02 and MacPro6,1 and it works perfect.

My CPU is Intel Core i7 4820 and it never worked without NullCPU whatever I did (in Yosemithe too), so I do with Null, the reason I don't know.

I can try F7 but I don't think it will bring a lot of differences in using. The CPU Power Management must have a reason in SSDT or DSDT, so they must be somehow fixed for PM.

For apfs, what do you mean with shell and UEFI OS from F12? I have a Mac drive, Mac Recovery and Windows drive, which one is UEFI OS? To put this file BOOTX64.efi to bios I need ffs file not efi. So I can't put it in bios

ammoune78 · November 14, 2017

So, I don't need InjectorKext for SATA it works perfect without it and I thought SATA will be taken from DSDT.

What I needed was USB Injector, I did it by myself for XHC EH01 and EH02 and MacPro6,1 and it works perfect.

My CPU is Intel Core i7 4820 and it never worked without NullCPU whatever I did (in Yosemithe too), so I do with Null, the reason I don't know.

I can try F7 but I don't think it will bring a lot of differences in using. The CPU Power Management must have a reason in SSDT or DSDT, so they must be somehow fixed for PM.

For apfs, what do you mean with shell and UEFI OS from F12? I have a Mac drive, Mac Recovery and Windows drive, which one is UEFI OS? To put this file BOOTX64.efi to bios I need ffs file not efi. So I can't put it in bios

If you want to use APFS, the only way you will have is to do an BCFG, and to do the BCFG you need to call it from shell. To put it in BIOS is quite simple, go to first page and download Kext2Ffs and it's command, unzip it, replace the command inside the folder with the one downloaded, Rename the BOOTX64.efi to HermitShellX64.efi and put it on the efi folder, run the command and the ffs file will be generated in the Ffs folder. You can add the APFS.efi in the Efi/ folder.

Do this to register the APFS:

fs0:

cd EFI

bcfg driver add 0 APFS.efi "APFS"

You will be now able to run macOS APFS drive

For the power management the SSDT I gave you already have the plugin infos, logically you don't have to use NullCPUPowerManagement, but instead did you tried cpus=1 from the boot-args?

Edited November 14, 2017 by ammoune78

medallo · November 15, 2017

Here's patched AppleALC Rev 1.2.1 with Lillu Kext, Layout ID used: 1 and will not work with other Layout ID's, so in HDEF only put 1 as Layout ID, you have the FfsCompressed file for ROM and kext. Rename your OzmosisDfaults to Defaults and put it in Efi/Oz/.

AppleALC 887 L1 Rev1.2.1 Kext-Ffs.zip

Hi.

Thank you .. very light the kext for the rom.

ammoune78 · November 15, 2017

Cecek, I've found strength things when used AcpiPatcher, when I open MaciASL and select New From ACPI I have the followed things duplicated except CpuPm that I don't know where it come from, I don't have any CpuPm in my entire disk, here's the duplicates I've found with screenshot, and settings:

FACS-1

CpuPm

CpuCst

<?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>ACPI</key>
	<dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>DMAR</string>
			</dict>
		</array>
		<key>FixHeader</key>
		<true/>
		<key>GenerateCPUStates</key>
		<true/>
		<key>PatchOemTableOnly</key>
		<true/>
		<key>Patches</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>change TMR to TIMR</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				VE1S
				</data>
				<key>Replace</key>
				<data>
				VElNUg==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>change GFX0 to IGPU</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				R0ZYMA==
				</data>
				<key>Replace</key>
				<data>
				SUdQVQ==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>change SAT0 to SATA</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				U0FUMA==
				</data>
				<key>Replace</key>
				<data>
				U0FUQQ==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>change H_EC to EC__</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				SF9FQw==
				</data>
				<key>Replace</key>
				<data>
				RUNfXw==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>change PEGP to GFX0</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				UEVHUA==
				</data>
				<key>Replace</key>
				<data>
				R0ZYMA==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>change B0D3 to HDAU</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				QjBEMw==
				</data>
				<key>Replace</key>
				<data>
				SERBVQ==
				</data>
			</dict>
		</array>
	</dict>
	<key>Preferences</key>
	<dict>
		<key>Debug</key>
		<true/>
		<key>Off</key>
		<false/>
		<key>SaveLogToFile</key>
		<true/>
	</dict>
</dict>
</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>KernextPatches</key>
	<dict>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>remove usb limit</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g72M/v//EA==
				</data>
				<key>MatchOS</key>
				<string></string>
				<key>Name</key>
				<string>AppleUSBXHCIPCI</string>
				<key>Replace</key>
				<data>
				g72M/v//Fg==
				</data>
			</dict>
		</array>
	</dict>
	<key>Preferences</key>
	<dict>
		<key>Debug</key>
		<true/>
		<key>Off</key>
		<false/>
		<key>SaveLogToFile</key>
		<true/>
	</dict>
</dict>
</plist>

cecekpawon · November 16, 2017

No idea about FACS-1. While using GenerateCPUStates, CpuPm & CpuCst is auto generated, you may also need to drop Cpu0lst & CpuSsdt first, and do not mix with other generator. Or turn off GenerateCPUStates when you have cpu ssdt already to load with Oz.

09:926 00:000 Remove SSDT r1  0x09AA 0xED "PmRef " "Cpu0Ist " 0x00003000 "INTL" 0x20051117 - Success
09:926 00:000 Remove SSDT r1  0x0A92 0xFF "PmRef " "CpuPm   " 0x00003000 "INTL" 0x20051117 - Success
09:926 00:000 Inject SSDT r1  0x074E 0xC1 "APPLE " "CpuPm   " 0x00018400 "INTL" 0x20140926 "SSDT-1.aml" - Success

Bur for me, Oz will remove my CpuPm & Cpu0Ist automatically when I have custom CpuPm to load.

Merronk · November 16, 2017

If you want to use APFS, the only way you will have is to do an BCFG, and to do the BCFG you need to call it from shell. To put it in BIOS is quite simple, go to first page and download Kext2Ffs and it's command, unzip it, replace the command inside the folder with the one downloaded, Rename the BOOTX64.efi to HermitShellX64.efi and put it on the efi folder, run the command and the ffs file will be generated in the Ffs folder. You can add the APFS.efi in the Efi/ folder.

Do this to register the APFS:

fs0:

cd EFI

bcfg driver add 0 APFS.efi "APFS"

You will be now able to run macOS APFS drive

For the power management the SSDT I gave you already have the plugin infos, logically you don't have to use NullCPUPowerManagement, but instead did you tried cpus=1 from the boot-args?

Thank you very much for your explanation, but can you describe a little bit more? I don't want to put something on the EFI partition, I want to have everything in BIOS.

So far I can understand, I must do:

1. Convert BOOTX64.efi and APFS.efi to FFS

2. Rename BOOTX64.ffs to HermitShellX64.ffs

3. Put both in BIOS

4. Reflash BIOS

What must I do next? Where must I write the fs0 and so on?

What must I write if the apfs is in bios and not in Efi partition?

Can I install High Sierra without apfs formatting or will it happen automatically?

The other thing to try with cpus=1 and -v I will try and will write you.

ammoune78 · November 16, 2017

No idea about FACS-1. While using GenerateCPUStates, CpuPm & CpuCst is auto generated, you may also need to drop Cpu0lst & CpuSsdt first, and do not mix with other generator. Or turn off GenerateCPUStates when you have cpu ssdt already to load with Oz.
09:926 00:000 Remove SSDT r1  0x09AA 0xED "PmRef " "Cpu0Ist " 0x00003000 "INTL" 0x20051117 - Success
09:926 00:000 Remove SSDT r1  0x0A92 0xFF "PmRef " "CpuPm   " 0x00003000 "INTL" 0x20051117 - Success
09:926 00:000 Inject SSDT r1  0x074E 0xC1 "APPLE " "CpuPm   " 0x00018400 "INTL" 0x20140926 "SSDT-1.aml" - Success
Bur for me, Oz will remove my CpuPm & Cpu0Ist automatically when I have custom CpuPm to load.

Now I used GenerateCPUStates-No FixeHeader-No DropOEMOnly-Yes, dropped Cpu0lst and CpuSsdt now only FACS-1 appear. If i 4 fingers then the FACS-1 isn't there.

Thank you very much for your explanation, but can you describe a little bit more? I don't want to put something on the EFI partition, I want to have everything in BIOS.

So far I can understand, I must do:

1. Convert BOOTX64.efi and APFS.efi to FFS

2. Rename BOOTX64.ffs to HermitShellX64.ffs

3. Put both in BIOS

4. Reflash BIOS

What must I do next? Where must I write the fs0 and so on?

What must I write if the apfs is in bios and not in Efi partition?

Can I install High Sierra without apfs formatting or will it happen automatically?

The other thing to try with cpus=1 and -v I will try and will write you.

1- Rename BOOTX64.efi to HermitShellX64.efi

2- Convert 10.13.1 APFS.efi from /usr/standalone/i386/APFS.efi and HermitShellX64.efi to .ffs using Kext2Ffs

3- Put them on the ROM

4- Flash the ROM

5- Restart, do 4 fingers (NVRAM Reset)

6- Restart again

7- Install HighSierra as normal but formatting as APFS, then when Install process finish

8- Set your macOS drive as First bootable drive

9- Restart, Press F12 and select UEFI OS, or restart and wait the Shell to be loaded

10- You will be prompted, then write this as is, press enter for each line command

fs0:

cd EFI

bcfg driver add 0 APFS.efi "APFS"

Now exit from the Shell and reboot, you should be able to see APFS drives and you can boot from normally.

Note: to avoid some HighSierra installation problems, download the latest CloverConfigurator, generate SMBios data, convert the FirmwareFeatures and FirmwareFeaturesMask to number, put them on your OzmosisDefaults.

davidm71 · November 17, 2017

Hi,

Just noticed Station-Drivers is hosting updated beta drivers for the Gigabyte Z87X and Z77X that claim to fix the MATS issue and enhance OS compatibility. Makes wonder if this is really an official release.

WinstonAce · November 17, 2017

If it's here it's supposed to be genuine

https://forums.tweaktown.com/gigabyte/28441-gigabyte-beta-bios.html

Sent from my ONEPLUS A5000 using Tapatalk

Tusskan · November 17, 2017

Hi,

Just noticed Station-Drivers is hosting updated beta drivers for the Gigabyte Z87X and Z77X that claim to fix the MATS issue and enhance OS compatibility. Makes wonder if this is really an official release.

They are all old, even the modded ones at tweaktown are old too.

WinstonAce · November 17, 2017

The link I gave aren't tweaked bios, just beta

This for example:

https://www.gigabyte.com/Motherboard/GA-Z87X-UD5H-rev-1x#support-dl

Is from 14/11/2017

And it has MATS table fix

Sent from my ONEPLUS A5000 using Tapatalk

ammoune78 · November 18, 2017

:angry: :angry: :angry: :wallbash: :thumbsdown_anim: Definitely canceled Oz stuffs in Efi Dir, 5 hours of complete HeadAche to boot with same things that was before inside ROM, and hundreds boot from windows and opening Efi Dir with Diskpart, the HfsPlus.efi is deleted after each reboot, the OS X drives appears and sometimes disappears.

ON THE ROM NOW, I keep only Theme.bin, no need tweaking until summer 2018 for same result or less.

For me the SPY Flasher if something was bad is more confortable than breaking my head, and stoping my entire life hoping this will work and maybe with less stability.

I enjoy the system with babes inside, if not why the MAIN DEVELOPPERS OF QUO AOS did it inside ROM, MANY OF QUO BOARDS ARE STILL ALIVE BECAUSE THE USERS TAKES CARE OF! :thumbsup_anim: :hammer: :king:

Edited November 18, 2017 by ammoune78

davidm71 · November 18, 2017

Gigabyte in that case has gone beyond the call of duty.

ammoune78 · November 18, 2017

Hhh, it seems that you forgot answering people on Win-Raid Mr david, they are waiting for answers about CPUMicrocode, this, is a real CALL OF DUTY :yes: :hysterical: my friend, hurry up!!! :wink_anim:

davidm71 · November 18, 2017

Hhh, it seems that you forgot answering people on Win-Raid Mr david, they are waiting for answers about CPUMicrocode, this, is a real CALL OF DUTY my friend, hurry up!!!

I didn’t know. That site sometimes does not auto notify. Thanks I’ll take a look.

Btw Whats a SPY Flasher?

ammoune78 · November 18, 2017

It upload a ROM file to the physical chip itself, flashing directly the chip securely! If the mobo has bad flash or something else!

iPhone Tapatalk

Ozmosis

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites