Difference between revisions of "De Brick or Un Bricking a WRT Series Router"

De Brick or Un Bricking a WRT Series Router (view source)

Revision as of 14:10, 25 September 2021

496 bytes added , 14:10, 25 September 2021

m

→‎Special Thanks To...

Root

Bureaucrats, Interface administrators, Administrators

1,723

edits

@@ Line 1: / Line 1: @@
 This article was written for the WRT32X.  The WRT3200ACM and various iterations of the WRT1900AC, WRT1900ACS, etc. are similar.  The intent is to save a router and make it useful again.  It is not intended to facilitate recovery of settings.  Just a re-installation or installation of a working OpenWRT image.
-There are certain assumptions made (and not covered) in this article
+There are certain assumptions made (and not covered) in this article (sorry, it's for advanced users, but take heart novices or beginners, search for the below items then come back here);
+*Familiarity with the WRT series of routers, Linux, etc.
 *Serial / TTL access has been connected / configured / setup, etc. (Remember, this router has a connector for Serial / TTL output which gives full command line access to the router without needing network connectivity)
 *The U-Boot / Das Boot (Marvell Version of them that is) is functional
@@ Line 66: / Line 67: @@
 </syntaxhighlight>
-* Get the proper firmware file;
+*Get the proper firmware file;
-** Start Here: https://downloads.openwrt.org/releases/
+**Start Here: https://downloads.openwrt.org/releases/
-** Pick a firmware version version (usually the latest one, 21.02.0 as of the writing of this article)
+**Pick a firmware version version (usually the latest one, 21.02.0 as of the writing of this article)
-** Navigate through the Directories: targets, mvebu (which stands for something like Marvell Business Unit), corexa9 (the SoC technology the WRT32X is based on)
+**Navigate through the Directories: targets, mvebu (which stands for something like Marvell Business Unit), corexa9 (the SoC technology the WRT32X is based on)
-** Select the SquashFS - Factory Image - IMG Firmware File (openwrt-21.02.0-mvebu-cortexa9-linksys_wrt32x-squashfs-factory.img as of this writing)
+**Select the SquashFS - Factory Image - IMG Firmware File (openwrt-21.02.0-mvebu-cortexa9-linksys_wrt32x-squashfs-factory.img as of this writing)
-* Set the IP Address of the Router: setenv ipaddr 192.168.1.1 (the IP Address is just an example, and is also the default)
+*Set the IP Address of the Router: setenv ipaddr 192.168.1.1 (the IP Address is just an example, and is also the default)
-* Set the IP Address of the TFTP Server: setenv serveip 192.168.1.254 (the IP Address is just an example, and is also the default)
+*Set the IP Address of the TFTP Server: setenv serveip 192.168.1.254 (the IP Address is just an example, and is also the default)
-* Set the name of the firmware image file: setenv venom.img (it can be any name, including the default one from OpenWRT)
+*Set the name of the firmware image file: setenv venom.img (it can be any name, including the default one from OpenWRT)
-* Run the "installation script": run update_both_images (The update_both_images "script" is actually an environmental variable set by LinkSys in the U-Boot partition stored on the router's "disk drive" (AKA NAND memory))<br />
+*Run the "installation script": run update_both_images (The update_both_images "script" is actually an environmental variable set by LinkSys in the U-Boot partition stored on the router's "disk drive" (AKA NAND memory))
+If everything was typed correctly, then some messages begin to display loading of image, ...erase, ...write, etc.
+* When the "script" is done and the Venom>> command prompt is available, type: reset (equivalent to "reboot")
+At this point, it should reboot and start the OpenWRT firmware (which will be available on both partitions)
 ==Special Thanks To...==