10-05-2017 09:13 PM
Hi, I have just bought a factory refurbished X1 Carbon 5th gen and was going through the initial updates routine.
After the classical huge Win10 initial update, I opened Lenovo companion and started the update process.
It started a bios update, rebooted and after 5 minutes the screen went black.
I waited some time, tried pressing some keys... nothing. It's dead.
Is there any one with some experience on the subject that has some good ideas on how to wake it up?
10-05-2017 09:52 PM - edited 10-05-2017 09:54 PM
Sorry you're having trouble.
So it's fiully powered down, or in a hung state?
Not sure it will help, but you might try the emergency reset hole.
See page 6 in the user guide: https://download.lenovo.com/pccbbs/mobiles_pdf/x1_carbon_5th_ug_en.pdf
10-06-2017 01:35 AM
>It started a bios update, rebooted and after 5 minutes the screen went black.
In order to understand the current your situation clearly, what kind of screen activities you watched this 5 minuts duration after reboot?
Normally, when System Update kicked BIOS Update Utility, it copies BIOS and ECFW files and start the Windows shutdown process, then reboot to perform the actual BIOS update process by displaying text mode message/indicator. Did you see this BIOS update process, or you didn't see any screen contenst after reboot?
Did you see this BIOS update progress message/indicators ? or just
Have you seen this
10-06-2017 07:40 AM
Yes the update process started.
Update: Restarting the laptop produced a series of beeps. Using the official Lenovo PC diagnostic application to identify the beep signals showed a critical problem with the TCG-compliant-functionality. The suggested action is the replacement of the system board. I have now started a return procedure.
10-30-2017 09:53 AM
I have the same issue as well. My Thinkpad Twist is bricked after an unsuccessful install of the BIOS yesterday.
I called Lenovo Support and they had two solutions: a new motherboard at £x00's, or to buy a new laptop.
Not impressed with the customer support. This does seem to be a widespread problem with this BIOS release. Lenovo should be doing something about it.