Permalink
Browse files

Recommend pali's repo

  • Loading branch information...
1 parent 47bdc71 commit 67584f51fca3a0a0ba410f3d43659837ebd8700a @radare committed Dec 11, 2016
Showing with 8 additions and 9,153 deletions.
  1. +0 −2 AUTHORS
  2. +0 −842 COPYING
  3. +0 −26 INSTALL
  4. +0 −2 Makefile
  5. +0 −49 README
  6. +8 −0 README.md
  7. +0 −6 config.mk
  8. +0 −5 debian/changelog
  9. +0 −1 debian/compat
  10. +0 −25 debian/control
  11. +0 −29 debian/copyright
  12. +0 −2 debian/docs
  13. +0 −11 debian/rules
  14. +0 −1 debian/source/format
  15. +0 −71 doc/dumping
  16. +0 −46 doc/examples
  17. +0 −35 doc/faq
  18. +0 −80 doc/faq2
  19. +0 −57 doc/fiasco
  20. +0 −36 doc/local-flash
  21. +0 −90 doc/mkii
  22. +0 −98 doc/nokia-tips
  23. +0 −37 doc/pieces
  24. +0 −45 src/Makefile
  25. +0 −263 src/cal.c
  26. +0 −35 src/cal.h
  27. +0 −415 src/cold-flash.c
  28. +0 −35 src/cold-flash.h
  29. +0 −328 src/device.c
  30. +0 −59 src/device.h
  31. +0 −188 src/disk.c
  32. +0 −37 src/disk.h
  33. +0 −572 src/fiasco.c
  34. +0 −42 src/fiasco.h
  35. +0 −24 src/global.h
  36. +0 −611 src/image.c
  37. +0 −83 src/image.h
  38. +0 −194 src/libusb-sniff.c
  39. +0 −617 src/local.c
  40. +0 −65 src/local.h
  41. +0 −1,364 src/main.c
  42. +0 −106 src/mangen.c
  43. +0 −239 src/mkii.c
  44. +0 −64 src/mkii.h
  45. +0 −885 src/nolo.c
  46. +0 −65 src/nolo.h
  47. +0 −639 src/operations.c
  48. +0 −83 src/operations.h
  49. +0 −96 src/printf-utils.c
  50. +0 −37 src/printf-utils.h
  51. +0 −349 src/usb-device.c
  52. +0 −62 src/usb-device.h
View
@@ -1,2 +0,0 @@
-Copyright (C) 2007-2010 pancake <pancake@youterm.com>
-Copyright (C) 2011-2012 Pali Rohár <pali.rohar@gmail.com>
View
842 COPYING

Large diffs are not rendered by default.

