Upgrading to dd-wrt v24 standard

Note: This guide is for users who have “bricked” their routers while trying to upgrade to dd-wrt v24 rc7 from dd-wrt v24 rc6. For flashing to dd-wrt from the stock firmware, you can refer to the Mini Flashing Guide for DIR-300.

It seems like quite a few users have “bricked” their router while trying to upgrade to the final dd-wrt v24 from rc6. Well, the device have not really bricked, it is just that the name of the flash image has changed and hence the system cannot boot pass the redboot. Not sure if it due to the new firmware, bootp was also switched to on, causing the system to take its own sweet time to get into redboot. It took around 30 to 40 seconds before I could actually telnet in.


  1. linux.bin from dd-wrt v24
  2. TFTP Server up and running, ready to serve the required files, e.g. PumpKIN
  3. Putty (telnet client) – Chosen because it helps you to Ctrl + C

Getting into RedBoot

Getting into Redboot could be a bit tricky. You can gauge the time you need to telnet to the DIR-300 by using continuous ping (ping -t -l 1 and then turning on the power to the unit. You should see mixed replies of hardware error, ping failures and a couple of successful pings. Try timing the amount of time it takes for the first successful ping from the time you turn on the power to the unit. So you should telnet to the DIR-300 at around that point of time.

  1. Connect the network cable to your PC’s ethernet port and the WAN port of DIR-300.
  2. Configure your System IP address (static) to be
  3. Telnet to port 9000
  4. You should be greeted by the DD-WRT prompt. DD-WRT>

== Executing boot script in 2.070 seconds – enter ^C to abort
DD-WRT> ip_address -h
IP:, Gateway:
Default server:
DD-WRT> fis init
About to initialize [format] FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xbfc30000-0xbffe0000: …………………………………………………..
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> load -r -b 0x80041000 linux.bin
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x803cffff, assumed entry at 0x80041000
DD-WRT> fis create linux
… Erase from 0xbfc30000-0xbffbf000: …………………………………………………
… Program from 0x80041000-0x803d0000 at 0xbfc30000: …………………………………………………
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Enter script, terminate with empty line
>> fis load -l linux
>> exec
Boot script timeout (1000ms resolution): 3
Use BOOTP for network configuration: false
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> reset

Have fun with your dd-wrt!


Treat shadowandy!

If these step-by-step guides have been very helpful to you and saved you a lot of time, please consider treating shadowandy to a cup of Starbucks.  

21 thoughts on “Upgrading to dd-wrt v24 standard

  • May 28, 2008 at 5:02 pm

    Wow! I almost thought my device have died from upgrading to dd-wrt v24 rc7. Thanks for the guide!

  • June 21, 2008 at 11:53 am

    Hi I keep getting this error…

    Error: invalid number ” for load address

    When I try to load the linux.bin

    The command I used is the ff step
    DD-WRT> load -r -b 0×80041000 linux.bin

  • June 24, 2008 at 7:21 pm

    DD-WRT> ip_address -h
    IP:, Gateway:
    Default server:
    DD-WRT> fis init
    About to initialize [format] FLASH image system – continue (y/n)? y
    *** Initialize FLASH Image System
    … Erase from 0xbffe0000-0xbfff0000: .
    … Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
    DD-WRT> load -r -b 0×80041000 linux.bin
    ** Error: invalid number ” for load address

    Hi this is my log… I dont know why it is the problem. I was able to update into the DD-WRT firmware from the default one before and was able to use the Pumpkin.. I dont know why it wont work anymore… Any ideas?
    Could you give me specific instructions on making the Pumpkin work on this one? Thanks!

  • June 24, 2008 at 7:45 pm

    Hi I have already found out the problem

    it is with this one when i copy and paste it
    load -r -b 0×80041000 linux.bin

    the “×” written above is not the x which we will need.. Hope other people could see the idfference. hehe (× vs x)

    That solved my problem… Thanks for the guide anyway! 🙂

  • June 25, 2008 at 9:26 am


    Oh I see! Perhaps, I should place a copy of the flashing procedures in a text file so that other users could avoid this problem!


  • July 4, 2008 at 3:03 pm

    Hi thanks again! was flashing from rc6 to final and didnt realize it ‘bricked’ the router, thanks for this page for helping me to solve the problem 🙂

    Btw, for anyone else reading this, this command:
    “DD-WRT> fis create linux ”
    takes abt 5-6 mins to complete, with no progress indication whatsoever.

    I actually restarted the procedure a few times when it came to that cos I thot the router hanged or something since there was no response for a few mins. 🙂

  • July 25, 2008 at 4:21 pm

    hu hu v24 final wild in my router now… thanks for your guide.

  • July 28, 2008 at 9:08 am


    You are welcome. Glad that the guide did help. 🙂

  • August 10, 2008 at 12:11 pm

    Hi All:
    I noticed when I try to load the ram to the router, I got such information:

    RedBoot> load ap61.ram
    Using default protocol (TFTP)
    TFTP timed out 1/15
    Can’t load ‘ap61.ram’: operation timed out

    Of coz I have the tfpt server PumpKin running and have the right image in the folder,

    And then I check the ip_address of the router, I noticed the Default server is pointed to the router itself, no wonder I can’t load the ram into the router.

    RedBoot> ip_address -h
    IP:, Gateway:
    Default server:

    So, is there anyone have some idea about that? Thanks in advance!!

  • August 10, 2008 at 11:32 pm

    Have you set your computer IP to be as mentioned in the flashing guide?

  • August 11, 2008 at 7:12 pm

    Yes I did… but that doesn’t seems to help me get further

  • September 2, 2008 at 12:08 am

    now I have a DIR-300 with DD-WRT v24.
    How do i go about updating to v24 SP1?
    at the dd-wrt download page there seems to be so many files there.
    Which one to download to update a DIR-300 DD-WRT v24 to v24 SP1?
    Please help.
    Thank you so very much in advance.

  • September 4, 2008 at 12:39 pm


    Follow this guide to upgrade to the SP1

  • September 30, 2008 at 8:12 pm

    i cant´t, PUTTY make this error ” Connection Close By Remote Host ” Pls Need help realy. … ::(((((

  • September 30, 2008 at 8:18 pm


    follow instructions for “Q: My Putty window closed while flashing the firmware! What should I do?” in DIR-300 FAQ

  • September 30, 2008 at 8:29 pm

    Dear all,

    Due to the large amount of repeated questions. I’ve compiled the common problems into an FAQ.

    Check out the DIR-300 FAQ

  • December 2, 2008 at 5:47 am

    in the last step I see
    ” DD-WRT> fconfig Run script at boot: false”,
    as a true change of false?

  • December 13, 2008 at 6:12 am

    well – I am affraifd I did brick it…
    I was proceeded accoring to the guide: http://www.shadowandy.net/wp/2007/09/mini-flashing-guide-for-dir-300.htm
    got as far as telnet to the new address, port 9000
    and typing reset:
    DD-WRT> fis create -l 0×30000 -e 0xbfc00000 RedBoot
    An image named ‘RedBoot’ exists – continue (y/n)? y
    … Erase from 0xbfc00000-0xbfc30000: …
    … Program from 0×80080000-0×800a8718 at 0xbfc00000: …
    … Erase from 0xbffe0000-0xbfff0000: .
    … Program from 0×807f0000-0×80800000 at 0xbffe0000: .
    DD-WRT> reset

    but than my putty window has disconnected on its own.

    And now I cannot even ping my DIR-300
    there are no LED indicator lights indicating presence of physical link
    and ipconfig claims that LAN is “Media disconnected”

    so I have no way to telnet back to my router to finish the firware flashing procedure….

    (I tried both WAN and LAN1 ports)

    Any suggestions?

  • December 15, 2008 at 9:17 am


    It is normal for the DIR-300 to reset after using the command “reset”. You should wait for at least 30 seconds before attempting to telnet back again (as mentioned in the guide).

  • December 30, 2008 at 4:31 am

    I’ve same problem as awatral, i can wait until death, there is no response from dir-300.

Comments are closed.