OpenWRT TRX unpacker fails to unpack when rootfs_offset is null about ofrak HOT 3 CLOSED

Thanks for reporting this and providing an example. Have you found documentation on this null-rootfs_offset behavior? It would help clarify the following questions:

1. I assume the desired behavior is that the OpenWrtTrxRootfs should be empty (or nonexistant) and the OpenWrtTrxKernel should include all the data starting from trx_kernel_offset to the end (or trx_binheader_offset if it's version 2)?
2. Is this just on Version 1, or 2, or both?

I can see where in the Packer and Unpacker this change is needed, should be simple enough once the desired behavior is clear.

from ofrak.

Unfortunately the only documentation I've come across so far is:

1. The OpenWRT header wiki page that the diagrams in the ofrak TRX unpacker appear to be from
2. trx.c from OpenWRT's firmware utils constructs TRX headers, but doesn't mention anything about the rootfs being null

Although I'm not seeing any documentation, I think your assumptions are accurate - ie. OpenWrtTrxRootfs should be empty/nonexistant and OpenWrtTrxKernel should include all data from trx_kernel_offset to the end of the file or trx_binheader_offset (if present).

It looks like all the TRX files I was able to pull from the OpenWRT website are TRX v1, so I have not yet tested this on TRX v2 firmware.

from ofrak.

#216 makes core changes to OpenWRT TRX files that should address this issue.

from ofrak.