OpenWRT One - 24.10.0-rc5 - LuCi missing

Installing and Using OpenWrt
1

Cannot for the life of me get luci back. I've installed 24.10.0-rc5 via USB but luci is not listed as installed. I receive the following conflict error when attempting package add:

root@OpenWrt:~# apk add luci
ERROR: unable to select packages:
  libuci20130104-2024.11.26~10f7996e-r1:
    conflicts: libuci20250117-2025.01.17~fb3c2343-r1[libuci=2024.11.26~10f7996e-r1]
    satisfies: world[libuci20130104] libiwinfo20230701-2024.10.20~b94f066e-r1[libuci20130104] netifd-2024.12.17~ea01ed41-r1[libuci20130104]
               odhcpd-ipv6only-2024.05.08~a2988231-r1[libuci20130104] procd-ujail-2024.12.22~42d39376-r1[libuci20130104] ubox-2024.04.26~85f10530-r1[libuci20130104]
               uci-2024.11.26~10f7996e-r1[libuci20130104] ucode-mod-uci-2024.12.06~209f041f-r1[libuci20130104]
  libuci20250117-2025.01.17~fb3c2343-r1:
    conflicts: libuci20130104-2024.11.26~10f7996e-r1[libuci=2025.01.17~fb3c2343-r1]
    satisfies: rpcd-2024.12.02~cc9a471c-r1[libuci20250117]
2

RC5 have luci pre installed, it's also using opkg.

5 Likes
3

Seems opkg is no more. As far as luci, check out the package list below. I can't raise luci gui via web browser.

root@OpenWrt:~# opkg list-installed
-ash: opkg: not found
root@OpenWrt:~# apk info
WARNING: opening from cache https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/packages/packages.adb: No such file or directory
WARNING: opening from cache https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/packages.adb: No such file or directory
WARNING: opening from cache https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/kmods/6.6.71-1-7520f413149ac060ff02685d13815237/packages.adb: No such file or directory
WARNING: opening from cache https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci/packages.adb: No such file or directory
WARNING: opening from cache https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages/packages.adb: No such file or directory
WARNING: opening from cache https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/routing/packages.adb: No such file or directory
WARNING: opening from cache https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/telephony/packages.adb: No such file or directory
WARNING: opening from cache https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/video/packages.adb: No such file or directory
airoha-en8811h-firmware
apk-mbedtls
base-files
busybox
ca-bundle
dnsmasq
dropbear
eip197-mini-firmware
firewall4
fitblk
fstools
fwtool
getrandom
hostapd-common
iw
iwinfo
jansson4
jshn
jsonfilter
kernel
kmod-cfg80211
kmod-crypto-acompress
kmod-crypto-aead
kmod-crypto-authenc
kmod-crypto-ccm
kmod-crypto-cmac
kmod-crypto-crc32c
kmod-crypto-ctr
kmod-crypto-des
kmod-crypto-gcm
kmod-crypto-geniv
kmod-crypto-gf128
kmod-crypto-ghash
kmod-crypto-hash
kmod-crypto-hmac
kmod-crypto-hw-safexcel
kmod-crypto-manager
kmod-crypto-md5
kmod-crypto-null
kmod-crypto-rng
kmod-crypto-seqiv
kmod-crypto-sha1
kmod-crypto-sha256
kmod-crypto-sha3
kmod-crypto-sha512
kmod-gpio-button-hotplug
kmod-hwmon-core
kmod-i2c-core
kmod-leds-gpio
kmod-lib-crc-ccitt
kmod-lib-crc32c
kmod-lib-lzo
kmod-libphy
kmod-mac80211
kmod-mt76-connac
kmod-mt76-core
kmod-mt7915e
kmod-mt7981-firmware
kmod-nf-conntrack
kmod-nf-conntrack6
kmod-nf-flow
kmod-nf-log
kmod-nf-log6
kmod-nf-nat
kmod-nf-reject
kmod-nf-reject6
kmod-nfnetlink
kmod-nft-core
kmod-nft-fib
kmod-nft-nat
kmod-nft-offload
kmod-nls-base
kmod-nvme
kmod-phy-airoha-en8811h
kmod-phy-aquantia
kmod-ppp
kmod-pppoe
kmod-pppox
kmod-rtc-pcf8563
kmod-slhc
kmod-thermal
kmod-usb-core
kmod-usb-xhci-hcd
kmod-usb-xhci-mtk
kmod-usb3
libblobmsg-json20240329
libc
libgcc1
libiwinfo-data
libiwinfo20230701
libjson-c5
libjson-script20240329
libmbedtls21
libmnl0
libnftnl11
libnl-tiny1
libubox20240329
libubus20250102
libuci20130104
libuclient20201210
libucode20230711
libudebug
libustream-mbedtls20201210
logd
mt7981-wo-firmware
mtd
netifd
nftables-json
odhcp6c
odhcpd-ipv6only
openwrt-keyring
ppp
ppp-mod-pppoe
procd
procd-seccomp
procd-ujail
ubi-utils
uboot-envtools
ubox
ubus
ubusd
uci
uclient-fetch
ucode
ucode-mod-digest
ucode-mod-fs
ucode-mod-nl80211
ucode-mod-rtnl
ucode-mod-ubus
ucode-mod-uci
ucode-mod-uloop
urandom-seed
urngd
usign
wifi-scripts
wireless-regdb
wpad-basic-mbedtls
zlib
root@OpenWrt:~#
4

You're not running RC5, there's no opkg in snapshots.

2 Likes
5

Well, this is curious. I did NOT flash snapshot. I downloaded RC5 (just double-checked the files on my thumb drive). Checksum matches RC5 download listed here: https://firmware-selector.openwrt.org/?version=24.10.0-rc5&target=mediatek%2Ffilogic&id=openwrt_one

