Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#484 - Image Builder generates broken image for ASUS WL500W #5583

openwrt-bot opened this issue Feb 8, 2017 · 1 comment

FS#484 - Image Builder generates broken image for ASUS WL500W #5583

openwrt-bot opened this issue Feb 8, 2017 · 1 comment


Copy link

@openwrt-bot openwrt-bot commented Feb 8, 2017


====Software Revision====
LEDE 17.01.0-rc2


====Issue description====
An image generated with the Image Builder can be booted only once after flashing it. On the second and further boot attempts, the device stays in the bootloader.

The OpenWrt 15.05.1 Image Builder is not affected. The official 17.01.0-rc2 image also works fine.

I wonder if the following Image Builder message hints at the problem:

WARNING: maxlen exceeds default maximum! Beware of overwriting nvram!

The Image Builder result is actually smaller than the official image, 3608576 vs. 4001792 bytes.

====Steps to reproduce====

  • Use Debian Jessie amd64 or another suitable host system
  • Unpack lede-imagebuilder-17.01.0-rc2-brcm47xx-legacy.Linux-x86_64.tar.xz
  • Within the Image Builder directory: make image PROFILE=asus-wl-500w
  • Copy this resulting image to the device: bin/targets/brcm47xx/legacy/lede-17.01.0-rc2-r3131-42f3c1f-brcm47xx-legacy-asus-wl-500w-squashfs.trx
  • sysupgrade -n -v *.trx
  • Wait for automatic reboot, wait another 3 minutes
  • ssh root@
  • Check dmesg for "jffs2 [...] complete" message, or wait until it appears
  • reboot

The device is now stuck in the bootloader, power-cycling does not help.

I can do further tests if necessary.


Copy link

@openwrt-bot openwrt-bot commented Feb 26, 2017


The mtd fixtrx subcommand was previously missing in this package:
which is used by the Image Builder.

However, the mtd binary built into the official firmware image was working OK, which explains the difference in behaviour.

Apparently the broken mtd package has now been replaced with a fixed version,
and this bug report can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant