Posted: Mon May 27, 2013 21:06 Post subject: RT-N16 Bricked
Hi
I install dd-wrt.v24-21676_NEWD-2_K2.6_mega on my RT-N16, then i log on putty console and make the biggest mistake.
i give this tree comands in console:
erase nvram;
erase dd-wrt;
erase cfe
and of course reboot, then my router refuse to start up.
I have no power light, only lan port light and i can't enter to recovery mode, the restore button doesn't work.
I also tried a ca-42 cable but i can't see nothing on serial connection on putty (i set the right port and bud rate).
Any chance to revive the router?
Thanks
why turn so many ppl their routers into paperweighters ?
ok, that happend to me, too. but with a wrt54gl, that can be rivived with jtag for sure. _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
Joined: 17 Apr 2009 Posts: 627 Location: Philadelphia, PA
Posted: Sat Jun 01, 2013 13:33 Post subject:
BasCom wrote:
why turn so many ppl their routers into paperweighters ?
ok, that happend to me, too. but with a wrt54gl, that can be rivived with jtag for sure.
I don't think that they are doing it on purpose!
It really does get confusing as to which firmware is for which router (except for the trailed builds - they make it nice and easy!). You have k2.4, k2.6, VINT, NEWD, NEWD2, NV60K, NV64K, etc, etc...
Then if you try to read and actually understand the "peacock" thread - as the one user just loves to constantly point out instead of actually helping folks, that confuses people even more. Then, of course, we have the Router Database, which everyone says not to use, but it is right in your face on the main page! Then we have SP1 labeled as the "stable" version... Really, it's no wonder there are so many bricks.
The whole purpose of this board to ask questions and get help, isn't it? I swear that there are certain users who would rather the whole site only be the damn Peacock thread! The peacock thread is not a substitute for personalized help...
Sorry - got off on a tangent a little bit there!! _________________ 1 x Linksys WRT160n v3
1 x Linksys WRT310n v1
1 x Linksys WRT600n v1.1
1 x Linksys WRT610n v1
1 x Linksys E2500
1 x Netgear WNDR3300
1 x Dlink DIR-825 v1
2 x Asus RT-AC66U
but, if you do not have the possibillities to recover, you´d better dont touch experimental Builds. JTAG isnt a garantuee for newer routers. This Forum is full of:"i have bricked my unit" threads _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
I see no reason for erase cfe. Nobody on this forum suggests that you should erase cfe (perhaps for older G routers there was a need to do it in order to write a new cfe, but there is no such need for a RT-N16). _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
That would be fine had it only been the firmware that was erased, but removing the CFE is essentially the same thing as removing your computer's BIOS. The router isn't going to be receptive to the firmware recovery because it has no way to start up beyond simply powering on.
That would be fine had it only been the firmware that was erased, but removing the CFE is essentially the same thing as removing your computer's BIOS. The router isn't going to be receptive to the firmware recovery because it has no way to start up beyond simply powering on.