Clover General discussion

PMheart · January 17, 2017

:wink_anim:

Slice · January 18, 2017

What if we revert changes of 23702?

Philip Petev · January 18, 2017

What if we revert changes of 23702?

Yes, it should be r23701. r23702 is the first problematic for most of us.

Sent from my MI 5s using Tapatalk

Micky1979 · January 18, 2017

Yes, it should be r23701. r23702 is the first problematic for most of us.

Sent from my MI 5s using Tapatalk

changes updating from 23701 to 23702:

MdePkg:

checking..available, continuing..

Updating '.':

U Include/Library/BaseLib.h

U Library/BaseLib/String.c

Updated to revision 23702.

(like already mentioned by dgsga)

Attached some builds of Clover r3977 with different edk2 revs, if someone-else is intrested to help and confirming that the problem starts with r23702:

Clover_r3977_edkII_23700.pkg.zip

Clover_r3977_edkII_23701.pkg.zip

Clover_r3977_edkII_23702.pkg.zip

What if we revert changes of 23702?

....testing

edk2 r23700 here works well (+/- 10 seconds to the login screen)

edk2 r23701 here works well (+/- 10 seconds to the login screen)

edk2 r23702 slow boot. Quickly show some dots and here hangs for 10/12 seconds, than boot as usual.

Edited January 18, 2017 by Micky1979

tluck · January 18, 2017

@micky1979

i tested your builds and then build them myself.

same results as you

edk2 r23700: Ok
edk2 r23701: Ok (same boot time as before)
edk2 r23702: very slow boot. after OsxAptio2 - then long hang.

Micky1979 · January 18, 2017

Yep, the problem is always there

Philip Petev · January 18, 2017

edk2 r23700 here works well (+/- 10 seconds to the login screen)
edk2 r23701 here works well (+/- 10 seconds to the login screen)

edk2 r23702 slow boot. Quickly show some dots and here hangs for 10/12 seconds, than boot as usual.

Same results for me on both my desktop (AMI Aptio) and my laptop (HPQ EFI) with one difference: with r23702 Clover stays at the dots forever on both machines

Maniac10 · January 18, 2017

Mine isn't slow with 23702, it just freezes. With 23701 it works just fine.

r2tincan · January 19, 2017

Can't boot into clover at all on my x99-E WS with the newest version. (Clover_v2.3k_r3974) I am using an older version on another drive that I've had since Yosemite and it's working fine. Anyone have any idea why? No errors because clover doesn't even load.

X99-E WS

Xeon 2630v3

Thanks much

cecekpawon · January 19, 2017

Capturing screen after OnExitBootServices has called (what come after '+++++' line) with KernelAndKextsPatch debug ON might help Slice to determine where the delay is. Can be bad reading kernelcache plist? AsciiStrHexToUint64 in 'GetPlistHexValue' has new return value? Safestring with "-D DISABLE_NEW_DEPRECATED_INTERFACES" defined in shell patch only.

I test Mickeys precompiled 23701 & 23702, they both boot just fine on my machine (uEFI BOOTX64 with HFSPlus, FSInject, OsxAptioFixDrv/OsxAptioFix2Drv drivers).

shaggymane · January 19, 2017

I have kernel panic if I use fixairport in clover...

it is killerwifi 1535 qualcomm atheros on a alienware 17r4

Slice · January 19, 2017

Who have a problem with 23702 please show your set of KernelAndKextPatches. Is there any empty patch?

artur_pt · January 19, 2017

hello Slice

this is mine

KernelAndKextPatches

AppleRTC

AsusAICPUPM

Debug

ForceKextsToLoad

\System\Library\Extensions\IOAudioFamily.kext

KernelCpu

KextsToPatch

Comment
Patch_Ig-paftform-id 4 LVDS
Find

BQMAAAIAAAAwAgAA

MatchOS
10.11.x,10.12.x
Name
AppleIntelFramebufferCapri
Replace

BQMAAAIAAAAwAAAA

Comment
Apple Logo 10.12
Find

AQAAdSU=

MatchOS
10.12.x
Name
IOGraphicsFamily
Replace

AQAA6yU=

Comment
Apple Logo
Find

QYjE6xE=

MatchOS
10.11.x
Name
IOGraphicsFamily
Replace

QYjE6zE=

Comment
Apple Logo Yose / El Capo
Find

AQAAdRc=

MatchOS
10.11.x
Name
IOGraphicsFamily
Replace

AQAA6xc=

Comment
BT4LE-Handoff-Hotspot Fix
Find

SIXAdFwPt0g=

MatchOS
10.11.x,10.12.x
Name
IOBluetoothFamily
Replace

Qb4PAAAA61k=

Comment
BCM94352 5Ghz Fix
Find

QYP8/3QsSA==

MatchOS
10.11.x
Name
AirPortBrcm4360
Replace

ZscGVVPrKw==

Comment
Yosemite Handoff
Find

SIX/dEdIiwc=

MatchOS
10.11.x,10.12.x
Name
IOBluetoothFamily
Replace

Qb4PAAAA60Q=

Comment
BCM94352 5Ghz Fix Sierra
Find

gflSqgAAdSk=

MatchOS
10.12.x
Name
AirPortBrcm4360
Replace

gflSqgAAZpA=

Number_of_KextsToPatch
8

thanks

Philip Petev · January 19, 2017

Who have a problem with 23702 please show your set of KernelAndKextPatches. Is there any empty patch?

I have no empty patches, but I have disabled ones (my config is based on a generic config for the whole ProBook 4x40s series by RehabMan):

<key>KextsToPatch</key>

<array>

<dict>

<key>Comment</key>

<string>change 15 port limit to 26 in XHCI kext (100-series)</string>

<key>Disabled</key>

<true/>

<data>

g72M/v//EA==

</data>

<string>AppleUSBXHCIPCI</string>

<key>Replace</key>

<data>

g72M/v//Gw==

</data>

</dict>

<dict>

<key>Comment</key>

<string>AppleHDA .xml.zl to .zml.zl</string>

<key>Disabled</key>

<true/>

<data>

LnhtbC56bA==

</data>

<string>AppleHDA</string>

<key>Replace</key>

<data>

LnptbC56bA==

</data>

</dict>

<dict>

<key>Comment</key>

<string>Enable TRIM for non-Apple SSDs</string>

<key>Disabled</key>

<data>

AEFQUExFIFNTRAA=

</data>

<string>IOAHCIBlockStorage</string>

<key>Replace</key>

<data>

AAAAAAAAAAAAAAA=

</data>

</dict>

<dict>

<key>Comment</key>

<string>Boot graphics glitch, 10.12.dp1 (credit denskop)</string>

<data>

AQAAdSU=

</data>

<string>IOGraphicsFamily</string>

<key>Replace</key>

<data>

AQAA6yU=

</data>

</dict>

<dict>

<key>Comment</key>

<string>Boot graphics glitch, 10.10.x/10.11.x (credit lisai9093, cecekpawon)</string>

<data>

AQAAdRc=

</data>

<string>IOGraphicsFamily</string>

<key>Replace</key>

<data>

AQAA6xc=

</data>

</dict>

<dict>

<key>Comment</key>

<string>AirPortBrcm4360 whitelist patch (board-id), 10.12.dp1, credit RehabMan</string>

<data>

MdtMO33YdRI=

</data>

<string>AirPortBrcm4360</string>

<key>Replace</key>

<data>

Mdv/w5CQkJA=

</data>

</dict>

<dict>

<key>Comment</key>

<string>AirPortBrcm4360 whitelist patch (board-id), 10.11.x, credit RehabMan</string>

<data>

MdtMO2XYdRI=

</data>

<string>AirPortBrcm4360</string>

<key>Replace</key>

<data>

Mdv/w5CQkJA=

</data>

</dict>

<dict>

<key>Comment</key>

<string>AirPortBrcm4360 whitelist patch (board-id), 10.10.5, credit RehabMan</string>

<data>

MdtJiwQkSDtF2HUS

</data>

<string>AirPortBrcm4360</string>

