Note: don't try this without having a working JTAG. I didn't have a JTAG or serial console cable for this Netgear, but I got the router very cheap, and was happy to throw it in the bin if it all went wrong. Fortunately, nothing went wrong - but it could very easily have gone horribly wrong, ending up with a router that was irrecoverable.
Anyway, this is what I did:
1. Got a cheapo DG834G V2 from Ebay. It came with Netgear's firmware v2.10.22
2. Got the latest DGTeam firmware from here: http://dgteam.ilbello.com/index.php?pid=9
3. Pressed the reset button, and then upgraded the firmware to the DGTeam firmware (via the web interface) - the purpose of this step was to get a working telnet and an up-to-date firmware to work with
4. Configured the router for my ISP, and connected to the net (the purpose of this step was to download the psp bootloader that I was going to use)
5. Connected to the router (192.168.0.1) via telnet (username=admin; password=password)
6. Ran "cat /proc/ticfg/env" and copied the contents to a backup file on my hard disk
6. Changed to the /var/ directory, and downloaded my psp bootloader with "wget" (a copy of the one I used (4MB/16MB, AMD flash) is attached below)
8. Copied the bootloader over
Code: Select all
cp boot.bin /dev/mtdblock/2
9. Rebooted the router, connected with the pctool, and flashed the RT firmware with it
10. Rebooted the router, configured it, restored the MAC addresses from the backup original environment
11. Connected to RouterTech, and started writing this!
As you can see, it was all fairly painless for me. Of course your mileage may vary. Don't try this if you're not happy to throw the router in the bin if it gets bricked.
Only one problem - in my unseemly haste, I did not back up the Netgear led.conf file, so the LEDs are all wrong (in fact, only two of them light up, and only one of those two is correct). I tried any old led conf file (aam6020v), and all it did was cause an endless reboot cycle. So I removed it with the pctool. Will see whether they all will cause endless reboots. The wrong LEDs is not an issue for me, but watch this space as to whether it gets sorted. If you love your LEDs, then don't try this!
Here is a copy of the current environment
Code: Select all
/var # printenv|sort -f
BOOTCFG m:f:"mtd1"
bootloaderVersion 1.4.0.9
BUILD_OPS 0x201
CPUFREQ 150000000
cron_enable 1
FLASHSZ 0x00400000
HWA_0 00:0f:b5:xx:xx:xx
HWA_1 00:0f:b5:xx:xx:xx
HWRevision Unknown
IPA 192.168.1.1
MAC_PORT 1
MEMSZ 0x01000000
MIPSFREQ 150000000
MODETTY0 38400,n,8,1,hw
MODETTY1 38400,n,8,1,hw
modulation 0xff
mtd0 0x9009e000,0x90400000
mtd1 0x90020090,0x9009e000
mtd2 0x90000000,0x90010000
mtd3 0x90010000,0x90020000
mtd4 0x90020000,0x90400000
ProductID AR7WRD
PROMPT psbl>
SerialNumber none
SYSFREQ 125000000
vcc_encaps0 0.0
vcc_encaps1 0.0
vcc_encaps2 0.0
vcc_encaps3 0.0
vcc_encaps4 0.0
vcc_encaps5 0.0
vcc_encaps6 0.0
vcc_encaps7 0.0
/var #