Here is the image of the WRT32X firmware, self-compiled out of GPL sources provided yesterday as Linksys only provides sysupgrade.
I simplified, by a mile, the method I initially used with the sysupgrade file.
Set PC's IP to 192.168.1.254 / 255.255.255.0 and serve provided rango.img via TFTP and after reboot you'll be running WRT32X firmware
To flash and boot served image issue in U-Boot:
To reverse the process:
Download and serve via TFTP any WRT3200ACM firmware file (only full factory images), be that LEDE, OpenWrt, oficial firmware and change the name to rango.img
And use those commands respectively:
this is great. (i/m getting my wrt3200acm tomorrow, and hope to make it a wrt32x asap.)
is u-boot accessible any way other than serial port?
does stock wrt3200acm firmware have ssh access?
thank you!
Nope and nope. While in theory you could issue all those setenv commands from a running OpenWrt via fw_setenv you still need to flash the firmware via u-boot console, so unfortunately you need a serial connection.
Make sure to ssh in and remove the fan_ctrl.sh cron job. I giggled when I saw that in there (seems OpenWRT is a bit behind to say the least, but it's still a step in the right direction).
there is another step to complete the conversion from wrt3200acm to wrt32X:
i edited the mtd4 dump to update to the wrt32X values:
hw_version=48SAM204.0GA
modelNumber=WRT32X
however, mtd4 is write-protected and cannot be unlocked with the mtd tools in dd-wrt or lede
thus i think the process for complete transition of a wrt3200acm to wrt32x should also include modifying those devinfo values from the u-boot command line via serial port. as i recall, the devinfo partition can be modified using tools that are like the nvram tool:
devinfo set hw_version=48SAM204.0GA
devinfo modelNumber=WRT32X
devinfo commit
but dd-wrt/lede do not have access to the devinfo tool.
although mtd4 cannot be unlocked, mtd3 can be, and mtd4 is mapped to a segment within mtd3.
so - i editted the mtd3 partition to include the updated hw_version and modelNumber as above. i think this completes the conversion of wrt3200acm to wrt32x
I have transformed my wrt3200 in wrt32x, but the wifi performance is pretty far from expected (116 Mbits in 5GHz) with iperf in an OSX. Compared to my telco router that is making 250 Mbits.
Original software was making 450 Mbits. For now I´ve moved back to stock. I might test DD-WRT or Lede
is there any development on a lede image that can be flashed on the wrt32x platform (codename venom), or do i have to cross-flash back to wrt3200acm to use lede? i have tried using the wrt3200acm images but the sysupgrade fails. if i replace the text 'rango' with 'venom' in the image, the sysupgrade works, but the router hangs.
i'm alittle confused, becasue the stock firmware runs openwrt, so sysupgrade is available.
thanks!
Although this is the most recent sources for the WRT32X (matching their latest WRT32X firmware release as well), this seems to be the same firmware version from latest WRT3200ACM firmware release.
Interesting to note, the latest firmware release for WRT32X (FW_WRT32X_1.0.170828.208) which is still available for download on Linksys server (despite link removed), the source file WRT32X_gpl_v1.0.170828.208.tar, despite having the same version number in the file name has much newer material within the sources. The firmware for 88W8964 as an example, is much newer.
The source file WRT32X_gpl_v1.0.170828.208.tar is up-to-date as far as 2017-09-20 for the sources that are included. Whereas, the latest WRT32X (FW_WRT32X_1.0.170828.208) firmware release of the same version number/name, the materials included are dated up until 2017-07-16.
So the more developer-minded folks here will understand what's included much better since that is above my skill level, but there quite likely is newer sources for kernel driver as well.
Does anyone know if these sources can be used to compiled a kernel driver for WRT3200ACM?
Hello! I used this lines to convert my wrt32x to a wrt3200acm with running lede. but a reboot fails. it seems like those env's arent persistent. surely i do "saveenv" before booting - i also checked fw_printenv and the output looks identical on mtdparts, bootargs etc...
Can you point me into a proper direction here?