|
2005-12-07
, 11:06
|
|
Posts: 78 |
Thanked: 1 time |
Joined on Sep 2005
@ San Francisco, CA
|
#2
|
|
2005-12-07
, 11:28
|
Posts: 111 |
Thanked: 9 times |
Joined on Nov 2005
@ Hong Kong
|
#3
|
|
2005-12-07
, 14:58
|
Posts: 51 |
Thanked: 4 times |
Joined on Nov 2005
@ Midlands, UK
|
#4
|
Yes, I think re-flashing the firmware should work.
While updating to the latest firmware I noticed that the lock code was gone. It only came back after doing a full restore from a backup.
The Following User Says Thank You to jaycee For This Useful Post: | ||
|
2005-12-07
, 16:08
|
Posts: 111 |
Thanked: 9 times |
Joined on Nov 2005
@ Hong Kong
|
#5
|
I saw the exact opposite.
After flashing from version 45-7 to 45-8, the lock code /wasn't/ reset to 12345, but stayed as the lock code I'd specified after my first bootup.
jc
I'm not finding it anywhere on the filesystem, but /dev/mtdblock1 seems to hold config info. Has anyone decoded this yet, or found a tool that does so?
(For what its worth, the partition layout seems to be:
/dev/mtdblock0 - bootloader
/dev/mtdblock1 - config info
/dev/mtdblock2 - kernel
/dev/mtdblock3 - initrd (jffs2)
/dev/mtdblock4 - root fs (jffs2)
..)