Not sure if these differences are due to physical variations or only region-dependent (like US vs UK). Maybe someone with deeper knowledge could explain us what exactly is stored here.
2 Likes
I'd say yes. Better safe and a bit more time consuming than sorry.
Cheers.
1 Like
@loyukfai or better just a minimal backup (which is sufficient and automatically created by the installer) than bricking the device when not carrying out the full backup procedure correctly...?
2 Likes
Following the Device flash complete backup procedure I also got a bit nervous at step 5 when my Belkin router didn't want to boot back to stock firmware after a power cycle. Tried it several times, and kept booting back to OpenWRT. So I can see how people would mess up there... Happened again when backing up my second RT3200 but at least then I knew this could happen. Not sure what the procedure is to make it boot back to stock, just tried power cycling several times.
2 Likes
And one that works with installer upgrades, in terms of retaining the original stuff rather than overwriting it? So that if the installer is run, and then an upgraded installer run, the user does not have to first backup mtd0, mtd1 and mtd2 manually before running the upgraded installer?
I also got confused / messed up with one device in trying to go back to stock and gave up. The instructions are much clearer now than they were before.
Perhaps this bit in the instructions:
Do not attempt to flash
openwrt-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itbfrom the running initramfs system -- it will fail to reboot, possibly requiring serial console access. Instead, powercycle the device to reboot into the original non-ubi firmware, and then flash theinstallerversion.
Should be highlighted somehow and also placed underneath the restoring vendor firmware, for those who give up.
I think this may have been what I did. Because back when I tried to go back to stock, I flashed the recovery image, and then found I could not run:
insmod mtd-rw i_want_a_brick=1
Because mtd-rw was not present.
Giving up, I thought I would just try to go back to production. I didn't realise at that point I needed to power cycle to get back to normal, freaked out, and then tried flashing the installer, imagining this would at least get me back to production on the RT3200.
Only to find I was then stuck and had no clue how to get out of it. Files were accepted/read using TFTP (I found the details in an online thread somewhere because they were not in the instructions), but then the device always seemed stuck in the recovery thing. Did I just need to power off for 30s and power on once flashed over TFTP? If so, that is so frustrating! On the other hand, maybe the fact that the TFTP file seemed to get sent means that it is still possible to fix in this broken state without the serial console? The TFTP server application definitely showed the file being sent across.
I'd be really curious if anyone could give insight on the above.
1 Like
The min-1V should be also used, as reboot does not work always with less then 1V for any frequency. Maybe you should just use 3 patches, or simply all the 4
Hi guys, I came from a TPLink Archer A7v5 and used to use the LuCI Network->Switch page to configure VLAN.
Now with a Belkin RT3200 with UBI mode installer and sysupgrade flashed, from dangowrt v0.6.1 (not the openwrt most up-to-date snapshot images), I find there is no Switch submenu under Network. Other things seemed fine though.
I am still new to openwrt, did some guessing here - Is it true that Switch submenu is not added to LuCI in that github image version? Or Switch is not added in LuCI for this device in general?
This is not rt3200 specific, but just a side effect of using DSA based switch drivers rather than out-of-tree swconfig, it applies to many other devices/ targets alike (yes, also the archer a7 v5 in the near future).
Please check DSA based configuration for details:
2 Likes
thank you guys, saved my day
1 Like
I'm looking forward to trying OpenWrt on the RT3200 but unfortunately it didn't work using the Fri Jan 7 12:11:01 2022 snapshot files:
Writing from <stdin> to firmware1 ...
Appending jffs2 data from /tmp/sysupgrade.tgz to firmware1..
.File /tmp/sysupgrade.tgz does not exist
Master boot:
NAND read: device 0 offset 0x500000, size 0x2000
8192 bytes read: OK
[do_read_image_blks] This is a FIT image,img_size = 0x73b20c
[do_read_image_blks] img_blks = 0xe77
[do_read_image_blks] img_align_size = 0x73b800
NAND read: device 0 offset 0x500000, size 0x73b800
7583744 bytes read: OK
bootm flag=0, states=70f
## Loading kernel from FIT Image at 4007ff28 ...
Bad FIT kernel image format!
ERROR: can't get kernel image!
MT7622>
Any idea what's wrong with it?
Each line is terminated with \n and the rest of the file is 0x00.
sw_version=1.0.0.1
modelNumber=RT3200
cert_region=
wan_mac_addr=
lan_mac_addr=
wifi_2g_mac_addr=
wifi_5g_mac_addr=
hw_revision=
hw_version=
manufacturer_date=
serial_number=
default_ssid=
default_passphrase=
wps_device_pin=
uuid_key=
manufacturer=Belkin
manufacturerURL=http://www.belkin.com
modelDescription=RT3200 AX3200 Gigabit WiFi Router
1 Like
Hi, is there an updated document covering benchmarks and ideal configurations of the device? Behind a 1Gbit/s cable I'm seeing very slow WiFi speeds and wonder if the default WiFi options are an issue?
2 Likes
mtd5 of the stock formware is covered by mtd3 in UBI layout, which is exactly why the minimal backup grabs the first 2048kB from there, because that's where devinfo is located.
See this to understand stock vs. ubi layout:
1 Like
You may want to use the installer (to switch to UBI) or regular initramfs image (because otherwise what ever you write to flash won't be ok to read by OpenWrt, so initramfs is needed for initial flash of non-UBI variant)
1 Like
Yes, but I think this was only recently added. Looks like he had installed the UBI version before this change and he only has mtd0..2 in the backup partition.
2 Likes
Image builder broken for upgrade now?
Error building the sysupgrade
asu.build.PackageSelectionError
Please report the error message and request
Request to server:
{
"board_name": "linksys,e8450-ubi",
"target": "mediatek/mt7622",
"version": "SNAPSHOT",
"packages": [
"auc",
"base-files",
"blockd",
"blockdev",
"busybox",
"ca-bundle",
"dnsmasq",
"dropbear",
"firewall",
"fstools",
"ip6tables",
"iperf3",
"iptables",
"kernel",
"kmod-fs-exfat",
"kmod-fs-ext4",
"kmod-fs-f2fs",
"kmod-fs-vfat",
"kmod-gpio-button-hotplug",
"kmod-ipt-offload",
"kmod-leds-gpio",
"kmod-mt7615-firmware",
"kmod-mt7615e",
"kmod-mt7915e",
"kmod-nls-base",
"kmod-nls-cp437",
"kmod-nls-iso8859-1",
"kmod-nls-utf8",
"kmod-usb-storage",
"kmod-usb-storage-uas",
"kmod-usb3",
"libc",
"libustream-openssl",
"logd",
"luci",
"luci-app-attendedsysupgrade",
"luci-ssl-openssl",
"luci-theme-openwrt-2020",
"mtd",
"netifd",
"odhcp6c",
"odhcpd-ipv6only",
"opkg",
"ppp",
"ppp-mod-pppoe",
"procd",
"procd-seccomp",
"procd-ujail",
"uboot-envtools",
"uci",
"uclient-fetch",
"urandom-seed",
"urngd",
"wpad-openssl"
],
".anonymous": false,
".name": "request",
".type": "request",
".index": 0
}
Package list missing or not up-to-date, generating it.
Building package index...
Downloading http://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/packages/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/openwrt_core
Downloading http://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/packages/Packages.sig
Signature check passed.
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/openwrt_base
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/Packages.sig
Signature check passed.
Downloading http://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/kmods/5.10.90-1-55878d243c4e5090eec0d590dd761867/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/openwrt_kmods
Downloading http://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/kmods/5.10.90-1-55878d243c4e5090eec0d590dd761867/Packages.sig
Signature check passed.
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/openwrt_luci
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci/Packages.sig
Signature check passed.
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/openwrt_packages
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages/Packages.sig
Signature check passed.
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/routing/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/openwrt_routing
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/routing/Packages.sig
Signature check passed.
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/telephony/Packages.gz
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/openwrt_telephony
Downloading http://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/telephony/Packages.sig
Signature check passed.
Downloading file:packages/Packages
Updated list of available packages in /home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/../../../../../../../../../../../home/aparcar/asu/worker2/cache/SNAPSHOT/mediatek/mt7622/dl/imagebuilder
Downloading file:packages/Packages.sig
Signature check failed.
Remove wrong Signature file.
Collected errors:
* check_conflicts_for: The following packages conflict with firewall:
* check_conflicts_for: firewall4 *
* opkg_install_cmd: Cannot install package firewall.
* check_conflicts_for: The following packages conflict with firewall:
* check_conflicts_for: firewall4 *
* opkg_install_cmd: Cannot install package firewall.
make[2]: *** [Makefile:168: package_install] Error 255
make[1]: *** [Makefile:133: _call_manifest] Error 2
make: *** [Makefile:252: manifest] Error 2
Close
3 Likes
I tried this, but after uploading initranfs-kernel.bin using the vendor UI the power button starts flashing. I can't connect to the router even after setting static IP. If I hold the reset button for 30 seconds and power it off and on, the router goes back to the stock firmware. Any ideas?
Before doing anything else I suggest you recover the master back to stock firmware. Boot the working stock firmware (presumably the slave) and use it's firmware upgrade page to flash the stock firmware and it will recover the broken master. If both the master and slave break you'll need a serial console to fix it.
My RT3200 booted fine after I flashed openwrt-mediatek-mt7622-linksys_e8450-initramfs-kernel.bin and I was able to temporarily install luci to try it out. I was unable to get the sysupgrade file working though so I am back with stock firmware and about to install the ubi version as suggested by daniel.
How do I choose which to use for boot? Is there a button or something? I don't see anything in the wiki.
I'm running stock firmware, I don't know what exactly holding the reset button did, but I presume it reverted everything back to stock.