N66U bricked

[lfbb]

I've noted something very strange in my Ubuntu 12.04 LTS virtual machine... The Network settings shows the router is connected. Does this mean I can do something from the Linux VM?

- lfbb

 

[RMerlin]

Most likely not. You probably configured VirtualBox (or whatever VM solution you use) to NAT the network interfaces of the guests, so that IP was actually allocated by the VM solution, not by the router.

 

[fritsp1989]

Well to be honest i don't think flashing your CFE will do any good to your warranty of course i dont know how much time and effort asus sticks in it to find out that you flashed your CFE.

Are u absolutly sure you did everything you could ?

Did you disconnected all cables and connected the router straight to your PC ?
I had this a few times already it did not respond but that was on stock CFE and stock firmware.
But i kept trying and trying and all of the sudden it worked i was able to flash it with the asus recovery tool

 

[kuby8388]

Well to be honest i don't think flashing your CFE will do any good to your warranty of course i dont know how much time and effort asus sticks in it to find out that you flashed your CFE.

It happened once before already with version 1.0.1.2 (where the ASUS Firmware Restoration Utility was having a hard time detecting rescue mode on the wireless router); that was really why I upgraded the CFE version. And the CFE upgrade being at fault is just a hunch.... although like I said, I think the router always had this problem (the first time before I got the rescue mode to work, the 2nd time though this time it's locked me out of the router).

EDIT: I was lucky last time that after several tries the utility did detect the router. Dunno if it's a coincidence that right after the CFE upgrade the router's rescue mod no longer responds to 192.168.1.1 pings.

 

[lfbb]

Most likely not. You probably configured VirtualBox (or whatever VM solution you use) to NAT the network interfaces of the guests, so that IP was actually allocated by the VM solution, not by the router.

I use VMWare Workstation and yes, you are right about the NAT, in Bridge mode it can't connect, though it recognizes something is there.

- lfbb

EDIT:

this router is unbrickable (to dead). You can always revive router using Asus Firmware Restoration.

1) install Asus utils from CD or download from my website
2) set a static IP on your network card 192.168.1.5 netmask 255.255.255.0 gateway 192.168.1.1 dns 192.168.1.1
3) run Asus firmware restoration tools and select tomato image
4) unplug power from router, press restore button, hold and plug power
5) wait about 5secs, power led should blinking
6) release restore button and press flash
7) if yuo will get some cancels, errors, timeouts - try again

i bricked my asus routers a hundreds of times and always will revive
http://tomatousb.org/forum/t-522303

I wish I was this lucky!

 

[Zol77]

Hi lfbb!

(sorry my english)
Today I was in a similar situation. (win7 64 bit)
Flashed the tomato firmware,reboot,and nothing happened.
I used the Asus firmware restoration tool to upload original,and tomato firmware,
and again nothing.
With this i tried my father pc (win xp) ,and successfully flashed the firmware.
My settings in win xp:
- static ip 192.168.1.10
- netmask 255.255.255.0
- gateway,and dns empty
- power unplug,press and hold reset,plug power,and release after 5 sec,power led blinking slowly
- start the upload,in the Asus firmware restoration tool.

 

[kuby8388]

I got an RMA from an ASUS Tech. and sent it over to the ASUS Repair Facility. Hopefully they can help me repair it; or provide a refurbished version.

Word of advice for people out their flashing CFEs; don't set the router into rescue mode after updating to a new CFE (my personal recommendation). First it's called rescue mode for a reason (so it should be considered as the last-resort method for saving the router), and secondly this feature seems to be broken after flashing to a new CFE version (IE. a few people here have bricked their router setting the router into rescue mode 'right after' flash upgrading their CFE).

 

[fritsp1989]

I got an RMA from an ASUS Tech. and sent it over to the ASUS Repair Facility. Hopefully they can help me repair it; or provide a refurbished version.

Word of advice for people out their flashing CFEs; don't set the router into rescue mode after updating to a new CFE (my personal recommendation). First it's called rescue mode for a reason (so it should be considered as the last-resort method for saving the router), and secondly this feature seems to be broken after flashing to a new CFE version (IE. a few people here have bricked their router setting the router into rescue mode 'right after' flash upgrading their CFE).

CFE rescue mode is not broken i flashed my CFE and already used it a couple of times already to flash tomato, ddwrt, merlin wrt and asus wrt.

 

[RogerSC]

CFE rescue mode is not broken i flashed my CFE and already used it a couple of times already to flash tomato, ddwrt, merlin wrt and asus wrt.

Yes, rescue mode is fine on my router as well after flashing the CFE.

 

[KevTech]

I got an RMA from an ASUS Tech. and sent it over to the ASUS Repair Facility. Hopefully they can help me repair it; or provide a refurbished version.

Word of advice for people out their flashing CFEs; don't set the router into rescue mode after updating to a new CFE (my personal recommendation). First it's called rescue mode for a reason (so it should be considered as the last-resort method for saving the router), and secondly this feature seems to be broken after flashing to a new CFE version (IE. a few people here have bricked their router setting the router into rescue mode 'right after' flash upgrading their CFE).

If during testing Asus finds the CFE does not match the router hardware version they may reject your RMA.

 

[kuby8388]

If during testing Asus finds the CFE does not match the router hardware version they may reject your RMA.

Yah. In that case I might be screwd. But from what people are saying, it seems that the problem is not the new CFE.. although I'm not sure if they're going to blame it on the CFE; the router was okay after the new CFE upgrade. I applied (mtd-erase -d nvram) and upgraded it from .220 to .24x in the new CFE even.

It was only when I boot into the router's rescue mode that it suddenly stopped working.... hopefully the ASUS repair facility can figure out what's wrong with the router.

-

Again, thx for the posts everyone! I've learned a lot about the ASUS RT N66U from reading your posts/comments about the ASUS RT N66U router.