top
logo slogan

Asistenta Online

Comenzi, Vanzari
Telephone number of  Comenzi, Vanzari +40-731.078.302
Administratie, Contabilitate
Telephone number of Administratie, Contabilitate +40-723.177.301
Suport Tehnic
Telephone number of Suport Tehnic +40-733.078.300

Newsletter

Vizitatori pe site

mod_vvisit_countermod_vvisit_countermod_vvisit_countermod_vvisit_countermod_vvisit_countermod_vvisit_counter

Online: 11
IP-ul dvs: 38.107.191.102
,

Afiseaza cosul
Cosul DVS. este gol
Restoring original firmware to EOC-5610
Evaluare utilizator: / 30
Cel mai slabCel mai bun 

Procedure for restoring original firmware for EOC-5610 device from EnGenius

After doing extensive research, i almost find no documentation about this, EnGenius giving no official support on this issue on their site, 

and the userbase from the Internet found no real solution for this.

This procedure applies to devices that had been updated to DD-WRT / OSBRIDGE / OPEN-MESH  or any other firmware compatible with EnGenius hardware.

My frustration is that, EnGenius included in the product package a flyer that shows you how to update your EOC-5610 to DD-WRT and with a small fineprint, that you have to pay a licence to use that firmware. 

Personally i consider that not being fair to the users, not to mention that there is no way to go back to your original firmware, in case that you don't like a 3rd-party firmware that you have installed on the device. 

 So, let's begin:

First, you have to enter to your device's RedBoot. The procedure seems complicated at first, but with the right tools, it's pretty easy:

 - configure your network card with ip 192.168.1.11  netmask 255.255.255.0

 - create a directory , let's say c:\engenius

 - create an empty file with notepad in that directory called redboot.bat and fill it with these commands: 

rem echo off
:start
rem ------------------------------------------------
ping 192.168.1.1 -n 1 -w 1 >NUL
IF ERRORLEVEL 1 goto start
rem putty
rem ------------------------------------------------
break
putty.exe telnet://192.168.1.1:9000 -m redboot.txt
exit

- after you saved that file, create another one named redboot.txt and fill it with this text:

^C

 - save file, and be sure that in that directory you have also putty.exe 

 - in the same directory, put the files needed for EOC-5610  found here.

- install tftpd32 and configure it to listen to 192.168.1.11 interface, and to serve files from C:\engenius

 - start the redboot.bat file. You will see a cmd window, with text scrolling fast.

 - connect the cable to your network card, and power up the device.

 - after a few seconds, a new window will pop-up, that's putty connected to your device. You will see a prompt RedBoot>

 At this point, you have successfully conected to your device. Please don't play with cables, power, etc. You may brick for good your device.

 Enter the following commands (enter only the bolded text):


RedBoot> ip_address -l 192.168.1.1 -h 192.168.1.11
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.11
RedBoot> fis init -f
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xbe030000-0xbe7e0000: ...........................................................................................................................
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
RedBoot> load -r -b %{FREEMEMLO} jffs2.ap48.bin
Using default protocol (TFTP)
Raw file loaded 0x80000400-0x803f03ff, assumed entry at 0x80000400
RedBoot> fis create -f 0xbe030000 -l 0x3f0000 -e 0 rootfs
... Erase from 0xbe030000-0xbe420000: ...............................................................
... Program from 0x80000400-0x803f0400 at 0xbe030000: ...............................................................
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
RedBoot> load -r -b %{FREEMEMLO} vmlinux.ap48.bin.l7
Using default protocol (TFTP)
Raw file loaded 0x80000400-0x800a03ff, assumed entry at 0x80000400
RedBoot> fis create -l 0xa0000 -f 0xbe420000 -e 0x8016c040 -r 0x80002000 vmlinux.bin.l7
... Erase from 0xbe420000-0xbe4c0000: ..........
... Program from 0x80000400-0x800a0400 at 0xbe420000: ..........
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .
RedBoot> load -r -b %{FREEMEMLO} cfg.jffs2
Using default protocol (TFTP)
Raw file loaded 0x80000400-0x800103ff, assumed entry at 0x80000400
RedBoot> fis create -l 0x10000 -f 0xbe4c0000 -e 0 cfg
... Erase from 0xbe4c0000-0xbe4d0000: .
... Program from 0x80000400-0x80010400 at 0xbe4c0000: .
... Erase from 0xbe7e0000-0xbe7f0000: .
... Program from 0x81fe0400-0x81ff0400 at 0xbe7e0000: .

RedBoot> fconfig

>>fis load -l vmlinux.bin.l7

>>exec -c "root=/dev/mtdblock2"

Press Enter to save the script.

RedBoot> reset

 After this, you may need to powercycle your device. If everything went ok, you should have your firmware restored to original.

 

 

 

bottom
top
Termeni Legali | Contact | PROTECTIA CONSUMATORILOR – ANPC

bottom
Copyright © 2010 wLantrade. Toate drepturile rezervate.
Powered by Dinamism si Interactivitate

Director web WooW.ro - director web, anunturi, bancuri, horoscop, jocuri Director web