Yey, after some while I have written the support for unpacking fiasco
firmwares. The current work in pvc is quite initial, so it does not
yet supports the creation of fiasco firmwares (will be soon done), and
it is not yet possible to flash a device using a fiasco image.

It has been tested against the first old fashion firmwares of the times
of flasher-1.0 until the latest ones for n800. I'm planning to mix some
code from the mtd side to be able to create on the fly backups of
the device generating a single file containing all the firmware pieces.

It does not yet supports model-specific information for retrieving
certain pieces for the bootloader and so, but work will say.

Here's how it works:

$ mkdir RX-34-2007-3
$ cd RX-34-2007-3
$ 0xFFFF -u ../RX-34_2007SE_3.2007.10-7_PR_COMBINED_MR0_ARM.bin 
Dumping firmware pieces to disk.
Fiasco version:  2
Name: OSSO UART+USB
Name: 1 RX-34_2007SE_3.2007.10-7_PR_MR0
 kernel
   size:    1311104 bytes
   hash:    92b3
   version: 2.6.18-200710osso2
 initfs
   size:    1689216 bytes
   hash:    e6cf
   version: 0.93-40
 rootfs
   size:    83886080 bytes
   hash:    2462
   version: RX-34_2007SE_3.2007.10-7_PR_MR0
 2nd
   size:    8064 bytes
   hash:    dae4
   version: RX-34
   version: 1.1.5-3
 xloader
   size:    9088 bytes
   hash:    9df2
   version: RX-34
   version: 1.1.5-3
 secondary
   size:    95872 bytes
   hash:    d56d
   version: RX-34
   version: 1.1.5-3


  --pancake
_______________________________________________
0xffff mailing list
0xffff@lists.nopcode.org
https://lists.nopcode.org/mailman/listinfo/0xffff

Reply via email to