![]() Hereby is my connection of the cable with the motherboard: The motherboard of the router contains Serial TTL hear as it is shown on the picture below (which you can find in the original post here):ĬAUTION: You must NOT connect the red wire of your USB-Serial TTL connector, as it is 5V but in the motherboard it is just 3.3V. Connectivity of the cable with the motherboard Of course, one needs to disassemble it, but it is very simple task and I won’t explain here any details of it. ![]() This table gives an idea, how we can connect the cable to the router. Thank you the post here, I got the information as follows: Well, having the cable doesn’t answer the next question, how one can use it. The cable is based on Prolific PL2303 chip. In my case, as I test a lot of Android devices, I was lucky to find a “cubieboard USB – Serial TTL” cable. Hereby are step-by-step instructions, which saved my device 1. We need a firmware, which we want to use in order to reflash the brick. ![]() We need to connect to the console of the router via the cable.We are to figure out how it can be connected to the router motherboard.First of all, one needs a “USB – Serial TTL” connector, to se what happens inside the brick.The system is keep rebooting as the firmware image is broken due to the flash size issue.The recovery processĪs I learned from aforementioned links, is the following: Thank to several forums as follows: #1, #2, I found a solution, which works for me. ALL VERSIONS AFTER THAT DO NOT WORK, because of the following, Netgear makes flash size of their routers a bit smaller, so, actual flash size is about 3.4Mb or less, while the latest firmware size is about 4mb. The last DD-WRT version that works with this router is r18777 released 3-19-12. Finally, using latest firmware for wnr2000v3 from dd-wrt is a bad ideas as the flash memory is a bit less than the firmware file. It is basically a good idea except the fact, there are plenty of mistakes/ errors in documentation, which leads us to a lot of troubles. Finally, don't listen to users telling you to do "erase nvram" on a telnet cmd line.Well, it happens, when you try to make WiFI installation at client location batter, one can upgrade routers with dd-wrt firmware. You may need to do a reset to factory defaults if an nvram variables function changes between firmware version something which is extremely rare. Reset to factory defaults keeps variables which are needed for router type detection so it is the only nvram reset you should ever use before an upgrade. The gui function for Factory defaults will wipe out any ddwrt setting but will keep defaults from CFE and from stock firmware. It does not work in the u-boot boot loader (atheros, ralink, marvell) only in Broadcom. The 3rd 30 is what does something but should only be used when nothing else helps. The 2nd 30, ie turn off router and wait 30 seconds before turning it on is just bogus, has no effect other than a placebo effect. Y ou can achieve the same by pushing the gui reboot button. The 1st 30 second of pushing the resetbutton when ddwrt runs is just not needed, a short push will do the same which is reboot the router. You will lose any factory defaults that the routers stock firmware has stored in nvram.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |