Contribute
Register

Matebook 13 boot every two attempts

Status
Not open for further replies.
the KextsToPatch section in your config.plist:
Code:
        <dict>
                <key>Comment</key>
                <string>Zeroing 10ec0261 codec (patched by AppleHDA Patcher.app)</string>
                <key>Disabled</key>
                <true/>
                <key>Find</key>
                <data>
                YQLsEA==
                </data>
                <key>Name</key>
                <string>com.apple.driver.AppleHDA</string>
                <key>Replace</key>
                <data>
                AAAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Zeroing 10ec0262 codec (patched by AppleHDA Patcher.app)</string>
                <key>Disabled</key>
                <true/>
                <key>Find</key>
                <data>
                YgLsEA==
                </data>
                <key>Name</key>
                <string>com.apple.driver.AppleHDA</string>
                <key>Replace</key>
                <data>
                AAAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Zeroing 10ec0885 codec (patched by AppleHDA Patcher.app)</string>
                <key>Disabled</key>
                <true/>
                <key>Find</key>
                <data>
                hQjsEA==
                </data>
                <key>Name</key>
                <string>com.apple.driver.AppleHDA</string>
                <key>Replace</key>
                <data>
                AAAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Patching 11d41984 with 10ec0236 codec (patched by AppleHDA Patcher.app)</string>
                <key>Disabled</key>
                <true/>
                <key>Find</key>
                <data>
                hBnUEQ==
                </data>
                <key>Name</key>
                <string>com.apple.driver.AppleHDA</string>
                <key>Replace</key>
                <data>
                NgLsEA==
                </data>
            </dict>
delete all that above
All done, but this step :
* Moved "AptioMemoryFix-64.efi" from Clover/Drivers/UEFI to Clover/Driver64UEFI(Cant find AptioMemoryFix(non 64) in latest clover installation options)
OS won't boot(Stuck at "end random seed"), and I have to re put AptioMemoryFix-64.efi in Clover/Drivers.
 
Last edited:
Installed 4972v and put AptioMemoryFix-64.efi in Driver64Uefi folder and boot, but still the problem, one time it boots one time it reboot after few second from selection in clover

I don't know what try :'(
no problem reporting files uploaded....
 
no problem reporting files uploaded....
Just for curiosity, I've seen the boot log and I have a lot of row like this:

10:219 0:000 0. [_DSM to XDSM]: pattern 5F44534D, bin not found / already patched!
It's slowing boot time? can I remove it?

Scuse, here is the reporting
 

Attachments

  • MacBook Pro di Edoardo.ioreg
    6.6 MB · Views: 102
  • debug_25646.zip
    1.6 MB · Views: 51
Last edited:
Hey there, funny you’d mention that - I have the exact same problem with the exact same laptop haha. Sometimes it will boot fine, other times I need two or so attempts...
 
Hey there, funny you’d mention that - I have the exact same problem with the exact same laptop haha. Sometimes it will boot fine, other times I need two or so attempts...
We are in the @Feartech hands, but maybe it's related to some other things, so it's hard to fix with a log. I'm about to surrender
 
Just for curiosity, I've seen the boot log and I have a lot of row like this:

10:219 0:000 0. [_DSM to XDSM]: pattern 5F44534D, bin not found / already patched!
It's slowing boot time? can I remove it?

Scuse, here is the reporting
Why do you have a Fake ALS when you also have a real one?
I think NvmExpressDxe-64.efi can be safely removed.
It's fine to put kexts within Clover/Drivers/UEFI when using latest release. Make sure everything is really there, and that Drivers64UEFI is removed.

You should have necessary kexts in Clover/kexts/Other (while you still have them in /L/E). Put there kexts that are necessary for booting Recovery/Installer (SMC, display, I/O)

I see you don't have a Broadcom card, why do you have AirportBrcmFixup.kext?

You don't need keepsyms=1 in your config.plist.

Are your reboots kernel panics? I see you have some panic logs there, are you referring to them?
Can you attach a screenshot taken when booting verbose, before it reboots?
 
Why do you have a Fake ALS when you also have a real one?
I don't know what is "fake Als" I've copied some files from here and there(most from matebook X).
* I think NvmExpressDxe-64.efi can be safely removed.
* It's fine to put kexts within Clover/Drivers/UEFI when using latest release. Make sure everything is really there, and that Drivers64UEFI is removed.
* I see you don't have a Broadcom card, why do you have AirportBrcmFixup.kext?
* You don't need keepsyms=1 in your config.plist.
Will do it, and will delete airport kext and keepsysms=1

Are your reboots kernel panics? I see you have some panic logs there, are you referring to them?
Can you attach a screenshot taken when booting verbose, before it reboots?
Sometimes yes and even with panic, after some seconds the system boot fine, and sometimes it stucks with a black screen(in verbose mode, it just get black screen after some text rows)

nb. it's hard to reproduce panic, but will try. I think that panic comes because i reboot repeatelly laptop until boot success(by pressing without release the power button)
 
Last edited:
Why do you have a Fake ALS when you also have a real one? I don't know what is "fake Als" I've copied some files from here and there(most from matebook X).
You should have necessary kexts in Clover/kexts/Other (while you still have them in /L/E). Put there kexts that are necessary for booting Recovery/Installer (SMC, display, I/O)* Will do it
"AirportBrcmFixup.kext" Wil delete it
Well, no need to use the Fake ALS SSDT you have there. ALS = Ambient Light Sensor.

What about my last question, about your reboots?
 
Status
Not open for further replies.
Back
Top