![]() |
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? |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
looking forward to N9 version
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
What about documentation, is there some comprehensive explanation about the workings of the whole flashing chain in Harmattan? What is the function of the different parts of the flashing process, for example what is the APE algorithm that is needed, for example when flashing only the kernel image? I tried googling for that but no success really? |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Here is public git repository for 0xFFFF: https://gitorious.org/0xffff/0xffff
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Final version 0.6 was released, see first post!
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
I pushed package to extras-devel & extras-testing, so limited operations can be also done on device.
http://maemo.org/packages/view/0xffff/ |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Code:
Error: Dump image via USB is not supported |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Only on device.
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Code:
0xFFFF -e /path/to -t rootfs |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
I discovered that it is easy to create rootfs backup with this tool so If anyone is interested:
First use 0xFFFF -e to dump all images. It will partially fail because of not enough memory to dump emmc but kernel and rootfs will be dumped. Then create fiasco image from dumped files: 0xFFFF -m 2.6.28:kernel:kernel-RX-51_2.6.28-20103103\+0m5 - m rootfs:rootfs-RX-51_RX-51_2009SE_21.2011.38-1_PR_MR0 -g fiasco.image. |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
I bricked my testing N900 running CSSU thumb by installing U-Boot without creating bootmenu entries. U-Boot came up fine but of course couldn't boot anything.
At that point 0xFFFF gave me that output for the device: Code:
# ./0xFFFF/src/0xFFFF-i386 -I Code:
# ./0xFFFF/src/0xFFFF-i386 -m zImage-2.6.28.10-cssu3 -f 0xFFFF now says this: Code:
# ./0xFFFF/src/0xFFFF-i386 -I Since I've never flashed an N900 before I neither have any experience with this, nor do I have any images. I obviously have 0xFFFF and I got the maemo-flasher debian package from here [2] (afaik it's the same for N810 and N900, please correct me if I'm wrong). So can someone please tell me what files I need to obtain and what to do with them (if it differs from the standard procedure)? The image links in the wiki are dead, so seem the links panjgoori put up here [3]. [1] http://maemo.merlin1991.at/cssu/comm...k/kernel-cssu/ [2] http://www.jedge.com/n810/flasher/ [3] http://talk.maemo.org/showthread.php?t=88795&page=2#13 |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
You must also copy modules from kernel-cssu-modules_2.6.28-10cssu3_armel.deb package to maemo rootfs.
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Afair u-boot had (has?) the stock kernel attached.
So you should have only selected run attached kernel!? Now you have cssu kernel and possibly no modules, as said. I would go and flash the u-boot kernel (package u-boot-flasher) if its size is around 2MB. Then you should be able to run attached kernel. Furthermore ther is u-boot console giving you the possibility to "run noloboot" which should also work. More info in u-boot thread. If all fails, just extract stock kernel and load/flash this one to device, as you have done with cssu. This should boot. |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Why no modules? He clearly stated, that he had been running CSSU thumn before flashed u-boot to kernel area.
I have no idea what is going wrong, sulu - flashing zImage, as you did (if it was the SAME kernel and version, that you used before u-boot) should be enough to boot without problems. Maybe you were running older version? /Estel // Edit Also, I don't get the thing about "cold flashing mode" from your logs. Why the hell 0xFFFF brings it up on it's own? Maybe flashing kernel's zImage went wrong, somehow? |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
Quote:
I'm not sure what exactly happened but it was either a bunch of messages saying the FS couldn't be mounted (this definitely happened when trying to boot from eMMC and µSD) or plain nothing. Quote:
Code:
# ./0xFFFF/src/0xFFFF-i386 -m u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco -f Code:
# ./0xFFFF/src/0xFFFF-i386 -I Quote:
Quote:
[1] http://repository.maemo.org/extras-t...free/u/u-boot/ |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
fiasco image is just archive (with attributes) which can contains more raw images. |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
You can use rescueos to copy modules or first try to flash kernel-power image.
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Flashing u-boot was successful - sort of:
Code:
# ./0xFFFF/src/0xFFFF-i386 -M u-boot-2013.04-1+zImage-2.6.28-omap1.fiasco -f Code:
# ./0xFFFF/src/0xFFFF-i386 -I U-boot now comes up fine but when trying to boot the attached kernel I get these messages (transcribed from a photo): Code:
mmc1(part 0) Is current device @elros34: I'd prefer to have u-boot on this device so I'd like to follow this path first. |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
Debian has 0xFFFF in sid: https://packages.debian.org/sid/0xffff |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
I rebuilt the 0xFFFF Jessie/amd64 package but the result was the same. Flashing went fine but the same memory corruption occured afterwards.
I then flashed the combined image I found here [1] and the device came up fine. Reinstalled CSSU thumb, u-boot and bootimg packages and everything is ok. I think my initial fault was that I only installed u-boot but not the bootimg package. [1] http://gsmphonetricks.blogspot.de/20...212011381.html edit: After successfully flashing the combined image 0xFFFF repeated this in an infinite loop (had to kill it via ctrl+c): Code:
Waiting for USB device... |
The Greatest Flasher :D
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
But I haven't flashed in ages, so forgive, if I messed something. Also, it's of no importance, as you have already reflashed, right? |
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
Quote:
|
Re: 0xFFFF - Open Free Fiasco Firmware Flasher
But it should have! :confused:
So apparently something else has been messed up. |
[ASK]
I got trouble with My Other N9 On Ubiboot MODE :( Its totally dead. I try to re-Flash. But My PC won't detect my N9 :( I try flasher -i and (PC Wont dettect but LED still Breathing) :( And i try Phoenix too, its not detect :( So!? Can I fix it using this Flasher!? And HOW to do it!? Please HELP n Advice :( |
All times are GMT. The time now is 21:17. |
vBulletin® Version 3.8.8