CFE bootloader update

[lfbb]

lfbb@ubuntu:~$ cd Desktop/cfe
lfbb@ubuntu:~/Desktop/cfe$ ./cfe_update.sh cfe_old.bin cfe_new.bin
[1/4] Dumping default NVRAM settings from your CFE...
nvsimple 0.2 (c) theMIROn
nvram start 0x400
nvram end 0x1410
nvram len 4092
nvram crc 0x14
nvram ver 0x01
passing "sdram_init"="0x0000"
passing "sdram_config"="0x0000"
passing "sdram_refresh"="0x0000"
passing "sdram_ncdl"="0x00000000"
passing ""="<$P*H"
Segmentation fault (core dumped)
[2/4] Modifying NVRAM settings (silent step)...
[3/4] Creating new CFE...
4092+0 records in
4092+0 records out
4092 bytes (4.1 kB) copied, 0.007589 s, 539 kB/s
[4/4] Checking differences between NVRAM from old and new CFE's
Segmentation fault (core dumped)
0a1,5
> odmpid=ASUS
> sdram_config=0x0000
> sdram_init=0x0419
> sdram_ncdl=0x00000000
> sdram_refresh=0x8040
If you see only two differences: one is for 'bl_version' and second is a new 'odmpid=ASUS' variable then all step are done! New CFE image 'cfe_new.bin' is prepared for flash.

Tried with CFE 1.0.1.3 as original file and this is what I get.

- lfbb

 

[jbombs16]

I updated to the latest ASUS firmware (3.0.0.4.260) and then flashed the latest Merlin.

I ran steps 1 and 2 and received this output:

jay@jay-VirtualBox:~/cfe$ ./cfe_update.sh cfe.original cfe.new
[1/4] Dumping default NVRAM settings from your CFE...
too small file size: Success
[2/4] Modifying NVRAM settings (silent step)...
[3/4] Creating new CFE...
4092+0 records in
4092+0 records out
4092 bytes (4.1 kB) copied, 0.0306782 s, 133 kB/s
[4/4] Checking differences between NVRAM from old and new CFE's
0a1,5
> odmpid=ASUS
> sdram_config=0x0000
> sdram_init=0x0419
> sdram_ncdl=0x00000000
> sdram_refresh=0x8040
If you see only two differences: one is for 'bl_version' and second is a new 'odmpid=ASUS' variable then all step are done! New CFE image 'cfe.new' is prepared for flash.

-----

The differnces don't seem to be what I am supposed to get. Did the script work correctly?

If so, how to I "Place cfe.new back to router" for step 3? I am using putty to ssh to the router.

3. Flashing new CFE.
Place cfe.new back to router and run:

$ mtd-write -i cfe.new -d pmon


Thanks in advance

 

[lfbb]

The differnces don't seem to be what I am supposed to get. Did the script work correctly?

Which Linux distro are you using? I'm on Ubuntu 12.04.1 LTS 32 bit.

- lfbb

 

[jbombs16]

Which Linux distro are you using? I'm on Ubuntu 12.04.1 LTS 32 bit.

- lfbb

I am running the same using virtual machine - Could that be the issue?

 

[lfbb]

I am running the same using virtual machine - Could that be the issue?

Let's wait for rhyzov's reply.

You used the 1.0.1.3 CFE as cfe.original?

- lfbb

 

[ryzhov_al]

Tried with CFE 1.0.1.3 as original file and this is what I get.

No, no use for the CFE 1.0.1.3 as original file! Please, do not update CFE with that.

 

[ryzhov_al]

I updated to the latest ASUS firmware (3.0.0.4.260) and then flashed the latest Merlin.

I ran steps 1 and 2 and received this output:
...
The differnces don't seem to be what I am supposed to get. Did the script work correctly?

This is a old archive. A new one prints

nvsimple 0.2 (c) theMIROn

to the console. Please, download new archive (link stays the same) and try again.

 

[lfbb]

