openwrt / openwrt/firmware-utils
TP Link EAP615 Wall V1 factory.bin can't be loaded with recent OEM firmware
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 20
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
I have a TP Link EAP615 Wall V1 sold in Australia. The label says US/1.0 but evidently the preloaded OEM firmware knows it is AU and refuses to load the OpenWRT factory.bin. I tried downgrading to an earlier OEM firmware as interim step, but EAP615-WALLv1_1.5.3 is the earliest version with AU support. After spending some time with TP-Link support they confirmed this.
Also, the way format of the TP-Link support list has changed somewhere between EAP615-WALLv1_1.2.3 and EAP615-WALLv1_1.5.0.
From tplink-safeloader -i <OEM >.bin.
1.2.3
SupportList:
EAP615-Wall(TP-Link|UN|AX1800-D):1.0
EAP615-Wall(TP-Link|CA|AX1800-D):1.0
EAP615-Wall(TP-Link|JP|AX1800-D):1.0
EAP615-Wall(TP-Link|EG|AX1800-D):1.0
1.5.3
SupportList:
EAP610(TP-Link|UN|AX1800-D):3.0 RU,EG,CA,JP,KR,AU
EAP613(TP-Link|UN|AX1800-D):1.0 JP,CA,KR,AU
EAP615-Wall(TP-Link|UN|AX1800-D):1.0 RU,EG,CA,JP,KR,AU
EAP615-WE(TP-Link|UN|AX1800-D):1.0 JP
This tplink-safeloader-support.patch worked for me, but I don't know it it breaks installation on devices with earlier OEM firmware. Maybe both styles of support list can co-exist, but I didn't try that and I notice TP-Link don't do that.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running tplink-safeloader -i on the cited EAP615-WALLv1_1.2.3 and 1.5.3 OEM images, then inspect the attached tplink-safeloader-support.patch. Compare how both SupportList formats are handled and verify that the resulting factory.bin loads for AU firmware without breaking devices using the earlier format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100