Unable to find factory.bin for GL-MT1300

Installing and Using OpenWrt
1

I tried to find the factory.bin image for the 21.02.3 release from here and I cannot find it.

I only find the glinet_gl-mt1300-initramfs-kernel.bin and https://downloads.openwrt.org/releases/21.02.3/targets/ramips/mt7621/openwrt-21.02.3-ramips-mt7621-glinet_gl-mt1300-squashfs-sysupgrade.bin . When I tried to flash either from the web interface I got the following message:

Device gl-mt1300 not supported by this image Supported devices: glinet,gl-mt1300 - Image version mismatch: image 1.1, device 1.0. Please wipe config during upgrade (force required) or reinstall. Reason: Config cannot be migrated from swconfig to DSA Image check failed.

The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.

Obviously I didn't try to force install it. Any ideas?

2
3

Says right so in the message. That should fix it.

1 Like
4

Use the sysupgrade.bin version from the uboot interface.

5

The first thing I tried is to follow the instructions here. I did try the web interface instructions and the command line instructions with sysupgrade.
The message that I mention does not appear anywhere on the page, so this is not helpful.

6

How? If you suggest that I reset the router to factory settings and try it again, I already did that and it did not work. The same message. I even tried the command line sysupgrade tool but no option to wipe config:

root@GL-MT1300:/tmp# sysupgrade --help
Usage: /sbin/sysupgrade [<upgrade-option>...] <image file or URL>
       /sbin/sysupgrade [-q] [-i] [-c] [-u] [-o] [-k] <backup-command> <file>

upgrade-option:
        -f <config>  restore configuration from .tar.gz (file or url)
        -i           interactive mode
        -c           attempt to preserve all changed files in /etc/
        -o           attempt to preserve all changed files in /, except those
                     from packages but including changed confs.
        -u           skip from backup files that are equal to those in /rom
        -n           do not save configuration over reflash
        -p           do not attempt to restore the partition table after flash.
        -k           include in backup a list of current installed packages at
                     /etc/backup/installed_packages.txt
        -T | --test
                     Verify image and config .tar.gz but do not actually flash.
        -F | --force
                     Flash image even if image checks fail, this is dangerous!
        -q           less verbose
        -v           more verbose
        -h | --help  display this help

backup-command:
        -b | --create-backup <file>
                     create .tar.gz of files specified in sysupgrade.conf
                     then exit. Does not flash an image. If file is '-',
                     i.e. stdout, verbosity is set to 0 (i.e. quiet).
        -r | --restore-backup <file>
                     restore a .tar.gz created with sysupgrade -b
                     then exit. Does not flash an image. If file is '-',
                     the archive is read from stdin.
        -l | --list-backup
                     list the files that would be backed up when calling
                     sysupgrade -b. Does not create a backup file.
7

I am not comfortable flashing via uboot. Have you come across the same issue on the same device and uboot flash worked?

Can you explain to me why uboot flash will work, while sysupgrade and web interface flash failed with the same message?

8

Well, you only (clearly) said you tried the web interface.

If everything else fails, go uboot, it doesn't involve the current OS, when performing the flash.

9

Do you consider that if I ignore the message that I got and flash via uboot is safe?

10

uboot flashing have a better chance of succeeding, but you could probably force ( -F) the sysupgrade, unless already tried.

11

Do you understand the message that I mention above? Have you seen it before?

12

Which one of them?

The 1.0 <> 1.1 or the one about DSA?

The DSA is solved by wiping the settings, as stated, the 1.1 - 1.0 shouldn't really matter, usually the devices don't change, hw wise, in a minor update.

If you're worried, don't flash openwrt.

13

How do you wipe the seettings?

14

Did you read the sysupgrade help screen you posted?

2 Likes
15

Use -F -n $sysupgrade-image on the command line, as documented in the help you pasted.

2 Likes
16

I did and it does not mention something about "wiping".

I appreciate the time you spend on this thread, but I do not think you want to help. Every question I have asked you, you deliberately did not answer. Since you do not want to help, I would appreciate it if you start spending your time in someone else's post.

17

I will give it a try, thank you.

18

And I don't think you take in the things you claim you've read.

-n do not save configuration over reflash

2 Likes
19

Aka 'wipe settings'. By default OpenWrt will try to keep settings, so to wipe them you need to tell it not to keep them.

3 Likes
20

Like I said, spend your time in someone else's post.