# EA3500 bricked by nandboot command

**URL:** <https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857>\
**Category:** Installing and Using OpenWrt\
**Created:** [October 25, 2026, 8:45pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857 "2026-10-25T20:45:45Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![tocguy](https://forum.openwrt.org/user_avatar/forum.openwrt.org/tocguy/32/65234_2.png) [@tocguy](https://forum.openwrt.org/u/tocguy)\
**Post date:** [October 25, 2026, 8:45pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/1 "2026-10-25T20:45:46Z")

</div>

Tried AttendedSysUpgrade from 25.12.4 to 25.12.6 on EA3500 Travel router. It failed. SysLog provided explanatory note and remedy instructions that entailed enlarging the boot partition again. It was set at 0x2E6 (shorthand) per fw\_printenv. The SysLog provided command attempts to enlarge from 0x3E6 to 0x4E6. So, that couldn't work because the command was looking for 0x3E6 rather than 0x2E6. Tweaked the command accordingly to swap 0x2E6 with 0x4E6 and the unit transmogrified into the familiar uniform brick shape. Now, power led just rapid flashes forever, alt-boot fails, reset fails, tftp fails.

Other options...?

---

<div class="post-metadata">

**Author:** ![LilRedDog](https://forum.openwrt.org/user_avatar/forum.openwrt.org/lilreddog/32/117047_2.png) [@LilRedDog](https://forum.openwrt.org/u/LilRedDog)\
**Post date:** [October 25, 2026, 8:51pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/2 "2026-10-25T20:51:37Z")

</div>

Plug it in, wait 15 seconds un pluge it.

Do this three times, that could trigger Linksys' fallback, even though you are on OpenWrt.

If it does not work, try 20 seconds. Linksys is looking for:  
First an attempt to boot.  
and then three failures. So it has to get to knowing it tried.

In some Linksys this is baked in and flashing did not change it.

---

<div class="post-metadata">

**Author:** ![tocguy](https://forum.openwrt.org/user_avatar/forum.openwrt.org/tocguy/32/65234_2.png) [@tocguy](https://forum.openwrt.org/u/tocguy)\
**Post date:** [October 25, 2026, 9:11pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/3 "2026-10-25T21:11:28Z")

</div>

Thx, tried the longer intervals to no avail. Had previously tried 5 and 10-second intervals to achieve alt-boot also to no avail. Just constant led flashing... For the sake of completeness, the PC was set to a defined IP within the scope of the router during the test.

---

<div class="post-metadata">

**Author:** ![LilRedDog](https://forum.openwrt.org/user_avatar/forum.openwrt.org/lilreddog/32/117047_2.png) [@LilRedDog](https://forum.openwrt.org/u/LilRedDog)\
**Post date:** [October 25, 2026, 9:13pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/4 "2026-10-25T21:13:34Z")

</div>

Un plug the ethernet and try again.  
Cross fingers.

Or it's going to become a thread on CLI and terminals. The flash can be forced, based on your apparent skills.

---

<div class="post-metadata">

**Author:** ![tocguy](https://forum.openwrt.org/user_avatar/forum.openwrt.org/tocguy/32/65234_2.png) [@tocguy](https://forum.openwrt.org/u/tocguy)\
**Post date:** [October 25, 2026, 10:23pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/5 "2026-10-25T22:23:05Z")

</div>

Finding great conflicting info about the EA3500 and TFTP. Google says that TFTP isn't native to the EA3500 so attempting to send the TFTP boot interrupt from Windows following device power-on is moot. But then Google also says Windows doesn't have a native TFTP app but it actually does and you can guess what its name is. Yup, it's TFTP. AI is so stoooopid. Just need to enable the TFTP app via Windows Options.  
Ok, that aside it appears that a UART solution is the only go-forward option but that's only because I'm er ah, ... frugal. 😉 I have a USB-UART adapter laying around here somewhere. Just need to locate or replace it to see if I can establish any connection with the router. Not that urgent so adding this to my back-burner ToDo list. Sigh...

---

<div class="post-metadata">

**Author:** ![LilRedDog](https://forum.openwrt.org/user_avatar/forum.openwrt.org/lilreddog/32/117047_2.png) [@LilRedDog](https://forum.openwrt.org/u/LilRedDog)\
**Post date:** [October 25, 2026, 10:51pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/6 "2026-10-25T22:51:42Z")

</div>

I can't do it.

But now people have a plan and will step in.

---

<div class="post-metadata">

**Author:** ![LilRedDog](https://forum.openwrt.org/user_avatar/forum.openwrt.org/lilreddog/32/117047_2.png) [@LilRedDog](https://forum.openwrt.org/u/LilRedDog)\
**Post date:** [October 26, 2026, 5:22pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/7 "2026-10-26T17:22:51Z")

</div>

Bump8ty ump ump

---

<div class="post-metadata">

**Author:** ![frollic](https://forum.openwrt.org/user_avatar/forum.openwrt.org/frollic/32/30113_2.png) [@frollic](https://forum.openwrt.org/u/frollic)\
**Post date:** [October 26, 2026, 5:46pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/8 "2026-10-26T17:46:48Z")

</div>

> [@tocguy](#):
>
> Google also says Windows doesn't have a native TFTP app but it actually does and you can guess what its name is. AI is so stoooopid. Just need to enable the TFTP app via Windows Options

Based on the EA3500 wiki page, AI's correct, since you need a TFTP server, while Windows ships with a client.

---

<div class="post-metadata">

**Author:** ![Raddy\_Stowe](https://forum.openwrt.org/letter_avatar/raddy_stowe/32/5_5575768a8748004e209b776fc1b2916d.png) [@Raddy\_Stowe](https://forum.openwrt.org/u/Raddy_Stowe)\
**Post date:** [November 15, 2026, 3:42pm UTC](https://forum.openwrt.org/t/ea3500-bricked-by-nandboot-command/254857/9 "2026-11-15T15:42:37Z")

</div>

Well, the thing is that 25.12.6 build itself breaks all LAN/WAN ports due to the some bug or an error.

> <https://github.com/openwrt/openwrt/issues/26320#issuecomment-6673553741>
>
> \### Describe the bug
> 
> I was running 24.10 and went to upgrade to 25.12.6 today. … The device took the firmware upload through the UI, looked like it was working, and restarted. The result was that the device appeared on, but none of the ethernet ports worked. Restarting didn't help. Even after several restarts, it didn't roll back to the backup firmware. So I assume that the device thinks the upgrade worked. But I still wasn't able to connect. I had to unplug/replug it three times during the boot sequence to trigger rollback to the backup firmware.
> 
> 
> My first thought was that it was too big a jump from 24.10.\* to 25.12.6, so I installed 25.12.3, and that worked perfectly. Then I went to 25.12.5 successfully. Then I tried 25.12.6 again, with the same results. I had to triple unplug/replug to get back to 25.12.5.
> 
> 
> I'm a bit stuck on how to debug this. The device seems to take the 25.12.6 firmware, and doesn't seem to know that it's broken, but when it does I can't connect to it. I don't seem to have any way to get onto the device to see what's going wrong.
> 
> 
> Any suggestions on how I can get more info to help track this issue down? I'm happy to help test where I can.
> 
> \### OpenWrt version
> 
> 25.12.6
> 
> \### OpenWrt release
> 
> 25.12.6
> 
> \### OpenWrt target/subtarget
> 
> kirkwood/generic
> 
> \### Device
> 
> Linksys EA4500 (v1)
> 
> \### Image kind
> 
> Official downloaded image
> 
> \### Steps to reproduce
> 
> Have a Linksys EA4500.
> Be on version 25.12.5
> Try to upgrade to 25.12.6 using the official sysupgrade image and the UI to upload.
> 
> \### Actual behaviour
> 
> Device accepts the upload, restarts, boots, then is uncontactable. I ran ifconfig in a loop during the process and I think I see the link negotiate speed with the client, but after that the connection drops (before any dhcp IP is provided). The ethernet ports don't light up at all once the device is fully on.
> 
> \### Expected behaviour
> 
> \_No response\_
> 
> \### Additional info
> 
> \_No response\_
> 
> \### Diffconfig
> 
> \`\`\`text
> 
> \`\`\`
> 
> \### Terms
> 
> \- \[x\] I am reporting an issue for OpenWrt, not an unsupported fork.
