Boot Loop & Firmware Download

GetLoDo

Hello,

I factory reset a 100h and now it's stuck in a boot loop. Where can I download the firmware so I can load it on a USB? Are there particular instructions for the Flex 100h to boot from USB?

Zyxel_Melen

Hi @GetLoDo,

USG FLEX H doesn't support USB bootup.

Could you help to connect the console and record the booting log so we can help to check what happens and provide you the next step?

GetLoDo

Hello,

Here is the SSH terminal information:

Starting binary extension
mv_ddr: Marvell-10.3.7.0-1 (release) (Nov 06 2023 - 01:18:57)
using ddr topology of ZYXEL_BOARD_USGFLEX100H
mv_ddr: completed successfully
Booting Trusted Firmware
BL1: Booting BL2
BL1: Booting BL31

U-Boot 2018.03-7.1.0 (Nov 06 2023 - 01:18:30 +0000)

BootModule Version: V1.1.3 Nov 06 2023 01:18:30
DRAM: Size = 4096 Mbytes

Press any key to enter debug mode within 3 seconds.
.............................................................
RAM test ........ done !

Loading kernel from FIT Image at 20000000 ...

Using 'conf@1' configuration
Verifying Hash Integrity ... sha1,rsa2048:dev+ OK
Trying 'kernel@0' kernel subimage
Description: Linux Kernel
Created: 2025-01-09 4:35:14 UTC
Type: Kernel Image
Compression: uncompressed
Data Start: 0x200000d8
Data Size: 24445440 Bytes = 23.3 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x08080000
Entry Point: 0x08080000
Hash algo: sha1
Hash value: 448020f0583c5d578d2f805402cc889172a28ea2
Verifying Hash Integrity ... sha1+ OK

Loading fdt from FIT Image at 20000000 ...

Using 'conf@1' configuration
Trying 'fdt@0' fdt subimage
Description: Flattened Device Tree blob
Created: 2025-01-09 4:35:14 UTC
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x217503d0
Data Size: 29126 Bytes = 28.4 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: b09363b438e145cf092cad80bd0c6050fb3088f4
Verifying Hash Integrity ... sha1+ OK
Loading Kernel Image ... OK
Start to check file system...
/dev/mmcblk0p6: 12/65536 files (8.3% non-contiguous), 20237/262144 blocks
/dev/mmcblk0p7: 708/118080 files (0.4% non-contiguous), 27051/472064 blocks
Done
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

mount: mount point /etc/zyxel/ftp/wtp_image does not exist
Error: We can't mount /share/AP-image/FW1/wtp_image to /etc/zyxel/ftp/wtp_image partition
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000

CPU: 1 PID: 1 Comm: init Tainted: P O 4.14.207-10.3.7.0-2 #5
Hardware name: Marvell Armada 7040 USG40V3 - USG4060V3_version (DT)
Call trace:
dump_backtrace+0x0/0x130
show_stack+0x14/0x20
dump_stack+0x9c/0xd8
panic+0x118/0x290
do_exit+0x700/0x990
do_group_exit+0x38/0xa0
__wake_up_parent+0x0/0x30
__sys_trace_return+0x0/0x4
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x8,01002000
Memory Limit: none
Unable to handle kernel paging request at virtual address ffff0000096d4400
Mem abort info:
Exception class = DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
Data abort info:
ISV = 0, ISS = 0x00000007
CM = 0, WnR = 0
swapper pgtable: 4k pages, 48-bit VAs, pgd = ffff000009832000
[ffff0000096d4400] *pgd=000000013fffe003, *pud=000000013fffd003, *pmd=000000013f ff8003, *pte=0000000000000000
Internal error: Oops: 96000007 [#1] PREEMPT SMP
Modules linked in: zyxel_disklog(O) watchdog_touch(O) xt_zld_ctstatus_confirmed( PO) xt_zyusergroup(O) xt_traffic_flow(O) zyxel_route_multipath(PO) libiface_modu le(O) zld_conntrack_data(O) lm96000(O) zld_mrd(PO) mv88e6191x(O) zyklog(PO) swit chdev_netlink(O) switchdev_char(O) switchdev(PO) platform_support(O)
Process init (pid: 1, stack limit = 0xffff80013b254000)
CPU: 1 PID: 1 Comm: init Tainted: P O 4.14.207-10.3.7.0-2 #5
Hardware name: Marvell Armada 7040 USG40V3 - USG4060V3_version (DT)
task: ffff80013b258000 task.stack: ffff80013b254000
pc : _raw_spin_lock+0x14/0x50
lr : mod_timer+0xf0/0x2f0
sp : ffff80013b257920 pstate : a00001c5
x29: ffff80013b257920 x28: 0000000000000022
x27: ffff80013a5a0000 x26: 0000000000000000
x25: 0000000000000000 x24: 00000000ffffffff
x23: 0000000000000000 x22: 00000000fffef798
x21: ffff0000096d4400 x20: ffff0000096d4400
x19: ffff80013ac9f988 x18: 00000000fffffff0
x17: 0000000000000000 x16: ffff80013b258000
x15: ffff000009714530 x14: 74612065646f6e20
x13: 6120676e696b6146 x12: 203a414d554e0a64
x11: 6e756f66206e6f69 x10: 746172756769666e
x9 : ffff80013b257c10 x8 : ffff80013b257ab0
x7 : ffff80013b257c00 x6 : 0000000000000001
x5 : 0000000000000001 x4 : 0000000000000040
x3 : 0000000000000040 x2 : ffff80013b258000
x1 : 0000000000000003 x0 : ffff0000096d4400
Call trace:
_raw_spin_lock+0x14/0x50
sdhci_send_command+0x11c/0xa30
zymmc_simple_transfer+0x168/0x1c0 [zyxel_disklog]
zymmc_basic_run+0xfc/0x120 [zyxel_disklog]
diskWriteSectorUnstable.part.0+0x4c/0x60 [zyxel_disklog]
writeLogToDisk+0x118/0x1b0 [zyxel_disklog]
do_dump+0x64/0x80 [zyxel_disklog]
kmsg_dump+0xc0/0x100
panic+0x150/0x290
do_exit+0x700/0x990
do_group_exit+0x38/0xa0
__wake_up_parent+0x0/0x30
__sys_trace_return+0x0/0x4
Code: b9401041 11000421 b9001041 f9800011 (885ffc01)
---[ end trace c6f5e1b6f550e10a ]---

PeterUK

If you press any key to enter debug mode you should be able to boot the other firmware slot?

GetLoDo

I'm getting ERROR with any command I try.

Press any key to enter debug mode within 3 seconds.
.................
Enter Debug Mode

USG FLEX 100H> atcb 2

ERROR

USG FLEX 100H>

PeterUK

try

cmd firmware boot-number 2

GetLoDo

No dice.

USG FLEX 100H> cmd firmware boot-number 2

ERROR

USG FLEX 100H>

PeterUK

You my have to wait to be given the firmware file to do this.

How do I perform firmware recovery on USG Flex H series models? — Zyxel Community

edit

try

atcd 1

atgo

GetLoDo

Thanks for your help, it might be an RMA situtation.

@Zyxel_Melen, do you know when we can download the firmware for a Flex 100h or can you provide it to me?

Zyxel_Melen

Hi @GetLoDo,

I will send you the link and guide in the private message. Please check my message.

Zyxel_Melen

Hi @GetLoDo,

I have sent you the firmware file in the private message. Please help to follow the steps to recovery the firmware. If you can't process firmware recovery, this could be an hardware issue, also because you tried change boot image but failed. Please submit a RMA request via the link I provided in the private message.