04-09-2014 11:49 AM
I flashed the middleton BIOS for an R61i (14.1" model 7732 with firewire): battery is also dead, so I used WinPlash.exe directly, skipping WINUPTP.EXE. (As the latter insists on a charged battery.)
I renamed the image files as well, but I guess it’s of no importance. – Initially I thought `platform.bin` is linked to from `bios.rom`, but no. It turned out that the embedded controller did not got flashed! I was lucky the new BIOS worked with the old controller.
Once rebooted into Windows, I restarted the tool and selected platform.bin, flashed it (I got a warning, see below), then canceled the reboot (be quick!), then selected bios.rom and flashed it again. – And I ended up with a working system with both BIOS and EC updated.
How did I know the tool can do multiple flashes in a row without reboot?
How did I know platform.bin will not get flashed over the BIOS instead of updating the Embedded Controller?
Did I get any surprises?
Anything on the timing?
03-05-2019 12:07 PM - edited 03-05-2019 12:08 PM
Just wanted to say thanks. Flashed the BIOS and Platform on a ThinkPad L412 with this process.
I understand why Lenovo/IBM don't want you to flash without a charged battery but not giving the option after a clear warning is pretty ridiculous. It's not like millions upon millions of PC's, TV's, Printer's, IP Phones, etc. etc. aren't flashed yearly without a battery backup.
Avoid flashing during Thunderstorms, Tsunami's and Hurricanes, you'll probably be ok without backup power
03-05-2019 12:15 PM
Looks like someone figured it out (see below). Thanks for for going so far out of your way to weigh in with an effortless, completely unhelpful response though. It's comforting to know you're out there. "Moderating"