<key>Replace</key>

<data>

Mdv/w5CQkJCQkJCQ

</data>

</dict>

<dict>

<key>Comment</key>

<data>

WFQAIBcnIAAA

</data>

<string>AirPortBrcm4360</string>

<key>Replace</key>

<data>

WFQAG2cxlQAJ

</data>

</dict>

<dict>

<key>Comment</key>

<string>10.10.2+ 5Ghz US FCC, the-darkvoid</string>

<data>

QYP8/3QsSA==

</data>

<string>AirPortBrcm4360</string>

<key>Replace</key>

<data>

ZscGVVPrKw==

</data>

</dict>

<dict>

<key>Comment</key>

<string>10.10.2+ BT4LE-Handoff-Hotspot, Dokterdok</string>

<data>

SIXAdFwPt0g=

</data>

<string>IOBluetoothFamily</string>

<key>Replace</key>

<data>

Qb4PAAAA61k=

</data>

</dict>

<dict>

<key>Comment</key>

<string>10.11.dp1+ BT4LE-Handoff-Hotspot, credit RehabMan based on Dokterdok original</string>

<data>

SIX/dEdIiwc=

</data>

<string>IOBluetoothFamily</string>

<key>Replace</key>

<data>

Qb4PAAAA60Q=

</data>

</dict>

<dict>

<key>Comment</key>

<string>HDMI-audio HD3000, 0x00010000, port 0406</string>

<key>Disabled</key>

<data>

BAYAAAAEAAAJAAAA

</data>

<string>AppleIntelSNBGraphicsFB</string>

<key>Replace</key>

<data>

BAYAAAAIAAAJAAAA

</data>

</dict>

<dict>

<key>Comment</key>

<string>HDMI-video, 64MB BIOS, HD4000 0x01660004 #1 of 2</string>

<data>

BABmAQEDAQEAAAAC

</data>

<string>AppleIntelFramebufferCapri</string>

<key>Replace</key>

<data>

BABmAQECBAIAAAAE

</data>

</dict>

<dict>

<key>Comment</key>

<string>HDMI-video, 64MB BIOS, HD4000 0x01660004 #2 of 2 (order dependency, port 0406 patch)</string>

<data>

MAIAAAAAAAABAAAAQAAAAAAAAAABAAAAQAAAAAAAAAAB

AAAAQAAAAAAAAAAAAAAA

</data>

<string>AppleIntelFramebufferCapri</string>

<key>Replace</key>

<data>

MAIAAAIFAAAABAAABwQAAAMEAAAABAAAgQAAAAQGAAAA

BAAAgQAAAAAAAAAAAgAR

</data>

</dict>

<dict>

<key>Comment</key>

<string>HDMI-audio HD4000 0x01660003/0004, port 0406 (order dependency HDMI-video 0x01660004 above)</string>

<key>Disabled</key>

<data>

BAYAAAAEAACBAAAA

</data>

<string>AppleIntelFramebufferCapri</string>

<key>Replace</key>

<data>

BAYAAAAIAAAGAAAA

</data>

</dict>

<dict>

<key>Comment</key>

<key>Disabled</key>

<true/>

<data>

PYsZ1BE=

</data>

<string>AppleHDA</string>

<key>Replace</key>

<data>

Pdl2HRE=

</data>

</dict>

<dict>

<key>Comment</key>

<key>Disabled</key>

<true/>

<data>

PYQZ1BE=

</data>

<string>AppleHDA</string>

<key>Replace</key>

<data>

PQAAAAA=

</data>

</dict>

<dict>

<key>Comment</key>

<key>Disabled</key>

<true/>

<data>

PYMZ1BE=

</data>

<string>AppleHDA</string>

<key>Replace</key>

<data>

PQAAAAA=

</data>

</dict>

<dict>

<key>Comment</key>

<key>Disabled</key>

<true/>

<data>

PYoZ1BE=

</data>

<string>AppleHDA</string>

<key>Replace</key>

<data>

PQAAAAA=

</data>

</dict>

</array>

shaggymane · January 19, 2017

do I need to apply airport fix in order to use the Apple Store? If so I can't use the fix because it causes kernel panic

Maniac10 · January 20, 2017

Who have a problem with 23702 please show your set of KernelAndKextPatches. Is there any empty patch?

None disabled nor empty, though I do have a copy of KextsToPatch called #KextsToPatch where I moved some patches I can't use with this motherboard.

	<key>KernelAndKextPatches</key>
	<dict>
		<key>#KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>USB3 - Patch MSI or pin interrupts 2</string>
				<key>Find</key>
				<data>
				QcdHCAAAQAA=
				</data>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Replace</key>
				<data>
				QcdHCAAAAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>USB3 - Patch MSI or pin interrupts 1</string>
				<key>Find</key>
				<data>
				gUkIAABAAA==
				</data>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Replace</key>
				<data>
				gUkIAAAAAA==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>USB3 - Disable Intel USB3.0 10.10</string>
				<key>Find</key>
				<data>
				9oDUAAAAgHU0
				</data>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Replace</key>
				<data>
				9oDUAAAAgOs0
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>USB3 - Disable XHCI 1.0 check 10.10</string>
				<key>Find</key>
				<data>
				QbzHAgDgPQABAAA=
				</data>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Replace</key>
				<data>
				QbzHAgDgPQAAAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>USB3 - Enable PCI power management</string>
				<key>Find</key>
				<data>
				dU1Ii7voAQAA
				</data>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Replace</key>
				<data>
				601Ii7voAQAA
				</data>
			</dict>
		</array>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>KernelPm</key>
		<false/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>Fix Orange Disk</string>
				<key>Find</key>
				<data>
				RXh0ZXJuYWw=
				</data>
				<key>Name</key>
				<string>AppleAHCIPort</string>
				<key>Replace</key>
				<data>
				SW50ZXJuYWw=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Wi-Fi Region to RoW</string>
				<key>Find</key>
				<data>
				D7eH3AQAAA==
				</data>
				<key>Name</key>
				<string>AirPortAtheros40</string>
				<key>Replace</key>
				<data>
				uGoAAACQkA==
				</data>
			</dict>
		</array>
	</dict>

liujianwei · January 20, 2017

   <key>KernelAndKextPatches</key>
    <dict>
      <key>AppleRTC</key>
      <true/>
    </dict>

Micky1979 · January 20, 2017

mine:

<?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">
<array>
	<dict>
		<key>MatchBuild</key>
		<string>158778 16B2555</string>
		<key>MatchOS</key>
		<string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x,10.12.x</string>
		<key>Comment</key>
		<string>Enable TRIM for SSD</string>
		<key>Find</key>
		<data>AEFQUExFIFNTRAA=</data>
		<key>Name</key>
		<string>IOAHCIBlockStorage</string>
		<key>Replace</key>
		<data>AAAAAAAAAAAAAAA=</data>
	</dict>
	<dict>
		<key>MatchOS</key>
		<string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x,10.12.x</string>
		<key>Comment</key>
		<string>remove usb limit</string>
		<key>Find</key>
		<data>g72M/v//EA==</data>
		<key>Name</key>
		<string>AppleUSBXHCIPCI</string>
		<key>Replace</key>
		<data>g72M/v//Fg==</data>
	</dict>
	<dict>
		<key>MatchOS</key>
		<string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x</string>
		<key>Comment</key>
		<string>Zeroing 11d41983 codec</string>
		<key>Find</key>
		<data>gxnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>AAAAAA==</data>
	</dict>
	<dict>
		<key>MatchOS</key>
		<string>10.12.x</string>
		<key>Comment</key>
		<string>Zeroing 11d4198a codec (patched by AppleHDA Patcher.app)</string>
		<key>Find</key>
		<data>ihnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>AAAAAA==</data>
	</dict>
	<dict>
		<key>Comment</key>
		<string>Zeroing 11d41984 codec (patched by AppleHDA Patcher.app)</string>
		<key>Find</key>
		<data>hBnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>AAAAAA==</data>
	</dict>
	<dict>
		<key>Comment</key>
		<string>Patching 11d4198b with 111d76e0 codec (patched by AppleHDA Patcher.app)</string>
		<key>Find</key>
		<data>ixnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>4HYdEQ==</data>
	</dict>
