how to upgrade EA4500 from Chaos Calmer 15.05.1 to latest trunk
i used candyhouse project to flash it before and in LUCI i can't use flash new firmware this message appeared to me:
Sorry, there is no sysupgrade support present; a new firmware image must be flashed manually. Please refer to the OpenWrt wiki for device specific install instructions.
please help
also i don't know how i can return to stock firmware
Topic: EA4500 how to upgrade from Chaos Calmer 15.05.1 to latest trunk
The content of this topic has been archived on 28 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
Page 1 of 1
i would also like some advice on this before i flash..
Like the error message says, Openwrt wiki for your device offers more info:
https://wiki.openwrt.org/toh/linksys/ea … stallation
Based on that wiki and later source commits to Openwrt trunk, it looks like there is no sysupgrade support on 15.05.1, but the current trunk has that support.
https://wiki.openwrt.org/toh/linksys/ea … k_firmware
Based on wiki, your router seems to have two copies of the firmware. Manually breaking the boot three times (but cutting power) should force the bootloader to swich to the old Linksys firmware...
Method 2: This works too if you had flashed a firmware image from the stock Linksys web interface.
Cut the power to the router while the router is booting up. The router white LED shall blink rapidly and that's when you cut the power–inducing a failed boot. After 3 failed boots, the EA4500 then boots from the backup partition and reverts back to its Linksys firmware.
i test this method but nothing happened and still the firmware is CC
Trueplayer wrote:
i test this method but nothing happened and still the firmware is CC
hmm...is it possible when you have flashed your ea4500 from stock linksys to candyhouse cc, you had flashed both the primary and alternate firmware partitions to cc? perhaps that would help explain why after 3 induced failed reboots your router is still on the cc firmware since neither of the dual firmware layout has a stock linksys firmware.
i'm not familiar with the candyhouse project but a quick search had led me to http://www.wolfteck.com/projects/candyhouse/openwrt/. claudio leite has made a comment and you should read it yourself http://www.wolfteck.com/projects/candyh … 2351050026 on flashing back to linksys firmware. i surmise you flash back to the linksys firmware directly from candyhouse cc?? i would suggest choosing the linksys classic.
i have tested the following:
flashed from linksys cloud to linksys classic -- success.
flashed from linksys classic to dd trunk -- success.
flashed from dd trunk to linksys classic -- success.
induced 3 failed boots from dd trunk to linksys classic -- success.
induced 3 failed boots from linksys classic to dd trunk -- success.
if you are successful in flashing from candyhouse cc to linksys classic, please share your results back in this thread so others may learn and the ea4500 wiki can be updated. good luck.
now after i put this two command the router is totally bricked and i can't access even with my candyhouse usb
fw_setenv auto_recovery yes
fw_setenv boot_part 2
Trueplayer wrote:
now after i put this two command the router is totally bricked and i can't access even with my candyhouse usb
wait, instead of flashing a stock linksys ssa firmware image from the candyhouse cc, you execute these u-boot commands?
fw_setenv auto_recovery yes
fw_setenv boot_part 2hmm... why?
Actually i don't know why and now i can't access the candyhouse also i don't know how i can use tftp there is no step by step doc
please help, the router is dead now and i used tftp client but no response
(Last edited by Trueplayer on 12 Apr 2016, 06:57)
Trueplayer wrote:
please help, the router is dead now and i used tftp client but no response
i hate to break this to you but it appears you have inadvertently modified the bootloader environment and you are now looking at fixing the environment variables via serial console.
There is no way except serial
Trueplayer wrote:
There is no way except serial
you can try inducing at least 3 failed reboots to see if you have any partition left with a working firmware. you basically cut the power when the white LED starts to flicker.
wrtboy wrote:
Trueplayer wrote:There is no way except serial
you can try inducing at least 3 failed reboots to see if you have any partition left with a working firmware. you basically cut the power when the white LED starts to flicker.
i did it i cut off the power when it was start flickering but nothing happened, i have RJ45 DB9 Cisco console cable it will works if i connect it to the lan or wan port or not and if it is not what i need to make a serial connection and what is the simplest way with EA4500 ?
Trueplayer wrote:
i have RJ45 DB9 Cisco console cable
the rj45 db9 cable won't work. you will need an usb ttl cable and solder the appropriate wire leads (rx, tx, and ground) to the J5 serial port. this involves taking the ea4500 housing apart so you can reach the board serial port. whatever you do, ensure you do not use the red wire (vcc).
I purchased cable like that http://www.amazon.co.uk/Adafruit-USB-TT … B00KAE2EL4
But i don't know how i can hold it or connect it to the board do i need something else bcz the board is flat
you will need to solder the appropriate wires to the board. here's a pic from the ea3500 wiki to give you an idea but don't follow the wiring on this picture because i think something looks wrong when the red wire (vcc) is soldered to the serial (rx). others reading this thread can also weigh in.
How i can solder it there is black header in this wires i need to remove it or wht
yes you will have to cut off the black ttl pin connectors for the wires you need to solder. make sure you do not use the red wire (power). all you need is to solder the green (rx), white (tx), and black (gnd) to the board J5 serial port.
How i can solder it wht tools i need, i need a solder pump or not?
Please if u have step by step document how i can sold the wires?
now i solder it but my mac os x 10.11 can not detect the usb i will try to use windows now
Also in windows 7 is not working, there is any help?
Trueplayer wrote:
Also in windows 7 is not working, there is any help?
you mean win7 failed to detect the usb ttl cable? you should contact the vendor who sold you the cable and find out what driver is needed for win7 for it to work.
wrtboy wrote:
Trueplayer wrote:Also in windows 7 is not working, there is any help?
you mean win7 failed to detect the usb ttl cable? you should contact the vendor who sold you the cable and find out what driver is needed for win7 for it to work.
Yes with message device is not recognized
The discussion might have continued from here.
Page 1 of 1