unpack / repack a firmware

[avkiev]

I am using the script that recreates md5sum for all files, before packing, found it on forum

Please, share this script

[Schenk2302]

I am using the script that recreates md5sum for all files, before packing, found it on forum

Please, share this script

I think he means the one from Tjay in the third post

[avkiev]

I think he means the one from Tjay in the third post

Thanks, it works.
But my question is:
There are >8000 files in fw. In b-rad's fw just 270 entries in file md5sum.txt.
Why ? Which files we have to hash ? What is criteria ?

Empty md5sum.txt - is solution. Is it good solution ?

[b-rad.cc]

Empty md5sum.txt - is solution. Is it good solution ?

it depends, do you care about things like a bad flash or parts on the nand randomly going bad?

[avkiev]

Ok, understand. To be on safe side we have to hash some files.
But why not all of them ? Why only 270 ? What is criteria ?

[zmiki]

if I checked correctly in original md5 text file there are no files from osd. So if you are replacing just osd
you can keep old md5 text file
right???

[avkiev]

Imho,
- hash all files - not good idea
- no hashing (empty file md5sum.txt) - not good idea.

So, my solution is: just rehash files, which already hashed (contents of md5sum.txt).
Script:
cut -d" " -f3 md5sum.txt | xargs md5sum > md5sum.new
mv -v md5sum.new md5sum.txt

[bovirus]

I tried to use

cut -d" " -f3 md5sum.txt | xargs md5sum > md5sum.new

on Ununtu 10.04 but the command answer that "" are not in pair and " has a special menaing for xtag except using -0 option.

What's the matter?

[jamesr219]

When using Ty's tool to pack/unpack (thanks BTW!) an release firmware should I expect the filesize of the re-pack to be the same? For me it is growing a bit, but I can't figure out why. I am not touching any files in the unpacked directory.

I'm using the following commands:

Code: Select all

user@ubuntu:~/wdltv$ ./wdtvfw_tool unpack rootfs 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin
stripping firmware ...
unpack cramfs image ...
unpacked to rootfs
user@ubuntu:~/wdltv$ ./wdtvfw_tool pack rootfs 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin.new
create md5sum.txt ...
create cramfs image ...
warning: gids truncated to 8 bits (this may be a security concern)
sign image ...
1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin.new created
user@ubuntu:~/wdltv$ ls -lad 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin*
-rw-r--r-- 1 user user 93159472 2010-10-12 00:05 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin
-rw-r--r-- 1 user user 93372464 2010-11-29 07:51 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin.new


Is it ok for there to be this difference? Will this create a bootable firmware?

thanks,

-jr

[jamesr219]

When using Ty's tool to pack/unpack (thanks BTW!) an release firmware should I expect the filesize of the re-pack to be the same? For me it is growing a bit, but I can't figure out why. I am not touching any files in the unpacked directory.

I'm using the following commands:

Code: Select all

user@ubuntu:~/wdltv$ ./wdtvfw_tool unpack rootfs 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin
stripping firmware ...
unpack cramfs image ...
unpacked to rootfs
user@ubuntu:~/wdltv$ ./wdtvfw_tool pack rootfs 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin.new
create md5sum.txt ...
create cramfs image ...
warning: gids truncated to 8 bits (this may be a security concern)
sign image ...
1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin.new created
user@ubuntu:~/wdltv$ ls -lad 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin*
-rw-r--r-- 1 user user 93159472 2010-10-12 00:05 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin
-rw-r--r-- 1 user user 93372464 2010-11-29 07:51 1.03.39_B_WDLXTV.COM_WDLXTV_PLUS-0.4.3.1/wdtvlive2.bin.new


Is it ok for there to be this difference? Will this create a bootable firmware?

thanks,

-jr

Anyone comment on this? I don't want to brick my unit, but need to reconfigure some things for a custom application I am working on with the WDLive devices?

thanks!