[Solved] Installer cannot boot m3-7y30

[RehabMan]

What do you mean? The usb should be correctly configured because I can use it to boot El capitan... What I should modify? (I used spoofed config.plist for El capitan, while I use not spoofed for high Sierra)

The USB guides are linked from the FAQ.
You should start by reading them.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

 

[AldoTar]

The USB guides are linked from the FAQ.
You should start by reading them.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Made it, from El capitan I cloned the installer onto the ssd and then run the installer from that... It worked...
Now I have only to configure osx

 

[RehabMan]

Made it, from El capitan I cloned the installer onto the ssd and then run the installer from that... It worked...
Now I have only to configure osx

And you will soon discover why USB was not working...

 

[AldoTar]

And you will soon discover why USB was not working...

Why?
However I tried disassemble DSDT/SSDT but I got the error in photo... Then I don't know what to patch

 

[RehabMan]

Why?

Because you'll be able to look at what is going on in ioreg as you work through the USB guides.

However I tried disassemble DSDT/SSDT but I got the error in photo... Then I don't know what to patch

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.

 

[AldoTar]

Because you'll be able to look at what is going on in ioreg as you work through the USB guides.


No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the gen_debug.sh tool mentioned in the FAQ, that way it is less likely you'll omit something.

What's that error recompiling the files?

 

[RehabMan]

What's that error recompiling the files?

I disassembled with: iasl -da -dl DSDT.aml SSDT*.aml

Then fixed the (very common) BNUM problem by removing the "External (BNUM, UnknownObj)" line.
Result: no errors in DSDT.dsl

Make sure you're using correct tools and procedures. See guide:
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

Note: You should re-install Clover to re-create the correct directory structure (eg. ACPI/patched ACPI/origin vs. what you have now 'AICP'...)

 

[AldoTar]

I disassembled with: iasl -da -dl DSDT.aml SSDT*.aml

Then fixed the (very common) BNUM problem by removing the "External (BNUM, UnknownObj)" line.
Result: no errors in DSDT.dsl

Make sure you're using correct tools and procedures. See guide:
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

Note: You should re-install Clover to re-create the correct directory structure (eg. ACPI/patched ACPI/origin vs. what you have now 'AICP'...)

Uhm thanks.. One question, what I should do to fix the ig-platfrom-id that I set to 0x12345678, I don't understand and see a guide to patch edid(than should I modify 0x12345678 or leave it?)
Thanks

 

[RehabMan]

Uhm thanks.. One question, what I should do to fix the ig-platfrom-id that I set to 0x12345678, I don't understand and see a guide to patch edid(than should I modify 0x12345678 or leave it?)
Thanks

You will need to find an ig-platform-id that works (try them all systematically). You may need to inject EDID. And you may need to use other kexts (depends on screen resolution).

You should start by filling out your profile as per FAQ (for example, screen resolution is missing)