summaryrefslogtreecommitdiffstats
path: root/doc/faq
diff options
context:
space:
mode:
authorpancake <pancake@dazo>2008-03-07 00:20:45 +0100
committerpancake <pancake@dazo>2008-03-07 00:20:45 +0100
commitedac98d26ee29bbdc3e16be8ecec5cbfff80482f (patch)
tree100f244d6a80590c3a7641b3dcdd452309c788d0 /doc/faq
parent83c25d7eb267f866968c7806c4afacf00fdfead5 (diff)
download0xFFFF-edac98d26ee29bbdc3e16be8ecec5cbfff80482f.tar.bz2
* Shift doc/faq to doc/faq20.3.9
* Add 'doc/faq' with most used commands * -e can be used with -u to specify the path to extract the files * Remove gui directory - GUI source is in src/gui - Incrusted inside the build and install targets (ignores build and install errors)
Diffstat (limited to 'doc/faq')
-rw-r--r--doc/faq78
1 files changed, 24 insertions, 54 deletions
diff --git a/doc/faq b/doc/faq
index 5212753..5a5ec7a 100644
--- a/doc/faq
+++ b/doc/faq
@@ -1,79 +1,49 @@
-<b>FAQ</b>
+<h2>FAQ</h2>
-This file tries to collect a bunch of common questions/answers about flashing
+<b>*) How can I set my Internet Tablet into RD mode with 0xFFFF?</b>
-<b>*) Why implement a free software flasher?</b>
+ Just type '0xFFFF -r 1' as root
- The Nokia Internet Tablets are based on Free Software (software libre), but
- not everything included *is* free software, for instance, the firmware flasher
- tool.
- The 0xFFFF project aims to feed the minds of those who really want to
- understand how these gadgets work internally, free the knowledge to
- avoid the restrictions and fill the lack of information on the most
- important part of the system.
+<b>*) How can I unpack a FIASCO firmware?
- That's it, now you can build and run this flasher on *BSD, w32, MacOSX on ARM,
- powerpc, x86, mips, etc...
+ Just type '0xFFFF -r 1' as root
-<b>*) Can I brick my device?</b>
+<b>*) How can I unpack a FIASCO firmware?</b>
- Of course! You're free to do what you want with your device :)
+ Just type '0xFFFF -u FiascoFirmware.bin -e /tmp' as root
- Seriously. Flashing a device is not a safe thing, so I give no warranty
- of what will happen to your device when using this tool.
- BTW, after a huge number of tests I can say that these devices are hard
- to brick, but if you are scared about bricking your device you should
- use the flasher provided by Nokia, it's better for your heart's health.
+<b>*) How can I flash a new rootfs?
+ Unpack the pieces from the fiasco firmware (the one distributed by Nokia for example) and then type:
-<b>*) What can I do with 0xFFFF?</b>
+ # 0xFFFF -R -p rootfs.jffs
- Actually 0xFFFF allows you to:
-
- - flash separated pieces of the firmware.
- - retrieve information about the device
- - reboot de mother board
- - extract the current firmware pieces from the device (reverse flash)
- - set the USB host/slave mode
- - set the R&R mode
- - identify firmware pieces
+<b>*) How can I flash a full FIASCO image?</b>
-<b>*) What is NOLO?</b>
+ It is not recommended to use, it needs more testing, and is more secure to unpack them first manually
+ and flash the pieces manually with multiple '-p' flags. If you are brave try:
- NOLO is the 'server-side' part of the flasher from Nokia. NOLO means
- NOkia LOader and it's composed by two pieces of the firmware that are
- flashed together.
+ # 0xFFFF -F FiascoFirmware.fiasco
- On the n800 firmwares, these two pieces are distributed in a single
- file, but when flashing a n770, NOLO requires to provide the xloader
- (without commiting) and then the secondary piece.
- This piece of software is closed source and is the responsable of
- handling the requests from the client-side flasher. It provides a
- query-like interface via usb control messages for doing different
- actions on the device.
+<h2>Advanced commands</h2>
+<b>*) How to extract the firmware pieces from a running device?</b>
-<b>*) How can I identify my device?</b>
+ 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:
- Theorically n770 and n800 have different USB device ID, but this is not
- true at all. The first series of the n800 comes with the same usb-id
- than n770. That's weird!
+ # mkdir /media/mmc1/backup
+ # 0xFFFF -e /media/mmc1/backup
- So, the only way to identify the device is by asking nolo for the version
- information of different pieces of the firmware. This can be faked, because
- you can flash n770 stuff on n800 and viceversa, but it's not recommended
- because it wouldn't work :)
+<b>*) Dumping configuration region</b>
-<b>*) Can I unpack fiasco blobs?</b>
+ There's a hidden mtd partition containing undocumented configuration information. This one can be
+ dumped from the device using the following command:
- Actually the fiasco format is not yet supported and not planned in
- short term. There is no real need for supporting a proprietary
- format image containing a proprietary system.
-
- We can just use tarballs containing the desired pieces.
+ # 0xFFFF -x