The secret Thinkpad powerbutton code to bring dead laptops back to life (2007)
masnick.com
masnick.com
Spent hours disassembling it and probing various test points, all to no luck. It seems the issue was somewhere before powering up the CPU, and therefore kinda out of my expertise.
But this method seems to have brought it back to life.
Shame I've now cannibalized the screen and trackpad and CPU heatsink :-(
Did you try just turning it on before trying this method?
Not really, no
I believe the idea of "draining charge that shouldn't be there" has been properly conveyed nevertheless.
I submit that a definition of static electricity as "charge at rest at non-ground potential" is so broad as to exist in any non-trivial circuit and many trivial circuits. Such a definition is therefore less useful than more common notion as electricity generated as a result of physical surface interactions of dissimilar materials.
Calling it "static electricity" is likely to cause reasonably intelligent and well-educated people to conclude it's related to wearing wool socks in Winter while being insufficiently grounded, as opposed to charge being there as a result of normal circuit operation.
Looks like there's no standard term that everyone uses; I'd say it's entirely forgivable that the tech called it "static" for lack of a better word.
The description of this "flea power" reads like some cargo cult narrative that summarily conflates a handful of disjoint electrical characteristics/phenomena. It's like the modus operandi of interwebs consumerism.
I had to force it to power off, but that apparently broke it, it won't light up the screen and respond to inputs despite blowing the fan. I disassembled the screen and replugged the data cable, pressed power button in various ways to no avail.
I was about to give up before reading a forum post describing a similar laptop, and emptyed the RAM slots and found it beeped when powered up, so the CPU is OK.
I then unplugged the battery and CMOS battery and pressed power button for a while, put RAMs and batteries back on, and it just revived.
Removing RAMs made the difference, it's done if RAMs were soldered on.
It happened again a few days ago after it was left with no power, and I had to do those thing again, otherwise it has no issues. I think the CMOS battery is probably dead.
Once in a while after a resolution switch (e.g. exiting a game), one of my displays will go into its sleep mode and won't come back. Unplugging it and hitting the power button a few times fixes this, no PC restart needed. My friend had a TV that'd do something similar once in a while and this fix worked for him as well.
I'd be willing to bet the specific sequence in this article isn't really important, but rather that you're draining every capacitor in the PC by hitting the power button without a power source available (my understanding of what's happening with my fix).
The one I usually work with (LTC2954) does have an RC circuit attached to it to determine how long to hold the button to force a shutdown. And I'd wager a guess that this is the capacitor you're discharging by kicking the controller a few dozen times. But there's no possible way I can see that you're discharging every cap in the system.
The procedure to restore it sounds similarly weird. You plug and unplug video connectors, the monitor power and boot/shutdown the computer in a certain sequence. I didn't believe that worked when I first read about it. I've done it several times over the years however and it did in fact restore the EDID every single time.
https://www.tablix.org/~avian/blog/archives/2010/06/the_curi...
Unplug it, press the power button, watch as the LED lights up briefly (before the monitor discharges), then plug it all back in and it would work.
One day the screen went black and stayed that way. Hard reset did nothing. The screen didn't turn on when charging, but the watch got warm. Apple tech support said it was a hardware problem and I would need them to service the watch.
This is a 1st generation watch though, and their nearly $200 service fee seemed excessive. So I just let the watch sit around for a week or so. Then I tried charging it again and it worked!
What must have happened was that it was either a really bad software issue of some kind or an intermittent hardware issue that prevented the watch from working or rebooting, but when the power gave completely out and it was recharged, everything was set back into a functioning state.
The watch has worked perfectly (or as well as it ever did) for weeks now.
I copy the "trick" here, to have it available, in case that page disappears:
"push the power button 10 times in a row at one second intervals. Next, you push and hold the power button for 30 seconds. Then you put the battery back in and push the power button… and she lives. The computer came back, good as ever"
https://web.archive.org/web/20080310221514/http://www.masnic...
The idea was if you decided you didn't want /cats.html archived you'd robot.txt it, archive.org would notice, and delete the archive; but it also meant if the domain changes and robots.txt just blocked everything, everything would be lost.
Is this specific order a thinkpad related order, or is this just a generalized discharge reset? I realize that its fairly common to need to discharge, but is the order (10 presses here, hold for X amount of seconds there) important?
This sounds like a sequence designed to get people to wait long enough until the computer is fully drained of power, causing any latch-ups to clear. Sometimes a tech (or their troubleshooting tree) will have you unplug/debattery the computer, then read out serial numbers or something to accomplish this task without you noticing. I bet if you just removed the power sources, then waited a minute timed by a stopwatch it would work just as well.
There is a art to making troubleshooting steps resolve a problem without the customer needing to tell the technician they made a bone headed mistake. Really well written steps like these ones make it so the customer is completely unaware that the actual problem was that they did not wait long enough.
The apprentice noticed his machine was malfunctioning. He consulted his sensei who suggested to simply turn the machine off and back on.
The apprentice tried this many times yet the machine still did not work correctly.
Then the sensei turned the machine off and back on. It worked.
> Knight, seeing what the student was doing, spoke sternly: “You cannot fix a machine by just power-cycling it with no understanding of what is going wrong.”
> Knight turned the machine off and on.
> The machine worked.
But at least I now know this trick for the next time I need to do something like that. Thanks!
The ones where weird sequences do something are with power still plugged in (the chipset can react differently when it notices the power button is held down as it turns on, etc).
If there was a "no dial tone" call the first thing I needed to check was obviously if the phone cord was plugged in. And I had a few of these calls that ended the same way: me several pages deep in the troubleshooting tree before the customer sheepishly admitting that the phone cord wasn't plugged in.
I asked my coworkers and they all had their own tricks. One liked to have the caller unplug/plug the wire back in at the modem while they looked for a serial number printed by the jack. Another knew the Bell system pinout order and would have customers unplug and "check the wires" on both ends to be sure they "had the right wire". No one cared what the results of those questions were – of course the cord you bought from Radio Shack was wired up correctly. But you checking means you have to unplug and plug back in and that makes you discover that "oops, when I moved the filing cabinet I must've ripped the plug out of the wall". Or "oops, the pin on the back of the modem broke off and I was too cheap to get a new one and it wasn't making contact". Or whatever.
About a week ago my fairly new Clevo OEM/ODM (the actual badge on it doesn't really matter) laptop wouldn't come back to life from sleep – screen was black. The AC cable/power light and the battery light, both those lights were on meaning the machine wasn't dead dead. After waggling the mouse a bit, running my finger over the trackpad, pressing the power button a bunch of times, and striking random keys on the keyboard … I still had a dead laptop. So I did what any one of us would normally do in this situation. I held down the power button for a good ten seconds expecting the machine to power off, and from there I expected to boot the machine back up and have it complain to me that it had been unsummarily shut-off and could I please not do that.
No dice.
Tried this reliable technique a few times and still no dice. I could not believe that my newish laptop (about three months old) was dead as a door-nail. So unresponsive that not even holding down the power button until it switched itself off would work. Absolutely black-pilled and pretty determined to ask the manufacturer for a refund I rang up tech support fully expecting to be on hold for about half-an-hour but thankfully got through fairly quickly. I explained the situation to the techie and was surprised when they said, “Disconnect power, take out the battery, hold the power button for 30 seconds.” I've been around computers a long time and I'd never hear this one. Extremely dubious I did what I was told and, as you say, “Voila. Fixed.” Machine sprung back to life. (After reinserting battery, reconnecting power, pressing power button – obviously.)
What. Sorcery. Is. This?
My DELL has a press and hold the power button an arbitrary period of time to do something similar when it won't reboot.
And there I found this one https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/... which says, literally:
Remove the battery
Press power button 10 times
Press power button down for 30 seconds
Press power button twice
Attach ac adapter
Press power button once. PC should come up. Perform normal start up. Everything should be fine.
Shut down and reinstall the battery
After looking at Millionshort, it's pretty sad to go back to Google and realize that it is unable (or unwilling) to move beyond simple ranking and group results into categories.
I'm sure the underlying problem was some kind of hardware damage because I dropped that laptop so often that it's a miracle the thing still boots in the first place.
Sent it back to Lenovo for warranty repair. Waiting on parts... estimate is 4 months!
Not sure if right-to-repair could have helped me get it fixed faster locally.
Have done this a few times.