Have you messed up your QuestionXMG laptop by putting in the wrong EC chip? What should I do to fix it?
Have you messed up your QuestionXMG laptop by putting in the wrong EC chip? What should I do to fix it?
Hey everyone, I have trouble with my XMG laptop's mainboard from Schenker technologies: Board Information Manufacturer: NB02 Product Name: GMxNGxx Version: Standard Serial Number: Standard Asset Tag: Standard. Just now, I accidentally flashed the wrong EC firmware. Turns out, there were only problems with the lid device, meaning when the battery isn't full, the screen doesn't stay on (ACPI: button: The lid device is not compliant to SW_LID.). -> The incorrect EC was just a single file, version EC-1.23.61. -> The right EC comes along with the current BIOS, version EC-1.30.xx Unfortunately, my BIOS still shows the old EC version, even though I had recently flashed the new one. The BIOS itself did get updated to the new version. The manufacturer doesn't reply to me. My search for other sources for the mainboard didn't work well. Does anyone know what to do?
Why? Did you try emailing? Do you have a reply with a ticket number? If not, check this help article. To begin, please forward your message to [email protected] . We'll ask for your serial or order number and send the right firmware later separately. Cheers, Tom
I don't know how that happened. I got no reply at all. No ticket number, no proof of forwarding. I tried using the email addresses on the website and sent a message through my usual e-mail provider (t-online.de) to [email protected] and [email protected]. Thank you for sending me the right address! ### EDIT: I just emailed them at the community address, but I changed to @mail.ch so other companies won't get into trouble with me.
We got an email and replied back. Our e-mail server has some trouble with spam filters from Microsoft. Right now we have to look at the spam boxes one by one to find your emails. So most of your messages are getting lost somewhere along the way. It looks like you missed us because of a mistake made by humans. We talked to Microsoft's cloud team about this problem and started fixing it right away. If we don't get things fixed soon, we might have to tell everyone on our pages or in our forums. Sorry for all the trouble you had. Best regards, Tom (Product Manager / Community Manager)