m.m.m wrote:since noob beginner, I found out I should make a contact with the router with its serial port after a lot of searching. built the ttl to rs232 converter
You're doing things in either strange or even dangerous ways. As of 2013 the simplest way to convert USB to low-voltage UART is to use appropriate chip like FT232, CP201...2103 and somesuch. And of course there are ready solutions based on these ICs selling around. Starting from "old" mobile phone cables (which convert USB to low-voltage UART excatly like that one you need) up to embedded developer tools (those guys are often use those UARTs for debug). In fact USB to UART converters are quite common and inexpensive these days. You can read openwrt wiki to get some ideas on this.
If I got it right. you are about to convert USB to RS232 first (RS232 is *not* level compatible with 3.3V UART!) and then ... downconvert it to 3.3V UART using MAX232?
Usually "USB to RS232" converter is in fact some USB to UART bridge IC like FT232, CP2101 or similar, which converts USB to low-voltage UART (like that one you actually need) and then another IC shifts levels to RS232 using IC like MAX232 to reach RS232 compatibility (i.e. bipolar 12V levels, you don't need or want them!). Then you put yet another MAX232 to ... downshift levels back to 3.3V UART? 
Well, you see, it's a bit silly: two extra MAX232-like ICs on the way and RS232 physical level used which you don't need or want anyway. OTOH it makes things more complicated, could make signal worse and harder to troubleshoot as there are more connections involved. Though theoretically it could work and isn't anyhow invalid on it's own. Just somewhat suboptimal.
And hopefully you've never attached RS232 (bi-polar, 12V) levels to 3.3V UART. Doing so is likely to fry router CPU. Pay extra attention to this. As for me it's not a great idea to have RS232 bipolar 12V levels around when dealing with 3.3V ICs. Basically it's wrong to attach digital I/O pins to anything above IC supply (i.e. 3.3V) or below GNS (0V). Doing so is likely to fry IC. That's why modern ICs need MAX232-like level shifter to operate with ancient bipolar RS232 levels.
Then, guy suggested that
1) Grab your converter.
2) Connect converter's TX pin to converter's RX pin. There should be no other devices attached to UART (i.e. don't connect bricked device, etc).
3) Start some terminal and connect to that COM port.
4) Set up port to use no flow control. And make sure local echo is off.
5) Type something.
5) Check if you can see what you type.
If everything is done correctly and your converter actually works, you will see same text as you typed because it's transmitted via TX line and then immediately received via RX like on the same port (that's why guy asked to connect them). Note that terminal could do local echo - make sure it's off. This test allows to understand if your converter actually works and is able to transmit data and receive it back. It's easier since no external devices involved, only converter itself should work for this test. If you can't get past this point, there is something wrong with your converter, OS drivers, port settings or something else, not anyhow related to bricked device(s) or something like that.