CFE bootloader update

[hggomes]

I really doubt those results are accurate, if 10% represets 3mb/s then 100% would be 30mb/s

 

[noric]

It looks pretty much to me too (especially the write boost), but I've tested this on a gigabit lan connection and values are pretty consistent.
Did anyone do the same test?

 

[hggomes]

I did at the time when i uploaded the CFE 1.0.1.4 and the results were improved in 1-1.5mb/s, and those are amazing considering a 60mhz overclock.

 

[noric]

Well, I don't know then. I'd need to downclock to retest but I'm too lazy.

 

[hggomes]

The overclock difference is much bigger in ARM arch and it overclocks alot more comparing with MIPS, but it's always good having some more mb/s anyway.

 

[DrTeeth]

It looks it made a HUGE difference to me. I went from 16MB/s to 19MB/s read, and from 9MB/s to 12MB/s right.
This is with a 10% overclock (from 600 to 660MHz).

With all due respect, I doubt you would have noticed that increase if somebody would have done the over-clocking without your knowing if you had no figures.

 

[Builder71]

Thanks for your script.
Used it a second time, now to go from 1.0.1.4 (EU) to 1.0.1.9 (EU)
Not because it's needed but just because it can.

All seems to work fine.

I do have one question.

If I type "nvram get bl_version" it still gives me: 1.0.1.4

This "strings /dev/mtd0 | grep bl_" gives me: bl_version=1.0.1.9
And the GUI gives me 1.0.1.9



Do I need to worry?

Edit: I fixed it with "nvram set bl_version=1.0.1.9"

 

[RMerlin]

I do have one question.

If I type "nvram get bl_version" it still gives me: 1.0.1.4

This "strings /dev/mtd0 | grep bl_" gives me: bl_version=1.0.1.9
And the GUI gives me 1.0.1.9



Do I need to worry?

Edit: I fixed it with "nvram set bl_version=1.0.1.9"

That's because you never did a factory default reset after upgrading the CFE.

That's why tests all use the strings method to extract it from the bootloader rather than rely on the nvram value.

 

[Builder71]

That's because you never did a factory default reset after upgrading the CFE.

That's why tests all use the strings method to extract it from the bootloader rather than rely on the nvram value.

True!
Is there more stuff "under the hood" that justifies a reconfigure from scratch?

 

[dmarl27]

Upgraded from 1.0.1.1 to 1.0.1.9

I had a few free minutes today so I took the plunge and upgraded from 1.0.1.1 to 1.0.1.9.

One oddity- Ryzhov's script didn't have the 1.0.1.1 listed as a known version so I had to tweak one of the comparison values.

Upgrade went fine and so far the router seems ok. Thanks Ryzhov!

 

[zbeyuz]

I bought my router - RT-AC87U in Singapore, when I tried to change the region and channels + TX power to #a, it seems that the router reverts back after a commit and reboot.

Btw, I am running latest beta version of Merlin and it seems that I have to edit my CFE in order to change the region and channels as well as the TX power.

Can somebody please tell me how to edit CFE exactly? What are the steps?

Thanks in advance.

 

[GoNz0]

I bought my router - RT-AC87U in Singapore, when I tried to change the region and channels + TX power to #a, it seems that the router reverts back after a commit and reboot.

Btw, I am running latest beta version of Merlin and it seems that I have to edit my CFE in order to change the region and channels as well as the TX power.

Can somebody please tell me how to edit CFE exactly? What are the steps?

Thanks in advance.

it has been gone over enough times, read all the posts, backup the CFE you have and follow the instructions.

 

[chrisnasah]

Hi Guys,

need some help. So my router which is one of the first versions that came out, I had done a cfe update long way back when a fix for 64 NVRAM came out.

I am wanting to do clocking, so what would the best process would be for me to update my CFE, currently running 1.0.1.3 and I don't think I have the old file anywhere if needed.

Can anyone provide few pointers before I brick my router.

Thanks

 

[Pierino]

