1,723
edits
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:05, 25 September 2021
, 14:05, 25 September 2021no edit summary
(Created page with "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 use...") |
m |
||
| Line 3: | Line 3: | ||
There are certain assumptions made (and not covered) in this article | There are certain assumptions made (and not covered) in this article | ||
* 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) | *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 | *The U-Boot / Das Boot (Marvell Version of them that is) is functional | ||
* A TFTP Server is available and functional on the same network as the router | *A TFTP Server is available and functional on the same network as the router | ||
== Recovery == | ==Recovery== | ||
* Enter the U-Boot command line in the three second boot pause window: Start pressing enter when you see the initial boot up message and the line that shows "MMC: mv_sdh:0" (about 2 seconds after turning the router on) | *Enter the U-Boot command line in the three second boot pause window: Start pressing enter when you see the initial boot up message and the line that shows "MMC: mv_sdh:0" (about 2 seconds after turning the router on) | ||
* Below is the typical output from a WRT32X as it boots up | *Below is the typical output from a WRT32X as it boots up | ||
<syntaxhighlight lang="text"> | <syntaxhighlight lang="text"> | ||
BootROM - 1.73 | BootROM - 1.73 | ||
| Line 66: | Line 66: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
* Get the proper firmware file; | |||
** 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) | |||
** 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) | |||
* 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 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 /> | |||
== Special Thanks To... == | ==Special Thanks To...== | ||
Usori's post was the 'starting hint': https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=311272&view=next&sid=f4fceb306811c819d84fc1c6a1d34fc0<nowiki/>(...it wasn't a step by step set of instructions from him, but he included all the command line output, which was enough of a hint, specifically the line(s) right after "MMC: mv_sdh: 0, Venom>> | Usori's post was the 'starting hint': https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=311272&view=next&sid=f4fceb306811c819d84fc1c6a1d34fc0<nowiki/>(...it wasn't a step by step set of instructions from him, but he included all the command line output, which was enough of a hint, specifically the line(s) right after "MMC: mv_sdh: 0, Venom>> | ||
== An Oddity Worth Noting == | ==An Oddity Worth Noting== | ||
It cannot be an coincidence that the WRT32X, black in color with a code name of "Venom" and a SoC from Marvell, isn't somehow named after the 2018 Marvel movie, Venom. | It cannot be an coincidence that the WRT32X, black in color with a code name of "Venom" and a SoC from Marvell, isn't somehow named after the 2018 Marvel movie, Venom. | ||