I have a long serving WRT54GL that has been running Tomato 1.28 for ages and it has been great. Recently, I decided to add ad blocking capabilities which involved updating firmware. I read around and decided the shibby version was active and had what I wanted. I saw shibby suggest tomato-K26-1.28.RT-MIPSR1-XXX-Mini would work on my WRT54GL. So I downloaded the file, went into firmware admin panel to update, uploaded the file and everything looked good until the router rebooted. Then, to my horror, I discovered I'd actually just updated with tomato-K26-1.28.RT-MIPSR2-XXX-Mini.
The symptoms: The power light flashes without stopping, the DMZ light never even blinks, and the ethernet lights are solid green - I've read this means a defective bootloader is present. The web gui does not come up. It will not assign IP addresses. It doesn't respond to pings during the boot process or thereafter.
What I've tried: 30-30-30 power cycling. Power cycling, holding and releasing the reset button at various intervals, with an ongoing ping command (always "Request timed out."). Cannot get it into management mode either. I ran through everything here and all the links here except jtag/serial.
What I have NOT tried: I have tried to telnet in, since it won't respond to pings. I have not tried jtag or serial adapter methods, I don't have the cables for it or a soldering iron. I have not tried to pin short the router, in hopes the router may be recoverable.
Sadly, I'm ready to junk it, I'm not sure jtag is worth the time/cost investment for a 6+ year old router. But I thought I'd ask to see if there is something specific to try out, given I know what bricked the device. Just in the off chance the MIPSR2 v. MPISR1 mistake had been made before.