1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Shibby + CFE Update = Unresponsiveness

Discussion in 'Tomato Firmware' started by Cyberian75, Dec 8, 2012.

  1. Cyberian75

    Cyberian75 Network Guru Member

    Hey,

    I recently updated the CFE of my RT-N66U with no problem. I had to flash the stock firmware in order to do the update. Now I'm not able to go back to yours. It flashes ok, and all the lights come up; however, it doesn't respond to anything -- not even to pings from my computer set up with a static IP.

    What's even more odd is that the reset button doesn't work with yours flashed.

    Any thoughts?
     
  2. M0g13r

    M0g13r LI Guru Member

    switch it off press reset switch back on wait 5 secs release reset

    in browser 192.168.1.1 asustek mini cfe webblah restore default nvram blah

    reboot
     
  3. Cyberian75

    Cyberian75 Network Guru Member

    I'm not new to flashing firmwares...
     
  4. jakey

    jakey Networkin' Nut Member

    FYI I also updated my CFE on RT-N66 and went back to Shibby with no issues.

    I agree with the poster above though, it does sound like a sticky nvram, when changing to a different firmware I always clear nvram from the mini webif and again from firmware once loaded. Don't suppose it makes any difference but I used RMerlin's firmware to do the CFE update.
     
  5. lefty

    lefty Networkin' Nut Member

    I'd say if you did a CFE upgrade and then reboot the unit and it didn't come back up than this statement is contradictory of what you are saying "I recently updated the CFE of my RT-N66U with no problem." I'd say you had a problem if the unit didn't come back up after the CFE upgrade because when you rebooted the unit, the new CFE got initialized, before you rebooted the unit you still had the old CFE in memory running.

    Be that as it may, since we can pretty much rule this off as a CFE problem (yes the CFE is probably fubar) you'd either need to look into jtag, which i don't even know if RT-N66U supports jtag or not, or return the unit in hope of getting another one.
     
  6. Cyberian75

    Cyberian75 Network Guru Member

    The problem is that once I flash Shibby's onto it, nothing comes up. No web updater,, no pings, nothing. Fortunately, Firmware Restoration Utility still works. After I flash Merlin's, I have to reset it once more using the reset button which works; however, the reset button doesn't work with Shibby's.

    So before I flash Shibby's, I'd reset the nvram using the web updater...?
     
  7. jakey

    jakey Networkin' Nut Member

    So why don't you perform the CFE update again using your original back up but this time put a RMerlin build on to do the job. Such an easy job now it can be done entirely on the router.
     
  8. lefty

    lefty Networkin' Nut Member

    Ah ha, more info that should have been included in the first post. I would have to agree with jakey, do the procedure as jakey posted then once you have it on there with no problems and the unit is then functioning properly, then look into switching it over to shibby's tomato build.
     
  9. Cyberian75

    Cyberian75 Network Guru Member

    I just thought that there's some kind of an incompatibility with the new bootloader since the reset button worked before.

    Thanks.
     
  10. Andy_113

    Andy_113 Networkin' Nut Member

    correct me if i'm wrong but the reset button doesn't restore nvram defaults with tomato on this router, i thought it was the wps button.
    Can you still connect to the cfe miniweb server with tomato flashed? also, which version of the cfe updater did you use, as the first had vlan bug?
     
  11. Cyberian75

    Cyberian75 Network Guru Member

    Oh! I didn't know about the WPS button. As for CFE updater, I used the most recent one.

    I'll try it this evening.
     
  12. Cyberian75

    Cyberian75 Network Guru Member

    The WPS button doesn't work, either, after flashing to Shibby's. I gave up. Gonna stick with Merlin's.
     
  13. Cyberian75

    Cyberian75 Network Guru Member

    FYI: I did "mtd-erase -d nvram", and then I put it in recovery mode to flash Tomato.
     
  14. lefty

    lefty Networkin' Nut Member

    mtd isn't needed for erasing nvram, and i would be cautious in general with using mtd commands or you could end up wiping out board data that will make your router not function properly. Which shibby build flavor are you using in all of this?
     
  15. Cyberian75

    Cyberian75 Network Guru Member

    I had to clear the nvram via the web updater before using the Firmware Restoration utility to flash Tomato. This enabled the reset button, which I had to use after flashing. It's working fine now!

    Thanks!
     

Share This Page