u/Dizzy_Ad_4872

Hi all,

I have a few VSOL V2802DAC v5 units and I'm looking to do some "white-labeling" or rebranding for a small project. Specifically, I want to change the default logos, CSS, and perhaps some default config settings in the Web UI.

I’ve managed to extract the firmware, but the upgrade process seems very pick about the modified files.

Has anyone here worked with VSOL firmware before? I'm looking for advice on:

  • How to safely flash modified firmware without getting "Update Failed" errors.
  • If there's a hidden "Super Admin" or "Engineer" mode that allows for easier UI customization.
  • Any community tools for VSOL/Realtek firmware modding.

Thanks in advance for any help!

reddit.com
u/Dizzy_Ad_4872 — 14 days ago

 Hey everyone,

I'm currently working on a project to rebrand and customize the web UI for a VSOL V2802DAC v5 ONU router (Firmware V3.2.00).

What I've done so far:

  • Extracted the firmware components: uImage (kernel), rootfs (SquashFS), and custconf.
  • Analyzed the fwu.sh upgrade script to understand the partition mapping and MD5 verification process.
  • Successfully modified the web assets in the SquashFS filesystem.

The Problem: I'm running into some issues with the "round-trip" process. Specifically, ensuring the modified rootfs (repacked with xz compression) is accepted by the bootloader/upgrade script without bricking. I've noticed differences in the custconf partition sizes between the "Normal" and "VSOL" versions of the firmware that I can't quite account for.

Questions:

  1. Has anyone successfully bypassed or modified the signature/integrity checks on these Realtek-based VSOL units?
  2. Are there specific mksquashfs parameters required for this hardware beyond standard xz compression?
  3. Does anyone have experience with the custconf partition structure for VSOL?

Any pointers or documentation on VSOL's specific MTD layout would be greatly appreciated!

reddit.com
u/Dizzy_Ad_4872 — 14 days ago