I've been reading about this but I'm still a unsure what this means. I guess I need to do more reading. 
Somebody had the same issue as me here:
@richardhopton do you still remember how you solved this?
I see 2 new commits for the router: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=de1f47cd9faf210d802cb39debaab6d7821412cc and https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=058bd6c9d3a058206f1b8eb9f229d5793eea1df4. Thanks for the developers!
2 Likes
Well, as I have limited knowledge about these commits, but I am tring to understand them - can I ask if the first commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=de1f47cd9faf210d802cb39debaab6d7821412cc, allows to boot another Openwrt version from an USB stick and run it from it, or I missunderstood it?
10x
Kr
K
It's only for the delivery of the initramfs.
2 Likes
As far as i know, most of the EX5601-T0's out there have a zloader that does signature verification.
That's why I recommend to flash the bl2,fip and zloader, because i've tested them myself and i know they are working without any additional verification.
Also your boot log indicates that the partitions are not set up correctly.
[ 179.747382] mtdblock: MTD device 'BL2' is NAND, please consider using UBI block devices instead.
[ 184.531651] mtdblock: MTD device 'u-boot-env' is NAND, please consider using UBI block devices instead.
[ 186.736367] mtdblock: MTD device 'Factory' is NAND, please consider using UBI block devices instead.
[ 190.770334] mtdblock: MTD device 'FIP' is NAND, please consider using UBI block devices instead.
[ 193.295363] mtdblock: MTD device 'zloader' is NAND, please consider using UBI block devices instead.
[ 205.069796] mtdblock: MTD device 'ubi' is NAND, please consider using UBI block devices instead.
[ 362.627863] mtdblock: MTD device 'ubi2' is NAND, please consider using UBI block devices instead.
[ 496.848949] mtdblock: MTD device 'zyubi' is NAND, please consider using UBI block devices instead.
I don't know about the other partitions, but I'm pretty sure you are not supposed to get that notice for at least : ubi, ubi2 and zyubi.
Please try formatting them with ubiformat and try again.
I only get that notification for partition 'Factory'
[ 14.579410] mtdblock: MTD device 'Factory' is NAND, please consider using UBI block devices instead.
I have no way to replicate your conditions on my device to try and find where the problem is.
Also there could be a thousand different reasons why your device isn't working properly which is impossible for me to know about in this situation.
I can only confidently provide support when my instructions have been followed from my guides.
My knowledge about routers, linux and openwrt are minimal and limited to the EX5601-T0 mostly.
3 Likes
Goodmorning. I have 4 T-56 on OpenWrt 24.10.0 or OpenWrt 24.10.1. All 4 flashed according to the tutorial found on the website. All running fine for some months now.
I managed to flash 2 units to OpenWrt 24.10.2.
But the 3th i just cannot get from OpenWrt 24.10.0 to OpenWrt 24.10.2.
- Not using manual firmware update with downloaded itb file
- not through Attended upgrade in LuCi,
- not using sysupgrade on cli.
It just stays OpenWrt on 24.10.0 after a reboot.
How do i force this unit to update? Is this T-56 specific?
The 4th i just keep at OpenWrt 24.10.0 until i figure this out.
thank you
Are you running the ubootmod or stock layout?
That it resets to the previous version after a restart is probably an indication that it's not able to write the new firmware to the partitions.
I had a similar issue to this one time, in my case it was because ubi volume rootfs_data was somehow broken.
What is the output in your console after entering
ubinfo -a
cat /etc/openwrt_release
cat /etc/os-release
ubus -v call system board
Example console output
root@OpenWrt:~# ubinfo -a
UBI version: 1
Count of UBI devices: 1
UBI control device major/minor: 10:127
Present UBI devices: ubi0
ubi0
Volumes count: 5
Logical eraseblock size: 253952 bytes, 248.0 KiB
Total amount of logical eraseblocks: 256 (65011712 bytes, 62.0 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 38
Current maximum erase counter value: 20
Minimum input/output unit size: 4096 bytes
Character device major/minor: 249:0
Present volumes: 0, 1, 2, 3, 4
Volume ID: 0 (on ubi0)
Type: dynamic
Alignment: 1
Size: 17 LEBs (4317184 bytes, 4.1 MiB)
State: OK
Name: kernel
Character device major/minor: 249:1
-----------------------------------
Volume ID: 1 (on ubi0)
Type: dynamic
Alignment: 1
Size: 22 LEBs (5586944 bytes, 5.3 MiB)
State: OK
Name: root
Character device major/minor: 249:2
-----------------------------------
Volume ID: 2 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1 LEBs (253952 bytes, 248.0 KiB)
State: OK
Name: zyfwinfo
Character device major/minor: 249:3
-----------------------------------
Volume ID: 3 (on ubi0)
Type: dynamic
Alignment: 1
Size: 22 LEBs (5586944 bytes, 5.3 MiB)
State: OK
Name: rootfs
Character device major/minor: 249:4
-----------------------------------
Volume ID: 4 (on ubi0)
Type: dynamic
Alignment: 1
Size: 150 LEBs (38092800 bytes, 36.3 MiB)
State: OK
Name: rootfs_data
Character device major/minor: 249:5
root@OpenWrt:~#
root@OpenWrt:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='24.10.1'
DISTRIB_REVISION='r28597-0425664679'
DISTRIB_TARGET='mediatek/filogic'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt 24.10.1 r28597-0425664679'
DISTRIB_TAINTS=''
root@OpenWrt:~# ubus -v call system board
{
"kernel": "6.6.86",
"hostname": "OpenWrt",
"system": "ARMv8 Processor rev 4",
"model": "Zyxel EX5601-T0 (stock layout)",
"board_name": "zyxel,ex5601-t0-stock",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.1",
"revision": "r28597-0425664679",
"target": "mediatek/filogic",
"description": "OpenWrt 24.10.1 r28597-0425664679",
"builddate": "1744562312"
}
}
root@OpenWrt:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="24.10.1"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 24.10.1"
VERSION_ID="24.10.1"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r28597-0425664679"
OPENWRT_BOARD="mediatek/filogic"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 24.10.1 r28597-0425664679"
OPENWRT_BUILD_DATE="1744562312"
Thank you for looking into it. I followed this guide. https://openwrt.org/toh/zyxel/t-56
"model": "Zyxel EX5601-T0 ubootmod",
Since i got the 4th unit from .0 to .1 i figured the .1 to .2 also was gonna work and it did. So its just this one device now that didnt update.
comparing below output of a .0 and a .2 seems to be exactly the same info. every bit and byte is the same.
root@OpenWrt-accesspoint-woonkamer:~# ubinfo -a
UBI version: 1
Count of UBI devices: 1
UBI control device major/minor: 10:127
Present UBI devices: ubi0
ubi0
Volumes count: 5
Logical eraseblock size: 253952 bytes, 248.0 KiB
Total amount of logical eraseblocks: 1898 (482000896 bytes, 459.6 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 40
Current maximum erase counter value: 5
Minimum input/output unit size: 4096 bytes
Character device major/minor: 250:0
Present volumes: 0, 1, 2, 3, 4
Volume ID: 0 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1 LEBs (253952 bytes, 248.0 KiB)
State: OK
Name: ubootenv
Character device major/minor: 250:1
-----------------------------------
Volume ID: 1 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1 LEBs (253952 bytes, 248.0 KiB)
State: OK
Name: ubootenv2
Character device major/minor: 250:2
-----------------------------------
Volume ID: 2 (on ubi0)
Type: dynamic
Alignment: 1
Size: 42 LEBs (10665984 bytes, 10.1 MiB)
State: OK
Name: recovery
Character device major/minor: 250:3
-----------------------------------
Volume ID: 3 (on ubi0)
Type: dynamic
Alignment: 1
Size: 38 LEBs (9650176 bytes, 9.2 MiB)
State: OK
Name: fit
Character device major/minor: 250:4
-----------------------------------
Volume ID: 4 (on ubi0)
Type: dynamic
Alignment: 1
Size: 1770 LEBs (449495040 bytes, 428.6 MiB)
State: OK
Name: rootfs_data
Character device major/minor: 250:5
root@OpenWrt-accesspoint-woonkamer:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='24.10.0'
DISTRIB_REVISION='r28427-6df0e3d02a'
DISTRIB_TARGET='mediatek/filogic'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt 24.10.0 r28427-6df0e3d02a'
DISTRIB_TAINTS=''
root@OpenWrt-accesspoint-woonkamer:~#
root@OpenWrt-accesspoint-woonkamer:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="24.10.0"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 24.10.0"
VERSION_ID="24.10.0"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r28427-6df0e3d02a"
OPENWRT_BOARD="mediatek/filogic"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 24.10.0 r28427-6df0e3d02a"
OPENWRT_BUILD_DATE="1738624177"
```root@OpenWrt-accesspoint-woonkamer:~# ubus -v call system board
{
"kernel": "6.6.73",
"hostname": "OpenWrt-accesspoint-woonkamer",
"system": "ARMv8 Processor rev 4",
"model": "Zyxel EX5601-T0 ubootmod",
"board_name": "zyxel,ex5601-t0-ubootmod",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.0",
"revision": "r28427-6df0e3d02a",
"target": "mediatek/filogic",
"description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
"builddate": "1738624177"
}
}
Are you sure you've got enough storage left for it to be able to write the firmware?
Or perhaps you could try a factory reset if that is possible for you.
First make a backup of your configuration, then run command firstboot && reboot (you will have to press y ). This should factory reset your OpenWrt. Try flashing 24.10.2 directly after the reboot and check if it works. After that it should be possible to restore the backup.
1 Like
I did exactly that. After flashing im still at 24.10.0
Is below correct? the ubi0_4 thing?
This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
/dev/ubi0_4 is mounted as /overlay, only erasing files
root@OpenWrt-accesspoint-woonkamer:~#Honestly, It's a strange situation.
I suggest you start over using mtk_uartboot to boot the initramfs-recovery.itb and flash it like it's the 1st time, but this time with the 24.10.2 files.
When flashing 24.10.2, after entering command
ubidetach -p /dev/mtd5; ubiformat /dev/mtd5 -y; ubiattach -p /dev/mtd5
I don't see any way possible for it to come up as 24.10.0 again, since mtd5 is formatted, unless the command failed.
2 Likes
without the uarttool and just using serial cli I booted recovery from the bootmenu and ended up at a 23.05.5 prompt.
From there i proceeded the steps from the tutorial and reinstalled v23. yes 23. Because for v24 and up i had to run an apk command and the device didnt have network (too lazy to move device).
After the succesful flashing of 23 i uploaded the 24.10.2 sysupgrade and ended up with v24!
So redoing all steps worked. After restoring the backup the device is now on the latest.
Thank you for your patience and help. I hope it will nog upgrade to a coming new one and not stall again.
3 Likes
Bought two EX5601-T1's from Markplaats this week. One came with b7_1006 and the other with b10_0130. Both succesfully flashed using serial! Very happy with the outcome and the amount of information available on this topic. Was a bit scared the 130 would not work, but seems it's safe to flash!
5 Likes
Hi,
I've installed the latest 24.10.2 release (using serial and uartboot, worked flawlessly, please take the 'make sure your TFTP server is working warning seriously , mine didn't like a long directory structure as in /home/blabla/Downloads/Zyxel-Ex5601-T0/firmware etc, only managed to get it working when i used the default directory of atftpd)
I really like it so far, but i've been wondering can i flash a SNAPSHOT build with sysupgrade ?
No idea why you'd want it, but yes.
You can use owut or asu for upgrading without losing all packages.
I'm glad it all worked out for you finally.
Though 24.10.2 still uses opkg and not apk as far as i know.
2 Likes
Thank you for the reply!
I ended up using the ubootmod steps documented at the T-56 device page, which worked. I then successfully upgraded to 24.10.2 using sysupgrade. So, flashing OpenWrt ubootmod from stock EX5601-T0 running V5.70(ACDZ.4)C0 works.
I also read some more about mtd devices, NAND flash, and ubi, which was really interesting.
I also verified that the partition layout was in fact the same as seen on the T-56 device page before flashing.
If I have time, I might update the wiki with instrucitons on obtaining the root password for stock firmware, and also add a device page for the EX5601-T0. Or should it be combined with the T-56 somehow, since the info is essentially the same? There is also this EX5601 T1, which is misspelled (it shouldn't contain a space in the name). Can I just rename it (once I open a wiki account)?
1 Like
For T-56's there's already a link to a forum post, where it's described.
I think they should be kept apart, even though most of the info is the same, as you said.
Not sure it can be done without being a wiki admin.
I used a slightly different process for the EX5601-T0, since that guide didn't work. Also the the password was different than the one posted there. So I thought I'd document the process (not the password, I'm not sure it's the same for ever unit) on the EX5601-T0 specific page.
Fair
Ah, well I'll figure it out.
1 Like
Since 2.5Gbps ports are not stable on T-56 (a well known bug, as I understand it), should that info be added to https://openwrt.org/toh/zyxel/t-56
Adding to rc.local limits speed to 1Gps, but is stable:
ethtool -s eth1 advertise 0x028
ethtool -s eth1 speed 1000 duplex full autoneg on