Forums

Home Forums Troubleshooting Image corrupted on updating toronto-N v 1.2

Image corrupted on updating toronto-N v 1.2

This topic contains 9 replies, has 2 voices, and was last updated by  alfredosc8 5 months, 1 week ago.

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #4367

    alfredosc8
    Participant

    I have toronto-N with v 1.20 and trying to update automatically it tells Image corrupted. I have 2 of them and this one is not showing the apps like vpn.
    I try to reset with button without any luck. Do I have to update to previous version before use the latest?
    In case where are the files tu update manually?

    Thanks
    Alfredo

    #4371

    support
    Participant

    The v1.20 image is pretty old. Your hardware probably doesn’t have enough space to hold the new firmware image.

    #4408

    alfredosc8
    Participant

    It doesn’t include the apps menu, I believe the previous owner flushed using bad firmare. Do you have the files for update manually at list closed but higher?

    #4442

    alfredosc8
    Participant

    I have 2 of them internally the same as cpu/ memory/ etc.
    I believe previous owner flushed with wrong image and now I have to apply manually updates to move fro 1.20 to 2.2.x as now.
    Thai is the reason I’m asking for the image files of the previous versions. I didn’t find in any place.
    Can you give an help.
    Tanks

    #4444

    support
    Participant

    In that case, manual upgrade won’t help. The update process will fail because it will detect that there’s not enough space to hold the new firmware.

    If originally there’s enough space, after you downgrade to 1.20, the amount of storage space was brought down to that in the 1.20 image. Restoration back to a later version that requires more space becomes impossible.

    #4449

    alfredosc8
    Participant

    The reset bring it to 1.20, not myself. I’m comparing the one working and this one. They are exactly the same as HW and memory.
    The only difference on the one that is not working are: busybox 1.23.2 ,
    DISTRIB_ID=”OpenWrt”
    DISTRIB_RELEASE=”Chaos Calmer”
    DISTRIB_REVISION=”r47466″
    DISTRIB_CODENAME=”chaos_calmer”
    DISTRIB_TARGET=”ramips/mt7620″
    DISTRIB_DESCRIPTION=”pcWRT TORONTO-N v1.20″
    and df is:
    Filesystem 1K-blocks Used Available Use% Mounted on
    rootfs 3456 404 3052 12% /
    /dev/root 2816 2816 0 100% /rom
    tmpfs 30208 80 30128 0% /tmp
    /dev/mtdblock6 3456 404 3052 12% /overlay
    overlayfs:/overlay 3456 404 3052 12% /
    tmpfs 512 0 512 0% /dev

    this has /rom of 2816 and the good one has 6144 1k blocks.
    Do you think the flash memory is smaller or it’s formatted differently?
    I’m thinking flash harder the device, eventually with openwrt distribution, I’m a colleague pretty confident on those embedded linux. I has been pioneer on using unix embedded for building laser printers on 90s .
    Thanks

    #4454

    support
    Participant

    @alfredosc8 The boxes may look the same but the earlier version has only 8MB flash. The later version has 16MB. The RAM size did not change between the versions.

    #4456

    alfredosc8
    Participant

    Is there a version, enough for 8M flash, I can install that includes vpn? probably the latest based on Chaos-Calmer could be good.

    #4458

    support
    Participant

    @alfredosc8 The pcWRT firmware with VPN support does not fit in 8MB.

    #4460

    alfredosc8
    Participant

    As higher can I update it?

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.