Posted: Sat Mar 20, 2010 23:17 Post subject: Buffalo firmware v1.60
Oh, I also notice that you have the v1.60 firmware file. My router rejected this file as having an "invalid format". I could ONLY get the v1.65 and v1.72 firmwares from Buffalo to work and the OpenWRT firmware.
Now the transfer starts. Instead of constantly resetting, the router stays on and flashes the diag light twice and repeats a second later. I assume in this mode, it's waiting to accept a firmware.
I still have a problem though. I get the following error after a few "send" commands.
tftp> put wzrhpg300nh-160.bin
putting wzrhpg300nh-160.bin to 192.168.11.1:wzrhpg300nh-160.bin [octet]
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
sent WRQ <file=wzrhpg300nh-160.bin, mode=octet>
received ACK <block=0>
sent DATA <block=1, 512 bytes>
received ERROR <code=0, msg=Unsupport HW>
Error code 0: Unsupport HW
Any ideas? Maybe there's a problem with the file? I might try 172 as well. 160 was always fishy because it came as a .exe that I had to move to windows to run and extract and then copy back.
Posted: Sun Mar 21, 2010 0:35 Post subject: buffalo 1.65, 1.72, openwrt on new WZR-HP-G300NH US Version
Same issue with my experiences this weekend. Buffalo 1.65, 1.72, and openwrt's snapshot work perfectly flashing via tftp.
However, the buffalo web interface under 1.72 is accepting the buffalo_to_ddwrt_webflash-EU-US.bin, progressing the flash to 100%, then endlessly cycle rebooting every 15 secs. I dont have serial access yet to see why this occurring.
Using the correct arp command and using the right firmware (1.60 DOES NOT WORK) put the router back where it was supposed to be.
My next question to those who have brought your router back from the dead is, what's next? Did you try to flash to DD-WRT again successfully? Did you flash using the "obsolete" method?
Posted: Sun Mar 21, 2010 1:10 Post subject: Life after "death"
I've tried almost every file I can find but nothing loads on the router except 1.65, 1.72 and OpenWRT. Doesn't matter which method I use: tftp or webgui.
I can always get it back to Buffalo firmware so I;ve tried many different things since "bricking" the router. Nothing seems to work.
Obviously, something is different. I don't know how others got this to work.
Glad yours is working now, even if it's only sort-of working :)
Posted: Sun Mar 21, 2010 1:22 Post subject: Re: Life after "death"
aturnbul wrote:
I've tried almost every file I can find but nothing loads on the router except 1.65, 1.72 and OpenWRT. Doesn't matter which method I use: tftp or webgui.
I can always get it back to Buffalo firmware so I;ve tried many different things since "bricking" the router. Nothing seems to work.
Obviously, something is different. I don't know how others got this to work.
Glad yours is working now, even if it's only sort-of working
Well that's disappointing... Perhaps I'll wait this out. There should be something when it becomes "official." I don't have any experience with OpenWRT and DD-WRT has been good to me for so long.
Which OpenWRT firmware did you use? This router doesn't show as supported on their site.
Posted: Sun Mar 21, 2010 1:42 Post subject: Re: Life after "death"
BDawg wrote:
aturnbul wrote:
I've tried almost every file I can find but nothing loads on the router except 1.65, 1.72 and OpenWRT. Doesn't matter which method I use: tftp or webgui.
I can always get it back to Buffalo firmware so I;ve tried many different things since "bricking" the router. Nothing seems to work.
Obviously, something is different. I don't know how others got this to work.
Glad yours is working now, even if it's only sort-of working
Well that's disappointing... Perhaps I'll wait this out. There should be something when it becomes "official." I don't have any experience with OpenWRT and DD-WRT has been good to me for so long.
Which OpenWRT firmware did you use? This router doesn't show as supported on their site.
I also rename all firmwares to *.tftp just in case(dd-wrt/openwrt: from *.bin to *.tftp, official firmware: add a .tftp extenstion), not sure if its necessary, and tftp always works for me.
Using the correct arp command and using the right firmware (1.60 DOES NOT WORK) put the router back where it was supposed to be.
My next question to those who have brought your router back from the dead is, what's next? Did you try to flash to DD-WRT again successfully? Did you flash using the "obsolete" method?
excellent news bdawg! did you use a tftp program or did you do everything from terminal?
Using the correct arp command and using the right firmware (1.60 DOES NOT WORK) put the router back where it was supposed to be.
My next question to those who have brought your router back from the dead is, what's next? Did you try to flash to DD-WRT again successfully? Did you flash using the "obsolete" method?
excellent news bdawg! did you use a tftp program or did you do everything from terminal?
Everything from terminal. I think you have to since the magic step is aliasing the router's MAC address to 192.168.11.1.
Because I'm sitting here watching my team get whipped by Kentucky by 30, I figured misery loves company, so I tried again.
Webupdate from Buffalo to DD-WRT - Failed (reboots)
TFTP bricked router using Brainslayer's file - Tranferred, but back into reboots
TFTP bricked router using 1.72 - Back to Buffalo firmware
4. Dont know if this is necessary but I copied my firmware file into the linux documents folder for easy navigating and I renamed the firmware extension to end in ".tftp".
May seem trivial to most but took me a long time to figure this out. I hope it helps.[/url]