What the developer wrote
Authored by odudex
docs: update Mac driver troubleshooting II
What changed, and why it matters
This commit only updates user documentation about installing USB drivers on macOS and Windows. It changes the recommended macOS driver installation method to use the Homebrew package manager and makes minor formatting edits. There is no code change and no security issue.
No security action required. Treat as a normal documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies two documentation snippet files. For macOS, it replaces a direct download link to the CH341 driver with a brew install --cask wch-ch34x-usb-serial-driver command and bolds the opening phrase. For Windows, it only bolds the opening phrase. No source code, build scripts, or cryptographic material is touched.
Changed components
docs/snippets/error-flashing-mac.en.txtdocs/snippets/error-flashing-windows.en.txtInspect captured patch +7 / −3
diff --git a/docs/snippets/error-flashing-mac.en.txt b/docs/snippets/error-flashing-mac.en.txt
index 19cb809..766b349 100644
--- a/docs/snippets/error-flashing-mac.en.txt
+++ b/docs/snippets/error-flashing-mac.en.txt
@@ -1,2 +1,6 @@
-On macOS, you may also run into flashing errors. This often happens when a proper CH34X USB driver is missing, preventing proper communication with the device. To fix it, download and install the [CH341 driver](https://www.wch-ic.com/downloads/CH341SER_MAC_ZIP.html).
-After installing, you may also need to approve driver's "extension" in macOS system settings, identified as CH34xVCPDriver.app
\ No newline at end of file
+**On macOS**, you may also run into flashing errors. This often happens when a proper CH34X USB driver is missing, preventing proper communication with the device.
+To fix it, install the CH341 driver. In a terminal, type:
+```
+brew install --cask wch-ch34x-usb-serial-driver
+```
+After installing, you may also need to approve driver's "extension" in macOS system settings, identified as CH34xVCPDriver.app"
\ No newline at end of file
diff --git a/docs/snippets/error-flashing-windows.en.txt b/docs/snippets/error-flashing-windows.en.txt
index 1ce55e1..712cfc8 100644
--- a/docs/snippets/error-flashing-windows.en.txt
+++ b/docs/snippets/error-flashing-windows.en.txt
@@ -1,4 +1,4 @@
-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)*).
+**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;">
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.