RouterTech Firmware 2.97 Discussion

All about firmwares for routers. Support for RouterTech firmwares is here too.
Post Reply
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Tue Feb 14, 2012 9:41 pm

Run this from telnet

Code: Select all

setenv mac_ap 00:11:22:33:44:55
Substitute the correct wireless MAC for "00:11:22:33:44:55".
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
harimkb
Newbie
Newbie
Posts: 8
Joined: Fri Jul 29, 2011 3:40 pm

Re: RouterTech Firmware 2.97 Discussion

Post by harimkb » Wed Feb 15, 2012 8:44 am

chief , thank you , used "setenv mac_ap xx:xx:xx:xx:xx:xx" to set my wifi ap address and every things works fine (except for staus led - not a problem though...)

no problems with this firmware for huawei wa1003a for this ROM , no hanging , no heating , very stable , i thank once again every one for all this effort! :mrgreen:
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Wed Feb 15, 2012 1:28 pm

You are welcome :)
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Wed Feb 15, 2012 7:09 pm

Anyone who has successfully upgraded to v2.97 can assist us by following the procedure outlined in this thread: viewtopic.php?f=3&t=4191
(but only if you did not supply that information for v2.96). Thanks. :)
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
User avatar
Pondera
Experienced
Experienced
Posts: 254
Joined: Sun Mar 25, 2007 4:06 pm
Location: Brindisi (Italy)

Re: RouterTech Firmware 2.97 Discussion

Post by Pondera » Sun Feb 19, 2012 1:11 am

Problems with a DSL-504T A1 via web upgrading from:

RouterTech_3.6.0D_20110502_2.96_AR7RD-4Ports_Adam2-4mb-flash

to:

RouterTech_3.6.0D_20120130_2.97_AR7RD-4Ports_Adam2-4mb-flash

The serial console output during upgrading:

Code: Select all

Received signal 15, exiting...
select() exited with errno = 4
May  2 01:14:48 cfgmgr(fdb): May  2 01:14:48 | Firewall NAT service stopped
Exiting
root: setenv: RouterTech: defragRouterTech: received the "DEFRAG" command - defragmenting the environment ...
menting the bootloader environment

/usr/sbin/mini_httpd: exiting due to signal 15


****************** NSP Firmware Upgrade ******************
Mounting PROC on /var/proc...OK
Mounting DEV on /var/dev...OK
Pivoting / to /var...OK
Changing work dir to / ...OK
Unmounting /flash/proc...OK
Unmounting /flash/dev...OK
Unmounting /flash...OK
Upgrading flash memory...
FLASH /tmp/fw.bin...
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 128
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 136
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 144
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 152
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 160
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 168
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 176
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Progress: |*                               |  3%Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 184
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 192
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 64, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 24, datum is 97a8
end_request: I/O error, dev 1f:04 (mtdblock), sector 200
Last[3] is 64, datum is 97a8
and after disconnecting power:

Code: Select all

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD > 
Press any key to abort OS load, or wait 8 seconds for OS to boot...
File for wrong Endian!
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Sun Feb 19, 2012 8:37 am

Hmmm ... looks like a trashed environment. Check your environment, and you'll probably find that it has default values. Since you have a serial console, it should be easy to set the correct environment variables, and then upgrade with the pctool.

How did this happen? It is anyone's guess - but it may have been during defragmentation. Unfortunately, these things sometimes happen - which is why upgrading a firmware is always a risky process.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
User avatar
Pondera
Experienced
Experienced
Posts: 254
Joined: Sun Mar 25, 2007 4:06 pm
Location: Brindisi (Italy)

Re: RouterTech Firmware 2.97 Discussion

Post by Pondera » Sun Feb 19, 2012 9:01 am

Instead RT 2.96 is very stable: never a problem during upgrading, even if you try to upgrade from other firmwares.
Have you changed anything from 2.96 to 2.97 regarding the upgrade process?
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Sun Feb 19, 2012 9:56 am

