thank you again for your time helping me, i really appreciate this.
i noticed the cpu stall myself in the logs, it could be faulty, i purchased this in broken state, i just thought it would make a faster vpn throughput than my current router with its 1.8ghz cpu.
seems odd that it will take the image if cpu faulty unless the file writes straight to the nand and bypasses the cpu, again above my knowledge i am afraid.
i noticed the two file sizes are different
image file named flat-FW_WRT32x.......img is 11.8MB but the EW_WRT32X_1.0.17919.......img is 13.1MB
i will try what you suggested when i get home this evening.
again massive thanks for your time in replying and help with this
Yes flat-FW_WRT32X_1.0.180404.58.img from a different guy (same thread). The explanation of his conversion method is good and others have repeated his steps with success on other files. It's also the latest "official" build available.
Maybe it's a bad power supply? Who knows, maybe it's toast. Have you examined the board?
Nothing visible on the board no nasty electrical burns or smells nothing like that, looks mint to be honest.
it's a strange one as you say everything seems to look ok comparing the output to others i've seen posted.
I've tried another power supply none genuine but correct volts/amps/polarity still same...
Is there a DD-WRT or openwrt image that can be flashed from TFTP server? maybe worth trying that, i seemed to have tried everything else now lol although i dont expect it will work but worth a go if there is an image.
Gutted really gutted, when it took the image first time i really thought it was there.
Is there a erase nvram command? before i setenv ip, subnet, server etc?
Thanks again for your help
The DD-WRT and OpenWRT images are not formatted for serial flashing; we have the correct flat images.
Have you tried flashing the other image? flat-FW_WRT32X_1.0.180404.58.img
Rename it venom.img, make sure TFTP is pointed to the new file and go through the same serial flash process as before, only this time adding the few envars that were wiped during the reset. Don't forget to disable firewall and set your ethernet adapter's tcp/ip properties.
No good blkt, still stops at the same point during boot .
Well blkt all i can do is thank you for all the time and help you've provided mate, your a genuine star, sadly on this occasion i think the router has a hardware issue.
Very strange how it takes an image and even a u-boot file but it will not boot, stops at the same point as before, cpu self detect stall
Yeah it fails shortly after init ddr with bad len followed by a cpu stall; not sure what Linksys would offer in terms of RMA but maybe worth a shot after posting your results to a support rep. These routers run really hot due to packaging, thermal pad, heatsink design and no fan.
I have managed to get this to a command prompt now, Venom>>
i have downloaded the image from Linksys website its quite small 10,490 KB
I've started the TFTPD server pointed to the firmware etc,
then in the putty window i executed the commands
Venom>> setenv ipaddr 192.168.1.1
Venom>> setenv netmask 255.255.255.0
Venom>> setenv serverip 192.168.1.254
Venom>> run update_both_images
Using egiga0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
i have also tried what was suggested on a youtube guide
setenv firewareName venom.img
also changing firmware_name as was suggested
also setenv firmware_name firmware_venom.img
but still get the retry count exceeded
its like the tftp server is not pushing it
I had the same error...tftp server wasn't on the network since I forgot to reconnect my ethernet. Also assume 192.168.1.254 is the address you used for your NIC?
Posted: Fri Jul 05, 2019 2:41 Post subject: WRT32X Un-Bricked
Finally got the stock firmware installed. Here is what finally worked for me:
Using Adafruit cable (not recommended by me due to poor connections):
setenv ipaddr 192.168.1.1 # modify for your LAN
setenv serverip 192.168.1.2 # modify for your TFTP server
setenv firmwareName venom.img (flat-FW_WRT32X_1.0.180404.58.img saved as venom.img)
ping 192.168.1.1 # confirm LAN
Thanks to everyone for the posts that finally helped me solve this.