Guide: Flash Linksys EA6300v1, EA6400, EA6500v2, EA6700, EA6900v1.0/1.1 with Tomato

Discussion in 'Tomato Firmware' started by monoton, Nov 15, 2017.

  1. pylsar

    pylsar Network Newbie Member

    I did everything according to the instructions from this topic for my router EA6500v2. From the information on the putty by serial port, the version of CFE has changed. Now version of CFE:
    CFE version 6.37.14.86 (r456083) based on BBP 1.0.37 for BCM947XX (32bit,SP,)
    Build Date: Wed Mar 4 08:30:18 MSK 2015 (Vortex)

    I attach a log of loading of a router after reboot!

    I do not know how to do it.

    / # nvram show | grep board | sort
    size: 32747 bytes (32789 left)
    0:boardflags2=0x00100000
    0:boardflags=0x80001200
    1:boardflags2=0x00200002
    1:boardflags3=0x0
    1:boardflags=0x30000000
    boardflags2=0x00000000
    boardflags=0x00000110
    boardnum=01
    boardrev=0x1100
    boardtype=0xF646

    I use firmware from http://tomato.groov.pl/download/K26ARM/140-MultiWAN/tomato-EA6500v2-ARM--140-AIO-64K.zip

    I can install the Freshtomato firmware tomorrow.
     

    Attached Files:

  2. txnative

    txnative Addicted to LI Member

    The cfe should be accessible by
    create a static of ip so you can monitor ping responses

    unplugging the power, hold the reset button, plug power back, start the ping on the router ip
    you should be able to check when you are able to see the response then release the button. You should be able to login into
    192.168.1.1 default ip, cfe mini web server is available for you to flash other firmware as desired. If you didn't modified it properly but i see you have it in your bootlog so that should be an issue.

    The older shibby image may work as I would've suggested to use what version was in the monoton download, then update or try out newer freshtomato-arm images as to check it there maybe a problem if any.

    The nvram size should be visible on the GUI, or know that the firmware is compile for 64k, as your last statement went update to a newer build and check if there is a problem.
     
  3. pylsar

    pylsar Network Newbie Member

    OK. I'll check tomorrow

    I see size of nvram - 64K, free - 32K (50%) on the GUI tomato.

    Regards!
     
  4. txnative

    txnative Addicted to LI Member

    Make sure to clear the nvram before/after
    you install the freshtomato firmware.
     
  5. pylsar

    pylsar Network Newbie Member

    Ok.

    By the way. Now when the router is turned on, the LED does not flash. when the router is fully loaded, the LED is on. this is normal?
     
  6. txnative

    txnative Addicted to LI Member

    There had been a change in the way the led behaves, yes this is normal for open source firmware, dd-wrt may do something different but with similar results and oem of course has their sources.
     
  7. pylsar

    pylsar Network Newbie Member

    cfe mini web server works! Through it, I first flashed against Tomato 140 firmware, and then with the firmware Freshtomato 2019.1. Full reset done before and after the firmware update. Firmware give out that my router EA6700. screenshots attached application. In general, the router works.
     

    Attached Files:

    • 1.jpg
      1.jpg
      File size:
      209.6 KB
      Views:
      7
    • 2.jpg
      2.jpg
      File size:
      257.2 KB
      Views:
      7
    • 3.jpg
      3.jpg
      File size:
      209.7 KB
      Views:
      7
  8. pylsar

    pylsar Network Newbie Member

    I install latest ddwrt firmware. And again EA6700 :))
     
  9. txnative

    txnative Addicted to LI Member

    The miss identified model needs to be reported, but with the xvortex installed you are more than able to install which ever firmware you'd like to. I see in the sources that nothing really spans to the a missed identification of this model. Congratulations anyway that you got this working, please report any other issues to the freshtomato-arm thread as this thread is for installing the linksys ea models.

    Edited: I had reported this to kille72 bitbucket. It may take till the next release to see that changed unless someone compiles an image for you to flash or if you decide to it yourself.
     
    Last edited: Apr 15, 2019
  10. pylsar

    pylsar Network Newbie Member

    I understand that in order for the firmware to see the router correctly, do I need to change CFE image again?
     
  11. txnative

    txnative Addicted to LI Member

    There is no need to do that at all now with the xvortex, unless you would like to restore the unit to its former glory oem. The xvortex it to get around the limited 32k in the linksys ea model problem either it was deliberate or not or just a problem Broadcom but now with the modified cfe, there is a mini web server to flash the unit or by gui now, reset nvram, but most of all it recognizes 64k.
     
  12. pylsar

    pylsar Network Newbie Member

    Ok. But I do not understand why before the change in firmware, Tomato's firmware determined the router correctly, but now it does not. And how can this affect the work of the router?
     
  13. pedro311

    pedro311 Networkin' Nut Member

  14. pylsar

    pylsar Network Newbie Member

    Tell me please, does the router somehow affect the fact that it is defined by firmware as 6700? This is bad? or is it just an inscription and it does not affect anything?
     
  15. txnative

    txnative Addicted to LI Member

    No it does nothing other than have a different model number, they are pretty much the same type of hardware etc.

    Edited: In photos did you erase the nvram before or after the photos posted? I see the mac addresses as I don't believe they coincide with Linksys models. Do you by chance know what the first 3 numbers xx:xx:xx: and compare them to the photo to make sure they are correct, regards.
     
    Last edited: Apr 15, 2019
  16. txnative

    txnative Addicted to LI Member

    All what has been done as far as the user and I have done are in this thread. Nothing changed in the sources pedro. model ea6500v2 it is not in the if (hw == HW_BCM4708) { of the router/shared/id.c it only has the ea6400,ea6700,ea6900 unless it's being identified somewhere else other than the Makefile?
    I don't change anything in the repo as I don't have access.
     
  17. pedro311

    pedro311 Networkin' Nut Member

    As I said, it's recognized in init.c script by correct nvram value not by id.c script.
    So change it, and forget it.

    Code:
    nvram set modelNumber=EA6500
    nvram commit
    reboot
     
    M_ars likes this.
  18. txnative

    txnative Addicted to LI Member

     
  19. pylsar

    pylsar Network Newbie Member

    these photos after full erase nvram. I do not know why this mac address 00:90:4C is taken. It is now the same in all firmware: tomato, freshtomato, ddwrt. In cfe, I entered the original mac address 48:F8:B3 from case and according to the instructions +2 +4. But I did not see these addresses anywhere during the operation of the router.

    I downloaded cfe image from the router and opened it to the cfeeditor. All settings and mac addresses correspond to what I wrote before the firmware. why then address 00:90:4C? Or is this mac address embedded in the tomato's and ddwrt firmware itself?

    I'll try to do it tomorrow on tomato firmware.

    regards
     
  20. tvlz

    tvlz LI Guru Member

    Actually it's not using the correct nvram value for the Xvortex CFE which is "model=EA6500"

    Another thing you could do for all models with Xvortex CFEs is make it clear that the Xvortex CFE is being used, is to change the "mfr = Cisco Linksys" to "mfr = Xvortex Linksys" when the nvram value "odmpid=LINKSYS" is set. (line#2932)
    EA6500-CFE.png
     
  21. pylsar

    pylsar Network Newbie Member

    Maybe in CFE "model=EA6500" to replace on "modelNumber=EA6500" ??? so that each time you reset nvram, the tomato firmware correctly identifies the model?
     
  22. ddimitrov

    ddimitrov Network Newbie Member

    ... A wrong post of mine, please ignore it.
     
    Last edited: Apr 18, 2019 at 10:43 PM
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice