Posted: Fri Oct 26, 2012 22:53 Post subject: N66U bricked
Power went out during upgrade. Can't ping router, can't connect to any of the ethernet ports(windows says cable is disconnected, but I know cable is good), so basically when I set the static IP (192.168.1.1) it won't connect to router. Asus Firmware Restoration can't find router. Need help here.
Peacock announcement, note 6. You probably need a serial cable to fix it. _________________ 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.."
Joined: 26 May 2009 Posts: 183 Location: N34 31.872 E69 10.821 for now.
Posted: Sat Oct 27, 2012 1:08 Post subject:
Just curious, what model router is it?
Some ASUS models have a recovery mode built directly into the CFE... and as long as the CFE wasn't compromized you should be able to debrick without a serial or JTAG.
Reading through the rest of that might be a good idea as well.
Unless of course that's what you tried with the Asus recovery software. I've never used it, and have no idea what the procedure is for it. _________________ The Peacock Thread <-- New? READ THIS!
------
Current: ASUS RT-N16 DD-WRT v24-sp2 mega(SVN revision 19519)Running OTRW - Take 2 on 8 GB Flash Disk. 128M swap + 7.5 GB ext2 on /opt Past:
ASUS WL500GP v2 [DD-WRT v24-sp2 (06/17/09) mega-(SVN 12307M NEWD Eko)]
Registered Linux User #491768
Okay i know this sounds stupid..........
But i had this issue to, what you need to do is set a static ip like this
IP 192.168.1.2 you can try higher numbers it doesnt matter
Subnetmask 255.255.255.0
Gateway 192.168.1.1
Erase your NVRAM before you go to recovery mode
30 sec WPS button while on keep in pushed while the router is off for 30 seconds keep it pushed and turn your router on for 30 seconds.
When you did that put the router in recovery mode, start a CMD and '' ping 192.168.1.1 '' if the ping responds quick fire up the recovery tool and flash the original asus 220 firmware.
AFTER all of that ERASE your nvram before you try to connect to your router and also delete the static ip and stuff from your computer else you cant connect to the internet.
I know this is a bit messy but this is the only way for me that i actualy works.
Recovery will probably tell you that the flash went wrong, but that isn't the case !
Recovery utility cant ping the router because you had a static IP and the router did not accepted it.
I am willing to help you i think your router is not bricked unless you messed with the CFE please give me a PM and i will look what i can do for you
Router's LAN ports are not dead. I found a traffic analyzer called 'Wireshark' and when I turn router on it shows a lot of activity on the network, but I still can't obtain ping reply from router.
I've noted something very strange in my Ubuntu 12.04 LTS virtual machine... The Network settings show the router is connected. Does this mean I can do something from the Linux VM?
And the only traffic I see on that capture is yours, router is not talking at all...
Sorry, but I disagree. I've made a test in Wireshark, I waited 5 minutes with the router off, no traffic at all, zero. Then I turned the router on and the traffic started, so the LAN ports are not dead, but can't reply to pings. Very strange.
Anyway, thanks for your effort in helping me, I really appreciated it.
