Table of Contents
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.
- Indicator lights are off
- Cannot ping the router
- No serial output
- Usually indicates Flash or Bootloader damage
Partially Bricked
Some functions work normally, others are abnormal.
- Indicator lights are on but cannot access the internet
- Web interface inaccessible
- Serial may have output
- Possible firmware corruption
Soft Brick
Firmware issue but Bootloader is intact.
- Can enter Recovery mode
- TFTP flashing is effective
- Serial may have output
- Easiest to recover
LED Status Codes
Indicator light meanings vary by brand.
TP-Link
| 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
- Router IP defaults to factory address
- TFTP server is connectable
- Web recovery page is accessible
- Serial output shows recovery mode
Hardware Inspection
Voltage Measurement
Use a multimeter to measure voltages at key points:
- Power output: 12V/9V/5V DC
- Key chips on motherboard: 3.3V, 1.8V, 1.2V
- TTL Serial: 3.3V TX/RX
Visual Inspection
- Check capacitors for bulging
- Check chips for burning
- Look for cold solder joints
- Check Ethernet ports for damage
Common Troubleshooting
Cannot Enter Recovery Mode
- Try holding the reset button for 30 seconds
- Check if the reset button is damaged
- Measure continuity across the reset button terminals
TFTP Transfer Failed
- Replace the ethernet cable
- Disable computer firewall
- Confirm computer IP settings are correct
- Try a different TFTP client
Will Not Boot After Flashing
- Confirm firmware matches the model
- Check if Flash chip is damaged
- Try clearing NVRAM
- Reflash via TTL