OpenWrt build for ZBT z8102ax - M2-a -t (v2)

For Developers
41

Please test https://releases.openmptcprouter.com/v0.62-6.6/z8102ax_128m/targets/mediatek/filogic/openmptcprouter-v0.62-6.6-r0+28431-92e020b50f-mediatek-filogic-z8102ax-128m-squashfs-sysupgrade.bin and/or v2 from http://aturnofthenut.com/autobuilds/ZBT-Z8102AX-GO2025-05-01-ABSmn.zip

Done, but with similar results:

Note:
I messed up before this, so the original UBI partition was modified (well the original firmware was crap anyway :slight_smile: ) I do not have the original fw on the ubi mtd partition..

So my upgrade procedure is:

  1. Boot via serial console using the openwrt-24.10.1-mediatek-filogic-zbtlink_zbt-z8102ax-initramfs-kernel.bin image via tftp
  2. Copy the openmptcprouter-v0.62-6.6-r0+28431-92e020b50f-mediatek-filogic-z8102ax-128m-squashfs-sysupgrade.bin to the /tmp folder
  3. Perform sysupgrade -F openmptcprouter-v0.62-6.6-r0+28431-92e020b50f-mediatek-filogic-z8102ax-128m-squashfs-sysupgrade.bin

Trying the above file:

root@OpenWrt:/tmp# sysupgrade -F openmptcprouter-v0.62-6.6-r0+28431-92e020b50f-mediatek-filogic-z8102ax-128m-squashfs-sysupgrade.bin
Thu Jan  1 00:05:20 UTC 1970 upgrade: Device zbtlink,zbt-z8102ax not supported by this image
Thu Jan  1 00:05:20 UTC 1970 upgrade: Supported devices: z8102ax-128m
invalid sysupgrade file
Image check failed.
Thu Jan  1 00:05:29 UTC 1970 upgrade: Device zbtlink,zbt-z8102ax not supported by this image
Thu Jan  1 00:05:29 UTC 1970 upgrade: Supported devices: z8102ax-128m
invalid sysupgrade file
Image check failed but --force given - will update anyway!
Cannot save config while running from ramdisk.
Thu Jan  1 00:05:30 UTC 1970 upgrade: Commencing upgrade. Closing all shell sessions.
Watchdog handover: fd=3
- watchdog -
Watchdog does not have CARDRESET support
Thu Jan  1 00:05:31 UTC 1970 upgrade: Sending TERM to remaining processes ...
Thu Jan  1 00:05:31 UTC 1970 upgrade: Sending signal TERM to netifd (1969)
Thu Jan  1 00:05:35 UTC 1970 upgrade: Sending KILL to remaining processes ...
Thu Jan  1 00:05:35 UTC 1970 upgrade: Sending signal KILL to netifd (1969)
[  343.454663] stage2 (3472): drop_caches: 3
Thu Jan  1 00:05:43 UTC 1970 upgrade: Switching to ramdisk...
Thu Jan  1 00:05:44 UTC 1970 upgrade: Performing system upgrade...
verifying sysupgrade tar file integrity
[  346.850666] block ubiblock0_1: released
Volume ID 0, size 45 LEBs (5713920 bytes, 5.4 Mi[  347.017053] ubi0 error: 0xffffffc0805cdcbc: not enough PEBs, only 442 available B), LEB size 126
[  347.025481] ubi0 error: 0xffffffc0805cdc18: cannot create volume 1, error -28
976 bytes (124.0 KiB), dynamic, name "kernel", alignment 1
ubimkvol: error!: cannot UBI create [  347.042009] reboot: Restarting system

...
ubi0 error: scan_peb: bad image sequence number 1744562312 in PEB 512, expected 418050938
Erase counter header dump:
        magic          0x55424923
        version        1
        ec             1
        vid_hdr_offset 2048
        data_offset    4096
        image_seq      1744562312
        hdr_crc        0xaea3c922
erase counter header hexdump:
00000000: 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 01 00 00 08 00 00 00 10 00 67 fb e8 88 00 00 00 00  UBI#....................g.......
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ae a3 c9 22  ..............................."
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd6, error -22
UBI error: cannot attach mtd6
UBI error: cannot initialize UBI, error -22
UBI init error 22
Please check, if the correct MTD partition is used (size big enough?)

So I did some additional digging into the UBI partition

ubinfo /dev/ubi0 -a gives:

ubi0
Volumes count:                           1
Logical eraseblock size:                 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks:     512 (65011712 bytes, 62.0 MiB)
Amount of available logical eraseblocks: 442 (56123392 bytes, 53.5 MiB)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  19
Current maximum erase counter value:     3
Minimum input/output unit size:          2048 bytes
Character device major/minor:            249:0
Present volumes:                         0

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        45 LEBs (5713920 bytes, 5.4 MiB)
State:       OK
Name:        kernel
Character device major/minor: 249:1

And mounting it gives a empty partition of 4 MB size:

root@OpenWrt:/tmp# mount -t ubifs ubi0 /mnt
[ 1681.013022] UBIFS (ubi0:0): default file-system created
[ 1681.018611] UBIFS (ubi0:0): Mounting in unauthenticated mode
[ 1681.024403] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 3475
[ 1681.059300] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "kernel"
[ 1681.066733] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 1681.076648] UBIFS (ubi0:0): FS size: 4444160 bytes (4 MiB, 35 LEBs), max 45 LEBs, journal size 1015809 bytes (0 MiB, 6 LEBs)
[ 1681.087859] UBIFS (ubi0:0): reserved for root: 209908 bytes (204 KiB)
[ 1681.094295] UBIFS (ubi0:0): media format: w5/r0 (latest is w5/r0), UUID 0D9895F4-B42B-4CA2-AE02-1C6E62147009, small LPT model

root@OpenWrt:/tmp# df -h
Filesystem                Size      Used Available Use% Mounted on
tmpfs                   493.8M     25.6M    468.2M   5% /
tmpfs                   493.8M     17.3M    476.4M   4% /tmp
tmpfs                   512.0K         0    512.0K   0% /dev
ubi0                      3.1M     24.0K      2.9M   1% /mnt

Probably have to recreate the whole thing by hand...
any tips much appreciated..

42

Please open a new thread for more visibility

43

Thanks switched to here

1 Like