Posted: Sat Sep 04, 2021 23:13 Post subject: Bricked Archer C9v1 need helps
Hi,
I have TP-link Archer C9 v1. I have been using DD-wrt for many years. The last known good firmware I used is around April 2021. After I updated the latest firmware from Sep 2021 or latest Aug one, I'm not sure, the router keeps rebooting itself after 15-30 seconds from powering up.
I'm able to get the TFTP to recovery firmware to be downloaded by the router. I tried the stock TP link firmwares -- 2016, 2018, and 2020 ones. I tried DD-wrt firmware from April 2021 -- factory to DD-WRT and DD-wrt itself. Every time, these firmwares seemed to be triggered and shipped to the router. I'm not sure if they were successfully flashed.
Regardless, all of them didn't solve the issue. The router keeps restart itself.
I'm not sure if this relates but before all of this happened I have "Keep Alive" setting to restart if it can't ping 8.8.8.8 (Google DNS). Flashing, 30-30-30 reset have been tried. These NVRAM should be clear, imo but I've never been sure.
It looks like the problem's to do with nvram can't be open or something
paste the snippet from the console here before I attempt the flash
--
Registering SWP/SWPB emulation handler
found cfe nvram
check if nvram copy is required CFE Size is 65536
nvram copy magic is FFFFFFFF
copy cfe nvram to base nvram
remap nvram 4044
max nvram space = 131072
read 65536 bytes to offset 0
Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
brcmnand: found no supported devices
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 328K
init : starting devinit
cannot open /dev/nvram
udevtrigger[424]: parse_config_file: can't open '/etc/udev/udev.conf' as config file: No such file or directory
init : no previous bootfails detected! (all ok)
init : starting Architecture code for northstar
softdog: Software Watchdog Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=1)
length = 40000
try modules for ethernet adapters
clear nvram
create ctf proc
et_module_init: passivemode set to 0x0
et_module_init: txworkq set to 0x0
et_module_init: et_txq_thresh set to 0x400
et_module_init: et_rxlazy_timeout set to 0x3e8
et_module_init: et_rxlazy_framecnt set to 0x20
et_module_init: et_rxlazy_dyn_thresh set to 0
robo attach
robo id 53012
attaching FA
CHIPID 53010, rev 5
aux0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.18 (r692288)
robo attach
robo id 53012
Posted: Wed Sep 08, 2021 9:19 Post subject: Re: Bricked Archer C9v1 need helps
jerryjyrer wrote:
Successfully flashed back to the stock firmware. Case's closed!!
CFE> ^C
CFE> ifconfig
Device eth0: hwaddr 00-90-4C-11-20-01, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
*** command status = 0
CFE> flash -noheader 192.168.1.66:12.bin flash0.trx
Reading 192.168.1.66:12.bin: Done. 15335424 bytes read
Programming...done. 15335424 bytes written
*** command status = 0
CFE> flash -noheader -offset=0xfe0000 192.168.1.66:mtd3.bin flash0
Reading 192.168.1.66:mtd3.bin: Done. 65536 bytes read
Programming...done. 65536 bytes written
*** command status = 0
CFE> go
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .... 4232512 bytes read
Entry at 0x00008000
Closing network.
Starting program at 0x00008000
Hi, @jerryjyrer , thank you for answering my post about bricked archer c9 v4 router. Can you please point out to / where / how to obtain those bin images that you successfully used on your router?
Cheers! _________________ Villager of the Globe we all live in.
Used dd-wrt on:
ARCHER C9 - V.4 (EU)
(In a lingering "resurrection" state, will it revive? Stay tuned folks... )
I don't think those apply to the v4. All you should have to do is put it into recovery mode and TFTP.
Hi again, I have just posted in the thread that I have created.
Ok, @kernelpanic69, you say tftp should be the only thing I would need. Do you think I should post the boot serial terminal output to try to debug this?
For now I feel "lost". Besides having tried to flash too experimental a build and having bricked the damn router... I can't even settle down and focus on a path to recover it... (That's supposing it is recoverable).
But thank you. I will try and settle down first and then summarize things and see if I can be more helpful at getting ... "help"
See you soon... Hopefully... _________________ Villager of the Globe we all live in.
Used dd-wrt on:
ARCHER C9 - V.4 (EU)
(In a lingering "resurrection" state, will it revive? Stay tuned folks... )