Jump to content
30960 posts in this topic

Recommended Posts

do you have fixheaders / fixheader20000000 patch maybe you need it.

I don’t need fix header or drop bgrt.

 

 

从我的 iPhone 发送,使用 Tapatalk

Looks like you do have an error. Maybe it wasn't known cause you did not have correctly working system. You have add IMEI fix set? Maybe disable it.

 

EDIT: You may also need to set some nvram variables, that are set by nvram.plist in EFI shell before booting.

Yes I have add SSDT-IMEI.aml to fix Imei because imei could cause many problem in video playback.

 

 

从我的 iPhone 发送,使用 Tapatalk

I don’t need fix header or drop bgrt.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Yes I have add SSDT-IMEI.aml to fix Imei because imei could cause many problem in video playback.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

You are redefining it, it's already defined. You need to edit your original tables and remove or fix it, or make sure you don't have add IMEI dsdt fix enabled. Don't reinject that table without removing the previous definition.

 

EDIT: Also, reconcile your nvram since all the stuff from nvram.plist needs added back.

  • Like 1

You are redefining it, it's already defined. You need to edit your original tables and remove or fix it, or make sure you don't have add IMEI dsdt fix enabled. Don't reinject that table without removing the previous definition.

 

EDIT: Also, reconcile your nvram since all the stuff from nvram.plist needs added back.

When I use official osxaptiov2 have no problem.

 

I will test more and give some feedback.

 

 

从我的 iPhone 发送,使用 Tapatalk

When I use official osxaptiov2 have no problem.

 

I will test more and give some feedback.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Yes, I am aware but the fixes have bugs, three of which I am aware, maybe more. I'm trying to fix them. I modified to prevent from moving runtime code areas, where SMM would be located, SMM uses physical mode so cannot be moved because the moving means that you have to adjust the physical addresses which can't be done, only virtual mode addresses can be changed.

I test again with drop SSDT-IMEI but no use.

 

Try to remove IMEI Dsdt parched from heci but still can’t boot into OS X and always reboot.

 

 

 

从我的 iPhone 发送,使用 Tapatalk

Now I test add fix headers and drop bgrt but still reboot.

 

 

从我的 iPhone 发送,使用 Tapatalk

I test again with drop SSDT-IMEI but no use.

 

Try to remove IMEI Dsdt parched from heci but still can’t boot into OS X and always reboot.

 

 

 

从我的 iPhone 发送,使用 Tapatalk

 

I don't know what you mean. Are you injecting that table? Are you using the dsdt fix mask from clover? Did you edit your original table where IMEI is? Did you restore the values from your nvram.plist into your actual nvram? It may be easier for you to run the installer again to get proper nvram. See if you can launch the installer.

I replaced with official osxaptiofixdrv2 with no emu driver and can run into the OS X.

 

 

从我的 iPhone 发送,使用 Tapatalk

I don't know what you mean. Are you injecting that table? Are you using the dsdt fix mask from clover? Did you edit your original table where IMEI is? Did you restore the values from your nvram.plist into your actual nvram? It may be easier for you to run the installer again to get proper nvram. See if you can launch the installer.

1. I don’t inject that table and I delete the dsdt patch (heci to Imei) and delete dsdt-imei.aml but still.

 

2. I didn’t need restore full nvram to native native because when I use official osxfix2 it works well.

 

3. Both system ,recoveryhd and installer can’t boot anymore.

 

 

从我的 iPhone 发送,使用 Tapatalk

I replaced with official osxaptiofixdrv2 with no emu driver and can run into the OS X.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Dude, I get that. There's a huge difference if you have working runtime that was not before. Do you still get message about it failing to load table because IMEI was already defined?

  • Like 1

Dude, I get that. There's a huge difference if you have working runtime that was not before. Do you still get message about it failing to load table because IMEI was already defined?

Yes I have removed all the patch and ssdt related with Imei but with no use.

 

I want test this kext but can’t boot into OS X.

 

 

从我的 iPhone 发送,使用 Tapatalk

committed.

test all again. fusion drive.

thanks in advance.

 

@Sherlocks,

 

