CFE bootloader update

[Pierino]

Done. Thanks for the help.

 

[hggomes]

You are welcome and btw there's a botton for that purpose here in the forum eheheh

 

[Pierino]

I know. I had already used it.

 

[halex4u]

Something is wrong there, have you poweroff/on the router? How you have done the CFE update?

1) Yes, the router was power off/on. In GUI I see: CFE 1.0.1.4.

CFE v.1.0.1.3 is showed only I if I run: nvram get bl_version.

2) Following the instructions in the first post.

Sent from my Galaxy Nexus using Tapatalk

 

[ryzhov_al]

Something is wrong there, have you poweroff/on the router? How you have done the CFE update?

1) Yes, the router was power off/on. In GUI I see: CFE 1.0.1.4.

CFE v.1.0.1.3 is showed only I if I run: nvram get bl_version.

It's fine! Let me explain that.

CFE has NVRAM default values, embedded right into it's code.
The current NVRAM values stored in separate part of flash.
When you resetting router to defaults, firmware erases NVRAM partition and CFE fills basic NVRAM variables from it's code to NVRAM partition (including bl_version variable) on the next boot.

So, while you not reset you router to defaults again, you'll see old bl_version value. You may check CFE version by:

strings /dev/mtd0ro | grep bl_version

 

[halex4u]

It's fine! Let me explain that.

CFE has NVRAM default values, embedded right into it's code.
The current NVRAM values stored in separate part of flash.
When you resetting router to defaults, firmware erases NVRAM partition and CFE fills basic NVRAM variables from it's code to NVRAM partition (including bl_version variable) on the next boot.

So, while you not reset you router to defaults again, you'll see old bl_version value. You may check CFE version by:

strings /dev/mtd0ro | grep bl_version

Thank you!

Sent from my Galaxy Nexus using Tapatalk

 

[ryzhov_al]

2. I didn't notice any changes on temperatures, i have double check it.

Nothing serious:

Taken from my stat site. RT-N66U was under typical load.

 

[oversim]

Update to CFE v.1.0.1.4 (previous was .3 updated from .2).
All was Ok, update, ...and overcloked to 650, 325, 162
thanks

 

[bluepoint]

It's fine! Let me explain that.

Is the bootloader EU only? Is it okay to upgrade an RT-N66U US model to this CFE bootloader using your procedures?

 

[KevTech]

Is the bootloader EU only? Is it okay to upgrade an RT-N66U US model to this CFE bootloader using your procedures?

Yes it works for US models but check what your router has first as the router may already have the updated one.

 

[bluepoint]

Yes it works for US models but check what your router has first as the router may already have the updated one.

Mine was 1.2 updated to 1.3. I hesitated to do it cause hggomes post indicated the bootloader is for EU.
http://forums.smallnetbuilder.com/showthread.php?t=17793

I'm thinking of regulation domain, MAC addresses, do we need to edit it or just using ryzhov_al's procedure will be enough to copy all info from the old bootloader?

 

[dsring]

Mine was 1.2 updated to 1.3. I hesitated to do it cause hggomes post indicated the bootloader is for EU.
http://forums.smallnetbuilder.com/showthread.php?t=17793

I updated my RT-N66U (US) from 1.0.1.3 to 1.0.1.4, and overclocked it to 662 MHz. No issues with the upgrade if you follow the instructions in the first post.

 

[bluepoint]

That's good to know. Have you reset your router to factory default and if so retained the MAC addresses?

 

[hggomes]

I didn't told it was for EU, but from EU

Regarding the 1.0.1.4 upgrade you are safe to do it via ryzhov_al first post script, i guess it will do all necessary changes to the 1.0.1.4, including .EU to .US. changes if that's the case.

If in doubt, you can always check it after creation of "newcfe.bin" by editing and checking for those changes.

Good luck

 

[dsring]

That's good to know. Have you reset your router to factory default and if so retained the MAC addresses?

I did not reset the router. I did reboot it. As far as I know, it has retained all of the MAC addresses. Everything is working normally.

 

[bluepoint]

Regarding the 1.0.1.4 upgrade you are safe to do it via ryzhov_al first post script, i guess it will do all necessary changes to the 1.0.1.4, including .EU to .US. changes if that's the case.

Good luck

Done and overclocked!

 

[Pierino]

I am trying to update another unit but am getting an error mesage. the bootloader on it now is 1.0.1.2

RT-N66U login: admin
Password:


ASUSWRT-Merlin RT-N66U_3.0.0.4 Fri May 9 21:15:50 UTC 2014
admin@RT-N66U:/tmp/home/root# cd /tmp
admin@RT-N66U:/tmp# wget http://files.ryzhov-al.ru/Routers/RT-N66U_CFE_update/cf
e_n66u-1.0.1.4.tgz
Connecting to files.ryzhov-al.ru (198.12.78.68:80)
cfe_n66u-1.0.1.4.tgz 100% |*******************************| 108k 0:00:00 ETA
admin@RT-N66U:/tmp# ./cfe_update.sh /dev/mtd0ro
-sh: ./cfe_update.sh: not found
admin@RT-N66U:/tmp#

 

[bluepoint]

You're missing a step after wget, see below.

tar -xzvf cfe_n66u-1.0.1.4.tgz

 

[Pierino]

Face palm. Thanks. You'd think this being the 4th time I'd get it right. Lol

 

[akbor]

Hi,

the script output:

admin@RT-N66U:/tmp# ./cfe_update.sh /dev/mtd0ro
Current CFE version is 1.0.1.2
[1/4] Dumping default NVRAM settings from original CFE...
nvram header found:
start   0x400
end     0x1374
len     3956
crc     0x7c
ver     0x01
[2/4] Preparing new CFE...
nvram header created:
start   0x400
end     0x1370
len     3952
crc     0x98
ver     0x01
[3/4] Checking differences between old and new NVRAM areas:
--- nvram_orig.txt      2014-07-05 18:06:06.359498627 +0200
+++ nvram_updated.txt   2014-07-05 18:06:06.409498627 +0200
-bl_version=1.0.1.2
+bl_version=1.0.1.4
Something goes wrong, unexpected NVRAM values, exiting...

The script has produced some output files in /tmp, e.g:

-rw-rw-rw-    1 admin    root        262144 Jul  5 18:06 cfe.new
-rw-rw-rw-    1 admin    root           153 Jul  5 18:06 diff.txt
-rw-rw-rw-    1 admin    root          4011 Jul  5 18:06 nvram.txt
-rw-rw-rw-    1 admin    root          4011 Jul  5 18:06 nvram_orig.txt
-rw-rw-rw-    1 admin    root          4011 Jul  5 18:06 nvram_updated.txt

The MAC values in the nvram*.txt belong to my router, I checked that.

Anybody an idea, what went wrong?

A little addition: installed FW is Merlin's 3.0.0.4.374.43_0

BR