Skip to content

Commit 99a4e9e

Browse files
Update README.md
1 parent b9f8b15 commit 99a4e9e

File tree

1 file changed

+13
-6
lines changed

1 file changed

+13
-6
lines changed

README.md

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -123,24 +123,30 @@ Probe for the flash chip:
123123
flashrom --programmer ch341a_spi
124124
```
125125
>**💡Important:**
126-
> Always probe first to try and get the name of the chip.
127-
128-
Read and dump the firmware:
126+
>Always probe first to try and get the name of the chip.
127+
## Ok, Let's get hands on: ✋🤚
128+
<details>
129+
<summary> Read and dump the firmware: </summary>
130+
Commands:
129131
```bash
130-
flashrom --programmer ch341a_spi --chip [Chip Name] --read doorbell-1.bin
132+
flashrom --programmer ch341a_spi --chip [Chip Name] --read doorbell-1.bin
131133
```
132134

133135
It is a good idea to dump the firmware twice just to make sure you have the complete image.
136+
134137
```bash
135-
flashrom --programmer ch341a_spi --chip [Chip Name] --read doorbell-2.bin
138+
flashrom --programmer ch341a_spi --chip [Chip Name] --read doorbell-2.bin
136139
```
137140

138141
Then compare image 1 with image 2 and if there are no differences, you know you have the entire, non-corrupted image:
139142
```bash
140143
diff --side-by-side doorbell-1.bin doorbell-2.bin
141144
```
145+
</details>
146+
142147
## Before we begin analysis, it's a good idea to first get a hash of the image:
143-
There are several command line utilities that we could use for this including `sha256sum,` `sha512sum` and `md5sum.`
148+
<details>
149+
<summary> There are several command line utilities that we could use for this including sha256sum, sha512sum and md5sum. </summary>
144150

145151
Getting a md5 hash:
146152
```bash
@@ -160,6 +166,7 @@ Getting a sha512 hash:
160166
090ba7fcc514530399953de1e65dfc08851aabf08905eab21d501c0630900d445deda27634b5f70b5fe3861ffa735d001987ece7739f31e84a3e8c2f03a0b178 doorbellfirm.bin
161167
162168
```
169+
</details>
163170

164171
## Basic Analysis of the Firmware: 💻🕵️
165172
To gather basic strings and identify potential embedded information in the firmware before performing further analysis:

0 commit comments

Comments
 (0)