Clover r4301 working as expected, like rc test, for High Sierra installation on Fusion Drive.  ScanLoader finds 2 macOS install entries after first reboot, since the Apple installer creates a com.apple.boot.R folder in each "Boot OS X" partition...

 

 

 

post-846696-0-64807400-1510698793_thumb.png

post-846696-0-22237900-1510698687_thumb.png

0:661  0:004  === [ ScanLoader ] ========================================
0:661  0:000  - [03]: 'EFI'
0:661  0:000  - [05]: 'Boot OS X'
0:669  0:007          AddLoaderEntry for Volume Name=Boot OS X
0:688  0:019  - [06]: 'EFI'
0:703  0:014  - [08]: 'Boot OS X'
0:716  0:012          AddLoaderEntry for Volume Name=Boot OS X

 

 

 

GetOSVersion correctly finds 10.13 and Clover injects kexts from /Other and /10.13...

 

 

 

27:650  0:000  Loading boot.efi  status=Success
27:672  0:021  GetOSVersion: 10.13.1

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: BD4D2798
27:760  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !
27:764  0:004  Use origin smbios table type 1 guid.
27:766  0:002  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
27:766  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
27:766  0:000  SetStartupDiskVolume:
27:766  0:000    * Volume: 'Boot OS X'
27:766  0:000    * LoaderPath: '\com.apple.boot.R\boot.efi'

 

 

 

Block injected kexts menu also shows /Other and /10.13 folders etc... 

 

 

 

post-846696-0-48733900-1510698746_thumb.png

post-846696-0-84964900-1510698773_thumb.png

post-846696-0-18834900-1510698820_thumb.png

 

 

 

Thanks Sherlocks :).

  • Like 2

Nope, although I've never had a OsxAptioFix Issue .

 

Cause I made a mistake.... Did not remove something that still relocates runtime code areas, lol. I only have a virtual machine currently, trying to get physical install so I can test with real firmware. Give me a bit, I will give another test driver. Need it to work for everyone still though, so your test is helpful.

  • Like 1

lol good to know, I just spent half an hour trying to figure out how to rename a file in efi using windows 10 power shell LOL the answer is also no it did not boot

 

You would have easier time with command prompt or EFI shell, lol.

  • Like 1

@Sherlocks,

 

Clover r4301 working as expected, like rc test, for High Sierra installation on Fusion Drive. ScanLoader finds 2 macOS install entries after first reboot, since the Apple installer creates a com.apple.boot.R folder in each "Boot OS X" partition...

 

 

 

 

attachicon.gifInstalling on FusionHD first phase.png

attachicon.gifBoot macOS Install from Boot OS X.png

0:661  0:004  === [ ScanLoader ] ========================================
0:661  0:000  - [03]: 'EFI'
0:661  0:000  - [05]: 'Boot OS X'
0:669  0:007		  AddLoaderEntry for Volume Name=Boot OS X
0:688  0:019  - [06]: 'EFI'
0:703  0:014  - [08]: 'Boot OS X'
0:716  0:012		  AddLoaderEntry for Volume Name=Boot OS X

 

 

GetOSVersion correctly finds 10.13 and Clover injects kexts from /Other and /10.13...

 

 

27:650  0:000  Loading boot.efi  status=Success
27:672  0:021  GetOSVersion: 10.13.1

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: BD4D2798
27:760  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !
27:764  0:004  Use origin smbios table type 1 guid.
27:766  0:002  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
27:766  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
27:766  0:000  SetStartupDiskVolume:
27:766  0:000    * Volume: 'Boot OS X'
27:766  0:000    * LoaderPath: '\com.apple.boot.R\boot.efi'

 

 

Block injected kexts menu also shows /Other and /10.13 folders etc...

 

 

 

 

Thanks Sherlocks :).

Thank you so much. Have a good day:)

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 2

So, apparently, there IS an AICPUPM problem in clover past r4180 r4073 somewhere. I really don't feel like tracing the problem, so I'll leave this for now.... Because I can't boot without AICPUPM panic. Can anyone who downloaded that previous driver give me screen shot if you hit space menu on entry and select the options verbose, keep symbols on panic, and don't reboot on panic? I want to see if it is AICPUPM related or not.

 

EDIT: I attached it again, if anyone could please try and post pic.

