Posted: Sun Mar 27, 2011 4:43 Post subject: EOC-2610 flashed with EOC-5610 firmware - Solved!
I was recently upgrading some EOC-5610 devices and today I updated multiple EOC-2610 with the latest firmware from EOC-5610 in error and now I have multiple devices bricked. They are all responding the same way. As soon as I get a reply to the ping after powering on each device, I telnet to 192.168.1.1 9000 and I get:
Connected to 192.168.1.1.
Escape character is '^]'.
== Executing boot script in 1.890 seconds - enter ^C to abort
^C
Nothing ever happens after I do "Control c" and press enter. Pressing "Control c" multiple times does nothing either. I have de-bricked various devices and am familiar with the process but no luck whatsoever with these EOC-2610's. Would really appreciate any help I can get, I about now 3 devices bricked. It's a shame Engenius does some a poor job and not prevent the device from taking the wrong firmware. BTW, all devices were running the original Engenius firmware and that is all i'm trying to get back on them.
-Mike
Last edited by mikefl on Sun Mar 27, 2011 18:02; edited 2 times in total
Posted: Sun Mar 27, 2011 7:23 Post subject: Re: EOC-2610 flashed with EOC-5610 firmware can't de-brick
Ok I am now able to get into RedBoot after much hassle (I use a Mac and run VMWARE fusion for windows junk). Anyway now i'm trying to flash the unit back to the stock firmware (which is what was on it before I bricked it) but it appears the instructions I am following are bad/old:
I have slightly different filenames than what is mentioned on the above instructions. Can somebody point me to where I can download the proper instructions and files needed for EOC-2610? Because using the instructions/files that I have, I have not accomplished anything. I still cannot access the web interface just RedBoot. Only way I could get RedBoot by the way was by using PUTTY under my vmware, would not work under the mac using telnet. Then for the TFTP server I had to run that under the mac or it would not work if I tried running it under windows (due to vmware). Thanks.
Posted: Sun Mar 27, 2011 16:53 Post subject: Re: EOC-2610 flashed with EOC-5610 firmware can't de-brick
I ended up installing dd-wrt on it and that worked. But then I wanted to go back to the stock firmware and doing that appears to have bricked the device for good. The LAN port no longer lights up on the device or work. My concern putting dd-wrt on these devices is that I don't know if the firmware is reliable or if it works well in WDS mode and then the cost of having to buy a license for each device since I now have multiple devices that I need to fix. So again my question is, is there a way to install stock firmware from RedBoot? Where can I find the instructions and files?
Is there anything else I can do to fix this bricked device since the LAN port no longer works which of course means I cannot get into RedBoot?
Posted: Sun Mar 27, 2011 17:57 Post subject: Re: EOC-2610 flashed with EOC-5610 firmware can't de-brick
I got lucky and found the correct files and the correct instructions so I was able to un-brick one of the devices back to stock firmware here is the link and instructions (I did this on a EOC-2610):
== Executing boot script in 1.990 seconds - enter ^C to abort
^C
RedBoot> ip_address -l 192.168.1.1/24 -h 192.168.1.100
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.100
RedBoot> load -r -b %{FREEMEMLO} jffs2.eoc-2610.bin
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x80430fff, assumed entry at 0x80041000
RedBoot> fis init -f
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xa8030000-0xa87e0000: .......................................... ................................................................................ .
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> fis create256 -f 0xa8030000 -l 0x3f0000 -e 0 rootfs
... Erase from 0xa8030000-0xa8420000: .......................................... .....................
... Program from 0x80041000-0x80431000 at 0xa8030000: .......................... .....................................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> RedBoot> load -r -b %{FREEMEMLO} vmlinux.ap51.bin.l7
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x800e0fff, assumed entry at 0x80041000
RedBoot> fis create256 -l 0xa0000 -f 0xa8420000 -e 0x80041798 -r 0x80041000 vmlinux.bin.l7
... Erase from 0xa8420000-0xa84c0000: ..........
... Program from 0x80041000-0x800e1000 at 0xa8420000: ..........
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> load -r -b %{FREEMEMLO} cfg.jffs2
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x80041000, assumed entry at 0x80041000
RedBoot> fis create256 -l 0x10000 -f 0xa84c0000 -e 0 cfg
... Erase from 0xa84c0000-0xa84d0000: .
... Program from 0x80041000-0x80041001 at 0xa84c0000: .
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> reset
^C
I found these instructions and the hard to find files here (it appears to also work for other models, I fear dd-wrt will remove the link):
So looks like I will be able to recover 2 out of 3 devices. It is unfortunate what dd-wrt is doing, seems like they are more interested in the commercial/profit end of these devices. I find it rather odd that after you install dd-wrt you cannot go back to stock yet it appears you can do it if you happen to install something other than dd-wrt. Lately quite a few disappointments with dd-wrt, for example on the Buffalo WZR-HP-G300NH it comes with dd-wrt pro firmware which I really like but the WDS function does not work at all, Buffalo says you have to use stock firmware due to a bug in dd-wrt, that is really poor testing from dd-wrt since one of the main features on these units is WDS.
