noquest banner

How to fix a bricked Senao/Engenius EOC-5610 Wireless Access Point

How to fix a bricked Senao/Engenius EOC-5610 Wireless Access Point.

EOC-5610 is a good high power wireless outdoor access point.
Main features are:
Option to choose 802.11a or 802.11b/g working at 5GHz or 2.4GHz.
Two build in panel type antennas 13dBi in 5GHz and 5dBi in 2.4GHz.
RP-SMA connectors for external antennas.
High transmit power of 600mW.

eoc-5610 front
Access Point EOC-5610

If your access point has died and you want to revive it, if it's locked and you can not access the configuration, if no username or password is accepted when trying to login, then this article may help you.

Be warned that not all the bricked EOC-5610 could be recovered by this instructions, but we may want to give it a try.

EOC-5610 is now a discontinued product (since October 2011) replaced by EOC-5611P or/and EOC-2611P.
The instructions could be similar for other products, but not the files to use. Each model must have it's own debricking instructions.

eoc-5610 connections
Connectors on EOC-5610

EOC-5610 default configuration:

Default IP address:
Configuration URL:
user: admin
password: admin

Official  rescue software

Locator.exe is an official tool for Windows to locate the device IP and to remote reset.
Latest firmware and locator.exe software can be found at:


Standard reset procedure.

In order to reset to factory default configuration (but keeping the current firmware version), press the reset button 5 seconds by using a paper clip.

Second reset procedure.

If the standard reset procedure is not working, try this aproach:
Hold reset button while you apply power, keep pressing the button and release it after 60 seconds.

EOC-5610 inside board
Main board inside EOC-5610

Troubleshoting after the reset procedure

Web interface not accepting user and password.
Default configuration URL is:
user: admin
password: admin

When not working with default admin/admin, then try
user: (left blank)
password: admin

Still not working? try other browser (firefox, opera, ...), disable firewall/antivirus software.
Be careful, may other device in your network share the same IP adress, maybe your router?
Connect only EOC-5610 cable to your computer network card. Nothing else.
Disable any wireless card on your computer, configure manually an IP adress like netmask: on your computer wired connection. Try again the URL user and password.

EOC-5610 antennas
Left: Little 2.4GHz antenna. Right: 5 GHz antenna

Redboot, your last option

When EOC-5610 is really dead and it's not a power supply issue, we could try to upload the operating system to the AP.
We are going to describe the process in Windows XP/Vista/7 operating system.

Download putty.exe
Configure the wired network card local IP address to
Run putty.exe and set Host Name to: Port: 9000
Connect the network cable between computer and the AP, a switch can be used.
Power on the EOC-5610, now we just have 2 seconds to login into the device bootloader.
Note that this is a tricky procedure, so we will have to try more than once to acomplish it.

To be sure that the IP adress is keep a console windows pinging as:
ping -t
Then power on the AP and we'll see replies.
Note that if the firmware was changed, may be the Redboot IP adress is not, try or read the third party firmware documentation.

When the putty login is successful, we'll see a text message like: == Executing boot script in... enter ^C to abort"
Press then CTRL+C and a nice RedBoot prompt will be displayed.
Now we're in.

The TFTP server

We need to download and install a TFTP server like:
Download and install 32 or 64 bit for your system.
This is needed for uploading the firmware files to the AP.
Create a folder in C:\5610
In TFTP server set Current Directory to that folder, and Server interface to:
Copy the three files there.


Download the files here.

We return to putty and type next commands:

ip_address ‐l ‐h
fis init ‐f
load ‐r ‐b %{FREEMEMLO} jffs2.ap48.bin
fis create ‐f 0xbe030000 ‐l 0x3f0000 ‐e 0 rootfs
load ‐r ‐b %{FREEMEMLO} vmlinux.ap48.bin.l7
fis create ‐l 0xa0000 ‐f 0xbe420000 ‐e 0x8016c040 ‐r 0x80002000 vmlinux.bin.l7
load ‐r ‐b %{FREEMEMLO} cfg.jffs2
fis create ‐l 0x10000 ‐f 0xbe4c0000 ‐e 0 cfg
fis load ‐l vmlinux.bin.l7
exec ‐c "root=/dev/mtdblock2"

In about two minutes the EOC-5610 must return from the underworld and back to life again.

New life
New life

April 2012.

Use main page comments for questions.

Copyright Contact