PGHammer
join:2003-06-09
Accokeek, MD
clubs:
 ·Comcast
| [Firmware] Routers and Bricking: It Happens To The Best
I just finished a thread on IPv6 support in a third-party WRT54GS firmware (specifically, Sveasoft) right here and it turned basically into a rant. Because of the thread's age (largely caused by said rant), I'm not replying there. Besides, the issue I'm posting abouit affects anyone that's tried to update their router's firmware; even to a newer sanctioned release.
The subject, if you haven't guessed, is the dreaded router brick.
Yes; it happens. It happens more often than folks will admit (doubtless far often, as few of the technically adept would dare admit that it's happened to them, out of fear of embarrassment).
In fact, it has happened to me.
Not long ago, I had gotten a surprise gift, a Linksys WRT-310N router that I had originally installed for friends of our family. (The router itself I had recommended because of my experiences with the WRT54GS, which I had bought in 2005, and still have; the 310N I was gifted with was planned to replace it, with the GS becoming a backup).
I wasn't even planning (initially) to deviate from Linksys firmware. I was moving from the firmware the router originally came with to the latest version of the factory firmware (despite having run DD-WRT on my current GS for most of the last two years; I've only moved to Sveasoft's Talisman/Basic for the GS today because I will likely need IPv6 routing support and both DD-WRT and OpenWRT have issues there).
Result was a brick.
I can use it as a gigabit switch, but that's it.
I read the DD-WRT forums (remember, that's what I had been running on my GS) and saw more tales of bricking woe (and with routers of every flavor), including other issues of bricking with straight factory firmware updates (including some with routers more expensive than the 310N).
Now, it's possible that the router can be JTAGged (and debricked); however, given the low (and headed lower) price of the router, is it worth the time (and expense) of getting a JTAG package? JTAG itself is a last-ditch effort, and doesn't always work.
Therefore, relax.
Bricking happens....and sometimes, it's despite following directions to the letter. |
|
Phil
Rojo Sol
Premium
join:2001-06-11
Camarillo, CA | I guess you've tried TFTP'ing the OEM firmware back onto the router without success? Can you even ping the router? |
|
decades
join:2005-01-17
San Francisco, CA | reply to PGHammer
i bricked a linksys router and linksys is replacing it. I told them it happened while I was updating the firmware. the rep did not press me any more on that. |
|
PGHammer
join:2003-06-09
Accokeek, MD
clubs:
·Comcast
| reply to Phil
said by Phil  :I guess you've tried TFTP'ing the OEM firmware back onto the router without success? Can you even ping the router? Yup....TFTP was a nonstarter. The router is not pingable (not even a 60-60-60 reset could jumpstart it into a pingable state). |
|
Phil
Rojo Sol
Premium
join:2001-06-11
Camarillo, CA | Bummer. I've probably flashed 50+ Linksys routers and of the bad flashes I've experienced I was at least always able to re-flash via TFTP. |
|
grcore
New and Improved
join:2003-12-06
usa
| reply to PGHammer
If you have no success debricking it, send it to me and I will.
I have debricked many of these linksys routers via tftp.
The trick is to connect a 10mbs hub between the PC you are using to debrick and the router. Then use the linksys tftp application (win32) to zap a new firmware to it.
Sometimes you only have a very small window to start the tftp, and the NiC in your PC cannot react fast enough to the linksys switch ports powering up. A 10mbs hub syncs almost immediately.
g |
|
