diff options
Diffstat (limited to 'docs/install/t60_unbrick.md')
-rw-r--r-- | docs/install/t60_unbrick.md | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md index aab55241..7a0d4e7f 100644 --- a/docs/install/t60_unbrick.md +++ b/docs/install/t60_unbrick.md @@ -14,7 +14,7 @@ Table of Contents - Types of brick: - [Brick type 1: bucts not reset](#bucts_brick) - - [Brick type 2: bad rom (or user error), system won\'t + - [Brick type 2: bad rom (or user error), system won't boot](#recovery) @@ -23,11 +23,11 @@ Brick type 1: bucts not reset. {#bucts_brick} ============================== You still have Lenovo BIOS, or you had libreboot running and you flashed -another ROM; and you had bucts 1 set and the ROM wasn\'t dd\'d.\* or if -Lenovo BIOS was present and libreboot wasn\'t flashed.\ +another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if +Lenovo BIOS was present and libreboot wasn't flashed.\ \ In this case, unbricking is easy: reset BUC.TS to 0 by removing that -yellow cmos coin (it\'s a battery) and putting it back after a minute or +yellow cmos coin (it's a battery) and putting it back after a minute or two:\ ![](../images/t60_dev/0006.JPG)\ \ @@ -47,7 +47,7 @@ but instructions for t60 are identical) -bad rom (or user error), system won\'t boot {#recovery} +bad rom (or user error), system won't boot {#recovery} =========================================== In this scenario, you compiled a ROM that had an incorrect @@ -56,8 +56,8 @@ booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all. -\"Unbricking\" means flashing a known-good (working) ROM. The problem: -you can\'t boot the system, making this difficult. In this situation, +"Unbricking" means flashing a known-good (working) ROM. The problem: +you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). @@ -132,11 +132,11 @@ system:\ Now wire up the BBB and the Pomona with your PSU.\ Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for flashing.\ -**Note, the guide mentions a 3.3v DC PSU but you don\'t need this on the -T60: if you don\'t have or don\'t want to use an external PSU, then make +**Note, the guide mentions a 3.3v DC PSU but you don't need this on the +T60: if you don't have or don't want to use an external PSU, then make sure not to connect the 3.3v leads mentioned in the guide; instead, connect the AC adapter (the one that normally charges your battery) so -that the board has power (but don\'t boot it up)**\ +that the board has power (but don't boot it up)**\ ![](../images/t60_dev/0030.JPG)\ Correlate the following with the BBB guide linked above: @@ -156,7 +156,7 @@ Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot\_util. Alternatively, libreboot also distributes flashrom source code which can be built. -SSH\'d into the BBB:\ +SSH'd into the BBB:\ \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom** @@ -207,7 +207,7 @@ It lives!\ ![](../images/t60_dev/0071.JPG) ![](../images/t60_dev/0072.JPG) ![](../images/t60_dev/0073.JPG) -Always stress test (\'stress -c 2\' and xsensors. below 90C is ok) when +Always stress test ('stress -c 2' and xsensors. below 90C is ok) when replacing cpu paste/heatsink:\ ![](../images/t60_dev/0074.JPG) |