Posted: Thu Apr 11, 2019 18:02 Post subject: BS -r39469 Bricked my wrt54gl v1.1
Tried everything on the wiki and peacock posts. Switching IPv4 address to 192.168.1.10, tried going half duplex 10mbps. Won't ping even on router reboot.
Flashed from linksys webpage http in waterfox, said successful, waited, power light never stopped blinking, wan light doesn't come on, responds with led to having a ethernet plugged in to wired hub but absolutely won't ping. won't respond to arp -s even in administrator cmd.
Request time out and destination host unreachable.
Flashed a broadcom micro generic from standard linksys firmware also
Yeah, my WRT54GL v1.1 was bricked by v24_voip_generic.r39296 last week.
I don't understand how this could go from working for such a long time to completely bricking. BS builds have worked for a long time for me and now they brick perfectly good hardware. Oh well...
Yeah, my WRT54GL v1.1 was bricked by v24_voip_generic.r39296 last week.
I don't understand how this could go from working for such a long time to completely bricking. BS builds have worked for a long time for me and now they brick perfectly good hardware. Oh well...
You've been lucky then; there have been many bad builds over the years for k2.4 firmware.
I spoke to BS about this; I'm going to try my GL and GSv6 this weekend on serial and see what's going on. @invisibletouch What exact build did you use? Also, you'd need a pretty big failure to require JTAG; serial will work unless you somehow overwrite the CFE (bootloader). _________________ #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
[/quote]You've been lucky then; there have been many bad builds over the years for k2.4 firmware. Cool
I spoke to BS about this; I'm going to try my GL and GSv6 this weekend on serial and see what's going on. @invisibletouch What exact build did you use? Also, you'd need a pretty big failure to require JTAG; serial will work unless you somehow overwrite the CFE (bootloader).
[/quote]
I appreciate it but I tried to look up how to jtag and there isn't enough easily digestable material with resources I could readily use, a la, I don't have a soldering iron or materials required to make a cable, or the knowledge. I did this to myself by not being prepared. it should be a prerequisite for anyone wanting to flash custom firmware to have a jtag cable.
I think I tried 39469. I'm really just a hobbyist at this and wanted to challenge myself to custom firmware but I'm at 2 bad routers now and I think it's time to call it quits.
I appreciate it but I tried to look up how to jtag and there isn't enough easily digestable material with resources I could readily use, a la, I don't have a soldering iron or materials required to make a cable, or the knowledge. I did this to myself by not being prepared. it should be a prerequisite for anyone wanting to flash custom firmware to have a jtag cable.
I think I tried 39469. I'm really just a hobbyist at this and wanted to challenge myself to custom firmware but I'm at 2 bad routers now and I think it's time to call it quits.
Did you try to TFTP the OEM firmware, as a first step? _________________ #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
Ok, k2.4 issue is fixed, it will be in the next release.
See here for the GL brick testing I did. BS said the issue was due to "a change in the special kernel loader. dont know why it wont work. use now the old loader again." This isn't part of the SVN repo.