diff --git a/Document0-Initial_Information_Gathering.md b/Document0-Initial_Information_Gathering.md
index 99f7a39..b850afd 100644
--- a/Document0-Initial_Information_Gathering.md
+++ b/Document0-Initial_Information_Gathering.md
@@ -117,6 +117,7 @@ Here you can see:
 
 ## 1.5 Software Components from Firmware Analysis
 
+#TODO
 
 ## 1.6 Collect "Fresh" Firmware Dump
 
@@ -124,7 +125,9 @@ The device has been tampered with before, therefore there is no fresh dump avail
 
 ## 1.7 && 2.3 Initial setup
 
-The initial setup is done using the Shelly App. The capture can be found [here](captures/init.pcapng).
+The initial setup is done using the Shelly app. The capture can be found [here](captures/init.pcapng).
+
+Additionally, the Shelly app offers to download the data stored on the device, which you can find [here](lock_data/after_init/README.md).
 
 Unsure which IP address is most relevant, here are all Shelly-like or LOQED-like addresses:
 - `34.62.47.252`: changelog-backend.shelly.cloud0
@@ -181,13 +184,9 @@ However, ToothFairy labelled `WRLS-FUZZ-002` as `FAIL`, due to the target not re
 
 ### Outer Module
 
-## 1.9 && 2.4 Firmware Update
+## 1.9 && 2.4 Firmware Update / 1.10 Collect Updated Firmware Dump
 
-## 1.10 Collect Updated Firmware Dump
-
-### Bridge
-
-### Outer Module
+There is no FW update available.
 
 ## 1.11 Collect Firmware Dump after Factory Reset
 
diff --git a/firmware/inner_module/boot.txt b/firmware/inner_module/boot.txt
new file mode 100644
index 0000000..158cf13
--- /dev/null
+++ b/firmware/inner_module/boot.txt
@@ -0,0 +1,5 @@
+000000 ff 00 00 00 2a 00 ff ff ff 41 01 00 02 3d 89 32  >....*....A...=.2<
+000010 00 ff ff ff 41 01 00 02 3d 89 32 00 ff ff ff 41  >....A...=.2....A<
+000020 01 00 02 3d 89 32 00 ff ff ff 41 01 00 02 3d 89  >...=.2....A...=.<
+000030 32 00 ff ff ff 41 01 00 02 3d 89 32 00 ff ff ff  >2....A...=.2....<
+000040 41 01 00 02 3d 89 32 00 ff ff ff 41 01 00 02 3d  >A...=.2....A...=<