Hi, I bought a new TP-Link EAP 613 and trying to install OpenWRT using firmware upgrade option.
Below are the firmware details :
I tried using factory.bin (openwrt-23.05.3-ramips-mt7621-tplink_eap613-v1-squashfs-factory.bin) and sysupgrade.bin (openwrt-23.05.3-ramips-mt7621-tplink_eap613-v1-squashfs-sysupgrade) which i got from https://openwrt.org/toh/hwdata/tp-link/tp-link_eap613_v1 .
I get the below error when i use the factory.bin and get "bad file" when i use sysupgrade.bin
Can anyone please help if i am missing anything?
Per the git commit, you may need to shorten the filename, and you need to login via ssh first:
Factory install:
- Enable SSH on the device via web interface
- Log in with SSH, and run
cliclientd stopcs
- Upload -factory.bin image via web interface. It may be necessary to
shorten the filename of the image to e.g. 'factory.bin'.
Thanks, however i already tried that step.
I am able to log in ssh and do cliclientd stopcs which shows me success.
But still i am not able to install openwrt shortened name factory.bin image.
I am also getting into the same issue. Trying to figure out a way to install. Will keep you posted if I am successful.
1 Like
It looks like FW v1.4.4 (and probably v1.4.3) use a compatibility level of 2, instead of level 1 used by OpenWrt.
You should be able to use my patch-safeloader.py script to bump the compatibility version of a (OpenWrt) firmware image. Usage is
python patch-safeloader.py -f firmware.bin -o firmware-2.bin version -c 2
1 Like
I have the EAP613v1.6 and I used this script to patch the .bin. Flashing the firmware seemed to work (went 0% to 100% on the web UI).
The web ui lost connection (which is expected) but I don't see another host on my network. Initially, my router had the default openwrt hostname so I changed that and rebooted/reconnected the AP just in case that was an issue.
Not sure what to do from here.
1 Like
OpenWrt defaults to using a static 192.168.1.1 address on the LAN interface. You'll have to connect to this address (on a point-to-point connection if your LAN uses the same subnet) to configure the device.
Thank you! I'm not sure why I didn't think about that.
I disconnected my router from my network and was able to connect via Ethernet to change the IP address.
I'm very happy it works, especially given that it's v1.6 not the v1 that is officially supported.
Luckily minor versions with TP-Link usually don't offer signifcant changes that warrant seperate support: e.g. Archer AX23 (v1 and v1.20).
