Messages

1

Zaurus - pdaXrom / Archos

« on: October 23, 2005, 07:23:15 am »

Ultimately I would like to boot direct into pdaxrom, but first there will be a chroot method I expect.

To mount the cramfs on pc I did:
Search in aimage.img for bytes 45 3d cd 28 (this is the cramfs header start)
Then extract all  from that offset onwards to create a  cramfs.img (using dd)
I mounted it with:

mkdir /PMA400/rom
mount -o loop -t cramfs cramfs.img /PMA400/rom

The problem is in modfying the cramfs or the precceding data (kernel) and building a new aimage.img, because there are two meaty signatures at the start of aimage.img that are checked at boot time.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=100608\"][{POST_SNAPBACK}][/a][/div]

Yes, I tried that but my pc hangs when reading the files in the image, because I can't seem to get my kernel patched properly for the cramfs features that are used, esp. the xip stuff. Oh well, it's not going to be of much help untill that signature checking gets reverse-engineered  

Would love to help but wouldn't know where to start.... I have got some different
firmware releases (1.12, 1.13-2, 1.14-1 and 1.14-2) if anyone is interested for analysis of how the sig is created...

2

Zaurus - pdaXrom / Archos

« on: October 23, 2005, 03:32:25 am »

This is interesting stuff !
I have tried to dissasemble the firmware but never succeeded in mounting the resulting cramfs. Never figured out if the problem was related to xip-linear
patches I needed, or the image being bad.  

What did you do to mount the cramfs ?

And how would the pdaxrom work ? Changeroot from qtopia, killing qpe and starting X ? Or hacking the image so qpe does not start at all ?

I'd be very interested in helping, but must say I have no experience using arm (dis)assembler or kernel coding.  
BTW, are you using the latest (1.14-2) firmware for the kernel ? Or do you use 1.13-2 which, I believe, is more stable ?