1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

verify if I bricked it - Buffalo WHR-HP-G54 / Shibby tomato-K26-1.28.RT-MIPSR2-102-Mini.trx

Discussion in 'Tomato Firmware' started by chichow, Nov 29, 2012.

  1. chichow

    chichow Serious Server Member

    Can you guys help me verify if I've bricked it?

    Going from stock buffalo firmware.
    model: Buffalo WHR-HP-G54 /
    Shibby tomato-K26-1.28.RT-MIPSR2-102-Mini.trx

    Via OS X, Linux, and Other Unix-based OS's
    Warning: Be aware that Buffalo only has encrypted firmwares on their web site. You will not be able to revert back to Buffalo's firmware without an unencrypted version of their firmware.
    The following is for an initial install on a Buffalo router. If you're already using a third-party firmware or just upgrading a Tomato firmware, try uploading any of the .bin files from the GUI.
    1. Plug your computer directly to the router. This will not work over a wireless connection.
    2. Push the reset button for at least 30 seconds to reset the configuration.
    3. Unplug power to the router and plug it back in after at least 10 seconds.
    4. Set your computer's ethernet card settings to: IP=, mask=, gateway=
    5. Open two terminal windows.
      • In the first one, type and execute this: ping
      • You should now be continually pinging the router.
    6. Unplug power to the router. The pings should stop returning now.
    7. In the second window, cd to the directory in which your firmware is located. Then execute the following:
      rexmt 1
      connect Even though the router is still powered down, tftp doesn't actually "connect" when you execute the connect command. Instead, it merely stores the address away until needed.
    8. Still in the second terminal window, type the following but do not execute yet:
      • put tomato.trx
    9. Plug the router back in. The moment you see pings coming across in the first terminal window, execute the put code.trx command you prepared in the second terminal window. If you see a successful transfer, leave the router alone for at least 2 minutes, then unplug the power, wait 10 seconds and plug it back in.
    10. Reset your computer's ethernet card settings back to use DHCP. You can also manually enter the following settings: IP=, mask=, gateway=
    never get anything from this point.

    anything else to try? before I learn how to build a JTAG cable?

  2. lefty

    lefty Networkin' Nut Member

    Not that i can think of, 2 minutes in my opinion is not log enough to wait on flashing, i always give atleast 5 minutes, and yes i know some units don't take the long to flash, but i still give it time to be safe even if its just sitting there waiting. I also don't think you'll need a jtag to recover this, probably just a serial connection would do as i don't think in this process that you fubar'd the CFE enough to need a jtag.

    Also out of curiosity, how are the unit's leds looking? Blinking power led by chance?
  3. lsiguy10

    lsiguy10 Addicted to LI Member


    You used the wrong firmware. DO NOT use K26 MIPSR2! Only use K26 MIPSR1 or K24 firmware only.

    I have the same router and it works fine with K26 MIPSR1 firmware. It has 1 minor bug - the wireless LED does not turn off when I disable wireless.

    You definitely bricked it. I think there is some procedure to put the router in recovery mode. I'm not 100% sure. You will have to look it up.
  4. Elanzer

    Elanzer Addicted to LI Member

  5. Hogwild

    Hogwild Networkin' Nut Member

    You DID try hitting the factory reset for 30 seconds or so, yes?

  6. chichow

    chichow Serious Server Member

    I got it back w/o the JTAG

    I first did this

    Hard Reset (aka 30/30/30 reset):

    The following procedure will clear out the NVRAM and set dd-wrt back to default values:
    • With the unit powered on, press and hold the reset button on back of unit for 30 seconds
    • Without releasing the reset button, unplug the unit and hold reset for another 30 seconds
    • Plug the unit back in STILL holding the reset button a final 30 seconds (please note that this step can put Asus devices into recovery mode...see note below!)
    This procedure should be done BEFORE and AFTER every firmware upgrade/downgrade.

    Then I did

    I discovered that my bricked Buffalo WHR-HP-G54 router during the startup phase (with the reset buttom activated for 5 sec. during a power-on sequence) always responded positive with 3-5 pings on IP:, (no matter what IP address I've set it to) before the ping again timed out. So you might try this before you open the router:
    1. Set your computers ethernet cable interface to static IP address:, Network Mask: and Gateway IP:
    2. Connect the network cable to the bricked routers LAN port 4
    3. In Windows cmd interface start a "ping -t -w 10", continuous ping every 10 milliseconds
    4. Push the reset button (located in the buttom of the router), and keep it activated
    5. Unplug the routers 5v power cable, count slowly to 5 and reconnect the power cable.
    6. Count once again slowly to 5 and release the reset buttom
    If you are lucky you will see 3-5 ping answers from your router on IP: before the ping command again start responding with the timeout message.
    If you get a positive ping response then you can succesfully use the TFTP script
    to flash your router with new software. You just have to modify the procedure and hold the reset buttom while you unplug the 5v power cable, keep the reset buttom activated, restore power after 5 seconds and release the reset buttom after another 5 seconds.

    then did another flash. yawn so tired it was like 3 am by that time

    thanks for the replies
    minimario likes this.
  7. chichow

    chichow Serious Server Member

    was solid power led only
  8. lefty

    lefty Networkin' Nut Member

    ah, glad you got it recovered.

Share This Page