root@debian:~# mount -t cramfs -o loop ./cramfs.bin /mnt/tmp
root@debian:~# ls /mnt/tmp
???? ? ????l?????Z?libencoder.so
root@debian:~# cramfs-1.1-16k/cramfsck-16k -x ./dump/ ./cramfs.bin
cramfs-1.1-16k/cramfsck-16k: file length too short
recliq wrote:Maybe there is a checksum or hash in front of the actual filesystem (like in the WD firmware files, read first post).
A nice tool which will help you find out if so and which offset to use to get the actual filesystem is binwalk - maybe that helps
mad_ady wrote:cramfsck that comes with ubuntu doesn't support 16k blocksizes, so it will segfault (most likely it needs a patch or something - you'd need to file a bug report on leafpad). I haven't tried to run the older version, so there might be dependency issues.
The easiest way to unpack the firmware is to do it on the wdtv, via telnet/ssh - that cramfsck supports 16k blocks.
Or, here is an alternative without cramfsck: http://wiki.wdlxtv.com/Booting_Original_FW
Users browsing this forum: No registered users and 0 guests