Here are the three possible contents of /etc/fw_env.config. You can try each of them to figure out if the problem is there:
Uhg, and I just got the LTE 
kit. Not got it working yet, but itâs in there, but need time to configure and test it.
Many thanks for sharing! I will still need to stay on 6.5 I guess.
Seems like something is broken in the U-Boot of the router,
Iâve reset the fw_env.config with the command echo '/dev/mtd0 0xF0000 0x10000 0x10000' > /etc/fw_env.config
But if I run the command âfw_printenvâ Iâm getting â Read error on /dev/mtd0: Attempted to read 65536 bytes but got 0â
Which seemed to be documented in the forum here Fw_printenv not working
Weirdly enough I used the solution and it âworkedâ but the command fw_printenv doesnât get stuck but return an error as /dev/mtd2 doesnât exist but nor-update has been updatedâŚ
Not sure if itâs all right.
Itâs finally all back to normal.
Here is the full investigation.
basically the root cause was the file
/etc/fw_env.config
As spotted here and there, it seems the expected values would be /dev/mtd0 0xF0000 0x10000 0x10000 but after checking with the command
cat /proc/mtd
dev: size erasesize name
mtd0: 000f0000 00010000 âU-Bootâ
mtd1: 00700000 00010000 âRescue systemâ
mtd2: 00010000 00010000 âu-boot-envâ
u-boot-env is actually located on mtd2.
I then updated /etc/fw_env.config with the following values :
/dev/mtd2 0x00000 0x10000 0x10000
and with that, the command fw_printenv is fixed and then allow to update the U-Boot without any issues :
strings /dev/mtd0 | grep âU-Bootâ | head -1
U-Boot SPL 2024.10-rc3-OpenWrt-r20343+127-4e1d1b7df0 (Sep 13 2024 - 01:38:50 +0000)
Hope it will help those facing the same issue!
2 Likes
There are multiple threads about issue with that commads
Thank you for your reports and for figuring out what was going wrong. We just updated the release notes, to make it obvious, that this is Omnia release and that there no other changes.
Yes, same as the previous release.
Hi,
unfortunately, again, this update made things worse. Frist I had reboots at least twice a day - now after trying the 7.0.3 with the updates of u-Boot and MAC it crashed the WHOLE System - no webinterface, no SSH connection possible. Will try to flash medkit, but so far, this is really annoying! So far, I don´t have a clue if my Omnia or the wifi card is responsible. But the router was tested from the Turris team (thanks for that) - but only troublesâŚ
Greetz,
Vienna
UPDATE after Medkit
Changes performed by updater at 2024-09-24T07:45:27+00:00
⢠Downgraded package pkglists from version 1.13-58 to version 1.12-57
⢠Reinstalled package base-files from version 1517-7.0.3-r20343+127-4e1d1b7df0 to version 1517-7.0.2-r20343+125-4e1d1b7df0
⢠Installed package kmod-mt7916-firmware version 5.15.148+2023-09-11-bdf8ea71-5-644b272c1f9b9ebbbd72c885f37b488c
⢠Downgraded package turris-version from version 7.0.3 to version 7.0.2
⢠Removed package cznic-repo-keys-test version 4.2-5
⢠Removed package initial-config version 0.2.3-8
⢠Removed package kmod-fs-xfs version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
⢠Removed package kmod-fs-exfat version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
⢠Removed package kmod-fs-ext4 version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
⢠Removed package kmod-lib-crc16 version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
⢠Removed package kmod-fs-exportfs version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
⢠Removed package kmod-fs-vfat version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
⢠Removed package kmod-nls-iso8859-1 version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
⢠Removed package kmod-nls-cp437 version 5.15.148-1-644b272c1f9b9ebbbd72c885f37b488c
Iâm sorry for your experience. You can try the new reset mode - wait for 10 LEDs shining. This wouldnât alter your settings, will just change the frequency the RAM is working on to ensure better compatibility and stability.
Which medkit did you download? It clearly says downgrading from 7.0.3 to 7.0.2.
So it seems you used some HBK medkit
HBT otherwise I would not refer to 7.0.3⌠can you agree?
So basically it is not supported. I am 99% sure if you use HBS medkit and then change branch to HBK/HBT all will work. Its the downgrade that deletes core modules from kernel that messes up things
Sorry, but what is not supported - to flash medkit with latest image? And sorry to say, since the update caused it, why should it work?
Last time I was messing around with medkits each time I flashed somethibg else than stable there were problems. And it says on the wiki that changing branch i only supported going up. Some time ago I was using HBL but you first flash stable and then change branch to whatever up
Yeah but you used HBT not HBS so it first tried to downgrade to the default branch which is stable. So it was not really an upgrade but downgrade and because of that problems.
Alternatively you could TRY to flash HBT and after doing the initial wizard go yo ssh and before the pkgupdate kicks in do switch-branch hbt this MAY also work but its more hassle with timing
All medkits are by default pointing to stable branch. If you want to start from scratch in a different branch, you can use medkit from whatever branch you want, but you have to disable updates and before enabling them use switch-branch to point to the correct branch.
As suggested startet over with 7.0.3 - disabled updates, switched branches. Now running on minimal single band wifi. If nessasary I will post updates after I enabled Sentinel, DAWN and Ad block again. Since I am not sure if the MT79xx wifi interface is causing the troubles, I am truely looking forward to Turris 8! Further I did the reset with 10 LED as @miska suggested.
Great! And when will be TOS 8 based on OpenWrt 23.05 in HBT?
I had this issue with transmission on HBS, but it seems to have gone away since I switched to HBT. Though, in theory, they should be the sameâŚ