« La Fonera 2.0 temporarily out of stock, will be back soon!
The ugly earthy Mr. Caterpillar mutated into a beautyful and joyful flying butterfly »

Fonera 2.0 Failsafe image

Hi all,

This post is only to publish the failsafe image for your foneras 2.0. The failsafe image you have now (identified as image2) is broken. We recommend to replace it just in case you need it in the future.

These are the steps to flash it using ssh

  • Connect to the Fonera using ssh.
  • root@Fonera:/# cd /tmp
  • root@Fonera:/# wget http://download.fonosfera.org/failsafe/20090206_FON2202_failsafe.image
  • mtd -r write 20090206_FON2202_failsafe.image image2

The process might show some errors while flashing but they are probably not critical. Just MAKE SURE you don’t make any activity during this process.

The file is located here, if you want to download it and use a different method. The md5sum of the file is: d29e07bdcb6df04209cafafce8f3bc5f

This entry was posted on Tuesday, February 17th, 2009 at 9:54 am and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

11 Responses to “Fonera 2.0 Failsafe image”

  1. Olivier Says:
    February 17th, 2009 at 3:11 pm

    Hi !

    how to be sure that the update succeded ?
    I followed the instructions, and I had an error as you said…
    Now, I really don’t know if the failsafe image is the right one.

    Thanks. Olivier.

  2. mbirton Says:
    February 17th, 2009 at 9:02 pm

    What do yot mean by ’some errors’? i got ‘failed writing image’, so … it’s ok or not? i have oktopussy2. anybody tried this ‘failsafe’?

  3. Raphaël Says:
    February 17th, 2009 at 11:20 pm

    Same problem there :

    root@Fonera:~# mtd -r write 20090206_FON2202_failsafe.image image2
    Unlocking image2 …
    Writing from 20090206_FON2202_failsafe.image to image2 … [w]Error writing image.

    With OktoPussy 2 (v2.2.2.2).

  4. andyvalval Says:
    February 20th, 2009 at 8:54 pm

    I cann’t complete de process:

    root@Fonera:~# cd /tmp
    root@Fonera:~# wget http://download.fonosfera.org/failsafe/20090206_FON2202_fail
    safe.image
    Connecting to download.fonosfera.org (67.192.249.56:80)
    20090206_FON2202_fai 100% |*******************************| 1280k 00:00:00 ETA
    root@Fonera:~# mtd -r write 20090206_FON2202_failsafe.image image2
    Could not open mtd device: image2
    Can’t open device for writing!
    root@Fonera:~#

    Any ideas?
    TIA

  5. iurgi Says:
    February 22nd, 2009 at 8:25 pm

    Hi andyvalval,

    I think you don’t have an image2. run: cat /proc/mtd

    You should see an image2 in the list, but I think you won’t. Did you ever use redboot? If you did so, it looks like you erased image2 and never created it again :o

    If this is not the case, I suggest you ask in the mailing list or IRC

    iurgi

  6. andyvalval Says:
    February 22nd, 2009 at 10:05 pm

    iurgi,

    Yes, I used redboot three o four times to reinstall firmware, because the web process didn’t work properly.

    I¡ll try to run: cat /proc/mtd

    Thanks,

  7. andyvalval Says:
    February 22nd, 2009 at 10:21 pm

    root@Fonera:~# cat /proc/mtd
    dev: size erasesize name
    mtd0: 00030000 00010000 “RedBoot”
    mtd1: 00010000 00010000 “loader”
    mtd2: 007a0000 00010000 “image”
    mtd3: 006ed179 00010000 “rootfs”
    mtd4: 003b0000 00010000 “rootfs_data”
    mtd5: 0000f000 00010000 “FIS directory”
    mtd6: 00001000 00010000 “RedBoot config”
    mtd7: 00010000 00010000 “boardconfig”
    root@Fonera:~#

    You were right, I don’t have an image2

    What can I do?

    TIA

  8. Hubba Says:
    February 23rd, 2009 at 6:12 pm

    i got ‘failed writing image’ just like mbirton above - do have image2 listed in /proc/mtd though.

  9. mbirton Says:
    February 27th, 2009 at 3:24 pm

    i think there is nobody from support here … should i open a topic on wiki? or ticket? but im not sure for what … my fon is doing just fine without this update ;-)

  10. iurgi Says:
    March 2nd, 2009 at 10:26 am

    This update is not absolutely necessary. Those who used redboot in the past and now don’t have a image2 partition, will have more flash space for other apllications.
    Those who have the image2, but writing is failing… well, I’m not sure why this is happening, but if you wanna make sure you have the right image2, just use redboot to reflash it.

    In any case, as I said, image2 is not absolutely necessary, just a fallback system for unexperienced users. Assuming you’re all skilled users, you don’t need it. End user foneras, next production, will bring the correct image2.

    mbirton, there is people from support and active developers here ;) the thing is we don’t check much the comments for people asking for help, we do that through the mailing list or IRC.

  11. madrioso Says:
    March 20th, 2009 at 9:25 am

    I got the same writing error:
    # mtd -r write 20090206_FON2202_failsafe.image image2
    Unlocking image2 …
    Writing from 20090206_FON2202_failsafe.image to image2 … [w]Error writing image.

    I have an image2 partition:

    # cat /proc/mtd
    dev: size erasesize name
    mtd0: 00030000 00010000 “RedBoot”
    mtd1: 00010000 00010000 “loader”
    mtd2: 00620000 00010000 “image”
    mtd3: 0056d16f 00010000 “rootfs”
    mtd4: 00200000 00010000 “rootfs_data”
    mtd5: 00140000 00010000 “image2″
    mtd6: 0000f000 00010000 “FIS directory”
    mtd7: 00001000 00010000 “RedBoot config”
    mtd8: 00010000 00010000 “boardconfig”

    I wonder if someone was able to write the image2 sucessfully…

Leave a Reply