EAP225 Firmware Upgrade Failed - Unable to reset using physical reset switch
Hello. I was trying to update the firmware of a TP-Link EAP225-Outdoor AP V1.1 from 5.0.9 to 5.1.0, and somewhere along the update process, the update failed. Now the AP is blinking Green-Red-Orange-SteadyGreen6seconds, and this cycles infintenly. I am unable to recover the firmware as I am unable to access the device through its MAC address.
Is there some way to restore this AP to a fully working state?
Please advise. Thank you.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@d0ugmac1 Gonna try this later and keep you posted. Thanks, sir.
- Copy Link
- Report Inappropriate Content
d0ugmac1 wrote
@d0ugmac1 Hi, Sir. As per the page you referred me to, the hardware I failed to update are, unfortunately, EAP225v1 and EAP225v3, none of which are listed in the post.
"Sometimes, your EAP might become bricked during firmware upgrade mostly due to unpredictable power failure. Through firmware recovery you will make your bricked device enter Recovery Mode to recover its firmware and work as normal.
Note: Not all EAP models support firmware recovery, only models listed below do.
EAP225v5, EAP245v3/v4, EAP265HDv1, all 802.11AX EAP. All models support webpage method, EAP245v3 and EAP265HDv1 support TFTP as well."
But I did try the solution to no avail. Can we send these hardware to TP-Link to have them reset it? Do TP-Link Employees monitor this page?
- Copy Link
- Report Inappropriate Content
Hey sorry to hear there wasn't a quick fix. I will admit to not having bricked any of my 225s just yet...
There are plenty of posts on the web about bricked 225's needing serial port access to fix, this is beyond most people as it requires fine solder work, 3V uarts etc.
The only other hope I can offer is to suggest you setup Wireshark on your laptop and see if any packets are emitted by the AP's ethernet port during power on, power on with reset held for 5s, or 30s. If no packets are captured, then it truly is bricked and the serial approach the only option.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 314
Replies: 4
Voters 0
No one has voted for it yet.