![]() |
0xFFFF - Open Free Fiasco Firmware Flasher, version 0.8
EDIT 2018-07-08: Version 0.8 was released
EDIT 2016-12-25: Version 0.7 was released EDIT 2014-11-18: Security update 0.6.1 was released EDIT 2014-05-12: Final 0.6 was released I'm releasing 0xFFFF flasher. It is open source alternative to Nokia proprietary flasher-3.5. 0xFFFF supports: * generating and unpacking FIASCO images * flash any image via NOLO protocol * load+boot kernel & initfs without flashing * read device and version information from NOLO * dumping images to directory (or one fiasco image) on device (need deb package mtd-utils) Missing features: * flash mmc image image Mk II protocol * flashing on device ... Note that this is new rewritten beta version of 0xFFFF for Nokia N900. Flashing can damage or brick your device! You have been warned. Only for developers & testers! Download: Binary armel DEB package: http://repository.maemo.org/extras-d....8-1_armel.deb (also available in Application Manager with Extras-Devel or Extras-Testing enabled) Source code tarball: https://github.com/pali/0xFFFF/relea...FFF-0.8.tar.gz Source code git repository: https://github.com/pali/0xFFFF Examples: Via USB: Load kernel & initfs and boot it: $ 0xFFFF -m initfs -m kernel -l -b Flash kernel: $ 0xFFFF -m kernel -f Flash FIASCO image: $ 0xFFFF -M image.fiasco -f Flash only kernel from FIASCO image: $ 0xFFFF -M image.fiasco -t kernel -f Reboot: $ 0xFFFF -r Identify device: $ 0xFFFF -I On device (need nanddump from mtd-utils): Dump all images to current directory: $ 0xFFFF -e Dump all images to one fiasco file: $ 0xFFFF -E dump.fiasco FIASCO packaging: Show FIASCO archive: $ 0xFFFF -M image.fiasco -i Unpack fiasco image to current directory: $ 0xFFFF -M image.fiasco -u Generate new fiasco image from files xloader.bin, nolo.bin, zImage, rootfs and append device&version information (xloader for RX-51 hw revision: 2101 and 2102, version 1.0) $ 0xFFFF -m RX-51:2101,2102:1.0:xloader:xloader.bin -m RX-51:2101,2102:1.0:secondary:nolo.bin -m 2.6.28:kernel:zImage -m rootfs -g image.fiasco For all options see help: $ 0xFFFF -h 0xFFFF can detect more image types from file header. If autodetection not working, see syntax of param -m ([[[dev:[hw:]]ver:]type:]file[%lay]) |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Superb app
been waiting for it thanks |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Thanks :)
12345 |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
No big deal of course, I can compile it myself... Edit: Sorry, I missed them, they are in the src directory. |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Can support N9 or just N900?
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
There are static linked binaries: $ file 0xFFFF/src/0xFFFF-* 0xFFFF/src/0xFFFF-arm: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, for GNU/Linux 2.6.8, stripped 0xFFFF/src/0xFFFF-i386: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.6.24, BuildID[sha1]=0x95b814970da75646fcc042771ae0af158d6322ef, stripped 0xFFFF/src/0xFFFF-x86_64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for GNU/Linux 2.6.24, BuildID[sha1]=0x88be01a22db723230ade45f6811bf055644372ac, stripped |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Great thanks! As is currently stands is this capable of being a drop in replacement to flasher for most things? (eg http://wiki.maemo.org/Updating_the_f...MC_in_the_N900).
Also is there a source repository hosted anywhere currently? Thanks for this! :) |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Flashing eMMC is done via Mk II protocol which is not implemented yet. But some info about Mk II protocol is in "doc/mkii" file.
And for source code git repository: In will be in future... |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Is the flashing procedure very different between N900 and N9(50) devices?
As is well known the Harmattan flasher 3.12.1 cannot be used to flash an older PR release on a device that is flashed with a newer PR. Is that limitation built into the flasher executable or is it enforced in the NOLO part of the system on the device somehow? What about the bytestream transfer between the PC and the device when flashing, is that encrypted and authenticated? I guess it would be possible to build quite secure authentication mechanisms between the flasher and NOLO but has Nokia bothered to do that? |
All times are GMT. The time now is 13:49. |
vBulletin® Version 3.8.8