HELP: ZBT-Z8103AX Won't Boot After Sysupgrade - Recovery Needed
-
Device: ZBT-Z8103AX (MT7981)
-
Issue: Sysupgrade between custom OpenWrt 24.10.2 builds → won't boot
-
Status: NOT bricked (U-Boot works, InitRAMFS boots fine)
-
Need: How to recover persistent boot capability
What's Happening
ubi0 error: vtbl_check: too large reserved_pebs 751, good PEBs 512
UBI error: cannot attach mtd4
Kernel panic - not syncing: VFS: Unable to mount root fs
Root cause: U-Boot creates UBI volumes expecting 916 PEBs, but Linux only sees 512 PEBs available.
What Works 
-
U-Boot console access
-
InitRAMFS boots perfectly (all hardware functional)
-
TFTP/Ymodem file transfers
-
Original device with different build works fine
What I Need 
Any working solution to get persistent firmware booting again.
Specific Questions:
-
Boot parameters: How to force Linux to see full UBI partition size?
-
UBI rebuild: Commands to recreate volumes within 512 PEB limit?
-
Compatible firmware: Anyone have working custom ZBT-Z8103AX build?
-
Recovery method: Alternative approach that bypasses this issue?
Failed Attempts 
-
Various
ubi.mtd=
boot parameters -
Complete MTD erase and recreation
-
Factory firmware → same issue
-
U-Boot environment changes
Quick Details
U-Boot partition: mtd6, 114 MiB, 916 PEBs ← Works
Linux partition: mtd4, 64 MiB, 512 PEBs ← Fails
Help Appreciated
-
ZBT-Z8103AX users: Seen this before? How did you fix it?
-
OpenWrt devs: Standard way to handle UBI volume table mismatches?
-
Anyone: Even hacky workarounds welcome!
Have serial console access and can test any suggestions. Device is recoverable - just need the right approach.
Quick responses much appreciated!