Gargoyle Forum

mix wrote:I stand by my original comments then, the poster flashed the firmware to the wrong block device. Usually you get an error message when the block device doesn't exist. I have no idea how/why mtd thinks it found the device and started to write it, other than maybe erasing a non existent device actually creates one. The openwrt wiki that was linked to contains some info about doing a tftp recovery, and how you only have a 4 second window and need to act fast to do it. This is the best bet for recovery assuming the flash memory isn't completely hosed.

Yes, it will not do anything, if the destination does not exist, so if it did not exist, should nothing have happened.
But checking dd-wrt, it looks like it may be using linux as its partition: http://www.dd-wrt.com/wiki/index.php/Re ... _Bad_Flash
And as dd-wrt was the original firmware, should the partition of dd-wrt be used.

You think dd-wrt renames the "firmware" block device to "linux" for atheros? That might be interesting.

mix wrote:You think dd-wrt renames the "firmware" block device to "linux" for atheros? That might be interesting.

I have no idea, I do not know dd-wrt.

mtd0: 00020000 00010000 "u-boot"
mtd1: 00140000 00010000 "kernel"
mtd2: 00690000 00010000 "rootfs"
mtd3: 001d0000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "art"

Are going to be your most important parts...

U-Boot - you mess with that - your router IS NOT booting
Messing with this will result in a true brick and only recovery is
to un-solder the chip and flash it in a flashing device.

ART - DO NOT mess with this data area either.
I think its Atheros Radio Test - something like that
It stores the radio info for your router in this area
Mess with it and wireless goes bye-bye for good - dump the router
or use it as a LAN switch only from now on.

I think its part of DD-WRT where it converts things to the "linux"
name/area - buffalo might use "firmware" for their defaults.

I don't believe it matters what its called as long as the device
knows whether to read from linux or firmware

-------------------

But anyway - your router is recoverable via Serial recovery.

http://scarygliders.net/2010/02/23/hack ... -hp-g300n/

Read scarygliders - the WHOLE thing - very good info on the page
Ignore the parts about the Japanese version, the rest of the info
applies to all WZR-HP-G300NH's

Yuck, dd-wrt and openwrt do have different mtd partitions. What a mess. http://www.dd-wrt.com/phpBB2/viewtopic.php?p=482188

Looks like DoesItMatter has seen this before...

I'm not having much luck with TFTP either. I just tried to TFTP the original DD-WRT Pro image from Buffalo onto the router. No Go. Just times out.
Looking at DMESG I see the connection go up and down a couple of times.

I could really use some pointers here, detailed instructions would be better. I'd rather not have a bricked router.

Thanks!
Statik

dmesg... So wait a second, you have a working linux install. You can ssh or telnet in?

Linux on PC, not on router. Router, when booting, goes to solid (not blinking) red DIAG led almost immediately. On my PC, when I boot the router, I get connected/disconnected messages about 3 times. Gotta be a way to unbrick this .. .

Statik wrote:...
Gotta be a way to unbrick this .. .

try to have a look: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=87579