Public commit record
53/100 · Thin
What the developer wrote
Authored by Tads
Docs troubleshooting wonder-mv (#788)
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
What changed, and why it matters
This commit only updates user documentation. It reorganizes troubleshooting instructions for flashing Krux firmware onto WonderMV and Yahboom devices and removes an unused snippet file. There are no code changes and no security implications.
Recommended action
No security action required; this is a routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is limited to Markdown documentation files in the docs/ directory. It moves Windows CH340/341 driver guidance and WonderMV hardware-reset advice into the troubleshooting page, replacing an included snippet. No source code, build scripts, firmware, or installer logic was modified.
Changed components
docs/getting-started/installing/from-gui/usage.en.mddocs/snippets/error-flashing-windows.en.txtdocs/troubleshooting.en.mdInspect captured patch +8 / −11
diff --git a/docs/getting-started/installing/from-gui/usage.en.md b/docs/getting-started/installing/from-gui/usage.en.md
index f249ea3..6f28d6b 100644
--- a/docs/getting-started/installing/from-gui/usage.en.md
+++ b/docs/getting-started/installing/from-gui/usage.en.md
@@ -200,10 +200,8 @@ flash-krux-logo.en.txt
##### Error flashing
-----8<----
-error-flashing-windows.en.txt
-----8<----
+If **Krux-Installer** shows a **flash failed** error or freezes at **PLEASE DO NOT UNPLUG YOUR DEVICE** with the message **INFO Trying to Enter K210 ROM ISP Mode…**, it means the installer couldn’t establish a proper connection to the device. See the [troubleshooting](/krux/troubleshooting/#error-when-flashing) section for guidance on how to fix this.
#### Air-gapped update with
diff --git a/docs/snippets/error-flashing-windows.en.txt b/docs/snippets/error-flashing-windows.en.txt
deleted file mode 100644
index 1ce55e1..0000000
--- a/docs/snippets/error-flashing-windows.en.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-On Windows, you may encounter the **flash failed** error when trying to flash Yahboom or WonderMV using **Krux-Installer**. This means that Windows could not find the driver to communicate with the device via USB (an unrecognized *USB Serial* will be listed in *Device Manager -> Other devices*). To fix this, download and install the [CH340/341 driver](https://www.wch-ic.com/downloads/ch341ser_exe.html) (a *USB-SERIAL CH340* will be listed in *Device Manager -> Ports (COM & LPT)*).
-
-<img src="/krux/img/krux-installer/flash-failed.jpg" style="width: 38%; min-width: 320px;">
-<img src="/krux/img/krux-installer/usb-serial.jpg" style="width: 30%; min-width: 240px;">
-<img src="/krux/img/krux-installer/usb-serial-driver.jpg" style="width: 25%; min-width: 180px;">
\ No newline at end of file
diff --git a/docs/troubleshooting.en.md b/docs/troubleshooting.en.md
index 1d39642..a159e4e 100644
--- a/docs/troubleshooting.en.md
+++ b/docs/troubleshooting.en.md
@@ -44,9 +44,13 @@ If the device behaves this way when connected to the computer, Windows is known
### Error when flashing
If flashing fails with an error: `Greeting fail, check serial port (SLIP receive timeout (wait frame start))` or `[ERROR] No vaild COM Port found in Auto Detect, Check Your Connection or Specify One by --port/-p`, double check the command used. Most of devices need to pass the argument `-B goE` to *ktool*, but `dock` and `wonder_mv` uses the argument `-B dan` instead. For `yahboom` you also need to manually specify the port using the `-p` argument.
-----8<----
-error-flashing-windows.en.txt
-----8<----
+**WonderMV**: Some units have a hardware issue that can leave the device in a bad state in which it can't be flashed . If flashing fails, unplug the USB cable, wait 10+ seconds to allow the hardware to fully reset, then reconnect and retry.
+
+On **Windows**, you may encounter the **flash failed** error when trying to flash Yahboom or WonderMV using **Krux-Installer**. This means that Windows could not find the driver to communicate with the device via USB (an unrecognized *USB Serial* will be listed in *Device Manager -> Other devices*). To fix this, download and install the [CH340/341 driver](https://www.wch-ic.com/downloads/ch341ser_exe.html) (a *USB-SERIAL CH340* will be listed in *Device Manager -> Ports (COM & LPT)*).
+
+<img src="/krux/img/krux-installer/flash-failed.jpg" style="width: 38%; min-width: 320px;">
+<img src="/krux/img/krux-installer/usb-serial.jpg" style="width: 30%; min-width: 240px;">
+<img src="/krux/img/krux-installer/usb-serial-driver.jpg" style="width: 25%; min-width: 180px;">
## **After Installing**
Risk score
Our methodology →Why this scored 15/100
Human-validated context
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
No validated notes yet.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.