Ok just read you went from tomato to ddwrt. A 30/30/30 reset should get you to the screen where ddwrt is asking you to enter a new user name and password. If it's not at the ddwrt new user/pw screen you might still be on tomato. In that case you will want to use passwords for tomato to get into the router.
For recovering any ddwrt pw from a tomato install see here;
"If you're upgrading from the DD-WRT firmware, telnet into the router *before* upgrading and type "nvram get http_passwd". The result will be your password in Tomato. This is necessary because of a change in DD-WRT's way of using the standard http_passwd variable.
If you have a Buffalo router or a Linksys with a pushable Cisco logo, push the AOSS/Cisco button for at least 20 seconds, then telnet into the router on port 233. Type "nvram get http_passwd" to retrieve the password or "nvram set http_passwd='your_new_password'" followed by "nvram commit" to set it manually. Reboot the router using the command "reboot" after using this method.
If nothing else works, push the reset button for a few seconds to reset all of the settings. The default password after resetting is "admin"."
I can't telnet into the router because I don't have the password, I tried!
I did a 30/30/30 reset several times. But for some reason it won't reset the password and it did't reset my SSID either!
When I "upgraded" from Tomato to DD-WRT I reset the NVRAM several times to be on the safe side, but honestly, when I "Downgraded" From DD-WRT to Tomato I didn't clear the NVRAM (because I didn't know I had to do it there as well.)
According to your explanation and my experiance I still have DD-WRT.
What I have to do is telnet into my router type "nvram get http_passwd". But I can't do that because I don't have the password, so I'm screwed?
Or can I reflash everything via the USB port including the password?
Hmmm. If you're on ddwrt it should respond to the usual 30/30/30 with a blank password and user name field for you to fill in. If it's still asking for a pw, try the ones for tomato, wich by default are the user name left empty and the pw is root, or the other way around. If worse comes to worse, you might try reflashing it after rebooting the router. What router is it?
Also see here;
"Recovering with TFTP
Note that if you already have DD-WRT installed and working, and you are on this page because you want to revert to the router firmware, you need to break DD-WRT first! THIS IS AN EXTREMELY DANGEROUS PROCESS. SEE THE FIRST LINE IN CAPS ABOVE FOR BETTER SAFER METHODS.
telnet into the router, execute:
mtd erase linux (This bricked my Buffalo WHR-HP-GN! Don't do mtd erase linux!)
(Note: only tested on the WNDR3300 with 24preSP2; YMMV)
During startup, the router will pause to accept a temporary firmware upload via tftp. On the Linksys WRT54G routers, you need to flash an image that contains the "W54G" header (Linksys and mini_wrt54g images)
If pinging 192.168.1.1 does not work, check the IP Address of your computer and make sure it is assigned an IP address in the subnet of the router IP. For simplicity sake you can assume "192.168.1.x" is good. If you do not have a good IP, the DHCP Server might not be working. So set your IP manually to something like 192.168.1.77 with 192.168.1.1 as your gateway and then try pinging the router again. Finally, you may want to use a network scanner to scan your network (smaller networks) just to be sure that your router was not assigned another IP.
Power the router on with a continuous ping running in a command window:
ping -t -w 2 192.168.1.1
The -w 2 parameter forces a lower timeout for the ping answer, this makes easier to get an answer from the bricked router.
You should see at least a few replies from 192.168.1.1. Do this several times to be sure. If it does you have good chance of simple recovery. If you still receive no response, the IP address may be something other than 192.168.1.1. You should attempt to obtain the IP address of the router. Especially if previous firmware set the boot_wait variable to on, the router pauses even longer than normal during bootup to accept a recovery flash. All you need to do is provide a firmware to it via TFTP during this window of time.
Prepare your PC, firmware file and TFTP software and play with the timing of powering it on and starting the TFTP session just after applying power (or as soon as you start to see ping replies). If you try it a number of times (at least 10) you will probably rescue the router with no fuss!
If you see an 'Invalid Password' prompt from the router the bootloader did not accept the TFTP image and the firmware is refusing the TFTP upload. You can force the bootloader to accept the TFTP upload by holding the reset button while powering up the router. You may also improve success rates by ensuring there is a switch or hub between the PC and the router, maintaining link state when the router power cycles. "
Flashing directly from one third party firmware to another without going back to oem firmware in between can cause problems such as this. I believe it has to do with how the password nvram variables are stored differently. Try going back to stock firmware. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."