Pondera wrote:Instead RT 2.96 is very stable: never a problem during upgrading, even if you try to upgrade from other firmwares.
That is very good to know - but the conclusion drawn from that is not correct. Whatever happened did so under the auspices of 2.96 - it is always the old firmware that manages the process of upgrading to a new firmware.
Pondera wrote:Have you changed anything from 2.96 to 2.97 regarding the upgrade process?
Nope.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
User avatar
Pondera
Experienced
Experienced
Posts: 254
Joined: Sun Mar 25, 2007 4:06 pm
Location: Brindisi (Italy)

Re: RouterTech Firmware 2.97 Discussion

Post by Pondera » Sun Feb 19, 2012 1:05 pm

Upgrading via TIUpgrade, the v2.97 bricks the DSL-504T again. It happened also with the v2.94, as we discussed here:

viewtopic.php?p=46445#p46445

The v2.95 worked very well instead.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Sun Feb 19, 2012 5:16 pm

Pondera wrote:Upgrading via TIUpgrade, the v2.97 bricks the DSL-504T again.
Well, there is no reason why that should happen. You may want to post the boot log from the serial console (both during the tiupgrade process and when 2.97 boots up after the upgrade). I would say to check your flash chip, because what the earlier log showed was write-errors that should not normally happen.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
takla
Newbie
Newbie
Posts: 8
Joined: Tue Jan 12, 2010 7:43 am

Re: RouterTech Firmware 2.97 Discussion

Post by takla » Sun Feb 19, 2012 9:07 pm

I just upgraded my Pluscom AWR7200 to 2.97 and there were no problems. I've only been running it an hour or so but I noticed a small improvement, which is that I didn't need to set an environment variable "setenv vlynq_polarity high" to have the wireless work.

Thanks to everyone at RT for continuing to support and improve these firmwares.
User avatar
Pondera
Experienced
Experienced
Posts: 254
Joined: Sun Mar 25, 2007 4:06 pm
Location: Brindisi (Italy)

Re: RouterTech Firmware 2.97 Discussion

Post by Pondera » Mon Feb 20, 2012 1:26 am

Pondera wrote:Router=D-Link/DSL-504T; Board=AR7RD; Wireless=No; Firmware=RouterTech_3.6.0D_20110502_2.96; Bootloader=Adam2; Ports=4; Mem=16384kb; Flash=4096kb; Flash_type=AMD; Manufacturer=ATMEL.

Note: upgrading via the web interface is possible from 2.00 firmware version!
Serial console optput during upgrading from 2.96 to 2.97 via TIUpgrade:

Code: Select all

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD >
Press any key to abort OS load, or wait 8 seconds for OS to boot...
Rebooting the system in 3 secs...

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD >
Press any key to abort OS load, or wait 8 seconds for OS to boot...
Erasing from 0xb03f0000 to 0xb0400000.
FlashEraseBlock(b03f0000,b03fffff);
.
Erase Successful.
.
Erasing from 0xb0010000 to 0xb03f0000.
FlashEraseBlock(b0010000,b03effff);
..............................................................
Erase Successful.

Flash 'Write Byte' operation Failed: sts=00000020
ERROR: Flash write aborted b0018e0b
...................Flash 'Write Byte' operation Failed: sts=00000020
ERROR: Flash write aborted b0144c98
...........................Rebooting the system in 3 secs...

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD >
Press any key to abort OS load, or wait 8 seconds for OS to boot...
Error in checksum!
Serial console optput during boot up after the upgrade:

Code: Select all

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD >
Press any key to abort OS load, or wait 8 seconds for OS to boot...
Error in checksum!
Serial console output during reupgrading to 2.96 via TIUpgrade and boot up:

Code: Select all

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD > 
Press any key to abort OS load, or wait 5 seconds for OS to boot...
Rebooting the system in 3 secs...

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD > 
Press any key to abort OS load, or wait 8 seconds for OS to boot...
Erasing from 0xb03f0000 to 0xb0400000.
FlashEraseBlock(b03f0000,b03fffff);
.
Erase Successful.
.
Erasing from 0xb0010000 to 0xb03f0000.
FlashEraseBlock(b0010000,b03effff);
..............................................................
Erase Successful.

