Refactor documentation for consistency and clarity across multiple files

AlienWolfX · AlienWolfX · commit e87929ee7119 · 2025-08-31T21:12:54.000+08:00
diff --git a/pages/Debian.md b/pages/Debian.md
@@ -1,6 +1,6 @@
-&nbsp;
+# Debian Installation Guide
 
-Based on Debian 6.7 with MSM8916 mainline support
+> Based on Debian 6.7 with MSM8916 mainline support
 
 ## Prerequisites
 
@@ -23,13 +23,13 @@ unzip openstick-uz801-v3.0.zip
 cd openstick-uz801
 ```
 
-3. Boot into fastboot mode:
+1. Boot into fastboot mode:
 
 ```bash
-adb reboot-bootloader
+adb reboot bootloader
 ```
 
-4. Flash the firmware:
+1. Flash the firmware:
 
 - **Windows**:
 
diff --git a/pages/Firmware(Dump_and_Restore).md b/pages/Firmware(Dump_and_Restore).md
@@ -1,22 +1,21 @@
-&nbsp;
+# Firmware Dump and Restore
 
 ## Entering EDL Mode
 
 There are two methods to enable Emergency Download (EDL) mode:
 
 ### Method 1: Using ADB
 
-For Stock firmware:
+**For Stock firmware:**
 
 ```bash
 adb reboot edl
 ```
 
-For OpenWRT:
+**For OpenWRT:**
 
 ```bash
 adb reboot bootloader
-
 fastboot oem reboot edl
 ```
 
@@ -42,6 +41,12 @@ python3 edl rf backup_filename.bin
 python3 edl wf backup_filename.bin
 ```
 
+### Creating Individual Partition Backups
+
+```bash
+python3 edl rl output_folder --genxml
+```
+
 ## Analyzing the Firmware
 
 You can examine the partition structure of your backup using these tools:
@@ -50,7 +55,9 @@ You can examine the partition structure of your backup using these tools:
 - 7-Zip
 - HxD (Hex Editor)
 
-> [!NOTE]
+## Important Notes
+
+> [!IMPORTANT]
 >
 > - Always keep a backup of your original firmware
 > - Ensure stable USB connection during operations
@@ -62,7 +69,9 @@ You can examine the partition structure of your backup using these tools:
 
 If the device is not detected in EDL mode:
 
-1. Check USB drivers
+1. Check USB drivers are properly installed
 2. Try different USB ports
 3. Verify cable connection
 4. Ensure proper EDL mode entry
+
+For Windows users: Install the QDLoader 9008 driver if not automatically detected.
diff --git a/pages/Home.md b/pages/Home.md
@@ -1,4 +1,4 @@
-&nbsp;
+# UZ801 v3.2 Documentation
 
 ## Welcome to the UZ801-USB_MODEM repository Wiki!
 
