Opened a ticket on Trac to report on WDR3600 bricking on r26081 and I think anyone can add more comments or details on the ticket to describe how their WDR3600 are bricked. Info such as whether 30/30/30 reset was done, and what the status LEDs are doing maybe helpful for developers.
Hopefully, this issue with bricking TP-Link routers especially the WDR4300 and WDR3600 can be resolved quickly.
Joined: 05 Dec 2014 Posts: 52 Location: The Netherlands
Posted: Fri Jan 30, 2015 22:48 Post subject:
KrypteX wrote:
Pattagghiu wrote:
emilioditurio wrote:
Router Model: Netgear WNDR3700v1
Status: Up
Reset: no
Errors: Yes
Web flash failed from r25974 to r26081. TFTP recovery to r26081 worked.
i really can't understand this "alea" in web flash.. my 3700v2 update was perfect by web flash.. from 25974 to 26081..
Me neither. Flashed WNDR3800 from 25974 to 26081, didn't brick. It actually never bricked and I've tried ALL builds released in the last year, even going back and forth between them, several times.
They say it doesn't matter, but I always do a 30/30/30 reset before and after flash and clear the Firefox cache. And I always disconnect the WAN cable and the USB drive, leaving only the LAN cable used for flashing.
Bad luck, I think.. 95% of the web-flashes are going good..
Opened a ticket on Trac to report on WDR3600 bricking on r26081 and I think anyone can add more comments or details on the ticket to describe how their WDR3600 are bricked. Info such as whether 30/30/30 reset was done, and what the status LEDs are doing maybe helpful for developers.
Hopefully, this issue with bricking TP-Link routers especially the WDR4300 and WDR3600 can be resolved quickly.
Status: Up
Reset: No
Errors: Can't view the internet. Reset multiple times but only rolling back to the last version fixed it and allowed it to see the internet.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Jan 31, 2015 5:00 Post subject:
wrong forum r7000 is broadcom, this is atheros.
also broadcom just got a new driver which was having problems so it was reverted to the previous driver, but according to timeline bs fixed the issues & reenabled it in builds after r26081 _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Opened a ticket on Trac to report on WDR3600 bricking on r26081 and I think anyone can add more comments or details on the ticket to describe how their WDR3600 are bricked. Info such as whether 30/30/30 reset was done, and what the status LEDs are doing maybe helpful for developers.
Hopefully, this issue with bricking TP-Link routers especially the WDR4300 and WDR3600 can be resolved quickly.
I will try to flash mine tonight or tomorrow morning and if it gets bricked, I'll add console output to the ticket.
[ 0.980000] No filesystem could mount root, tried: squashfs
[ 0.980000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
Those are the last lines before reset, full console output attached.
Can't update ticket, I can't register (Submission rejected as potential spam). Please someone update ticket with the console output...
Posted: Sat Jan 31, 2015 7:03 Post subject: Re: New Build - 01/29/2015 - r26081
Router Model: TL-WDR3600
Status: Flash from 1-20 firmware (25974)
Reset: No
Errors: Bricked, flashing LEDs and repeated reboot, attempted recovery seems to illuminate the some LED on the right side with two arrows in a circle - never seen that before - probably recovery mode? Correct LAN port "PC" LED flashes, but it resets without requesting firmware (my PC is set to 192.168.0.66). It never negotiates a connection and nothing pops up. Tool lazy to open it tonight, but I'll be recovering through UART tomorrow. Getting tired with these brickings, I'll check the forums in the future.
also broadcom just got a new driver which was having problems so it was reverted to the previous driver, but according to timeline bs fixed the issues & reenabled it in builds after r26081
Oops my bad, I did the search quick after this version failed to report it. Just looked though and it looks like there isn't one for the Broadcom, not sure if its cool I make the topic myself.
