Most TP-Link squashfs images are created using mktplinkfw -a 0x4 The "Rootfs data offset" in the header of those images is 0x00100000. But the rootfs actually starts at "Kernel data offset" + "Kernel data length". As a result when extracting the rootfs with "mktplinkfw -x -i" the result is broken.
Bug or feature? Maybe the firmware header is checked by something that expects the "Rootfs data offset" value to be wrong? If so, could the real offset be stored somewhere else so "mktplinkfw -x -i" can do its work?
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
