<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Flashing DIR-300 back to original firmware</title>
	<atom:link href="http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm</link>
	<description>Dreams ∙ Passion ∙ Digital World</description>
	<lastBuildDate>Thu, 11 Mar 2010 01:46:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: shadowandy</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-13928</link>
		<dc:creator>shadowandy</dc:creator>
		<pubDate>Thu, 25 Jun 2009 01:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-13928</guid>
		<description>Velsa,

Make sure you are uploading dlink&#039;s firmware through the emergency page. It doesn&#039;t accept other type of firmwares.</description>
		<content:encoded><![CDATA[<p>Velsa,</p>
<p>Make sure you are uploading dlink&#8217;s firmware through the emergency page. It doesn&#8217;t accept other type of firmwares.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Velsas</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-13925</link>
		<dc:creator>Velsas</dc:creator>
		<pubDate>Wed, 24 Jun 2009 20:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-13925</guid>
		<description>didn&#039;t help</description>
		<content:encoded><![CDATA[<p>didn&#8217;t help</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shadowandy</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-13901</link>
		<dc:creator>shadowandy</dc:creator>
		<pubDate>Wed, 24 Jun 2009 03:42:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-13901</guid>
		<description>Velsas,

Try using IE6 to upload the firmware on the emergency page.</description>
		<content:encoded><![CDATA[<p>Velsas,</p>
<p>Try using IE6 to upload the firmware on the emergency page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Velsas</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-13896</link>
		<dc:creator>Velsas</dc:creator>
		<pubDate>Tue, 23 Jun 2009 18:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-13896</guid>
		<description>hi,
First of all sorry for my Eng.
I was trying to write dd-wrt soft to my dir-300. After doing this:

RedBoot&gt; load ap61.ram 
Using default protocol (TFTP) 
Entry point: 0×800410bc, address range: 0×80041000-0×800680d8 
RedBoot&gt; go
DD-WRT&gt; fconfig -i 
Initialize non-volatile configuration - continue (y/n)? y 
Run script at boot: false 
Use BOOTP for network configuration: true 
Default server IP address: 
Console baud rate: 9600 
GDB connection port: 9600 
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 0×80ff0000-0×81000000 at 0xbffe0000: . 
DD-WRT&gt; fis init 
About to initialize [format] FLASH image system - continue (y/n)? y 
*** Initialize FLASH Image System 
… Erase from 0xbffe0000-0xbfff0000: . 
… Program from 0×807f0000-0×80800000 at 0xbffe0000: . 
DD-WRT&gt; ip_address -h 192.168.1.2 
Default server: 192.168.1.23 
DD-WRT&gt; load -r -b %{FREEMEMLO} ap61.rom 
Using default protocol (TFTP) 
Raw file loaded 0×80080000-0×800a8717, assumed entry at 0×80080000
DD-WRT&gt; fis create -l 0x30000 -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&gt; reset

My router does not restart ant I restart it manualy, after this, then trying to log in by IP 192.168.1.2 I see blank window, no DD-WRT command line. I tried to repeat everything, but the result:

RedBoot&gt; load ap61.ram
Using default protocol (TFTP)
Entry point: 0x800410bc, address range: 0x80041000-0x800680d8
RedBoot&gt; go
[fload] execution fail! [go] abort...

Then I tried to restore my original firmwire:

RedBoot&gt; load -r -b %{FREEMEMLO} shadowandy_board_config.bin
Using default protocol (TFTP)
Raw file loaded 0x80036400-0x800463ff, assumed entry at 0x80036400
RedBoot&gt; fwrite -f 0xbfff0000 -b 0x80036400 -l 0x10000 -e 0x80036400
About to write image into flash - continue (y/n)? y
... Erase from 0xbfff0000-0xc0000000: .
... Program from 0x80036400-0x80046400 at 0xbfff0000: .
update image info..
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbfff0000-0xbfffffff: .
... Program from 0x80036400-0x80046400 at 0xbfff0000: .
RedBoot&gt; reset

And that’s all, it doesn’t restart and I can do nothing. There can be the problem, I tried averything I find in this page. I also tried to restore firmwire by emergency page, but then I press UPLOAD it stops responding.
P.S. wire is connected in WAN port, LAN ports are not responding. I hope you can help</description>
		<content:encoded><![CDATA[<p>hi,<br />
First of all sorry for my Eng.<br />
I was trying to write dd-wrt soft to my dir-300. After doing this:</p>
<p>RedBoot&gt; load ap61.ram<br />
Using default protocol (TFTP)<br />
Entry point: 0×800410bc, address range: 0×80041000-0×800680d8<br />
RedBoot&gt; go<br />
DD-WRT&gt; fconfig -i<br />
Initialize non-volatile configuration &#8211; continue (y/n)? y<br />
Run script at boot: false<br />
Use BOOTP for network configuration: true<br />
Default server IP address:<br />
Console baud rate: 9600<br />
GDB connection port: 9600<br />
Force console for special debug messages: false<br />
Network debug at boot time: false<br />
Update RedBoot non-volatile configuration &#8211; continue (y/n)? y<br />
… Erase from 0xbffe0000-0xbfff0000: .<br />
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .<br />
DD-WRT&gt; fis init<br />
About to initialize [format] FLASH image system &#8211; continue (y/n)? y<br />
*** Initialize FLASH Image System<br />
… Erase from 0xbffe0000-0xbfff0000: .<br />
… Program from 0×807f0000-0×80800000 at 0xbffe0000: .<br />
DD-WRT&gt; ip_address -h 192.168.1.2<br />
Default server: 192.168.1.23<br />
DD-WRT&gt; load -r -b %{FREEMEMLO} ap61.rom<br />
Using default protocol (TFTP)<br />
Raw file loaded 0×80080000-0×800a8717, assumed entry at 0×80080000<br />
DD-WRT&gt; fis create -l 0&#215;30000 -e 0xbfc00000 RedBoot<br />
An image named ‘RedBoot’ exists &#8211; continue (y/n)? y<br />
… Erase from 0xbfc00000-0xbfc30000: …<br />
… Program from 0×80080000-0×800a8718 at 0xbfc00000: …<br />
… Erase from 0xbffe0000-0xbfff0000: .<br />
… Program from 0×807f0000-0×80800000 at 0xbffe0000: .<br />
DD-WRT&gt; reset</p>
<p>My router does not restart ant I restart it manualy, after this, then trying to log in by IP 192.168.1.2 I see blank window, no DD-WRT command line. I tried to repeat everything, but the result:</p>
<p>RedBoot&gt; load ap61.ram<br />
Using default protocol (TFTP)<br />
Entry point: 0&#215;800410bc, address range: 0&#215;80041000-0&#215;800680d8<br />
RedBoot&gt; go<br />
[fload] execution fail! [go] abort&#8230;</p>
<p>Then I tried to restore my original firmwire:</p>
<p>RedBoot&gt; load -r -b %{FREEMEMLO} shadowandy_board_config.bin<br />
Using default protocol (TFTP)<br />
Raw file loaded 0&#215;80036400-0&#215;800463ff, assumed entry at 0&#215;80036400<br />
RedBoot&gt; fwrite -f 0xbfff0000 -b 0&#215;80036400 -l 0&#215;10000 -e 0&#215;80036400<br />
About to write image into flash &#8211; continue (y/n)? y<br />
&#8230; Erase from 0xbfff0000-0xc0000000: .<br />
&#8230; Program from 0&#215;80036400-0&#215;80046400 at 0xbfff0000: .<br />
update image info..<br />
Update RedBoot non-volatile configuration &#8211; continue (y/n)? y<br />
&#8230; Erase from 0xbfff0000-0xbfffffff: .<br />
&#8230; Program from 0&#215;80036400-0&#215;80046400 at 0xbfff0000: .<br />
RedBoot&gt; reset</p>
<p>And that’s all, it doesn’t restart and I can do nothing. There can be the problem, I tried averything I find in this page. I also tried to restore firmwire by emergency page, but then I press UPLOAD it stops responding.<br />
P.S. wire is connected in WAN port, LAN ports are not responding. I hope you can help</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shadowandy</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-13725</link>
		<dc:creator>shadowandy</dc:creator>
		<pubDate>Fri, 12 Jun 2009 15:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-13725</guid>
		<description>NeXuS,

I see. It seems that some DIR-300 requires me to hold on to the reset. Well, it is also logical that a DIR-300 without firmware will halt at the emergency web-server stage.

Thanks for the insight. :)</description>
		<content:encoded><![CDATA[<p>NeXuS,</p>
<p>I see. It seems that some DIR-300 requires me to hold on to the reset. Well, it is also logical that a DIR-300 without firmware will halt at the emergency web-server stage.</p>
<p>Thanks for the insight. <img src='http://www.shadowandy.net/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NeXuS</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-13724</link>
		<dc:creator>NeXuS</dc:creator>
		<pubDate>Fri, 12 Jun 2009 11:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-13724</guid>
		<description>Hi Andy, I just wanted to thank you and also to signal one thing:

after flashing the board config back you say to reboot and hold to reset button for 30 seconds. It did not work for me. In order to get to the emergency web-server I had to do a normal boot, without the reset button pressed.</description>
		<content:encoded><![CDATA[<p>Hi Andy, I just wanted to thank you and also to signal one thing:</p>
<p>after flashing the board config back you say to reboot and hold to reset button for 30 seconds. It did not work for me. In order to get to the emergency web-server I had to do a normal boot, without the reset button pressed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shadowandy</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-12680</link>
		<dc:creator>shadowandy</dc:creator>
		<pubDate>Tue, 19 May 2009 13:52:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-12680</guid>
		<description>Ant1][r1st,

Make sure your system IP is correct. The time you have to telnet to the DIR-300 during boot up is little.</description>
		<content:encoded><![CDATA[<p>Ant1][r1st,</p>
<p>Make sure your system IP is correct. The time you have to telnet to the DIR-300 during boot up is little.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roy</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-4#comment-12675</link>
		<dc:creator>roy</dc:creator>
		<pubDate>Tue, 19 May 2009 12:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-12675</guid>
		<description>Man...u &#039;r really somethin...thumbs up 4 u..!!!.....</description>
		<content:encoded><![CDATA[<p>Man&#8230;u &#8216;r really somethin&#8230;thumbs up 4 u..!!!&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ant1][r1st</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-3#comment-12332</link>
		<dc:creator>Ant1][r1st</dc:creator>
		<pubDate>Tue, 12 May 2009 01:35:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-12332</guid>
		<description>*When i ping router, connected trought WAN, i just get
&quot;ping: sendto: No route to host&quot; or
&quot;ping: sendto: Host is down&quot;</description>
		<content:encoded><![CDATA[<p>*When i ping router, connected trought WAN, i just get<br />
&#8220;ping: sendto: No route to host&#8221; or<br />
&#8220;ping: sendto: Host is down&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ant1][r1st</title>
		<link>http://www.shadowandy.net/2007/10/flashing-dir-300-back-to-original-firmware.htm/comment-page-3#comment-12331</link>
		<dc:creator>Ant1][r1st</dc:creator>
		<pubDate>Tue, 12 May 2009 01:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.shadowandy.net/wp/2007/10/flashing-dir-300-back-to-original-firmware-1764.htm#comment-12331</guid>
		<description>I&#039;m stuck on the first part of your guide. I can&#039;t telnet to 192.168.1.1, port 9000. I have tryed all WAN/LAN ports, different scripts from ddwrt forum, 30/30/30 resets... No success. I just can telnet to 23 port, when the ddwrt are fully loaded(( 
*I have flashed to ddwrt using your guide..
**Sorry for my eng</description>
		<content:encoded><![CDATA[<p>I&#8217;m stuck on the first part of your guide. I can&#8217;t telnet to 192.168.1.1, port 9000. I have tryed all WAN/LAN ports, different scripts from ddwrt forum, 30/30/30 resets&#8230; No success. I just can telnet to 23 port, when the ddwrt are fully loaded((<br />
*I have flashed to ddwrt using your guide..<br />
**Sorry for my eng</p>
]]></content:encoded>
	</item>
</channel>
</rss>