I followed steps listed here to the T: https://openwrt.org/toh/openwrt/one
First flashed NAND factory + NAND preloader. Then flashed factory UBI all from USB. I say flashed, because I followed the steps and received a solid green good boot light after. If it didn't take, no idea why.

{
        "kernel": "6.6.71",
        "hostname": "OpenWrt",
        "system": "ARMv8 Processor rev 4",
        "model": "OpenWrt One",
        "board_name": "openwrt,one",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "SNAPSHOT",
                "revision": "r28608-693c1ea81a",
                "target": "mediatek/filogic",
                "description": "OpenWrt SNAPSHOT r28608-693c1ea81a",
                "builddate": "1737032215"
        }
}
6

I'm going to spell out what I'm doing here because I'm at a loss:

  • Download openwrt-24.10.0-rc5-mediatek-filogic-openwrt_one-snand-factory.bin AND openwrt-24.10.0-rc5-mediatek-filogic-openwrt_one-snand-preloader.bin
  • Rename both to remove "-24.10.0-rc5." Don't know if this makes any difference, but someone on these forums suggested it might.
  • Copy both to a FAT32 thumb drive
  • Unplug the router
  • Move the rear dip switch to the NOR position
  • Insert the thumb drive into the FRONT USB-A port
  • Press & hold the FRONT button while simultaneously plugging in the router
  • Keep holding that FRONT button until I get a solid green light
  • Wait another minute just for good measure
  • Attempt to ssh to the router - receive a warning about host key verification failure
  • Clear the known hosts key entry
  • Retry ssh and add the new key - connection established
  • Run ubus call system board and receive the following result. Keep in mind we started with SNAPSHOT and flashed with RC5. We end up with RC2??
"kernel": "6.6.63",
        "hostname": "OpenWrt",
        "system": "ARMv8 Processor rev 4",
        "model": "OpenWrt One",
        "board_name": "openwrt,one",
        "rootfs_type": "initramfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.0-rc2",
                "revision": "r28161-ea17e958b9",
                "target": "mediatek/filogic",
                "description": "OpenWrt 24.10.0-rc2 r28161-ea17e958b9",
                "builddate": "1733226068"
7

I think RC2 is what the Ones are shipped with, from the vendor.

8

None of this is required in normal operation. You followed the Recovery, not Installation.

Go to:
https://downloads.openwrt.org/releases/24.10.0-rc5/targets/mediatek/filogic/

Download the openwrt_one-squashfs-sysupgrade.itb Copy it to your USB drive as openwrt-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb

Ensure NAND/NOR switch is set at NAND (normal operating mode)
Power down OO
Press and hold the reset button and power up the OO
Wait for green led for good boot

I suggest you read the Getting Sterted Guide from https://one.openwrt.org/sources/

1 Like
9

Followed and now I'm right back at SNAPSHOT with no working luci.

 "kernel": "6.6.71",
        "hostname": "OpenWrt",
        "system": "ARMv8 Processor rev 4",
        "model": "OpenWrt One",
        "board_name": "openwrt,one",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "SNAPSHOT",
                "revision": "r28608-693c1ea81a",
                "target": "mediatek/filogic",
                "description": "OpenWrt SNAPSHOT r28608-693c1ea81a",
                "builddate": "1737032215"

We are beyond "normal operation." Everything was working out of the box. I decided to update via luci (seemed like a sensible thing to do), and the update hung. Ever since I'm stuck without luci.

10

And, yes, I've read the guide.

11

That’s a relevant missing point.

Try booting into Recovery Mode.

  • power off the OO
  • ensure NAND boot is selected
  • Press and hold the front button
  • Power up the OO and wait for boot into initramfs

sysupgrade the RC5 sysupgrade.itb file from your PC instead of the USB and wait for good boot led.

1 Like
12

Following this, all I get is a rapidly flashing orange status LED that doesn't go away. Does not give a good boot green. Attempting to ssh into the OO returns "network is unreachable."

13

Try this once again and watch the led sequence on power up. You should see all three leds light up. As soon as you see the white and green leds go out and the red (orange) led only lit, immediately release the front button. The white led should flash rapidly and then to solid green good boot indication.

Rapidly flashing red(orange) led indicates the boot sequence start was missed.

On my OO, this boots me to my original initramfs with LuCI enabled on kernel 6.6.50 which is my original out of box flash (I am now at kernel 6.6.71). I suspect your OOB will boot to recovery initramfs with LuCI enabled to 24.10.0-rc2 kernel 6.6.63. See ouput of your ubus call system board from Post 6 that indicates:
"rootfs_type": "initramfs"

14

THANK YOU!!! That was the missing procedure: release front button AFTER white & green go out. This should be added to guides asap. As they read, it suggests the buttons should be held until solid green.

scp only worked with the -O flag. The sysupgrade flash from CLI was otherwise uneventful. RC5 is now running & LuCI is back!

15

Agreed. I’ll do so.

Glad to see your up and running.

FWIW, I see little need for typical users to use the SPI-NOR U-Boot procedures unless absolutely needed. I have never touched SPI-NOR nor SPI-NAND U-Boot on my production device. So far my Lab OO has shown me that it’s really only rarely needed other than an OOPS anomaly.

For normal firmware updates there are multiple methods that can be used by following typical OpenWrt firmware update procedures:

  • USB method from Getting Started Guide. Caveat - not all USB sticks are compliant. I tried several before I was able to use this method consistently.
  • Booting to Recovery initramfs Mode and running sysupgrade from CLI or LuCI. I will eventually upgrade this to more recent build but atm hasn’t caused any issues.
  • Upgrading from the Firmware-Selector, LuCI Attended SysUpgrade, or auc which will eventually be deprecated in favour of Owut.
1 Like
16

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.