The file sizes look correct. The only good explanation is that you must have done the backup after the device has already been flashed with OpenWrt, hence that's what you are restoring now.
LE: Another issue I've noticed, having an Android mobile phone and a Google Nest Hub 2nd gen, both connected to the same 5Ghz WLAN network. Using the "wed" testing version, the Google Home App saw all my devices fine, but when accessing the Nest Hub it said in a banner something like that "some settings are unavailable, check that your devices are on the same Wi-Fi network". Volume control and other functions worked OK, only the "restart device" function did not have any effect. Now I've reverted to the "master" version and the banner message disappeared and I can restart the Nest Hub from the Home App. Maybe this helps for further diagnosing.
4.3W idle with two ethernet cables connected (1 LAN, 1 WAN), after running echo "schedutil" > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
5.4W idle with two ethernet cables connected (1 LAN, 1 WAN), after running echo "schedutil" > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor and WiFi radios (2.4Ghz and 5Ghz) enabled.
Edit:
Forgot to enable the WiFi radio on OpenWRT, which was the reason the power usage on OpenWRT was lower than on stock firmware. With the schedutil governor power usage is about the same as on stock.
Interesting! According to your screenshot the CPU actually runs at 30Mhz most of the time. So does that mean 30Mhz actually works fine (in combination with schedutil) and doesn't need to be fixed as proposed in https://github.com/openwrt/openwrt/pull/4440?
I can confirm reboot works fine with schedutil without changing the minimum frequency.
Yes, many have confirmed that 30 MHz seems to work, but consumes just as much energy as 300 MHz does and the label of that lowest frequency in mt7622.dtsi device tree also hints that 300MHz was intended there.
Hi guys.. I'm usually a lurker but today i fucked up bad.
I was trying to install the snapshot on my RT3200.. everything was going swell 'til the part in the guide where you powercycle the router. I tried powercycling the router three times but it kept booting back up to the OpenWRT recovery.. I had a 'smart' idea. I decided to flash to the stock OEM firmware in the OpenWRT temp recovery in hopes that it would boot back to the oem firmware. But Alas, I believe i have a bricked RT3200 which just flashes twice every second now.
How do I unbrick? i'm going to run off tomorrow to Central Computers and buy a TTL to USB
Hello everyone, I will be on a gigabit connection this afternoon at 2 p.m. in Switzerland, it is currently 11:30 a.m. at home,
Do you want me to carry out tests as a qosify example or the script I am currently using from elan or specific commands, I would write to you around 2:15 p.m. Swiss time when I was installed at my uncle's house he told me that he was fiberglass but I do not know if it is 1GO or 10go because it is possible in Switzerland thank you
If you have flashed anything while running the UBI recovery on top of a non-UBI (ie. stock) bootchain, the only way to recover from there is by using the console on the serial port inside the device.
I start to wonder if it was a good idea to recommend everyone to do the full backup. The risks of getting it wrong may well outweigh.
Hi, I am planning to buy two Linksys E8450 to setup a 802.11s Mesh network with 802.11k/v/r Fast Roaming. However, I am not familiar with OpenWrt so I want to ask some basic questions:
Which image I should use to flash to OpenWrt firmware?
Do the Linksys E8450 with OpenWrt support 802.11s and 802.11k/v/r?
As I will flash the routers using non-UBI method (as the router is in warranty), I would like to know the correct method of flashing it in the vendor firmware web admin page. I see there are several image available in the download page. https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/
I managed to load Uboot on Putty but what option do I press? I just wanna flash this to go back to stock and try flashing OpenWrt again.
1. System Load Linux to SDRAM via TFTP.
2. System Load Linux Kernel then write to Flash via TFTP.
3. Boot master system code via Flash.
4. Boot slave system code via Flash.
5. System Load U-Boot then write to Flash via TFTP.
6. System Load U-Boot then write to Flash via Serial.
7. System Load ATF then write to Flash via TFTP.
8. System Load Preloader then write to Flash via TFTP.
U-Boot console
I don't know what option to press. I read somewhere in this thread I have to press two? Once I do, I have to have a filed called "lede-mediatek-mt7622-MTK-AX3200-MT7531-squashfs-sysupgrade.bin"
where do I even find this file?