...........................................Flash 'Write Byte' operation Failed: sts=00000020
ERROR: Flash write aborted b02bdcb8
...Rebooting the system in 3 secs...

ADAM2 Revision 0.22.07
(C) Copyright 1996-2009 Texas Instruments Inc. All Rights Reserved.
(C) Copyright 2003 Telogy Networks, Inc.
Usage: setmfreq [-d] [-s sys_freq, in MHz] [cpu_freq, in MHz]
Memory optimization Complete!

Adam2_AR7RD > 
Press any key to abort OS load, or wait 8 seconds for OS to boot...
Launching kernel LZMA decompressor.
Kernel decompressor was successful ... launching kernel.

LINUX started...
Config serial console: ttyS0,38400
Auto Detection SANGAM chip
CPU revision is: 00018448
Primary instruction cache 16kb, linesize 16 bytes (4 ways)
Primary data cache 16kb, linesize 16 bytes (4 ways)
Number of TLB entries 16.
Linux version 2.4.17_mvl21-malta-mips_fp_le (developers at RouterTech dot Org) #1 Mon May 2 01:09:35 BST 2011
Determined physical RAM map:
 memory: 14000000 @ 00000000 (reserved)
 memory: 00020000 @ 14000000 (ROM data)
 memory: 00fe0000 @ 14020000 (usable)
[...]
As we can see despite the writing error the 2.96 checksum pass.
Instead the 2.97 checksum doesn't pass.
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Mon Feb 20, 2012 7:29 am

The evidence is clear - you have a bad flash chip, or bad sectors on your flash chip, and that is why you are getting write errors. Smaller firmware images may be able to be contained in areas outside the bad sectors, which is why 2.96 may be written correctly to flash, while 2.97, which is at least 4kb bigger, seems too big to fit within the good sectors. The problem may have been there from the start (perhaps the manufacturer was not expecting a firmware that is so big, and therefore was happy to ship a device in which the flash chip's full 4mb size could not be used) - or it may simply be an issue of wear and tear on the flash.

So far, you have been unable to get 2.97 written correctly to your flash, so this is clearly not an issue with 2.97 (which has absolutely nothing to do with how you are trying to write it to flash). When you manage to write it to flash without any write errors, then we can discuss how it works or does not work. As you said, we have been here before, in your attempts to upgrade to 2.94. So please let us not repeat that discussion here, as we seem in danger of doing now. Sort out your bootloader, or your flash chip, or, try a smaller firmware image (e.g., the standard 2mb-flash 2.97 firmware), and you may be able to use 2.97.
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
flosi
Newbie
Newbie
Posts: 2
Joined: Mon Feb 20, 2012 11:21 am

Re: RouterTech Firmware 2.97 Discussion

Post by flosi » Tue Feb 21, 2012 11:41 am

On my dlink d624t i have tryed to install the new firmware direclty from browser "crome" starting from version 2.91, apparently all worked fine but after the reboot my router was bricked .
After tryed several times with pctool v 2.3 i had success and now my router have a new firmware, the reason of the insuccess for several time was a problem with erasing that around at fifty percent of the procedure had locked the program with the progress bar running fast disordered ( in windows task manager showed program not respond ) my windows version is XPprofessional 32bit sp3
All works fine no problem with wifi, status led and ADSL connection :D

sorry for my english
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12064
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: RouterTech Firmware 2.97 Discussion

Post by thechief » Tue Feb 21, 2012 12:58 pm

flosi wrote:After tryed several times with pctool v 2.3 i had success and now my router have a new firmware, the reason of the insuccess for several time was a problem with erasing that around at fifty percent of the procedure had locked the program with the progress bar running fast disordered
Pctool v2.3 does not work well with Adam2-based routers. You need pctool v2.1 for Adam2.
flosi wrote:All works fine no problem with wifi, status led and ADSL connection :D
Excellent!
flosi wrote:sorry for my english
It is good enough. :)
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
Post Reply