Older Firmware for USG FLEX 500

Options
CscCsc
CscCsc Posts: 3 image  Freshman Member
First Comment
in Security

Good evening,

I am requesting assistance regarding a Zyxel USG FLEX 500 firewall that is experiencing a firmware corruption issue on Partition 1.

Partition 1 (Standby): Non functional/corrupted. Original firmware version: v5.20 (ABUJ.0).

Partition 2 (Running/Active): Fully functional. The firewall was successfully booted from this partition via console. Firmware version: v5.30 (ABUJ.0).

My goal is to upgrade the firewall to the latest available version.

Are there intermediate versions available online to perform a step-by-step upgrade of the standby partition since?

I have already checked both the Download Library and the End-of-Life page, but I could only find versions v5.40, v5.41, and v5.42. 

Where can I locate the older firmware releases (v5.30, v.5.35, v.5.36) required to safely upgrade my USG FLEX 500? Could you please provide me with those versions?

All Replies

  • Zyxel_Judy
    Zyxel_Judy Posts: 2,626 image  Zyxel Employee
    Zyxel Certified Network Engineer Level 2 - Nebula Zyxel Certified Network Engineer Level 2 - Switch Zyxel Certified Network Engineer Level 2 - Security Zyxel Certified Network Engineer Level 1 - Nebula
    edited July 30
    Options

    Hi @CscCsc ,

    Older firmware releases are archived and not publicly listed on our standard Download Library to ensure users always install the most secure, up-to-date versions.

    In your case, you can upgrade the standby partition directly from 5.30P0 to 5.42P1. After rebooting, the firmware status will look like this: the standby partition is 5.30P0, and the running partition is 5.42P1.

    image.png

    Zyxel_Judy

  • CscCsc
    CscCsc Posts: 3 image  Freshman Member
    First Comment
    Options

    Hi Judy, thank you for your help.

    I managed to solve the issue and would like to share the procedure for anyone experiencing the same problem.

    The direct GUI/Cloud upgrade always returned “Firmware not compatible!”. I connected through the serial console (115200, 8N1), entered Debug Mode and kept Partition 2 with V5.30 as the working fallback.

    I selected the standby Partition 1 with atcd 1, configured recovery with atkz -f -l 192.168.1.1, and started it with atgof. I then connected a PC to port 2 and uploaded the firmware through anonymous FTP in binary mode.

    Using this method, I first restored the corrupted partition to V5.30 and then installed the official V5.36P2 (536ABUJ2C0.bin) on it. After successfully booting V5.36P2, the Cloud upgrade to V5.42P1 worked correctly, and I was then able to update both partitions to V5.42P1.

Categories

Security Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）