Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
toh:linksys:ea4500 [2020/04/29 17:25] – added boot envs bobafetthotmailtoh:linksys:ea4500 [2023/03/21 11:26] – [Installation] insaneknight
Line 3: Line 3:
  
 The Linksys EA4500 and E4200 v2 share identical hardware. The Linksys EA4500 and E4200 v2 share identical hardware.
-OEM source code available at: [[http://support.linksys.com/en-us/gplcodecenter]]+OEM source code available at: [[https://www.linksys.com/us/support-product?pid=01t80000003K7iqAAC]]
  
 ===== Supported Versions ===== ===== Supported Versions =====
Line 19: Line 19:
 | E4200 v2        |  October 2011  |  01C106  | Trunk (as of [[https://dev.openwrt.org/changeset/47458|r47458]]) | -                      | | E4200 v2        |  October 2011  |  01C106  | Trunk (as of [[https://dev.openwrt.org/changeset/47458|r47458]]) | -                      |
  
 +:!: **Caution:** **WPA3 WILL NOT WORK ON THESE DEVICES in 21.02.0** if you select WPA3, wireless will error out and not work. 
 +See: https://forum.openwrt.org/t/kirkwood-linksys-ea4500-openwrt-21-02-0-rc1-wifi-problems/95739/11 for more details.
  
 :!: **Caution:** The wireless seems to have problems with WiFi-stability on connections to certain client chipsets, e.g. Apple-devices. :!: **Caution:** The wireless seems to have problems with WiFi-stability on connections to certain client chipsets, e.g. Apple-devices.
Line 49: Line 51:
 ---- ----
  
 +For the installation guide for EA4500 v3, please go to [[toh:linksys:ea4500_v3|its own page]].
  
 The EA4500 has a dual firmware layout:  working and backup partitions.  It boots from the working partition in normal operation.  Firmware flashes occur on the backup partition and the EA4500 shall reboot from the backup partition following from a firmware flash.  The backup partition becomes the new working partition when the reboot was successful.  The former working partition becomes the new backup partition. The EA4500 has a dual firmware layout:  working and backup partitions.  It boots from the working partition in normal operation.  Firmware flashes occur on the backup partition and the EA4500 shall reboot from the backup partition following from a firmware flash.  The backup partition becomes the new working partition when the reboot was successful.  The former working partition becomes the new backup partition.
Line 58: Line 61:
 {{page>meta:infobox:attention_trunk&noheader&nofooter&noeditbtn}} {{page>meta:infobox:attention_trunk&noheader&nofooter&noeditbtn}}
  
-As of [[https://dev.openwrt.org/changeset/47458|r47458]] both EA4500 and E4200 v2 are fully supported. These boards are identified by the codename "**Viper**."  The ''**factory.bin**'' image can be flashed directly from the Linksys web interface. Upgrading between OpenWrt images is accomplished with the ''**sysupgrade.tar**'' image.+As of [[https://dev.openwrt.org/changeset/47458|r47458]] both EA4500 and E4200 v2 are supported EXCEPT FOR WPA3, **WPA3 WILL NOT WORK ON THESE DEVICES**. These boards are identified by the codename "**Viper**."  The ''**factory.bin**'' image can be flashed directly from the Linksys web interface. Upgrading between OpenWrt images is accomplished with the ''**sysupgrade.tar**'' image.
  
 Prebuilt trunk snapshots offer the **most straightforward** installation and they are available now: [[https://downloads.openwrt.org/snapshots/trunk/kirkwood/generic/]] Prebuilt trunk snapshots offer the **most straightforward** installation and they are available now: [[https://downloads.openwrt.org/snapshots/trunk/kirkwood/generic/]]
Line 110: Line 113:
  
 Now in booted OpenWrt, we need to flash OpenWrt into NAND. You need to get the network working first. Then you do: Now in booted OpenWrt, we need to flash OpenWrt into NAND. You need to get the network working first. Then you do:
-''+<code>
 # cd /tmp # cd /tmp
 # wget http://yourserver/openwrt-kirkwood-ea4500-rootfs.ubi # wget http://yourserver/openwrt-kirkwood-ea4500-rootfs.ubi
Line 118: Line 121:
 # mtd erase kernel # mtd erase kernel
 # mtd write openwrt-kirkwood-ea4500-uImage kernel # mtd write openwrt-kirkwood-ea4500-uImage kernel
-''+</code>
  
 After this you reboot the device, break u-boot again and set u-boot to boot OpenWrt from NAND: After this you reboot the device, break u-boot again and set u-boot to boot OpenWrt from NAND:
-''+<code>
 Viper>> setenv owrt_bootargs_root ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw Viper>> setenv owrt_bootargs_root ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs rw
 Viper>> setenv owrt_boot nand read.e \${loadaddr} 0x200000 0x200000 \; setenv bootargs \$(console) \$(owrt_bootargs_root) \; bootm \${loadaddr} Viper>> setenv owrt_boot nand read.e \${loadaddr} 0x200000 0x200000 \; setenv bootargs \$(console) \$(owrt_bootargs_root) \; bootm \${loadaddr}
Line 127: Line 130:
 Viper>> setenv auto_recovery no Viper>> setenv auto_recovery no
 Viper>> saveenv Viper>> saveenv
-''+</code>
  
-=== Installation without Serial ===+=== Older builds (deprecated):  Installation without Serial ===
  
 There is another way to Flash your device, without using a serial connection. There is another way to Flash your device, without using a serial connection.
Line 203: Line 206:
  
 ===== Back to the original stock firmware ===== ===== Back to the original stock firmware =====
-:!: **Caution:** Going back to the original stock firmware can be tricky on recent builds of OpenWrt.  Therefore, you should always **flash from the working Linksys partition only** if you want to be able to skip the following steps.  [[https://forum.openwrt.org/t/back-to-stock-factory-firmware-linksys-e4200-v2-openwrt-fw-to-linksys-fw/31570|See Forum]]+:!: **Caution:** Going back to the original stock firmware is impossible directly via OpenWrt (versions >=18.06).  Therefore, you should always **flash from the working Linksys partition only** if you want to be able to skip the following steps.  [[https://forum.openwrt.org/t/back-to-stock-factory-firmware-linksys-e4200-v2-openwrt-fw-to-linksys-fw/31570|See Forum]]
  
-**Generic method**: Probably the most generic way to go back to the stock firmware.+==== SSH method (OpenWrt >=18.06 and LEDE 17.01) ====  
 +Probably the most generic way to go back to the stock firmware. You can skip the downgrade to LEDE 17.01 if you already are running it.
  
   * On your workstation computer:   * On your workstation computer:
Line 215: Line 219:
       * Download [[http://downloads.linksys.com/downloads/firmware/1224692441473/FW_EA4500_2.1.41.164606.img.zip|EA4500v1 Linksys stock firmware 2.1.41.164606]]       * Download [[http://downloads.linksys.com/downloads/firmware/1224692441473/FW_EA4500_2.1.41.164606.img.zip|EA4500v1 Linksys stock firmware 2.1.41.164606]]
       * Extract the file ''FW_EA4500_2.1.41.164606.img'' from this archive on your workstation       * Extract the file ''FW_EA4500_2.1.41.164606.img'' from this archive on your workstation
-  * Connect the workstation using a cabled connection to the router and ensure that your workstation is configured as DHCP client +    * Connect the workstation using a cabled connection to the router and ensure that your workstation is configured as DHCP client 
-  * On your workstation using SCP, copy ''lede-17.01.4-kirkwood-linksys-viper-squashfs-sysupgrade.tar'' to /tmp on your router +  * Downgrade to LEDE: 
-  * On your router using SSH, issue the command ''sysupgrade -F -n /tmp/lede-17.01.4-kirkwood-linksys-viper-squashfs-sysupgrade.tar'' +    * On your workstation using SCP, copy ''lede-17.01.4-kirkwood-linksys-viper-squashfs-sysupgrade.tar'' to /tmp on your router 
-  * After a while, your router should reboot on LEDE 17.01.4 +    * On your router using SSH, issue the command ''sysupgrade -F -n /tmp/lede-17.01.4-kirkwood-linksys-viper-squashfs-sysupgrade.tar'' 
-  * For the **E4200v2** +    * After a while, your router should reboot on LEDE 17.01.4 
-    * On your workstation using SCP, copy ''FW_E4200v2_2.1.41.164606.img'' to /tmp on your router +  * Revert to factory: 
-    * On your router using SSH, issue the command ''sysupgrade -F -n /tmp/FW_E4200v2_2.1.41.164606.img'' - :!: Do not use the zip archive directly, you have to extract the firmware image from it first +    * For the **E4200v2** 
-  * For the **EA4500** +      * On your workstation using SCP, copy ''FW_E4200v2_2.1.41.164606.img'' to /tmp on your router 
-    * On your workstation using SCP, copy ''FW_EA4500_2.1.41.164606.img'' to /tmp on your router +      * On your router using SSH, issue the command ''sysupgrade -F -n /tmp/FW_E4200v2_2.1.41.164606.img'' - :!: Do not use the zip archive directly, you have to extract the firmware image from it first 
-    * On your router using SSH, issue the command ''sysupgrade -F -n /tmp/FW_EA4500_2.1.41.164606.img'' - :!: Do not use the zip archive directly, you have to extract the firmware image from it first +    * For the **EA4500** 
-  * After a while, your router should reboot on the stock Linksys firmware+      * On your workstation using SCP, copy ''FW_EA4500_2.1.41.164606.img'' to /tmp on your router 
 +      * On your router using SSH, issue the command ''sysupgrade -F -n /tmp/FW_EA4500_2.1.41.164606.img'' - :!: Do not use the zip archive directly, you have to extract the firmware image from it first 
 +    * After a while, your router should reboot on the stock Linksys firmware
  
-**Method 1**:  You could try to flash a Linksys firmware image directly from the LuCI web interface (not working on E4200v2 on recent OpenWrt versions).+==== GUI method (LEDE 17.01 only!) ==== 
 +You could try to flash a Linksys firmware image (extracted from zip) directly from the LuCI web interface. 
 + 
 +:!: Do not use the zip archive directly, you have to extract the firmware image from it first
  
   * Linksys EA4500v1 cloud: http://downloads.linksys.com/downloads/firmware/1224692441473/FW_EA4500_2.1.41.164606.img.zip   * Linksys EA4500v1 cloud: http://downloads.linksys.com/downloads/firmware/1224692441473/FW_EA4500_2.1.41.164606.img.zip
Line 234: Line 243:
   * Linksys E4200v2 classic: http://downloads.linksys.com/downloads/firmware/1224693043651/FW_E4200_2.0.37.131047.zip   * Linksys E4200v2 classic: http://downloads.linksys.com/downloads/firmware/1224693043651/FW_E4200_2.0.37.131047.zip
  
-**Method 2**:  This works too if you had flashed a firmware image from the stock Linksys web interface **and** you've not done another subsequent upgrade from OpenWrt.+==== Cut the power method ==== 
 + 
 +This works too if you had flashed a firmware image from the stock Linksys web interface **and** you've not done another subsequent upgrade from OpenWrt.
  
 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.  [[https://forum.openwrt.org/viewtopic.php?pid=317288#p317288|See Forum]] 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.  [[https://forum.openwrt.org/viewtopic.php?pid=317288#p317288|See Forum]]
-==== Alternative method ==== +==== Alternative method (serial console required)==== 
-''+<code>
 $ binwalk FW_EA4500_2.1.41.164606.img $ binwalk FW_EA4500_2.1.41.164606.img
 DECIMAL       HEXADECIMAL     DESCRIPTION DECIMAL       HEXADECIMAL     DESCRIPTION
Line 246: Line 257:
 2752512       0x2A0000        JFFS2 filesystem, little endian 2752512       0x2A0000        JFFS2 filesystem, little endian
 21603204      0x149A384       Zlib compressed data, compressed, uncompressed size >= 606 21603204      0x149A384       Zlib compressed data, compressed, uncompressed size >= 606
-''+</code>
  
 Break u-boot and do: Break u-boot and do:
-''+<code>
 Viper>> tftpboot 0x2000000 FW_EA4500_2.1.41.164606.img Viper>> tftpboot 0x2000000 FW_EA4500_2.1.41.164606.img
 Viper>> nand erase 0x200000 0x1500000 Viper>> nand erase 0x200000 0x1500000
Line 255: Line 266:
 Viper>> resetenv Viper>> resetenv
 Viper>> reset Viper>> reset
-''+</code>
  
 Note that for different versions size may differ. Note that for different versions size may differ.
Line 284: Line 295:
 | wlan1            | WiFi (5GHz)          | Disabled                | | wlan1            | WiFi (5GHz)          | Disabled                |
  
-Note:  Due to the unfortunate lack of DFS support in the current mwl8k driver, there are only four available channels in the 5GHz radio: +Note:  Due to the unfortunate lack of DFS support in the current mwl8k driver, only four were made available at first and up to nine should now be available for the 5GHz radio: 
- +^ WiFi Channel          ^ Frequency ^ Transmit power ^ 
-  5180 MHz [36] (20.0 dBm) +| 36                    | 5180 MHz  20.0 dBm | 
-  5200 MHz [40] (20.0 dBm) +| 40                    | 5200 MHz  20.0 dBm | 
-  5220 MHz [44] (20.0 dBm) +| 44                    | 5220 MHz  20.0 dBm | 
-  5240 MHz [48] (20.0 dBm)+| 48                    | 5240 MHz  20.0 dBm 
 +| 149<sup>1,2</sup>     | 5745 MHz  | 20.0 dBm | 
 +| 153<sup>1,2</sup>     | 5765 MHz  | 20.0 dBm | 
 +| 157<sup>1,2</sup>     | 5785 MHz  | 20.0 dBm | 
 +| 161<sup>1,2</sup>     | 5805 MHz  | 20.0 dBm | 
 +| 165<sup>1,2</sup>     | 5825 MHz  | 20.0 dBm | 
 +<sup>1</sup> [[commit>?p=openwrt/openwrt.git;a=commit;h=672c430d6e2a1dbc5f99fd5d8d9d47e6af02ad5e|Since OpenWrt 18.06.2]]
  
 +<sup>2</sup> Unavailable on some hardware depending on regulatory region.  Make sure to select your country first, then start the WiFi interfaces; sometime these channels are only visible after the first startup.
 ==== Failsafe mode ==== ==== Failsafe mode ====
 -> [[docs:guide-user:troubleshooting:failsafe_and_factory_reset]] -> [[docs:guide-user:troubleshooting:failsafe_and_factory_reset]]
Line 1094: Line 1112:
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
-{{tag>GigabitEthernet FastEthernet 4NIC 1WNIC 5Port USB kirkwood 128RAM 128Flash ARM dual_firmware}}+{{tag>kirkwood 128Flash 128RAM GigabitEthernet FastEthernet 4NIC 1WNIC 5Port USB ARM dual_firmware}}
  • Last modified: 2024/07/13 21:37
  • by cubytus