Based on my exploration of the various partitions' stock dumps, the partition mtd5 on the WD009 does not contain U-Boot parameters - in fact it's mostly the default setting for the stock firmware:
- handful of IP addresses between 0x00 and 0x40
- a block of device self-identification from 0x400 to 0x560, with a SHA256 hash trailing it at 0x510:
- Manufacturer and device name
- Firmware version
- MAC address
So unless the u-boot env NVRAM format has changed significantly since I last checked, no, mtd5
/params
should not contain the U-Boot env.
However mtd2
(the actual config
/uboot-env
partition) does contain relevant information, though it seems to me that e.g. the segment from 0x2000, and another segment at 0x6000 contain properties meant for the wireless configs. Then mtd3
contains some MAC addresses and such.
Also, you can easily create a dump of the flash even without telnet access - the dumb stock OS will happily execute a script called EnterRouterMode.sh
placed on the root of any attached storage medium, which then you can easily use to back every partition up, something like this:
#!/bin/sh
dd if=/dev/mtd0 of=$(pwd)/backup_mtd0
dd if=/dev/mtd1 of=$(pwd)/backup_mtd1
[ repeat the same as above but for mtd2..8 ]
In theory, $(pwd)
in this context should be the volume the script is run from, but fair warning, I have not tested this at all - you might have better luck with specifying the appropriate mount point. Either way, with this script you can easily back everything up without even touching the device, just plop it on an SD card or USB flash drive, plug it in, and boot it up.
And no, overall I don't think the kernel is larger than the 1536kB size, however I did not check thoroughly, and honestly, I see no reason to go back to the original software - sure, OpenWrt needs a bit of tinkering to get to the (almost) same level of functionality as the stock firmware, but overall I found it much more stable and reliable, not to mention the massive kernel version difference (2.6.36 vs 5.4.x).