Joined: 08 Mar 2008 Posts: 239 Location: Wayne, PA
Posted: Mon May 19, 2008 0:17 Post subject: ASUS WL-500g Premium bricked by Special Version DD-WRT
I think dd-wrt.v23_micro_special_generic.bin bricked my ASUS WL-500g Premium.
I can't get into the interface via SSH or the web, and I can't get pings or TFTP it when I hold down the reset button on power up.
Fortunately I have a second pre-configured ASUS as a backup that I'm running now.
Any thoughts, Brainslayer?
jas3
p.s. I posted the above about 4 weeks ago on another thread, but didn't get a reply, thus the repost. _________________ ~Netgear WNR834Bv2~ DD-WRT v24-sp2 (12/07/09) vpn-small (SVN revision 13401M NEWD Eko)
I am not sure if it works with Asus the same but I use this small batch (found at polarcloud.com/tomato) to flash my WRT54GL/Whr-H54G.
Please, verify that Asus is also having 192.168.1.1 at boot_wait otherwise you need to adjust it accordingly.
Make sure you copy the batch to the same directory your firmware image is and replace <filename> with your image filename.
Code:
@echo off
echo ===========================================================================
echo This batch file will upload the firmware in the current directory to
echo 192.168.1.1 during the router's bootup.
echo.
echo * Set your ethernet card's settings to:
echo IP: 192.168.1.2
echo Mask: 255.255.255.0
echo Gateway: 192.168.1.1.
echo * Unplug the router's power cable.
echo.
echo Press Ctrl+C to abort or any other key to continue...
pause > nul
echo.
echo * Re-plug the router's power cable.
echo.
echo ===============================================================================
echo Waiting for the router... Press Ctrl+C to abort.
echo.
set FIND=%WINDIR%\command\find.exe
if exist %FIND% goto PING
set FIND=%WINDIR%\system32\find.exe
if exist %FIND% goto PING
set FIND=find
echo tftp -i 192.168.1.1 put <filename>
tftp -i 192.168.1.1 put <filename>
if errorlevel 1 goto PING
set FIND=
echo.
echo ===============================================================================
echo * WAIT for about 2 minutes while the firmware is being flashed.
echo * Reset your ethernet card's settings back to DHCP.
echo * The default router address will be at 192.168.1.1.
echo.
I am using fixed special standard 24 on my Asus WL-500GP. I did web interface update from non-fixed version of special 24.
To get non-fixed special 24 on the router I did this:
1. Set computer to IP 192.168.1.xxx, Subnet mask 255.255.255.0, Gateway 192.168.1.1, DNS 192.168.1.1(as shown in page 7 of user manual)
2. Unplug router for 20 seconds then boot router in recovery mode.
3. Use Asus firmware restoration tool to flash wl500g-clear-nvram.trx
4. Unplug router for 20 seconds then boot router in recovery mode.
5. Use Asus firmware restoration tool to flash wl500g-recover.trx
6. Unplug router for 20 seconds then boot router in recovery mode.
7. Use Asus firmware restoration tool to flash special standard generic renamed to .trx
This is how I always do it if I am unable to in web interface. It's probably not all necessary but it's always worked for me before.
Joined: 08 Mar 2008 Posts: 239 Location: Wayne, PA
Posted: Sat May 31, 2008 2:26 Post subject:
shizuo wrote:
I am using fixed special standard 24 on my Asus WL-500GP. I did web interface update from non-fixed version of special 24.
To get non-fixed special 24 on the router I did this:
1. Set computer to IP 192.168.1.xxx, Subnet mask 255.255.255.0, Gateway 192.168.1.1, DNS 192.168.1.1(as shown in page 7 of user manual)
2. Unplug router for 20 seconds then boot router in recovery mode.
3. Use Asus firmware restoration tool to flash wl500g-clear-nvram.trx
4. Unplug router for 20 seconds then boot router in recovery mode.
5. Use Asus firmware restoration tool to flash wl500g-recover.trx
6. Unplug router for 20 seconds then boot router in recovery mode.
7. Use Asus firmware restoration tool to flash special standard generic renamed to .trx
This is how I always do it if I am unable to in web interface. It's probably not all necessary but it's always worked for me before.
Thanks for posting that shizuo, but my problem was REALLY weird. The router would not boot into a diagnostics mode if I held in either of the buttons in the back, and it always booted with a 65.19.x.y address that I had previously assigned it no matter what. But I still couldn't get into the interface since it somehow changed my password on me.
I ended up taking the unit apart and was able to force it into diagnostic mode by powering it up while shorting out pin 16 on the NVRAM chip. That forced the unit to accept a TFTP upload, and from there I was OK.
Joined: 08 Mar 2008 Posts: 239 Location: Wayne, PA
Posted: Thu Jun 19, 2008 21:13 Post subject:
As a follow up to my own post, the WL-500G Premium version 1 (apparently a version 2 has just shown up in stores) has been running DD-WRT v24 {5/24/08} std {SVN revision 9526} SPECIAL with current uptime of > 14 days since I last rebooted it and with 0 problems so far.
CPU usage is very low, and active IP connections are peaking at around 2,000 for 31 external IPs & about 28 routers behind it * about 200 peak simultaneous users behind that in various small offices on our campus.
I've got a 4GB USB 2.0 flash drive in it for storage and a hosts file.
And it's running absolutely perfectly.
I bought a spare which I've flashed and configured in case the main unit ever suffers a hardware failure due to lighting or etc.
Kudos to Brainslayer and the DD-WRT team for their work (and to everybody at OpenWRT, those who created BusyBox, etc.) in delivering a superb v24 product.