Posted: Mon Jul 09, 2018 23:54 Post subject: Help me with my WRT 54G V8.2 bricked!
I tried to downgrade my router from 14896 to 13064, so I started on "Update Firmware"using the file "vxworkskillerGv8-v3" but it said "Update Failed" and I cliked on continue, it took me to the DD-WRT IP page, then I tried the same thing but with "vxworksrevert-Gv8-v3" and It worked, it told me that the update was sucessful and to click on continue, I retyped the IP address and appeared a message called "Management mode" and a insert file, update and cancel buttons, I couldn't skip that page so I added "dd-wrt.v24_micro_generic" file and clicked update, after that, it looks to be bricked, when I plug it, no lights turn on but ethernet and internet lights when the cables are pluged in, my internet settings shows "non identified" and "no internet". I tried to use tftp with the files on DDWRT page and the original firmware but it says that I can't connect to the host. Help!
I reconnected it hours before and Ethernet-Internet cables started to blink like 20 secods.
Last edited by electroforesis18 on Tue Jul 10, 2018 17:23; edited 2 times in total
Posted: Tue Jul 10, 2018 1:01 Post subject: Re: Help me with my WRT 54G V8.2 bricked!
electroforesis18 wrote:
I tried to downgrade my router from 14896 to 13064, so I started on "Update Firmware"using the file "vxworkskillerGv8-v3" but it said "Update Failed" and I cliked on continue, it took me to the DD-WRT IP page, then I tried the same thing but with "vxworksrevert-Gv8-v3" and It worked, it told me that the update was sucessful and to click on continue, I retyped the IP address and appeared a message called "Management mode" and a insert file, update and cancel buttons, I couldn't skip that page so I added "dd-wrt.v24_micro_generic" file and clicked update, after that, it looks to be bricked, when I plug it, no lights turn on but ethernet and internet lights when the cables are pluged in
First, why did you rerun the vxworks files when you were already running DD? That procedure is only to go from OEM to DD. Upgrade instructions are on the wiki.
Second, why were you downgrading in the first place? How long were you running 14929? If it was running fine for a while then started having issues, I'd guess it was due to failing voltage I/O capacitors (I've seen many) or a bad power supply (I've seen none). You should be able to run latest micro builds on that router (currently 36247).
C:\WINDOWS\system32>arp -s 192.168.1.1 xx-xx-xx-xx-xx-xx
The ARP entry addition failed: Access is denied.
C:\WINDOWS\system32>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.0.22: Destination host unreachable
You have to run arp from an elevated cmd.
Also, looks like your using a 192.168.0.x subnet; TFTP would use 192.168.1.1. Of course arp would workaround that, but I've never had to do anything for TFTP except set my PC IP/subnet/gateway (e.g. IP 192.168.1.7), run a continuous ping to 192.168.1.1, and use a TFTP GUI to send the firmware file as soon as I see a TTL=100 response at powerup.
Focus on the TFTP Flash wiki; the Recovery wiki is quite old. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
C:\WINDOWS\system32>arp -s 192.168.1.1 xx-xx-xx-xx-xx-xx
The ARP entry addition failed: Access is denied.
C:\WINDOWS\system32>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.0.22: Destination host unreachable
You have to run arp from an elevated cmd.
Also, looks like your using a 192.168.0.x subnet; TFTP would use 192.168.1.1. Of course arp would workaround that, but I've never had to do anything for TFTP except set my PC IP/subnet/gateway (e.g. IP 192.168.1.7), run a continuous ping to 192.168.1.1, and use a TFTP GUI to send the firmware file as soon as I see a TTL=100 response at powerup.
Focus on the TFTP Flash wiki; the Recovery wiki is quite old.
I tried everything in TFTP Flash and Recover form a Bad Flash
The ping info is this:
Reply from 192.168.1.1: bytes=32 time=59ms TTL=252
Reply from 192.168.1.1: bytes=32 time=29ms TTL=252
Reply from 192.168.1.1: bytes=32 time=24ms TTL=252
Reply from 192.168.1.1: bytes=32 time=51ms TTL=252
Reply from 192.168.1.1: bytes=32 time=35ms TTL=252
Reply from 192.168.1.1: bytes=32 time=42ms TTL=252
Reply from 192.168.1.1: bytes=32 time=25ms TTL=252
Reply from 192.168.1.1: bytes=32 time=47ms TTL=252
Reply from 192.168.1.1: bytes=32 time=29ms TTL=252
Reply from 192.168.1.1: bytes=32 time=29ms TTL=252
Reply from 192.168.1.1: bytes=32 time=24ms TTL=252
Reply from 192.168.1.1: bytes=32 time=40ms TTL=252
Reply from 192.168.1.1: bytes=32 time=26ms TTL=252
TFTP and TFTP2 were unable to get response from the server.
I used advanced CMD with the commands as the page said and I got this:
C:\WINDOWS\system32>arp -s 192.168.1.1 xxxxxxxxx
C:\WINDOWS\system32>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\WINDOWS\system32>tftp -i 192.168.1.1 PUT code.bin code.bin
tftp: can't read from local file 'code.bin'
C:\WINDOWS\system32>
I tried with 192.168.1.2 and:
C:\WINDOWS\system32>arp -s 192.168.1.2 xxxxxxxxxxx
The ARP entry addition failed: Access is denied.
C:\WINDOWS\system32>ping 192.168.1.2
Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.0.22: Destination host unreachable.
Reply from 192.168.0.22: Destination host unreachable.
Reply from 192.168.0.22: Destination host unreachable.
Reply from 192.168.0.22: Destination host unreachable.
Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
192.168.0.22:
C:\WINDOWS\system32>ping 192.168.0.22
Pinging 192.168.0.22 with 32 bytes of data:
Reply from 192.168.0.22: bytes=32 time<1ms TTL=128
Reply from 192.168.0.22: bytes=32 time<1ms TTL=128
Reply from 192.168.0.22: bytes=32 time<1ms TTL=128
Reply from 192.168.0.22: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\WINDOWS\system32>tftp -i 192.168.0.22 PUT code.bin code.bin
tftp: can't read from local file 'code.bin'
It happened to 192.168.1.10 as well, connecting to WLAN prots and Internet ports.
think you just have to do as decribed in an earlier post.
and the line:
C:\WINDOWS\system32>tftp -i 192.168.0.22 PUT code.bin code.bin
tftp: can't read from local file 'code.bin'
doesnt seems right. you are using the wrong ip there i dare say. furthermore you are not in the right foler with the command prompt. and lastly i dont think ist called "code.bin"
the Situation might be much more Basic then dd-wrt, but Centers around the understanding of ip v4 subnetting. _________________ 2x Buffalo WHR-HP-G300N in AP
2x Buffalo WHR-HP-G300N in WDS (not working atm)
1x Buffalo WHR-HP-G300N in Wireless Client-Bridge (not working atm)
1x Buffalo WHR-HP-G300N in Reserve (still looking for that on ebay)
Set pc lan to
ip: 192.168.1.100
subnet 255.255.255.0
Gateway 192.168.1.1
disable all Firewall and antivirus and wlan or another other Connection your PC uses.
do a 30 30 30 reset on the router
then in a command prompt do
ping 192.168.1.1 -t
does the router respond continuously on that ip ?
you can cancel the command after 1 or 2 mins with ctlr+c pressed simultaniously _________________ 2x Buffalo WHR-HP-G300N in AP
2x Buffalo WHR-HP-G300N in WDS (not working atm)
1x Buffalo WHR-HP-G300N in Wireless Client-Bridge (not working atm)
1x Buffalo WHR-HP-G300N in Reserve (still looking for that on ebay)