</array>
</plist>

BTW commit r23702 introduce the "S" variant of some string functions and they later have done some corrections. the bug form me is in SafeString.c.

Maybe we should focus on strings that apparently contains some format string like '#', 'X' etc.?? (wont say something stupid.. but.. looks at Maniac10's config)

#	
Used with o, x or X specifiers the value is preceded with 0, 0x or 0X respectively for values different than zero. Used with e, E and f, it forces the written output to contain a decimal point even if no digits would follow. By default, if no digits follow, no decimal point is written. Used with g or G the result is the same as with e or E but trailing zeros are not removed.

@Maniac10 could you try w/o your unused #KextsToPatch?

smolderas · January 20, 2017

I've been having in the latest weeks the issue that my BIOS get reset after restarting (gigabyte), although I have AppleRTC set true. I'm booting legacy. Does anyone else have the same issue.

I'm now running the latest clover with the latest compatible edk2 version.

It is also possible that my mainboard dies...

Maniac10 · January 20, 2017

mine:

<?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">
<array>
	<dict>
		<key>MatchBuild</key>
		<string>158778 16B2555</string>
		<key>MatchOS</key>
		<string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x,10.12.x</string>
		<key>Comment</key>
		<string>Enable TRIM for SSD</string>
		<key>Find</key>
		<data>AEFQUExFIFNTRAA=</data>
		<key>Name</key>
		<string>IOAHCIBlockStorage</string>
		<key>Replace</key>
		<data>AAAAAAAAAAAAAAA=</data>
	</dict>
	<dict>
		<key>MatchOS</key>
		<string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x,10.12.x</string>
		<key>Comment</key>
		<string>remove usb limit</string>
		<key>Find</key>
		<data>g72M/v//EA==</data>
		<key>Name</key>
		<string>AppleUSBXHCIPCI</string>
		<key>Replace</key>
		<data>g72M/v//Fg==</data>
	</dict>
	<dict>
		<key>MatchOS</key>
		<string>10.7.x,10.8.x,10.9.x,10.10.x,10.11.x</string>
		<key>Comment</key>
		<string>Zeroing 11d41983 codec</string>
		<key>Find</key>
		<data>gxnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>AAAAAA==</data>
	</dict>
	<dict>
		<key>MatchOS</key>
		<string>10.12.x</string>
		<key>Comment</key>
		<string>Zeroing 11d4198a codec (patched by AppleHDA Patcher.app)</string>
		<key>Find</key>
		<data>ihnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>AAAAAA==</data>
	</dict>
	<dict>
		<key>Comment</key>
		<string>Zeroing 11d41984 codec (patched by AppleHDA Patcher.app)</string>
		<key>Find</key>
		<data>hBnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>AAAAAA==</data>
	</dict>
	<dict>
		<key>Comment</key>
		<string>Patching 11d4198b with 111d76e0 codec (patched by AppleHDA Patcher.app)</string>
		<key>Find</key>
		<data>ixnUEQ==</data>
		<key>Name</key>
		<string>AppleHDA</string>
		<key>Replace</key>
		<data>4HYdEQ==</data>
	</dict>
</array>
</plist>

BTW commit r23702 introduce the "S" variant of some string functions and they later have done some corrections. the bug form me is in SafeString.c.

Maybe we should focus on strings that apparently contains some format string like '#', 'X' etc.?? (wont say something stupid.. but.. looks at Maniac10's config)

#	
Used with o, x or X specifiers the value is preceded with 0, 0x or 0X respectively for values different than zero. Used with e, E and f, it forces the written output to contain a decimal point even if no digits would follow. By default, if no digits follow, no decimal point is written. Used with g or G the result is the same as with e or E but trailing zeros are not removed.

@Maniac10 could you try w/o your unused #KextsToPatch?

Sure, I'll try it tonight.

EDIT: It didn't boot either.

Edited January 21, 2017 by Maniac10

xelanaiznac · January 22, 2017

hi guys.

want to share with you a strange thing.

i have a maximus VIII gene + 6700k + 980ti and I used to install Sierra on that hack without using emuvariable64uefi.

yesterday I flash the new bios than I did I clean install and the result is that if I don't use emuvariable64uefi, Nvidia driver doesn't load.

so my question is: is emuvariable64uefi needed for Sierra?

I'm pretty sure that I did in the past month clean instal of Sierra without using it!!

Fljagd · January 22, 2017

hi guys.

want to share with you a strange thing.

i have a maximus VIII gene + 6700k + 980ti and I used to install Sierra on that hack without using emuvariable64uefi.

yesterday I flash the new bios than I did I clean install and the result is that if I don't use emuvariable64uefi, Nvidia driver doesn't load.

so my question is: is emuvariable64uefi needed for Sierra?

I'm pretty sure that I did in the past month clean instal of Sierra without using it!!

For my part, I do not use it

oswaldini · January 23, 2017

hi guys.

want to share with you a strange thing.

i have a maximus VIII gene + 6700k + 980ti and I used to install Sierra on that hack without using emuvariable64uefi.

yesterday I flash the new bios than I did I clean install and the result is that if I don't use emuvariable64uefi, Nvidia driver doesn't load.

so my question is: is emuvariable64uefi needed for Sierra?

I'm pretty sure that I did in the past month clean instal of Sierra without using it!!

Asus changed 3xxx BIOSes and brake nvram, same here for Z170 Pro Gaming BIOS 3016.

Slice · January 23, 2017

hi guys.

want to share with you a strange thing.

i have a maximus VIII gene + 6700k + 980ti and I used to install Sierra on that hack without using emuvariable64uefi.

yesterday I flash the new bios than I did I clean install and the result is that if I don't use emuvariable64uefi, Nvidia driver doesn't load.

so my question is: is emuvariable64uefi needed for Sierra?

I'm pretty sure that I did in the past month clean instal of Sierra without using it!!

For my GA-Z170X there are rules:

if BIOS F5 then emuvariable64uefi is not needed

if BIOS F20 then needed else graphics card will not light.

PMheart · January 24, 2017

Hi.

Could someone explain what's changed in Clover r3978? (https://sourceforge.net/p/cloverefiboot/code/3978/)

It seems that we introduce some new kernel patches. But in the latest 10.12.3 build 16D32 I don't get these datas...

Edit: I can still get NO data in the kernel of 10.12.2 build 16C68.

Edit 2:

Get nothing in the kernel of 10.12.1 build 16B2657.

Get nothing in the kernel of 10.12 build 16A323.

Get nothing in the kernel of 10.12 GM build 16A320.

Get nothing in the kernel of 10.12 PB4 build 16A284a.

Get nothing in the kernel of 10.12 PB1 build 16A238m.

Get nothing in the kernel of 10.12 DP1 build 16A201w.

So. What these patches will do?

IMHO. These could be NOP a jmp in KBESieDebugSearchEXT and KBESieDevelSearchEXT, and changed an offset that we shall jump to in KBESieDebugSearchSIP, KBESieDevelSearchSIP.

Also. It seems that the replacement for KBESieDebugSearchEXT and KBESieDevelSearchEXT is wrong. It NOP a short jmp (e9 09 00 00 00) but just replace with two NOPs. (90 90 00 00 00). This could be a problematic if KBESieDebugSearchEXT and KBESieDevelSearchEXT can be found.

If these ones really make a difference and then we should change the 'e9 09 00 00 00' above to '90 90 90 90 90' (fill the complete short jmp with nops). Or we can let the jmp jump to the next offset, change to 'e9 00 00 00 00'.

Edit: There's a little weird... I can even get nothing in the kernel of 10.11.6 build 15G31...

Edit: It seems that KBESieDebugSearchEXT == KBESieDevelSearchEXT, KBESieDebugSearchSIP == KBESieDevelSearchSIP?!?!

TBH the new patches really make a difference???

Thanks in advance.

PMheart

Clover General discussion

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