First of all, thank you so much for all your effort and all the information you share.
Is there any chance you could create a set of steps including the latest findings and the main instructions (page 3 of this thread) in order to convert a wrt3200acm into a wrt32x?
It would be really helpful to have everything combined in one post for all of us who don't have the knowledge you have guys.
Download tftpd:
http://tftpd32.jounin.net/
Place it somewhere you can find it, you'll need to set the default directory and put the rango.img in that location
Download PuTTY or another terminal program
Open your WRT3200ACM (screws in the feet of the front are enough to remove, then just pull it apart) and connect your USB-TTL cable left to right to the serial connection (far right side, white header):
GND - pin 1 - black
RX - pin 2 - white
TX - pin 4 - green
Connect your PC's network interface to one of the LAN interfaces on your router
IMPORTANT:
If you're running a firewall, DISABLE IT (that means McAfee, Kaspersky, Symantec, Bitdefender, Panda or any one of the other antivirus suites that includes the firewall)
When you've done that, if running Windows 10, go into the Windows firewall settings and disable that one as well, as it will have auto-renabled when you disabled the third party firewall
Settings on PC:
Set PC's IP to 192.168.1.254 / 255.255.255.0
Run PuTTY
Run tftpd
In PuTTY (or your terminal program), set it to serial and select the correct com port (you may need to check your Windows device manager to determine what com port your USB-TTL cable has been assigned)
Boot your router, watch for the interrupt boot message, hit a key to stop it. It will then boot you into the U-boot
Type (these IP settings may not be required, I used them because of familiarity with doing it in the past):
I've put a blank line after each command because the word wrap the forum is doing, be sure to get the whole command, copy it into notepad if you need to be sure.
Executing the run update_both_images makes the router connect to your tftp server and download the rango.img file
This is enough to get you to the WRT32X firmware, but if you want to change the U-boot to the WRT32X U-boot, do the following (this is NOT required):
Code:
SSH to your router from PuTTY and execute:
mtd write /uboot209.bin u-boot
reboot
Load into the U-boot with your console cable (as with above)
resetenv
reset
Log back into the U-boot with console cable
setenv -f silent
saveenv
IMPORTANT FINAL STEP:
Finally, when you're completely done, go to the Linksys support site and download the updated firmware for the 32X and update your router. There are fixes in that firmware for the wireless driver and for the Killer prioritization. Once you've done that (after the update is complete and it has rebooted on its own):
Cold boot (power cycle) your router. This is important or you may experience instability with the wireless connectivity.
If anyone sees anything I missed, please let me know and I'll update this post.
Last edited by Beradon on Tue Oct 03, 2017 22:02; edited 2 times in total
Just wanted to let everyone know of some updates coming to the firmware as well...
I received an evaluation version of the actual WRT32X device to review, and based on my review, Linksys has contacted me for more input. They plan on updating the firmware with some or all of the following features:
MAC Address and IP address visibility on the Killer Prioritization UI
MAC Address visbility on the Devices page
They've also said they will consider including the VPN Server functionality, as the firmware already has client functionality, which is rare for a consumer device.
I also mentioned that the port forwarding UI is very limited and suggested they add the capability for different internal vs external ports, as well as the option to comma-separate different ports so you dont need to have a separate line for every port (if they aren't consecutive numbers)
Just wanted to let everyone know of some updates coming to the firmware as well...
I received an evaluation version of the actual WRT32X device to review, and based on my review, Linksys has contacted me for more input. They plan on updating the firmware with some or all of the following features:
MAC Address and IP address visibility on the Killer Prioritization UI
MAC Address visbility on the Devices page
They've also said they will consider including the VPN Server functionality, as the firmware already has client functionality, which is rare for a consumer device.
I also mentioned that the port forwarding UI is very limited and suggested they add the capability for different internal vs external ports, as well as the option to comma-separate different ports so you dont need to have a separate line for every port (if they aren't consecutive numbers)
If your in contact, ask them why they went with dead openwrt when the last commit is over a year old, and LEDE is the standard now.
And, why they haven't cleaned out the fan_ctrl.sh script from cron. WRT1900ACv1 is no longer really relevant .
Just wanted to let everyone know of some updates coming to the firmware as well...
I received an evaluation version of the actual WRT32X device to review, and based on my review, Linksys has contacted me for more input. They plan on updating the firmware with some or all of the following features:
MAC Address and IP address visibility on the Killer Prioritization UI
MAC Address visbility on the Devices page
They've also said they will consider including the VPN Server functionality, as the firmware already has client functionality, which is rare for a consumer device.
I also mentioned that the port forwarding UI is very limited and suggested they add the capability for different internal vs external ports, as well as the option to comma-separate different ports so you dont need to have a separate line for every port (if they aren't consecutive numbers)
If your in contact, ask them why they went with dead openwrt when the last commit is over a year old, and LEDE is the standard now.
And, why they haven't cleaned out the fan_ctrl.sh script from cron. WRT1900ACv1 is no longer really relevant .
I dont have that level of contact I could only hope they'd put me into contact with someone like that, but they had me talk to the 'special WRT32X team' and he said he would forward my suggestions to the devs.
.