[solved]foolish error wrt54g v2
Posted: Sat Jan 12, 2013 12:01 pm
Hi all
I had both firmware version 1.4.7 and 1.5.7, having read the forums I discovered not to install x.5.x on a wrt54g, yet on flashing from dd-wrt i still managed to flash the wrong file. I shouldn't enjoy scotch and flash routers!
The router will now boot (slowly) and I can access the web interface. When I get to the firmware upgrade page I can select the 1.4.7 file, tells me its uploading then just sits there, i'm guessing this is down to the ram limitation.
I've tried catching it via TFTP but sofar its not caught, it could just be down to my timing. Tried starting it just after it responds to a ping. Doing a 30/30/30 reset doesn't seem to work as its still on 192.168.2.1 which I set compared to 192.168.1.1 as default.
I can ssh to the router and have managed to scp across a micro build of dd-wrt and run sysupgrade -n /tmp/[firmware_file] but it just reboots back to 1.5.7
Is there anything else I can try without opening it up? via telnet, ssh or the web interface.
Cheers
Edit
I've managed to reset it back to default by ssh'ing in and running the 'firstboot' command
Tried uploading various firmwares but it seems only the micro dd-wrt build has a small enough file size to transfer to /tmp correctly. (Everything else fails below 90% transfered)
I can upload micro using the web interface & it seems to complete successfully but on reboot I'm back into 1.5.7, the same happens when running the sysupgrade command via ssh. Is there any unnecessary processes I can kill whilst ssh'd to free up ram to try to get it to run through?
I've tried using mtd as per the openwrt forums but I get the below
root@Gargoyle:/tmp# mtd -r write dd-wrt.v24_micro_generic.bin firmware
Could not open mtd device: firmware
Can't open device for writing!
So I'm guessing thats not supported or do I have the syntax wrong?
Edit 2
Further digging gives
root@Gargoyle:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "cfe"
mtd1: 003b0000 00010000 "linux"
mtd2: 002c3400 00010000 "rootfs"
mtd3: 00080000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "nvram"
the next question is can I use mtd to upload to any of the above without bricking any further?
I had both firmware version 1.4.7 and 1.5.7, having read the forums I discovered not to install x.5.x on a wrt54g, yet on flashing from dd-wrt i still managed to flash the wrong file. I shouldn't enjoy scotch and flash routers!
The router will now boot (slowly) and I can access the web interface. When I get to the firmware upgrade page I can select the 1.4.7 file, tells me its uploading then just sits there, i'm guessing this is down to the ram limitation.
I've tried catching it via TFTP but sofar its not caught, it could just be down to my timing. Tried starting it just after it responds to a ping. Doing a 30/30/30 reset doesn't seem to work as its still on 192.168.2.1 which I set compared to 192.168.1.1 as default.
I can ssh to the router and have managed to scp across a micro build of dd-wrt and run sysupgrade -n /tmp/[firmware_file] but it just reboots back to 1.5.7
Is there anything else I can try without opening it up? via telnet, ssh or the web interface.
Cheers
Edit
I've managed to reset it back to default by ssh'ing in and running the 'firstboot' command
Tried uploading various firmwares but it seems only the micro dd-wrt build has a small enough file size to transfer to /tmp correctly. (Everything else fails below 90% transfered)
I can upload micro using the web interface & it seems to complete successfully but on reboot I'm back into 1.5.7, the same happens when running the sysupgrade command via ssh. Is there any unnecessary processes I can kill whilst ssh'd to free up ram to try to get it to run through?
I've tried using mtd as per the openwrt forums but I get the below
root@Gargoyle:/tmp# mtd -r write dd-wrt.v24_micro_generic.bin firmware
Could not open mtd device: firmware
Can't open device for writing!
So I'm guessing thats not supported or do I have the syntax wrong?
Edit 2
Further digging gives
root@Gargoyle:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "cfe"
mtd1: 003b0000 00010000 "linux"
mtd2: 002c3400 00010000 "rootfs"
mtd3: 00080000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "nvram"
the next question is can I use mtd to upload to any of the above without bricking any further?