You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically minifs consists of a header with a few fields (including the number of files in the image), followed by a lookup table for the directory names and file names, meta information for each file (including relative offsets into the name table for both the directory name and file name), the number of the LZMA blob in which the file can be found, and offsets and size of each file in the uncompressed data. This is then followed by some metadata for each LZMA blob (size, relative offset in the data region of minifs) and then the data region with all of the LZMA blobs.
In the example you listed there are actually 0x16a (= 362) files. If files have the same name (but a different directory), then they will use the same offset for the file name but a different one for the directory name.
The operating system of this device is as far as I can tell TP-Link's own RTOS called "TPOS", but I cannot find any relevant information about it.
Hope this helps.
The text was updated successfully, but these errors were encountered:
Wow! Such a great contribution, thanks!
I have this project on pause, but I will totally investigate this further and extract the files when I get back to it!
thank you @hacefresko for sharing your progress , i have been working on the same router but different model (C24) your work helped me figuring out many points there is some diff but most of things are similar ( private key is the same :X ) including the minifs @armijnhemel thanks for mentioning your contribution .
You might be interested in this Kaitai Struct specification for minifs that I made:
kaitai-io/kaitai_struct_formats#682
Basically minifs consists of a header with a few fields (including the number of files in the image), followed by a lookup table for the directory names and file names, meta information for each file (including relative offsets into the name table for both the directory name and file name), the number of the LZMA blob in which the file can be found, and offsets and size of each file in the uncompressed data. This is then followed by some metadata for each LZMA blob (size, relative offset in the data region of minifs) and then the data region with all of the LZMA blobs.
In the example you listed there are actually
0x16a
(=362
) files. If files have the same name (but a different directory), then they will use the same offset for the file name but a different one for the directory name.The operating system of this device is as far as I can tell TP-Link's own RTOS called "TPOS", but I cannot find any relevant information about it.
Hope this helps.
The text was updated successfully, but these errors were encountered: