# Adding support for EAP235-WALL **URL:** \ **Category:** For Developers\ **Created:** [January 9, 2021, 5:35pm UTC](https://forum.openwrt.org/t/adding-support-for-eap235-wall/86280 "2021-01-09T17:35:20Z")\ **Posts on this page:** 1\ **Showing post:** 70
**Author:** ![svanheule](https://forum.openwrt.org/user_avatar/forum.openwrt.org/svanheule/32/88134_2.png) [@svanheule](https://forum.openwrt.org/u/svanheule)\ **Post date:** [August 21, 2021, 9:05am UTC](https://forum.openwrt.org/t/adding-support-for-eap235-wall/86280/70 "2021-08-21T09:05:05Z")
I dug a bit more, and found the likely cause of this issue: starting from FW v3, downgrades are disallowed. Since OpenWrt carries version number "0.0.0", the firmware considers this a downgrade and refuses the file. ``` [NM_Error](nm_fwup_verifyFwupFile) 02278: EAP235/230-Wall forbid fw reverted from 3.x.x to lower version! ``` As a quick fix, you could patch the "soft-version" partition of a TP-Link image into an OpenWrt factory image. 1. Download my [safeloader patching script](https://gist.github.com/svanheule/9f82e156a3601d4a726639eb7400ec97) 2. Download a v3 (or later, _must be different from the current firmware version_) [firmware](https://www.tp-link.com/support/download/eap235-wall/#Firmware), and the OpenWrt factory image (e.g. [for 21.02-rc4](https://downloads.openwrt.org/releases/21.02.0-rc4/targets/ramips/mt7621/)) 3. Run the patch script (change file names accordingly): `python patch.py -f OPENWRT_FACTORY.bin -i EAP235-WALLv1_3.0.0.bin -p soft-version -o FACTORY_PATCHED.bin` 4. Flash the patched factory image Please let me know the results, then I can come up with a proper solution for OpenWrt. Edit: People building their own firmware can also [test patches](https://github.com/svanheule/openwrt/tree/patch/safeloader-soft-verion-overwrite) --- _[View the full topic](https://forum.openwrt.org/t/adding-support-for-eap235-wall/86280)._