EDIT2: Looked what revision I last made a change at, the only one I know for sure I was last at I think was r4073, but I thought I had r4180 after that, should have checked before I replaced...

EDIT3: AAAAAAAAaaaaaaaaaaaaaaaaaarrrrrrrrrrrrrrrrrrrgggggggggggggggggggggggggggghhhhhhhhhhhhhhhhhhhh.... HULK SMASH.

OsxAptioFix2Drv-64.efi

  • Like 3

So, apparently, there IS an AICPUPM problem in clover past r4180 r4073 somewhere. I really don't feel like tracing the problem, so I'll leave this for now.... Because I can't boot without AICPUPM panic. Can anyone who downloaded that previous driver give me screen shot if you hit space menu on entry and select the options verbose, keep symbols on panic, and don't reboot on panic? I want to see if it is AICPUPM related or not.

 

EDIT: I attached it again, if anyone could please try and post pic.

EDIT2: Looked what revision I last made a change at, the only one I know for sure I was last at I think was r4073, but I thought I had r4180 after that, should have checked before I replaced...

EDIT3: AAAAAAAAaaaaaaaaaaaaaaaaaarrrrrrrrrrrrrrrrrrrgggggggggggggggggggggggggggghhhhhhhhhhhhhhhhhhhh.... HULK SMASH.

Was getting the same error that I showed you in chat but this time it never went into OS X and rebooted 35 times, same error.

 

88YRUDi.jpg

So, apparently, there IS an AICPUPM problem in clover past r4180 r4073 somewhere. I really don't feel like tracing the problem, so I'll leave this for now.... Because I can't boot without AICPUPM panic. Can anyone who downloaded that previous driver give me screen shot if you hit space menu on entry and select the options verbose, keep symbols on panic, and don't reboot on panic? I want to see if it is AICPUPM related or not.

 

EDIT: I attached it again, if anyone could please try and post pic.

EDIT2: Looked what revision I last made a change at, the only one I know for sure I was last at I think was r4073, but I thought I had r4180 after that, should have checked before I replaced...

EDIT3: AAAAAAAAaaaaaaaaaaaaaaaaaarrrrrrrrrrrrrrrrrrrgggggggggggggggggggggggggggghhhhhhhhhhhhhhhhhhhh.... HULK SMASH.

still

cd949912c03a0db629299ac20b0c75cf.jpg

 

 

从我的 iPhone 发送,使用 Tapatalk

Even I put back emu driver but still reboot.

 

Only use official osxaptiofixdrv2 can boot normal with and without emu driver but have no native nvram support.

 

 

从我的 iPhone 发送,使用 Tapatalk

still

 

从我的 iPhone 发送,使用 Tapatalk

Even I put back emu driver but still reboot.

 

Only use official osxaptiofixdrv2 can boot normal with and without emu driver but have no native nvram support.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

I still see error about IMEI already found, please hit the space bar on your macOS boot entry and select the verbose, keep symbols on panic, and don't reboot on panic options. So that it will not reboot on a panic and instead prints out info.

I still see error about IMEI already found, please hit the space bar on your macOS boot entry and select the verbose, keep symbols on panic, and don't reboot on panic options. So that it will not reboot on a panic and instead prints out info.

Yes I know.

 

This picture is when I select don’t reboot on panic and shows, otherwise it was rebooted.

 

May I should drop more table?

 

 

从我的 iPhone 发送,使用 Tapatalk