Follow the steps in the first post. It's all automated now.

 

[chrisnasah]

Follow the steps in the first post. It's all automated now.

thanks, I wasn't sure if I had to revert back to original CFE before using the automatic script.

Will give it a go tonight.

 

[Axel Foley]

Wireless channels and TX power - CFE edit

I've managed to update CFE to 1.0.1.9 on my RT-N66U and overclocked it to 662Mhz, working fine.

Now I'd like to improve my wireless tx power and number of available channels, and I read that I have to hex-edit CFE binary (I want to stay with fw 376.xx).

Question: is there a single post with instructions on what to edit? I found many partial instructions spread throughout the forum.

Should I dump my working CFE and edit it since it's up and running fine?

Thanks for this thread.

 

[KevTech]

Maybe this should be sticky.

 

[extremmax]

Hello,

So i take the same script for my Asus AC68-U or i need i diffrent?


Download and unpack update script
Get access to the RT-N66U console via Telnet/SSH/Serial and type:
Quote:
cd /tmp
wget http://files.ryzhov-al.ru/Routers/RT-N66U_CFE_update/cfe_n66u-1.0.1.9.tgz
tar -xzvf cfe_n66u-1.0.1.9.tgz


Best regards

 

[VANT]

i update my rt-n66u, and i think that everythink is ok

admin@RTN66U:/tmp# ./cfe_update.sh /dev/mtd0ro
Current CFE version is 1.0.1.4
[1/4] Dumping default NVRAM settings from original CFE...
nvram header found:
start   0x400
end     0x1374
len     3956
crc     0xa4
ver     0x01
[2/4] Preparing new CFE...
nvram header created:
start   0x400
end     0x1370
len     3952
crc     0x36
ver     0x01
[3/4] Checking differences between old and new NVRAM areas:
-bl_version=1.0.1.4
+bl_version=1.0.1.9
Everything looks good.
[4/4] Are you sure you want to flash a new CFE? [y,n]: y flashing...
Update completed. An old CFE is stored to cfe.old file, a new one - to cfe.new
It's strongly recommended to store them, just in case.
Please note, your personal MAC addresses in there, do not distribute them.

only len is difffrent ....

 

[VANT]

i can't back to my backup.
i have my cfe.old, use command ./cfe_update.sh ./cfe.old

admin@RTN66U:/tmp# ./cfe_update.sh ./cfe.old
Current CFE version is 1.0.1.4
[1/4] Dumping default NVRAM settings from original CFE...
nvram header found:
start   0x400
end     0x1374
len     3956
crc     0xa4
ver     0x01
[2/4] Preparing new CFE...
nvram header created:
start   0x400
end     0x1370
len     3952
crc     0x36
ver     0x01
[3/4] Checking differences between old and new NVRAM areas:
-bl_version=1.0.1.4
+bl_version=1.0.1.9
Everything looks good.
[4/4] Are you sure you want to flash a new CFE? [y,n]: y flashing...
Update completed. An old CFE is stored to cfe.old file, a new one - to cfe.new
It's strongly recommended to store them, just in case.
Please note, your personal MAC addresses in there, do not distribute them.
admin@RTN66U:/tmp# strings /dev/mtd0ro | grep bl_ver
bl_version=1.0.1.9
admin@RTN66U:/tmp#

current cfe is 1.0.1.9 but script says 1.0.1.4 ???
Anybody can help me ?

ps.
ok i back to my cfe 1.0.1.4 using command

mtd-write -i cfe.old -d pmon

but script cant't back to cfe.old, becouse have not command to write cfe.old...script can only flash cfe.new IMO

ps2.
i back to my old cfe becouse after i update cfe yesterday, today i have 2 Times loose internet connection...estabilished connection works (skype and others running) but new not. I must find where is the problem

IMO command

./cfe_update.sh ./cfe.old

not write cfe.old to mtd0, but only use cfe.old instead mtd0, so read cfe.old, backup again to cfe.old.... and finally write cfe.new