|
 
Bill_MI
Bill In Michigan
Premium,MVM
join:2001-01-03
Royal Oak, MI
 ·Comcast
| Re: [Firmware] Did I brick it? Yep, if I wanted to brick a router on purpose I'd pull the plug in the middle of flashing.
Reset button attempting to restore factory defaults... may make it better or worse with a lot of ifs.
But there is faint hope before JTAG. I never worked with a V1 but are you familiar with the tftp window that occurs during boot? It will be at HARD address 192.168.1.1. Get a static PC in this subnet and see if, during boot, ping -t 192.168.1.1 gets a reply for a few seconds. | |
|
 | |
| | |
| |
Bill_MI
Bill In Michigan
Premium,MVM
join:2001-01-03
Royal Oak, MI
·Comcast
2 edits | said by PeeWee  :I tried the ping on boot and I do get a reply that continues after boot. Does that mean it can be fixed? That doesn't sound like it. The period I mean should last only a few seconds and go away for, I want to say, 10-15 seconds. What you describe sounds like the firmware (sorta) came up.
Important - this is hard coded at address 192.168.1.1 regardless what the router is set to normally. It's easier if you're not set the same because there's no mistaking it (but the pinging machine has to be static IP to do this properly).
Is the router also set to 192.168.1.1?
I'm thinking this is all for nothing... the V1 was different. If someone knows, please jump in.
EDIT: The procedure that I've used a lot that may work:
»wiki.openwrt.org/OpenWrtDocs/Installing/TFTP
Boot code, which has no reason to be corrupt since it's not part of firmware flashing, opens a small window for tftp flashing of firmware. Any firmware can be flashed as long as it's got a valid header for the model you're flashing.
But I can't confirm the V1 can do this - I only recall some special procedures but I think they were only to get around early Linksys firmware for the V1. | |
|
|
|
|
·
