View Single Post
Old 12-19-2009, 02:13 AM   #32
jusmee
Wizard
jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.
 
Posts: 1,047
Karma: 203682
Join Date: Oct 2009
Device: Libre 2
Quote:
Originally Posted by jusmee View Post
Yes, this is what I found also. At least, when at looked at the header, size seemed to be x7E (126) blocks instead of x36 (44). Extracting that size however does not yield a mountable root.fs filesystem. I suspect ro.fs is a different size too, and that's throwing out all the rest after it.
In fact, the kernel image is twice the size by the looks of it

block 0 - header
block 1-2 - kernel
blocks 3-8 - ro.fs
blocks 10-135 - root.fs

that'll be something like

dd if=$file of=$out_dir/zImage bs=1M count=2 skip=1
dd if=$file of=$out_dir/ro.fs bs=1M count=6 skip=3
dd if=$file of=$out_dir/root.fs bs=1M count=126 skip=9
dd if=$file of=$out_dir/logo bs=1 count=240000 skip=$[1024*1024*135]
dd if=$file of=$out_dir/jffs2.fs bs=1M count=2 skip=136

If I have it right.

The resulting ro.fs and root.fs mount successfully but appear to contain nothing - so something is still amiss.
jusmee is offline   Reply With Quote