May be the following messages deserve developers attention? False alarms are possible. (-;

[CloverEFI/BiosKeyboard/LegacyBiosThunk.c:126]: (warning) Possible null pointer dereference: IdtArray
[CloverEFI/BiosVideo/LegacyBiosThunk.c:126]: (warning) Possible null pointer dereference: IdtArray
[CloverEFI/OsxPciBusNoEnumerationDxe/PciDriverOverride.c:178]: (error) Resource leak: Node
[LegacyBios/BlockIoDxe/LegacyBiosThunk.c:126]: (warning) Possible null pointer dereference: IdtArray
[LegacyBios/LegacyBios.c:640]: (error) Uninitialized variable: MemoryAddressUnder1MB
[LegacyBios/LegacyBios.c:641]: (error) Uninitialized variable: MemoryAddressUnder1MB
[LegacyBios/LegacyBios.c:642]: (error) Uninitialized variable: MemorySize
[Library/GenericBdsLib/BdsBoot.c:3564]: (error) Resource leak: DevicePath
[Library/GenericBdsLib/BdsBoot.c:4452]: (error) Resource leak: NewDevicePath
[Library/GenericBdsLib/BdsBoot.c:792]: (error) Deallocating a deallocated pointer: DevPath
[Library/OsxBdsPlatformLib/BdsPlatform.c:660]: (error) Resource leak: DevicePath
[Library/OsxBdsPlatformLib/BdsPlatform.c:849]: (error) Resource leak: DevicePath
[Patches_for_EDK2/OvmfPkg/CsmOld/LegacyBiosDxe/Thunk.c:79]: (error) Null pointer dereference
[Patches_for_EDK2/OvmfPkg/Library/PlatformBdsLib/BdsPlatform.c:201]: (error) Resource leak: DevicePath
[Patches_for_EDK2/OvmfPkg/Library/PlatformBdsLib/BdsPlatform.c:421]: (error) Resource leak: DevicePath
[Patches_for_EDK2/ShellPkg/Application/Shell/ShellProtocol.c:3197]: (error) Dereferencing 'CurrentDirectoryPath' after it is deallocated / released
[Patches_for_EDK2/ShellPkg/Library/UefiShellDebug1CommandsLib/Edit/FileBuffer.c:1869]: (error) Resource leak: NewLine
[Patches_for_EDK2/ShellPkg/Library/UefiShellDebug1CommandsLib/Edit/FileBuffer.c:692]: (error) Resource leak: Line
[Patches_for_EDK2/ShellPkg/Library/UefiShellLib/UefiShellLib.c:2106]: (error) Resource leak: CurrentItemPackage
[Patches_for_EDK2/ShellPkg/Library/UefiShellLib/UefiShellLib.c:713]: (error) Resource leak: FileNameCopy
[rEFIt_UEFI/entry_scan/securehash.c:215]: (error) Resource leak: NewDatabase
[rEFIt_UEFI/libeg/lodepng.c:62]: (error) Resource leak: p
[rEFIt_UEFI/libeg/lodepng.h:223]: (error) Code 'namespacelodepng{' is invalid C code. Use --std or --language to configure the language.
[rEFIt_UEFI/Platform/ati.c:1252]: (error) Resource leak: pciName
[rEFIt_UEFI/Platform/device_inject.c:132]: (error) Resource leak: DevicePath
[rEFIt_UEFI/Platform/device_inject.c:153]: (error) Resource leak: DevicePath
[rEFIt_UEFI/Platform/FixBiosDsdt.c:662]: (error) Shifting signed 32-bit value by 31 bits is undefined behaviour
[rEFIt_UEFI/Platform/kext_inject.c:151]: (error) Invalid CopyMem() argument nr 3. The value is 0 but the valid values are '1:'.
[rEFIt_UEFI/Platform/kext_inject.c:151]: (warning) Possible null pointer dereference: executableBuffer
[rEFIt_UEFI/Platform/kext_inject.c:154]: (warning) Possible null pointer dereference: executableFatBuffer
[rEFIt_UEFI/Platform/kext_inject.c:157]: (error) Resource leak: infoAddr
[rEFIt_UEFI/Platform/LegacyBiosThunk.c:143]: (warning) Possible null pointer dereference: IdtArray
[rEFIt_UEFI/Platform/LegacyBoot.c:321]: (error) Mismatching allocation and deallocation: sectorBuffer
[rEFIt_UEFI/Platform/Settings.c:4726]: (error) Shifting signed 32-bit value by 31 bits is undefined behaviour
[rEFIt_UEFI/Platform/Settings.c:6606]: (error) Shifting signed 32-bit value by 31 bits is undefined behaviour
[rEFIt_UEFI/refit/menu.c:2879] -> [rEFIt_UEFI/refit/menu.c:2877]: (error) Modifying string literal "..." directly or indirectly is undefined behaviour.

Why there are many LegacyBiosThunks?

  • Like 1
×
×
  • Create New...