Hi,
What are my benefits if I update the Cfe to 1.0.1.3,did the n66u runs better ? Do I have any disadvantages if I stay with 1.0.1.2 ?
Andy i did not understand why i must keep the old CFE ?
Best regards
stargate
Where do we enter in these commands? in the browser bar asHi.It's taken from new RT-N66U device. You may check current CFE version this way:
Where do we enter in these commands? in the browser bar as
eg. 192.168.1.2 # strings /dev/mtd0ro | grep bl_version
or via the GUI in an admin section ?
I tried this today on the latest firmware Version:3.0.0.4.354.27 BETA1 from Merlin
Got this result
[4/5] Checking differences between NVRAM from old and new CFE's
./diff: can't resolve symbol '_stdlib_mb_cur_max' in lib './diff'.
If you see only two differences: one is for 'bl_version' variable change
and second is a new 'odmpid=ASUS' variable then all goes well!
After that i did a manual compare of the two text files and they were fine so executed the CFE update anyway.
Just wanted to let you know
There is no benefit to upgrading the CFE if you are still running Asuswrt or Asuswrt-Merlin.
Even with DD-WRT now, the CFE upgrade is no longer necessary, as Brainslayer recently released a build that handles any CFE version.
25-May-2013: Since the experimental K3.X Broadcom Builds are out, you do not need to care what CFE you have. DD-WRT detects it automatically and extends 32KB NVRAM Version to 64KB. Which Image you have to flash, depends on your previous Image ( Stock, Merlin, K2.6 DD-WRT ).
Hi Soul-Reaver
Im getting the same message ("can't resolve ..."). My N66U is running on Merlin 3.00.254.29 BETA1. Your cfe/firmware update worked well despite the warning message? How did you find out it should work well?
Thanks!
…for DD-WRT users. I'm not using it, but I was interested to return CFE ability to read NVRAM variables to:CFE version no longer of interest
[4/5] Checking differences between NVRAM from old and new CFE's
./diff: can't resolve symbol '_stdlib_mb_cur_max' in lib './diff'.
If you see only two differences: one is for 'bl_version' variable change
and second is a new 'odmpid=ASUS' variable then all goes well!
[5/5] Flashing new CFE...
Do you want to flash a new CFE bootloader that? [y,n]nflashing canceled!
admin@RT-N66U:/tmp/home/root#
It's normal. Backup is a partition image, but new CFE file is a program image.Old CFE file is a 256KB file, new CFE file is 128KB, is this normal?? Can i flash the 128KB file?
cfe_n66u-1.0.1.3.empty.bin image contains no MAC addresses. You have to modify update script to embed MAC's into CFE image.I've got another device to recover (JTAG) from a friend should i flash the backup CFE or can i flash directly the new file?
Really curious. My update is for older devices only, there was no sense to analyse new devices, where CFE 1.0.1.3 is already installed.Theres a curious thing, if you analise the CFE (1.0.1.3) via Hex Editor after the conversion you will still see the MAC address there, but if you analise the same CFE (1.0.1.3) dumped from the new RT-N66U devices with new revision / cfe you will not see the MAC address from the device.
cfe_n66u-1.0.1.3.empty.bin image contains no MAC addresses. You have to modify update script to embed MAC's into CFE image
Hello, this might be a dumb question so excuse my ignorance on the subject but does it matter where the scripts are stored and unpacked on the desktop after being downloaded? It is not put on a flash drive and have to be mounted or anything correct? I take it the command will automatically find it then
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!