It was a spare that I was going to integrate into my home network for convince, so this isn't a dire urgency to fix it, so ill try whatever you guys suggest. I cant get any sort of ping from it, so I think the only chance I have left is jtagging it. Please tell me there's some sort of known software fix for my stupidity. I mean someone has to of done this on accident before.
Date: 12 Dec 2010 17:34
Number of posts: 3
RSS: New posts
I have found the reset button to clear nvram often doesn't work - one reason is an nvram entry for reset_gpio.
Are the leds cycling? If so likely in a reboot cycle, with cfe only accessible for a couple of seconds in any 10.
I recommend connecting PC via a hub/switch - so no autonegotiation, set static IP and try continuous ping again. If you can get a ping, you can tftp good firmware on, possibly using Linksys tool.
I actually woke it up. It was absolute no ping, I made sure with about a half hour of unplugging/replugging and watching console. I shorted pins 16 and 17 on the flash chip (you can find directions in many recovering from a bad flash guides, ddwrt wiki helped) and it came right back to me :3 Flashed the default firmware though tftp, cleared nvram a couple times, flashed the ddwrt-mini build and then tomato from there. Whoever said this method was highly dangerous is silly.
Thanks for the help though. I just figured id post this in case anybody comes along looking for the same thing.
Oh, it did seem to brick again (got a ping with tftp though) when I tried flashing directly to tomato from the default firmware. Does the default have some sort of maximum fw upload size? Shouldnt this be mentioned in the compatibly matrix of having to go through the ddwrt-mini build method?