Firmware for EDUP RT2960

Installing and Using OpenWrt
1

I got this device from alibaba and found some threads that talked about this device being similar to other ones.

AFAIU this device is similar to simax1800T, https://openwrt.org/toh/sim/simax1800t

Following Help flashing Fenvi wr1800k with tftpd, I was able to flash https://downloads.x-wrt.com/rom/x-wrt-24.04-b202411071136-ramips-mt7621-xwrt_wr1800k-ax-nand-initramfs-WR1800K-factory.bin via the web UI of the stock firmware and now I can access X-WRT LuCI web UI.

Now when trying to upload https://downloads.openwrt.org/releases/23.05.4/targets/ramips/mt7621/openwrt-23.05.4-ramips-mt7621-sim_simax1800t-squashfs-sysupgrade.bin via X-WRT web UI, it throws error,

2024-11-14_15-00
2024-11-14_15-00618×623 78.3 KB

but https://downloads.x-wrt.com/rom/x-wrt-24.04-b202411071136-ramips-mt7621-xwrt_wr1800k-ax-nand-squashfs-sysupgrade.bin has no issues with flashing.

I did not proceed with flashing as I would like to use OpenWrt on this device if possible.

How can I identify this device to know what OpenWrt firmware can be installed on this device?

2

then you should flash it based on the wiki page you linked to.

or try forcing the upgrade, but there's always a risk of soft bricking.

x-wrt <> openwrt.

3

then you should flash it based on the wiki page you linked to.

https://openwrt.org/toh/sim/simax1800t this one?

this one fails, should I force upgrade? I don't have any backup and/or stock firmware available.

4

that was the one you posted, right ?

I wouldn't, not without an USB TTL on stand by.

5

I have one, but I have 0 experience with working with hardware. I have minicom and putty (both on Linux), what do I need to do? How should I proceed?

6

I'm not saying you need it, I'm saying you might need it.

the serial interface is also described in the wiki.

7

Usually you can sysupgrade resetting configuration, BUT compare DTS files and ask them specifically.

8

I understand how to connect it, I was asking, what do I have to do with it.

I see the u-boot boot menu, and none of the key word to stop the boot process.

then after boot I just have a prompt to login to router, is that what you mean I would use to fix/debrick it?

9

Can you explain a little? I don't know what DTS files are and who should I ask?

10

it's the one of the ways of recovering a soft bricked device, assuming you can interact with u-boot.

11

As I mentioned, I am not able to interrupt boot sequence meaning I cannot choose any item in the list of u-boot menu.. also I know nothing about u-boot other than its a bootloader for embedded devices.

12

not a big issue, as long as you can't communicate with it...

I assume you didn't connect Vcc to the serial interface of the device ?

13

I didn't as it was not marked in photo that shows how to connect serial interface for the device. Do I have to? is this the reason key input was not getting through during boot?

14

Vcc shouldn't be used, you did the right thing....

why you can't talk to u-boot is a different issue, it might have been locked down by the vendor.

if x-wrt works the same way as openwrt, you could try to extract the u-boot settings by running fw_printenv via ssh, it might be a simple (and removable) soft lock.

and no, we don't know how to install the binary on x-wrt, if it isn't already there.

1 Like
15

Yes sometimes the manufacturer sets the u-boot environment parameter bootdelay = 0 which prevents interrupting the bootloader and taking serial control. But you can change that setting using a running OpenWrt based OS. That will make debricking with serial possible, so you definitely want that in place before trying an unproven image.

1 Like
16

my thought exactly, but we need to get to those settings 1st.

1 Like
17

here is the output for fw_printenv

root@X-WRT:~# fw_printenv
baudrate=115200
bootcmd=mtkautoboot
bootdelay=0
bootmenu_0=Factory Network Boot=factoryboot
bootmenu_1=Auto Dual System Boot=autoramboot
bootmenu_2=Upgrade firmware=mtkupgrade fw
bootmenu_3=Upgrade bootloader=mtkupgrade bl
bootmenu_4=Upgrade bootloader (advanced mode)=mtkupgrade bladv
bootmenu_5=Load image=mtkload
bootmenu_6=Main system=mtkboardboot
bootmenu_7=Boot From Firmware2=bootfw2
ethact=eth@1e100000
factory_boot=1
fdtcontroladdr=8ffed140
ipaddr=192.168.1.28
netmask=192.168.1.254
serverip=192.168.1.254
stderr=uartlite0@1e000c00
stdin=uartlite0@1e000c00
stdout=uartlite0@1e000c00
factory_mode=1
firmware_select=2

bootdelay is indeed set to 0.

18

fw_setenv bootdelay=5

verify afterwards.

1 Like
19

then reboot? this persists?

20

yes, it should stick.

it might also be fw_setenv bootdelay 5, trial and error.