SamyGO

Hi.
I am the preparing SamyGO Firmware Patcher.
I changed exeDSP file as it required and implement VideoARFix v1 in place. But there is some problem with CHL5DEUC structure. It uses squashfs.
So, I have root image but don't know how to prepare new squashFS image. Because there is options like endianess.
I will diggin problem. Will ready soon.
Might be you wanted to test it first

uadre wrote:Hi,

You are right. This is the information that I get from exe.img file before using unsquashfs command in the original file

Code: Select all

.\unsquashfs -ll -s exe.img
Found a valid little endian SQUASHFS 3:0 superblock on exe.img.
Creation or last append time Thu Jan  1 01:00:00 1970
Filesystem is not exportable via NFS
Inodes are compressed
Data is compressed
Fragments are compressed
Check data is not present in the filesystem
Fragments are present in the filesystem
Always_use_fragments option is not specified
Duplicates are removed
Filesystem size 13144.50 Kbytes (12.84 Mbytes)
Block size 65536
Number of fragments 3
Number of inodes 22
Number of uids 1
Number of gids 0

Dani

Hi!
I am searching for this infos
Thanks.

@cryoz
Yes I know that packaging problem. Difference is huge. Even If we can find a way to pack again in exact order of original file, there is again too much difference because of compression. Instead of implementing diff of image, I prefer to use automated unsquasfs patch and squashfs approach. But this time we needed to solve SquashFS v3.0 problem. Might be include SquasFS tools to python file. This could be problematic too. Alternative way is using tools like xdiff like binary diff engine for that. Those algorithms has chance to detect same portion of file and implement binary diff. It's like delta rpm images on linux. Need test for that. xdiff of original exe.img binary could be included to script and created as file at patch time.