[FS#3927] OpenWrt 21.02.0-rc3 bricks Netgear WNDR3700 v4

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Mon Jul 12 05:13:46 PDT 2021


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3927 - OpenWrt 21.02.0-rc3 bricks Netgear WNDR3700 v4
User who did this - Walter Sonius (walterav1984)

----------
3927

Documentation can always be improved for instance on level of detail, scope or even the skill of the user. Its almost a dynamic thing serving different needs for different users, but in its current form it is indeed generic for different kind of hardware and problems. It describes roughly 3 steps of pointing in which direction the problem may exist. Not talking about a specific problem nor about any solution in sight yet! 

It seems you have followed the "1st" failsafe procedures which are indeed not specifically written for your hardware/problem (scattered around wiki/forum/etc/pages). It will help us, if you specifically described what behavior of which leds and timings on your router are responding to draw better conclusions of what may be wrong. This stage is however incredibly vague since different routers use different leds/timings/buttons whatever so I would skip this stage if you haven't took the time earlier to know/understand/verify the leds/buttons responses from a "correctly" working router. Its kind of a blind process, time consuming trial and error procedure... try these procedures the next time before trusting the hardware (to late now). Readon.

However the "2nd" step in this debrick/guide process you started, but never mentioned finishing quoting: "Breaking open the case I see a UART header and some pads for a JTAG but I’m not the guy to debug what broke" is very important! Also it may not only bring you to a specific problem but also very close to a possible solution. 

In the worst case if you only heave header holes on the board, soldering 3 pins for uart and cabling it to a "Raspberry Pi" may bring you unique and valuable insight in text/code form what the problem is exactly. It might even give you the interaction to solve it. Having access to a soldering iron and a Raspberry Pi can be of great value on the 20-ish years IT-skills you already had. Not doing this step may lead to the premature conclusion that the debricking guide is useless!

Not sure if you want/need specific guidance on your debricking problem since one obvious reason for your BUG report is warning others which is a good thing. But I'm quite sure you are quite lucky with this v4 being (atheros) and not broadcom based revision of your routers and you have very high chances of de-bricking it your-self as a OpenWrt developer (not user). Albeit via (tftp) recovery software in Windows from Netgear itself, might work on different models...

Just post more "usefull" info in this bug report, because it will probably be some kind of bootloader kernel/partition size thing which is very likely to get fixed. See this as an example report:
https://bugs.openwrt.org/index.php?do=details&task_id=3750

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3927#comment9914

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the openwrt-bugs mailing list