On my E3000, I upgraded from base Tomato to Shibby's latest (build5x-121-EN/tomato-E3000USB-NVRAM60K-1.28.RT-MIPSR2-121-BT-VPN.bin) last night. Configured it, and everything was happy until I rebooted the router, at which point it went into a reboot loop. This morning, just to leave my wife with functional Internet during the day, I wound up clearing settings (reset button for 30 seconds) and configured just the basics for the WLAN network. Having read a comment about doing a full nvram wipe when making major build jumps, I did that this evening and again reconfigured from scratch. Reboot took me into a loop again.
Another reset, and I've saved a .cfg file and rebooted after each major batch of changes. It appears that it's the point where I enable QoS that puts it into the loop. I can make zero config change beyond clicking the QoS checkbox, reboot, and start looping.
Of course, once it goes into the reboot loop, I'm not aware of a way to get the logs off to know what's going wrong. By uploading my last non-looping .cfg, I can at least come back to a good state quickly. Other than skipping on QoS, any suggestions how I might debug this or work around it? Or does turning on QoS somehow make it take many reboot cycles before it becomes usable again?