You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Robin Schneider e08046b2b6
Fix x220 ec firmware image file in radare project file
No fully decrypted version of this file is available yet.

Closes: #26
7 years ago
asm Fix right-win and right-menu key definitions 7 years ago
docs Merge pull request #29 from ypid/fix-docs 7 years ago
mec-tools@07a1b14073 Update mec-tools to get a couple of fixes 8 years ago
radare Fix x220 ec firmware image file in radare project file 7 years ago
scripts Add rm-on-fail to the hexpatch script, allowing more confidence that repeated make invocations will not accidentally succeed 7 years ago
t430.G1HT34WW.img.d Disable battery_validate.patch for all supported models to match docs 7 years ago
t430.G1HT35WW.img.d Mark t430 battery patch as known working 8 years ago
t430s.G7HT39WW.img.d BUG: remove extra line from patch file 8 years ago
w530.G4HT39WW.img.d After testing by MarzEz, mark the T530 battery patch as working. 7 years ago
x230.G2HT35WW.img.d Add patch to swap caps lock and escape 7 years ago
x230t.GCHT25WW.img.d Ensure that all battery patches have the same name 7 years ago
.gitignore Merge branch 'ypid-add-txt-dl-target' 7 years ago
.gitmodules Add x230 image and infrastructure 8 years ago
Descriptions.txt Add some ISO image details for newer systems. Or: A quick check on just how much different hardware can have the name 'X1' 7 years ago
LICENSE Add License details 8 years ago
Makefile Rearrange the clean target so we dont recursively delete things 7 years ago
README Make the USB stick instructions more failsafe, and add a warning about erasing the stick 7 years ago
autoexec.bat.template Add the checksum of the built FL2 to the details shown 8 years ago
fix-hdd-image-33554432.patch The t430 ISO images are slightly larger than all the other ones, so the hdd image fix does not apply. Fix this by selecting the patch to use based on the size of the hdd image 8 years ago
fix-hdd-image-38797312.patch The t430 ISO images are slightly larger than all the other ones, so the hdd image fix does not apply. Fix this by selecting the patch to use based on the size of the hdd image 8 years ago
t430.G1HT34WW.img.enc.slice Added T430 BIOS 2.57, plus battery patch 8 years ago
t430.G1HT35WW.img.enc.slice Add t430 bootable ISO 8 years ago
t430s.G7HT39WW.img.enc.slice Add t430s bootable ISO 8 years ago
t530.G4HT39WW.img.d Add t530 support - this appears to share the EC firmware with the w530 8 years ago
t530.G4HT39WW.img.enc.slice Add t530 support - this appears to share the EC firmware with the w530 8 years ago
w530.G4HT39WW.img.enc.slice Add image extractor for w530 8 years ago
x220.8DHT34WW.img.enc.slice Start extracting the FL2 files, and use that as the basis for extracting the firmware. This will allow us to update or diff against the FL2 file 8 years ago
x220.8DHT34WW.s01CB000.FL2.slice Start extracting the FL2 files, and use that as the basis for extracting the firmware. This will allow us to update or diff against the FL2 file 8 years ago
x230.G2HT35WW.img.enc.slice Start extracting the FL2 files, and use that as the basis for extracting the firmware. This will allow us to update or diff against the FL2 file 8 years ago
x230t.GCHT25WW.img.enc.slice Add image extractor for x230t 8 years ago
x250.N10HT17W.img.enc.slice Have a quick look at the x250 and x260 firmware, it looks like they are both ARC cpus with a similar layout. They both have different checksumming than the xx30 range and the x260 looks like it is not even encrypted (however there is a strange 256byte block at the top of the file - perhaps a signature) 8 years ago
x260.R02HT29W.img.slice Have a quick look at the x250 and x260 firmware, it looks like they are both ARC cpus with a similar layout. They both have different checksumming than the xx30 range and the x260 looks like it is not even encrypted (however there is a strange 256byte block at the top of the file - perhaps a signature) 8 years ago

README

The main purpose of this software is to patch the EC on xx30 series thinkpads
to make the classic 7-row keyboards work.  There are also patches included (but
disabled by default) to disable the authentic battery validation check.

With the patches included here, you can install the classic keyboard
hardware on many xx30 series laptops and make almost every key work properly.
The only keys that are not working are Fn+F3 (Battery) and Fn+F12 (Hibernate)

Unfortunately, it turns out that not all xx30 series thinkpads have the same
BIOS and EC arrangement - some do not have a "FL2" file in the BIOS update
image and thus the location of the EC to patch is missing.  This is known to
be the case with at least the L530.

* A full writeup of the hardware modifications needed can be found at:
    http://www.thinkwiki.org/wiki/Install_Classic_Keyboard_on_xx30_Series_ThinkPads

* More information for hacking on this can be found in the docs/HACKING.txt
  file.

* A video presenting how these thinkpad laptops were hacked is online:
    https://www.youtube.com/watch?v=Fzmm87oVQ6c

Step-by-step instructions:
--------------------------

This software expects to be run under Linux.  For best results, ensure you
have updated your BIOS to a recent version before starting.  If there is too
large a difference between the BIOS and EC versions then the flash process
will not complete.

1. Ensure you have installed the prerequisite packages
   On debian, this can be done with:

    apt-get install build-essential git mtools libssl-dev

2. Clone a copy of this repo on to your computer:

    git clone https://github.com/hamishcoleman/thinkpad-ec

3. Change to the directory created by the clone:

    cd thinkpad-ec

4. Show the list of laptops and USB image file names:

    make list_laptops

5. Choose your laptop model name from the list shown.
   E.G. "patched.x230.img" for a x230 laptop.

6. Using the name chosen in the previous step, make the fully
   patched image for this laptop (this will download the original
   file from Lenovo and patch it):

    make patched.x230.img

7. Insert your USB stick and determine what device name it has.
   (Note: chose a USB stick with nothing important on it, it will
   be erased in the next step) This command should help you find the
   right device:

    lsblk -d -o NAME,SIZE,LABEL

8. Write the bootable patched image onto the USB stick device (replace
   the "sdx" in this command with the correct name for your usb stick)

   WARNING: if you do not have the right device name, you might overwrite
   your hard drive!

   sudo dd if=patched.x230.img of=/dev/sdx

Your USB stick is now ready to boot and install the patched firmware.

Notes:
------

* You can also create a bootable CDROM image for burning to a disk
  by asking for a ".iso" file instead of the ".img" in step 6 above.
  Then you can use your normal CDROM burning tools to put this image on
  a blank cd and boot it up, skipping steps 7 and 8.

* To include the battery validation patch or to make a build that
  reverts any EC changes, read the docs/CONFIG.txt and follow
  the configuration instructions in it before running step 6.


Booting the stick and flashing the firmware:
--------------------------------------------

While flashing the firmware is as simple as booting the USB stick
created above, there are a couple of steps that can help the process.
This is more a list of issues that the community has discovered as the
patch was applied in different circumstances than a hard and fast set
of requirements.

* The firmware flash process generally requires you to have a charged
  battery plugged in to the laptop before it will complete.

* Ensure your BIOS has been configured to boot from "Legacy" and not
  "UEFI" before trying to boot.

* If you do normally use UEFI boot, there has been at least one case where
  the EC does not get flashed until the BIOS is switched back into UEFI
  mode - after which the EC was automatically flashed on the next reboot.

* When you boot the stick, you will be shown information about the patch,
  including which laptop type it was built for.  It pauses at this point
  for you to confirm that you wish to proceed.  It will then automatically
  flash the patched firmware.