@@ -13,20 +13,23 @@ This Wiki contains extensive information and research findings about the UZ801 v
 - [Debian](https://github.com/AlienWolfX/UZ801-USB_MODEM/wiki/Debian)
 - [Troubleshooting](https://github.com/AlienWolfX/UZ801-USB_MODEM/wiki/Troubleshooting)
 
-## Required Tools
+## Prerequisites
 
-Before proceeding with any instructions in this guide, please ensure you have the following tools:
+Before proceeding with any instructions in this guide, ensure you have the following tools installed:
 
 - [edl](https://github.com/bkerler/edl)
 
-If you are using Windows, you must install the following:
+### Windows Users
+
+If you are using Windows, you must also install:
 
 - [Universal ADB Driver](https://adb.clockworkmod.com/)
 - [QDLoader 9008 Driver](https://qdloader9008.com/)
 - [ADB Platform Tools](https://gist.github.com/ifiokjr/b70882d3f1182ed48ec7eefa5c93a740)
 - [Zadig](https://zadig.akeo.ie/)
 
-On Windows, If you intend to use edl you might encounter this error: `NotImplementedError: Operation not supported or unimplemented on this platform`. One way to fix this is by uninstalling the QDLoader 9008 Driver and replacing it with Zadig WinUSB[⁽¹⁾](https://github.com/bkerler/edl/issues/349#issuecomment-2060152724).
+> [!NOTE]
+> If you encounter the error `NotImplementedError: Operation not supported or unimplemented on this platform` while using edl, uninstall the QDLoader 9008 Driver and replace it with Zadig WinUSB[⁽¹⁾](https://github.com/bkerler/edl/issues/349#issuecomment-2060152724).
 
 ## Contributing
 
diff --git a/pages/Modifications.md b/pages/Modifications.md
@@ -1,4 +1,4 @@
-&nbsp;
+# Modifications
 
 ## Root Access Setup
 
@@ -43,13 +43,13 @@ The default BusyBox installation lacks several commands (like `vi`). Here's how
 
 1. Download [BusyBox APK](https://github.com/AlienWolfX/UZ801-USB_MODEM/releases/download/rev1/busybox.apk)
 
-2. Install the APK:
+1. Install the APK:
 
 ```bash
 adb install busybox.apk
 ```
 
-3. Launch BusyBox:
+1. Launch BusyBox:
    - Follow the [View Display Guide](https://github.com/AlienWolfX/UZ801-USB_MODEM?tab=readme-ov-file#view-device-display)
    - Open BusyBox application
    - Tap "Install"
@@ -101,22 +101,22 @@ mv platform.keystore {YOUR_WORK_DIR}
 java -jar apktool.jar d MifiService.apk -o MifiService
 ```
 
-2. Make modifications in the `assets` folder or any part of the APK that you need to modify
+1. Make modifications in the `assets` folder or any part of the APK that you need to modify
 
-3. Recompile (use `android` as passphrase when prompted):
+1. Recompile (use `android` as passphrase when prompted):
 
 ```bash
 java -jar apktool.jar b -o unsigned.apk MifiService
 ```
 
-4. Sign and align:
+1. Sign and align:
 
 ```bash
 zipalign -v 4 unsigned.apk aligned.apk
 jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore ./platform.keystore aligned.apk testkey
 ```
 
-5. Install modified APK:
+1. Install modified APK:
 
 ```bash
 adb install -r aligned.apk
diff --git a/pages/OpenWRT.md b/pages/OpenWRT.md
@@ -1,16 +1,19 @@
-&nbsp;
+# OpenWRT Installation Guide
 
 ## Important Notes
 
 > [!WARNING]
 > The OpenWRT build is based on an older version of OpenWRT. While some packages and applications may have limited functionality, the build remains usable. This guide is intended for users with OpenWRT experience.
 
+> [!IMPORTANT]
+> If you cannot get a signal after installation, please refer to the [Region Change Guide](Troubleshooting.md#changing-modem-region).
+
 ## Installation Steps
 
 ### Prerequisites
 
 - Download [`openwrt-UZ801.tar.xz`](https://github.com/AlienWolfX/UZ801-USB_MODEM/releases) from releases
-- Ensure device is in fastboot mode
+- Ensure device is in EDL mode
 - Backup your current firmware (recommended)
 
 ### Installation Process
@@ -22,7 +25,7 @@ tar xf openwrt-UZ801.tar.xz
 cd OpenWRT-UZ801
 ```
 
-2. Run the appropriate flash script:
+1. Run the appropriate flash script:
 
 - **Windows**:
 
diff --git a/pages/Overview.md b/pages/Overview.md
@@ -1,4 +1,4 @@
-&nbsp;
+# Overview
 
 A couple of months ago, I purchased this 4G LTE USB dongle from Shopee for around 300+ PHP. Out of curiosity, I searched the internet to see if there was a way to modify the horrible web UI of the device. Here are some images of the device along with the board and its chips.
 
@@ -9,13 +9,11 @@ A couple of months ago, I purchased this 4G LTE USB dongle from Shopee for aroun
 | ![board1](https://i.ibb.co/jTwXYQ8/soc1.jpg "board1")   | ![board2](https://i.ibb.co/GWfPq4M/soc2.jpg "board2")   |
 | ![front](https://i.ibb.co/dQ82vyz/soc3.jpg "front")     |                                                         |
 
-## Device
+## Device Specifications
 
-The heart of the dongle is an MSM8916, running a stripped-down version of Android 4.4.4 KitKat. Interestingly, **the setup restricts the use of two other CPU cores, likely to prevent the device from overheating**.
+The heart of the dongle is an MSM8916, running a stripped-down version of Android 4.4.4 KitKat. Interestingly, **the setup restricts the use of two CPU cores, likely to prevent the device from overheating**.
 
-### Device Specs
-
-Processor:
+### Processor Information
 
 ```bash
 root@msm8916_32_512:/ $ cat /proc/cpuinfo
@@ -46,7 +44,7 @@ Serial          : 0000000000000000
 Processor       : ARMv7 Processor rev 0 (v7l)
 ```
 
-Ram:
+### Memory Information
 
 ```bash
 root@msm8916_32_512:/ $ cat /proc/meminfo
diff --git a/pages/References.md b/pages/References.md
@@ -1,4 +1,4 @@
-&nbsp;
+# References
 
 This project references the following resources:
 
diff --git a/pages/Troubleshooting.md b/pages/Troubleshooting.md
@@ -1,29 +1,42 @@
-&nbsp;
+# Troubleshooting
 
-## OpenWRT
+## OpenWRT Issues
 
-### No network/Modem stuck at searching
+### No Network/Modem Stuck at Searching
 
-First step is to extract the contents of modem.bin from your firmware dump if you use edl without `--genxml` flag you need to open the bin file with PowerISO or another software and extract the partition having type of `GPT FAT16`
+First, extract the contents of `modem.bin` from your firmware dump. If you used `edl` without the `--genxml` flag, you need to open the bin file with PowerISO or another software and extract the partition with type `GPT FAT16`.
 
-Once you have the `IMAGE` folder then go to this directory `IMAGE\MODEM_PR\MCFG\CONFIGS\MCFG_SW\GENERIC\` choose the folder according to your region:
+Once you have the `IMAGE` folder, navigate to this directory: `IMAGE\MODEM_PR\MCFG\CONFIGS\MCFG_SW\GENERIC\` and choose the folder according to your region:
 
-- APAC - Asia Pacific
-- CHINA - China
-- COMMON - (You can use this if your region is not in the folders list)
-- EU - Europe
-- NA - North America
-- SA - South America
-- SEA - South East Asia
+- **APAC** - Asia Pacific
+- **CHINA** - China
+- **COMMON** - Use this if your region is not listed
+- **EU** - Europe
+- **NA** - North America
+- **SA** - South America
+- **SEA** - South East Asia
 
-Once you have selected your region, you'll find a group of folders typically representing Telcos in your area. Click on the appropriate one until you locate `MCFG_SW.MBN`. Once found, proceed to transfer the file to your dongle by executing `adb push MCFG_SW.MBN /lib/firmware`. After the transfer is complete, execute `adb reboot`. You can now access the internet with your modem.
+Once you have selected your region, you'll find folders typically representing Telcos in your area. Navigate through the appropriate folder until you locate `MCFG_SW.MBN`.
+
+**To apply the fix:**
+
+1. Transfer the file to your dongle: `adb push MCFG_SW.MBN /lib/firmware`
+2. Reboot the device: `adb reboot`
+3. Your modem should now have internet access
 
 > [!NOTE]
-> There are instances that the modem doesn't automatically work, If you encounter this issue you need to execute `adb shell` and `mmcli -m 0 -e` to enable your modem.
+> If the modem doesn't automatically work, you may need to execute:
+>
+> ```bash
+> adb shell
+> mmcli -m 0 -e
+> ```
+>
+> This will manually enable your modem.
 
-### Connection Refuse
+### Connection Refused
 
-If you encounter this problem simply set this on your OpenWRT dashboard
+If you encounter this problem, configure the following settings in your OpenWRT dashboard:
 
 ```bash
 Name
@@ -45,9 +58,9 @@ Action
 MASQUERADE - Automatically rewrite to outbound interface IP
 ```
 
-### Can't use RNDIS after Installation
+### Can't Use RNDIS After Installation
 
-Download [RNDIS Driver](https://github.com/milkv-duo/duo-files/raw/main/common/RNDIS_drivers_20231018.zip) and add it your device manager
+Download the [RNDIS Driver](https://github.com/milkv-duo/duo-files/raw/main/common/RNDIS_drivers_20231018.zip) and add it to your device manager.
 
 Alternatively you can use `Microsoft USB RNDIS` driver.
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`- `
	`1`	`+# References`
`2`	`2`
`3`	`3`	`This project references the following resources:`
`4`	`4`