lfbb@ubuntu:~/Desktop/cfe$ ./cfe_update.sh cfe_old.bin cfe_new.bin
[1/4] Dumping default NVRAM settings from your CFE...
nvsimple 0.2 (c) theMIROn
nvram start 0x400
nvram end 0x13d8
nvram len 4036
nvram crc 0x3f
nvram ver 0x01
[2/4] Modifying NVRAM settings (silent step)...
[3/4] Creating new CFE...
4092+0 records in
4092+0 records out
4092 bytes (4.1 kB) copied, 0.02426 s, 169 kB/s
[4/4] Checking differences between NVRAM from old and new CFE's
0a1,7
> @=
> �=
> �@=
> =
><�=
> =
> �2=
4c11
< bl_version=1.0.1.2
---
> bl_version=1.0.1.3
64c71
< pci/1/1/regrev=3
---
> pci/1/1/regre�����=
176d182
< wait_time=3
If you see only two differences: one is for 'bl_version' and second is a new 'odmpid=ASUS' variable then all step are done! New CFE image 'cfe_new.bin' is prepared for flash.

This is what I get... don't know what am I doing wrong.

- lfbb

 

[jbombs16]

I downloaded the archive at this link:

https://github.com/downloads/ryzhovau/asuswrt-ryzhov/cfe_n66u-1.0.1.3.tgz


I got the same results:

jay@jay-VirtualBox:~/cfe1$ ./cfe_update.sh cfe.original cfe.new
[1/4] Dumping default NVRAM settings from your CFE...
too small file size: Success
[2/4] Modifying NVRAM settings (silent step)...
[3/4] Creating new CFE...
4092+0 records in
4092+0 records out
4092 bytes (4.1 kB) copied, 0.0433392 s, 94.4 kB/s
[4/4] Checking differences between NVRAM from old and new CFE's
0a1,5
> odmpid=ASUS
> sdram_config=0x0000
> sdram_init=0x0419
> sdram_ncdl=0x00000000
> sdram_refresh=0x8040
If you see only two differences: one is for 'bl_version' and second is a new 'odmpid=ASUS' variable then all step are done! New CFE image 'cfe.new' is prepared for flash.

 

[lfbb]

jay@jay-VirtualBox:~/cfe1$ ./cfe_update.sh cfe.original cfe.new

I'm using VMWare Workstation 9.0.1 build-894247

- lfbb

 

[lfbb]

Anyone managed to get this new code to work?

- lfbb

 

[lfbb]

rhyzov, can you post what the output should be with this new code? Which Linux distro are you using?

- lfbb

 

[jbombs16]

Can someone post a link to the updated archive?

 

[lfbb]

It's on the first page of this thread.

- lfbb

 

[RogerSC]

No, no use for the CFE 1.0.1.3 as original file! Please, do not update CFE with that.

It sounds like one cannot do this update unless one happens to have kept the "cfe.original" (1.0.1.2) from the original update from 1.0.1.2 to 1.0.1.3? The reason for this, I assume, is that the update from 1.0.1.2 to 1.0.1.3 is re-done with this bug fixed?

Am I missing something, or is this true? Does the contents of the CFE bootloader 1.0.1.2 different for each router, or is there somewhere that I can get the 1.0.1.2 version that would work for re-updating the CFE bootloader on my router? I believe that I got rid of the cfe.original that I generated and used after the dust settled on the original update.

 

[lfbb]

Roger, if you want I can send you mine 1.0.1.2 cfe just for you to try this new update, as it seems no one is acomplishing that.

- lfbb

 

[RMerlin]

The CFE will be different based on which region you are in (i.e. the US CFE will be different from a EU one).

 

[RogerSC]

The CFE will be different based on which region you are in (i.e. the US CFE will be different from a EU one).

If that's the only difference, I'm in the US (California)...so if I could find one of those, I'd be glad to spend some time looking at this.

Thanks.

 

[lfbb]

The CFE will be different based on which region you are in (i.e. the US CFE will be different from a EU one).

Merlin, did you manage to get this new code to work as expected?

- lfbb

 

[themiron]

Merlin, did you manage to get this new code to work as expected?

- lfbb

what exactly issues do you have with nvsimple? it's totally unclear what you're afraid of, please clarify. thanks.