Oops, something went wrong.
View
26 INSTALL
@@ -1,26 +0,0 @@
-Installation instructions:
-==========================
-
-To build the flasher you will need gcc, make and libusb. For crosscompiling
-to arm you can use scratchbox. But you will probably need the libusb.so of
-the scratchbox environment to the device.
-
-Just type:
-
- $ make
-
-The most interesting targets for make are:
-
- all normal build
- install installs into /usr/local by default
- uninstall remove installed files
- clean clean compilation objects and generated binaries
-
-
-The installation procedure is quite simple and you can define a new PREFIX
-manually from the command line:
-
- $ sudo make install PREFIX=/usr
-
-The default one is /usr/local (not very userfriendly but standards are
-standards :P hehe)
View
@@ -1,2 +0,0 @@
-all clean install uninstall:
- $(MAKE) -C src $@
View
49 README
@@ -1,49 +0,0 @@
-
-
- ------. ,---------.--.--.
- / | ___ | | | \\------------ -- .
- | .__ / \/ . ____/ _/ _/ The 0pen
- | / . < | | | Free Fiasco
- | '- > ^ ___| _| .' Firmware Flasher
- | | ' | - -- --- ----------------\\
- \_____/7_/\______ : I 0xFFFF
- _/ ___|_.|__|
- '`
-
-0xFFFF is Open Free Fiasco Firmware Flasher for Maemo devices. It support
-generating and unpacking FIASCO images on local computer. Useful for editing
-Maemo firmware package for future flash. It support via USB flashing any image
-type to Maemo device and also \"cold\" flashing which means flashing dead device
-with erased bootloader. There is support for booting kernel via USB without
-flashing to NAND and also changing configuration of Maemo device (enable/disable
-R&D mode, changing HW revision strings, ...).
-
-0xFFFF is alternative tool to proprietary Nokia flasher-3.5 and fiasco-gen.
-0xFFFF generate compatible FIASCO images and also accept FIASCO images generated
-by Nokia fiasco-gen.
-
-Use it with CARE. This is an experimental tool and it can brick your device.
-It's not suposed to be stable, so nokia will probably release incompatible
-bootloaders to break this tool. USE IT AT YOUR OWN RISK.
-
-PLEASE. Read carefully all the documentation inside doc/* for more information
-before building or using the flasher to avoid questions, problems or so.
-
-Feel free to join to the mailing list and visit the homepage for more info:
-
- 0xffff@lists.nopcode.org
- http://www.nopcode.org/0xFFFF
-
------------8<---------------------------------------------------------------
-
-Build:
- $ make
-
-To install: (by default is /usr/local)
- $ make install PREFIX=/usr DESTDIR=/
-
-
-
-Have phun!
- --pancake
- --Pali
View
@@ -0,0 +1,8 @@
+0xFFFF
+======
+
+This repository contains the source code of the original implementation of the flasher for the Nokia Internet Tablet devices done by pancake (see the pancake branch).
+
+You can find an updated and maintained version in Pali's repository:
+
+* [https://github.com/pali/0xFFFF](https://github.com/pali/0xFFFF)
View
@@ -1,6 +0,0 @@
-VERSION = 0.6
-PREFIX = /usr/local
-
-# NetBSD stuff
-#CPPFLAGS += -I/usr/pkg/include
-#LDFLAGS += -L/usr/pkg/lib -Wl,-R/usr/pkg/lib
View
@@ -1,5 +0,0 @@
-0xffff (0.6-1) unstable; urgency=low
-
- * This is new rewritten version of original 0xFFFF 0.5 tool
-
- -- Pali Rohár <pali.rohar@gmail.com> Sun, 07 Apr 2013 15:01:50 +0200
View
@@ -1 +0,0 @@
-7
View
@@ -1,25 +0,0 @@
-Source: 0xffff
-Section: utils
-Priority: extra
-Maintainer: Pali Rohár <pali.rohar@gmail.com>
-Build-Depends: debhelper (>= 7), libusb-dev
-Standards-Version: 3.9.3
-
-Package: 0xffff
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Open Free Fiasco Firmware Flasher
- 0xFFFF is Open Free Fiasco Firmware Flasher for Maemo devices. It support
- generating and unpacking FIASCO images on local computer. Useful for editing
- Maemo firmware package for future flash. It support via USB flashing any image
- type to Maemo device and also \"cold\" flashing which means flashing dead
- device with erased bootloader. There is support for booting kernel via USB
- without flashing to NAND and also changing configuration of Maemo device
- (enable/disable R&D mode, changing HW revision strings, ...).
- .
- 0xFFFF is alternative tool to proprietary Nokia flasher-3.5 and fiasco-gen.
- 0xFFFF generate compatible FIASCO images and also accept FIASCO images
- generated by Nokia fiasco-gen.
- .
- Supported Maemo devices:
- Nokia 770, Nokia N800, Nokia N810, Nokia N810 WiMAX, Nokia N900
View
@@ -1,29 +0,0 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-Upstream-Name: 0xffff
-
-Files: *
-Copyright: 2007-2012 pancake <pancake@youterm.com>
- 2011 Michael Buesch <mb@bu3sch.de>
- 2011-2013 Pali Rohár <pali.rohar@gmail.com>
-License: GPL-3.0+
-
-Files: debian/*
-Copyright: 2013 Pali Rohár <pali.rohar@gmail.com>
-License: GPL-3.0+
-
-License: GPL-3.0+
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
- .
- This package is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
- .
- You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>.
- .
- On Debian systems, the complete text of the GNU General
- Public License version 3 can be found in "/usr/share/common-licenses/GPL-3".
View
@@ -1,2 +0,0 @@
-README
-doc/*
View
@@ -1,11 +0,0 @@
-#!/usr/bin/make -f
-# -*- makefile -*-
-
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
-
-%:
- dh $@
-
-override_dh_auto_install:
- dh_auto_install -- PREFIX=/usr
View
@@ -1 +0,0 @@
-3.0 (quilt)
View
@@ -1,71 +0,0 @@
-Dumping the firmware:
-
-This technique consists on reconstructing a firmware image dumping
-pieces at certains offsets of the device internal memory.
-
-Technical details:
-
- * The internal flash memory is exposed to the system as MTD devices.
- * Is possible to dump the individual sections of a flashed firmware.
- *
- * READ src/local.c for detailed information.
-
- mtd0 - contains xloader and sencodary pieces of the bootloaders
- 0x00000 - xloader.bin (size is 0x03600)
- 0x04000 - secondary.bin (size is 0x15400)
- 0x1FFFF - eof
-
- mtd1 - looks like there's a pool ConF structures
-
- mtd2 - starts with NOLO img\x5c\x13 and \x00 padding
- 0x00800 - zImage
-
- > NOLO is a four byte marker, next four bytes
- > can vary since it is kernel image size
-
- mtd3 - initfs.jffs2 (2M) aka 0x200000 vs 0x3900000
-
- mtd4 - rootfs.jffs2 (a fucking copy of the above rootfs?)
-
-For dumping mtd parition is used tool nanddump. Here is example how to dump
-kernel image without padding to file zImage:
-
- $ nanddump -i -o -b -s 0x00000800 -l 0x001FF800 -f zImage /dev/mtd2
-
-Params means:
--i - "Ignore errors"
--o - "Omit oob data"
--b - "Omit bad blocks"
--s - "Start address"
--l - "Length"
--f - "Output file"
-
-Please note that some new versions of naddump have some options removed and
-some are enabled by default. Before using check params of your nanddump version.
-
-
-// Extra notes //
-
-[MTD] NAND Consolidate oobinfo handling
-
-The info structure for out of band data was copied into
-the mtd structure. Make it a pointer and remove the ability
-to set it from userspace. The position of ecc bytes is
-defined by the hardware and should not be changed by software.
-
-// The oob stuff
-
-In mtd3 the OOB data is 64 bytes aka 0x40, and this oob stuff
-appears every 2KB aka 0x800 bytes.
-
-/*
- * Obsolete legacy interface. Keep it in order not to break userspace
- * interfaces
- */
-struct nand_oobinfo {
- uint32_t useecc;
- uint32_t eccbytes;
- uint32_t oobfree[8][2];
- uint32_t eccpos[32];
-};
-
View
@@ -1,46 +0,0 @@
-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])
View
35 doc/faq
@@ -1,35 +0,0 @@
-FAQ:
-
-*) How can I set my Internet Tablet into RD mode with 0xFFFF?
-
- Just type '0xFFFF -R 1' as root
-
-
-*) How can I unpack a FIASCO firmware?
-
- Just type '0xFFFF -M FiascoFirmware.bin -u'
-
-
-*) How can I flash a new rootfs?
-
- # 0xFFFF -m rootfs.jffs2 -f
-
-
-*) How can I flash a full FIASCO image?
-
- # 0xFFFF -M FiascoFirmware.fiasco -f
-
-
-Advanced commands:
-
-*) How to extract the firmware pieces from a running device?
-
- It is possible to dump the firmware pieces from the internal MTD to reconstruct a FIASCO image.
- To do this recompile the flasher for ARM and run this command in the device:
-
- # mkdir /media/mmc1/backup
- # 0xFFFF -e /media/mmc1/backup
-
- To dump directly into FIASCO image run:
-
- # 0xFFFF -E /media/mmc1/backup.fiasco
Oops, something went wrong.

0 comments on commit 67584f5

Please sign in to comment.