@@ -123,24 +123,30 @@ Probe for the flash chip:
123
123
flashrom --programmer ch341a_spi
124
124
```
125
125
>**💡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:
129
131
` ` ` 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
131
133
` ` `
132
134
133
135
It is a good idea to dump the firmware twice just to make sure you have the complete image.
136
+
134
137
` ` ` 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
136
139
` ` `
137
140
138
141
Then compare image 1 with image 2 and if there are no differences, you know you have the entire, non-corrupted image:
139
142
` ` ` bash
140
143
diff --side-by-side doorbell-1.bin doorbell-2.bin
141
144
` ` `
145
+ < /details>
146
+
142
147
# # 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>
144
150
145
151
Getting a md5 hash:
146
152
` ` ` bash
@@ -160,6 +166,7 @@ Getting a sha512 hash:
160
166
090ba7fcc514530399953de1e65dfc08851aabf08905eab21d501c0630900d445deda27634b5f70b5fe3861ffa735d001987ece7739f31e84a3e8c2f03a0b178 doorbellfirm.bin
161
167
162
168
` ` `
169
+ < /details>
163
170
164
171
# # Basic Analysis of the Firmware: 💻🕵️
165
172
To gather basic strings and identify potential embedded information in the firmware before performing further analysis:
0 commit comments