Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#682 - WNR2000v3 bootloop after installing 17.01.0 #7403

openwrt-bot opened this issue Apr 6, 2017 · 1 comment

FS#682 - WNR2000v3 bootloop after installing 17.01.0 #7403

openwrt-bot opened this issue Apr 6, 2017 · 1 comment


Copy link

openwrt-bot commented Apr 6, 2017


My Netgear WNR2000v3 goes into a bootloop after installing 17.01.0 but is fine with the Trunk snapshot from 6 April 2017.
When it starts up, it gives me 4 pings, then it stops responding until it wakes back up. When it stops responding,m the network interface acts like it is disconnected (no link), then it comes back up just before it responds to pings again.
I had time tonight to plug a serial console into it and record what it does when you install 17.01.0
These were installed with TFTP from the recovery (hold reset for ~30 seconds when powering up, then tftp the image to
Attached are two bootlogs:

  • Bootlog of the upgrade to 17.01 from recovery mode using the lede-17.01.0-r3205-59508e3-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img image (goes into a bootloop after the install): WNR2000V3To17.01UpgradeBootlog.txt
  • Bootlog of the upgrade to the 6 April 2017 nightly (r3922-9613d97) using the lede-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img image (works as expected): WNR2000V3To6April17SnapshotUpgradeBootlog.txt

I saw the same thing installing lede-17.01.0-r3205-59508e3-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img from the factory web interface (Netgear wnr2000v3-V1.1.2.14) but I didnt save a bootlog of that

Let me know if more info is needed.

Aaron Z

Copy link

openwrt-bot commented Aug 27, 2017


The current hardware table says 17.01.2 is the latest LEDE supported release for this model.*~%5D=WNR2000&dataflt%5BVersions*~%5D=V3

However, I'm seeing a similar issue as reported by Aaron Z. Device gets into a reboot loop. Doesn't respond to pings or any network activity unless I do a hard reset on the device. After it resets, I'm able to flash and recover, but that's it.

I verified the img checksum and retried flashing it a couple times. I'm able to recover each time, but the device is unusable after flashing LEDE. Keeps rebooting and is unresponsive. I don't have a serial cable to debug.

I recently tried the latest OpenWrt guide for the WNR2000v3.

I'm able to flash that OpenWrt image fine, but because there's so little space on the device, root mounts as a tmpfs and no changes persist. It's essentially unusable.

I wonder if a similar problem is at play here? Not enough device space for the most recent LEDE builds? I wonder if it makes sense to mark this device as unsupported and either reference an older build or guide users towards building a custom image that'll fit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant