I've been able to compile it on Windows... But it still get the same result! It detects the processor and the flash chip, but it stalls at "[0% Flashed] 1fc00000: "
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Sep 14, 2007 0:03 Post subject:
this is the commandline i used today for recovering my unit
wrt54g -flash:cfe /noreset /nobreak /noemw _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Sep 14, 2007 0:51 Post subject:
interesting. my WRT54GV8 has a Samsung flash _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
hey i flashed the vxworks killer waited a minute tftp the dd wrt bin rebooted then tried the web gui no work no dhcp no nothing but i can still tftp it tryed it multiple times it seems like the router is rebooting because it shows the wifi signal for like 5 sec then it reboots or at least i think it reboots it dosnt reboot like my wrt54gl or wrt54g v4 were the power led blinks repeditly it turns on then after about 5 sec it shuts down wlan led turns on power led turns on after then they both turn off then the cycle begins again
First of all, thanks for all the hard work you put into this, I appreciate it.
Now, I downloaded vxworkskillerv8.bin and dd-wrt.v24_micro_wrt54gv8.bin, then I followed these instructions to the T:
Quote:
How To Flash the WRT54G v8 / WRT54GS v7
01. configure your local lan ethernet address to 192.168.1.100 and connect your local
ethernet to your WRT54Gv8/GSv7 on one of the 4 switch ports
02. plugoff the power cord from the WRT54G v8/GSv7
03. push the reset button while replugin the power cord and hold the button for about 20
seconds
04. open your browser and open http://192.168.1.1
05. use the firware upgrade dialog to flash vxworkskillerGv8.bin / vxworkskillerGSv7.bin
06. after the dialog is shown that you need to plugoff the power cord, remove the power
cord and replug it in
07. wait for about 1 - 2 minutes
08. plugoff the power cord again and replug it in.
09. enter "tftp -i 192.168.1.1 put dd-wrt.v24_micro_wrt54gv8.bin" on your local windows
console and press enter
(for linux, tftp 192.168.1.1; mode octet;put dd-wrt.v24_micro_wrt54gv8.bin)
10. the file will now be transfered to your router and be flashed. after this is done,
dd-wrt will automaticly boot and you can reach your router at http://192.168.1.1
What I have right now is a router that responds to pings, but not http requests. In addition, it doesn't reliably respond to pings. I issued ping -t 192.168.1.1 and here is a sample of the output (notice the TTL values and how they change)
Quote:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
I've tried reflashing the firmware several times, I've rebooted the device, and I followed the directions that appeared earlier to try to flash my firmware again. I've got nothing.
Also of interest is that the power light flashes on and off intermittently, it's really slow (10-15 seconds), and not very regular.
First of all, thanks for all the hard work you put into this, I appreciate it.
Now, I downloaded vxworkskillerv8.bin and dd-wrt.v24_micro_wrt54gv8.bin, then I followed these instructions to the T:
Quote:
How To Flash the WRT54G v8 / WRT54GS v7
01. configure your local lan ethernet address to 192.168.1.100 and connect your local
ethernet to your WRT54Gv8/GSv7 on one of the 4 switch ports
02. plugoff the power cord from the WRT54G v8/GSv7
03. push the reset button while replugin the power cord and hold the button for about 20
seconds
04. open your browser and open http://192.168.1.1
05. use the firware upgrade dialog to flash vxworkskillerGv8.bin / vxworkskillerGSv7.bin
06. after the dialog is shown that you need to plugoff the power cord, remove the power
cord and replug it in
07. wait for about 1 - 2 minutes
08. plugoff the power cord again and replug it in.
09. enter "tftp -i 192.168.1.1 put dd-wrt.v24_micro_wrt54gv8.bin" on your local windows
console and press enter
(for linux, tftp 192.168.1.1; mode octet;put dd-wrt.v24_micro_wrt54gv8.bin)
10. the file will now be transfered to your router and be flashed. after this is done,
dd-wrt will automaticly boot and you can reach your router at http://192.168.1.1
What I have right now is a router that responds to pings, but not http requests. In addition, it doesn't reliably respond to pings. I issued ping -t 192.168.1.1 and here is a sample of the output (notice the TTL values and how they change)
Quote:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
I've tried reflashing the firmware several times, I've rebooted the device, and I followed the directions that appeared earlier to try to flash my firmware again. I've got nothing.
Also of interest is that the power light flashes on and off intermittently, it's really slow (10-15 seconds), and not very regular.
Any thoughts (please?)
this might seem like a double post but thats exactly whats happening to me i get the exact same results as predated
I too am having the exact same problem as predated & Extibal I tried the suggestion to press the reset button while getting the ttl=100 ping return but that did not affect anything. I am still receiving the exact same results.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Fri Sep 14, 2007 7:27 Post subject:
it seems like dd-wrt gets a problem with these devices. i just have one WRT54G v8 for testing and Tornado already noted that there are some different devices around the world with a weired flash memory. i hope we find a solution for this quickly _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s