Diagnostic Techniques

How to identify the problem after a router gets bricked? This page covers common diagnostic methods.

Bricked States

Fully Bricked

The router is completely unresponsive.

  1. Indicator lights are off
  2. Cannot ping the router
  3. No serial output
  4. Usually indicates Flash or Bootloader damage
Partially Bricked

Some functions work normally, others are abnormal.

  1. Indicator lights are on but cannot access the internet
  2. Web interface inaccessible
  3. Serial may have output
  4. Possible firmware corruption
Soft Brick

Firmware issue but Bootloader is intact.

  1. Can enter Recovery mode
  2. TFTP flashing is effective
  3. Serial may have output
  4. Easiest to recover

LED Status Codes

Indicator light meanings vary by brand.

LED Status Meaning
All lights blinking Starting up
SYS light slow blinking Normal boot
All lights on simultaneously Recovery mode
WAN light orange WAN port not connected
Xiaomi / Redmi
LED Status Meaning
Blue solid Normal
Blue blinking Data transmission in progress
Orange blinking TFTP Recovery mode
Orange solid System anomaly
Off Powered off or damaged
ASUS
LED Status Meaning
Green Power light Normal
Power light blinking Boot in progress
WPS light on WPS connecting
All lights on simultaneously Recovery mode
Netgear
LED Status Meaning
Power light green Normal
Power light orange Firmware corrupted
All lights blinking simultaneously NMRP mode

Serial Log Analysis

Viewing boot logs via TTL Serial is the core of diagnostics.

Normal Boot Log
U-Boot 1.1.4 (Dec  6 2021 - 11:13:09)
CPU: MediaTek MT7621AT
RAM: 256MB DDR3
Flash: W25Q128JV
Hit any key to stop autoboot:  0
## Booting image at 9f020000 ...
  Image Name:   MIPS OpenWrt Linux-5.4.188
  Image Type:   MIPS Linux Kernel Image
  Data Size:    4194304 Bytes
## Loading kernel from 0x9f020000
Common Error Logs
## Error: "bootargs" not defined
# Boot argument error, needs to be reset
## Error: unrecognized filesystem type
# Filesystem corrupted, need to reflash firmware
## JFFS2: magic bits don't match
# JFFS2 filesystem corrupted
Kernel panic - not syncing: VFS: Unable to mount root fs
# Kernel or filesystem issue
MTD: partition "linux" not found
# Flash partition table corrupted
U-Boot Command Diagnostics
# View environment variables
printenv

# View Flash info
sf probe

# Test memory
md.l 0x81000000 10

# View boot arguments
print bootcmd
print bootargs

Network Diagnostics

ping Test
# Test local connectivity
ping 192.168.1.1

# If ping works but Web is inaccessible
# May be a Web service issue, try Telnet
telnet 192.168.1.1
TFTP Connection Test
# Windows
tftp -i 192.168.1.1 get test.txt

# If connection works but transfer fails
# Check firewall and ethernet cable

Recovery Mode Identification

How to Enter Recovery Mode
Method Procedure Applicable Brands
Hardware reset Power off β†’ Hold Reset β†’ Power on β†’ Wait 10 seconds TP-Link
TFTP mode Power off β†’ Hold Reset β†’ Power on β†’ Wait for LED to blink Xiaomi
WPS mode Hold WPS β†’ Power on β†’ Wait for LED to blink ASUS
NMRP mode After boot, run nmrpflash via telnet Netgear
Recovery Mode Characteristics
  1. Router IP defaults to factory address
  2. TFTP server is connectable
  3. Web recovery page is accessible
  4. Serial output shows recovery mode

Hardware Inspection

Voltage Measurement

Use a multimeter to measure voltages at key points:

  1. Power output: 12V/9V/5V DC
  2. Key chips on motherboard: 3.3V, 1.8V, 1.2V
  3. TTL Serial: 3.3V TX/RX
Visual Inspection
  1. Check capacitors for bulging
  2. Check chips for burning
  3. Look for cold solder joints
  4. Check Ethernet ports for damage

Common Troubleshooting

Cannot Enter Recovery Mode
  1. Try holding the reset button for 30 seconds
  2. Check if the reset button is damaged
  3. Measure continuity across the reset button terminals
TFTP Transfer Failed
  1. Replace the ethernet cable
  2. Disable computer firewall
  3. Confirm computer IP settings are correct
  4. Try a different TFTP client
Will Not Boot After Flashing
  1. Confirm firmware matches the model
  2. Check if Flash chip is damaged
  3. Try clearing NVRAM
  4. Reflash via TTL

⚠️ Technical Disclaimer

This tutorial is for learning and reference only. Flashing firmware carries risks and may cause bricked devices or void warranty. Before proceeding:

Last updated: April 2026